closed 4.2.1.1 2005-05-26T20:13:50.752-06:00 2004-06-12T21:33:48.688-06:00 TSD4.2 Archaeological Markup Language (ArchaeoML), version 0.9, February 2006. Created by David Schloen of the University of Chicago. Map document type. A Map document stores information about a vector or raster map, plan, or section drawing. Users may wish to display a given map in terms of a local, two-dimensional Cartesian coordinate grid. For this purpose, coordinates stored in UTM meters are converted using a scaling factor (= 1 if the local grid is also in meters), rotation angle in decimal degrees, and translations along X (easting) and Y (northing) axes. Any number of three-dimensional conformal (similarity) transformations can be specified to allow automatic conversions from UTM map coordinates to other named coordinate systems. Each such transformation uses a set of seven parameters: three translations along X- Y- and Z-axes, three rotation angles about X- Y- and Z-axes, and a scaling factor. Note that rotation angles are specified in seconds of arc. A map can have an optional georeferenced background image as an underlying layer. The resourceID must reference a TIFF, JPEG, BMP, GIF, or PNG image. The worldFileData contains the transformation parameters in ESRI world-file format (calculated using ArcGIS or some other tool) for georeferencing the image file into UTM meters (or into decimal degrees, if the map uses degrees instead of UTM meters). A docID here must refer to a Set document, which corresponds to a map layer composed of all the map shapes that belong to items in that set. Z elevations are stored as meters above mean sea level. A docID here must refer to a MapShape document. nestedDocIdIndex