openrouteservice

<openrouteserviceConfiguration
<service
<url
>
required
anyURI

Main URL of the service, such as https://routing.gdi.disy.net/ors.

</url>
<version
xsd:string
v2

Version 2 of OpenRouteService, the latest as of end 2021.

>
required

API version setting of the routing. Currently only v2 is supported by the Cadenza client implementation. Version 1 is not supported.

</version>
<apiKey
>
optional
string

API key necessary for accessing some restricted OpenRouteServices.

</apiKey>
<capabilities
<profiles
<profile
xsd:string
driving-car

Car.

driving-hgv

Heavy goods vehicle.

cycling-regular

Bicycle.

cycling-road

Road bicycle.

cycling-mountain

Mountain bicycle.

cycling-electric

Electric bicycle.

foot-walking

Pedestrian.

foot-hiking

Hiker.

wheelchair

Wheelchair.

default
optional
=
boolean

true to set the profile as default. The profile will be selected initially when routing is started.

Default: false

>
requiredmax. unbounded

Routing profile. At least one has to be defined.

</profile>
>
required

Settings for one or more routing profiles (locomotion modes). If no profile is explicitly set as default, the first profile will be used.

</profiles>
<elevation
>
optional

Add this element without content if elevation data is available and supported for the service.

</elevation>
<isochrones
<direction
>
optional

Add this element without content if direction for isochrones requests are supported for the service and its profiles.

</direction>
>
optional

Add this element without content if isochrone requests are supported for the service and its profiles.

</isochrones>
<statistic
>
optional

Add this element without content if server has statistic capability for its profiles.

</statistic>
>
required

Property settings of the routing. Defines what the service offers via its API, most importantly, which routing profiles are available. Other information such as the availabilty of elevation data can be provided as well, enabling the client to query and display additional data for a route.

</capabilities>
<tuning
<language
>
optional
string

The language in which the description of the calculated route is displayed. Default value is de (German).

Default: de

</language>
<defaultIsochroneDuration
xsd:duration
>
optional

Default duration between isochrones in minutes (according to the ISO 8601 standard). Default is 60. Note: The values must be below the constraint defined in the <restrictions> section.

</defaultIsochroneDuration>
<defaultIsochroneDistance
xsd:int
>
optional

Default distance between zone borders in meters. Default is 5000. Note: The values must be below the constraint defined in the <restrictions> section.

</defaultIsochroneDistance>
<httpRequestTimeout
>
optional
duration

Duration (according to the ISO 8601 standard) the OpenRouteService will wait for a response. A response timeout value is already globally defined for Cadenza, but since requests for the isochrones can take longer than usual, it may be useful to define a higher timeout value here.

Default: PT30S

</httpRequestTimeout>
>
optional

Optional tuning settings for the routing. Set properties to more preferable defaults, e.g. set default language for textual instructions (the service does not support all languages and using the user language may not be possible). Note: Setting may be overwritten by a client request, e.g. because the user chose a different routing language.

</tuning>
<restrictions
<maxStopovers
>
optional
int

Maximum number of stopovers between start and end point. Can be between 0 and 48 (resulting in a maximum of 50 waypoints in total). Note: Start and end point are not counted.

</maxStopovers>
<maxIsochroneLocations
>
optional
int

Number of isochrone waypoints. Default is 2.

</maxIsochroneLocations>
<maxIsochroneZones
>
optional
int

Number of isochrone zones. Default is 7.

</maxIsochroneZones>
<maxIsochroneDuration
xsd:duration
>
optional

Maximum sum of inter-isochrone durations.

</maxIsochroneDuration>
<maxIsochroneDistance
xsd:int
>
optional

Maximum sum of inter-isochrone distances.

</maxIsochroneDistance>
<maxGeometryPointCount
>
optional
int

Maximum number of points for a geometry or route. Default is 50000.

</maxGeometryPointCount>
<maxAvoidPolygonCount
>
optional
int

Maximum number of polygon-delimited regions to avoid in the route and isochrone calculations.

Default: 5

</maxAvoidPolygonCount>
<maxAvoidPolygonArea
>
optional
long

Maximum area in square meters of each polygon-delimited region to avoid in the route and isochrone calculations.

Default: 500000000

</maxAvoidPolygonArea>
<maxAvoidPolygonWidth
>
optional
int

Maximum width in meters of the bounding box of each polygon-delimited region to avoid in the route and isochrone calculations.

Default: 20000

</maxAvoidPolygonWidth>
<maxAvoidPolygonHeight
>
optional
int

Maximum height in meters of the bounding box of each polygon-delimited region to avoid in the route and isochrone calculations.

Default: 20000

</maxAvoidPolygonHeight>
<onDemand
>
optional

Add this element without content if the route should not be calculated until clicking the corresponding button on the user interface. By default, the route is calculated dynamically while the user sets the waypoints of the route.

</onDemand>
>
optional

Settings for restricting the capabilities of the routing service, in order to prevent overloading the system or the user. Restrictions could be length of routes, quality of received routing geometry or number of stopovers. Also allows restricting the service to be only executed on demand, rather than automatically on drag'n'drop of way points.

</restrictions>
>
optionalmax. unbounded

Settings for the connection of a routing service. Can be one or more. That way, you can add different settings for each profile of a routing service. Note: Currently only OpenRouteService (API version v2) is supported. Note: Cadenza does not validate if a routing service actually supports the API version, configured profiles or further configured properties (e.g. maximum 48 waypoints).

