Not routing the right segment

Developers
1

Hello guys,

I’m running a GH instance in my own k8s infra, and I received a request where a certain routing, is taking an exit, when It shoudn’t.

image
image917×689 65.1 KB

The route should follow for the redline, instead of the blue line.

Analising the routing graph I could realize that 3 different segments makes this little network.

image
image947×677 86.9 KB

And this segments have a weird subnetwork flag:

image
image978×846 116 KB

image
image1008×737 104 KB

image
image900×808 96.8 KB

The segment where the route should follow have truck_subnetwork and big_truck_subnetwork with true, and I only could route through it with car profile. I believe is not just a coincidence.

I’m running a planet-260629 pbf, and this is my config.yml

    graphhopper:
      datareader.file: ""
      datareader.worker_threads: 16
      custom_models.directory: /data/config/profiles
      profiles:
        - name: car
          custom_model_files: [ car.json ]
        - name: truck
          custom_model_files: [ truck.json ]
        - name: big_truck
          weighting: custom
          custom_model_files: [ big_truck.json ]
      profiles_ch:
        - profile: car
        - profile: truck
      profiles_lm:
        - profile: car
        - profile: truck
        - profile: big_truck
      prepare.min_network_size: 1000
      prepare.subnetworks.threads: 50
      prepare.ch.threads: 2
      prepare.lm.threads: 3
      routing.non_ch.max_waypoint_distance: 100_000_000 #100.000.000
      routing.max_visited_nodes: 15_000_000 #15.000.000
      import.osm.ignored_highways: footway,cycleway,path,pedestrian,steps # typically useful for motorized-only routing
      index.max_region_search: 30
      graph.location: graph-cache
      graph.dataaccess.default_type: RAM_STORE
      graph.encoded_values: country,hgv,max_weight,max_height,max_width,toll,car_access,car_average_speed,road_access,road_class
    server:
      application_connectors:
        - type: http
          port: 8989
          bind_host: localhost
          max_request_header_size: 50k
      request_log:
        appenders: []
      admin_connectors:
        - type: http
          port: 8990
          bind_host: localhost
    logging:
      appenders:
        - type: file
          time_zone: UTC
          current_log_filename: logs/graphhopper.log
          log_format: "%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n"
          archive: true
          archived_log_filename_pattern: ./logs/graphhopper-%d.log.gz
          archived_file_count: 30
          never_block: true
        - type: console
          time_zone: UTC
          log_format: "%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n"
      loggers:
        "com.graphhopper.osm_warnings":
          level: DEBUG
          additive: false
          appenders:
            - type: file
              currentLogFilename: logs/osm_warnings.log
              archive: false
              logFormat: '[%level] %msg%n'

In the Graphhopper web, the same problem doesn’t happen.

Here’s the coordinates to reproduce the error:
Start: -24.27515,-47.412064
End: -24.273523,-47.408053

2

I can only guess, here, but I would guess it is somehow related to specifics of your truck profiles? Does the highway edge have any unusual tags?

3

Hey @easbar !

I don’t know about the highway tags. And yes, it’s seems related to my truck and big_truck profile. With car, this problem doesn’t happen, and in GH Web the same problem also doesn’t happen even with the truck profile.

4

I think because of this way: https://www.openstreetmap.org/way/1494460136, which is tagged hgv=no, your highway is disconnected from the road network (truck_subnetwork=true)

5

Can you try changing

"if": "!car_access && road_access != PRIVATE && hgv != DELIVERY && hgv != DESTINATION"

to "if": "!car_access && road_access != PRIVATE && hgv != DELIVERY && hgv != DESTINATION && hgv != YES"

in truck.json? This should allow the alternative driveway to the closed section.

But be careful, because allowing car_access=false+hgv=yes would open any kind of one-way road (including roads with separated lanes!) tagged as hgv=yes in both directions.

6

The truck.json is in its current form not production ready, but it would be nice to get some feedback and improve it.

Can you have a look into this branch, which uses the ModeAccessParser and should now handle many real world scenarios. Basically you just have

{ "if": "!hgv_access",  "multiply_by": "0" }

instead of the hgv exception for the car_access, which does not work properly in several edge cases.

If you still find a problem you can now just let us know the tags where it fails and add it as a unit test to avoid that it fails in the future.

1 Like