-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add support for hwy and freeway exits as intersections #6
Comments
I think a slight clarification is required, for (1) the street alias is not |
For now we will only add the exit <#> alias to the exit segment. We will not worry about the -bound or "to wherever" part of this problem at this time. |
So assuming hwy 1 has an exit 305, please confirm after this enhancement, the geocoder will be able to match the following intersection:
It should actually return more than one match since there are eastbound and westbound exit 305s. |
While there is no exit 305 in BC, for exit 366 in Kamloops at Copperhead Dr, yes there should be two Hwy 1 and Exit 366 intersection points generated with this enhancement. Quality of data will be based on what is in ITN. There will likely be a few segments that need updating to add or remove exit attribution in order to fix issues. |
Verified in v4.1 gold in Test using Hwy 1 and Exit 366. |
Highway and freeway exits should be recognized as a type of intersection by the geocoder and route planner since they are part of the road network.
BC Wildfire Service Fire Reporting Centre needs to be able to find a location by hwy exit number.
There are a couple of ways to do this:
Option 1 seems simpler at this point.
In ITN data prep, create street aliases for off-ramps in the following form:
Here's an example:
This form doesn't distinguish between the two directions of travel (e.g., NorthBound/ SouthBound) This would require an addition as in:
and here's another example:
With this intersection format you can enter:
and the geocoder in autocompletion mode should return:
The text was updated successfully, but these errors were encountered: