PTV Logistics Product Forum

What maplanguage parameter can we use to translate all languages to latin, e.g. russian, ukrainian, greek, etc.

E.g. with reverse geocoding we do not know at request time which country prefix (e.g. "-t-el") we need to use. So a "one for all" solution would be great.

Since yesterday approx. 13:00 we get errors when calculating routes via https://xserver2-europe-eu.cloud.ptvgroup.com/services/rs/XRoute/calculateRoute


Sending HTTP request POST https://xserver2-europe-eu.cloud.ptvgroup.com/services/rs/XRoute/calculateRoute

Status: 500
Response:
{"faultInfo ...

Let's say we don't want to add another API to our product, when can we expect to see matching functions in xServer API v2?

We have implemented the map matching functionality according to this use case: https://xserver2-eu-test.cloud.ptvgroup.com/dashboard/Default.htm#UseCases/MapMatching/UC_track_matching.htm?Highlight=road%20matching

But the request still throws an error 404. Can you tell us what the current status is ...

Many, many thanks for the great help. The axle load was indeed the problem.

Another remark. If truck attributes are enabled (second request in previous post), the route does not go through St Bernard Tunnel and therefore no toll is calculated:

Here the exact request produced by our software:

With toll returned:

{
"$type":"RouteRequest",
"waypoints":[
{
"$type":"OffRoadWaypoint",
"location":{
"$type":"OffRoadRouteLocation",
"offRoadCoordinate":{
"x":7.4404602694,
"y":46.948429118
}
},
"tourStopOptions":{
"serviceTime":0.0 ...

Unfortunately, our customer informed us, that the toll information is still not calculated. Now after a diagnose session with them we could isolate the cause: If we activate the truck attribute layer, the toll for St. Bernhard Tunnel is not calculated. If the truck attribute layer is deactivated it ...

Hello PTV,

I have another question today regarding xServer2 and routing. A customer has brought to our attention that transit traffic in Austria on the B 180 is closed for trucks over 7.5t, but can be used for origin and destination traffic if there are loading or unloading stations in the ...

Many thanks to all,

I can confirm that the toll for example Saint Bernard Tunnel is calculated for cars in our case. I will ask the customer if maybe the vignette calculation is missing. Was this vignette calculation perhaps included in the MapServer and is no longer shown by xServer2?

Hello Bernd,

thank you very much for your response. Unfortunately, our problem is not about a 40t Truck. We get standard toll costs for that.

It is about a PKW and the extra tolls which were calculated in MapServer, and are now missing in xServer 2.


{
"$type":"RouteRequest",
"waypoints ...

When we calculate the toll for the route of a car in the old MapServer, so-called extra toll and named toll is calculated for Switzerland (standard toll is empty).

When calculating the route with xServer 2, no toll is returned at all for Switzerland. We set ResultFields.Toll to { Enabled = true ...

I would like to add here that also our customers are used to receive a number of results with different postal codes when searching for an address, e.g. by entering a city, which contain many (or even all) of the existing postal codes in the searched city.

With XServer2 it is the case that only one ...

a route will still be calculated if Course.Violations.Enabled=true is specified in the routing profile

This is not correct. When you set prohibitedCountries the engine will no load map data for these countries. In other words: as far as the engine is concerned that country does not exist for the ...

We are using the XServer2 calculateRoute operation and have the following problem:

If, for example, prohibitedCountries=["CH"] is specified in the GeographicRestrictions and the route contains an arrival stop within this prohibited country, a route will still be calculated if Course.Violations ...