You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using this library in our application. Has worked fairly well for most of the US addresses, however fails for certain unusual but valid ones like - "N95W18000 Appleton Ave, Menomonee Falls, WI 53051" or other highway addresses. Can this library be enhanced to handle those ?
The text was updated successfully, but these errors were encountered:
I've never seen a US street address with a street number with letters in like that. However, I searched for this address and it appears to be real. Strange. This case also fails with a competing parser:
A pull request would accepted that fixes this case without breaking the other test cases.
markstos
changed the title
Fails to parse certain US address (Like the ones on Highways)
Fails to parse "N95W18000 Appleton Ave, Menomonee Falls, WI" (PR welcome)
Apr 26, 2016
A core concept of the street address number is that it is in-fact a number.
This seems like some sort of highway marker where we would need to implement a special construct similar to apartment/unit to handle this.
I'm not familiar with the US Highway Address formats, I did find this spec from USPS, which I assume would contain a specification for the address format. http://pe.usps.com/text/pub28/welcome.htm
We are using this library in our application. Has worked fairly well for most of the US addresses, however fails for certain unusual but valid ones like - "N95W18000 Appleton Ave, Menomonee Falls, WI 53051" or other highway addresses. Can this library be enhanced to handle those ?
The text was updated successfully, but these errors were encountered: