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:
| 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 under | 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 |
| FAQ | Frequently Asked Questions | Everyone |
| 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 |
| 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 |
| Glossary of Geocoder Terms | Defines all technical terms used 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 addresses matches are ranked by the geocoder. A companion document to Understanding Address Match Scoring | Geocoder clients, app developers, address data suppliers |
| Batch Geocoder User Acceptance Test Plan | Plan for user acceptance testing of new versions of the geocoder | Batch geocoder clients |
| Examples of addresses Geocoder 4.0 didn't handle well | Common types of bad addresses that geocoder 4.0 didn't handle well. They are mostly handled in Geocoder 4.1. They were discovered by analysing some of the biggest address lists in government | Geocoder clients, app developers |
| Geocoder 4.1 Product Development Plan | List of tasks and their status in support of geocoder 4.1 development | Geocoder clients, app developers. |
| Addresses for geocoder feature and configuration data testing | List of test addresses for QA of new versions of the geocoder | Geocoder clients, app developers |
| Addresses for verifying presence of addresses from every locality in BC | One address from every locality in BC to be used in verification of latest release of Geocodable BC which is the reference data the geocoder will use | BC Geocoder administrators, geocoder prospects |
| Geocoder configuration files | Configuration files for the BC Address Geocoder which is a reference deployment of the OLS Address Geocoder. Configuration data includes abbreviations used in street and site names, unit designators, and locality aliases. Abbreviations and unit designators are a super-set of those found in the Canada Post Mailing Address Standard | Geocoder developers and operators, other Canadian jurisdictions considering adoption of the geocoder, anyone interested in a deeper understanding of the geocoder |
| 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 |
| Draft BC Physical Address Conceptual Model v2 | 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 |
| 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 |
| OpenStreetMap Suitability Addresses | Random addresses selected for use in the OSM suitability study | App developers |
| Geocoder Roadmap | Planned major enhancements to the geocoder | Everyone |
| Geocoder Standards Roadmap | Planned standards and updates to existing standards | Data administrators, geocoder clients,app developers,address authorities, address data suppliers |
| OLS Geocoder Installation Instructions | Instructions for installing OLS-Geocoder in your own environment | Developers |