handling of delivery (API v1)

[Bernd Welter]

Hi there,

even nowadays the handling of delivery restrictions requires some explanation. I therefore collect some URLs that could be helpful in this context.

Let's start with the potential values of road segments attributes.

• Use cases/xRoute/DSC_TruckAttributesFormat.htm#Special - this chapter describes the two kinds of delivery attributes: roughly spoken: "available for delivery" versus "available for delivery under certain conditions" (e.g. weight).

Once you understood the potential values of the related attributes on the segments it is time to check the corresponding properties that are part of a routing profile:

• Routing/Vehicle/Legal/LegalCondition/@isDelivery
• Routing/Course/BasicDataRules/VehicleSpecific/DeliveryVehicles/@segmentMalus
• Routing/Course/AdditionalDataRules/VehicleSpecific/Malus/@delivery
• And here is another thread in the forum that is related to this topic

Be aware that as of today PTV engines can't derive a vehicle's delivery context. Therefore the client is responsible to decide about the settings of these parameters.

Besides the built in logic of "blocking segments if they match specifc conditions" (such as delivery) you could also consider further ways to block segments in a specific routing, e.g. by using the ExceptionPath object. With this approach you could refer to objects such as specific mountain passes, tunnels and more if they are not accessible through the regular truck attributes. To keep it short: you could describe the exception path via one of the following mechanisms:

• List of nodes
• External segment IDs
• street name
• binary path description
• an intersecting line

Attention "intersecting line" and "street name" are the only approaches that do NOT depend on a map version. E.g. if you try to work with BinaryPath you should be aware that this string representation of a calculated route changes with a map update!

Fernpass B179 (D-Füssen : A-Nassereith) blocked via ExceptionPath.IntersectingLine

Bernd