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

What data is available from Trax Matching?

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

Does Trax Matching have an on-premise option?


What are the accepted file formats?

GZIP compress CSV, GPX 1.0 or GPX 1.1

In what formats will I receive the response data?


What are the available parameters?

groupByWays, linkGeometries, osmProjection, linkMatchingError, waypoints and waypointsIDs

What happens if the GPS data is very infrequent?

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

Is Trax Matching compatible with other map providers other than OpenStreetMaps?

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

When using the API, is there any restriction on being able to cache the results/output data of the request for later use?


What’s your definition of a ‘point’?

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

In addition to the motorised road network, does Trax Matching also cover other networks?

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

Where are your servers located?

AWS Ireland

What are the maximum points per request allowed?

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

Does Trax Matching support analytics?

Yes, API usage statistics are available in the account dashboard

Can Trax Matching scale to very large databases?

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

What metadata will I receive?

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

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