CO2: ‘Hybrid ratio’ is taken into account when using Actual (total) tour consumption for CO2 calculations

This forum deals with any kind of routing computation whether it is simple A:B-routing, calculation of isochrones, simple matrix computation or nearest search.
Post Reply
CAPcargo
Posts: 58
Joined: Tue May 19, 2015 12:53 pm

CO2: ‘Hybrid ratio’ is taken into account when using Actual (total) tour consumption for CO2 calculations

Post by CAPcargo »

Hi all,

We are currently facing an issue regarding CO2 calculation when using Actual fuel and electricity consumption on tours with hybrid vehicles.
When a hybrid vehicle is assigned to a tour, and actual consumption values are provided, you still apply the Hybrid ratio from the vehicle profile during CO2 calculation.

However, from our perspective, this behavior is not correct when actual values are explicitly provided.

i.e. Tour with Hybrid vehicle that has Hybrid ratio 40 (40% of the total energy consumption is from electricity), has stated Actual Fuel consumption of 100l and Actual electricity consumption of 200kWh.

Currently when calculating CO2, PTV is taking into account the hybrid ratio and reducing the total fuel consumption by the ratio indicated.

Example:
Actual fuel consumption: 100 liters
Actual electricity consumption: 200 kWh

Current behavior
PTV applies the hybrid ratio again:
Fuel:
Actual Fuel 100 * 0.72 (specific weight) * hybrid ratio (0.6) = 44.4 kg
Electricity:
Actual electricity 200 * hybrid ratio (0.4) = 80 kWh

Expected behavior
When actual values are provided, they should be treated as final total consumption values, without any further distribution based on hybrid ratio:
Fuel used should be Actual fuel * specific weight (100*0.72 for gasoline = ~72 kg of fuel, and Electricity = Actual electricity = 200 kWh.

Is this the intended behavior, or is this a known issue?

Also, are there any plans to adjust this logic in future versions, or should we handle this via a workaround on our side?

Thanks in advance for your clarification!
Last edited by Bernd Welter on Thu Apr 09, 2026 8:19 am, edited 1 time in total.
Reason: Forwarded to DEV via Ticket #5823
Post Reply