Marble/GPXStatus: Difference between revisions

From KDE Community Wiki
No edit summary
m (6 revisions imported)
 
(4 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 what needs to be done to update the current GPX implementation in Marble.  
This page is intended to be a reference as to the current GPX implementation in Marble.


*Remove the Abstract Layer
===GeoData Binding===
*Uncouple the current GPS location rendering from the GPS Layer
Here is the current binding of Gpx tags to Geodata model classes:
*Load files through the FileManager
{| border="1"
! 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
*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==
*Make GPX loading and rendering a plugin

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