<?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>200605</pubdate>
				<title Sync="TRUE">honolulu_downtown_2d_buildings</title>
				<geoform Sync="TRUE">vector digital data</geoform>
				<pubinfo>
					<pubplace>Chantilly, VA</pubplace>
					<publish>Science Applications International Corp. (SAIC)</publish>
				</pubinfo>
				<othercit>Represents building "footprints" or outline of outermost perimeter of a contiguous building. Individual building features attributed with geometric dimensional information.</othercit>
				<ftname Sync="TRUE">honolulu_downtown_2d_buildings</ftname><onlink Sync="TRUE">\\144-vdu\lidar_temp\Honolulu\Delivery\honolulu_downtown_2d_buildings.shp</onlink></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. This raw LIDAR data was then exploited using SAIC proprietary Automated Feature Extraction software that automatically detects and delineates features present in the LIDAR data. These features include 3D building features, tree points and forest polygons. This file represents the outer extent or building "footprint" as detected in the LIDAR data</abstract>
			<purpose>LIDAR data is used for 3D visualization, elevation based analysis and for feature extraction.  Extracted features can be used for any analysis or visualization task that requires vector feature data.</purpose>
			<langdata Sync="TRUE">en</langdata></descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20051222</begdate>
					<enddate>20051229</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>Irregular</update>
		</status>
		<spdom>
			<bounding>
				<westbc>
-80.004598</westbc>
				<eastbc>
-79.852819</eastbc>
				<northbc>
32.927498</northbc>
				<southbc>
32.763719</southbc>
			</bounding>
			<lboundng><leftbc Sync="TRUE">591487.299823</leftbc><rightbc Sync="TRUE">638855.056818</rightbc><bottombc Sync="TRUE">2350890.098406</bottombc><topbc Sync="TRUE">2368997.229860</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>
				<themekt>Software driven extraction of geographic feature data</themekt>
				<themekey>Automated Feature Extraction</themekey>
			</theme>
			<theme>
				<themekt>Building footrpints attributed with height information to support viewing in a 3D environment</themekt>
				<themekey>2D Buildings</themekey>
			</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>
			</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>HI</placekey>
			</place>
			<place>
				<placekt>City name</placekt>
				<placekey>Honolulu</placekey>
			</place>
			<place>
				<placekt>Location description</placekt>
				<placekey>Downtown</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>National Geospatial-Intelligence Agency</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>physical address</addrtype>
					<address>12300 Sunrise Valley Drive</address>
					<city>Reston</city>
					<state>VA</state>
					<postal>20191</postal>
					<country>USA</country>
				</cntaddr>
			</cntinfo>
		</ptcontac>
		<datacred>National Geospatial-Intelligence Agency</datacred>
		<secinfo>
			<secclass>Unclassified</secclass>
		</secinfo>
		<native Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722</native>
		<natvform Sync="TRUE">Shapefile</natvform></idinfo>
	<dataqual>
		<logic>LIDAR data is processed using Automated Feature Extraction routines.  This software is tunable to produce consistent results from different LIDAR sources and collection locations.  For this collection area the software was run with the same settings for the entire extent of LIDAR data.  Following Automated Feature Extraction Q/C processes are used to verify consistency of automated extraction and perform any required manual editing.</logic>
		<complete>LIDAR data is processed using SAIC Automated Feature Extraction software.  Results of automated process are reviewed to verify consistancy and accuracy of feature extraction.  During review features may be added, deleted or modified to better represent the feature portrayed in the raw LIDAR data.  The goal of the process is to capture greater than 95% of building features greater than 8m x 8m in size.  In practice the software consistently exceeds this standard when processing high quality LIDAR data.</complete>
		<posacc>
			<horizpa>
				<horizpar>Estimated horizontal accuracy of extracted feature data.  Informal assessments indicate that horizontal accuracy is better than 2 m based on comparisons with ortho imagery.</horizpar>
				<qhorizpa>
					<horizpav>less than 1 m</horizpav>
				</qhorizpa>
				<qhorizpa>
					<horizpav>less than 5 m</horizpav>
					<horizpae>Estimated horizontal accuracy of extracted feature data.  Informal assessments indicate that horizontal accuracy is better than 2 m based on comparisons with ortho imagery.</horizpae>
				</qhorizpa>
			</horizpa>
			<vertacc>
				<vertaccr>The vertical accuracy was tested following the National Standards for Spatial Data Accuracy.  Based on a total of 61 points (53 QC checkpoints, and 8 GPS points), the average error between the bare earth LiDAR coverage and the control was 0.002 m with a root mean square error (RMSE) of 0.089 m.</vertaccr>
				<qvertpa>
					<vertaccv>0.002 m</vertaccv>
					<vertacce>Average error between Bare Earth LiDAR coverage and control</vertacce>
				</qvertpa>
				<qvertpa>
					<vertaccv>0.089 m</vertaccv>
					<vertacce>root mean square error (RMSE)</vertacce>
				</qvertpa>
			</vertacc>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<title>LIDAR Data Collection</title>
					</citeinfo>
				</srccite>
				<srcscale>3000</srcscale>
				<typesrc>DVD-ROM</typesrc>
				<srctime>
					<timeinfo>
						<rngdates>
							<begdate>20051222</begdate>
							<enddate>20051229</enddate>
						</rngdates>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>LIDAR</srccitea>
			</srcinfo>
			<procstep>
				<procdesc>Production Narrative:  

