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

Insufficient anchor points on segment #380

Closed
BK01 opened this issue Aug 14, 2019 · 3 comments
Closed

Insufficient anchor points on segment #380

BK01 opened this issue Aug 14, 2019 · 3 comments

Comments

@BK01
Copy link
Collaborator

BK01 commented Aug 14, 2019

The correct location of the following address is not found using adaptive or linear. Rather a block level match is found.

4760 Roger St, Port Alberni, BC

Following review of surrounding sites as well as intersections we can see that insufficient anchor points are available per segment for successful adaptive interpolation. In particular the segment of Roger St closest to the address is broken by an emergency lane.

@BK01 BK01 changed the title Minimal anchor points on segment Insufficient anchor points on segment Aug 14, 2019
@cmhodgson
Copy link
Collaborator

It is true that there are two many segments with no enough address points. However it is weird that the access point for 4780 Roger St is so far down the road, rather than being placed on the segment immediately in front of the parcel. I suspect that anchor points from other sources are making this worse instead of better. There is definitely room for smarter address assignment logic in cases where there is a shortage of information (likely only a couple of anchor points and a single parcel point). The extra segment breaks due to the rail crossing and emergency lane work against the post-smoothing logic, as does the apparent offset in addressing between the sides of street, and the existence of the same-name side-street branches.

@mraross
Copy link
Contributor

mraross commented Aug 15, 2019

I added an additional address on each side of the emergency lane (4760 and 4724) to sites_databc.csv. That should give the address range maker a little more grist for the mill.

@mraross
Copy link
Contributor

mraross commented Sep 21, 2019

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

@mraross mraross closed this as completed Sep 21, 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

3 participants