FAQs

Below you’ll find answers to our most commonly asked questions.

If you don’t find the answer you are looking for, please email us at info@traxmatching.io

TraxMatching returns by default:
- A consistent path with OpenStreetMap node IDs and way IDs representing road segments
- A global matching performance indicator, e.g. mean error
And optionally:
- Coordinates and IDs of the matched points
- The geometry of the matched road segments
- Link specific matching performance indicator

Yes

GZIP compress CSV, GPX 1.0 or GPX 1.1

JSON or XML

groupByWays, linkGeometries, osmProjection, linkMatchingError, waypoints and waypointsIDs

Trax Matching is unique in offering a Coordinate Gaps Service. This service fills the gaps in data for up to 5km, based on the shortest predicted path

While the public API only supports the OSM data, the on-premise solution can be adapted to any local map

No

One point = one coordinate pair (i.e. longitude & latitude)

Road, cycling and pedestrian networks are next on the roadmap. If you would like to find out more, please get in touch

AWS Ireland

200, which is double the limit of key competitors, but Trax Matching can handle up to 10,000 for specific use cases. Contact us for details

Yes, API usage statistics are available in the account dashboard

Yes, it can process up to 3k GPS positions per second on a single CPU

You will receive geometry (lat, lon and timestamp).

Additional metadata can be downloaded from OSM and combined using the “way IDs”