Traffic events

Do you remember the traffic delay introduced in one of the last versions of the PTV Developer Routing API? For the delay we compare the travel time with and without live traffic on the same route (see this blog post).

In the new version of the PTV Developer Routing API V1.11.0 the request parameter ‘TRAFFIC_EVENTS’ provides traffic events chronologically along the route in the event list, together with all other events like waypoints, maneuvers or toll (see this concept). Then you know exactly where and why there is a delay.

Check out the traffic events in the code sample for recalculating a route with events. Do you need a RouteId? Just create one with the code sample for RouteIds.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Guided navigation

With guided navigation you have the possibility to use a calculated route from PTV Developer in our truck app PTV Navigator. For this we offer in the new version of the PTV Developer Routing API V1.11.0 the request parameter ‘GUIDED_NAVIGATION’ to get the calculated route in an additional format easy to import in PTV Navigator.

Detailed information is available in the corresponding concept. In addition you can test it in our new code sample!

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Release of Area POI Search

In the new version of the PTV Developer Geocoding & Places API V1.4.0 you  find a new Feature for the POI / Places Search.

The new endpoint is named searchPlacesByArea and enables you to find places in a map view, around a route or in more complex constructs like multiple polygons. 

You can use a GeoJSON string as input. Which enables you to use complex gometries like multi polygons or polygone with hole.

Try out code sample which gives you the possibility to see results out without any effort. The code sample allows you to manipulate the sqare as you wich.
You have also the possibility to select categories to filter your results.

...
"address": {
"countryName": "United States",
"state": "District of Columbia",
"postalCode": "20005",
"city": "Washington",
"district": "Downtown",
"street": "Vermont Ave NW",
"houseNumber": "1029"
},
"formattedAddress": "Stan's Restaurant - 1029 Vermont Ave NW, Washington, DC 20005",
"name": "Stan's Restaurant",
...

If you need more information about this new Feature please have a look at the API documentation or at the concept wich describes the purpose of this feature in detail.

You can test PTV Developer for free by registering a MyPTV account and activating the product on the website.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.

Release of Map Matching API V1.3.6

Since we first released our PTV Developer Map Matching API there were a lot of improvements in the API.
All new features and improvements are listed in the API changes.

Today we like to introduce you to the highlights of the latest release of PTV Developer Map Matching API V1.3.6:

  • Feature: Providing segment attributes like bridge, tunnel, speed limit, etc. for a single matched GPS position.
  • Feature: Providing segment attributes like bridge, tunnel, speed limit, etc. for a complete matched GPS track.
  • Improvement: The preferred default languages used to return the result attributes ‘countryName’, ‘city’ and ‘street’ depend on the region of the matched segment instead of the complete country.
{
"latitude": 37.799984608,
"longitude": -122.43496504,
"segmentGeometry": "{\"type\":\"LineString\",\"coordinates\":[[-122.43506078,37.799970422],[-122.43436873,37.800072952]]}",
"matchDistance": 2,
"segmentLocationDescriptors": {
"countryName": "United States",
"city": "San Francisco",
"postalCode": "94123",
"street": "Lombard St/US-101"
},

"segmentAttributes": {
"bridge": false,
"tunnel": false,
"ramp": false,
"frontage": false,
"paved": true,
"requiresFourWheelDrive": false,
"privatelyManaged": false,
"publicAccess": true,
"parkingLot": false,
"priorityRoad": false,
"builtUpArea": false,
"speedLimit": 48
}
}

You can test PTV Developer for free by registering a MyPTV account and activating the product on the website.
To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.

Release of Route Optimization API V1.4.0/1.4.1

A new version of the PTV Developer Route Optimization API is now available!

You can check the new features in the list below or use the API Changes webpage for more details.

Route Optimization API V1.4.0

  • Feature: Added functionality “alternative capacities” to specify different options for the capacities.
    Therefore added fields ‘alternativeCapacities’ and ‘capacitiesChangePosition’ to ‘Vehicle’.
  • Feature: Added functionality “Drivers’ Working Hours” in order to  specify restrictions on working time and driving time of drivers and enforce breaks and rest periods.
    Note: From this release on, the working and driving time will be unlimited, unless specified otherwise. Previously, EU driving time regulations were applied as the default. To achieve the same behavior as before, set workingHoursPreset to EU_DRIVING_TIME_REGULATION_FOR_SINGLE_DAY or EU_DRIVING_TIME_REGULATION_FOR_MULTIPLE_DAYS depending on the planning horizon. 
    Note: Currently all drivers must have the same rules specified, setting them differently will be available in a later release.
  • Feature: Added functionality for restricting the maximum travel time and driving time of drivers. Therefore added fields ‘workLogbook’, ‘maximumDrivingTime’ and ‘maximumTravelTime’ to ‘Driver’.
    Note: From this release on, the travel and driving time will be unlimited, unless specified otherwise. Previously, EU driving time regulations were applied as the default for plans with a single day horizon. To achieve the same behavior as before, set maximumDrivingTime to 32400 (9 hours), and maximumTravelTime to 46800 (13 hours).
    Note: Currently all drivers must have the same maximum value specified, setting them differently will be available in a later release.
  • Documentation: Added concept for alternative capacities
  • Documentation: concept for Drivers’ Working Hours will be added on Monday

Route Optimization API V1.4.1

  • Bugfix: When using an empty list of quantities a proper response instead of an error is returned.

You can test PTV Developer for free by registering a MyPTV account and activating the product on the website.
By doing this you will gain 100k transaction per month for free to directly start testing.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.

Release of Route Optimization API V1.2.7

A new version of the PTV Developer Route Optimization API is now available!

You can check the bugfixes/improvements in the list below or use the API Changes webpage for more details.

Route Optimization API V1.2.7

  • Bugfix: When using coordinates where no street is available and no airline distance can be calculated, a proper exception message is returned.

Route Optimization API V1.2.4

  • Improvement: Improved calculation time for small requests.

You can test PTV Developer for free by registering a MyPTV account and activating the product on the website.
By doing this you will gain 100k transaction per month for free to directly start testing.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.