About Hannah Esswein

Technical Product Manager for PTV xServer

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 Content Update Service available


Update your PTV Content Update Service now. The new release is available for download. It comes along with the following improvements:

  • A notified PTV xServer is checked frequently for restarts and is notified again if it has restarted.
  • Additional components may be notified on content changes (toll updates or feature layer changes).
  • The number of maximal reconnect attempts to the message broker of the PTV Layer Delivery Server is no longer limited.
  • The version of the PTV Content Update Service is returned in the result of the statusInfo rest call.

And several bugs have been fixed:

  • Toll update files from previous toll updates are not overwritten any longer to avoid file locking conflicts.
  • New toll updates are now identified in all cases by comparing the current version instead of the release date.
  • All kinds of exceptions occurring at servlet initialization lead to a fatal error.
  • If the hash value of a feature layer file changed on the PTV Layer Delivery Server, it is downloaded again.
  • HTTP connections are always closed.

The new PTV Content Update Service Release can be downloaded from the customer area of the PTV Developer Zone (login required).

In the PTV xServer Manual you can find a detailed description of the setup and configuration. Also have a look at our former Blog Post. If you need further information or support please contact the Support Team.

How to use Feature Layer PTV Traffic Incidents

PTV_TrafficIncidentsTogether with our PTV xServer Release 1.20, the new Feature Layer “PTV Traffic Incidents” was released. Didn’t try it yet? Here is all you need to know to get started.

What is it?

TI_scale_150Feature Layer add additional routing network and rendering attributes to a map. The Feature Layer PTV Traffic Incidents provides actual traffic information to consider incidents like traffic jams in the route planning. The information is provided as dynamic Feature Layer and can be automatically downloaded from the PTV Layer Delivery Server with the PTV Content Update Service plugin.

What do I need to use it?

  • PTV xServer 1.20
  • Installed and configured PTV Content Update Service
  • License: Each Feature Layer theme must be licensed separately and for each PTV xServer

Where can I get it?

The PTV Content Update Service can be downloaded from the customer area of the PTV Developer Zone (login is required). If you have installed and configured the service properly the traffic information data is automatically downloaded in your defined folder. Please contact your sales representative in order to get the corresponding license keys.

Where can I find information?

In the online manual of PTV xServer you can find documentation How to use Feature Layer PTV Traffic Incidents 

TI_scale_1000Just want to have a look?

Visit our Feature Layer Lab: http://ptv-logistics.github.io/fl-labs/

If you need further information or support please contact the Support Team.

Blog Series Emissions #summary

Emissionsberechnung_80x80Our Emission Wednesdays have come to an end. How did you like our blog series? Got an idea of emissions and their calculation with PTV xServer?

If you are interested in further information, we collected all important links for you:


On the 15th of September, there will be a Webinar about the new PTV xServer Release 1.20.1. There, we will also present the new emission calculation with COPERT Australia and UK DEFRA. Interested? Register now.

Any other information needed? Don’t hesitate to contact our Support Team.

Blog Series Emissions #3b Carbon Reporting

Emissionsberechnung_80x80In our last post you learned about carbon reporting with PTV xRoute and comprehensive approaches. Today, we focus on factor-based approaches and their calculation with PTV xRoute.

Factor-based approaches contain emission factors but no consumption values. Consumption values are chosen by the user and can be based on own average fuel consumption or different recommended consumption default values. See our post about emission standards for details. CEN and UK DEFRA are examples for this type of calculation approach.

What you need to have

  • PTV xRoute Server
  • PTV Map including the area where emissions are calculated
  • In case of calculation according to factor-based data approaches there is no specific data or license needed.

What you need to do

You need to send a PTV xRoute request for either the method calculateExtendedRoute or calculateAdvancedTour. The route must at least contain two waypoints and you have to specify the data standard type you want to use e.g. CEN_2012. Additionally, you set the consumption of your fleet or the expected consumption for the route as average or the current measured value. This is described in the proceeding sample request. As a result you receive the values for the available greenhouse gases supported by the standard.

Sample Request

In the PTV xRoute request you specify at least two waypoints and your vehicle routing profile. Set the cenVersion attribute in the ResultListOptions element according to the emission standard you want to use. Don’t be confused about the naming. Here, you can also choose other emission standards than CEN although it is called ‘cenVersion’. All comprehensive approaches will be set via this cenVersion even if they are not CEN. If you want to use CEN 2012, as done in this sample, set the cenVersion to CEN_2012.

