Convert GPI to GML
Turn GPI files into GML. A GML 3.2 document with one feature type holding the features and their attributes, in the source's coordinate system and without a separate schema file.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop GPI files on the dialor turn it to pick what to do
Garmin POI points as GML 3.2 features.One GML file with one feature type, in the coordinate system of the source.
What you get
A single GML 3.2 document. It holds one feature type with all the features and their attributes. No separate schema file comes with it.
Waypoints become points, routes become lines, and tracks become multilines with a part for each segment. A layer column names the layer each feature comes from: waypoints, routes, tracks, route_points or track_points.
Points from routes and tracks
Every route point and track point also becomes a point of its own. Each carries its time in UTC and the values the device logged with it, such as satellites, heart rate as hr and cadence as cad.
The track_fid and route_fid columns tie each point to its track or route.
What changes
Heights stay in the shapes as Z and in the ele column of points. When some features have heights and others do not, the ones without get a height of 0.
Lists and nested values become JSON text. Columns that no feature fills are left out.
GPI and GML.What each format is.
The formats
Garmin POI
Points of interest that Garmin car and handheld navigators load as custom POI files.
- Extensions
- .gpi
- MIME type
- application
/x -garmin -gpi - Kind
- Text and data
GML
Geography Markup Language, the OGC's XML for map features, as WFS services send it.
- Extensions
- .gml
- MIME type
- application
/gml +xml - Kind
- Text and data
In your code.The same GPI to GML conversion through the API, for your app or your agent.
$ cv convert report.gpi report.gml$ cv convert report.gpi report.gmlQuestions.What people ask about GPI to GML.
Yes. The features stay in the source's coordinate system.
No. The output is one GML 3.2 document without a separate schema file.
When some features have heights and others do not, the ones without get a height of 0.
Use the track_fid column. For points on a route, use route_fid.