Support of Hybrid Itineraries

The new json itinerary format allows specification of different compute type option per routepart.
It means you can have some settings from waypoint 1 to waypoint 2, and then different settings from waypoint 2 to waypoint 3, etc.
The change of route compute type is managed through the json parameter routeComputeType

There are 5 types currently available:

  • car
  • truck
  • van
  • camper
  • bus

Example with global settings:

{
    "name": "HybridRouteTest 1",
    "version":  "2.2",
    "directives":   {
        "routeComputeType": "van",
        ...
    },
    "routeParts":   [
      ...
    ]
}

Example with local settings:

{
    "name": "HybridRouteTest 2",
    "version":  "2.2",
    "routeParts":   [
      {
        "directives":   { "routeComputeType":   "car" }
        "waypointTo" :  { ... }

      },
      {
        "directives":   { "routeComputeType":   "van" }
        "waypointTo" :  { ... }
      },
      ...
    ]
}

Definition of the routeComputeType parameter

Route Compute type Description
car no truck attributes applied
truck truck attributes applied
camper only dimensional truck attributes restrictions applied
bus similar to camper, but opens up special roads for buses
van similar to car, but opens up delivery zones for routing

Note
Please note the above json settings for a route calculation is the better alternative to relatively cumbersome settings over settings.ini, which moreover can only be set global without dynamic variability. The relation is as follows:

car         UseTruckAttribs=no  Camper=no   Van=no      OnlyDimRestrictions=no
van         UseTruckAttribs=no  Camper=no   Van=yes     OnlyDimRestrictions=no
truck       UseTruckAttribs=yes Camper=no   Van=no      OnlyDimRestrictions=no
camper      UseTruckAttribs=no  Camper=yes  Van=no      OnlyDimRestrictions=yes