Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fails to parse certain US address (Like the ones on Highways) #3

Open
ChandanNM opened this issue Apr 25, 2016 · 7 comments
Open

Fails to parse certain US address (Like the ones on Highways) #3

ChandanNM opened this issue Apr 25, 2016 · 7 comments

Comments

@ChandanNM
Copy link

We are using this library in our application. Has worked fairly well for most of the US addresses, however fails for certain unusual valid ones like - "N95W18000 Appleton Ave, Menomonee Falls, WI 53051" or other highway addresses. Can this library be enhanced to handle those ?

@hassansin
Copy link
Owner

I'm getting following for the above address:

{ street: 'N95W18000 Appleton',
  type: 'Ave',
  city: 'Menomonee Falls',
  state: 'WI',
  zip: '53051' }

Is it supposed to be different?

@simpixelated
Copy link

Not sure how common this is, but when there's a street type in the name of the street, I'm getting incorrect results. e.g. "3180 N Harbor Dr, San Diego, CA 92101, USA" results in:

{number: "3180", street: "N", type: "Harbor"}

Will need to dig into the code to see if there's an easy fix, but maybe you could look for two occurrences of type and assume the first one is meant to be part of the street name?

@cgirod3
Copy link

cgirod3 commented Sep 6, 2017

+1 to ^. I came here with a similar issue, 34 E Terrace Ave, Flagstaff, Arizona 86001, United States fails to parse, likely due to Terrace being a type? Not sure if this is being monitored still.

Also potentially unrelated, 540 E, Ogden, Utah 84404 fails to parse though is valid

@aannecchiarico
Copy link

Fails to parse highway addresses for example: "112 LEE RD 795"

@cody-lettau
Copy link

Has anyone figured out a fix for these issues?

@liamhession
Copy link

The case of "3180 N Harbor Dr, San Diego, CA 92101, USA" not being parsed correctly, plus others I've seen, is fixed by removing the ", USA" portion. So if you input "3180 N Harbor Dr, San Diego, CA 92101" at http://hassansin.github.io/parse-address/ you'll see it parsed as desired.

@canand2810
Copy link

Hello all this address => 2631 HIGHWAY J BOURBON MO 65441 is getting parsed like below
"number": "2631",
"street": "HIGHWAY",
"city": "J BOURBON",
"state": "MO",
"zip": "65441"
}
But i think the street should be HIGHWAY J. Is there a fix for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants