OMN4 documentation is still being worked on. Images will be added later.
OMN4
Reference

GPX Format

GPX is an XML file format for exchanging routes, tracks, and waypoints between mapping apps and GPS devices. This page describes the file structure and what OMN4 can preserve; use the Routes page for import and export steps.

Core GPX Elements

GPX elementMeaning in OMN4
<wpt>A waypoint or point with a position and optional details.
<rte>A route made from ordered route points.
<rtept>A point within a route.
<trk>A recorded or imported track.
<trkseg>A segment within a track.
<trkpt>A point within a track segment.

Common Fields

FieldTypical use
NameThe visible name of a route, track, waypoint, or folder-like item.
Description or commentNotes that another app may show as description text.
TimeTimestamp for track points or other recorded positions, when present.
ElevationHeight value for a point, when present in the file.
LinkA web link attached to a GPX item.
SymbolIcon or symbol hint for a waypoint or point.
Extension dataApp-specific metadata outside the base GPX fields.
TypeActivity classification for a route or track. OMN4 exports the catalogue's exact GPX type.

Different apps use these fields differently. When exchanging GPX, expect the route or track geometry to be the safest part of the file.

OMN4 Metadata

OMN4 tries to preserve supported route, track, waypoint, folder, icon, timestamp, elevation, link, and style metadata when it imports and exports GPX. Some OMN4-specific data is stored in GPX extensions so that OMN4 can understand it on re-import.

For each exported route or track, OMN4 writes the exact system Activity ID and its catalogue display name in an OMN4 extension. On re-import, a recognised ID restores the exact Activity before OMN4 considers the standard GPX <type>. The display name in the extension is descriptive and is not used as identity.

For third-party GPX, OMN4 can match <type> against a system Activity's catalogue code, exact GPX value, current display name, or another approved synonym. Matching ignores letter case and normalises surrounding or repeated whitespace, but it does not remove punctuation. If a selected batch still contains unknown or missing Activities, the user must choose one Activity for those items or explicitly choose the account default.

Other apps may ignore OMN4-specific extensions. They may still read the basic GPX geometry, names, and common fields. OMN4 preserves Waypoint metadata and unrelated third-party extensions during a local export and re-import, but another app may remove extensions it does not understand.

Legacy And Third-Party Files

OMN4 also reads common GPX files from other apps and legacy OMN exports where the supported data can be mapped into OMN4 routes, tracks, waypoints, and folders.

Malformed fields, unsupported extension data, or app-specific styling from another product may be skipped. That should not be treated as a full OMN4 backup failure; GPX is an exchange format, not a complete account or device backup.

Not A Full Backup

GPX does not contain offline map downloads, subscription state, full app settings, or every OMN4-specific detail. Use backup and restore for data protection, and cloud sync to keep supported personal data in step across devices.

On this page