PTV xServer 1.24 now available

Our new PTV xServer 1.24 release is available NOW!


Besides several Bugfixes, Improvements and some Features, the Highlights of the 1.24 Version are:

PTV xRoute Server: With the new xRoute 1.24, the time zone of the start and destination point of a route is determined automatically if no time zone is set.

PTV xMap Server: Several displaying improvements and some new icons.

PTV xTour Server: As an additional vehicle restriction you can set the maximum distance per tour. With this you can plan tours for example with electric powered vehicles with a maximum reach.

See the 1.24 Release Notes for more details.

The PTV xServer 1.24 can be downloaded from the customer area Downloadof the PTV Developer Zone. If you need further information or support please contact the Support Team.


PTV xServer 1.22 – out NOW!

Our new PTV xServer 1.22 release is available NOW!

Highlights of the new 1.22 Version:

featurelayerPTV xServer: With the upcoming Europe City Map 2016.2 we will introduce a new Feature Layer Truck Waiting times. This first version will include the waiting times at toll booths. As soon as the Feature layer is available you can use it for predictive routing and display the waiting times in the map.

Toll ScenarioPTV xRoute Server: With the new xRoute 1.22, the Belgium Toll valid from 01.04.2016 can be calculated respecting the three different toll regions. The NGA emission factors for Australia are updated to the 2015 version. There is a new way for exception path input using an intersecting line.

PTV xMapMatch Server: Improved global matching by when driving PTV xMapmatch Serverwith low speed, comming from off-road or when the GPS tracks ends.


At thiWebinarss point we would like to inform you of our Webinar taking place March, 3th 2016 where we will demonstrate the new features of PTV xServer 1.22.

Missed our Webinar? Recording is available now

1.20.1You missed our webinar about the PTV xServer 1.20.1 release?
You want to know more about PTV xTerritory and Emission Calculation? You want to see some fancy demos?

Have a look at the recorded session:

IMG_0260Thanks to all attendees! If you have any further questions. Don’t hesitate to contact us.

If you haven’t seen it yet, there were also two Blog Post Series about the topics PTV xTerritory and Emission Calculation, here on our Developer Blog. Have a look…

PTV xTerritory 1.20.1 Blog Series #3 – Consider incompatibilities of locations and territories

xTerritory-Server-Icon_Puzzleteil-grau_64pIncompatibilities ensure that certain locations are kept separate to certain territories during the location assignment. A typical use case are sales representative that should not serve certain customers or field worker with specific qualifications. So an incompatibility is a property that disqualifies a location for certain territories.

Needs and Benefits

To distribute locations with incompatibilities a PTV xTerritory Server has to be installed and if applicable, a High-performance routing network for calculating routes. With these prerequisites you have the possibility that during the distribution of locations to territories, incompatibilities between locations and territories can be taken into account.This enables you to depict real customer relationships during the planning process. The incompatibilities have to be set as properties in the locations.

WebinarsThere is also an use case documentation for this new feature available. This was the last post of our PTV xTerritory Blog Series and if you want to know more about the PTV xTerritory features and also about the other new features of the PTV xServer 1.20.1 release I recommend you to join our webinar that will be presented on Tuesday. During the webinar you have the opportunity to ask your questions that you might have after the blog series or you maybe will get in the webinar.

Further information about all PTV xServer you can find on our product site.


PTV xTerritory 1.20.1 Blog Series #2 – Activity limits for territory planning

xTerritory-Server-Icon_Puzzleteil-grau_64pIn our last post we indicated that activity limits can have a major impact on the tour estimation by setting for example TourPeriodLimits for each territory. By setting activity limits in general you ensure that the sum of all its activities is roughly constrained. Because a territory can only have exactly one limit assigned, the entire territory will be limited by this single constraint on the basis of the sum of all its activities. Having multiple limits constraining one and the same territory is therefore not possible. Furthermore one limit has to be uniquely assigned to one territory.

Why is this useful?

  • Limits give more fine-grain control over the calculation process during territory planning, location assignment and change territories by optionally limiting the sum of activities within territories.
  • Limits constrain the sum of activities of territories (for each territory individually by a unique limit) to fit to individual site conditions or employee experience.

