enrichment_isochrones

<enrichmentIsochrones
<timeout
>
optional
duration
</timeout>
<validationCriteria
>
requiredmax. unbounded
Choice: Choose only ONE of the following
<maxDuration
>
required
duration

Defines a maximum value for the duration (inclusive) according to the ISO 8601 standard. If the routing mode is of type “Duration”, then the value selected by the user must be less than or equal to this duration value for the criteria to match. This setting should not exceed the value maxIsochroneDuration in the openrouteservice-config.xml file.

</maxDuration>
<maxDistance
>
required
int

Defines a maximum (inclusive) distance value in meters. If the routing mode is of type "Distance", then the value selected by the user must be less than or equal to this distance value for the criteria to match. This setting should not exceed the value maxIsochroneDistance in the openrouteservice-config.xml file.

</maxDistance>
Choice End
<maxRecordCount
>
required
long

Defines a limit (inclusive) for the maximum number of data records so that execution with the parameterization selected by the user is still allowed. Note that for a multi-point geometry type, more isochrone requests could be made than the defined maxRecordCount.

</maxRecordCount>
</validationCriteria>
>
required

Configuration for isochrones enrichment. These settings are optional. An ordered list of validation criteria is used to limit the number of data records that can be used in a individual isochrones enrichment run, depending on the given distance/duration value. Cadenza provides the following defaults if no configuration is given.

For distance value:

<validationCriteria>
  <maxDistance>25000</maxDistance>
  <maxRecordCount>400</maxRecordCount>
</validationCriteria>
<validationCriteria>
  <maxDistance>50000</maxDistance>
  <maxRecordCount>200</maxRecordCount>
</validationCriteria>
<validationCriteria>
  <maxDistance>100000</maxDistance>
  <maxRecordCount>50</maxRecordCount>
</validationCriteria>

For duration value:

<validationCriteria>
  <maxDuration>PT15M</maxDuration>
  <maxRecordCount>400</maxRecordCount>
</validationCriteria>
  <validationCriteria>
  <maxDuration>PT30M</maxDuration>
<maxRecordCount>200</maxRecordCount>
</validationCriteria>
<validationCriteria>
  <maxDuration>PT60M</maxDuration>
<maxRecordCount>50</maxRecordCount>
  </validationCriteria>

Given a certain number of data records, one criterion must be applied in order to perform isochrones enrichment. For example, for

  • 150 records, the distance must be less than 50000 m (50 km) or the duration less than 30 minutes.

  • For 280 records, the distance must be less than 25 km or the duration less than 15 minutes.

More than 400 records cannot be used in this configuration.

Please note that the values used here for duration and distance take into account the settings for maxIsochroneDuration and maxIsochroneDistance in the openrouteservice-config.xml file.

</enrichmentIsochrones>