We currently have 2 resources that do basically the same thing, parse an address string into its component parts.
/parse is a general-purpose parser, and generally returns the results directly from the usaddress library, even allowing usaddress-specific features to be passed in on the request.
/standardize is very opinionated, and geared to what our Census TIGER-based geocoder needs.
I would like to refactor /parse, abstracting away any usaddress specifics, and incorporating any features in /standardize that make it useful for our specific needs. Now seems like a good time to do this as we're rearranging the guts up of the geocoder now anyway.
We currently have 2 resources that do basically the same thing, parse an address string into its component parts.
/parseis a general-purpose parser, and generally returns the results directly from theusaddresslibrary, even allowingusaddress-specific features to be passed in on the request./standardizeis very opinionated, and geared to what our Census TIGER-based geocoder needs.I would like to refactor
/parse, abstracting away anyusaddressspecifics, and incorporating any features in/standardizethat make it useful for our specific needs. Now seems like a good time to do this as we're rearranging the guts up of the geocoder now anyway.I will post my proposed changes shortly.