|
|
| (2 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| ==Gpx Status==
| | {{ Moved To Community }} |
| 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 (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
| |
Latest revision as of 04:45, 26 October 2016
