Changes between Version 4 and Version 5 of WorldMappingIssues

Timestamp:

Feb 9, 2010, 8:32:45 AM (14 years ago)

Author:

warmerdam

Comment:

--

WorldMappingIssues

@@ -13 +13 @@
 In the case of world spanning polygons this logic can sometimes mis-fire resulting in features getting stretched over more than 360 degrees. 
 
+== BBOX Transformation ==
+
+One fairly common use case is maps rendered in projected coordinates but read from geographic raster sources (sometimes a cascaded WMS).  In these cases the projected map region needs to be reprojected into lat/long and used to fetch raster data for resampling.  If the projected rectangle crosses the dateline it is easy to end up requesting a window of data that wraps around the world.  This wouldn't be so bad, but because MapServer tries to request raster data from remote WMSes or raster files at roughly the size of the output map it ends up getting much lower resolution data in the actual area of interest than will be needed to render well.  This problem is addresed in #3179. 
+
 == Some Related Tickets ==
 
@@ -20 +24 @@
  * #740 - WMS client requests with non-square pixels
  * #3111 - WMS Reprojection misses stuff near the dateline
+ * #3179 - WMS Client Requests Pixelated