<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Science Applications International Corporation (SAIC)</origin>
				<pubdate>20071212</pubdate>
				<title Sync="TRUE">mb1_be_01.img</title>
				<geoform Sync="TRUE">remote-sensing image</geoform>
				<pubinfo>
					<pubplace>Chantilly, VA</pubplace>
					<publish>Science Applications International Corp. (SAIC)</publish>
				</pubinfo>
				<othercit>Bare Earth DEM</othercit>
				<pubtime>Unknown</pubtime><onlink Sync="TRUE">\\ph40nsx5\v5$\PH\67481_USGS_Mexico\SAIC\Area_1\Area_1_Bare_earth\mb1_be_01.img</onlink><ftname Sync="TRUE">mb1_be_01.img</ftname></citeinfo>
		</citation>
		<descript>
			<abstract>LIDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform.  Using a combination of laser rangefinding, GPS positioning and inertial measurement technologies; LIDAR instruments are able to make highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures and vegetation.  This data was collected at a resolution of 1 meter and includes reflective surface, last return, bare earth model and intensity data in separate data files.</abstract>
			<purpose>LIDAR data is used for 3D visualization, elevation based analysis and for feature extraction.</purpose>
			<supplinf>Reflective surface data represents the DEM created by laser energy reflected from the first surface encountered by the laser pulse.    Some energy may continue beyond this initial surface to be reflected by a subsequent surface as represented by the Last Return data.    Intensity information is captured from the Reflective Surface pulse and indicates the relative energy returned to the sensor as compared to the energy transmitted.  The Intensity image is not calibrated or normalized but indicates differences in energy absorption due to the the interaction of the surface materials with laser energy at the wavelength transmitted by the sensor.    Bare earth model is created by identifying those returns that fall on the ground surface and interpolating a surface between these points.  In this manner buildings and vegetation are removed from Bare Earth Model.   This data set does not include bridges and overpasses in the Bare Earth model as the delineation point for these structures is not reliably discernable in the LiDAR data.</supplinf>
			<langdata Sync="TRUE">en</langdata></descript>
		<timeperd>
			<timeinfo>
				<rngdates><begdate>20071005</begdate><begtime>unknown</begtime><enddate>20071015</enddate><endtime>unknown</endtime></rngdates><sngdate><caldate>REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.</caldate></sngdate></timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>Irregular</update>
		</status>
		<spdom>
			<bounding>
				<westbc Sync="TRUE">-114.011532</westbc>
				<eastbc Sync="TRUE">-113.752630</eastbc>
				<northbc Sync="TRUE">32.261084</northbc>
				<southbc Sync="TRUE">32.116038</southbc>
			</bounding>
			<lboundng><leftbc Sync="TRUE">216279.000000</leftbc><rightbc Sync="TRUE">240300.000000</rightbc><bottombc Sync="TRUE">3557258.000000</bottombc><topbc Sync="TRUE">3572712.000000</topbc></lboundng></spdom>
		<keywords>
			<theme>
				<themekt>Light Distancing And Ranging</themekt>
				<themekey>LIDAR</themekey>
			</theme>
			<theme>
				<themekt>Digital Elevation Model</themekt>
				<themekey>DEM</themekey>
			</theme>
			<theme>
				<themekt>Average ground sample distance 1m</themekt>
				<themekey>1meter resolution elevation model</themekey>
			</theme>
			<theme>
				<themekey>Bare Earth</themekey>
				<themekt>Model of earth surface with buildings and vegetation removed</themekt></theme>
			<place>
				<placekt>U.S. Department of Commerce, 1995, Countries, Dependencies, Areas of Special Sovereignty, and Their Principal Administrative Divisions (Federal Information Processing Standard (FIPS) 10-4): Washington, D.C., National Institute of Standards and Technology</placekt>
				<placekey>US</placekey>
				<placekey>Mexico</placekey></place>
			<place>
				<placekt>U.S. Department of Commerce, 1987, Codes for the Indentification of the States, the District of Columbia and the outlying areas of the United States, and associated areas (Federal Information Processing Standards (FIPS) 5-2): Washington, D.C., National Institute of Standards and Technology.</placekt>
				<placekey>AZ</placekey>
			</place>
			<place>
				<placekt>City name</placekt>
				<placekey>Area 1</placekey>
			</place>
			<place>
				<placekt>Location Description</placekt>
				<placekey>Border</placekey>
			</place>
		</keywords>
		<accconst>None</accconst>
		<useconst>None.  However, users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions.  Users should not use this data for critical applications without a full awareness of it's limitations.</useconst>
		<ptcontac>
			<cntinfo>
				<cntorgp>
					<cntorg>USGS</cntorg>
				</cntorgp>
			</cntinfo>
		</ptcontac>
		<datacred>n/a</datacred>
		<secinfo>
			<secclass>Unclassified</secclass>
			<secsys>US DOD</secsys><sechandl>Information Unclassified - distribution limited by Point of Contact</sechandl></secinfo>
		<native Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350</native>
		<natvform Sync="TRUE">Raster Dataset</natvform></idinfo>
	<dataqual>
		<logic>All IMG formatted image data are validated using commercial GIS software to ensure proper formatting and loading before delivery.  This validation procedure ensures that data on delivery media is in correct physical format and is readable.</logic>
		<complete>LIDAR raster data is visually inspected for completeness to ensure that any gaps between flight lines or loss of signal represents less than 5% of required collection area.  Areas of open water where loss of LIDAR signal is common are corrected to the best estimate of water level at time of collection.  Areas of NODATA resulting from differences between required collection area and minimum bounding rectangle and/or areas of missing data are coded -999 to ensure compatibility between ESRI production software and ERDAS delivery format.  LIDAR is self-illuminating and has minimal cloud penetration capability.  Water vapor in steam plumes or particulates in smoke may cause reflection of LIDAR signals and loss of elevation information beneath these plumes.  Glass structures and roofs may appear transparent to the LIDAR signal and therefore may not register on the reflective surface.  Some asphalt formulations have been shown to absorb topographic LIDAR wavelength energy resulting in "pitting" of roof surfaces using this material.</complete>
		<posacc>
			<horizpa>
				<horizpar>Horizontal accuracy of the source LIDAR data can be characterized by the rule of thumb of 1/2000th of flying height or roughly 0.5 meters for this collect.  Spot checks in the field routinely are measured at 1/4000th of flying height but are not formally characterized.</horizpar>
				<qhorizpa>
					<horizpav>0.5</horizpav>
					<horizpae>Estimated based on rule of thumb and collection altitude - units in meters</horizpae></qhorizpa>
			</horizpa>
			<vertacc>
				<vertaccr>The vertical accuracy was tested following the National Standards for Spatial Data Accuracy.  Based on a total of 85 control points, the average error between the bare earth LiDAR coverage and the control was -0.005 m with a root mean square error (RMSE) of 0.110 m.</vertaccr>
				<qvertpa>
					<vertaccv>-0.005 m</vertaccv>
					<vertacce>Average error between Bare Earth LiDAR coverage and control</vertacce>
				</qvertpa>
				<qvertpa>
					<vertaccv>0.110 m</vertaccv>
					<vertacce>root mean square error (RMSE)</vertacce>
				</qvertpa>
			</vertacc>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Woolpert</origin>
						<pubdate>Unpublished Material</pubdate>
						<title>LIDAR data collection</title>
						<othercit>Type of Scanner = LH Systems ALS50
