v2.21: monetary cost optimization finalized...

[Bernd Welter]

Hi there,

Just for your information: with our upcoming v2.21 we finalized our "monetary cost optimized" routing and for this we made some changes in the API:

• The switch between "abstract routing (oldschool)" and "monetary cost optimization (the new feature)" has been changed from a boolean value to an "enum" with possible the values ABSTRACT_COSTS and MONETARY_COSTS
• Whenever you apply MONETARY_COSTS we always use the combination of the factors
  • costPerKilometer (api)
  • workingCostPerHour (api)
  • tollCosts (data)
• the CostPerSpeed parameter has been removed at all

If you used a pre-v2.21 version of the experimental API you will face a change in the interface (both request- and response wise). Just recreate your client classes and fix these minor parts.

Find more details at

• RouteCalculationCriteria : choose your algorithm
• MonetaryCostOptions : specify the tarrifs

Best regards,
Bernd

[Bernd Welter]

And one more important info in this context:
In the meantime the number of influencing factors is grown - MONETARY now covers:

• costs per distance (v2.21)
• costs per working time (v2.21)
• toll (derived by the geometry and vehicles properties, not via parameter)
• fuel /energy costs : e.g. it is now possible to define
  • costs per energy unit (e.g. 2.00€ per 1 liter Diesel) (v2.23: costsPerEnergyUnit / v2.26: costsPerFuelUnit)
  • energy/fuel consumption per speed, e.g. 30km/h: 20l/100km versus 80km/h: 30l/100km...(v2.23)