Marble/GeoData: Difference between revisions

    From KDE TechBase
    No edit summary
    (Replaced content with "{{ Moved To Community }}")
     
    (5 intermediate revisions by 2 users not shown)
    Line 1: Line 1:
    == GeoData Overview ==
    {{ Moved To Community }}
     
    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 is built through parsing of files and creating a stack of {{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].
     
    ;[[/GeoDataParsing|Parsing GeoData]]
    ;[[/GeoDataUse|Using GeoData classes]]

    Latest revision as of 04:45, 26 October 2016

    This page is now on the community wiki.