| (2 intermediate revisions by one user not shown) | |||
| 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 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]] | |
| − | ;[[/GeoDataUse| | + | |
;[http://websvn.kde.org/*checkout*/trunk/KDE/kdeedu/marble/src/lib/geodata/data/README.html GeoData API Description] | ;[http://websvn.kde.org/*checkout*/trunk/KDE/kdeedu/marble/src/lib/geodata/data/README.html GeoData API Description] | ||
| + | |||
| + | |||
| + | ;[[/GeoDataParsing|Parsing GeoData]] | ||
| + | ;[[/GeoDataWriter|Writing GeoData]] | ||
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.
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.
KDE TechBase 