Organic maps gives a bit to much weight to cycleways #1772

Closed
opened 2022-01-03 07:06:04 +00:00 by vincentvd1 · 19 comments
vincentvd1 commented 2022-01-03 07:06:04 +00:00 (Migrated from github.com)

I have noticed that organic maps gives a bit to much weight to cycleways during navigation for bicycles. See the example below:
Organic maps navigation
Graphhopper naviation

Graphhopper location

The route by organic maps results in an additional 500m where logically, I would use the route by graphhopper this time. It is more direct where in my opinion the shorter route outweights the additional 500m that is over cycleways.

I have to note though that this preference for cycleways in general results in better routes then graphhopper. In the example below, organic maps routes me over cycleways near major routes where graphbopper gives me a route through the residential area. Using the cycleways gives a much nicer bicycle experience and almost no additional time.
correct route
Graphhopper route

I have noticed that organic maps gives a bit to much weight to cycleways during navigation for bicycles. See the example below: ![Organic maps navigation](https://i.imgur.com/d6Z9lHj.png) ![Graphhopper naviation](https://i.imgur.com/uqncjDs.png) [Graphhopper location](https://graphhopper.com/maps/?point=52.253405%2C6.182288&point=52.247599%2C6.197973&locale=nl-nl&elevation=true&profile=bike&use_miles=false&selected_detail=Elevation&layer=Omniscale) The route by organic maps results in an additional 500m where logically, I would use the route by graphhopper this time. It is more direct where in my opinion the shorter route outweights the additional 500m that is over cycleways. I have to note though that this preference for cycleways in general results in better routes then graphhopper. In the example below, organic maps routes me over cycleways near major routes where graphbopper gives me a route through the residential area. Using the cycleways gives a much nicer bicycle experience and almost no additional time. ![correct route](https://i.imgur.com/RTDPNbo.png) ![Graphhopper route](https://i.imgur.com/HQzsaAy.png)
biodranik commented 2022-01-03 07:21:57 +00:00 (Migrated from github.com)

Do you think that providing alternative routes will solve this issue? Or simply slightly reducing the weight should be enough?

Do you think that providing alternative routes will solve this issue? Or simply slightly reducing the weight should be enough?
biodranik commented 2022-01-03 07:22:08 +00:00 (Migrated from github.com)

assigned to @vng

assigned to `@vng`
vincentvd1 commented 2022-01-03 12:08:29 +00:00 (Migrated from github.com)

@biodranik With alternative routes, do you mean like Google maps showing multiple routes where you can select the one you like? I peronally don't like that. It clutters the navigation. I would like to trust on the navigation that it gives me the most optimal route. Otherwise you would have to assess the alternatives during or prior to navigation.

Reducing the weight might be an option that can be looked at. If it is possible to reduce the weight while still providing the same routes in other cases (like the second example), that would be fine to me. But that is something that needs to be tested.

`@biodranik` With alternative routes, do you mean like Google maps showing multiple routes where you can select the one you like? I peronally don't like that. It clutters the navigation. I would like to trust on the navigation that it gives me the most optimal route. Otherwise you would have to assess the alternatives during or prior to navigation. Reducing the weight might be an option that can be looked at. If it is possible to reduce the weight while still providing the same routes in other cases (like the second example), that would be fine to me. But that is something that needs to be tested.
biodranik commented 2022-01-03 12:18:29 +00:00 (Migrated from github.com)

When the app shows you only one route, it's hard to decide how good is it. If it shows "the shortest", "the fastest", and "by cycleway", then at least you can choose the best one for you.

When the app shows you only one route, it's hard to decide how good is it. If it shows "the shortest", "the fastest", and "by cycleway", then at least you can choose the best one for you.
vincentvd1 commented 2022-01-03 12:27:19 +00:00 (Migrated from github.com)

I don't agree entirely. When I enter a destination in our car navigation, it gives 1 route. Imagine if you would first have to look at each route which you like the most. For shorter routes this is doable but for longer routes not. The most optimal route should be a balanced one. By reports like this one, you can fine tune the algorithm.

It is also possible to make a setting whether you want to see alternative routes.

I don't agree entirely. When I enter a destination in our car navigation, it gives 1 route. Imagine if you would first have to look at each route which you like the most. For shorter routes this is doable but for longer routes not. The most optimal route should be a balanced one. By reports like this one, you can fine tune the algorithm. It is also possible to make a setting whether you want to see alternative routes.
biodranik commented 2022-01-03 14:14:30 +00:00 (Migrated from github.com)

The problem roots are in the imperfect OSM data. Fine-tuning the algorithm won't help with it. From the user perspective, there is no overhead: you still have some ("the best") route selected by default, while seeing several alternate ones with an option to touch and activate them (or ignore and just press "GO!").

The problem roots are in the imperfect OSM data. Fine-tuning the algorithm won't help with it. From the user perspective, there is no overhead: you still have some ("the best") route selected by default, while seeing several alternate ones with an option to touch and activate them (or ignore and just press "GO!").
vincentvd1 commented 2022-01-03 14:52:58 +00:00 (Migrated from github.com)

Thanks for the clearification. About fine tuning, you as developer know the algorithm the best so if fine tuning (lowering the weight) does not help in your opinion, okay. Then the best alternative is indeed showing multiple routes which you can select (and a balanced route selected as default).

Thanks for the clearification. About fine tuning, you as developer know the algorithm the best so if fine tuning (lowering the weight) does not help in your opinion, okay. Then the best alternative is indeed showing multiple routes which you can select (and a balanced route selected as default).
chereskata commented 2022-10-23 17:54:41 +00:00 (Migrated from github.com)

The problem roots are in the imperfect OSM data. Fine-tuning the algorithm won't help with it. From the user perspective, there is no overhead: you still have some ("the best") route selected by default, while seeing several alternate ones with an option to touch and activate them (or ignore and just press "GO!").

This is THE feature i am missing atm :)