Using a LH Systems ALS50 Light Detection and Ranging LiDAR) system, 122 flight lines of high density (submeter ground sample distance) data were collected over Honolulu, HI area (approximately 395 square kilometers).  Two returns were recorded for each laser pulse along with an intensity value for each return.  One mission was flown over a seven days period:  on December 22, 23, 24, 25, 26 and 29th, 2005.  Two airborne global positioning system (GPS) base stations were used to support the LiDAR data acquisition: AFS1 and ZHN1, sites that Woolpert located using static GPS positioning methods.  In addition, eight control points were surveyed through real-time kinematic (RTK) methods, tied into NGS points  1 5, 161 2340 TIDAL 21, A 111, B 111, L 13, STATE SURVEY 4 22, WAIKIKI 3, ZHN B to support the final accuracy analysis.

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.</procdesc>
				<procdate>200512</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.

Post Processing Procedure:

Airborne GPS is differentially processed using the POSGPS V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada.  The PDOP and distance separation by day is as follows:

Mission 1 - December 22, 2005 (AFS1):
Average PDOP = 2.5
Average Distance Separation: 15 km

Mission 2 - December 22, 2005 (AFS1):          				                  
Average PDOP = 2.3
Average Distance Separation: 15 km

Mission 3 - December 23, 2005 (AFS1):	                 			            
Average PDOP = 2.5
Average Distance Separation: 20 km

Mission 4 - December 23 2005 (AFS1):	             			            
Average PDOP = 2
Average Distance Separation: 25 km

Mission 5 - December 24, 2005 (AFS1):		           					
Average PDOP = 2
Average Distance Separation: 15 km

Mission 6 - December 24, 2005 (AFS1):								Average PDOP = 2.5
Average Distance Separation: 18 km

Mission 7 - December 24, 2005 (AFS1):								Average PDOP = 2
Average Distance Separation: 15 km

Mission 8 - December 25, 2005 (AFS1):								Average PDOP = 1.6
Average Distance Separation: 25 km

Mission 9 - December 26, 2005 (AFS1):								Average PDOP = 3
Average Distance Separation: 20 km2

Mission 10 - December 26, 2005 (AFS1):								Average PDOP = 2.2
Average Distance Separation: 18 km

Mission 11 - December 26, 2005 (AFS1):								Average PDOP = 2.8
Average Distance Separation: 10 km

Mission 12 - December 29, 2005 (AFS1):								Average PDOP = 1.2
Average Distance Separation: 10 km

Mission 13 - December 29, 2005 (AFS1):								Average PDOP = 1.6
Average Distance Separation: 12 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>200512</procdate>
			</procstep>
			<procstep>
				<procdesc>Data Consolidation and Review:
Raw LiDAR data is delivered in small tiles in ESRI GRID format.  These tiles are merged into larger ESRI GRID files, limited by the 2.1GB limit of this format, 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>200605</procdate>
			</procstep>
			<procstep>
				<procdesc>Automated Feature Extraction:
Using proprietary SAIC software the raw LIDAR and Bare Earth model were processed to extract and attribute building and vegetation features.  Automated extraction was followed by detailed Q/C to verify completeness and accuracy of extraction.  Final Q/C'ed features were attributed with geometrically derived attributes based on feature extents, reflective surface DEM and Bare Earth DEM.</procdesc>
				<procdate>200605</procdate>
			</procstep>
			<procstep>
				<procdesc>Data Formatting and Q/C:
Extracted and attributed features were reviewed for completeness and consistency.  Projection information and metadata were added to final vector data files.</procdesc>
				<procdate>200605</procdate>
			</procstep>
			<procstep>
				<procdesc>Transfer to delivery media:
