Ok Thank you...I'll get in touch with the support asap.Asterix wrote:Hello G.,
As this requires some 1:1 handling I recommend to get in touch with support.
Best regards from Paris,
Bernd
Have a good day
Gianni
Ok Thank you...I'll get in touch with the support asap.Asterix wrote:Hello G.,
As this requires some 1:1 handling I recommend to get in touch with support.
Best regards from Paris,
Bernd
When you say that "an average time on an average Tuesday", how many Tuesday were considered? How long have traffic information been recorded?Asterix wrote:Hello Norbert,
the answer is a bit "grey": depends on what kind of impact you expect from the response:
I assume you refer to "considering additional data in the request". Now here's a quick overview which additional source could help with which contribution:
OK, this was the more detailed answer and I'm aware that this is probably not what you want to have. But it is the current situation.
- FeatureLayer PTV_SpeedPatterns, PTV_TruckSpeedPatterns (based on historical traffic information): if used in the request we determine the day of the week of the routing context, e.g. tuesday. Then we apply the traffic conditions that were given on "THE TUESDAY data" in combination with the time. This does not consider the conditions of a specific TUESDAY but is more heuristic, some kind of an average time on an average tuesday
- FeatureLayer PTV_TrafficIncidents (used to be TrafficInfoLoader, based on LIVE traffic info, updated every XX minutes): as this info is updated quite often the traffic condition few days ago is gone and no longer part of the current file (or database) content.
- Custom RoadEditor layer (content maintained by the customer within MAP&GUIDE RoadEditor): well, that's tricky. Depending on when and how you maintain the data it might be possible that using this data sources information reflects the street conditions at a specific point in time (the past). But this is outside the scope of PTVs maintenance
Best regards
Bernd