Closed EWCLighting closed 1 year ago
The path is not tagged as cycleway nor is it designated. The tagging highway=path
leads to a big penalty (priority is 0.9, speed 4km/h) which is only lifted due to bicycle=yes (priority is 1.2, speed is 10km/h) minus a minor penalty due to foot=yes (priority is then 1.1). Whereas highway=tertiary has the same priority of 1.1 but a faster speed (18km/h). In my opinion this sounds reasonable. Could this be improved via tagging like bicycle=designated?
(note that I moved your issue from the frontend repository to here)
The combination of highway=path
+bicycle=yes
+foot=yes
+segregated=no
would be a strong indicator that a lower speed is justified here.
I should have specified that it is for golf carts if that helps.
The problem is that this way is potentially shared with pedestrians which limits the expected speed.
Closing here for now as this is kind of expected behaviour. If you want to change the behaviour for you personally you can tweak the routing using the custom model (gear button in the top left corner).
Hi Peter, I don’t know how to do this. It just seems crazy that it is taking the golf carts off the multi-model path when that is what it was built for. Now our users are asking us to fix it. Regards, Eddie
On Mar 29, 2023, at 4:15 AM, Peter @.***> wrote:
Closing here for now as this is kind of expected behaviour. If you want to change the behaviour for you personally you can tweak the routing using the custom model (gear button in the top left corner).
— Reply to this email directly, view it on GitHub https://github.com/graphhopper/graphhopper/issues/2779#issuecomment-1488138593, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6ZIPJYCIL6I6J7RIH3AGADW6PVRFANCNFSM6AAAAAAWKCSD4Q. You are receiving this because you authored the thread.
Based on the markings, the route should be tagged with segregated=yes
I’m not sure how to do that… We are talking about the bicycle routes right? You can see the golf carts in that image. Regards, Eddie
On Mar 29, 2023, at 8:01 AM, otbutz @.***> wrote:
@.***,-82.0152727,3a,30y,203.61h,80.69t/data=!3m7!1e1!3m5!1sTDOBCLtpEkik7k1V6j_zHA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DTDOBCLtpEkik7k1V6j_zHA%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D203.62561%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192
Based on the markings, the route should be tagged with segregated=yes
— Reply to this email directly, view it on GitHub https://github.com/graphhopper/graphhopper/issues/2779#issuecomment-1488471015, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6ZIPJ7KPX4LGUTNF5X7RE3W6QQATANCNFSM6AAAAAAWKCSD4Q. You are receiving this because you authored the thread.
This route is taking me the wrong way. It should stay on the multi-model path instead of taking me back on residential roads. From: 28.9703, -82.0154 To: 28.9621, -82.0036
https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=28.9703%2C-82.0154%3B28.9621%2C-82.0036
Can this be fixed? Best Regards