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.

Sign up for GitHub

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

Jump to bottom

Incorrect matches of short segments at some three way intersections? #26

Open
mharnold opened this issue Apr 14, 2015 · 4 comments
Open

Incorrect matches of short segments at some three way intersections? #26

mharnold opened this issue Apr 14, 2015 · 4 comments
Labels
bug

Comments

@mharnold
Copy link
Owner

Paul Cone noted some 'false positives' in matching OSM to RLIS in the Portland area that suggest that the spiderosm core algorithm is failing to properly match intersections in these cases?

Adding images of example cases as separate comments.
@mharnold mharnold added the bug label Apr 14, 2015
@mharnold
Copy link
Owner Author

CASE 1

screen shot 2015-04-14 at 12 31 40 pm

@mharnold
Copy link
Owner Author

CASE 2

screen shot 2015-04-14 at 12 34 03 pm

@mharnold
Copy link
Owner Author

CASE 3

screen shot 2015-04-14 at 12 35 32 pm

@mharnold
Copy link
Owner Author

CASE 2 & 3 may be hard to fix, since the underlying topology in RLIS (the jurisdictional data) is different than in OSM. In both cases two OSM intersections are represented as a single intersection in RLIS.

CASE 1 - Looks fixable. It may be that the distance between the intersection locations (coordinates) in the OSM vs RLIS exceeds the threshold at which spiderOSM will match them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mharnold