Skip to content
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

Multiple routing profile in one data file #2791

Closed
homersimpsons opened this issue Aug 19, 2016 · 6 comments
Closed

Multiple routing profile in one data file #2791

homersimpsons opened this issue Aug 19, 2016 · 6 comments

Comments

@homersimpsons
Copy link

homersimpsons commented Aug 19, 2016

Hello,

There is a request mapsme/omim#1888 in maps.me to add an option to avoid toll. But as it's a smartphone software, they care about map size. Then they can't add this profile.

Is it possible to extend routing data configuration to support multiple routing. This is to avoid one routing data per profile.

I know that this is not the base idea (which was we 'basicaly' search for lowest penalty between two nodes to get the fastest route for this profile) maybe data file can describe more profile just by supporting boolean value (here is it for toll, but it could be heigh preference or to avoid trunk). The different profile should be penalty compatible but can get roads restrictions.

@danpat
Copy link
Member

danpat commented Aug 19, 2016

@homersimpsons Because of the Contraction Hierarchy graph structure that OSRM uses, it is non-trivial to support query-time options like "avoid tolls" or "avoid ferries".

For a more detailed discussion, see: #2377

@frodrigo
Copy link
Member

Also look at #10

@homersimpsons
Copy link
Author

First of all, in profile you need to include different condition to take care (boolean toll, float height, float weight etc.)
This condition can be evaluated and only return a boolean.

@homersimpsons
Copy link
Author

For toll road, we can consider that a road is paid or not, then maybe is it possible to consider paid road as a subgraph.
Then do two different Contraction for paid road and free ones

@daniel-j-h
Copy link
Member

Closing here as duplicate of the issues linked above. CH does not support dynamic query time flags e.g. for tolls, ferries and so on. What you can do is create multiple profiles run OSRM on each of them. This will create multiple .osrm. datasets. Feel free to zip them up and ship them.

@danpat
Copy link
Member

danpat commented Sep 2, 2016

@daniel-j-h In theory we could create a second overlay graph for different profiles, as much of the underlying data would be common. It would basically require an additional .hsgr file per profile, which is quite large, but #10 is the container ticket for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants