Marble/GeoData: Difference between revisions
< Marble
No edit summary |
No edit summary |
||
| 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. | 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. | 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. | ||
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]. | ||
Revision as of 22:43, 14 August 2010
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 this data is built through parsing of files or more generally feeding data and creating a GeoDataDocument containing various other GeoDataObject representing its data. The Geodata objects are all modeled after the Google KML files as defined in the KML documentation.