Activity limits when planning territories

The following sample scenario will help you to understand how territories can be limited right from their initial planning by using exact limit values.

  1. There are three existing locations, each given with the following activity values:
    • Location A: activity = 60.0
    • Location B: activity = 50.0
    • Location C: activity = 30.0

    This totals to an overall sum of activity of 140.0 for all three existing locations.

  2. Furthermore, the number of territories to be planned (not yet existing) are: exactNumberOfTerritories = 3.
  1. Finally, the three activity limits (as many as exactNumberOfTerritories) that you want to be considered by the PTV xTerritory server for the three future territories are:
    • Activity limit for future territory I: maximumValue = 30.0
    • Activity limit for future territory II: maximumValue = 60.0
    • Activity limit for future territory III: maximumValue = 50.0

    All three activity limits must not carry any territory assignment, since there are no assignable territories yet.

Planning results
xTerritory Activity Limits

Since the limit values exactly fit the specified activity values, the expected result is that location A is assigned to territory II, location B is assigned to territory III, and location C is assigned to territory I.

There is also an use case documentation available if you need further information and additionally you can see the activity limits in our Code Sample Browser.

After getting to know about the activity limits of the PTV xTerritory Server, you will get a glance at considering of incompatibilities of locations and territories in the next post of our blog series tomorrow.


PTV xTerritory 1.20.1 Blog Series #1 – Tour Estimator

xTerritory-Server-Icon_Puzzleteil-grau_64pWith the PTV xServer 1.20.1 Release the PTV xTerritory provides now a quick way to estimate the route travel times within a territory. And this without using the PTV xTour Server.

Different periods

The output format (time in seconds) can be split in service period and driving period. The service period is the activity value of a location interpreted as time in seconds spent for providing service by an employee at a particular location. A driving Period is the server calculated time from one location to another within a territory. It is estimated by the average distance to a location’s nearest neighbouring locations.                                          The estimated driving time from a territory’s center to the territory itself is the average distance to the territory center’s nearest five locations.

Why is this useful?

  • It is very difficult to consider driving periods between locations and service periods at locations in the tour estimation for exactly one territory. For this reason tour estimates on basis of the PTV xTerritory Server are helpful to plan better calculated tours with the PTV xTour Server. So it can be regarded as a prior step for a more fine-grained tour calculation by the PTV xTour server with many more parameters.
  • The PTV xTerritory Server is able to interpret activity values as service periods. For example you can use the activity value as a service period for a service employee who provides at certain service at a location or for a truck driver who unloads certain goods at a location.
  • The PTV xTerritory server allows constraining tour periods by setting a single TourPeriodLimit for each territory. With this, a service tour period can be limited to, for example 8 hours of a typical work day.

How it works

tour_estimationEstimating tour periods for territories is a concept by which activity values of locations are interpreted as service periods, e.g. working hours of a service employee, and driving periods between locations are summed up. This sum then represents an estimated round trip time for a tour through all locations of a territory. This concept provides the basic mechanism for planning, distributing and changing territories according to a tour estimate. It can be regarded as a prior step for a more fine-grained tour calculation by the PTV xTour server with many more parameters. In general, for an estimate of a round trip tour period within a territory, service times and driving times are the only time contributions that are considered. The driving period from a territory center to the territory itself is not considered by the PTV xTerritory’s tour estimation. Nonetheless, this particular driving time is provided within the territory summary as additional value.

Tour estimation and activity limits

Setting limits with the PTV xTerritory server is possible for each territory and the three use cases: territory planning, location assignment and change territories.                       Limiting the duration of a tour period for a territory can have a major impact on the calculation results in all use cases. However, when limits are applied, it can become impossible to find a valid calculation result. If this occurs, more reasonable values for the limits themselves or other planning parameters within the planningProfile need to be considered.                                                                                                                           For further information of activity limits read the next post of our PTV xTerritory 1.20.1 Blog Series.

Additionally to this post you can read its use case documenation here.