Data Acquisition Height = 5,000-feet AGL
Scanner Field of View = 25 degrees
Scan Frequency = 36 Hertz
Pulse Repetition Rate - 44.2 Kilohertz
Aircraft Speed = 122 KIAS
Swath Width = 2217-feet
Nominal Ground Sample Distance = 3.0-feet
Number of Returns Per Pulse = 2 (first and last)
Distance Between Flight Lines = 1,331-feet</othercit>
					</citeinfo>
				</srccite>
				<srcscale>3000</srcscale>
				<typesrc>DVD</typesrc>
				<srctime>
					<timeinfo>
						<rngdates>
							<begdate>20071005</begdate>
							<enddate>20071015</enddate>
						</rngdates>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>LIDAR</srccitea>
				<srccontr>Raw spatial elevation information</srccontr></srcinfo>
			<procstep>
				<procdesc>Process Step:

Production Narrative:  

Using a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, 108 flight lines of high density (submeter ground sample distance) data were collected along US and Mexico border in Arizona (approximately 1493 square kilometers).  Two returns were recorded for each laser pulse along with an intensity value for each return.  A total of eleven missions were flown over an eleven day period: October 5, 2007, October 6, 2007, October 7, 2007, October 8, 2007, October 9, 2007, October 10, 2007, October 11, 2007, October 12, 2007, October 13, 2007, October 14, 2007, and October 15, 2007. Nine airborne global positioning system (GPS) base stations were used to support the LiDAR data acquisition: New Tucson Base, Sasabe 0&amp;1 Base 1, Sasabe 0&amp;1 Base 2, Sasabe 2 Base 1, Sasabe 2 Base 2, Sasabe 3 V307, Sasabe 3 Z307, Sasabe 4 SIGMA, and Sasabe 4 YUMA BASE, pointed established by Woolpert using static method.  In addition, one hundred four control points were surveyed through static methods.

Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET).  The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line.  The coverage was classified to extract a bare earth digital elevation model (DEM) and separate last returns.  

