Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

http://10.250.60.189/validate/streetAddress/100%20main%20St/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:

Code Block
{
    "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%.
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.

Here are validation links to 10 random addresses from  the 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

...