362 results have been found
Vehicles
/en/documentation/route-optimization-optiflow-api/concepts/vehicles
Without a vehicle, nothing can be transported. This is why an optimization request is required to contain at least one vehicle. They can be customized in various ways by specifying a routing profile, enforcing constraints and defining costs. While vehicle …
Locations
/en/documentation/route-optimization-optiflow-api/concepts/locations
Locations play a crucial role in efficient route planning, directly impacting travel efficiency and resource utilization. They represent geographical points, encompassing a variety of destinations. Places where orders are picked up or delivered. This can …
Resources
/en/documentation/route-optimization-optiflow-api/concepts/resources
Some vehicles cannot operate on their own but rather depend on additional shared assets to execute their routes. These assets are called resources . A resource can represent anything such as a driver, trailer or a specialized piece of equipment. The …
Orders
/en/documentation/route-optimization-optiflow-api/concepts/orders
An order is a request to either transport goods consisting of a pickup and a delivery task or provide a service at a specific location. The main goal of the optimization is to effectively schedule these tasks onto routes. We differentiate among four types …
Routes
/en/documentation/route-optimization-optiflow-api/concepts/routes
The primary objective of the optimization is to effectively allocate tasks to routes. As such, a route is a sequence of tasks, assigned to a vehicle. The efficiency of routes is gauged by metrics such as the total drive duration, the count of scheduled …
Cookies (LO) (EN)
/en/cookies
Manage your Cookie Preferences When using our website, so-called cookies may be used. These are small text files that are stored on your end device (PC, smartphone, tablet, etc.) When you access a website, a cookie may be stored by your browser. This …
Constraints and Rules
/en/documentation/route-optimization-optiflow-api/concepts/constraints-and-rules
Constraints and rules play a crucial role in establishing relationships between various entities like vehicles, orders, tasks, and depots within the optimization process. They define specific limitations or conditional modifications that need to be taken …
Clean Input (experimental)
/en/documentation/geocoding-places-api/concepts/clean-input
Challenge Some customers need to geocode address data containing additional information that is not available in the map data. Some examples can be seen here: Tel. avis Hr. Max Mustermann:0123-456789 Im Klapperhof 1, 50670 Koeln 15 School St, Woods Hole, …
Optimization
/en/documentation/route-optimization-optiflow-api/concepts/optimization
The optimization process involves refining a solution through repeated cycles of continuous improvement . The algorithm starts by generating initial routes or reconstructing the routes provided in the input . After which, through a series of iterations, …
FAQ (Help)
/en/help/faq-help
You need to sign up for a PTV account and then activate your free subscription of PTV Developer. If you already have a PTV account, you can directly activate your free product . No payment details are needed to activate your free product. … No. Every …
Depots
/en/documentation/route-optimization-optiflow-api/concepts/depots
When an optimization needs to schedule the execution of pickup or delivery orders, the delivery (resp. pickup) task needs to be executed at a depot. Therefore, at least one depot needs to be specified when the optimization request contains pickup or …
API Changes
/en/documentation/sequence-optimization-api/api-changes
API Changes … This list shows all changes of the API between releases like new features, significant improvements and bug fixes. We recommend that API developers periodically check it for …
Places by Text
/en/documentation/geocoding-places-api/concepts/places-text
Allows searching for places (i.e. addresses of businesses and services) matching a name given by a single text field. … Input The places by text endpoint considers the following input fields: Input Field Description searchText (required) A free-form text …
Places by Area
/en/documentation/geocoding-places-api/concepts/places-area
Allows finding places (i.e. addresses of businesses and services) in a given area. Input The places by area endpoint considers the following input fields: Input Field Description area The area which is searched for places. It is given as JSON in the body …
Locations by Position
/en/documentation/geocoding-places-api/concepts/locations-position
Allows finding locations (i.e. localities, postal codes, streets or houses) near a given position. Input The input parameters of the Locations by position endpoint are latitude and longitude (WGS84) of a geographical position, given as path parameters. To …
Which Endpoints Are in the Geocoding API and Which One Should I Use?
/en/documentation/geocoding-places-api/concepts/endpoints-explained
The Geocoding API Offers the Following Services: Find locations matching an address to get their geographic positions, with a single address string ( Locations by Text ). with separate input strings for each address field ( Locations by Address ). Get …
Help
Support and Contact
Check our FAQ Within the FAQ you will find questions and answers from account creation to rate limits. FAQ … Ask on Stackoverflow Want to be part of the community? Ask your question on Stackoverflow. Make sure to tag your questions with the tag …
PTV Developer
PTV Developer (Home)
OptiFlow route optimization algorithms now available as API NEW and available now – Integrate our superior & high-performance route optimization algorithms directly into your platform and enhance it with cutting-edge technology designed for developers, by …
Segment Attributes
/en/documentation/map-matching-api/concepts/segment-attributes
Segment attributes describe the physical and legal characteristics of road segments returned by the MapMatching API. These attributes provide additional context for interpreting the matched segments, such as whether a segment is part of a bridge, located …
Profiles and Countries
/en/documentation/route-optimization-optiflow-api/concepts/profiles-and-countries
Profiles and Countries | Route Optimization API Documentation | PTV Developer European profiles Profiles Description Supported traffic modes EUR_TRAILER_TRUCK Typical 40t semi-trailer truck (Euro-tractor) with 5 axles consisting of tractor with 2 or 3 …
Terms & Privacy (EN)
/en/terms-privacy
General Terms and Conditions General Terms and Conditions (PTV America) General Terms and Conditions (PTV UK) Data Privacy Statement Websites Data Privacy Statement Communication Data Privacy Statement Interested Parties & Customers Code of Conduct … …
Time-Dependent Matrix
/en/documentation/matrix-routing-api/concepts/time-dependent-matrix
Matrices are often calculated based on an average traffic situation. But, with the following options, it is possible to get more precise values: trafficMode startTime duration The following usecase are handled, depending on the combination of these …
Waypoints
/en/documentation/routing-api/concepts/waypoints
The Routing API supports different waypoint types and attributes in order to support different use cases. … Waypoint Types By choosing the appropriate waypoint type the route will actually reach the location off the road, stop on the road close to the …
Feature List
/en/resources/feature-list
Explore the most important features of PTV Developer and find the API that fits your needs: Route Optimization, Geocoding, Routing, Map Matching, and more. Follow the link that is hidden behind the information icon 🛈 of the corresponding API to find out …
Relevant Terms
/en/documentation/route-optimization-optiflow-api/concepts/relevant-terms
The following terms are important to understand the whole use case. Appointment A sequence of tasks, scheduled to be executed respecting a specific time slot. Break A scheduled pause in a driver's or vehicle's operation, typically for rest, refueling, …