</service>
>
required

Configuration of an OpenRouteService routing service for Cadenza.

</openrouteserviceConfiguration>
<service
<url
>
required
anyURI

Main URL of the service, such as https://routing.gdi.disy.net/ors.

</url>
<version
xsd:string
v2

Version 2 of OpenRouteService, the latest as of end 2021.

>
required

API version setting of the routing. Currently only v2 is supported by the Cadenza client implementation. Version 1 is not supported.

</version>
<apiKey
>
optional
string

API key necessary for accessing some restricted OpenRouteServices.

</apiKey>
<capabilities
<profiles
<profile
xsd:string
driving-car

Car.

driving-hgv

Heavy goods vehicle.

cycling-regular

Bicycle.

cycling-road

Road bicycle.

cycling-mountain

Mountain bicycle.

cycling-electric

Electric bicycle.

foot-walking

Pedestrian.

foot-hiking

Hiker.

wheelchair

Wheelchair.

default
optional
=
boolean

true to set the profile as default. The profile will be selected initially when routing is started.

Default: false

>
requiredmax. unbounded

Routing profile. At least one has to be defined.

</profile>
>
required

Settings for one or more routing profiles (locomotion modes). If no profile is explicitly set as default, the first profile will be used.

</profiles>
<elevation
>
optional

Add this element without content if elevation data is available and supported for the service.

</elevation>
<isochrones
<direction
>
optional

Add this element without content if direction for isochrones requests are supported for the service and its profiles.

</direction>
>
optional

Add this element without content if isochrone requests are supported for the service and its profiles.

</isochrones>
<statistic
>
optional

Add this element without content if server has statistic capability for its profiles.

</statistic>
>
required

Property settings of the routing. Defines what the service offers via its API, most importantly, which routing profiles are available. Other information such as the availabilty of elevation data can be provided as well, enabling the client to query and display additional data for a route.

</capabilities>
<tuning
<language
>
optional
string

The language in which the description of the calculated route is displayed. Default value is de (German).

Default: de

</language>
<defaultIsochroneDuration
xsd:duration
>
optional

Default duration between isochrones in minutes (according to the ISO 8601 standard). Default is 60. Note: The values must be below the constraint defined in the <restrictions> section.

</defaultIsochroneDuration>
<defaultIsochroneDistance
xsd:int
>
optional

Default distance between zone borders in meters. Default is 5000. Note: The values must be below the constraint defined in the <restrictions> section.

</defaultIsochroneDistance>
<httpRequestTimeout
>
optional
duration

Duration (according to the ISO 8601 standard) the OpenRouteService will wait for a response. A response timeout value is already globally defined for Cadenza, but since requests for the isochrones can take longer than usual, it may be useful to define a higher timeout value here.

Default: PT30S

</httpRequestTimeout>
>
optional

Optional tuning settings for the routing. Set properties to more preferable defaults, e.g. set default language for textual instructions (the service does not support all languages and using the user language may not be possible). Note: Setting may be overwritten by a client request, e.g. because the user chose a different routing language.

</tuning>
<restrictions
<maxStopovers
>
optional
int

Maximum number of stopovers between start and end point. Can be between 0 and 48 (resulting in a maximum of 50 waypoints in total). Note: Start and end point are not counted.

</maxStopovers>
<maxIsochroneLocations
>
optional
int

Number of isochrone waypoints. Default is 2.

</maxIsochroneLocations>
<maxIsochroneZones
>
optional
int

Number of isochrone zones. Default is 7.

</maxIsochroneZones>
<maxIsochroneDuration
xsd:duration
>
optional

Maximum sum of inter-isochrone durations.

</maxIsochroneDuration>
<maxIsochroneDistance
xsd:int
>
optional

Maximum sum of inter-isochrone distances.

</maxIsochroneDistance>
<maxGeometryPointCount
>
optional
int

Maximum number of points for a geometry or route. Default is 50000.

</maxGeometryPointCount>
<maxAvoidPolygonCount
>
optional
int

Maximum number of polygon-delimited regions to avoid in the route and isochrone calculations.

Default: 5

</maxAvoidPolygonCount>
<maxAvoidPolygonArea
>
optional
long

Maximum area in square meters of each polygon-delimited region to avoid in the route and isochrone calculations.

Default: 500000000

</maxAvoidPolygonArea>
<maxAvoidPolygonWidth
>
optional
int

Maximum width in meters of the bounding box of each polygon-delimited region to avoid in the route and isochrone calculations.

Default: 20000

</maxAvoidPolygonWidth>
<maxAvoidPolygonHeight
>
optional
int

Maximum height in meters of the bounding box of each polygon-delimited region to avoid in the route and isochrone calculations.

Default: 20000

</maxAvoidPolygonHeight>
<onDemand
>
optional

Add this element without content if the route should not be calculated until clicking the corresponding button on the user interface. By default, the route is calculated dynamically while the user sets the waypoints of the route.

</onDemand>
>
optional

Settings for restricting the capabilities of the routing service, in order to prevent overloading the system or the user. Restrictions could be length of routes, quality of received routing geometry or number of stopovers. Also allows restricting the service to be only executed on demand, rather than automatically on drag'n'drop of way points.

</restrictions>
>
required

Exists only for testing the service definition directly, e.g. in OrsRoutingRequestBuilderTest.

</service>