Function documentationStatic Route Determination

 

Static route determination is part of route determination in the routing guide (see Route Determination). In static route determination, the system uses the existing routes to determine possible trips, in other words, instances of these routes (see Route).

Prerequisites

See the prerequisites under Route Determination.

Features

Determination of Geographically Possible Routes

The system first determines the number of routes that are geographically possible. Here the route must contain the start location and destination location from the request in the correct order.

A leg of a route and therefore the route itself contains a location if at least one stop in its sequence of stops contains this location. A stop of a leg contains a given location if one of the following conditions is met:

  • The stop is a location and is identical to the given location.

  • The stop is a direct zone (see Zone) and includes the given location.

  • The stop is a postal code zone or a regional zone and includes the postal code or the region of the given location.

A route contains the start location and destination location from the request in the correct order in one of the following cases:

  • At least one leg that contains the start location lies before another leg that contains the destination location in the leg sequence of the route.

  • A leg in this route contains both the start location and the destination location, and at least one stop that contains the start location lies before another stop that contains the destination location in the stop sequence of this leg.

Determination of Valid Routes

A route that is possible from a geographical point of view is valid for a request if it meets all the following conditions:

  • You have not explicitly excluded this route.

  • You have not marked the route for deletion.

  • You have not defined any restrictions for this route that make it invalid for the request (see Route).

Creating the Location Sequence of a Trip

In accordance with the division of a route into legs, the location sequence of a trip is also divided into legs.

For each relevant leg of a valid route, the system uses the stop sequence to form a fixed sequence of locations for the relevant leg of the trip. A leg of a route is only relevant to a request in the following cases:

  • It is the start leg for the request because it is the closest of all the legs containing the start location in the request to the destination location.

  • It is the destination leg for the request because it is the closest of all the legs containing the destination location in the request to the start location.

  • It is a leg between the start leg and the destination leg of the request.

Only the following locations are relevant to the system for the location sequence of the trip:

  • Start location of the request; the last stop of the start leg that contains it is called the start stop.

  • Destination location of the request; the first stop of the destination leg that contains it is called the destination stop.

  • Each transshipment location that connects two consecutive relevant legs

  • Each location in a relevant leg that you have marked as mandatory

    As a result, the zones that you have defined as (optional) stops along legs are skipped when the location sequence of the trip is created.

To create the location sequence of the trip, the system arranges the relevant locations in accordance with the following rules:

  • Two locations of different legs

    Their arrangement is given by the leg sequence of the route.

  • Two locations of different stops along the same leg

    Their arrangement is given by the stop sequence of the leg.

  • Two locations of the same stop (along the same leg)

    This case only occurs if both the start location and the destination location from the request lie in the same zone and you have defined this zone as a stop along a leg. In this case, the location sequence of each trip consists of the start location and the destination location only.

Assignments

Among other reasons, a geographical route is not valid for a request if you have excluded the means of transport of a relevant leg as a result of the request. On the other hand, you reduce the assignment to its means of transport by explicitly excluding carriers.