Street routing from one to many places or many to one. The order in the response array corresponds to the order of coordinates of the \`many\` parameter in the query.
Query parameters
geo location as latitude;longitude
geo locations as latitude;longitude,latitude;longitude,...
The number of accepted locations is limited by server config variable onetomany_max_many.
Street modes
- WALK
- BIKE
- RENTAL Experimental. Expect unannounced breaking changes (without version bumps) for all parameters and returned structs.
- CAR
- HGV Heavy goods vehicles (only supported for direct connections)
- CAR_PARKING Experimental. Expect unannounced breaking changes (without version bumps) for all parameters and returned structs.
- CAR_DROPOFF Experimental. Expect unannounced breaking changes (without version bumps) for all perameters and returned structs.
- ODM on-demand taxis from the Prima+ÖV Project
- RIDE_SHARING ride sharing from the Prima+ÖV Project
- FLEX flexible transports
Transit modes
- TRANSIT: translates to TRAM,FERRY,AIRPLANE,BUS,COACH,RAIL,ODM,RIDE_SHARING,FUNICULAR,AERIAL_LIFT,OTHER
- TRAM: trams
- SUBWAY: subway trains (Paris Metro, London Underground, but also NYC Subway, Hamburger Hochbahn, and other non-underground services)
- FERRY: ferries
- AIRPLANE: airline flights
- BUS: short distance buses (does not include COACH)
- COACH: long distance buses (does not include BUS)
- RAIL: translates to HIGHSPEED_RAIL,LONG_DISTANCE,NIGHT_RAIL,REGIONAL_RAIL,SUBURBAN,SUBWAY
- HIGHSPEED_RAIL: long distance high speed trains (e.g. TGV)
- LONG_DISTANCE: long distance inter city trains
- NIGHT_RAIL: long distance night trains
- REGIONAL_FAST_RAIL: deprecated, REGIONAL_RAIL will be used
- REGIONAL_RAIL: regional train
- SUBURBAN: suburban trains (e.g. S-Bahn, RER, Elizabeth Line, ...)
- ODM: demand responsive transport
- RIDE_SHARING: ride sharing
- FUNICULAR: Funicular. Any rail system designed for steep inclines.
- AERIAL_LIFT: Aerial lift, suspended cable car (e.g., gondola lift, aerial tramway). Cable transport where cabins, cars, gondolas or open chairs are suspended by means of one or more cables.
- AREAL_LIFT: deprecated
- METRO: deprecated
- CABLE_CAR: deprecated
routing profile to use (currently supported: `WALK`, `BIKE`, `CAR`)
maximum travel time in seconds. Is limited by server config variable street_routing_max_direct_seconds.
maximum matching distance in meters to match geo coordinates to the street network
Is limited by server config variable max_max_matching_distance, larger values are capped to this limit.
Vehicle height for HGV routing in meters
Vehicle width for HGV routing in meters
Vehicle length for HGV routing in meters
Vehicle gross weight for HGV routing in tons
Whether the vehicle carries hazardous materials for HGV routing
Whether the vehicle carries hazardous materials dangerous to water for HGV routing
Axle count for HGV routing
Maximum axle load for HGV routing in tons
Whether the vehicle has a trailer for HGV routing
Vehicle top speed for HGV routing in km/h
Whether the vehicle is allowed to use low-emission zones for HGV routing
Different elevation cost profiles for street routing. Using a elevation cost profile will prefer routes with a smaller incline and smaller difference in elevation, even if the routed way is longer.
- NONE: Ignore elevation data for routing. This is the default behavior
- LOW: Add a low penalty for inclines. This will favor longer paths, if the elevation increase and incline are smaller.
- HIGH: Add a high penalty for inclines. This will favor even longer paths, if the elevation increase and incline are smaller.
Optional. Default is NONE.
Set an elevation cost profile, to penalize routes with incline.
- NONE: No additional costs for elevations. This is the default behavior
- LOW: Add a low cost for increase in elevation and incline along the way. This will prefer routes with less ascent, if small detours are required.
- HIGH: Add a high cost for increase in elevation and incline along the way. This will prefer routes with less ascent, if larger detours are required.
As using an elevation costs profile will increase the travel duration, routing through steep terrain may exceed the maximal allowed duration, causing a location to appear unreachable. Increasing the maximum travel time for these segments may resolve this issue.
Elevation cost profiles are currently used by following street modes:
- BIKE
true = many to one false = one to many
Optional. Default is false. If true, the response includes the distance in meters for each path. This requires path reconstruction and is slower than duration-only queries.
Response
A list of durations. If no path was found, the object is empty.