RouteConverter
DE Download

CompeGPS / TwoNav (.rte, .trk, .wpt)

CompeGPS data files are the working formats of TwoNav's outdoor software and GPS devices: .trk for a recorded track, .rte for a planned route and .wpt for waypoints — three files, one job each.

At a glance
Extension .rte, .trk, .wpt
Encoding text
By CompeGPS Team S.L., Arenys de Mar, Catalonia, Spain — trading as TwoNav

History

The formats come from CompeGPS Team S.L., a Spanish company based in Arenys de Mar, Catalonia, which trades as TwoNav. Its desktop product Land (and the aviation variant Air) grew up alongside TwoNav, navigation software first written for early Symbian phones and Windows Mobile PDAs and later for the company's own handheld devices. TwoNav publishes its own format documentation, which is unusual for a vendor format of this age.

Where it is used

These files are produced by TwoNav Land and Air on the desktop, by the TwoNav mobile app, and by TwoNav handhelds such as the Aventura and Sportiva when connected in mass storage mode. The company's strongholds are hiking, mountain biking and trail running, particularly in Spain and France.

Structure

All three are plain text with one record per line: a short header declaring datum and field layout, then the data rows. Splitting tracks, routes and waypoints into three separate files is the defining habit of the family — where GPX puts all three in one document, CompeGPS expects three, which is why a single "convert this ride" job can involve more than one file.

How widespread

A live vendor format with a real user base rather than a legacy curiosity. TwoNav's software has read and written GPX for import and export since CompeGPS Land 6.1, so the native formats are mostly encountered when working with files straight off a device or out of an older project folder.

RouteConverter support
Reads CompeGPS Data Route, CompeGPS Data Track, CompeGPS Data Waypoint
Writes CompeGPS Data Route, CompeGPS Data Track, CompeGPS Data Waypoint

RouteConverter handles all three CompeGPS file types through the bundled GPSBabel rather than with its own parser, so gpsbabel must be present — the installer ships it.

Specifications and documentation