As of now the map/map-setup PTV Arabia City Map 2016 (HERE 2016.Q2) is released for the following products:
PTV Smartour 2016.2
Dynamic Traffic Information (TMC Tables) is available for Israel
Traffic Patterns FL is available for Israel
no RoadEditor Layer for Truck Attributes
Time Zones Feature Layer
Traffic Patterns Feature Layer
Preferred Routes Feature Layer
Truck Attributes Feature Layer
The Feature Layer content is included in the map-setup by default. You can get the other contents separately (e.g. via Product Management, Dev-Zone or product-setup).
Find general information about our PTV Maps and content here.
Our new PTV xServer 1.22 release is available NOW!
Highlights of the new 1.22 Version:
PTV 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.
PTV 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 with low speed, comming from off-road or when the GPS tracks ends.
At this 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.
Geocoding improvement: A new property is introduced which sets the number of leading characters that are not used for fuzzy search. Due to performance reasons, the first and second characters are not used for fuzzy search. So, typos in these characters are not handled by this search. If performance is not of major interest, the property NumberOfLeadingNonFuzzyCharacters can be set to 0 (or 1) to avoid this limitation.
Geocoding improvement: A new column erpMatchingLevel is introduced in the
result set of method IGeocode::FindCoordinates(). The corresponding value for
each result entry indicates the data level, which was responsible for finding
this result. For example, a matching level = 11 indicates a finding via road intersection
Common improvement: CodingInfo.ini used by the CodingTool object, is updated
by additional currencies (for example Mexican peso), and by removed legacy
currencies like Latvian Lats, which is replaced by Euro.