> The problem roots are in the imperfect OSM data. Fine-tuning the algorithm won't help with it. From the user perspective, there is no overhead: you still have some ("the best") route selected by default, while seeing several alternate ones with an option to touch and activate them (or ignore and just press "GO!"). This is THE feature i am missing atm :)
Member

mentioned in issue #7954

mentioned in issue #7954
matkoniecz commented 2024-10-30 16:09:03 +00:00 (Migrated from github.com)
> The problem roots are in the imperfect OSM data. what about https://private-user-images.githubusercontent.com/899988/323778942-fae51b62-afcb-41ae-9d58-e1b5384bd83a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzAzMDQ3NjAsIm5iZiI6MTczMDMwNDQ2MCwicGF0aCI6Ii84OTk5ODgvMzIzNzc4OTQyLWZhZTUxYjYyLWFmY2ItNDFhZS05ZDU4LWUxYjUzODRiZDgzYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMDMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTAzMFQxNjA3NDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01NjI2YzY0MGQ4MTQ5ZTAyZWIzMjY4ZjVjMTU3OWI3NzFlYTkwMmZiZWJlMjk3MTU1NmYwZDg3MzY2ZTQ0Mjg2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.gxGaukAvLtbz3bgpZkzU9Nnrn8TdIA4sQPvk57nbyyA case? here https://git.omaps.dev/organicmaps/organicmaps/issues/1772 is part of the problem, but even without crossing this route would be still silly, cycleways seem clearly overprefered. In general I seen OM choosing quite suboptimal routes just because it had more cycleway there.
matkoniecz commented 2024-10-30 16:11:30 +00:00 (Migrated from github.com)

When the app shows you only one route, it's hard to decide how good is it. If it shows "the shortest", "the fastest", and "by cycleway", then at least you can choose the best one for you.

Though maybe having separate "fast bicycle" and "safe bicycle" would make sense. (bicycle with shield for icon? child bicycle? Bicycle with speed/wind dashes behind it for fast one?)

> When the app shows you only one route, it's hard to decide how good is it. If it shows "the shortest", "the fastest", and "by cycleway", then at least you can choose the best one for you. Though maybe having separate "fast bicycle" and "safe bicycle" would make sense. (bicycle with shield for icon? child bicycle? Bicycle with speed/wind dashes behind it for fast one?)
Member

what about

