Different routing results between foot and pt

Open Source Routing Engine
1

I’ve been testing foot and pt routing in an area with separate sidewalks that I added to my local OSM server, and the results aren’t consistent. For only walking routes, foot and pt profiles have different results.

In the foot profile, it takes only the sidewalks and crossings as its supposed to.
image

In the pt profile, it goes into the roundabout, for some reason. I don’t believe it should, as the secondary highway are supposed to be avoided, according to FootFlagEncoder, and there are other possible ways, as proven by the previous screenshot.
image

What is the cause of this? Shouldn’t both cases use the same FlagEncoder?

2

Are you really using the same coordinates? This looks like there is a tunnel and a different destination forces the route into it.

3

Here it is with the exact same coordinates for start and end points.

image
image916×292 98.3 KB

image
image858×351 111 KB

4

Not sure what exactly happens but both paths are valid paths and the 2nd example goes through the tunnel a bit longer: see this and this. So it might be that both weights are nearly equal and some rounding issues happen.

Can you show the weight, the distance and the time of both paths from the JSON response?

5

1st example

...
"paths": [
    {
      "distance": 237.783,
      "weight": 148.368477,
      "time": 177143,
...

2nd example

...
"paths": [
    {
      "distance": 237.113,
      "weight": 0.0,
      "time": 170715,
...

I’m afraid the pt route JSON response doesn’t contain the weight value. It does show however that the path is shorter for the 2nd example. Does foot in pt routing give less weight to the avoid tags?

6

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