Four layers of coverage were delivered in the ArcINFO ArcGrid binary format: reflective surface, bare-earth, last return and intensity.  

System Parameters:

	- Type of Scanner = LH Systems ALS50
	- Data Acquisition Height = 5,000-feet AGL
	- Scanner Field of View = 25 degrees
	- Scan Frequency = 36 Hertz
	- Pulse Repetition Rate - 44.2 Kilohertz
	- Aircraft Speed = 122 KIAS
	- Swath Width = 2217-feet
	- Nominal Ground Sample Distance = 3.0-feet
	- Number of Returns Per Pulse = 2 (first and last)
	- Distance Between Flight Lines = 1,331-feet
</procdesc>
				<procdate>200712</procdate>
			</procstep>
			<procstep>
				<procdesc>System Calibration Procedure:

The ALS50 calibration and system performance is verified on a periodic basis using Woolpert's calibration range.  The calibration range consists of a large building and runway.  The edges of the building and control points along the runway have been located using conventional survey methods.  Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data against control points along the runway.  

Field calibration is performed on all flight lines to refine the IMU misalignment angles.  IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines.  The raw LiDAR data is reduced using the refined misalignment angles.
</procdesc>
				<procdate>200712</procdate>
			</procstep>
			<procstep>
				<procdesc>Post Processing Procedure:

Airborne GPS is differentially processed using the GrafNAV V4.20 software by Waypoint Consulting of Calgary, Alberta, Canada.  The PDOP and distance separation by day is as follows:

October 5, 2007 (New Tucson Base):
				Average PDOP = 1.5
Average Distance Separation: 85 km

October 6, 2007 (New Tucson Base):
				Average PDOP = 2.0
Average Distance Separation: 90 km

October 7, 2007 (Sasabe 0&amp;1 Base 1):
				Average PDOP = 2.0
Average Distance Separation: 30 km

October 8, 2007 (Sasabe 0&amp;1 Base 1):
				Average PDOP = 2.0
Average Distance Separation: 60 km

October 9, 2007 (Sasabe 0&amp;1 Base 1):
				Average PDOP = 1.8
Average Distance Separation: 40 km

