I'm running a self-hosted OpenRouteService v8.2.0 instance with Docker, but my custom service limits (specifically maximum_distance: 8000000) are not being applied. The status endpoint continues to show the default limit of 100000 instead of my configured

openrouteservice
1

My Use Case

  • Objective: Regional car routing service for South America using matrix API
  • Required Output: Only distance and duration values (no geometry/instructions)
  • Need: Increase maximum distance limit from default 100km

Current Configuration

Docker Compose:
ors-south-america:
container_name: ors-south-america
image: openrouteservice/openrouteservice:v8.2.0
ports:
- “8083:8082”
volumes:
- ./files:/home/ors/files:ro
- ./graphs-south-america:/home/ors/graphs
- ./logs-south-america:/home/ors/logs
- ./config:/home/ors/config
environment:
REBUILD_GRAPHS: “true”
CONTAINER_LOG_LEVEL: INFO
ADDITIONAL_JAVA_OPTS: “-Xms4g -Xmx16g”
ORS_CONFIG_LOCATION: /home/ors/config/ors-config-south-america.yml
restart: unless-stopped
networks: [ors-network]
profiles: [south-america]

networks:
ors-network:
driver: bridge

ors-config-south-america.yml
ors:
engine:
source_file: /home/ors/files/south-america-latest.osm.pbf
graphs_root_path: /home/ors/graphs
graphs_data_access: MMAP
elevation:
cache_path: /home/ors/elevation_cache

profiles:
  car:
    enabled: true
    encoder_options:
      turn_costs: true
      block_fords: false
    preparation:
      min_network_size: 200
      min_one_way_network_size: 200
    service:
      maximum_distance: 8000000                      
      maximum_distance_dynamic_weights: 8000000     
      maximum_distance_avoid_areas: 8000000          
      maximum_distance_alternative_routes: 8000000  
      maximum_distance_round_trip_routes: 8000000   
     
      maximum_way_points: 50                         
      maximum_snapping_radius: 5000                 
      maximum_alternative_routes: 3                  
      
      
      force_turn_costs: true                         
      
     
      execution:
        methods:
          lm:
            active_landmarks: 16                     
          astar:
            approximation: BeelineAccurate           
            epsilon: 1.2

server:
port: 8082
servlet:
context-path: /ors

logging:
level:
org.heigit.ors: INFO
root: INFO
org.heigit.ors.routing.RoutingProfile: DEBUG

Current Behavior

When I check the status endpoint:
curl -s “http://localhost:8083/ors/v2/status” | grep maximum_distance
“limits”:{“maximum_distance”:100000,“maximum_waypoints”:50}

  1. Is there a specific configuration hierarchy that overrides service limits?
  2. Are there any environment variables that might be overriding my YAML config
    Any guidance would be greatly appreciated!
2

Hey,

is there a reason you are using 8.2.0?
We can unfortunately not support old openrouteservice versions - would you mind upgrading to 9.3.1 and checking whether that improves things?

Best regards

1 Like
3

Thank you for the quick response ,
I will upgrade to OpenRouteService v9.3.1 and test the maximum distance configuration with the newer version.
I will update this thread with my results after testing v9.3.1, and let you know if the issue persists or if any new challenges arise during the upgrade.
Thank you again for your assistance

1 Like