one of my counterparts is interested in the routing polygon that is logically applied when Drive&Arrive has computed a new ETA internally and triggers the subscription. As far as I know neither the drivers current position is available for the consumers of the latest ETA nor is the polygon.
Is this corect?
So the player wants to create a standard routing call (current xy to next destinations xy) towards the PTV xServer Internet. Is it possible to use an equal parameter set? What would he have to consider to be as close to the internal route as possible?
At least it makes sense to consider PTV_TrafficIncidents (and further data layers such as PTV_SpeedPatterns)):
Code: Select all
<requestProfile>
<featureLayerProfile><themes id="PTV_TrafficIncidents" enabled="true" />
</featureLayerProfile><routingProfile></requestProfile>
Bernd