Calculating Emissions for a Routing
PTV provides the possibility to calculate emission values for routingsA route corresponds to a path of a vehicle through the underlying transport network. The main attributes of a route are the distance and the time that the vehicle travels along the path. taking vehiclesIn this context the term vehicle is used to describe what is being routed for. Commonly this will be a motorized vehicle like a truck including its trailer or a car. However also a bike or a pedestrian are included in this definition. and routeA route corresponds to a path of a vehicle through the underlying transport network. The main attributes of a route are the distance and the time that the vehicle travels along the path. into account. Different approaches according to various international standards are available for the calculation. These standards provide region specific factors for the determination of the emission values. Currently, PTV xServer offers emission calculation based on the following standards:
- NGA 2015 (Australia): Emission calculation for transports in Australia have to be in accordance with the National Greenhouse Accounts (NGA) factors published by the Australian government.
- CEN 2012 (Europe): The CEN standard EN 16258 is an European standard specifying general principles, definition, calculation methods and data recommendations, with the objective to promote standardized, accurate, credible and verifiable declarations, regarding energy consumption and emissions related to any transport service.
- CEN ISO 14083 2023 (Europe/North America/South America/Africa/Asia): The CEN standard ISO 14083 is an european / american / asian / african standard reporting greenhouse gas emissions arising from transport chain operations
- CO2 Decree France 2011 (deprecated): Since 2013, all commercial transports (trucks, taxis, ships, trains, etc.) starting or ending in France have to report their CO2 emissions. In other words, a company carrying out a transport from or to France has to report their emissions.
- CO2e Decree France 2017: Since 2013, all commercial transports (trucks, taxis, ships, trains, etc.) starting or ending in France have to report their CO2e emissions. In other words, a company carrying out a transport from or to France has to report their emissions.
- COPERT Australia 1.2: COPERT Australia is designed to be used for road transport emission inventories across Australia. It is the result of a joint effort of EMISIA and the Queensland Department of Science.
- HBEFA 3.2 or HBEFA 4 (Europe): The Handbook of Emission Factors for Road Transport (HBEFA) was originally developed on behalf of the Environmental Protection Agencies of Germany, Switzerland and Austria. In the meantime, further countries (Sweden, Norway, France) as well as the JRC (European Research Center of the European Commission) are supporting HBEFA. This procedure is obsolete and has been superseded by ISO 14083 and CEN 2012 for the calculation of CO2e. For the standard-compliant calculation of CO2e, this procedure should not be implemented in new projects/products.
- UK DEFRA 2014: Government conversion factors for greenhouse gas reporting. These factors are suitable for use by UK based organization of all sizes, and for international organizations reporting on UK operations. This procedure is obsolete and has been superseded by ISO 14083 and CEN 2012 for the calculation of CO2e. For the standard-compliant calculation of CO2e, this procedure should not be implemented in new projects/products.
In order to get correct emissions values, make sure the PTV xRoute response does not contain any ParameterInconsistencyLimitation. In such case, resolve those first.
If the given vehicle The term vehicle describes what is being routed or planned for. Vehicles are used in route calculation, distance matrix calculation and effectively also in tour planning. In route calculation, vehicle properties like overall size, weight and speed are in focus. In tour planning, it is vehicle properties like capacity and availability. Commonly a vehicle is motorized, like a truck - including its trailer or a car. However also a bike or even a pedestrian are included in this definition. configuration is not supported by the emissions standard requested, the PTV xRoute will return a VehicleNotSupportedForEmissionsLimitation. In this case, the returned emission values will contain only zeros.
Benefits
Obtain the levels of emissions according to the various approaches and profit from the advantages:
- Verify your emission totals
- Meet legal requirements
- Choose between different calculation approaches fitting to your fleet
- Use your own average fuel consumptions or take one of the provided default value catalogs
Prerequisites
Check if the following prerequisites are fulfilled in order to use Emission calculation.
- Installed and licensed PTV xRoute service
- PTV xRoute Server and PTV map of the area for routeA route corresponds to a path of a vehicle through the underlying transport network. The main attributes of a route are the distance and the time that the vehicle travels along the path. calculation.
- License key for emissions (depending on the type of emissions).
- For HBEFA and COPERT: Additional emission data are obligatory such as emission factors, global data and specific vehicleIn this context the term vehicle is used to describe what is being routed for. Commonly this will be a motorized vehicle like a truck including its trailer or a car. However also a bike or a pedestrian are included in this definition.-dependent properties.
Concepts
For HBEFA and COPERT: Additional emission data are obligatory such as emission factors, global data and specific vehicleIn this context the term vehicle is used to describe what is being routed for. Commonly this will be a motorized vehicle like a truck including its trailer or a car. However also a bike or a pedestrian are included in this definition.-dependent properties:
- Vehicle-specific factors as for example vehicle type, fuel type, fuel consumption
- Route-specific factors like heights, distance, speed, network level etc.
These factors can be different from area to area; country to country or continent to continent. Therefore, area-specific data standards have been developed by various institutes and governments to provide the most suitable factor set. A lot of them are supported by PTV xRoute as shown in the introduction of this use case documentation. The data standards vary a lot, support different vehicle types, contain more or less factors and offer different result sets. If you want to meet national requirements you have to chose a suitable data standard.
As described above, vehicle- and route-specifics are needed for emission calculation. One important vehicle factor is the fuel consumption. It is treated different in different data standards. This is shown later. All other specifics are reflected in factors provided by the data standard.
In simple terms, emissions are calculated by multiplying fuel consumption values with emission factors. Depending on the chosen emission data standard for determining the emissions, consumption and factors are both included in the data or are provided separately. Two basic approaches are distinguished according to this difference:
- Comprehensive Approach
- Factor-based Approach
The Comprehensive Approach includes both, consumption default values and emission factors. Additionally, it also takes height data into account. HBEFA and COPERT Australia are standards of the comprehensive approach.
The Factor-based Approach provides emission factors. Consumption values are chosen by the user and can be based on own average fuel consumptions or different recommended consumption default values provided in this PTV xServer manual. Australia NGA 2015, CEN 2012, ISO 2023, CO2 Decree France 2011, CO2e Decree France 2017 and UK DEFRA 2014 are standards of the factor-based approach.
The table shows details of the various standards. It gives information of the specific consumption values and factors which are part of the standard or are recommended for it. Besides, the relevance is shown for each standard giving information for which countries the standard is published. Information about the required PTV license keys, data and PTV xServer version can also be found in this table:
Standard | Approach | Consumption | Factor | Relevance | PTV Licensing | Data Source | PTV xServer |
---|---|---|---|---|---|---|---|
Australia NGA 2015 | Factor-based | Own consumption values | Australia NGA factors | Australia | Base emission license required | No specific data required | since PTV xRoute 2.0.0 |
CEN 2012 | Factor-based | Own consumption values | CEN 2012 | Europe (without UK) | Base emission license required | No specific data required | since PTV xRoute 2.0.0 |
ISO 14083 2023 | Factor-based | Own consumption values | ISO 14083 2023 | Europe, North America, South America, Africa, Asia | Base emission license required | No specific data required | since PTV xRoute 2.26 |
CO2 Decree France 2011 (deprecated) | Factor-based | Own consumption values, default values provided in the manual | CO2 Decree France 2011 | France and Europe if start or destination is in France | Base emission license required | No specific data required | since PTV xRoute 2.0.0 |
CO2e Decree France 2017 | Factor-based | Own consumption values, default values provided in the manual | CO2e Decree France 2017 | France and Europe if start or destination is in France | Base emission license required | No specific data required | since PTV xRoute 2.9.0 |
COPERT Australia 1.2 | Comprehensive | COPERT default values included in the calculation | COPERT factors | Australia | License key required: COPERTAUS12 | COPERT data and height data required | since PTV xRoute 2.0.0 |
HBEFA 3.2 | Comprehensive | HBEFA default values included in the calculation | HBEFA factors | Europe (without UK) | License key required: HBEFA32 | HBEFA data and height data required | since PTV xRoute 2.0.0 |
HBEFA 4 | Comprehensive | HBEFA default values included in the calculation | HBEFA factors | Europe (without UK) | License key required: HBEFA | HBEFA data and height data required | since PTV xRoute 2.25.0 |
UK DEFRA 2014 | Factor-based | Own consumption values, default values provided in the manual | DEFRA factors | UK | Base emission license required | No specific data required | since PTV xRoute 2.0.0 |
The PTV xServer API does not restrict the emission calculation to the relevant region as mentioned in the table above, nevertheless emission values should only be used in the relevant region.
The calculation of emissions depends on the above mentioned standards and the combination of vehicle parameters described as follows. The parameter "average fuel consumption" serves as input for company specific consumption values and needs to be set if factor-based standards are used. Incorrect combinations of vehicle parameters might lead to falsified results, or various result limitations could be added. PTV recommends validating the API (especially the class description about vehicle parameters) before setting the specific characteristics.
Attribute | Description |
---|---|
Vehicle type | Legal values are car, van respectively mini van, truck respectively truck with trailer, combustible or water hazardous truck and motorbike. |
Total weight | The total permitted weight of the vehicle in [kg] including the trailer's weight. |
Trailer weight | The total permitted weight of the trailer in [kg]. |
Empty weight | The empty weight of the vehicle and trailer including driver and half-full fuel tank in [kg]. |
Load weight | The weight of the vehicle's load (including trailer) in [kg]. |
Emission class | The emission class of this vehicle. Legal values are I-VI. |
Cylinder Capacity | The cylinder capacity of this vehicle in [ccm]. This is only relevant for COMBUSTION and HYBRID vehicles. |
Engine type | The type of engine such as combustion, hybrid or electric. |
Fuel type | Legal values are DIESEL, GASOLINE, ETHANOL, CNG (compressed natural gas), LPG (liquefied petroleum gas), LNG (liquefied natural gas) and dual fuels as CNG_GASOLINE (compressed natural gas/gasoline) and LPG_GASOLINE (liquefied petroleum gas/gasoline). This is only relevant for COMBUSTION and HYBRID vehicles. |
Emission technology | The technology type of emission reduction for trucks such as exhaust gas recirculation or selective catalytic reduction. This is only relevant for COMBUSTION and HYBRID vehicles. |
Fuel consumption | The average fuel consumption of the current vehicle in [l/100km] for liquid and dual fuel types or [kg/100km] for gaseous fuel types only like compressed natural gas. This is only relevant for COMBUSTION and HYBRID vehicles. |
Electricity Consumption | The average electricity Consumption of the current vehicle in [kWh/100km]. This is only relevant for ELECTRIC and HYBRID vehicles. |
Biofuel ratio | The ratio of bio fuel compared to conventional fuel in [%]. This is only relevant for for COMBUSTION and HYBRID vehicles with diesel, gasoline and dual fuel types. |
Hybrid ratio | The ratio between electric and combustion energies for HYBRID vehicles in [%]. |
Dual fuel ratio | For dual fuel types (CNG_GASOLINE and LPG_GASOLINE), the ratio denotes the consumption percentage of CNG/LPG from the total vehicle fuel consumption. |
Electricity Type | Defines the electricity type, battery or fuel cell. This is only relevant for ELECTRIC and HYBRID vehicles. |
Year of manufacture | Specifies the vehicle's year of manufacture. |
Selection of the emissions calculation method
The latest standard that respect the international guidelines is ISO 14083:2023 (EmissionValueScenarioType_ISO14083_2023). This emission calculation respects the new ISO 14083:2023 which was published in March 2023 as a new ISO standard succeeding the European standard EMISSIONS_EN16258_2012.
In PTV xServer we still offer both standards, but we recommend to use ISO14083_2023
in order to calculate the energy consumption and greenhouse gas emissions in accordance with ISO 14083 'Quantification and reporting of greenhouse gas emissions arising from transport chain operations'. Nonetheless the following steps also apply when using the former European standard EN16258 2012
(EmissionValueScenarioType_EN16258_2012).
Please note that depending on your region, there could be slight changes in the application of ISO 14083:2023. The emission factors are different between continents. The GLEC framework recommends to use the same factors for Europe and South America. For Asia and Africa, an uplift of 22% should be applied to the regional values for Europe, for vehicles above 3,5t. For cars and vans, an uplift of 13% should be applied.
As the ISO standard specifies that "Users should also check whether official sources have updated their values, so the most current values for an official data source can be applied", PTV provides different versions of the factors. The EmissionValueFactorsVersion_ISO14083_2023 enumeration can be used to select the version of the factors to apply.
Specification of the fuel consumption
The fuel consumption is the key element to calculate emissions. It should be specified as accurately as possible.
There are different ways to define the consumption:
-
using a customer-defined value
In PTV xServer, it is possible to fill the EffectiveFuelConsumption property, depending on your knowledge (from the most to the less accurate):- ACTUAL_CONSUMPTION: use the actually-measured actualFuelConsumptionForThisRoute and actualElectricityConsumptionForThisRoute of the vehicle which is executing the tour, if you know it.
- ROUTE_SPECIFIC_AVERAGE_CONSUMPTION: use the saved routeSpecificAverageFuelConsumption and routeSpecificAverageElectricityConsumption of a regular and similar trip.
- VEHICLE_SPECIFIC_AVERAGE_CONSUMPTION: use the known fuelConsumption and electricityConsumption of the selected vehicle.
- FLEET_SPECIFIC_AVERAGE_CONSUMPTION: use the known fleetSpecificAverageFuelConsumption and fleetSpecificAverageElectricityConsumption of your vehicle fleet. Note: the average consumption should come from vehicles of the same type.
- HBEFA_BASED_CONSUMPTION: use the HBEFA Database (Handbook of Emission Factors). For Europe, GLEC Framework uses the specifications of HBEFA. With PTV xServer the customer can directly specify to use HBEFA, when he cannot provide any average fuel consumption. To do so, please select EmissionValueScenarioType_HBEFA_4 (or EmissionValueScenarioType_HBEFA_3_2 ) in the options, instead of defining a specific consumption.
- using the GLEC Framework recommandation. If none of the above values is known, then depending on the region, the vehicle type and the fuel type, a fuel consumption is recommended. Please refer to the tables which are available in the documentation.
- using the default vehicle properties. Each stored vehicle profile in PTV xServer contains a list of properties of the vehicle, including fuelConsumption and electricityConsumption properties.
Biofuel Ratio
Biofuels cover all liquid, solid or gaseous fuels produced from biomass. They are usually blended with standard fuels (for example, E10 ethanol is a low-level biofuel blend of 10% ethanol and 90% gasoline). There is a large variety of biofuels either with diesel (B100, B5, B7, B10, B20, B99) or gasoline (E10, E15, E85). In many countries, a bioFuelRatio is required by the law.
In all emissions calculations, ethanol is considered the same as gasoline with bioFuelRatio equal to 100%.
The default value of bioFuelRatio is 0. It can be specified in the request from 0 to 100%.
- B5
B5 is a biodiesel blend of 5% biodiesel and 95% petroleum diesel
{
vehicleProfile:{
engine:{
engineType: "COMBUSTION",
fuelType: "DIESEL",
bioFuelRatio: 5
}
}
}
- B99
B99 is the highest-level biodiesel blend, containing between 1 and 0.1 percent petroleum diesel
{
vehicleProfile:{
engine:{
engineType: "COMBUSTION",
fuelType: "DIESEL",
bioFuelRatio: 99
}
}
}
- E10
E10 is an ethanol blend composed of 10% ethanol and 90% gasoline
{
vehicleProfile:{
engine:{
engineType: "COMBUSTION",
fuelType: "GASOLINE",
bioFuelRatio: 10
}
}
}
Programming Guide
The example below shows the calculation of emissions of the route A route corresponds to a path of a vehicle through the underlying transport network. The main attributes of a route are the distance and the time that the vehicle travels along the path. using the JavaScript bindings to the xRoute API:
var A = { "$type": "OffRoadWaypoint", "location": { "offRoadCoordinate": {"x": 6.1256572, "y": 49.5983745 } } }; var B = { "$type": "OnRoadWaypoint", "location": { "coordinate": {"x": 6.1256572, "y": 49.4816576 } } }; var scenarioA = { "$type": "EmissionValueScenario_HBEFA_3_2", "scenarios": [ "CURRENT_ROUTE" ] }; var scenarioB = { "$type": "EmissionValueScenario_EN16258_DEFRA_2014", "scenarios": [ "VEHICLE_SPECIFIC_AVERAGE_FUEL_CONSUMPTION" ] }; xroute.calculateRoute({ "waypoints" : [A, B], "resultFields": { "emissions": true }, "routeOptions": { "emissionOptions": { "valueScenarios": [scenarioA, scenarioB] } } }, routingCompleted); function routingCompleted(route, exception) { print('HBEFA_3_2.hydrocarbons: ' + route.emissions.values[0].hydrocarbons + ', FRENCH_CO2E_DECREE_2017_639.energyUseTankToWheel: ' + route.emissions.values[1].energyUseTankToWheel); }Related Topics
The following use cases demonstrate the emission calculation with either the comprehensive or factor-based approach: