Building a config.yml that takes various driving sides and mi/km into account

Open Source Routing Engine
1

I am building a routing server that processes the planet osm file. This has been successful but I have some testers reporting that things need to be optimized such as:

  • Taking left side and right right driving into account (is this done automatically)
  • Not allowing u-turns at emergency vehicle crossings
  • What is the road priority? Will it always choose highways first?

Thank you!

1 Like
2

Taking left side and right right driving into account

For which feature do you need this? Currently there is no difference.

Not allowing u-turns at emergency vehicle crossings

What do you mean here? Do you have an example?

What is the road priority? Will it always choose highways first?

You can read more about it here: graphhopper/docs/core/custom-models.md at master · graphhopper/graphhopper · GitHub

3

I am using navigation directions (e.g. navigate/directions/v5/gh) and I had a user reporting that the roundabout was showing an incorrect icon and he is in the UK. He thought it had to do with the driving side.

Yes, graphhopper provided a u-turn here: Way: 973352843 | OpenStreetMap I would like to prevent this from happening. I assume the access=no needs to be somehow respected?

4

Ah, yes. Indeed this is something that we do not support yet.

Yes, graphhopper provided a u-turn here:

What exactly is your custom model? This is definitely not standard behaviour: OpenStreetMap

5

Looks like I previously did not use custom_model_files: [car.json]. After adding that and testing I get routing just like you provided in OpenStreetMap.

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.