Merge pull request #78 from jerstlouis/master

Fixes to meters/degrees confusion in Annex C/WKSS; Fixes to TileSet metadata overview

Author: joanma747

standard/sections/08-tileset_metadata.adoc

@@ -4,25 +4,38 @@
 
 === Overview
 
+[[tileset-medatadata-overview]]
+==== TileSet metadata
+
+Tiles are identified by tileMatrix id, tileRow number and tileCol number. These three
+elements only have meaning if they are associated with a TileMatrixSet description that
+contains the necessary information (in terms of scaleDenominator, cellSize,
+pointOfOrigin and cornerOfOrigin) to transform the indices into coordinates in a
+known CRS. The main purpose of the TileSetMetadata is to link the TileSet with the
+TileMatrixSet description. In addition, the model contains elements describing the
+main characteristics of a TileSet, preserving the connection from the TileSet to the original
+data collection and styles as well as a recommended center point to start the
+navigation.
+
 [[tile-matrix-set-limits-overview]]
 ==== TileMatrixSet limits
 
 Imagine a case where a tileset covers the whole bounding box of a tile matrix
 set. Now, imagine that the tileset extent needs to be expanded beyond the point
 and corner of origin of each TileMatrix. Changing the point of origin changes
 the position of any tile row and tile column indices. In other words, in the new
-tileset, tiles that cover the same bounding box than the previous tileset
+tileset, tiles that cover the same bounding box as the previous tileset
 receive different tile row and tile column indices. This invalidates any cached
 tiles that the client could have stored and all client copies need to be
 updated. To overcome this problem, a dataset can optionally use a more generic
-TileMatrixSet that covers a bigger area (or even global one, such as one of
-defined in <<annex-common-tilematrixset-definitions-informative>>). In fact,
-that TileMatrixSet that defines an area that might be covered by the dataset in
-a future could easily be shared for many datasets and become a common
+TileMatrixSet that covers a bigger area (or even the entire globe, such as one of
+those defined in <<annex-common-tilematrixset-definitions-informative>>). In fact,
+that TileMatrixSet defining an area that might be covered by the dataset in
+the future could easily be re-used for many other datasets and become a common
 TileMatrixSet.
 
 To inform the client about the valid range of tile indices in a tileset, the
-TileMatrixSetLimits concept is introduced. A list of TileMatrixSetLimit informs
+TileMatrixSetLimits concept is introduced. A list of TileMatrixSetLimits informs
 the minimum and maximum limits of these indices for each TileMatrix that
 contains actual data. The area outside these limits is considered empty space
 and is not covered by the tileset.
@@ -31,19 +44,6 @@ and is not covered by the tileset.
 .TileMatrixSet Limits
 image::4.png[TileMatrix Limits]
 
-[[tileset-medatadata-overview]]
-==== TileSet metadata
-
-Tiles are identified by tileMatrix id, tileRow number and tileCol number. These three
-elements only have meaning if they are associated with a tileMatrixSet description that
-contains the necessary information (in terms of scaleDenominator, cellSize,
-pointOfOrigin and cornerOfOrigin) to transform the indices into coordinates in a
-known CRS. The main purpose of the TileSetMetadata is to link the TileSet with the
-tileMatrixSet description. In addition, the model contains elements describing the
-main characteristics of a TileSet, the connection to the TileSet with the original
-data collection and styles as well as a recommended center point to start the
-navigation.
-
 === Requirements classes
 
 ==== TileMatrixSetLimits requirements class

standard/sections/ac-annex_c.adoc

@@ -106,7 +106,7 @@ is only accurate near the equator.
 .Definition of Well-known scale set GoogleCRS84Quad
 [cols="a,a,a",options="header"]
 |===
-| CRS | Scale Denominator | Cell Size (m)
+| CRS | Scale Denominator | Cell Size (degrees)
 
 .19+| http://www.opengis.net/def/crs/OGC/1.3/CRS84 | 559,082,264.0287178 | 1.40625000000000
 | 279,541,132.0143589 | 0.703125000000000