<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<metadata xml:lang="en">
<Esri>
<CreaDate>20180118</CreaDate>
<CreaTime>12372000</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">DSM_2015_5FT</itemName>
<nativeExtBox>
<westBL Sync="TRUE">2483463.481864</westBL>
<eastBL Sync="TRUE">2553468.481864</eastBL>
<southBL Sync="TRUE">309993.815800</southBL>
<northBL Sync="TRUE">445008.815800</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<itemLocation>
<linkage Sync="TRUE">file://\\spl103wpi3\e$\arcgisserver\data\elevation\dsm_hillshade_2015\dsm_hillshade_2015.gdb</linkage>
<protocol Sync="TRUE">Local Area Network</protocol>
</itemLocation>
<imsContentType Sync="TRUE">002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_NAD_1983_2011</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803_Ft_US</projcsn>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.7'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803_Ft_US&amp;quot;,GEOGCS[&amp;quot;GCS_NAD_1983_2011&amp;quot;,DATUM[&amp;quot;D_NAD_1983_2011&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,1968500.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-90.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,42.73333333333333],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,44.06666666666667],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,42.0],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,6609]]&lt;/WKT&gt;&lt;XOrigin&gt;-118121300&lt;/XOrigin&gt;&lt;YOrigin&gt;-97418300&lt;/YOrigin&gt;&lt;XYScale&gt;37501932.948264509&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.0032808333333333331&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;103191&lt;/WKID&gt;&lt;LatestWKID&gt;6609&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
<lineage>
<Process Date="20220330" Time="145013" ToolSource="c:\program files (x86)\arcgis\desktop10.7\ArcToolbox\Toolboxes\Data Management Tools.tbx\CopyRaster">CopyRaster "Database Connections\sql60wpchc_CNTYRASTER.sde\CNTYRASTER.GISADMIN.DSM_2015_5FT" U:\elevation\dsm_hillshade_2015\dsm_hillshade_2015.gdb\DSM_2015_5FT # # -3.402823e+38 NONE NONE # NONE NONE "Esri Grid" NONE</Process>
</lineage>
</DataProperties>
<SyncDate>20220330</SyncDate>
<SyncTime>14500900</SyncTime>
<ModDate>20220330</ModDate>
<ModTime>14500900</ModTime>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>ItemDescription</ArcGISProfile>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Sarah Zibart</rpIndName>
<rpOrgName>Quantum Spatial</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>859-277-8700</voiceNum>
<faxNum>859-277-8901</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>523 Wellington Way</delPoint>
<city>Lexington</city>
<adminArea>KY</adminArea>
<postCode>40503</postCode>
<country>US</country>
<eMailAdd>szibart@quantumspatial.com</eMailAdd>
</cntAddress>
<cntHours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</cntHours>
<cntInstr>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntInstr>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20220330</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<dataIdInfo>
<idCitation>
<resTitle Sync="FALSE">dsm_hillshade_2015</resTitle>
<date>
<pubDate>2016-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Southeastern Wisconsin Regional Planning Commission</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<fgdcGeoform>Lidar point cloud</fgdcGeoform>
<PresFormCd Sync="TRUE" value="011"/>
</presForm>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Geographic Extent: Milwaukee, Ozaukee, Walworth, Washington, and Waukesha Counties in southeastern Wisconsin, covering approximately 2,071 square miles. Dataset Description: The SEWRPC 2015 LiDAR project called for the Planning, Acquisition, processing and derivative products of LIDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LIDAR Specification, Version 1.2. The primary set of deliverable data was developed based on the following two horizontal projection/datum systems as specified in the contract: NAD27 State Plane Wisconsin South Zone, US survey feet; NGVD29, US survey feet for Milwaukee, Ozaukee, and Walworth Counties NAD83 (2011) State Plane Wisconson South Zone, US survey feet; NAVD88, US survey feet for Washington and Waukesha Counties LiDAR data was delivered in RAW flight line swath format, and processed to create Classified LAS 1.2 Files formatted to individual 10,000-foot x 10,000-foot tiles. Tile counts are listed below: Milwaukee: 89 tiles in NAD27 Ozaukee: 85 tiles Walworth: 192 tiles Washington: 146 tiles in NAD83 (2011) Waukesha: 187 tiles Corresponding hydro-flattened Digital Terrain Model (DTM) files were created in Esri file geodatabase format. 1-foot contours were created from the hydro-flattened digital terrain model data and delivered in Esri file geodatabase format. Additionally, a secondary set of unclassified and classified lidar data was developed for the following counties: Washington County: 154 tiles in NAD27 State Plane Wisconsin South Zone, US survey feet; NGVD29, US survey feet Milwaukee County: 91 tiles in NAD83 State Plane Wisconson South Zone, US survey feet; NAVD88 (2011), US survey feet Ground Conditions: LiDAR collection began in Spring 2015, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications, Quantum Spatial established a total of 127 QC points that were used to calibrate the LIDAR to known ground locations established throughout the project area.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>2015 DSM Hillshade. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Breaklines and DTMs. The purpose of these lidar...</idPurp>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>John DiGiovanni</rpIndName>
<rpOrgName>Quantum Spatial, Data Acquisition Department</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>859-277-8700</voiceNum>
<faxNum>859-277-8901</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>523 Wellington Way</delPoint>
<city>Lexington</city>
<adminArea>KY</adminArea>
<postCode>40503</postCode>
<country>US</country>
<eMailAdd>jdigiovanni@quantumspatial.com</eMailAdd>
</cntAddress>
<cntHours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</cntHours>
<cntInstr>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntInstr>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="011"/>
</maintFreq>
</resMaint>
<placeKeys>
<keyword>Milwaukee</keyword>
<keyword>Waukesha</keyword>
<keyword>Ozaukee</keyword>
<keyword>Washington</keyword>
<keyword>Wisconsin</keyword>
<keyword>Walworth</keyword>
</placeKeys>
<themeKeys>
<keyword>Lidar</keyword>
<keyword>Elevation data</keyword>
<keyword>Hydrology</keyword>
</themeKeys>
<searchKeys>
<keyword>Milwaukee</keyword>
<keyword>Waukesha</keyword>
<keyword>Ozaukee</keyword>
<keyword>Washington</keyword>
<keyword>Lidar</keyword>
<keyword>Elevation data</keyword>
<keyword>Wisconsin</keyword>
<keyword>Hydrology</keyword>
<keyword>Walworth</keyword>
</searchKeys>
<resConst>
<LegConsts>
<othConsts>No restrictions apply to this data.</othConsts>
</LegConsts>
</resConst>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</envirDesc>
<dataExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2015-03-24</tmBegin>
<tmEnd>2015-05-07</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-88.7954451566949</westBL>
<eastBL>-87.7552048758465</eastBL>
<southBL>42.4669599815093</southBL>
<northBL>43.5669587735573</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-88.080010</westBL>
<eastBL Sync="TRUE">-87.805873</eastBL>
<northBL Sync="TRUE">43.204614</northBL>
<southBL Sync="TRUE">42.829541</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idCredit>Milwaukee County Land Information Office</idCredit>
<tpCat>
<TopicCatCd value="006"/>
</tpCat>
</dataIdInfo>
<mdConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>None.</classSys>
<handDesc>NONE</handDesc>
</SecConsts>
</mdConst>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQConcConsis">
<measDesc>Data cover the entire area specified for this project.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>These raw LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and data passes Nonvegetated Vertical Accuracy specifications.</measDesc>
</report>
<report dimension="vertical" type="DQAbsExtPosAcc">
<measDesc>The specifications require that only Fundamental Vertical Accuracy (FVA) be computed for raw lidar point cloud swath files. The vertical accuracy was tested with 37 independent survey located in open terrain. These check points were not used in the calibration or post processing of the lidar point cloud data. The survey checkpoints were distributed throughout the project area. Specifications for this project require that the RMSEz be 0.5 feet or better.</measDesc>
<evalMethDesc>The FVA was tested using 37 independent survey located in open terrain. The survey checkpoints were distributed throughout the project area. The 37 independent check points were surveyed using GPS techniques. See survey report for additional survey methodologies. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control. The RMSEz was computed to be 0.041 meters (0.135 feet) and AccuracyZ to be 0.080 meters (0.264 feet). RMSEz has been tested to 0.5 feet or better per the task order specifications. AccuracyZ has been tested to meet 18.13 cm Fundamental Vertical Accuracy at 95 Percent confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</evalMethDesc>
<measResult>
<QuanResult>
<quanVal>0.041</quanVal>
</QuanResult>
</measResult>
</report>
<dataLineage>
<dataSource>
<srcDesc>This data source was used to populate the lidar point cloud data.</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>Lidar RAW Data for SEWRPC QL2 2015</resTitle>
<resAltTitle>SEWRPC_QL2_2015_LiDAR_Data</resAltTitle>
<date>
<pubDate>2015-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>2015</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Quantum Spatial</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Quantum Spatial</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<fgdcGeoform>lidar data</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2015-03-24</tmBegin>
<tmEnd>2015-05-07</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>This data source was used (along with the airborne GPS/IMU Data) to aid in the georeferencing of the lidar point cloud data.</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>Control Survey Report of LiDAR Ground Control Points</resTitle>
<resAltTitle>SEWRPC_QL2_2015_LiDAR_gnd_ctrl</resAltTitle>
<date>
<pubDate>2015-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Quantum Spatial</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Lexington, KY</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Quantum Spatial</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2015-04-22</tmBegin>
<tmEnd>2015-05-08</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>This data source was used to QC and vertically adjust the lidar point cloud data.</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>Control Survey Report of LiDAR Quality Control Points</resTitle>
<resAltTitle>SEWRPC_QL2_2015_LiDAR_qc_ctrl</resAltTitle>
<date>
<pubDate>2015-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Quantum Spatial</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Lexington, KY</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Quantum Spatial</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2015-04-22</tmBegin>
<tmEnd>2015-05-08</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<prcStep>
<stepDesc>Classified LAS Processing: The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro flattened breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 3 feet was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All bridge decks were classified to Class 14. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was identified using the Overlap Flag, per LAS 1.2 specifications. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Quantum Spatial proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.</stepDesc>
<stepDateTm>2016-01-01</stepDateTm>
<stepProc>
<rpIndName>Paul Bishop</rpIndName>
<rpOrgName>Quantum Spatial</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>859-277-8700</voiceNum>
<faxNum>859-277-8901</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>523 Wellington Way</delPoint>
<city>Lexington</city>
<adminArea>KY</adminArea>
<postCode>40503</postCode>
<country>US</country>
<eMailAdd>pbishop@quantumspatial.com</eMailAdd>
</cntAddress>
<cntHours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</cntHours>
<cntInstr>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntInstr>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>SEWRPC_QL2_2015_LiDAR_Data</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>SEWRPC_QL2_2015_LiDAR_qc_ctrl</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>Classified LAS</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs>
<geoObjTyp>
<GeoObjTypCd value="004"/>
</geoObjTyp>
</geometObjs>
</VectSpatRep>
</spatRepInfo>
<distInfo>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Raster Dataset</formatName>
</distFormat>
</distInfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="6609"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.9.3(10.3.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spdoinfo>
<rastinfo>
<rasttype Sync="TRUE">Pixel</rasttype>
<rowcount Sync="TRUE">27003</rowcount>
<colcount Sync="TRUE">14001</colcount>
<rastxsz Sync="TRUE">5.000000</rastxsz>
<rastysz Sync="TRUE">5.000000</rastysz>
<rastbpp Sync="TRUE">32</rastbpp>
<vrtcount Sync="TRUE">1</vrtcount>
<rastorig Sync="TRUE">Upper Left</rastorig>
<rastcmap Sync="TRUE">FALSE</rastcmap>
<rastcomp Sync="TRUE">LZ77</rastcomp>
<rastband Sync="TRUE">1</rastband>
<rastdtyp Sync="TRUE">pixel codes</rastdtyp>
<rastifor Sync="TRUE">FGDBR</rastifor>
<rastplyr Sync="TRUE">TRUE</rastplyr>
</rastinfo>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">row and column</plance>
<coordrep>
<absres Sync="TRUE">5.000000</absres>
<ordres Sync="TRUE">5.000000</ordres>
</coordrep>
</planci>
</planar>
</horizsys>
</spref>
</metadata>
