Category: PTV Developer
-
Dirt roads instead of highways?
Highways are not always the first choice for a routing. For example when it comes to farming, not all agricultural vehicles are built for highways. They are designed for rugged fields, not for speeding down the highway. While they might be kings of the countryside, these vehicles are better suited for dirt roads.…
-
Speed up or slow down
Distance and driving time are key characteristics for a route. While the distance is relatively static to calculate, many factors influence the driving time: The used vehicle, speed limits, typical traffic situations like rush-hours, live traffic situations like traffic jams, …
We try to provide the most realistic driving time possible, but it is not out of the question that the calculated driving time could differ from reality.…
-
Does my route pass a delivery-only road?
For delivery-only roads general traffic is restricted, but delivery vehicles are allowed to deliver goods to local businesses or residents. A typical example is a pedestrian zone. As we consider a malus on these roads or zones, shortcuts and through traffic are avoided, instead they are only used when a waypoint located there is reached or left.…
-
Don’t you understand แบบไทย(thai)?
In the new version of the PTV Developer Geocoding & Places API V1.12.14 we added a new feature for the endpoints searchLocationByText, searchLocationByAddress and searchLocationByPosition.
It’s now also possible to return the latinised version of the default language if the language parameter is set to x-ptv-Latn-DFT.…
-
Electricity consumption even more accurately
Charging of electric vehicles takes much longer than refueling a petrol or diesel vehicle, at least until now. Therefore, it is very important to accurately consider all the factors affecting the battery. In the new version of the PTV Developer Routing API V1.29.0 we provide two new features for a more detailed modelling of the electricity consumption.…