Hi,
We would like to set EmissionClass (EURO_4, EURO_5, ...) parameter in routing. We need this paramer for toll cost calculation and for avoiding routes which have EmissionClass restrictions (for example only EURO_6 vehicles can use the route).
As we figured out from the manual we have 2 options to set that parameter: in the XML profile (Routing/Vehicle/Physical/Drive/Emissions element) located on the server and/or in the request object by using the CountryInfoVehicleOptions class. We assume that we need to set both parameters. EmissionClass paramer of ContryInfoVehicleOptions class is necessary for toll cost calculation, and the EmissionClass parameter of the XML Profile is necessary for avoiding routes based on vehicle's emission class.
It would be great if we can set the EsmissionClass paramer on demand in every query (in this case we shouldn't modify our profile xml at all). Is it possible?
So which EmissionClass parameter should we use for our routing goals?
Best regards,
Dániel Biró
Emission class parmeter
Re: Emission class parmeter
Hello Dániel,
Emission class is not used for routing. In the reference documentation you see in the vehicle element and it's children small denotes on the attributes that tell you what they influence. This is described in the vehicle element. There the documentation states: "They are denoted with (1) for routing, (2) for toll, (3) for emission calculation, and (4) for road editor". EmmissionClass is denoted with 2,3 so toll and emission calculation.
On which the use the, XML value or vehicle option class: they both have exactly the same effect. When both are set vehicle option class will be used. Note: you can also use the xml in your request instead of server side. For more about this please check: http://xserver.ptvgroup.com/fileadmin/f ... ofiles.htm
Our recommendation if to work with XML profile snippets for dynamically setting options since they have all options unified in a single place.
On the routing aspect: we do not have a restriction in our data that literally triggers on the emission class. What we do have in our data are environmental zones. I believe these are the only restriction in the real world that tie in to the emission class of the vehicle. Unfortunately the rules for these zones are differing widely per city. There we are stick to environmental zone or not. You have to decide for yourself if you want to avoid those zones or not.
With regards,
Joost
Emission class is not used for routing. In the reference documentation you see in the vehicle element and it's children small denotes on the attributes that tell you what they influence. This is described in the vehicle element. There the documentation states: "They are denoted with (1) for routing, (2) for toll, (3) for emission calculation, and (4) for road editor". EmmissionClass is denoted with 2,3 so toll and emission calculation.
On which the use the, XML value or vehicle option class: they both have exactly the same effect. When both are set vehicle option class will be used. Note: you can also use the xml in your request instead of server side. For more about this please check: http://xserver.ptvgroup.com/fileadmin/f ... ofiles.htm
Our recommendation if to work with XML profile snippets for dynamically setting options since they have all options unified in a single place.
On the routing aspect: we do not have a restriction in our data that literally triggers on the emission class. What we do have in our data are environmental zones. I believe these are the only restriction in the real world that tie in to the emission class of the vehicle. Unfortunately the rules for these zones are differing widely per city. There we are stick to environmental zone or not. You have to decide for yourself if you want to avoid those zones or not.
With regards,
Joost
Joost Claessen
Senior Technical Consultant
PTV Benelux
Senior Technical Consultant
PTV Benelux