Data is transferred from hard-disk to DVD delivery media using a Primera Bravo DVD/CDROM disc publishing hardware.</procdesc>
				<procdate>200605</procdate>
			</procstep>
			<procstep><procdesc Sync="TRUE">Metadata imported.</procdesc><srcused Sync="TRUE">S:\Honolulu\Metadata\2d_buildings.xml</srcused><date Sync="TRUE">20060607</date><time Sync="TRUE">13420100</time></procstep></lineage>
		<cloud>none</cloud>
	</dataqual>
	<spdoinfo>
		<direct Sync="TRUE">Vector</direct>
		<ptvctinf>
			<sdtsterm Name="honolulu_downtown_2d_buildings">
				<sdtstype Sync="TRUE">G-polygon</sdtstype>
				<ptvctcnt Sync="TRUE">115123</ptvctcnt>
			</sdtsterm>
			<esriterm Name="honolulu_downtown_2d_buildings"><efeatyp Sync="TRUE">Simple</efeatyp><efeageom Sync="TRUE">Polygon</efeageom><esritopo Sync="TRUE">FALSE</esritopo><efeacnt Sync="TRUE">115123</efeacnt><spindex Sync="TRUE">FALSE</spindex><linrefer Sync="TRUE">FALSE</linrefer></esriterm></ptvctinf>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.000032</absres>
						<ordres>0.000032</ordres>
					</coordrep>
					<plandu>meters</plandu>
				</planci>
				<gridsys><gridsysn Sync="TRUE">Universal Transverse Mercator</gridsysn><utm><utmzone Sync="TRUE">4</utmzone><transmer><sfctrmer Sync="TRUE">0.999600</sfctrmer><longcm Sync="TRUE">-159.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>D_WGS_1984</horizdn>
				<ellips>WGS_1984</ellips>
				<semiaxis>6378137.000000</semiaxis>
				<denflat>298.257224</denflat>
			</geodetic>
			<cordsysn><geogcsn Sync="TRUE">GCS_WGS_1984</geogcsn><projcsn Sync="TRUE">WGS_1984_UTM_Zone_4N</projcsn></cordsysn></horizsys>
		<vertdef><altsys><altdatum>North American Vertical Datum of 1988</altdatum><altres>.1</altres><altunits>meters</altunits><altenc>Explicit elevation coordinate included with horizontal coordinates</altenc></altsys></vertdef></spref>
	<eainfo>
		<detailed Name="honolulu_downtown_2d_buildings">
			<enttyp>
				<enttypl Sync="TRUE">honolulu_downtown_2d_buildings</enttypl>
				<enttypt Sync="TRUE">Feature Class</enttypt><enttypc Sync="TRUE">115123</enttypc></enttyp>
			<attr>
				<attrlabl>FID</attrlabl>
				<attrdef>Internal feature number.</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<udom>Sequential unique whole numbers that are automatically generated.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>Shape</attrlabl>
				<attrdef>Feature geometry.</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<udom>Coordinates defining the features.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>MINHT_M</attrlabl>
				<attrdef>Minimum height of building (above ground), in meters. This is the arithmetic minimum difference between DEM and bare earth for all points within the entire building footprint. This value is not filtered to remove spurious values and is therefore sensitive to negative spikes and outliers. A single bad elevation value within the footprint can throw off the minimum.</attrdef>
				<attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">10</attwidth><atnumdec Sync="TRUE">2</atnumdec></attr>
			<attr>
				<attrlabl>LEN2D</attrlabl>
				<attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">10</attwidth><atnumdec Sync="TRUE">2</atnumdec><attrdef>Length of the building footprint polygon, in meters</attrdef></attr>
			<attr>
				<attrlabl>MAXHT_M</attrlabl>
				<attrdef>Maximum height above ground of building footprint, in meters. This is the arithmetric maximum difference between DEM and bare earth for all points within the entire building footprint. This is not a robust value and should only be used with caution, since the maximum operator is sensitive to outliers. A single bad elevation value within the footprint can throw off the maximum.</attrdef>
				<attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">10</attwidth><atnumdec Sync="TRUE">2</atnumdec></attr>
			<attr>
				<attrlabl>BASE_M</attrlabl>
				<attrdef>Mean elevation of base of building, in meters above sea level, based on the average elevation of all bare earth elevation data under the building footprint polygon.</attrdef>
				<attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr>
			<attr>
				<attrlabl>ID</attrlabl>
				<attrdef>Polygon ID number</attrdef>
				<attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr>
			<attr>
				<attrlabl>HGT2D</attrlabl>
				<attrdef>Median height of building footprint above ground level, based on the difference between the DEM and the bare earth model</attrdef>
				<attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">8</attwidth><atnumdec Sync="TRUE">2</atnumdec></attr>
			<attr>
				<attrlabl>WID2D</attrlabl>
				<attrdef>Width of the building footprint polygon, in meters</attrdef>
				<attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">8</attwidth><atnumdec Sync="TRUE">2</atnumdec></attr>
			<attr>
				<attrlabl Sync="TRUE">ARA2D</attrlabl>
				<attrdef>area of building footprint, in square meters</attrdef>
				<attalias Sync="TRUE">ARA2D</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr>
		</detailed>
	</eainfo>
	<distinfo>
		<distrib>
			<cntinfo>
				<cntorgp>
					<cntorg>National Geospatial-Intelligence Agency</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>physical address</addrtype>
					<address>12300 Sunrise Valley Drive</address>
					<city>Reston</city>
					<state>VA</state>
					<postal>20191</postal>
					<country>USA</country>
				</cntaddr>
			</cntinfo>
		</distrib>
		<resdesc>Downloadable Data</resdesc>
		<stdorder>
			<digform>
				<digtinfo>
					<transize>7.342</transize>
					<dssize Sync="TRUE">20.066</dssize></digtinfo>
			</digform>
		</stdorder>
	</distinfo>
	<metainfo>
		<metd Sync="TRUE">20060607</metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>National Geospatial-Intelligence Agency (NGA)</cntorg>
					<cntper>REQUIRED: The person responsible for the metadata information.</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>physical address</addrtype>
					<address>12300 Sunrise Valley Drive</address>
					<city>Reston</city>
					<state>VA</state>
					<postal>20191</postal>
					<country>VA</country>
				</cntaddr>
				<cntvoice>REQUIRED: The telephone number by which individuals can speak to the organization or individual.</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>
		<metsi>
			<metsc>Sensitive</metsc>
		</metsi>
		<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>20060607</ModDate><ModTime>14064200</ModTime><MetaID>{774B4AAD-24B0-4CAA-A9C9-C084240978C5}</MetaID><CreaDate>20060607</CreaDate><CreaTime>13420100</CreaTime><SyncOnce>FALSE</SyncOnce><SyncDate>20060607</SyncDate><SyncTime>14044100</SyncTime><DataProperties><lineage><Process Name="DefineProjection_19" ToolSource="C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\DefineProjection" Date="20060607" Time="134326">DefineProjection S:\Honolulu\Delivery\honolulu_downtown_2d_buildings.shp PROJCS['WGS_1984_UTM_Zone_4N',GEOGCS['GCS_WGS_1984',DATUM['D_WGS_1984',SPHEROID['WGS_1984',6378137.0,298.257223563]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Transverse_Mercator'],PARAMETER['False_Easting',500000.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-159.0],PARAMETER['Scale_Factor',0.9996],PARAMETER['Latitude_Of_Origin',0.0],UNIT['Meter',1.0]] S:\Honolulu\Delivery\honolulu_downtown_2d_buildings.shp</Process></lineage></DataProperties></Esri><mdDateSt Sync="TRUE">20060607</mdDateSt><dataIdInfo><envirDesc Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722</envirDesc><dataLang><languageCode Sync="TRUE" value="en"></languageCode></dataLang><idCitation><resTitle Sync="TRUE">honolulu_downtown_2d_buildings</resTitle><presForm><PresFormCd Sync="TRUE" value="005"></PresFormCd></presForm></idCitation><spatRpType><SpatRepTypCd Sync="TRUE" value="001"></SpatRepTypCd></spatRpType><dataExt><geoEle><GeoBndBox esriExtentType="native"><westBL Sync="TRUE">591487.299823</westBL><eastBL Sync="TRUE">638855.056818</eastBL><northBL Sync="TRUE">2368997.22986</northBL><southBL Sync="TRUE">2350890.098406</southBL><exTypeCode Sync="TRUE">1</exTypeCode></GeoBndBox></geoEle></dataExt><geoBox esriExtentType="decdegrees"><westBL Sync="TRUE">-158.118217</westBL><eastBL Sync="TRUE">-157.660266</eastBL><northBL Sync="TRUE">21.42098</northBL><southBL Sync="TRUE">21.254391</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><distInfo><distributor><distorTran><onLineSrc><orDesc Sync="TRUE">002</orDesc><linkage Sync="TRUE">file://\\144-vdu\lidar_temp\Honolulu\Delivery\honolulu_downtown_2d_buildings.shp</linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc><transSize Sync="TRUE">20.066</transSize></distorTran><distorFormat><formatName Sync="TRUE">Shapefile</formatName></distorFormat></distributor></distInfo><spatRepInfo><VectSpatRep><topLvl><TopoLevCd Sync="TRUE" value="001"></TopoLevCd></topLvl><geometObjs Name="honolulu_downtown_2d_buildings"><geoObjTyp><GeoObjTypCd Sync="TRUE" value="001"></GeoObjTypCd></geoObjTyp><geoObjCnt Sync="TRUE">115123</geoObjCnt></geometObjs></VectSpatRep></spatRepInfo><refSysInfo><RefSystem><refSysID><identCode Sync="TRUE">WGS_1984_UTM_Zone_4N</identCode></refSysID></RefSystem></refSysInfo></metadata>
