<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20250613</CreaDate>
<CreaTime>08573700</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">HYDRO_Ponds_2024</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">165792.964502</westBL>
<eastBL Sync="TRUE">274495.380955</eastBL>
<southBL Sync="TRUE">1701250.000041</southBL>
<northBL Sync="TRUE">1798073.371026</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</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_Indiana_East_FIPS_1301_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/3.5.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_2011_StatePlane_Indiana_East_FIPS_1301_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;Transverse_Mercator&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,328083.3333333333],PARAMETER[&amp;quot;False_Northing&amp;quot;,820208.3333333333],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-85.66666666666667],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9999666666666667],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,37.5],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,6459]],VERTCS[&amp;quot;NAVD88_height_(ftUS)&amp;quot;,VDATUM[&amp;quot;North_American_Vertical_Datum_1988&amp;quot;],PARAMETER[&amp;quot;Vertical_Shift&amp;quot;,0.0],PARAMETER[&amp;quot;Direction&amp;quot;,1.0],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,6360]]&lt;/WKT&gt;&lt;XOrigin&gt;-18119800&lt;/XOrigin&gt;&lt;YOrigin&gt;-45615400&lt;/YOrigin&gt;&lt;XYScale&gt;3048.0060960121928&lt;/XYScale&gt;&lt;ZOrigin&gt;-1000000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;0&lt;/MOrigin&gt;&lt;MScale&gt;1&lt;/MScale&gt;&lt;XYTolerance&gt;0.0032808333333333331&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.0032808333333333331&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;103041&lt;/WKID&gt;&lt;LatestWKID&gt;6459&lt;/LatestWKID&gt;&lt;VCSWKID&gt;105703&lt;/VCSWKID&gt;&lt;LatestVCSWKID&gt;6360&lt;/LatestVCSWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20260729</SyncDate>
<SyncTime>14434700</SyncTime>
<ModDate>20260729</ModDate>
<ModTime>14434700</ModTime>
</Esri>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Jacob Mark</rpIndName>
<rpOrgName>Dewberry Engineers Inc.</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>562-512-2143</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>1000 N Ashley Drive, Suite 801</delPoint>
<city>Tampa</city>
<adminArea>FL</adminArea>
<postCode>33602</postCode>
<eMailAdd>jmark@dewberry.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt>20260113</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>Joan Keene</rpIndName>
<rpOrgName>Hamilton County GIS</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>317-776-8254</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>1 Hamilton County Square, Suite 63</delPoint>
<city>Noblesville</city>
<adminArea>IN</adminArea>
<postCode>46060</postCode>
<country>US</country>
<eMailAdd>Joan.Keene@hamiltoncounty.in.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<resFees>None</resFees>
</distorOrdPrc>
<distorFormat>
<formatName>Digital Data</formatName>
</distorFormat>
<distorTran>
<onLineSrc>
<linkage>https://geohub.hamiltoncounty.in.gov/</linkage>
</onLineSrc>
</distorTran>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>https://geohub.hamiltoncounty.in.gov</linkage>
</onLineSrc>
</distTranOps>
<distFormat>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle>Elevation-Derived Hydrography for Hamilton County, Indiana</resTitle>
<date>
<pubDate>2026-01-13</pubDate>
</date>
<citRespParty>
<rpOrgName>Hamilton County GIS</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Dewberry Engineers, Inc.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</idCitation>
<idAbs>This dataset is Elevation-Derived Hydrography (EDH) for Hamilton County located in Indiana. The EDH contains line features representing streams and rivers and polygons representing waterbodies. The EDH was derived from a 2-foot lidar-derived Digital Elevation Model (DEM), acquired in 2024. This dataset meets the requirements of the USGS Elevation-Derived Hydrography Data Acquisition Specifications (2023 rev. A2) and READ Rules. The line features contain Elevation Class (EClass) codes useful for hydro-enforcement, including culvert identification. Feature Class (FClass) and Feature Codes (FCodes) are hydrography codes compatible with the National Hydrography Dataset (NHD), now retired. </idAbs>
<idPurp> The purpose of this Elevation-Derived Hydrography (EDH) dataset is to support Hamilton County's geospatial, planning, and water resource management workflows with an accurate, current, and 3D-integrated hydrographic representation. The data were developed from high-resolution QL1 lidar in accordance with USGS 3D Hydrography Program (3DHP) specifications. This vector hydrography content improves upon historic NHD datasets by offering more spatially accurate flowlines and waterbody features derived directly from recent lidar elevation surfaces. The EDH dataset is being integrated with Hamilton County's existing inventories of Legal Drains, Storm Sewer Networks, and Wetlands to support advanced hydrologic modeling, drainage assessment, regulatory compliance, and infrastructure planning. It also supports flood risk analysis, watershed delineation, culvert and outfall mapping, and long-term environmental planning. Hamilton County plans to contribute the eight (8) complete HUC-12 areas in Hamilton County to the USGS National Geospatial Program (NGP) through the "USGS 3DNTM Data Collaboration Announcement (DCA)" for integration into the USGS 3D National Topographic Model (3DNTM).</idPurp>
<idCredit>Hamilton County GIS, Dewberry Engineers Inc., United States Geological Survey</idCredit>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>Jacob Mark</rpIndName>
<rpOrgName>Dewberry Engineers Inc.</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>562-512-2143</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>1000 N Ashley Drive, Suite 801</delPoint>
<city>Tampa</city>
<adminArea>FL</adminArea>
<postCode>33602</postCode>
<eMailAdd>jmark@dewberry.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</resMaint>
<placeKeys>
<keyword>United States</keyword>
<keyword>Indiana</keyword>
<keyword>Hamilton County</keyword>
<keyword>05120201</keyword>
</placeKeys>
<themeKeys>
<keyword>inlandWaters</keyword>
<keyword>elevation</keyword>
<thesaName>
<resTitle>ISO 19115 Topic Category</resTitle>
</thesaName>
</themeKeys>
<themeKeys>
<keyword>hydrography</keyword>
<keyword>lidar</keyword>
<keyword>connector</keyword>
<keyword>indefinite surface connector</keyword>
<keyword>culvert</keyword>
<keyword>terrain breach</keyword>
<keyword>canal/ditch</keyword>
<keyword>dam/weir</keyword>
<keyword>lake/pond</keyword>
<keyword>stream/river</keyword>
<keyword>drainageway</keyword>
<keyword>artificial path</keyword>
</themeKeys>
<themeKeys>
<keyword>3DNTM</keyword>
<keyword>3DEP</keyword>
<keyword>QL1 Lidar</keyword>
<keyword>3DHP</keyword>
<keyword>EDH</keyword>
<thesaName>
<resTitle>USGS Program</resTitle>
</thesaName>
</themeKeys>
<searchKeys>
<keyword>inlandWaters</keyword>
<keyword>elevation</keyword>
<keyword>hydrography</keyword>
<keyword>lidar</keyword>
<keyword>connector</keyword>
<keyword>indefinite surface connector</keyword>
<keyword>culvert</keyword>
<keyword>terrain breach</keyword>
<keyword>canal/ditch</keyword>
<keyword>dam/weir</keyword>
<keyword>lake/pond</keyword>
<keyword>stream/river</keyword>
<keyword>drainageway</keyword>
<keyword>artificial path</keyword>
<keyword>3DNTM</keyword>
<keyword>3DEP</keyword>
<keyword>QL1 Lidar</keyword>
<keyword>3DHP</keyword>
<keyword>EDH</keyword>
<keyword>United States</keyword>
<keyword>Indiana</keyword>
<keyword>Hamilton County</keyword>
<keyword>05120201</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>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. Acknowledgement of the Hamilton County GIS Department would be appreciated for products derived from these data.</useLimit>
</Consts>
</resConst>
<resConst>
<LegConsts>
<useLimit>None. However, users are advised to read the EDH metadata thoroughly to understand appropriate use and data limitations. 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. Acknowledgement of Hamilton County GIS would be appreciated for products derived from these data. See access and use constraints information on GeoHub.</useLimit>
<accessConsts>
<RestrictCd value="008"/>
</accessConsts>
<othConsts>No restrictions apply to these data.</othConsts>
</LegConsts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<tpCat>
<TopicCatCd value="006"/>
</tpCat>
<tpCat>
<TopicCatCd value="012"/>
</tpCat>
<envirDesc>ArcGIS Pro; Arc Hydro; Dewberry Proprietary Scripts and QA Tools</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox>
<exTypeCode>true</exTypeCode>
<westBL>-86.2614570</westBL>
<eastBL>-85.8433670</eastBL>
<northBL>40.2347181</northBL>
<southBL>39.9176352</southBL>
</GeoBndBox>
</geoEle>
<vertEle>
<vertMinVal Sync="TRUE">697.710000</vertMinVal>
<vertMaxVal Sync="TRUE">898.140000</vertMaxVal>
</vertEle>
</dataExt>
<dataExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2023-12-21</tmBegin>
<tmEnd>2025-11-24</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
<vertEle>
<vertMinVal Sync="TRUE">697.710000</vertMinVal>
<vertMaxVal Sync="TRUE">898.140000</vertMaxVal>
</vertEle>
<geoEle/>
</dataExt>
<suppInfo>This task order involves the development of EDH products, including a complete hydrographic network and hydro-enforced DEMs for Hamilton County. The project area covers approximately 485 square miles of area in Indiana.</suppInfo>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-86.247513</westBL>
<eastBL Sync="TRUE">-85.857722</eastBL>
<northBL Sync="TRUE">40.184798</northBL>
<southBL Sync="TRUE">39.917717</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
</dataIdInfo>
<mdConst>
<Consts>
<useLimit>None.</useLimit>
</Consts>
</mdConst>
<mdConst>
<LegConsts>
<accessConsts>
<RestrictCd value="008"/>
</accessConsts>
<othConsts>None.</othConsts>
</LegConsts>
</mdConst>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQQuanAttAcc">
<measDesc>Attribute accuracy report contains information about ancillary data used to aid in attribution of features. The attributes were verified by comparison to the original National Hydrography Dataset attributes. Corrections to attribution are based, at the minimum, on elevation source data. All features contain attributes defined in the USGS Elevation-Derived Hydrography Data Acquisition Specifications and Elevation-Derived Hydrograhy-READ Rules.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>All area and line features meet 3DHP topology rules. Points, nodes, lines, and areas conform to topological rules. Lines intersect only at nodes, and all nodes anchor the ends of lines. Lines do not overshoot or undershoot other lines where they are supposed to meet. There are no duplicate lines. Gaps and overlaps among areas do not exist. The EDH was compared to the lidar-source bare-earth Digital Elevation Model and channels present within the surface that meet minimum mapping requirements were added to the EDH. The EDH was compared to the original NHD for the study area and any feature from the NHD that did not have a channel representation in the DEM was not added to the EDH. Stream connectivity was checked and any isolated networks were verified using a Geomorphic Index (GMI) coincident with the DEM. Features without clear channels present in the DEM are allowed if needed for connectivity between upstream and downstream features and have been added as indefinite surface connectors.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>The completeness of the data is relative to the DEM from which the EDH was derived, and must match the DEM. The goal of this product is to be vertically and horizontally integrated with the bare earth DEM. Published NHD is used as a guide for feature extraction and densification, but was not used as a source to verify the presence or absence of features.</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>All stream/river linear features have been placed within a channel of the bare earth DEM. Waterbody features have been placed at the limit or banks of the waterbody. All waterbody features were iteratively smoothed. Hydro-flattening is present in the source DEM, waterbodies and stream/river area features match the hydro-flattening breakline extent.</measDesc>
</report>
<report dimension="vertical" type="DQAbsExtPosAcc">
<measDesc>All features have z-values associated with every vertex. Waterbodies are flat, with a single z-value, at or just below the surface of the DEM at the edge of the polygon, assigned to all vertices. Linear features are flat or flow consistently downstream. Z-values are at, or just below, the surface of the DEM. Exceptions are allowed for connector features and features with no evidence of interaction, e.g. pipelines. Any other exceptions to vertical alignment, e.g. exceptions required to maintain monotonicity, are documented in the project report. There are 38 indefinite surface connectors and 38 connectors that are not monotonic and are attributed with a FlowClass of 2 to maintain connectivity.</measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>Dewberry used a generalized 11-step workflow to derive high-resolution EDH products. We designed our hydrographic models to derive channelized features from the DEM that generally conform with the existing NHD features, density guidelines, and/or are supported by various derivative surface models, including geomorphons. The workflow incorporated components from Esri ArcGIS Pro with Arc Hydro, and proprietary scripting to produce flowlines, conflate the flowlines to the elevation model, assuring complete network connectivity and monotonicity, attributing the flowlines to meet required specifications, constructing FGDC-compliant metadata, and internally provide quality assurance. As part of our QA workflow, Esri ArcGIS Data Reviewer checks are used to validate the geometry. The workflow included: 1. Supplementing 3DEP breaklines by collecting additional features meeting EDH collection requirements but which were not collected as part of the original 3DEP Task Order. 2. Locate culvert and other flow-disrupting features. Specifically, to locate culverts for the AOI, Dewberry used the existing, hydro-flattened DEM and derived a preliminary flowline network using a flow accumulation threshold significantly larger than that used for high-resolution flowline extraction. This resulted in a generalized network of features that are most likely to be impacted by culverts. This network was manually reviewed against the DEM, GMI, orthoimagery, road network and government furnished stormwater data to identify culverts and other flow-disrupting features. 3. The newly compiled breaklines and culvert data were assessed with the existing breaklines and available culvert and storm drain data and then used to re-process a hydro-flattened DEM to construct a hydro-conditioned DEM for feature extraction. 4. Extracting flowlines, using a proprietary workflow, at a resolution to achieve the target density specification for the AOI. 5. Flowlines were filtered and thinned based on standard USGS 3DHP guidance along with Hamilton County specific guidance and criteria. 6. The resulting geometric flow network was topologically/cartographically smoothed, with small flowlines removed (pruned), and the remaining network examined for flow backups (dams). 7. Once the flow network was complete, Dewberry refined the artificial flow paths using proprietary techniques that are compatible with USGS specifications ensuring connectivity through waterbodies and depressions. These final lines were smoothed appropriately and thinned to meet project density guidelines. 8. Upon successful completion of all network connectivity checks, the DEM elevations were assigned to the flowlines and monotonicity was enforced. 9. The flowlines, flow paths, and waterbodies are attributed to 3DHP specifications. Flowlines were attributed as stream/river/canal/ditch or indefinite surface connector based on the Geomorphic Index raster developed using the USGS guidelines. 10. FGDC-compliant metadata were developed and checked using the USGS Metadata parser. 11. A final quality review was performed on datasets prior to delivery. This review includes a complete set of checklists that are reviewed by independent reviewers. Checks include, but are not limited to, a comprehensive review of the EDH flowlines for completeness, verification of connectivity (2D and 3D) and downstream flow to a single pour point via ArcGIS Pro Trace Network tools, review of differences between the EDH and existing NHD (including review of the omissions.gdb to ensure any omitted existing NHD features are not represented in the EDH and are acceptable as omissions), horizontal alignment within GMI channels, vertical alignment, within specified tolerances, between EDH vector data and source DEMs, monotonicity and various topology checks (2D and 3D). Lastly, all documentation is independently reviewed.
</stepDesc>
<stepDateTm>2025-09-30</stepDateTm>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>3DEP OPR DEM, 3DEP breaklines, GMI, NHD, Local Storm Drain Inventories</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>As mentioned in steps 2 and 11 above, the GMI was utilized in conjunction with the DEM to identify channelized features and ensure horizontal alignment of EDH within GMI channels. The GMI raster was created by Dewberry using the USGS preferred model for GMI generation. First, the Feature Preserving Smoothing (FPS) tool is run in ArcGIS Pro to remove noise in the DEM. Next, the WhiteboxTools Multiscale Elevation Profile tool (now available in ArcGIS Pro) is used with the FPS raster as the input to measure the local topographic position of cells as a percentile range, and the lowest 10th percentile of the surface is extracted as an input to the GMI. Then, BotHat is used to filter the FPS raster based on two different neighborhood sizes of 3x3 and 11x11; the lowest elevation areas from the smaller 3x3 neighborhood that are also present within the 11x11 neighborhood are retained as channelized areas. Then the WhiteboxTools Geomorphons tool (now also available in ArcGIS Pro) is run with the FPS raster as the input DEM; the tool is run twice to create the geomorphon valley raster and geomorphon ridge raster. Last, WhiteboxTools D-Infinity flow direction and flow accumulation (now also available in ArcGIS Pro) steps are run on the FPS raster. The binary raster outputs from the four steps above are run in a tool to create the final GMI output. GMI values range from 0 (nodata) where no indicators are present, to 4 when all input rasters indicate a possible channel.</stepDesc>
<stepDateTm>2025-09-30</stepDateTm>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>3DEP OPR DEM</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<dataSource>
<srcDesc>Bare-Earth Digital Elevation Model (DEM) used for generating point, line, and polygon vector water features; identifying flat water bodies; and populating z-values.</srcDesc>
<srcMedName>
<MedNameCd value="digital"/>
</srcMedName>
<srcCitatn>
<resTitle>Hamilton County, Indiana 2024 Orthophotography and Lidar Basemap Project</resTitle>
<resAltTitle>DEM</resAltTitle>
<date>
<pubDate>2024-08-30</pubDate>
</date>
<citRespParty>
<rpOrgName>Dewberry</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>raster digital data</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2024-08-30</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>Originally delineated hydrography. Used as the guide for minimum set of features to capture for EDH. </srcDesc>
<srcMedName>
<MedNameCd value="digital"/>
</srcMedName>
<srcCitatn>
<resTitle>National Hydrography Dataset (NHDPlus HR)</resTitle>
<resAltTitle>NHD</resAltTitle>
<date>
<pubDate>2019-02-08</pubDate>
</date>
<citRespParty>
<rpOrgName>USGS</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<otherCitDet>USGS National Map</otherCitDet>
<citOnlineRes>
<linkage>https://apps.nationalmap.gov/downloader/</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2019-02-08</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>Used to validate culvert placement.</srcDesc>
<srcMedName>
<MedNameCd value="digital"/>
</srcMedName>
<srcCitatn>
<resTitle>Hamilton County, Indiana 2024 Orthophotography and Lidar Basemap Project</resTitle>
<resAltTitle>3-band orthoimagery</resAltTitle>
<date>
<pubDate>2024-08-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Dewberry</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>remote-sensing image</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2024-08-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="HYDRO_Ponds_2024">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">68</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<eainfo>
<overview>
<eaover>Hydrographic features collected as part of this AOI were generated, processed, and attributed according to USGS Elevation-Derived Hydrography Data Acquisition Specifications (2023 rev. A2) and READ Rules which is available online at https://www.usgs.gov/ngp-standards-and-specifications/elevation-derived-hydrography-data-acquisition-specifications. </eaover>
<eadetcit>USGS Elevation-Derived Hydrography Data Acquisition Specifications (2023 rev. A2) and READ Rules which is available online at https://www.usgs.gov/ngp-standards-and-specifications/elevation-derived-hydrography-data-acquisition-specifications. </eadetcit>
</overview>
<detailed Name="HYDRO_Ponds_2024">
<enttyp>
<enttypl Sync="FALSE">HYDRO_Ponds_2024</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">68</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Comments</attrlabl>
<attalias Sync="TRUE">Comments</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Desc_</attrlabl>
<attalias Sync="TRUE">Desc</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">EClass</attrlabl>
<attalias Sync="TRUE">EClass</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">FClass</attrlabl>
<attalias Sync="TRUE">FClass</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Limitation</attrlabl>
<attalias Sync="TRUE">Limitation</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Method</attrlabl>
<attalias Sync="TRUE">Method</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Source</attrlabl>
<attalias Sync="TRUE">Source</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">128</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">UniqueID</attrlabl>
<attalias Sync="TRUE">UniqueID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">UserCode</attrlabl>
<attalias Sync="TRUE">UserCode</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">FCode</attrlabl>
<attalias Sync="TRUE">FCode</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape.STArea()</attrlabl>
<attalias Sync="TRUE">Shape.STArea()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape.STLength()</attrlabl>
<attalias Sync="TRUE">Shape.STLength()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<subtype>
<stname Sync="TRUE">Stream/river</stname>
<stcode Sync="TRUE">46000</stcode>
</subtype>
<subtype>
<stname Sync="TRUE">Lake/pond</stname>
<stcode Sync="TRUE">39000</stcode>
</subtype>
<subtype>
<stname Sync="TRUE">Sea/ocean</stname>
<stcode Sync="TRUE">44500</stcode>
</subtype>
<subtype>
<stname Sync="TRUE">Dam/weir</stname>
<stcode Sync="TRUE">34300</stcode>
</subtype>
<subtype>
<stname Sync="TRUE">User-defined feature</stname>
<stcode Sync="TRUE">0</stcode>
<stfield>
<stfldnm Sync="TRUE">EClass</stfldnm>
<stflddd>
<domname Sync="TRUE">EClass</domname>
<domdesc Sync="TRUE">A short integer one-digit code indicating whether a feature is not used for elevation derivatives; used for hydroflattening or for other nonspecified elevation purposes; used for hydroflattening; or an elevation dataset limitation feature.</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">DBO</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">FClass</stfldnm>
<stflddd>
<domname Sync="TRUE">FClass</domname>
<domdesc Sync="TRUE">A short integer one-digit code defining whether a feature is intended for use as an NHD feature (1, will be used for conflation), a non-NHD feature (2, outside of the collection criteria and not intended to be used for conflation), or a nonhydrography feature (3, elevation dataset limitation).</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">DBO</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">Playa</stname>
<stcode Sync="TRUE">36100</stcode>
</subtype>
<subtype>
<stname Sync="TRUE">Canal/ditch</stname>
<stcode Sync="TRUE">33600</stcode>
</subtype>
<subtype>
<stname Sync="TRUE">Ice mass</stname>
<stcode Sync="TRUE">37800</stcode>
<stfield>
<stfldnm Sync="TRUE">EClass</stfldnm>
<stflddd>
<domname Sync="TRUE">EClass</domname>
<domdesc Sync="TRUE">A short integer one-digit code indicating whether a feature is not used for elevation derivatives; used for hydroflattening or for other nonspecified elevation purposes; used for hydroflattening; or an elevation dataset limitation feature.</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">DBO</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">FClass</stfldnm>
<stflddd>
<domname Sync="TRUE">FClass</domname>
<domdesc Sync="TRUE">A short integer one-digit code defining whether a feature is intended for use as an NHD feature (1, will be used for conflation), a non-NHD feature (2, outside of the collection criteria and not intended to be used for conflation), or a nonhydrography feature (3, elevation dataset limitation).</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">DBO</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">Limitation</stfldnm>
<stflddd>
<domname Sync="TRUE">Limitation</domname>
<domdesc Sync="TRUE">A short integer one-digit code that indicates whether the source elevation contained limitations that create issues meeting vertical or horizontal requirements for the hydrography feature.</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">DBO</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
</subtype>
</detailed>
</eainfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="6459"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.2.10(10.3.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="HYDRO_Ponds_2024">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">68</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
