Projects/Marble/GeoData - Revision history

Tgridel at 23:10, 14 August 2010

2010-08-14T23:10:06Z

Tgridel at 22:43, 14 August 2010

2010-08-14T22:43:18Z

Tgridel at 09:23, 15 August 2009

2009-08-15T09:23:16Z

Tgridel at 13:32, 2 August 2009

2009-08-02T13:32:47Z

Tgridel at 22:26, 31 July 2009

2009-07-31T22:26:39Z

Tackat at 16:46, 31 July 2009

2009-07-31T16:46:57Z

Tackat: Putting Parsing into a special page of its own

2009-07-31T16:34:39Z

Putting Parsing into a special page of its own

Tgridel: description moved from GraphicsViewGeoParser

2009-07-22T21:49:40Z

description moved from GraphicsViewGeoParser

Tampakrap: Created page with '== 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 per...'

2009-07-18T07:50:18Z

Created page with '== 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 per...'

New page

== 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.

{{class|GeoDataDocument|kdeedu|4.2}} describes a document.

A model representation is built through parsing of files and creating a stack of {{class|GeoDataObject|kdeedu|4.2}} representing its data.
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 {{class|GeoParser|kdeedu|4.2}} is a framework to parse xml files, which 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|GeoStackHandler|kdeedu|4.2}} which define how a node in the file is to be processed and should populate the data model.

@@ Line 11: / Line 11: @@
 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.
-A model representation of this data is built through parsing of files or more generally feeding data and creating a {{class|GeoDataDocument|kdeedu|4.x}}  containing various other {{class|GeoDataObject|kdeedu|4.x}} representing its data.
+A model representation of a document is built through parsing of files and creating a {{class|GeoDataDocument|kdeedu|4.x}} with {{class|GeoDataObject|kdeedu|4.2}} representing its data.
 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].

@@ Line 16: / Line 16: @@
 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]]
+;[[/GeoDataUse|Use cases for GeoData classes]]
-;[[/GeoDataUse|Using GeoData classes]]
 ;[http://websvn.kde.org/*checkout*/trunk/KDE/kdeedu/marble/src/lib/geodata/data/README.html GeoData API Description]

← Older revision		Revision as of 13:32, 2 August 2009
Line 18:		Line 18:
	;[[/GeoDataParsing\|Parsing GeoData]]		;[[/GeoDataParsing\|Parsing GeoData]]
	;[[/GeoDataUse\|Using GeoData classes]]		;[[/GeoDataUse\|Using GeoData classes]]
		+	;[http://websvn.kde.org/checkout/trunk/KDE/kdeedu/marble/src/lib/geodata/data/README.html GeoData API Description]

← Older revision		Revision as of 22:26, 31 July 2009
Line 17:		Line 17:

	;[[/GeoDataParsing\|Parsing GeoData]]		;[[/GeoDataParsing\|Parsing GeoData]]
		+	;[[/GeoDataUse\|Using GeoData classes]]

← Older revision		Revision as of 16:46, 31 July 2009
Line 1:		Line 1:
	== GeoData Overview ==		== GeoData Overview ==
		+
		+	The Marble Framework has got two major design goals:
		+	* The Marble Framework should build strongly on [http://qt.gitorious.org/qt/pages/ApiDesignPrinciples#Naming+Enum+Types+and+Values Qt-API principles] and Qt design concepts.
		+	* The map data should be handled using classes that are modelled after the [http://code.google.com/intl/de/apis/kml/documentation/kmlreference.html KML OGC standard].
		+
		+	The KML standard itself describes the properties of a data model for maps:
		+
		+

	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.		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.

@@ 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].
+;[[/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.

← Older revision		Revision as of 21:49, 22 July 2009
Line 9:		Line 9:


−	The {{class\|GeoParser\|kdeedu\|4.2}} is a framework to parse xml files~~, which~~ 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\|~~GeoStackHandler~~\|kdeedu\|4.2}} which define how a node in the file is to be processed and should populate the data model.	+	== 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.