Automate BC Geocoder

What BC Geocoder is

This API represents address cleaning, correction, completion, geocoding, reverse geocoding, and proximity resources for intersection addresses, physical addresses and their occupants in British Columbia. Please read our [data collection notice](https://github.com/bcgov/api-specs/blob/master/COLLECTION_NOTICE.md#collection-notice). Please note that you may experience issues when submitting requests

API host: geocoder.api.gov.bc.ca

What HumDay can read from BC Geocoder

These are the operations a schedule or a trigger can watch.

• GETGeocode an address/addresses.{outputFormat}
• GETFind sites near to a geographic point/sites/near.{outputFormat}
• GETFind sites in a geographic area/sites/within.{outputFormat}
• GETFind the site nearest to a geographic point/sites/nearest.{outputFormat}
• GETFind occupants of sites near to a geographic point/occupants/near.{outputFormat}
• GETFind occupants of sites in a geographic area/occupants/within.{outputFormat}
• GETFind occupants of the site nearest to a geographic point/occupants/nearest.{outputFormat}
• GETFind intersections near to a geographic point/intersections/near.{outputFormat}
• GETGeocode an address and identify site occupants/occupants/addresses.{outputFormat}
• GETFind intersections in a geographic area/intersections/within.{outputFormat}
• GETFind nearest intersection to a geographic point/intersections/nearest.{outputFormat}
• GETGet a site by its unique ID/sites/{siteID}.{outputFormat}
• GETGet an occupant (of a site) by its unique ID/occupants/{occupantID}.{outputFormat}
• GETGet an intersection by its unique ID/intersections/{intersectionID}.{outputFormat}
• GETGet a comma-separated string of all pids for a given site/parcels/pids/{siteID}.{outputFormat}
• GETRepresents all subsites of a given site/sites/{siteID}/subsites.{outputFormat}

How automating BC Geocoder works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live BC Geocoder account.
4. Grant access, then go live. You approve the specific BC Geocoder operations it may use — and only those.

Automate BC Geocoder with these

• BC Data Catalogue22 operations
• BC Geographical Names14 operations
• BC GeoMark7 operations
• BC Gov News 1.027 operations
• BC Groundwater Wells, Aquifers and Registry24 operations
• BC Route Planner24 operations
• DriveBC's Open5114 operations
• WorkBC Job Posting5 operations
• Monarchinitiative BioLink164 operations
• UniCourt Enterprise158 operations
• OSF APIv2 Documentation156 operations
• IllumiDesk143 operations

Categories

• Open data

Questions about BC Geocoder automation

Can HumDay connect to BC Geocoder?

Yes. HumDay reads BC Geocoder's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 16 operations are documented.

Do I need to write code to automate BC Geocoder?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your BC Geocoder account.

What can HumDay do in BC Geocoder?

0 of the 16 documented operations change something in BC Geocoder, and 16 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my BC Geocoder account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to BC Geocoder is held behind that approval.

Where this came from

The operations above are read from a published API description for BC Geocoder at raw.githubusercontent.com/bcgov/api-specs/master/geocoder/geocoder-combined.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.