A Technical introduction into PTV xServer internet for cloud developers.
“Which info would have prevented me from a lot of painful experiences and do-it-again‘s?“ Registration required before July 28th, free of cost
– What do we offer from a technical perspective? Which protocols and client environments are supported?
– How is the authentication established?
– Where to find which information? How to understand the documentation?
– Which modules are available and what is their functional scope?
– Why to communicate via asynchronous protocol?
– Sample application C#
Who should participate:
– Developers who are new in the topic Who should not participate
– Developers who are already familiar with PTV xServers : you will only see things you are familiar with
– Deciders : at this stage you should be aware of our capabilities (forward it to your teams!)
We provide this webinar in German and English:
German: Dienstag, 28. Juli 2020, 14:00 – 16:00 CEST
English: Wed, Jul 29, 2020 2:00 PM – 4:00 PM CEST
From the beginning of time PTV included Oracle JAVA Runtime Environment (JRE) in xServer. Oracle now changed its license policies and any updates for commercial use are only available with a paid subscription.
This marks a severe change for PTV especially in the xServer context. We want to be as flexible as possible and want to provide our customers a reliable, easy to maintain product.
Our learning from this was, we don’t want to be dependend on one particular JRE provider, but rather work with standard functionality, which is fulfilled by a number of providers.
What will happen?
Starting with the upcoming xServer Versions 1.28 and 2.12, PTV will not ship a JAVA JRE within its xServer products anymore. Instead it relies on a JAVA JRE provided by the operating system environment.
What are the advantages?
- PTV Customers are not limited to a specific JAVA distribution – reducing potentional license fees.
- You might just use an already installed JRE – reducing the number of JAVA Versions running on your System.
- The Server can install security updates for JAVA independent of xServer releases keeping your system security up to date.
What will NOT change?
- xServer will work just the same – it still uses JAVA to provide its services.
- xServer Internet will take care of that issue for you.
- Your integrations doesn’t need any ajustments and will still work and react the same.
- The xserver performance will be comparable to an integrated JRE – no change in any direction is to be expected.
Things to consider
- Since a JAVA RE is an additional xServer system requirement, you need to take care of that – just like any other JAVA depending software. But we worked hard to make it as simple as possible.
For more help and advice, contact firstname.lastname@example.org.
Dear Customer, Dear Partner,
we would like to inform you that we will perform a maintenance on the network environment. Beginning on Friday, May 12th until Sunday, May 14th. During this period the following systems/services may be temporarily unavailable.
Thank you very much for your understanding and cooperation.
With the Europe City Map Premium 2016.2H we introduced a new roadtype “Unpaved roads”. Because this roadtype is not known by the old renderer (xMap 1.20.1 and earlier) these roads will be displayed in bright green.
Workaround to change the colour of these roads
You need to edit the profile file. Depending on your used profile it is silkysand.ini, sandbox.ini or gravelpit.ini in your xMap or xServer /conf/ Folder.
Unfortunately the classic Profile is hardcoded and can not be edited manually.
must be changed to:
Alternatively you can download configuration files of the 188.8.131.52 version here and copy them to your conf folder, overwriting the existing ones.
The Belgian government introduced a complete new toll system. Usually, toll sections for dedicated way points are defined by the authorities. Each toll section does have a defined length. In case of exact toll cost calculation, those sections do have dedicated tariffs attributed. In case of average toll, the length of all routed toll sections would be multiplied with the costs per kilometre.
But for both types of toll calculations, it was not relevant on which map or map version this calculation was performed. The toll sections were fixed and as said therefore the length defined.
The new Belgian toll deviates from the known methods.
For the Belgian toll calculation the toll sections are divided into toll segments and these are added up and multiplied with the toll costs per kilometre. With this, the Belgian toll system reflects an average calculation. But this means also that the calculation depends on the map basis and how the street segments are digitized. So new segments or even missing roundabouts will lead to different results. Also the different way of digitizing the street segments at the map providers will
influence the results
The calculation of the Belgian toll has been implemented with the last toll update in February.
- The new distance based toll is introduced on 1 April 2016.
- And will supersede the currently applicable time-based Eurovignette
- Vignette will be replaced by satellite-based OBU
- The tariffs depend on 4 factors:
- Actual distance travelled in kilometres
- Vehicle weight (over 3.5 tons and higher)
- Emission class
- Road type
The new Feature Layer Truck Traffic Patterns is now also available in the new PTV Europe City Map Premium 2016.1.T that was released recently.
A more detailed descripton about this Feature Layer and what you have to do to use it, you can find on our blog post How to use Feature Layer Truck Traffic Patterns. If you have any further questions about the Truck Traffic Patterns don’t hesitate to contact the Support Team