Tag: Map Matching API
-
The left turn the driver never made
At a Paris intersection where a left turn is forbidden, a reconstructed trip shows the vehicle turning left anyway. Nobody broke the law. The driver took the legal route, exactly as they should have. It was the map matching that invented the shortcut, snapping the GPS trace through a maneuver that was never possible.…
-
From a coordinate to a country
A vehicle’s position arrives as a pair of numbers. Almost everything you want to do with it next depends on a single derived fact: which country is this point in? Bill a cross-border allowance, pick a toll scheme, log a frontier crossing, each one starts with the answer.…
-
One Trip, One Track: Closing the Ferry Gap in Map Matching
You’re sending a truck from Paris to London and would like to calculate the actual toll costs and emissions for the trip afterward. The GPS tracker recorded positions the whole way. You run those positions through track matching and instead of one continuous track, you get two separate pieces: a line through France, a line through England, and nothing where the Channel should be.…
-
Track Matching output now includes time stamp
In Version 1.7.0 of PTV Developer Map Matching API time stamps are supported in input and output.
This allows you to use the timestamp from the response for better toll calculation in the case of time-based tolls. You can easily get the “startTime” for each path and use it together with the “routeId” in the PTV Routing API to calculate the toll.…
-
Find out which vehicle can enter a low emission zone
The newest version of our Map Matching API version 1.4.0 now supports vehicle-based restriction information for low emission zones.
This information helps our customers to decide which vehicle can enter a low emission zone and when.
We added a new show case to see the new vehicle-based low emission zone information.…