SpeedForLinkDistance and HPR handling
Posted: Wed Jan 22, 2025 1:01 pm
Cheers,
these days I've been asked for the handling of speeds in xServer2. Roughly spoken the static speed approach is based on the following attributes within com.ptvgroup.xserver.vehicleprofile.Speeds
So it depends on how the transaction identifies the HPR in charge:
Bernd
these days I've been asked for the handling of speeds in xServer2. Roughly spoken the static speed approach is based on the following attributes within com.ptvgroup.xserver.vehicleprofile.Speeds
- speedRangesByNetworkClass (maximumSpeeds and minimumSpeeds)
- maximumSpeed
- speedForLinkDistance
- Left: implicit usage of an HPR: depending on the requests effective profile a matching HPR is searched
Right: explicit HPR usage - the desired HPR is identified ny it's unique ID. In this case the request can not contain further routing options / request profile options such as the speedForLinkDistance
- With the explicit HPR ID the underlying HPRs have to be recalculated if you want to "change" the speedForLinkDistance - though there are no waypoints available in the process of the HPR creation.
- With the implicit approach you need to know that the speedForLinkDistance is not a relevant property for the "matching process" which searches a valid HPR based on the effective profile gathered at runtime.
Bernd