[mapserver-commits] r7562 - trunk/docs/howto

[svn at osgeo.org]

Author: pramsey
Date: 2008-05-06 15:39:08 -0400 (Tue, 06 May 2008)
New Revision: 7562

Modified:
   trunk/docs/howto/tile_mode.txt
Log:
VE reference, wrap to 80


Modified: trunk/docs/howto/tile_mode.txt
===================================================================
--- trunk/docs/howto/tile_mode.txt	2008-05-06 03:37:04 UTC (rev 7561)
+++ trunk/docs/howto/tile_mode.txt	2008-05-06 19:39:08 UTC (rev 7562)
@@ -21,9 +21,9 @@
 
 MapServer can feed tile-based map clients directly using the CGI
 "tile mode".  Tile-based map clients work by dividing the map of the world up
-into a discrete number of zoom levels, each partitioned into a number of identically
-sized "tiles".  Instead of accessing a map by requesting a bounding box, a tile
-client builds a map by accessing individual tiles.
+into a discrete number of zoom levels, each partitioned into a number of 
+identically sized "tiles".  Instead of accessing a map by requesting a 
+bounding box, a tile client builds a map by accessing individual tiles.
 
 
 Configuration
@@ -51,9 +51,9 @@
    SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER 
    INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE DEBUG=MSDEBUG
    
-Mapserver requires that each LAYER in your map file have a valid PROJECTION block
-to support reprojection.  Because the tile mode uses reprojection, you will have 
-to ensure each LAYER has a valid PROJECTION block.
+Mapserver requires that each LAYER in your map file have a valid PROJECTION 
+block to support reprojection.  Because the tile mode uses reprojection, 
+you will have to ensure each LAYER has a valid PROJECTION block.
 
 Configuration checklist:
 
@@ -81,9 +81,9 @@
 About Spherical Mercator
 ------------------------
 
-Spherical mercator (also called "web mercator" by some) is a world projection. All
-the major tile-based map interfaces (Google Maps, Microsoft Virtual Earth, Yahoo Maps, 
-OpenLayers) use the spherical mercator system to address tiles.
+Spherical mercator (also called "web mercator" by some) is a world projection. 
+All the major tile-based map interfaces (Google Maps, Microsoft Virtual Earth, 
+Yahoo Maps, OpenLayers) use the spherical mercator system to address tiles.
 
 A spherical mercator set of tiles has the following properties:
 
@@ -93,17 +93,20 @@
  * Each successive zoom level (z) has 2^z tiles along each axis
  * Tiles are 256x256 in size
  
-Google Maps and Virtual Earth both use spherical mercator as their underlying tile
-projection, but use different formats to address the individual tiles.
+Google Maps and Virtual Earth both use spherical mercator as their underlying 
+tile projection, but use different formats to address the individual tiles.
 
-Google Maps uses an "x", "y", "zoom" format.  The zoom indicates which level to pull 
-tiles from, and the "x" and "y" indicate while tile in that zoom level to pull.
+Google Maps uses an "x", "y", "zoom" format.  The zoom indicates which level 
+to pull tiles from, and the "x" and "y" indicate while tile in that zoom 
+level to pull.
 
-Virtual Earth uses a single string to address each tile.  The top zoom level in Virtual Earth has
-four tiles (equivalent to Google's zoom level 1). The top left tile in the Virtual Earth top zoom
-level is addessed as "0", top right as "1", bottom left as "2" and bottom right as "3".  Each tile 
-the next level is addressed by first referencing the top level tile that contains it, then its address 
-relative to that tile.  So the top left tile in the second zoom level is "00" and the bottom right one is "33".  
+Virtual Earth uses a single string to address each tile.  The top zoom level 
+in Virtual Earth has four tiles (equivalent to Google's zoom level 1). The 
+top left tile in the Virtual Earth top zoom level is addessed as "0", top 
+right as "1", bottom left as "2" and bottom right as "3".  Each tile 
+the next level is addressed by first referencing the top level tile that 
+contains it, then its address relative to that tile.  So the top left tile 
+in the second zoom level is "00" and the bottom right one is "33".  
 See the Virtual Earth site for more details: http://msdn.microsoft.com/en-us/library/bb545006.aspx
 
 
@@ -152,9 +155,9 @@
   </body>
   </html>
 
-Note the format of the tileUrlTemplate: a valid URL, with {X}, {Y} and {Z} substitution
-tokens that Google Maps will replace with the tile coordinates and zoom level on the fly
-to retrieve tiles from your server.
+Note the format of the tileUrlTemplate: a valid URL, with {X}, {Y} and {Z} 
+substitution tokens that Google Maps will replace with the tile coordinates 
+and zoom level on the fly to retrieve tiles from your server.
 
 You can also use a Mapserver tile layer as an alternate base map::
 
@@ -197,8 +200,9 @@
   </body>
   </html>
 
-The only change from the previous example is that we don't create a GTileLayerOverlay, 
-we create a GMapType, and use addMapType(), instead of addOverlay().
+The only change from the previous example is that we don't create a 
+GTileLayerOverlay, we create a GMapType, and use addMapType(), instead of 
+addOverlay().
 
 
 Using Virtual Earth
@@ -246,3 +250,4 @@
 
 .. _`GTileLayerOverlay`: http://code.google.com/apis/maps/documentation/reference.html#GTileLayer
 .. _`Google Maps API`: http://code.google.com/apis/maps/
+.. _`Virtual Earth API`: http://dev.live.com/virtualearth/sdk/