selfserviceenrichmentisochrones

This configuration is optional when using the plugin Routing_Openrouteservice.

  • Documentation

  • YAML Format

  • XML Format

Fill relevant inputs (blue boxes) and click the blue bars on the left to copy XML configuration snippets.
<enrichmentIsochrones
<timeout
>
optional
duration

ISO 8601 Duration Format

Format: P[n]Y[n]M[n]DT[n]H[n]M[n]S

  • P is the duration designator (period) placed at the start of the duration representation
  • Y is the number of years
  • M is the number of months
  • D is the number of days
  • T is the time designator that precedes the time components
  • H is the number of hours
  • M is the number of minutes
  • S is the number of seconds

Examples:

  • PT5M - 5 minutes
  • PT1H30M - 1 hour and 30 minutes
  • P1D - 1 day
  • P1Y2M3DT4H5M6S - 1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds

Timeout (duration according to ISO 8601 in PnYnMnDTnHnMnS format, e.g. PT600S means "up to 600 seconds from now"; more information) for the execution of an isochrones enrichment. No timeout is set by default.

Note: The timeout setting httpRequestTimeout for the Openrouteservice (openrouteservice-config.xml file) is taken into account for each individual request to the Openrouteservice that is required to calculate the isochrones enrichment.

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

ISO 8601 Duration Format

Format: P[n]Y[n]M[n]DT[n]H[n]M[n]S

  • P is the duration designator (period) placed at the start of the duration representation
  • Y is the number of years
  • M is the number of months
  • D is the number of days
  • T is the time designator that precedes the time components
  • H is the number of hours
  • M is the number of minutes
  • S is the number of seconds

Examples:

  • PT5M - 5 minutes
  • PT1H30M - 1 hour and 30 minutes
  • P1D - 1 day
  • P1Y2M3DT4H5M6S - 1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds

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>
This is a generated sample file with fake data and all the possible options shown, refer to the Documentation tab for what combinations are valid and what is required or not. 
cadenzaconfig:
  settings:
    selfserviceenrichmentisochrones:
      timeout: "P2DT3M"
      validationCriteria:
      - maxDuration: "P2DT3M"
        maxDistance: 15
        maxRecordCount: 25
      - maxDuration: "P2DT3M"
        maxDistance: 15
        maxRecordCount: 25

Filename: selfserviceenrichmentisochrones-config.xml

This is a generated sample file with fake data and all the possible options shown, refer to the Documentation tab for what combinations are valid and what is required or not. 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<enrichmentIsochrones>
  <timeout>P2DT3M</timeout>
  <validationCriteria>
    <maxDuration>P2DT3M</maxDuration>
    <maxDistance>15</maxDistance>
    <maxRecordCount>25</maxRecordCount>
  </validationCriteria>
  <validationCriteria>
    <maxDuration>P2DT3M</maxDuration>
    <maxDistance>15</maxDistance>
    <maxRecordCount>25</maxRecordCount>
  </validationCriteria>
</enrichmentIsochrones>