Difference between revisions of "MapGuide RFC 4 - KML Support"

Latest revision as of 19:55, 15 March 2007

This page has moved to the MapGuide Trac Wiki:

http://trac.osgeo.org/mapguide/wiki/MapGuideRfc4

@@ Line 1: / Line 1: @@
- This page contains an change request (RFC) for MapGuide Open Source.
+This page has moved to the MapGuide Trac Wiki:
- More MapGuide RFCs can be found on the [[MapGuide RFCs]] page.
-=Status=
+http://trac.osgeo.org/mapguide/wiki/MapGuideRfc4
-*Submission Date:
-*Last Modified Date:
-*Author: Chris Claydon
-*RFC Status: (draft, proposed/pending vote, adopted or rejected)
-*Implementation Status: under development
-*Voting History:
-*Assigned PSC guide(s):
-=Overview=
-Google Earth allows external data to be overlaid upon its own vast collection of satellite imagery and vector graphics. It does this by supporting KML - an XML-based format that can be used to define how external vector and raster data may be dynamically loaded and displayed within the Google Earth application.
-=Motivation=
-By integrating MapGuide with Google Earth, we provide a compelling way for users to visualize their data in relation to the planet as a whole. In addition to satellite imagery, Google provides a large amount of useful content, such as road networks, points of interest, voting districts etc. By serving up MapGuide data via KML (and its compressed form, KMZ) we allow users to incorporate their specific data set with Google's.
-So, for example, if a MapGuide data set contained information about underground pipes and sewers, this information could be overlaid on a satellite image showing individual streets and houses. This would greatly facilitate the process of estimating exactly which homes and streets would be affected by any maintenance required on those pipes.
-=Funding/Resources=
-Resources supplied by Autodesk.
-=Proposed Changes=
-This is a more detailed description of the actual changes desired.  The contents of this section will vary based on the target of the RFC, be it a technical change, website change, or process change.  For example, for a technical change, items such as files, XML schema changes, and API chances would be identified.  For a process change, the new process would be laid out in detail.  For a website change, the files affected would be listed.
-=Implications=
-This section allows discussion of the repercussions of the change, such as whether there will be any breakage in backwards compatibility, if documentation will need to be updated, etc.
-=Test Plan=
-How the proposed change will be tested, if applicable.  New unit tests should be detailed here???

Difference between revisions of "MapGuide RFC 4 - KML Support"

Latest revision as of 19:55, 15 March 2007

Navigation menu

Search