Changes between Version 1 and Version 2 of MapGuideRfc55
- Timestamp:
- 08/07/08 16:05:45 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapGuideRfc55
v1 v2 11 11 ||Last Modified||Hugues Wisniewski [[Timestamp]]|| 12 12 ||Author||Hugues Wisniewski|| 13 ||RFC Status|| draft||13 ||RFC Status||for feview|| 14 14 ||Implementation Status||(pending, under development, completed)|| 15 15 ||Proposed Milestone||2.1|| 16 ||Assigned PSC guide(s)|| Tom Fukushima||16 ||Assigned PSC guide(s)||Bruce Dechant|| 17 17 ||'''Voting History'''|| || 18 18 ||+1|| || … … 24 24 == Overview == 25 25 26 For the coordinate system work, MapGuide uses the PROJ4 library which is wrapped into theMgGeometry.dll binary module.27 The coordinate system functionality is exposed through all the API interfaces prefixed with MgCoodinateSystem26 For the coordinate system work, !MapGuide uses the PROJ4 library which is wrapped into the !MgGeometry.dll binary module. 27 The coordinate system functionality is exposed through all the API interfaces prefixed with !MgCoodinateSystem 28 28 This proposal aims at replacing the PROJ4 implementation with the CS-Map implementation. CS-Map was recently open sourced and posted on at:[[BR]] 29 29 http://svn.osgeo.org/metacrs/csmap/ … … 38 38 - WKT transformations in multiple flavors like Oracle[[BR]] 39 39 - greater coverage in terms of coordinate system definitions, right now more than 4000 systems, roughly 700 datums and 100 ellipsoids[[BR]] 40 - CS-Map can provide an implementation to all the MgCoordinateSystem API methods that currently throwMgNotImplementedException[[BR]]40 - CS-Map can provide an implementation to all the !MgCoordinateSystem API methods that currently throw !MgNotImplementedException[[BR]] 41 41 42 42 == Proposed Solution == 43 43 44 The current MgCoordinateSystem API implementation code is a wrapper around PROJ4[[BR]]44 The current !MgCoordinateSystem API implementation code is a wrapper around PROJ4[[BR]] 45 45 This implementation code is located here: [[BR]] 46 46 http://svn.osgeo.org/mapguide/trunk/MgDev/Common/CoordinateSystem/ [[BR]] … … 48 48 http://svn.osgeo.org/metacrs/csmap/trunk/CsMapDev/ [[BR]] 49 49 [[BR]] 50 This API is part of the module MgGeometry.dll generated from the project:[[BR]]50 This API is part of the module !MgGeometry.dll generated from the project:[[BR]] 51 51 http://svn.osgeo.org/mapguide/trunk/MgDev/Common/Geometry/Geometry.vcproj [[BR]] 52 52 [[BR]] … … 63 63 PROJ4 would not be supported anymore.[[BR]] 64 64 The coordinate system definitions will come from the CS-Map coordinate system dictionaries.[[BR]] 65 All the MgCoordinateSystem API methods that currently throwMgNotImplementedException would have a fully functional implementation.[[BR]]66 The build process documentation will have to be updated to explain how to get and build CS-Map and then build MapGuide using CS-Map instead of PROJ4.[[BR]]65 All the !MgCoordinateSystem API methods that currently throw !MgNotImplementedException would have a fully functional implementation.[[BR]] 66 The build process documentation will have to be updated to explain how to get and build CS-Map and then build !MapGuide using CS-Map instead of PROJ4.[[BR]] 67 67 68 68 == Test Plan == 69 69 70 70 CS-Map has its own standalone unit tests so it can be tested separately.[[BR]] 71 The existing unit MapGuide unit tests would remain the same.[[BR]]71 The existing unit !MapGuide unit tests would remain the same.[[BR]] 72 72 More can be added, especially for the new functionality that CS-Map provides, like the WKT conversions.[[BR]] 73 73