-
Notifications
You must be signed in to change notification settings - Fork 411
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
driving-hgv routing over way with hgv=no #816
Comments
Thanks for reporting this! I can confirm the problem and I will look into it. |
Access restrictions for hgv driving profiles are currently not resolved on ORS maps because of a missing I couldn't find any recent changes in handling of |
No recent. See GIScience/openrouteservice-app@8c54a64 I've changed it back then to only add the The documentation is kind of ambigous for this, as it says the default value for @aoles do you think it's feasible to have |
We certainly could introduce a default value for |
#1054 fixes the problem that setting both |
It seems a bit unintuitive that IMO, when using the |
Thanks, these are all fair points!
While hgv-specific access restrictions are certainly important, there is still a number of other differences between these two profiles. Apart from a distinct set of default road speeds, the main difference between
I couldn't agree more on this. In particular, I'm not sure where the statement in the API docs about the default The main challenge here is to take these default hgv restrictions into account when performing routing with CH which is the default algorithm when no additional parameters are set. This is not entirely easily to implement because CH does not allow for setting any additional edge filters, both during contraction and routing. I've solved this by introducing an additional |
…hgv' when profile is 'driving-hgv' and no vehicle type is given, the API will default to hgv itself therefore it is unnecessary to set it as a default parameter in the request see also GIScience/openrouteservice#816
…hgv' when profile is 'driving-hgv' and no vehicle type is given, the API will default to hgv itself therefore it is unnecessary to set it as a default parameter in the request see also GIScience/openrouteservice#816
…hgv' when profile is 'driving-hgv' and no vehicle type is given, the API will default to hgv itself therefore it is unnecessary to set it as a default parameter in the request see also GIScience/openrouteservice#816
…hgv' when profile is 'driving-hgv' and no vehicle type is given, the API will default to hgv itself therefore it is unnecessary to set it as a default parameter in the request see also GIScience/openrouteservice#816
…hgv' when profile is 'driving-hgv' and no vehicle type is given, the API will default to hgv itself therefore it is unnecessary to set it as a default parameter in the request see also GIScience/openrouteservice#816
Here's what I did
Here's what I got
Here's what I was expecting
The route avoiding a way with tag
hgv=no
See also
https://maps.openrouteservice.org/directions?n1=40.746702&n2=-73.912582&n3=10&a=40.878103,-73.916973,40.794616,-73.971437&b=4a&c=0&k1=en-US&k2=km
https://www.openstreetmap.org/way/8608691#map=16/40.8135/-73.9649
The text was updated successfully, but these errors were encountered: