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

Two addresses for the same parcel: 588 Cedar Pl, Duncan, BC and 588 Cedar Ave, Duncan, BC #197

Closed
mraross opened this issue May 5, 2017 · 6 comments

Comments

@mraross
Copy link
Contributor

mraross commented May 5, 2017

588 Cedar Pl and 588 Cedar Ave occupy the same parcel.

@mraross mraross added the data label May 5, 2017
@mraross
Copy link
Contributor Author

mraross commented May 5, 2017

geocoder_703 may 05 12 36

@mraross
Copy link
Contributor Author

mraross commented May 5, 2017

In the screenshot above, 588 Cedar Pl and 588 Cedar Ave occupy the same parcel. They came from two different sources. One of them is wrong.

@mraross mraross changed the title Two address for same parcel: 588 Cedar Pl, Duncan, BC and 588 Cedar Ave, Duncan, BC Two addresses for same parcel: 588 Cedar Pl, Duncan, BC and 588 Cedar Ave, Duncan, BC May 5, 2017
@mraross mraross changed the title Two addresses for same parcel: 588 Cedar Pl, Duncan, BC and 588 Cedar Ave, Duncan, BC Two addresses for the same parcel: 588 Cedar Pl, Duncan, BC and 588 Cedar Ave, Duncan, BC May 5, 2017
@cmhodgson
Copy link
Collaborator

Can you think of a way we would programmatically tell the difference between this and for example your favorite, the Central Building, with valid addresses on 4 streets spanning 3 parcels?

@mraross
Copy link
Contributor Author

mraross commented May 5, 2017

The civic numbers are identical in this case. In general, the cases are:

  1. Same civic numbers and suffixes, different something else.

    • worth looking into
  2. Different civic numbers and suffixes, same everything else.

    • probably ok
  3. Different everything.

    • worth looking into

@cmhodgson
Copy link
Collaborator

We could potentially consider developing an address range QA process that put the points onto the parcel fabric and pointed out all of the potential issues.

@mraross
Copy link
Contributor Author

mraross commented Oct 22, 2019

Issue moved to bcgov/ols-geocoder #48 via ZenHub

@mraross mraross closed this as completed Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants