Calculating Emissions for a Routing with a Comprehensive Approach
Comprehensive emission calculation approaches contain default values for fuel consumption and factors for calculation. As user no own consumption data has to be added. PTV xRoute offers several comprehensive approaches: HBEFA (4 or 3.2) and COPERT Australia 1.2. In this use case description you see how both standards are designed and how you can use them for calculating your emissions with PTV xRoute. A general overview of emission calculation with PTV xServer can be found here: How to calculate emissions for a routing. Emission calculation with factor-based approaches is described here: How to calculate emissions with factor-based approaches.
Benefits
Using HBEFA, the entire bundle of emissions will be provided for each 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. type. The following list indicates the resulting attributes: Hydrocarbons, hydrocarbons except for methane, methane, carbon monoxide, carbon dioxide, carbon dioxide from fossil sources, sulphur dioxide, nitrous oxide, nitrogen oxides, nitrogen dioxide, ammonia, benzene, lead, particles, particle number and fuel.
COPERT Australia emission calculation reports values for CO2 and fuel consumption. It is explicitly designed for Australian fleets:
- It reflects Australian fleet composition
- It reflects Australian fuels
- It reflects Australian driving conditions
CO2-equivalent
Carbon dioxide is the best known greenhouse gas. However, there are other pollutants that have an effect on global warming. These gases can have a very significant warming power. The main greenhouse gases are carbon dioxide (CO2), methane (CH4) and nitrous oxide (N2O).
Based on the warming power of carbon dioxide, a scale of called "Global Warming Potential" can be defined. The CO2 has a GWP of 1, methane 25 and nitrous oxide 300. With the Global Warming Potential, we can define a new metric call CO2-equivalent, that represents the sum of the multiplication of all greenhouse gases by their Global Warming Potential.
Well to wheel, tank to wheel
The well to wheel/ tank to wheel are two metrics used in greenhouse gas emissions and energy efficiency.
The Well to wheel metric refers to all the fuel that was burnt from the production of the primary fuel to the fuel consumption. It includes production of the primary fuel, the transport of the primary fuel, the production of road fuel, the distribution of the road fuel and the consumption of this road fuel in the 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..
The Tank to wheel metric only refers to the consumption of the road fuel in the vehicle.
Influence of payload
In the vehicleProfile, the user can give the vehicle load informations in order to have more precise emissions factors. The xRoute module needs 3 informations:
- emptyWeight (The empty weight of the vehicle [kg])
- loadWeight (The weight of the vehicle's load [kg])
- totalPermittedWeight (The total permitted weight of the vehicle and load [kg])
With these 3 informations, The xRoute module will estimate the current load of the vehicle and map the result to the HBEFA data.
Concept HBEFA
Emission Calculation According to HBEFA
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 and France) as well as the JRC (European Research Center of the European Commission) are supporting HBEFA. HBEFA provides emission factors, i.e. the specific emission in g/km for all current 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. categories (PC, LCV, HCV, buses and motorcycles), each divided into different categories, for a wide variety of traffic situations. The first version (HBEFA 1.1) was published in December 1995, an update (HBEFA 1.2) followed in January 1999. Version HBEFA 2.1 was available in February 2004. The newest versions date are January 2010 (HBEFA 3.1), July 2014 (HBEFA 3.2), September 2019 (HBEFA 4.1) and January 2022 (HBEFA 4.2).
HBEFA calculation reports values for all global warming gases and other harmful substances. The internal process is independently certificated and therefore is independent of any external organizations.
Influencing Factors for Calculation
The following data properties were mapped from HBEFA to PTV's routingA 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. engine:
- Vehicle category such as car, van, truck, road train, bus or motorcycle.
- Fuel type such as GASOLINE, DIESEL, ETHANOL, CNG (Compressed Natural Gas), LPG (Liquefied Petroleum Gas), LNG (Liquefied Natural Gas), FFV (Flexible Fuel Vehicle) and dual fuels as CNG_GASOLINE and LPG_GASOLINE.
- Emission concept from Euro 0 until Euro 7.
- For truck profiles A profile is a collection of parameters used to configure the request. Full profiles consist of a number of specialized sub-profiles like the VehicleProfile which describes the properties of a vehicle. only, the loadWeight is relevant.
- Road types such as motorway national and cityA city is the largest or most important locality used in an address. The other localities are sometimes called districts to emphasize that they are part of, or smaller, or less important than the city., trunk road national and cityA city is the largest or most important locality used in an address. The other localities are sometimes called districts to emphasize that they are part of, or smaller, or less important than the city., distributor secondary, localAn address can have one or more localities, which are the names of cities or districts used to distinguish the address from other addresses sharing e.g. the same street name and house number. or access-residential.
- Heights, speed and network classesThe road segments are divided into eight network classes by importance of the roads they represent. The network class 0 represents the most important roads, for example highways, while road segments of network class 7 are the least important roads, for example pedestrian paths. The term network level is often used synonymously, in fact the network level equals the network class plus one.
HBEFA Support
Depending on the HBEFA version, a wide range of combinations are supported. Navigate the following HBEFA tree for a full list of supported combinations for each Hbefa data version.
Installation and Configuration Guide HBEFA
This installation is optional according to your licence agreement (additional licence fee is required). The data package HBEFA 3.2 or HBEFA 4 can be part of a map or it can be separately installed. Please contact your PTV representative to obtain the data. Following steps should be carried out:
- Order the data at PTV
- Install the new licence key
- Unzip and copy the content of the emissions data in
data/emissions
.
Emissions data already contained in the map is preferred over data in data/emissions.
Concept COPERT Australia
Emission Calculation According to COPERT Australia
The COmputer Program to calculate Emissions from Road Transport (COPERT) was originally developed by EMISIA and the European Environment Agency as road transport emission inventory preparation for European countries. COPERT Australia was adapted to the Australian driving conditions, vehicle types and fuel types by EMISIA and DSITIA. The COPERT Australia emission calculation reports values for CO2 and fuel consumption.
Supported vehicle types
pedestrian/bicycle/motorbike/car/truck less than 7.5 t total weight/Minivan |
Emission calculation is not supported. |
truck more than 7.5 t total weight/truck with trailer/combustible truck more than 7.5 t total weight/water hazardous truck more than 7.5 t total weight/bus |
Supported fuel types are Diesel and Liquefied Petroleum Gas. Euro 0 is not supported. The emission technology for exhaust gas recirculation(EGR) is needed for Euro 5, Euro EEV, Euro 6, Euro 6c and Euro 7. The loadWeight is considered. The cylinder capacity is not considered. |
Emission class mapping
Comparable to the European emission standards there are Australian Design Rules(ADR). The European classifications are mapped internally to ADRs as follows:
ADR30 | Euro 1 |
ADR70-00 | Euro 2 |
ADR80-00 | Euro 3 |
ADR80-02 | Euro 4 |
ADR80-03 with exhaust gas recirculation | Euro 5 |
ADR80-04 with exhaust gas recirculation | Euro 6 |
ADR80-05 with exhaust gas recirculation | Euro 7 |
Installation and Configuration Guide COPERT Australia
This installation is optional according to your licence agreement (additional licence fee is required). The data package COPERT Australia can be part of a map or it can be separately installed. Please contact your PTV representative to obtain the data. Following steps should be carried out:
- Order the data at PTV
- Install the new licence key
- Unzip and copy the content of the emissions data in
data/emissions
.
Emissions data already contained in the map is preferred over data in data/emissions.
Programming Guide
The example below shows the calculation of emissions using a comprehensive approach 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_HBEFA_4", "scenarios": [ "CURRENT_ROUTE" ] }; var scenarioC = { "$type": "EmissionValueScenario_EMISIA_COPERT_AUSTRALIA_1_2", "scenarios": [ "CURRENT_ROUTE" ] }; xroute.calculateRoute({ "waypoints" : [A, B], "resultFields": { "emissions": true }, "routeOptions": { "emissionOptions": { "valueScenarios": [scenarioA, scenarioB, scenarioC] } }, "requestProfile": { "vehicleProfile": { "engine": { "emissionStandardAustralia": "ADR_80_03" } } } }, routingCompleted); function routingCompleted(route, exception) { print('HBEFA_3_2.carbonDioxide: ' + route.emissions.values[0].carbonDioxide + ', HBEFA_4.carbonDioxide: ' + route.emissions.values[1].carbonDioxide + ', EMISIA_COPERT_AUSTRALIA_1_2.carbonDioxide: ' + route.emissions.values[2].carbonDioxide); }