Comparison actual speed from gps track versus allowed speed

[LNM_PTV]

Hello!

Does anyone have a code sample in which the input are the GPS tracks including the actual speed and the output is a comparison between actual speed and allowed speed?

Thank you very much.

[Joost]

My test client from http://xserver.ptvgroup.com/forum/viewt ... p?f=8&t=12 does that.

[Bernd Welter]

Hi there,

Do we have a minimalistic sample for the usecase based on just 1 single coordinate per call?
The logical signature I need is somehow
- input: latitude, longitude (optional: timestamp)
- output: speedlimit for that vehicle category (at the given timestamp)

When I use matchPositions the API complains about "Not enough input positions for stable matching (at least six are needed)".

Do we recommend to use xMapmatch for that or is it better to work with additional content such as A2I/I2A tables or IDMapping and a more or less simple SQL query?

Best regards,
Bernd

[Joost]

xMapmatch can work single points, but then you need to make you have Mapmatching / HistoryConsideration / @enabled set to false in your profile. You can use the standard profile "local-matching" for this.

Do we recommend to use xMapmatch for that or is it better to work with additional content such as A2I/I2A tables or IDMapping and a more or less simple SQL query?

Actually xMapmatch can also work with the A2I/etc tables. If you use the matchPositions method and set the ResultListOptions.vendorId to true then in the result on the matched segment you can find the vendor ID with can be used to lookup the date in the L2S / SPL side tables.

The question is more should you take the effort to implement the side table lookup or just use the forwardSpeedlimit returned by xMapmatch?

The benefit of using xMapmatch directly is that xMapmatch has used the heading to select correct directional speed limit.
The benefit of using side table is that you get more information on conditional speed limits like weather or time dependent.