-
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 to geocoder and data-prep for new ITN local/express ferry classes #26
Comments
Support was already added for FERRY_PASSENGER. |
At MOTI's request, BC Ferries is going to create new ferry classes this fiscal to distinguish local from express so that routers won't jump from one the other at common docks. |
Why would we not change ferries at a dock? What does "support" mean in terms of the geocoder? Just add them to the accepted road classes? Ferries segments don't have addressing anyway, I think we just need to ignore them at some level. |
I might not have the new typology right but from what I recall, OnRoute was having trouble routing with the current ferry classes and we would too if BC Ferries didn't add new ferry classes |
Issue moved to bcgov/ols-router bcgov/api-specs#21 via ZenHub |
Doesn't this belong in ols-router, if anywhere? I don't think that ITN added these yet. |
You're right. BC Ferries promised to restructure the ferry routes so its a future thing which is why I took it out of this year's work. I thought it would apply to both Geocodable BC Maker and Routable BC Maker. |
Closing for now. |
BC Ferries promised to refine their ferry classes. When these new classes make their way into ITN, geocoder prep will need to made aware of them.
The text was updated successfully, but these errors were encountered: