Difference between revisions of "Projects/Marble/GeoData"

Jump to: navigation, search
(Putting Parsing into a special page of its own)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== GeoData Overview ==
 
== 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.
+
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].
  
{{class|GeoDataDocument|kdeedu|4.2}} describes a document.
+
The KML standard itself describes the properties of a data model for maps:
  
A model representation is built through parsing of files and creating a stack of {{class|GeoDataObject|kdeedu|4.2}} representing its data.
+
 
 +
 
 +
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 {{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].
 
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].
 +
 +
;[[/GeoDataUse|Use cases for GeoData classes]]
 +
;[http://websvn.kde.org/*checkout*/trunk/KDE/kdeedu/marble/src/lib/geodata/data/README.html GeoData API Description]
 +
  
 
;[[/GeoDataParsing|Parsing GeoData]]
 
;[[/GeoDataParsing|Parsing GeoData]]
 +
;[[/GeoDataWriter|Writing GeoData]]

Latest revision as of 00:10, 15 August 2010

[edit] 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

This page was last modified on 15 August 2010, at 00:10. This page has been accessed 3,821 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal