Marble/GPXStatus: Difference between revisions
< Marble
No edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
===Todo=== | ===Todo=== | ||
*Remove the Abstract Layer | *Remove the Abstract Layer (in progress) | ||
*Uncouple the current GPS location rendering from the GPS Layer | *Uncouple the current GPS location rendering from the GPS Layer (done) | ||
*Remove Gpx specific Loading in MarbleModel and above | *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 | ||
Revision as of 21:13, 6 June 2010
Gpx Status
This page is intended to be a reference as to what needs to be done to update 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 the Abstract Layer (in progress)
- Uncouple the current GPS location rendering from the GPS Layer (done)
- 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
Ideas for later
- Make GPX loading and rendering a plugin