October 10, 2007 (Sasabe 2 Base 1):
				Average PDOP = 2.0
Average Distance Separation: 40 km

October 11, 2007 (Sasabe 2 Base 1):
				Average PDOP = 2.0
Average Distance Separation: 40 km

October 12, 2007 (Sasabe 3 Z307):
				Average PDOP = 2.0
Average Distance Separation: 30 km

October 13, 2007 (Sasabe 3 Z307):
				Average PDOP = 1.8
Average Distance Separation: 30 km

October 14, 2007 (Sasabe 3 Z307):
				Average PDOP = 1.8
Average Distance Separation: 80 km

October 15, 2007 (Sasabe 4 YUMA BASE):
				Average PDOP = 1.8
Average Distance Separation: 80 km

IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. 

The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS &amp; Mapping Division of Atlanta, Georgia.

The classification and quality control (QC) of LiDAR data is carried out using a combination of Woolpert proprietary software and TerraScan software by Terrasolid Limited of Helinski, Finland. 
</procdesc>
				<procdate>200712</procdate>
			</procstep>
			<procstep>
				<procdesc>Data Consolidation and Review:  Raw LiDAR data is delivered to contractor by collector. Four layers of coverage were delivered in the ArcINFO ArcGrid binary format: reflective surface, bare-earth, last return and intensity. These tiles are converted &amp; merged into larger ESRI GRID files and reviewed for quality and consistency. Preliminary Bare Earth surface is reviewed and edited as required to remove or add features to bare earth surface as required by cartographic requirements</procdesc>
				<procdate>200712</procdate>
			</procstep>
			<procstep>
				<procdesc>Data Conversion: Merged tiles of ESRI GRID formatted data are converted to ERDAS Imagine image format.  Areas coded as NODATA in ESRI GRID format are converted to -999 in ERDAS IMG format.  IMG files are encoded with projection information for proper zone and datum as part of conversion process. Metadata is added.</procdesc>
				<procdate>200712</procdate>
			</procstep>
			<procstep><procdesc Sync="TRUE">Dataset copied.</procdesc><srcused Sync="TRUE">C:\LIDAR\Metadata\bare_earth</srcused><date Sync="TRUE">20071213</date><time Sync="TRUE">10431100</time></procstep><procstep><procdesc Sync="TRUE">Dataset copied.</procdesc><srcused Sync="TRUE">C:\LIDAR\Metadata\Mexican_Border\bare_earth</srcused><date Sync="TRUE">20071213</date><time Sync="TRUE">11465000</time></procstep><procstep><procdesc Sync="TRUE">Metadata imported.</procdesc><srcused Sync="TRUE">Q:\MexicanBorderAreas\Area_1\metadata\fgdc-checked\bare_earth.xml</srcused><date Sync="TRUE">20071213</date><time Sync="TRUE">11472800</time></procstep></lineage>
		<cloud>0</cloud>
	</dataqual>
	<spdoinfo>
		<direct Sync="TRUE">Raster</direct>
		<rastinfo>
			<rasttype Sync="TRUE">Pixel</rasttype>
			<rowcount Sync="TRUE">15454</rowcount>
			<colcount Sync="TRUE">24021</colcount>
			<vrtcount Sync="TRUE">1</vrtcount>
			<rastxsz Sync="TRUE">1.000000</rastxsz><rastysz Sync="TRUE">1.000000</rastysz><rastbpp Sync="TRUE">32</rastbpp><rastorig Sync="TRUE">Upper Left</rastorig><rastcmap Sync="TRUE">FALSE</rastcmap><rastcomp Sync="TRUE">Run-Length Encoding (ESRI)</rastcomp><rastband Sync="TRUE">1</rastband><rastdtyp Sync="TRUE">pixel RGB</rastdtyp><rastplyr Sync="TRUE">TRUE</rastplyr><rastifor Sync="TRUE"></rastifor></rastinfo>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<planci>
					<plance Sync="TRUE">row and column</plance>
					<coordrep>
						<absres Sync="TRUE">1.000000</absres>
						<ordres Sync="TRUE">1.000000</ordres>
					</coordrep>
					<plandu Sync="TRUE">meters</plandu>
				</planci>
				<gridsys><gridsysn Sync="TRUE">Universal Transverse Mercator</gridsysn><utm><utmzone Sync="TRUE">12</utmzone><transmer><sfctrmer Sync="TRUE">0.999600</sfctrmer><longcm Sync="TRUE">-111.000000</longcm><latprjo Sync="TRUE">0.000000</latprjo><feast Sync="TRUE">500000.000000</feast><fnorth Sync="TRUE">0.000000</fnorth></transmer></utm></gridsys></planar>
			<geodetic>
				<horizdn Sync="TRUE">D_WGS_1984</horizdn>
				<ellips Sync="TRUE">WGS_1984</ellips>
				<semiaxis Sync="TRUE">6378137.000000</semiaxis>
				<denflat Sync="TRUE">298.257224</denflat>
			</geodetic>
			<cordsysn><geogcsn Sync="TRUE">GCS_WGS_1984</geogcsn><projcsn Sync="TRUE">WGS_1984_UTM_Zone_12N</projcsn></cordsysn></horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988</altdatum>
				<altunits>meters</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
				<altres>.01</altres></altsys>
		</vertdef>
	</spref>
	<eainfo>
		<detailed>
			<enttyp>
				<enttypl>
