Street Address Validation

Introduction

In collaboration with the Treasurer/Tax Collector we are making a street address validation service available.
This page describes this service.
This is the first version and we are waiting on the Treasurer to comment.

The Service

Here is the DEV URL with an example address of "100 Main St":

http://10.250.60.189/validate/streetAddress/ADDRESS STRING/

This validation uses the street segment network only.
These data are carefully maintained by Dept of Public works.
This service does not validate against the EAS addresses.

This returns JSON like so:

{
    "addressString": "100 main St", 
    "foundMatch": true, 
    "addressNumber": "100", 
    "street": {
        "streetNamePrimary": {
            "base_street_name": "MAIN", 
            "street_type": "ST"
        }, 
        "streetNameAliases": [], 
        "l_f_add": 101, 
        "l_t_add": 199, 
        "r_f_add": 100, 
        "r_t_add": 198, 
        "seg_cnn": 8628000
    }, 
    "validations": [], 
    "didYouMean": []
}

We strongly prefer JSON but we can produce XML if you buy us a beer.
We have tested the DEV implementation against a random sample of 1% of the Treasurers data and the success rate is about 95%.
You can see the unit tests here.
We get parse failures on addresses like this one: PMB 169 3701 SACRAMENTO ST
In the next iteration I am planing on including geocoding and zip code look up.

Examples

Below are validation links to 10 random addresses from the Treasurer's database.

1501 HOWARD ST
PMB 169 3701 SACRAMENTO ST
1560 DAVIDSON AVE
331 CORTLAND AVE
2000 FILLMORE ST
1017 DIVISADERO ST
1618 UNION ST
2250 PINE ST
559 PACIFIC AVE
157 NOE ST
1000 18TH

The JSON is formatted for readability but your browser may obscure that.
The way to see the nicely formated JSON is to right click on the web page and select "view source".
The Chrome browser has a nice feature here:

view-source:http://10.250.60.189/validate/streetAddress/1560%20DAVIDSON%20AVE/