Marble/GeoData: Difference between revisions

Latest revision as of 08:05, 21 October 2016

GeoData Overview

The Marble Framework has got two major design goals:

The Marble Framework should build strongly on Qt-API principles and Qt design concepts.
The map data should be handled using classes that are modelled after the 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.

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

Use cases for GeoData classes
GeoData API Description

Parsing GeoData
Writing GeoData

@@ Line 1: / Line 1: @@
 == 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.
-{{class|GeoDataDocument|kdeedu|4.2}} describes a document.
+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].
-A model representation is built through parsing of files and creating a stack of {{class|GeoDataObject|kdeedu|4.2}} representing its data.
+;[[/GeoDataUse|Use cases for GeoData classes]]
-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].
+;[http://websvn.kde.org/*checkout*/trunk/KDE/kdeedu/marble/src/lib/geodata/data/README.html GeoData API Description]
-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.
+;[[/GeoDataParsing|Parsing GeoData]]
+;[[/GeoDataWriter|Writing GeoData]]