Official areas and zones for each address
get_location_factsFor up to 200 addresses or points, the official areas each one falls in, from our own copies of the official maps. Name the fields you need to keep the answer short. US: census tract (GEOID) and FFIEC income level (LMI), county, metro area, SBA HUBZone, Opportunity Zone, USDA Rural Development eligibility, FEMA flood zone (high-risk SFHA, base flood elevation). Great Britain: conservation area, listed buildings within 60 m, the nearest UPRN, and England's Environment Agency flood zone (1, 2 or 3); in England also the council, green belt, Article 4 directions and tree preservation orders (where the council has published them: otherwise "not published by this council", never none), and national landscapes. Controlled parking zones (London Borough of Haringey so far, all its zones): the zone, its hours, whether the controls are on right now (UK time, bank holidays), null with depends_on when it turns on something we can't see (a stadium event, a pay bay's own hours, a spot on a zone's edge, a weekend Christmas), how far the spot is from the zone's edge and the nearest pay-by-phone bays, with a sentence to read out (says; lists over 25 rows get the short form: zone, hours, controls_now, depends_on): for "which parking zone am I in, can I park here now?" send the person's "lat,lng" or a full address with its postcode. For a whole road ("when is Pellatt Grove permit holders only? any pay and display?"), send roads (names, with the postcode district if you know it): each stretch of the road with its zone, the hours its resident bays are for permit holders only and whether that is on now, and every pay-by-phone bay on it with its paying hours (Haringey's pay-and-display became pay by phone, RingGo: those are its paid bays; TfL red routes on it are said), with a sentence to read out; two roads of one name both come back, each with its district. An address placed only on its street gets the whole road's answer (whole_road: true). A spot on or beside a TfL red route says so (red_route). When the account asking has a resident permit on file, each spot or road also says whether the permit covers it (permit_covers, with_your_permit; parking.your_permit names it). Each record says how it was placed; addresses we cannot place are listed with the reason. A guide, not an official determination.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| roads | No | Parking along whole roads, by name (Haringey so far): "Pellatt Grove", "Park Road, N8", "Lordship Lane". Answers come back in roads, not records; no addresses needed. A road we don't hold, or a place or district that rules it out, comes back ok:false with the reason and did_you_mean; one answered under another name says so first (note, matched_as). | |
| fields | No | Only these facts (default: all that apply). flood is FEMA in the US, the Environment Agency in England. parking_zone answers inside Haringey by default; named, it says "held for Haringey only so far" elsewhere. | |
| region | No | Optional; worked out per address from its postcode or ZIP. | |
| source | No | Instead of typing rows: { sheet: "<Google Sheets link>", tab?: "Sites" } (shared with the InstaMaps service account, or viewable by anyone with the link), { file: "<Drive link to a CSV or Excel file>" }, or { run: "<run_id from an earlier answer>" }. Columns are found by their headers (id, name, address or its parts, lat/lng); name them if they aren't obvious (id_column, address_column, lat_column, lng_column; from_column and to_column for road distances). Rows with coordinates are used as they are. | |
| records | No | {id, address} or {id, lat, lng}. Send your own ids to merge results back. | |
| addresses | No | Or plain addresses/postcodes, numbered from 1. | |
| background | No | With source: run as a background job and answer at once with job_id (automatic past 150 rows). Check with get_job; write_to_sheet with the job_id puts the results in the sheet as they finish. |