(Putting Parsing into a special page of its own) |
|||
| 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. | ||
The Marble Framework has got two major design goals:
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.
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.
KDE TechBase 