Marble/GPXStatus: Difference between revisions

Revision as of 23:30, 19 February 2010

This page is intended to be a reference as to what needs to be done to update the current GPX implementation in Marble.

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

@@ Line 2: / Line 2: @@
 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:
+{| border="1"
+! Tag !! Class
+|-
+| gpx || GeoDataDocument
+|-
+| trk || GeoDataMultiGeometry in a GeoDataPlacemark
+|-
+| trkseg || GeoDataLineString
+|-
+| trkpt || GeoDataCoordinates
+|-
+| wpt || GeoDataPlacemark
+|-
+| name || GeoDataPlacemark::name
+|-
+|  ||
+|}
+===Todo===
 *Remove the Abstract Layer
 *Uncouple the current GPS location rendering from the GPS Layer
-*Load files through the FileManager
+*Remove Gpx specific Loading in MarbleModel and above
 *Complete geodata parser for GPX file type
-*Share rendering from the current rendering of GeoDataDocuments
+*Improve rendering from the current rendering of GeoDataDocuments
-==Ideas for later==
+===Ideas for later===
 *Make GPX loading and rendering a plugin