Band_1</enttypl>
				<enttypd>Single Band Image - IMAGINE Format</enttypd><enttypds>ERDAS</enttypds></enttyp>
			<attr>
				<attrlabl>ObjectID</attrlabl>
				<attrdef>Internal feature number.</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<udom>Sequential unique whole numbers that are automatically generated.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>Value</attrlabl>
				<attrdef>Elevation value, in meters</attrdef>
				<attrdefs>ERDAS</attrdefs><attrdomv><rdom><rdommin>Unknown</rdommin><rdommax>Unknown</rdommax><attrunit>meters</attrunit><attrmres>.01</attrmres></rdom></attrdomv></attr>
			<attr>
				<attrlabl>Count</attrlabl>
				<attrdef>Number of cells with this value</attrdef><attrdefs>ERDAS</attrdefs><attrdomv><udom>Elevation statistics captured internally in IMAGINE data structure</udom></attrdomv></attr>
		</detailed>
	</eainfo>
	<distinfo>
		<resdesc>DVD</resdesc>
		<stdorder>
			<nondig>ERDAS Imagine format on DVD</nondig><fees>None</fees><ordering>Upon request from distributor.  Data release caveats may apply.</ordering><turnarnd>Variable</turnarnd><digform><digtinfo><transize Sync="TRUE">0.000</transize><dssize Sync="TRUE">0.000</dssize></digtinfo></digform></stdorder>
		<distliab>No warranty expressed or implied is made by provider regarding the utility or the data on any other system, nor shall the act of distribution constitute any such warranty.</distliab><distrib><cntinfo><cntperp><cntorg>TBD</cntorg></cntperp></cntinfo></distrib></distinfo>
	<metainfo>
		<metd Sync="TRUE">20071217</metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>USGS</cntorg>
					<cntper>TBD</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>Unknown</addrtype>
					<city>Unknown</city>
					<state>Unknown</state>
					<postal>Unknown</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>TBD</cntvoice>
			</cntinfo>
		</metc>
		<metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn>
		<metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv>
		<mettc Sync="TRUE">local time</mettc>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<langmeta Sync="TRUE">en</langmeta><metextns><onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink><metprof Sync="TRUE">ESRI Metadata Profile</metprof></metextns></metainfo>
	<Esri><ModDate>20071217</ModDate><ModTime>12314200</ModTime><CreaDate>20071213</CreaDate><CreaTime>11472800</CreaTime><SyncOnce>FALSE</SyncOnce><MetaID>{A37D010E-8A7E-453C-822B-E90AB7BF7B02}</MetaID><SyncDate>20071217</SyncDate><SyncTime>12314200</SyncTime></Esri><mdDateSt Sync="TRUE">20071217</mdDateSt><distInfo><distributor><distorTran><onLineSrc><linkage Sync="TRUE">file://\\ph40nsx5\v5$\PH\67481_USGS_Mexico\SAIC\Area_1\Area_1_Bare_earth\mb1_be_01.img</linkage><protocol Sync="TRUE">Local Area Network</protocol><orDesc Sync="TRUE">002</orDesc></onLineSrc><transSize Sync="TRUE">0.000</transSize></distorTran><distorFormat><formatName Sync="TRUE">Raster Dataset</formatName></distorFormat></distributor></distInfo><dataIdInfo><envirDesc Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350</envirDesc><dataLang><languageCode Sync="TRUE" value="en"></languageCode></dataLang><idCitation><resTitle Sync="TRUE">mb1_be_01.img</resTitle><presForm><PresFormCd Sync="TRUE" value="005"></PresFormCd></presForm></idCitation><spatRpType><SpatRepTypCd Sync="TRUE" value="002"></SpatRepTypCd></spatRpType><dataExt><geoEle><GeoBndBox esriExtentType="native"><westBL Sync="TRUE">216279</westBL><eastBL Sync="TRUE">240300</eastBL><northBL Sync="TRUE">3572712</northBL><southBL Sync="TRUE">3557258</southBL><exTypeCode Sync="TRUE">1</exTypeCode></GeoBndBox></geoEle></dataExt><geoBox esriExtentType="decdegrees"><westBL Sync="TRUE">-114.011532</westBL><eastBL Sync="TRUE">-113.75263</eastBL><northBL Sync="TRUE">32.261084</northBL><southBL Sync="TRUE">32.116038</southBL><exTypeCode Sync="TRUE">1</exTypeCode></geoBox></dataIdInfo><mdLang><languageCode Sync="TRUE" value="en"></languageCode></mdLang><mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName><mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer><mdChar><CharSetCd Sync="TRUE" value="004"></CharSetCd></mdChar><mdHrLv><ScopeCd Sync="TRUE" value="005"></ScopeCd></mdHrLv><mdHrLvName Sync="TRUE">dataset</mdHrLvName><refSysInfo><RefSystem><refSysID><identCode Sync="TRUE">WGS_1984_UTM_Zone_12N</identCode></refSysID></RefSystem></refSysInfo><spatRepInfo><GridSpatRep><numDims Sync="TRUE">2</numDims><cellGeo><CellGeoCd Sync="TRUE" value="002"></CellGeoCd></cellGeo><tranParaAv Sync="TRUE">1</tranParaAv><axDimProps><Dimen><dimName><DimNameTypCd Sync="TRUE" value="002"></DimNameTypCd></dimName><dimSize Sync="TRUE">24021</dimSize><dimResol><value Sync="TRUE">1</value><uom><UomLength><uomName Sync="TRUE">Meter</uomName><conversionToISOstandardUnit Sync="TRUE">1 Meter = 1 Meter(s)</conversionToISOstandardUnit></UomLength></uom></dimResol></Dimen><Dimen><dimName><DimNameTypCd Sync="TRUE" value="001"></DimNameTypCd></dimName><dimSize Sync="TRUE">15454</dimSize><dimResol><value Sync="TRUE">1</value><uom><UomLength><uomName Sync="TRUE">Meter</uomName><conversionToISOstandardUnit Sync="TRUE">1 Meter = 1 Meter(s)</conversionToISOstandardUnit></UomLength></uom></dimResol></Dimen></axDimProps></GridSpatRep></spatRepInfo></metadata>
