Difference between revisions of "Projects/Marble/GeoData"

Jump to: navigation, search
(description moved from GraphicsViewGeoParser)
(Putting Parsing into a special page of its own)
Line 8: Line 8:
 
The Geodata objects are all modeled after the Google KML files as defined in the [http://code.google.com/apis/kml/documentation/kml_tags_21.html KML documentation].
 
The Geodata objects are all modeled after the Google KML files as defined in the [http://code.google.com/apis/kml/documentation/kml_tags_21.html KML documentation].
  
 
+
;[[/GeoDataParsing|Parsing GeoData]]
== Parsing GeoData ==
+
The {{class|GeoParser|kdeedu|4.2}} is a framework to parse xml files based on the {{qt|QXMLStreamReader}} class in Qt (more info [http://doc.qtsoftware.com/4.5/qtxml.html here]).
+
 
+
It is specialised in {{class|GeoDataParser|kdeedu|4.2}} to handle KML, GPX, GeoRSS and OSM formats and populate the data model. The parser relies on
+
 
+
* {{class|GeoTagHandler|kdeedu|4.2}} classes which define how a node in the file is to be processed and should populate the data model.
+
* A {{class|GeoStackItem|kdeedu|4.2}} class that implements the Structural parts of the XML document
+
* The collection class where the results of the XML parsing will be placed
+
* An element dictionary that prevents the need for string comparison everywere
+
 
+
To implement a new XML parser you need to
+
#compile an element dictionary of all of the available tags in the namespace
+
#implement a tag handler for each of these elements
+
#register that tag handler with the GeoParser
+
 
+
==== Implementing a tag handler ====
+
Each tag handler is called when the relevant XML tag is reached by the GeoParser ( which knows what tags to call by its registered tag list ). Each tag can access the stack data structure of the GeoParser as well as the Collection Data Structure of the GeoParser. This allows the tag handler to access items from the stack and allows root elements of the XML to add themselves to the collection data structure.
+

Revision as of 17:34, 31 July 2009

GeoData Overview

GeoData holds the data model that is internally used for any geographic information which should be rendered. It deals whith the data only, drawing is performed elsewhere.

GeoDataDocument describes a document.

A model representation is built through parsing of files and creating a stack of GeoDataObject representing its data. The Geodata objects are all modeled after the Google KML files as defined in the KML documentation.

Parsing GeoData

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal