← cd ..

U-FEEL: road data for EV range

A backend that turns map data into drive-cycle files for truck energy simulation, and a comparison of 11 ways to measure a route, accuracy against speed.

Role
Engineering intern · master's thesis
Partners
Volvo Group · Scania · Chalmers · RISE · VTI
Year
01 – 06/2024, Gothenburg
Stack
Python · HERE Maps API · REST
U-FEEL conference poster on path-length estimation from geospatial data
The poster I designed for the SVEA conference.
Presenting the project objectives on stage
Presenting the objectives.

Context

The problem

U-FEEL is a range-estimation project for Volvo's electric trucks and cars, run by Volvo Group with Scania, Chalmers, RISE and VTI.

A range simulation is only as good as its route. Straight-line GPS distance ignores slope, curvature and elevation, so a hilly route looks shorter and cheaper than it is.

My part was the road data: a backend that builds deterministic Operating Cycle (dOC) files the simulation can run on.

Requirements

NeedWhy
AccurateOn flat and on hilly routes
FastSimulations run many routes
RobustReal GPS traces are noisy
ReusableOutput the simulation can load directly

Architecture

From coordinates to a drive cycle

Hover or tap any box for a plain-English explanation.

RouteGPS points HERE Mapsroad attributes BackendPython · clean, sort 11 methodsinterchangeable dOC generatordrive cycle file SimulationEV range
tipHover or tap a box to see what it does and why it's there.

The trade-off

Accuracy against speed

Three of the 11 methods, on the same routes. The test routes included the Stockholm Marathon, a Tour de France climb (Nice → Col de la Couillole), Lund–Malmö and Oslo–Bergen.

MethodError, flatError, hillyTime per route
Vincenty variant (chosen)0.008%0.10%~0.03 s
Geodesic with elevation–0.21%0.4 – 1.2 s
Haversine~0.31%~0.63%~0.005 s
  • Chosethe Vincenty variant for accuracy-critical simulation; Haversine only where real-time speed matters more than precision.
  • Testedrobustness by adding Gaussian noise (σ = 0.0001°) to the coordinates, to see how each method reacts to bad GPS.

Outcome

Where it landed

11
methods compared on accuracy and speed
0.008%
path-length error on flat routes
+25%
simulation efficiency
5
partners in the consortium
← Back to all work