Addition of two new range datapoints?

[erikbosch]

Another topics related to ACEA datapoints (#180). ACEA currently list two datapoints for range:

 10. Remaining Electric Range/Distance
 12. Total Remaining Range

VSS only has one, and it does not really match any of them (if we consider "FuelSystem" to refer to liquid fuel only)

Vehicle.Powertrain.FuelSystem.Range (meters)

If looking at other APIs (see list at bottom) one can see that it is common to either have separate ranges for Battery/Fuel, or just a common one.

Suggested discussion points:

• Shall we add e.g. "Vehicle.Powertrain.Battery.Range (range in meters using only battery)" and "Vehicle.Range or Vehicle.Powertrain.Range (total range in meters using both battery and fuel)" to cover all use-cases?
• (I assume that "Vehicle.Range == Vehicle.Powertrain.Battery.Range + Vehicle.Powertrain.FuelSystem.Range" is not always true, i.e. that the combination can be bigger than the individual parts)

Reference use case in other APIs:

Volvo: https://developer.volvocars.com/volvo-api/extended-vehicle/#Distance_To_Empty

distanceToEmpty in kilometers (not specified whether battery (if any) is considered)

Mercedes: https://developer.mercedes-benz.com/products/connect_your_fleet/details

Driving.Range.Electrical (km)
Driving.Range.Fuel (Remaining range liquid fuel, km)

Android: https://android.googlesource.com/platform/hardware/interfaces/+/master/automotive/vehicle/2.0/types.hal

RANGE_REMAINING

Meters remaining of fuel and charge.  Range remaining shall account for all energy sources in a vehicle.  For example, a hybrid car's range will be the sum of the ranges based on fuel and battery.

[SebastianSchildt]

I fell as avid PHEV fan @chheis has an opinion about this (I remember I once discussed this with him)

Vehicle.Powertrain.Battery.Range Vehicle.Powertrain.Range

sound sensible to me