-
Notifications
You must be signed in to change notification settings - Fork 0
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
geocoding improvements #22
Comments
2400 block of Colerain Ave was matched to the entire length of Colerain Ave. Upon further inspection, I don't think the 2400 block exists... the street is not continuous and jumps from 2100s to 2600s. When our desired outcome is a matched street range geography (as in |
Returning the numerically nearest street range would be a good option to provide instead of the union when the street is matched but the ranges do not contain the street number. edit: tracking this specific change in #29 |
I noticed when using e.g.,
The street suffixes are abbreviated in TIGER and not addr, but this doesn't cause a problem for lots of other addresses. Could this be related to the "number of edits" matching? I also don't see any interstates in the TIGER street ranges. Are those getting filtered out? |
Compare the address tags in those two cases. Maybe getting parsed incorrectly? |
yes, so this is related to #27. will track there. except the Taft one is just the difference in "H" vs "Howard" |
now that we have this broken up into more modular issues, closing tracking here. |
tiger_street
versustiger_range
#28The text was updated successfully, but these errors were encountered: