Marble/GPXStatus: Difference between revisions
< Marble
No edit summary |
m 6 revisions imported |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
==Gpx Status== | ==Gpx Status== | ||
This page is intended to be a reference as to | This page is intended to be a reference as to the current GPX implementation in Marble. | ||
===GeoData Binding=== | ===GeoData Binding=== | ||
| Line 23: | Line 23: | ||
===Todo=== | ===Todo=== | ||
*Remove Gpx specific Loading in MarbleModel and above (in progress) | *Remove Gpx specific Loading in MarbleModel and above (in progress) | ||
*Complete geodata parser for GPX file type | *Complete geodata parser for GPX file type | ||
*Improve rendering from the current rendering of GeoDataDocuments | *Improve rendering from the current rendering of GeoDataDocuments | ||
Latest revision as of 08:05, 21 October 2016
Gpx Status
This page is intended to be a reference as to the current GPX implementation in Marble.
GeoData Binding
Here is the current binding of Gpx tags to Geodata model classes:
| Tag | Class |
|---|---|
| gpx | GeoDataDocument |
| trk | GeoDataMultiGeometry in a GeoDataPlacemark |
| trkseg | GeoDataLineString |
| trkpt | GeoDataCoordinates |
| wpt | GeoDataPlacemark |
| name | GeoDataPlacemark::name |
Todo
- Remove Gpx specific Loading in MarbleModel and above (in progress)
- Complete geodata parser for GPX file type
- Improve rendering from the current rendering of GeoDataDocuments