Automate BC Geographical Names
HumDay reads BC Geographical Names’s own published API description and derives 14 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What BC Geographical Names is
This REST API provides searchable access to information about geographical names in the province of British Columbia, including name status and details about the corresponding geographic feature. Please note that you may experience issues when submitting requests to the delivery or test environment if using this [OpenAPI specification](https://github.com/bcgov/api-specs) in other API console viewe
API host: apps.gov.bc.ca
What HumDay can read from BC Geographical Names
These are the operations a schedule or a trigger can watch.
- GETSearch near to a geographic point
/names/near - GETSearch in a geographic area
/names/inside - GETSearch by name
/names/search - GETSearch for names with metadata changes in a given period
/names/changes - GETSearch for names affected by naming decisions in a given year
/names/decisions/year - GETSearch by name, limit to official names only
/names/official/search - GETSearch for names affected by recent naming decision
/names/decisions/recent - GETSearch by name, limit to unofficial names only
/names/notOfficial/search - GETGet all feature types
/featureTypes - GETGet all feature classes
/featureClasses - GETGet all name authorities
/nameAuthorities - GETGet all feature categories
/featureCategories - GETGet a feature by its featureId
/features/{featureId} - GETGet a name by its nameId
/names/{nameId}.{outputFormat}
How automating BC Geographical Names works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- 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.
- See it proven. The program runs and shows you the result before it is allowed near your live BC Geographical Names account.
- Grant access, then go live. You approve the specific BC Geographical Names operations it may use — and only those.
Automate BC Geographical Names with these
- BC Data Catalogue22 operations
- BC Geocoder16 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
Questions about BC Geographical Names automation
- Can HumDay connect to BC Geographical Names?
- Yes. HumDay reads BC Geographical Names's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 14 operations are documented.
- Do I need to write code to automate BC Geographical Names?
- 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 Geographical Names account.
- What can HumDay do in BC Geographical Names?
- 0 of the 14 documented operations change something in BC Geographical Names, and 14 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my BC Geographical Names 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 Geographical Names is held behind that approval.
Where this came from
The operations above are read from a published API description for BC Geographical Names at raw.githubusercontent.com/bcgov/api-specs/master/bcgnws/bcgnws.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.