Omim: [Routeing] Add the option to avoid toll roads and unpaved roads

Created on 11 Feb 2016  ·  30Comments  ·  Source: mapsme/omim

It would be useful to have the option to avoid toll and unpaved (dirt) roads.

Most helpful comment

Improving/fixing turns generation - done for 8.2 (future major release)
Memory issues investigation - done for 8.2/8.3
Car position extrapolation - done for 8.3
Unpaved roads get an additional fine during route calculation - done for 8.3
Unpaved and paid roads selection (mostly UI issue) - in progress, plan to finish it this year (8.5/8.6)

Also, as we finally hire a full routing team:

City roads get an additional fine during out-city routes calculation - done for 8.4
Speed cam notifications - in progress for 8.5
Much better work with speed limits from OSM - in progress for 8.5
Time estimation tuning - in progress for 8.6

All 30 comments

It's in our plans, the task is not easy: current routing algorithm does not support it at all.

On 11.2.2016, at 05.51, ignaciolep [email protected] wrote:

It would be useful to have the option to avoid toll and unpaved (dirt) roads.


Reply to this email directly or view it on GitHub.

I see. It's an OSRM limitation. Perhaps it's time to evaluate another open source routing engine that supports avoiding tolls like valhalla's toll_booth_penalty.

OSRM doesn't seem to be well-suited to mobile platforms anyway. The thing is, I don't know of any open source router that simply works (just like what commercial navigations have achieved like 10 years ago on hardware that was significantly less powerful).

CC @gardster @bykoianko

Any news about this issue ? Is it still in your plans ?

Hi!

Any news about this issue ? Is it still in your plans ?

As far as I’m aware, yes it is still in our plans. There’s a limitation of contraction hierarchy (osrm). So implementing it is not easy.

Vladimir

28 июля 2016 г., в 21:08, Adrien Pavie [email protected] написал(а):

Any news about this issue ? Is it still in your plans ?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/mapsme/omim/issues/1888#issuecomment-235977335, or mute the thread https://github.com/notifications/unsubscribe-auth/ABr6sjFu5e5l5Gflo_43Akxh6D36eszIks5qaPANgaJpZM4HX3Wk.

I don't see clearly the limitations you are talking about, OSRM seems to handle several routing profiles, are there any issues to create a copy of car profile and restrict using roads with toll=yes tag ?

Current algorithm supports only one possible path for one profile. It means that to have "toll-free" routes, we need to build all routing data files separately and duplicate them (~ +30% to mwm file sizes).

https://github.com/pgRouting/pgrouting but all engine need to be changed... Didn't check every capabilities

Or graphhopper

@homersimpsons do you have the postgresql instance on your phone to use pgrouting? Graphhopper uses same technics with the OSRM and has same limitations.

No, in fact I don't get postgre and porting it doesn't look easy/possible. But maybe you can try to adapt the code for SQLite ?
In fact, graph hopper also use CH, but others algorithms are implemented, like A* or Dijkstra, then maybe, for 'non CH' search, just display a reminder to prevent that it could be long.

I think you should check out Thor and help them port it to mobile.

Any news on this?

We are changing algorithm right now, so you can expect your feature to be
implemented in the first half of 2017.
Sorry it is taking so long.

On 6 December 2016 at 17:56, vvug notifications@github.com wrote:

Any news on this?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mapsme/omim/issues/1888#issuecomment-265170215, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACGjAfOL_mCZqBi9PiKsAPn78vCBRbPQks5rFXeBgaJpZM4HX3Wk
.

Great news, thank you!
Will it also solve #4394?

Thanks for letting us know, @burivuh.
Is the new algorithm just a new version of OSRM, or something completely different?
In the latter case, which algorithm will maps.me use?

Any news regarding implementation of this?

Bump… it’s 2018 now, any word? It’s a much needed feature IMO.

Hi!
Bad news: we had to change our plan in 2017.
Good news: we have a green light for a car navigation development. At least for now.
Plan for the near future:
Improving/fixing turns generation - done for 8.2 (future major release)
Memory issues investigation - in the process
Car position extrapolation
Unpaved roads get an additional fine during route calculation
Unpaved and paid roads selection (mostly UI issue)

Cool, thanks for the update, keep up the great work!

When routing between two points, the result still include unpaved ways.
This is unnaceptable when exist better alternatives to take, and users are obfuscated with the route propossed.
Please include a filter to exclude non paved ways from route.
Thank you.

Another feature request, similar to avoid unpaved and paid roads: avoid highways. It makes for a much more enjoyable drive.

I'd be willing to have a stab at making this if I were pointed in the right direction. Presumably it would be an option in the navigation settings, which would then add a huge fine for those types of roads during route calculation.

I too would appreciate an "avoid highways" route. It would also be useful to say use only minor roads.

Hi @burivuh,
It would be great if you could update us with the actual plan status.
Thanks!

Hi!
Bad news: we had to change our plan in 2017.
Good news: we have a green light for a car navigation development. At least for now.
Plan for the near future:
Improving/fixing turns generation - done for 8.2 (future major release)
Memory issues investigation - in the process
Car position extrapolation
Unpaved roads get an additional fine during route calculation
Unpaved and paid roads selection (mostly UI issue)

Improving/fixing turns generation - done for 8.2 (future major release)
Memory issues investigation - done for 8.2/8.3
Car position extrapolation - done for 8.3
Unpaved roads get an additional fine during route calculation - done for 8.3
Unpaved and paid roads selection (mostly UI issue) - in progress, plan to finish it this year (8.5/8.6)

Also, as we finally hire a full routing team:

City roads get an additional fine during out-city routes calculation - done for 8.4
Speed cam notifications - in progress for 8.5
Much better work with speed limits from OSM - in progress for 8.5
Time estimation tuning - in progress for 8.6

Excellent. Thank you!!

Hi @burivuh ,
As the latest version in production is 8.6.3, Could you update us the tasks status? (Specially the "Unpaved and paid roads selection")
Thanks!

It's seems that finally version 9.1.5 can avoid toll roads and unpaved roads! But it doesn't always work as expected.
Can anyone from staff explain how does it work the new router?
What are the exact conditions to avoid a toll road?
@burivuh @biodranik

Hi!

If you select a setting to avoid some type of the road, router will not use that type for the route.

Have you found any bug or inconsistent behaviour? Please, send it to the [email protected] so that we can properly track the issue.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

nh2 picture nh2  ·  6Comments

sangeetaggomes picture sangeetaggomes  ·  7Comments

berolinux picture berolinux  ·  7Comments

Tobey16 picture Tobey16  ·  5Comments

sils picture sils  ·  6Comments