PTV Group - Logistics Forum

We have implemented the map matching functionality according to this use case: https://xserver2-eu-test.cloud.ptvgroup ... 20matching

But the request still throws an error 404. Can you tell us what the current status is? Customers are asking about it regularly. We ported almost everything from MapServer to xserver2, but this is still missing.

Kind regards,
Andreas Schönebeck
ESYS GmbH

Hello Andreas,

Carolin and I will get back to you 1:1...

Best regards,
Bernd

Cheers,

if it is urgent I recommend to check the new Matching-API within PTV Developer!
This API offers
- matchPosition
- createMatchedTrack + getMatchedTrack
- deleteMatchedTrack

Though the core concept is a little bit different the usecase is what matching means.

Best regards,
Bernd

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?

Using PTV Developer with the async methods is a paradigm shift, but you as a Mapserver user do also used async methods for the Mapserver route calculation for example like IRouteLister::CalcRouteExtended.

We already had an abstraction layer for the xServer access and the code in our application does use this layer. Changing the implementation of the Match method or better to say deriving a new client class from the existing xServer 2 class, that overrides the Match method, was not a really big deal. The Match method of the xServer 2 + PTV Developer Hybrid class does the following:
- check if the xServer 2 supports Map Matching
(XRuntime::getRuntimeInformation -> serviceInformation -> check if licensed and active are true for XMatch)
- if yes, call the inherited method
- if not, call the the new method that is using the PTV Developer Map Matching methods

Most of the work is required for the basics like class creation, getting used to PTV Developer and handle the additional settings / licensing information.

Hello Uwe,

sounds like you managed to connect to PTV Developer's Matching API - thanks for the feedback.
In fact I spend more time in "how to establish connectivity to a new (but of course modern) protocol with async methods?" than I need for the parameters and intrepretation of the response.

So the info for Andreas is: please check the PTV Developer API - don't be scared

Best regards,
Bernd

Quick update from Product Management:

The map matching interface of PTV Developer is almost equal to PTV xServer2 and can be used without additional costs.
Therefore developers can use the new Developer API's matching approach without any additional costs.
There's no obstacle that prevents a user from using the new API and therefore we will not activate xMatch in xServer Internet 2.