could you please re-upload the pic (it doesn't work for me) and/or provide coords?

> what about could you please re-upload the pic (it doesn't work for me) and/or provide coords?
matkoniecz commented 2024-10-30 16:44:33 +00:00 (Migrated from github.com)
https://git.omaps.dev/organicmaps/organicmaps/issues/7954#issue-2251708146
Member

I have to note though that this preference for cycleways in general results in better routes then graphhopper. In the example below, organic maps routes me over cycleways near major routes where graphbopper gives me a route through the residential area. Using the cycleways gives a much nicer bicycle experience and almost no additional time.

These two routes differ by ~50m only (check GraphHopper vs Valhalla https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=51.18346%2C6.00122%3B51.19257%2C5.99385#map=16/51.18800/5.99714), so its very safe OM would still prefer cycleways even if the preference for them would be reduced significantly.

Do you perhaps have some other sample cases where there is a bigger difference between a preferred cycleways route vs a noticeably shorter but less pleasant road route?

> I have to note though that this preference for cycleways in general results in better routes then graphhopper. In the example below, organic maps routes me over cycleways near major routes where graphbopper gives me a route through the residential area. Using the cycleways gives a much nicer bicycle experience and almost no additional time. These two routes differ by ~50m only (check GraphHopper vs Valhalla https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=51.18346%2C6.00122%3B51.19257%2C5.99385#map=16/51.18800/5.99714), so its very safe OM would still prefer cycleways even if the preference for them would be reduced significantly. Do you perhaps have some other sample cases where there is a bigger difference between a preferred cycleways route vs a noticeably shorter but less pleasant road route?
Member

mentioned in issue #4059

mentioned in issue #4059
Member

mentioned in merge request !9692

mentioned in merge request !9692
matkoniecz commented 2024-11-20 07:10:46 +00:00 (Migrated from github.com)

Do you perhaps have some other sample cases where there is a bigger difference between a preferred cycleways route vs a noticeably shorter but less pleasant road route?

should I try find now before #9692 is merged or would it be more useful to wait for it to become available for me and then report some silly routes?

> Do you perhaps have some other sample cases where there is a bigger difference between a preferred cycleways route vs a noticeably shorter but less pleasant road route? should I try find now before https://git.omaps.dev/organicmaps/organicmaps/pulls/9692 is merged or would it be more useful to wait for it to become available for me and then report some silly routes?
Member

@matkoniecz yeap it'd be good to have a robust "cycleway detour is preferred" case
(to replace the RussiaMoscowSevTushinoParkPreferingBicycleWay case)

`@matkoniecz` yeap it'd be good to have a robust "cycleway detour is preferred" case (to replace the RussiaMoscowSevTushinoParkPreferingBicycleWay case)
matkoniecz commented 2024-11-21 14:11:31 +00:00 (Migrated from github.com)
https://git.omaps.dev/organicmaps/organicmaps/pulls/9692#discussion_r1851579177 <details> <summary>Click to expand - copied examples</summary> https://www.openstreetmap.org/directions?engine=fossgis_valhalla_bicycle&route=50.076924%2C19.917848%3B50.074458%2C19.910502#map=17/50.075451/19.914844&layers=N (this one misses even North-South shared sidewalk!) ![screen06](https://github.com/user-attachments/assets/c39e14ea-b4e6-4dfc-979d-bd883d144cef) https://www.openstreetmap.org/directions?engine=fossgis_osrm_bike&route=50.076924%2C19.917848%3B50.074480%2C19.910488#map=18/50.075936/19.914098&layers=N ![screen07](https://github.com/user-attachments/assets/ef7f3999-b43b-4b1f-8698-b7ab1d639eb5) more bordeline https://www.openstreetmap.org/directions?engine=fossgis_valhalla_bicycle&route=50.043813%2C20.016456%3B50.047522%2C20.029986 ![screen08](https://github.com/user-attachments/assets/8d1bd8bc-0164-406d-8490-32e88f1993c5) https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=50.043813%2C20.016456%3B50.047522%2C20.029986#map=17/50.046302/20.023109&layers=N ![screen09](https://github.com/user-attachments/assets/4ac85516-e608-43ac-8941-731702609f6b) this one has contraflow on service road as cycleway substitute https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=50.036180%2C19.982480%3B50.040088%2C19.983348#map=17/50.038544/19.985375&layers=N ![screen10](https://github.com/user-attachments/assets/efefe4b3-cf0b-4302-90e6-04df2ebe1269) https://www.openstreetmap.org/directions?engine=fossgis_osrm_bike&route=50.036180%2C19.982480%3B50.040088%2C19.983348#map=17/50.038172/19.982790&layers=N ![screen11](https://github.com/user-attachments/assets/31a6e9e9-09ec-4507-b914-82a8f9e54ef4) https://www.openstreetmap.org/directions?engine=fossgis_valhalla_bicycle&route=50.031478%2C19.948912%3B50.036289%2C19.941198#map=17/50.033927/19.945056&layers=N ![screen14](https://github.com/user-attachments/assets/4093d659-722a-45d4-a0f0-eb480a71b905) https://www.openstreetmap.org/directions?engine=fossgis_osrm_bike&route=50.031478%2C19.948912%3B50.036289%2C19.941198#map=17/50.033927/19.945164&layers=N ![screen15](https://github.com/user-attachments/assets/8a8d5561-b74f-4a7c-9f23-cf880fadd146) </details>
pastk closed this issue 2025-02-07 14:14:15 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: organicmaps/organicmaps#1772
No description provided.