PTV Developer Blog
Be part of the Community!
-
Clearer names for the Route Optimization API
If you plan tours with PTV Developer, you will notice new names in the documentation. We renamed our two route optimization APIs, so it is easier to see which one…
-
Reading a Route’s Climb Before You Commit
Two routes leave the same yard for the same delivery. One is eighty kilometres and climbs over a pass. The other is ninety-five kilometres and follows the valley. On a…
-
When 85 km/h is the wrong answer
A non-emergency patient transport van pulls onto the motorway carrying a passenger in a wheelchair. It will not do 85 km/h. It holds 60, steadily, because that is the speed…
-
Names before numbers in reverse geocoding
Tap a tracked vehicle on a stretch of the Kriegsstraße in Karlsruhe and ask what address sits there. The honest answer is two things at once: the street name, Kriegsstraße,…
-
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…
-
Why a messy address used to be slow to geocode
Real address data is rarely clean. A single field arrives carrying a recipient’s name, a depot label, and a phone number, all crammed in beside the actual street and postcode.…
-
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?…
-
A place that was really just a street
A user enters a postal code and receives a list of locations. Most of them are obviously correct. One of them is a location with a postal code that doesn’t…
-
When you want routing to ignore the clock
There is an assumption built into most routing requests: that a good travel time reflects the moment of travel. Rush hour is slower than midnight; a usual Tuesday is slower…