PTV Group - Logistics Forum

Download: https://github.com/ptv-jcl/XMapmatchTestClient

I'll use this thread to inform people about my test client. leave your feedback in the thread and then I can see If I can incoprorate it into the client.

Map Legend:
Blue dot: input GPS point
Black line: heading of the selected input GPS point

Green dot: matched location, no speeding detected
Orange dot: matched location, little speeding detected
Red dot: matched location, speeding detected

Purple line: route reconstruction using xRoute
(not shown) blue line: route reconstruction using the path of xMapmatch

Screenshots:

https://www.dropbox.com/s/u4mfets8dkte3 ... 140513.zip

Added ability to load data from NMEA log file
Added ability to filter out NMEA loggins to a more reasonable polling interval
Output points are colored based comparisys between driven speed and speedlimit

https://www.dropbox.com/s/uxp2wj0spp2py ... 140709.zip

Fixed issue with NMEA parsing on western hemisphere
Fixed issue with NMEA parsing where interval filter was not properly filtering if there was no valid input within the interval (for example a long time no input when you drive threw a tunnel)
Added small black line for visualizing the heading of input points, currently only visualize the selected input point

Updated initial post with map legend and screenshots

Hi Joost,

du you have a working download link for the Client?

With kind regards
Ellen

I moved the project over to github:

https://github.com/ptv-jcl/XMapmatchTestClient

I added a new function to the test client: "Route sanity check". This function is useful if you want to send xMapmatch results to xRoute and you signal as such a high interval that you cannot use HistoryConsideration (aka global matching). if you do not have HistoryConsideration the chances of xMapmatch picking the wrong result will increase. "Route sanity check" will evaluate the map match result and only send points it is fairly certain of that they are OK to xRoute for a route calculation.

Hello Joost,

How about a report of the result quality, some diagram

• index, match probability
• matchProbability,count(*) group by match probability

Best regards,
Bernd

I updated the client. When you check "Make own timestamp" it will now calculate the timestamp based on the airline distance and average speed between 2 points. This now also works if you load data from a request instead of only if you load data from a CSV.

I made an update to the client.

BugFix: grid no longer remains empty when xMapmatch has found 0 matches or encountered an exception

New feature: added export button to export the data in the grid to CSV.
New feature: if the selected record in the grid has a matchedloctation, the segment which contains the match in the map wil be highlighted in red

Improvement: Route sanity check is now by default off. This post processing step is only useful if you do local matching. With the addition of AStar optimization to the crawler you should be able to use global mode now also for sparse track.