Routing user stories
Posted: Wed Sep 21, 2022 8:54 am
| Story | Generic/KPI determination (strategic) | Tactical Route | LiveETA | Reconstruction |
|---|---|---|---|---|
| Demand / Purpose | For a tender the KPIs are required. No concrete date of execution given | We want to drive soon in a potential period, e.g. next Friday or calendar week 42 | Vehicle is on the road - route happens "now". | Sequence of GPS coordinates is used to create a route object which returns estimated KPIs and maybe also shows violations performed by the driver. |
| PTV_TruckAttributes, PTV_RestrictionZones, PTV_PreferredRoutes | yes | yes | yes | yes |
| PTV_SpeedPatterns / PTV_TruckSpeedpatterns | false - no precise routing time context is known |  | true | false |
| PTV_TrafficIncidents | maybe | yes | yes | maybe |
| TimeConsideration | TollOnly | TimeSpan (Performance: try to use a short period, e.g. one day, one week) | ExactAtStart | ExactAt... with known value, e.g. first or last GPS timestamp |
| Violations | maybe | maybe | maybe | true |
- I sometimes added a "maybe" into the columns. This is because I can't simply give the same advice under any circumstances. It might be helpful to discuss your expectation with us. What you could keep in mind: you might want to send an iteravite sequence of routings to the API, e.g. first call with "violations disabled" (returns a legal route, performance is high) and if that one fails you could send a second transaction with "violations enabled". In such a scenario I'd not recommend to apply "violations==true" with any transaction because this could have a negative impact on the routes in terms of legal constraints.
- PreferredRoutes: if you apply this layer you need to ensure that you also specify the relevant PreferredRouteTypes to be considered (e.g. only BK_4 for some swedish road categories) and you have to provide a proper value for the PreferredRoutePenalty (as part of the FeatureLayerProfile).