Changes between Version 4 and Version 5 of MapGuideRfc51

Timestamp:

Jul 14, 2008, 3:38:40 PM (16 years ago)

Author:

tonyfang

Comment:

--

MapGuideRfc51

@@ -28 +28 @@
 == Motivation ==
 
-MapGuide does not currently support any form of raster re-projection. If a user has a raster feature source, it can only be displayed in a MapGuide map that uses the same coordinate system as the raster data.
+!MapGuide does not currently support any form of raster re-projection. If a user has a raster feature source, it can only be displayed in a !MapGuide map that uses the same coordinate system as the raster data.
 
 Previously, in order for application developers to use images in multiple coordinate systems, they needed to create copies of the images in each coordinate system.  The re-projection capability that we are adding will allow developers to not have to have multiple versions of the same image (re-projected to different coordinate systems) at the cost of about 25% degradation in performance.
@@ -57 +57 @@
 Descriptive error messages will be logged to handle invalid configuration settings, invalid data, unsupported transformations etc.
 
-In keeping with MapGuide’s current behavior, if the re-projection fails for any reason, the map will still be rendered and returned, using any other layers that it contains, and the failed layer(s) will be skipped.
+In keeping with !MapGuide’s current behavior, if the re-projection fails for any reason, the map will still be rendered and returned, using any other layers that it contains, and the failed layer(s) will be skipped.
 
 We will add an optimization if the re-projection is a simple datum shift. The image will simply be shifted, and the advanced algorithm will not be invoked.
@@ -71 +71 @@
 
 Unit tests should cover:
-* The most common raster image formats (ECW, MrSid, TIFF)
+
+* The most common raster image formats (ECW, !MrSid, TIFF)
 * Re-projections between each of the main coordinate system types