...
In collaboration with Treasurer/Tax Collector and the Department of Public Health, we have written a restful street address geocoding service available. This page describes the that service. We try to follow the OGC geocoding standard which is described here. The service uses EAS addresses. While EAS addresses are bound to the street network, the results will differ significantly from a street network geocoding service. For example, if you try to geocode "100 Main St" using this service, you will get zero candidates. That's because (at the time of this writing) there is no "100 Main St" in EAS. Although there is a street segment that supports "100 Main St" there is no building or proposed building that has that address. Why use EAS geocoding? If you want units or parcels that are associated with an address, this is probably your best bet. EAS addresses are curated and maintained (not mined) and we synchronize the streets and parcels with Dept. of Public Works on a daily basis. To see what EAS address look like, check out the web interface which is here (internal).
User Contacts
| Contact | Department |
|---|---|
| Richard Hagner | Treasurer/Tax Collector |
Darrell Ascano | Treasurer/Tax Collector |
| Stephanie Cowles | Department Dept. of Public Health |
| Aksel Olsen | Dept. of Planning |
The Request
Here is the URL (DEV) with an example address of "100 Main St":
...
The service will geocode about 1000 addresses per minute.
...
Source Code
The server code is here and here.
The tests are over here.
And here is a working command line client and a sample data file.
Example URLs and Response
...
A query for 1000 Pine returns lots of units.
Example Client
Here is an example client written in python.