"details": {
    "cenEmissionConfiguration": {
      "$type": "CENEmissionConfiguration",
      "fleetSpecificAverageFuelConsumption": "8.7",
      "cenVersion": "CEN_2012"
    "emissions": {
    "$type": "EmissionType",
    "emissionLevel": "BASIC"

The fuel consumption is also specified in the request within the “cenEmissionConfiguration”. There are three types of consumptions available which can be set in the request:CENEmissionConfig

In this example the fleet specific average fuel consumption of 8.7 l/100km is used.

The granularity of the emission information returned is handled the same like for comprehensive approaches. There are three emission levels available:

  • BASIC, if you only need the total emissions of the route
  • STATIONS, if you want to obtain the emission per part of the route
  • SEGMENTS, if you additionally want to obtain the emissions per Segment

In the sample request, the level BASIC is used. Therefore, the response contains the total emissions summed up for the entire route.

Sample Response

The listed values in the response depend on the emission standard. Have a look at the documentation for CENEmissions2011, CENEmission2012, CO2DecreeFrance2011, AustraliaNGA2011 or UKDEFRA2014 for detailed information.

The response of the sample request contains several sections:

  • The first general section “Emissions” with the values of the greenhouse gases
  • The second section “vehicleSpecific”: The emissions based on the vehicle specific fuel consumption. The fuel consumption of the vehicle is set by request or in the vehicle Profile.
  • The third section “fleetSpecific”: The emissions based on a fleet specific fuel consumption.
  • The fourth section “basedOnHBEFA”: The emissions based on the fuel consumption as it was calculated by HBEFA 3.1 or higher. The values based on HBEFA 2.1 will not be correct. If you do not want to calculate emissions based on HBEFA, use HBEFAVersion NO_HBEFA.

If you would have provided other consumption values for the route or the actual fuel consumption in the request, there would also be sections for their values in the response:

"emissions": {
      "$type": "Emissions",
      "hydrocarbons": 0.26766972687899987,f
      "methane": 0.02248425285899999,
      "hydrocarbonsExMethane": 0.24518547402000002,
      "carbonMonoxide": 15.616740881359998,
      "carbonDioxide": 4.230746730810099,
      "sulphurDioxide": 0.186552613168,
      "nitrogenOxides": 0.8886238383990003,
      "nitrousOxide": 0.053431981629999965,
      "ammonia": 0.5341401447849998,
      "benzene": 0.03460969095000001,
      "toluene": 0.02489327998599999,
      "xylene": 0.020610580044,
      "lead": 0,
      "particles": 0,
      "fuel": 1.3325186338024397
    "cenEmissions": {
      "vehicleSpecific": {
        "$type": "CENEmissions2012",
        "energyUseTank2Wheel": 66.26502399999997,
        "energyUseWell2Wheel": 77.58358399999999,
        "energyUseWell2Tank": 11.31856000000002,
        "co2eTank2Wheel": 4.9801664,
        "co2eWell2Wheel": 5.926809600000004,
        "co2eWell2Tank": 0.9466432000000041,
        "fuelConsumption": 1.5331504000000014
      "fleetSpecific": {
        "$type": "CENEmissions2012",
        "energyUseTank2Wheel": 72.06321359999998,
        "energyUseWell2Wheel": 84.37214759999998,
        "energyUseWell2Tank": 12.308933999999994,
        "co2eTank2Wheel": 5.415930960000001,
        "co2eWell2Wheel": 6.445405439999999,
        "co2eWell2Tank": 1.029474479999998,
        "fuelConsumption": 1.6673010599999993
      "basedOnHBEFA": {
        "$type": "CENEmissions2012",
        "energyUseTank2Wheel": 42.89876173256145,
        "energyUseWell2Wheel": 50.226189978806374,
        "energyUseWell2Tank": 7.327428246244928,
        "co2eTank2Wheel": 3.224068428347786,
        "co2eWell2Wheel": 3.836907881670089,
        "co2eWell2Tank": 0.6128394533223032,
        "fuelConsumption": 0.9925334624459093

In our PTV xServer Codesample Browser you can find some examples for emission calculation according to Factor-based ApproachesThere, the result is visualized like this:




  • PTV xRoute Server allows calculating emissions for the methods calculateExtendedRoute or calculateAdvancedTour
  • For factor-based approaches no additional data and licensing is required
  • In the request you specify route, vehicle type and emission standard type and for factor-based approaches the fuel consumption
  • As a response you receive the values for the available greenhouse gases supported by the standard as provided in the request for the given consumption value type: fleet, route or actual consumption specific.

An use case documentation can be found here. Please remember that UK DEFRA is only available with the new PTV xServer 1.20.1 release, which has just been released yesterday. With this, the use case description will be updated containing the UK DEFRA information and other improvements. Just take another look on the use case docu right now.

Further links:

BlogSeriesThis was the last post of our “Emission Wednesday Series”. We hope you did get an impression of emission calculation with PTV xRoute. A short summary of all topics will follow next week.

The updating continues: Toll Update France and Germany available

Not only our PTV xServer received an update, also our data content is updated. There is new toll data available for Germany and additionally an correction of the French toll.


  • Germany: Extension of tolls on secondary highways from ca. 1000 km to ca. 2000 km. Toll valid now for trucks above 7.5 t instead of 12.0 t. This scenario replaces the previous ‘Germany October 2015 v3’ scenario.
  • Germany: New tariff tables 15.2 (Bundesautobahnen, federal motorways), 4.2 (Bundesstraßen, federal trunk roads) with 1.100 km more. This scenario replaces the previous ‘Germany July 2015 v3’ scenario.
  • France: Corrections

Concerned maps

  • PTV Europe City Map Premium 2015.2T (Update 2)
  • PTV Europe City Map Premium 2015.2H (Update 5)
  • PTV Europe City Map Premium 2015.1H (Update 8)
  • PTV Europe City Map Premium 2015.1T (Update 8)
  • PTV Europe City Map Premium 2014.2H (Update 11)
  • PTV Europe City Map Premium 2014.2T (Update 10)
  • PTV Europe City Map Premium 2014.1N (Update 14)

It is possible to use the download from the customer area of the PTV Developer Zone or the automatic download with the PTV Content Update Service. For the PTV Mapserver please use the current version of the PTV Toll Update Tool.

If you need further information or support please contact the Support Team.