BC Address Geocoder
The BC Address Geocoder provides REST APIs for address cleaning, correction, completion, geocoding, and reverse geocoding. The BC Address Geocoder has processed over one billion addresses since its initial release in 2013. To see it in use by an application, visit Location Services in Action.
For more information about using the BC Address Geocoder and incorporating it into your automated workflows, please consult the following documents:
Getting Started
Section titled “Getting Started”| Document | Description | Audience |
|---|---|---|
| Open Location Services Product Vision | Explains why BC built a geocoder and other products in its Open Location Services product line | Everyone |
| Location Services by the Numbers | Usage and adoption statistics | Everyone |
| License | License under which all documents and source code in this repository are released | Everyone |
| Copyright Notices | Copyright notices of all software packaged used by this repository | Everyone |
| What’s New | What’s new in latest release of Geocoder | Everyone |
| Geocoder Roadmap | Planned major enhancements to the geocoder | Everyone |
| FAQ | Frequently Asked Questions | Everyone |
| Glossary of Geocoder Terms | Defines all technical terms used by the geocoder | Geocoder clients, app developers, address data suppliers |
Batch Geocoder
Section titled “Batch Geocoder”| Document | Description | Audience |
|---|---|---|
| How to Register to Use the Batch Geocoder | If you have a very long list of addresses, here’s the three-step process to getting access to the batch geocoder | Anyone in a crown corporation, local or federal government, local health authority, or university |
| Preparing Your Address File for Batch Geocoding | An example-driven introduction to the input formats supported by the Address List Editor and the batch geocoder | Everyone |
| Batch Geocoder Application Guide | Step by step tutorial on submitting your address list to the batch geocoder | Everyone |
| Understanding Batch Geocoder Output | An example-driven introduction to the geocoder scoring system and the many fault messages that can help you pinpoint data issues | Everyone |
| Rejected Addresses | Common types of bad addresses that earlier versions of the geocoder didn’t handle well | Geocoder clients, app developers |
| Batch Geocoder User Acceptance Test Plan | Plan for user acceptance testing of new versions of the geocoder | Batch geocoder clients |
Developer Guide
Section titled “Developer Guide”| Document | Description | Audience |
|---|---|---|
| Geocoder Developer Guide | Learn the online geocoder API through a series of examples | App developers |
| Single-Line Address Format | The single-string format of addresses supported by the geocoder | Geocoder clients, app developers, address data suppliers |
| Understanding Address Match Scoring | Explains how address matches are ranked by the geocoder | Geocoder clients, app developers, address data suppliers |
| Geocoder Address Match Scoring Reference | Defines how address matches are ranked by the geocoder | Geocoder clients, app developers, address data suppliers |
API Reference
Section titled “API Reference”| Document | Description | Audience |
|---|---|---|
| OpenAPI Reference | Interactive API documentation for all geocoder REST endpoints | App developers |
Comparisons
Section titled “Comparisons”| Document | Description | Audience |
|---|---|---|
| Comparative Address Geocoder Match Accuracy Study | A comparison between Bing Maps, ESRI, Google Maps, and Here | Everyone |
| OpenStreetMap Suitability Study | Is OSM a suitable base map to display addresses from the BC Address Geocoder? | App developers |
Addressing Standards & Data
Section titled “Addressing Standards & Data”| Document | Description | Audience |
|---|---|---|
| BC Physical Address Exchange Schema | Defines a schema for the exchange of reference addresses between address authorities and geocoding service providers | Address authorities, app developers, geocoder developers and operators |
| Physical Address Conceptual Model | Defines what a physical address is and how it differs from a mailing address | Address authorities, address data suppliers, app developers, geocoder clients |
| Geocoder Data Integration Process | An overview of geocoder data integration process and a proposal to improve its implementation | Geocoder developers |
Reference Data & Configuration
Section titled “Reference Data & Configuration”| Document | Description | Audience |
|---|---|---|
| Geocoder Configuration Files | Configuration files for the BC Address Geocoder including abbreviations, unit designators, and locality aliases | Geocoder developers and operators, other Canadian jurisdictions |
| Test Addresses | List of test addresses for QA of new versions of the geocoder | Geocoder clients, app developers |
| BC Address Coverage Test Addresses | One address from every locality in BC for verification of Geocodable BC | BC Geocoder administrators, geocoder prospects |
| OSM Suitability Test Addresses | Random addresses selected for use in the OSM suitability study | App developers |
Installation
Section titled “Installation”| Document | Description | Audience |
|---|---|---|
| OLS Geocoder Installation Instructions | Instructions for installing OLS-Geocoder in your own environment | Developers |