<?xml version="1.0" encoding="UTF-8"?><metadata>
<Esri>
<CreaDate>20150204</CreaDate>
<CreaTime>14201900</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20251114</SyncDate>
<SyncTime>11145100</SyncTime>
<ModDate>20251114</ModDate>
<ModTime>14442800</ModTime>
<ArcGISFormat>1.0</ArcGISFormat>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">NHDStreamOrderLegacyVersionForChapter483_B</itemName>
<nativeExtBox>
<westBL Sync="TRUE">626409.195312</westBL>
<eastBL Sync="TRUE">1466563.711458</eastBL>
<southBL Sync="TRUE">-148633.456771</southBL>
<northBL Sync="TRUE">1035562.959375</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<itemSize Sync="TRUE">46.539</itemSize>
<imsContentType export="False">002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_New_Hampshire_FIPS_2800_Feet</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_StatePlane_New_Hampshire_FIPS_2800_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&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;,984250.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-71.66666666666667],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9999666666666667],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,42.5],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,3437]]&lt;/WKT&gt;&lt;XOrigin&gt;-17463700&lt;/XOrigin&gt;&lt;YOrigin&gt;-48257000&lt;/YOrigin&gt;&lt;XYScale&gt;3048.0060960121928&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;102710&lt;/WKID&gt;&lt;LatestWKID&gt;3437&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<scaleRange>
<minScale>100000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>FGDC</ArcGISProfile>
</Esri>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdHrLvName>dataset</mdHrLvName>
<mdContact>
<rpIndName>GRANIT Database Manager</rpIndName>
<rpOrgName>Earth Systems Research Center, University of New Hampshire</rpOrgName>
<rpPosName>GRANIT Database Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<eMailAdd>granit@unh.edu</eMailAdd>
<delPoint>Morse Hall, University of New Hampshire</delPoint>
<city>Durham</city>
<adminArea>NH</adminArea>
<postCode>03824</postCode>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>603-862-1214</voiceNum>
</cntPhone>
<cntHours>8:30AM-5PM, EST</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20251114</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distTranOps>
<onLineSrc>
<linkage>withheld</linkage>
</onLineSrc>
<transSize Sync="FALSE">71.4</transSize>
</distTranOps>
<distFormat>
<formatName>Shapefile</formatName>
</distFormat>
<distributor>
<distorCont>
<rpIndName>GRANIT Database Manager</rpIndName>
<rpOrgName>Earth Systems Research Center, University of New Hampshire</rpOrgName>
<rpPosName>GRANIT Database Manager</rpPosName>
<role>
<RoleCd value="005"/>
</role>
<rpCntInfo>
<cntAddress addressType="both">
<eMailAdd>granit@unh.edu</eMailAdd>
<delPoint>Morse Hall, University of New Hampshire</delPoint>
<city>Durham</city>
<adminArea>NH</adminArea>
<postCode>03824</postCode>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>603-862-1214</voiceNum>
</cntPhone>
<cntHours>8:30AM-5PM. EST</cntHours>
</rpCntInfo>
</distorCont>
<distorOrdPrc>
<resFees>No charge when downloaded from the Internet. Cost of reproduction for provision on CD/ROM of other media.</resFees>
<ordInstr>Email GRANIT (granit@unh.edu) or order from web site (www.granit.sr.unh.edu).</ordInstr>
<ordTurn>Two weeks.</ordTurn>
</distorOrdPrc>
<distorFormat>
<formatName>SHP</formatName>
<formatTech>None.</formatTech>
</distorFormat>
<distorTran>
<transSize>17.5 MB</transSize>
<onLineSrc>
<linkage>withheld</linkage>
</onLineSrc>
</distorTran>
</distributor>
</distInfo>
<dataIdInfo>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The New Hampshire Hydrography Dataset (NHHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the state's surface water drainage system. The NHHD, developed at 1:24,000 scale, is an extract from the high-resolution National Hydrography Dataset (NHD) housed at the US Geological Survey. The NHHD Shapefile Extract contains the NHDFlowline feature class from the original NHHD geodatabase. The shapefile covers the extent of the sixteen cataloging units that intersect the State of NH, and contain reach codes for networked features, stream order, flow direction, names, and centerline representations for areal water bodies. However, because this data is no longer contained in the original geodatabase, the networking capabilities of the NHDFlowline has been lost.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idCitation>
<resTitle>NHD Stream Order Legacy Version For Chapter 483-B</resTitle>
<date>
<pubDate>2006-01</pubDate>
</date>
<presForm>
<PresFormCd value="005"/>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<collTitle>NH GRANIT Database</collTitle>
<citRespParty>
<rpOrgName>Earth Systems Research Center, University of New Hampshire</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
<rpCntInfo>
<cntAddress addressType="postal">
<city>Durham</city>
<adminArea>NH</adminArea>
<postCode>03824</postCode>
</cntAddress>
</rpCntInfo>
</citRespParty>
<citRespParty>
<rpOrgName>Earth Systems Research Center, University of New Hampshire</rpOrgName>
<rpCntInfo>
<cntAddress addressType="postal">
<eMailAdd>granit@unh.edu</eMailAdd>
<city>Durham</city>
<adminArea>NH</adminArea>
<postCode>03824</postCode>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>603-862-1214</voiceNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
</idCitation>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-73.0244471345705</westBL>
<eastBL>-69.7932891534469</eastBL>
<northBL>45.2853234029577</northBL>
<southBL>42.0783826960364</southBL>
<exTypeCode>true</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>1956</tmBegin>
<tmEnd>2005</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-73.058099</westBL>
<eastBL Sync="TRUE">-69.791460</eastBL>
<northBL Sync="TRUE">45.340867</northBL>
<southBL Sync="TRUE">42.078383</southBL>
<exTypeCode>1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<idPoC>
<rpIndName>GRANIT Database Manager</rpIndName>
<rpOrgName>Earth Systems Research Center, University of New Hampshire</rpOrgName>
<rpPosName>GRANIT Database Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<eMailAdd>granit@unh.edu</eMailAdd>
<delPoint>Morse Hall, University of New Hampshire</delPoint>
<city>Durham</city>
<adminArea>NH</adminArea>
<postCode>03824</postCode>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>603-862-1214</voiceNum>
</cntPhone>
<cntHours>8:30AM-5PM, EST</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<searchKeys>
<keyword>NHHD</keyword>
<keyword>NHD</keyword>
<keyword>Hydrography</keyword>
<keyword>Surface Water</keyword>
<keyword>Streams</keyword>
<keyword>Rivers</keyword>
<keyword>Lakes</keyword>
<keyword>Ponds</keyword>
<keyword>Reservoirs</keyword>
<keyword>Wetlands</keyword>
<keyword>Swamps</keyword>
<keyword>Marshes</keyword>
<keyword>Network</keyword>
<keyword>Drainage</keyword>
<keyword>Centerlines</keyword>
<keyword>Artificial Paths</keyword>
<keyword>Transport Arcs</keyword>
<keyword>Reaches</keyword>
<keyword>Reach Codes</keyword>
<keyword>Stream Orders</keyword>
<keyword>Strahler</keyword>
<keyword>United States</keyword>
<keyword>Northeast</keyword>
<keyword>New England</keyword>
<keyword>New Hampshire</keyword>
</searchKeys>
<themeKeys>
<keyword>NHHD</keyword>
<keyword>NHD</keyword>
<keyword>Hydrography</keyword>
<keyword>Surface Water</keyword>
<keyword>Streams</keyword>
<keyword>Rivers</keyword>
<keyword>Lakes</keyword>
<keyword>Ponds</keyword>
<keyword>Reservoirs</keyword>
<keyword>Wetlands</keyword>
<keyword>Swamps</keyword>
<keyword>Marshes</keyword>
<keyword>Network</keyword>
<keyword>Drainage</keyword>
<keyword>Centerlines</keyword>
<keyword>Artificial Paths</keyword>
<keyword>Transport Arcs</keyword>
<keyword>Reaches</keyword>
<keyword>Reach Codes</keyword>
<keyword>Stream Orders</keyword>
<keyword>Strahler</keyword>
</themeKeys>
<idPurp>These data are extracted from a legacy version of the NHHD dataset and include stream orders retained for NH DES permitting purposes relating to the SHORELAND WATER QUALITY PROTECTION ACT (see Chapter 483-B). The data may also be used to construct municipal, regional or statewide base maps.</idPurp>
<idCredit>GRANIT database</idCredit>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Stream order as determined by the Strahler method is dependent upon the scale and accuracy of the hydrographic network that is being ordered. The primary data source for assigning stream orders to the 1:24,000-scale vector flowlines was the USGS digital line graphs (DLGs), representing blue line features on the 1:24,000-scale topographic maps. Given the acknowledged inaccuracies in the attribution of intermittent versus perennial hydrographic features as depicted on these maps, all blue line features were included as part of the drainage network and subject to ordering. This approach is consistent with the Strahler method as originally proposed. However, some of these data were subsequently modified in an attempt to account for known differences in drainage density in limited areas of the state where density differences could reasonably be attributed to cartographic representation by the DLGs and not physical differences in geology and/or hydrology. Specifically, areas where DLGs were digitized from provisional 1:25,000-scale 7.5x15-minute metric source maps exhibited a significantly higher drainage density than contiguous areas. Strahler stream order is very sensitive to drainage density and the overall consistency with which blue line features are defined and mapped. To enforce consistency in drainage density in those areas with provisional map coverage, the drainage network was systematically pruned based on an empirical upstream drainage area threshold value that was representative of the initiation points (network starts) of blue line features in neighboring areas. Ordering was performed on the pruned network in these areas. The resulting order values represent the best characterization possible given the limitations in the currency, accuracy and resolution of the source data, and serve the expressed goal of providing a meaningful parameter that can support hydrologic assessments of relative stream discharge and classifications of channel geometry. The 1:24,000-scale flowline network has not been subject to rigorous ground-truthing and, therefore, is subject to significant errors of omission, inclusion, and connectivity. Users of these data should be aware that any such error has the potential to significantly affect the stream order of downstream reaches. Furthermore, errors in the network have been discovered since the ordering was completed and additional errors are likely to be identified over time as more and more users with local hydrographic knowledge reference the dataset. The vector flowlines will be revised accordingly, but no plan exists to maintain the associated stream order attributes to be consistent with modified geometry. Significant differences exist between stream orders as assigned in this dataset and those assigned in an earlier version (1995) by the NH Office of State Planning (now the Office of Energy and Planning). Users should carefully consider their objectives when deciding which dataset to reference, given that some limitations apply in both cases. An understanding of the specific data sources and methods, as documented above and in the accompanying metadata records, is critical for appropriate application of the stream order dataset.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<resConst>
<LegConsts>
<accessConsts>
<RestrictCd value="008"/>
</accessConsts>
<useLimit>Digital data in NH GRANIT represent the efforts of the contributing agencies to record information from the cited source materials. Earth Systems Research Center, under contract to the NH Department of Business and Economic Development, and in consultation with cooperating agencies, maintains a continuing program to identify and correct errors in these data. OEP, CSRC, and the cooperating agencies make no claim as to the validity or reliability or to any implied uses of these data.</useLimit>
<othConsts>None.</othConsts>
</LegConsts>
</resConst>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<envirDesc>ArcGIS 9.x</envirDesc>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<resMaint>
<maintFreq>
<MaintFreqCd value="011"/>
</maintFreq>
</resMaint>
<aggrInfo>
<aggrDSName>
<resTitle>NH GRANIT Database</resTitle>
<date>
<pubDate>1986-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Earth Systems Research Center, University of New Hampshire</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Earth Systems Research Center, University of New Hampshire</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Durham, New Hampshire</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citOnlineRes>
<linkage>withheld</linkage>
</citOnlineRes>
</aggrDSName>
<assocType>
<AscTypeCd value="002"/>
</assocType>
</aggrInfo>
<aggrInfo>
<aggrDSName>
<resTitle>New Hampshire Geological Survey</resTitle>
<citRespParty>
<rpOrgName>New Hampshire Department of Environmental Services</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>New Hampshire Department of Environmental Services</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Concord, NH</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citOnlineRes>
<linkage>http://www.des.state.nh.us</linkage>
</citOnlineRes>
</aggrDSName>
<assocType>
<AscTypeCd value="001"/>
</assocType>
</aggrInfo>
<placeKeys>
<keyword>United States</keyword>
<keyword>Northeast</keyword>
<keyword>New England</keyword>
<keyword>New Hampshire</keyword>
</placeKeys>
<tpCat>
<TopicCatCd value="012"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</maintFreq>
<maintNote>Last metadata review date: 2007-04</maintNote>
</mdMaint>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<dataLineage>
<dataSource type="">
<srcDesc>Spatial and attribute information</srcDesc>
<srcMedName>
<MedNameCd value="001"/>
</srcMedName>
<srcScale>
<rfDenom>24000</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>1:24000 Digital Line Graphs</resTitle>
<resAltTitle>USGS1</resAltTitle>
<citRespParty>
<rpOrgName>US Geological Survey</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>US Geological Survey</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Reston, VA</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="006"/>
</presForm>
<presForm>
<fgdcGeoform>map</fgdcGeoform>
</presForm>
<collTitle>National Cartographic Database</collTitle>
<citOnlineRes>
<linkage>http://edcsns17.cr.usgs.gov/EarthExplorer/</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>1956</tmBegin>
<tmEnd>2002</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>8 and 12-Digit HUCs</srcDesc>
<srcMedName>
<MedNameCd value="001"/>
</srcMedName>
<srcScale>
<rfDenom>24000</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Level 6 Hydrologic Unit Boundaries for New Hampshire</resTitle>
<resAltTitle>NRCS</resAltTitle>
<date>
<pubDate>2001</pubDate>
</date>
<citRespParty>
<rpOrgName>US Department of Agriculture, Natural Resources Conservation Service</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>US Department of Agriculture, Natural Resources Conservation Service</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Fort Worth, Texas</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="map, table"/>
</presForm>
<presForm>
<fgdcGeoform>map, table</fgdcGeoform>
</presForm>
<citOnlineRes>
<linkage>http://www.nrcs.usda.gov/</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2001</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>reference for digitizing connectors</srcDesc>
<srcMedName>
<MedNameCd value="001"/>
</srcMedName>
<srcScale>
<rfDenom>24000</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>1:24000 Digital Raster Graphics</resTitle>
<resAltTitle>USGS2</resAltTitle>
<citRespParty>
<rpOrgName>US Geological Survey</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>US Geological Survey</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Reston, VA</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="006"/>
</presForm>
<presForm>
<fgdcGeoform>map</fgdcGeoform>
</presForm>
<collTitle>National Cartographic Database</collTitle>
<citOnlineRes>
<linkage>http://edcsns17.cr.usgs.gov/EarthExplorer/</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>1956</tmBegin>
<tmEnd>2002</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Reach codes and flow direction attributes.</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcScale>
<rfDenom>100000</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>100K National Hydrography Dataset</resTitle>
<resAltTitle>USGS3</resAltTitle>
<date>
<pubDate>1999</pubDate>
</date>
<citRespParty>
<rpOrgName>US Geological Survey in cooperation with the U.S. Environmental Protection Agency</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>US Geological Survey</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Reston, VA</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="006"/>
</presForm>
<presForm>
<fgdcGeoform>map</fgdcGeoform>
</presForm>
<collTitle>National Cartographic Database</collTitle>
<citOnlineRes>
<linkage>http://nhd.usgs.gov/data.html</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Names for reaches and areal water bodies.</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>Geographic Names Information System Oracle Database</resTitle>
<resAltTitle>USGS4</resAltTitle>
<citRespParty>
<rpOrgName>US Geological Survey</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>US Geological Survey</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Reston, VA</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="006"/>
</presForm>
<presForm>
<fgdcGeoform>map</fgdcGeoform>
</presForm>
<collTitle>National Cartographic Database</collTitle>
<citOnlineRes>
<linkage>http://www.usgs.gov/</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Spatial processing</srcDesc>
<srcMedName>
<MedNameCd value="digital file"/>
</srcMedName>
<srcScale>
<rfDenom>24000</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Digital Elevation Model</resTitle>
<resAltTitle>USGS5</resAltTitle>
<citRespParty>
<rpOrgName>US Geological Survey</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>US Geological Survey</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Reston, VA</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="006"/>
</presForm>
<presForm>
<fgdcGeoform>map</fgdcGeoform>
</presForm>
<collTitle>National Cartographic Database</collTitle>
<citOnlineRes>
<linkage>http://ned.usgs.gov/</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>1979-01-01T00:00:00</tmBegin>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<prcStep>
<stepDesc>Pre-conflation
Using a suite of tools provided by the USGS, the DLG quads for each 11-digit CU were paneled into one coverage and arcs within 40 feet of each other along the neatline were again snapped together if the feature types were the same. Next, the 11-digit Hydrologic Unit Code (HUC) boundary was used to extract features from the paneled coverage that fell within the boundary. Next, arcs from the extracted coverage were grouped in order to examine the connectivity of the dataset for flow determination. In some cases it was necessary to correct digitizing errors. Using contour lines from the New Hampshire Digital Raster Graphics, lines called connectors were added to join features that were deemed to have flow between each other. All arcs were directed downstream and the nodes were prepared to help create artificial paths through 2-D waterbodies and complete the flow through the hydrography network. The artificial path coverage was combined with the single line stream network to create the drainage network. The drainage network was grouped again, and each group was directed downstream. The data was then appended to conform to the 8-digit CU boundaries. Feature codes (fcodes) were assigned to network and waterbody features through a crosswalk that converts DLG-3 attributes to fcodes, where an fcode is a five digit integer that encodes a set of feature type characteristics. At this point, all spatial and attribute data were QC'd by staff at both CSRC and the NH Department of Environmental Services.
Conflation/Post-conflation:
Then, reach codes and associated attributes were conflated from the 100K NHD data to the 24K drainage network and 2-D waterbodies. Several checks were performed to validate the reach transfer process. Any reach codes that could not be maintained are tracked in the Reach Cross Reference table. New reaches that do not exist in the 100K data were defined according to reach delineation rules (See http://nhd.usgs.gov/chapter1/index.html). New waterbody reaches were assigned to 2-D lake/pond and reservoir features that do not exist in the 100K NHD. New reaches were assigned reach code values that are sequentially ordered to 2-D and then 1-D reaches. New 24K reach codes are larger than any existing 100K reach code in the associated Catalog Unit. Additional Geographic Names that exist in the Geographic Names Information System (GNIS) were added to reaches in the 24K dataset. Names for the 24K drainage network were interactively transferred from the vector GNIS coverage. Additional GNIS names for waterbody features were also added.</stepDesc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>NRCS, USGS1, USGS2, USGS3, USGS4</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>Due to a higher feature density resulting from a smaller mapping scale in Southwest NH and the White Mountain National Forest, the stream network generated from pre-conflation in these areas was "pruned" prior to the stream ordering process. This was accomplished through the following steps using ArcInfo and Grid tools: - Burned the stream network into a Digital Elevation Model. - Ran the FLOW ACCUMULATION command using a threshold value that produced a rasterized stream network matching the 1:24000 scale stream density representative of the majority of the state. - The grid resulting from the FLOW ACCUMULATION was visually compared to the stream network in the high density areas to determine which streams would not receive a stream order. Streams that were not to be ordered were retained in the data, but were "pruned" by assigning a flag value.</stepDesc>
<stepDateTm>2000-01-01T00:00:00</stepDateTm>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>USGS1,USGS5</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>DLG files were converted to ArcInfo coverages and projected to the New Hampshire State Plane coordinate system (NHSP NAD83 Feet). Attributes were standardized to ensure consistent number of MAJOR/MINOR pairs. Attributes were also verified, using one or more of the following methods: manual comparison of the source with hardcopy plots; symbolized display of the digital line graph on an interactive computer graphic system; selected attributes that could not be visually verified on plots or on screen were interactively queried and verified on screen. The DLG coverages were edgematched using a 40 foot snapping tolerance. Features outside the tolerance were not moved; instead, a feature of type connector was added to join the features.</stepDesc>
<stepDateTm>2000-01-01T00:00:00</stepDateTm>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>USGS1</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>Using the Strahler method, stream orders were manually assigned to the "pruned" pre-conflation data using ArcEdit tools. The following additional rules were applied to the stream ordering process: - Artificial paths in lakes and reservoirs received the value of the outflowing stream. The out flowing stream (and artificial paths) were coded one order higher if two streams of the same order flowed into the waterbody. - Divergent paths received the order of the stream immediately upstream from the divergent path. Stream order only increased if a tributary of higher or equal order flowed into a divergent path. - Features that did not receive a stream order were "pruned" streams, coastline arcs and pipelines. - Streams that originate in tidal wetlands were coded as first order streams. Stream orders were QC'd by staff at CSRC and NHDES.</stepDesc>
<stepDateTm>2005-01-01T00:00:00</stepDateTm>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>USGS1</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>Once the NHD was certified and downloaded from USGS, the streams orders were spatially joined and transferred to the NHDFlowline feature class. However, due to spatial edits to the NHD during the conflation process, the stream order data required editing to spatially match the NHD before the attribute could be transferred. Modifications were made in ArcGIS, using standard editing tools.</stepDesc>
<stepDateTm>2006-01-01T00:00:00</stepDateTm>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>USGS1</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>The NHDFlowline, NHDWaterbody and NHDArea feature classes were extracted from each geodatabase and mosaicked into a statewide dataset in ArcSDE. These feature classes were then exported back out of ArcSDE into shapefiles.</stepDesc>
<stepDateTm>2007-01-01T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
<report type="DQQuanAttAcc">
<measDesc>One or more of the following methods were used to test attribute accuracy of the source USGS Digital Line Graph data: manual comparison of the source with hardcopy plots; symbolized display of the digital line graph on an interactive computer graphic system; selected attributes that could not be visually verified on plots or on screen were interactively queried and verified on screen. In addition, software validated feature types (FCODEs) and characteristics against a master set of types and characteristics, checked that combinations of types and characteristics were valid, and that types and characteristics were valid for the delineation of the feature. Feature types, characteristics, and other attributes conform to the Standards for National Hydrography Dataset (USGS, 1999) as of the date they were loaded into the database. All names were validated against a current extract from the Geographic Names Information System (GNIS). The entry and identifier for the names match those in the GNIS. The association of each name to reaches has been interactively checked, however, operator error could in some cases apply a name to a wrong reach.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>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. Lines bound areas and lines identify the areas to the left and right of the lines. Gaps and overlaps among areas do not exist. All areas close.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>Data is complete for the hydrologic cataloging unit. The completeness of the data reflects the content of the source (the published USGS topographic quadrangles). The USGS topographic quadrangle is usually supplemented by Digital Orthophoto Quadrangles (DOQs). Features found on the ground may have been eliminated or generalized on the source map because of scale and legibility constraints. In general, streams longer than one mile (approximately 1.6 kilometers) were collected. Most streams that flow from a lake were collected regardless of their length. Only definite channels were collected so not all swamp/marsh features have stream/rivers delineated through them. Lake/ponds having an area greater than 6 acres were collected. Note, however, that these general rules were applied unevenly among maps during compilation. Reach codes are defined on all features of type stream/river, canal/ditch, artificial path, coastline, and connector. Waterbody reach codes are defined on all lake/pond and most reservoir features. Names were applied from the GNIS database. Detailed capture conditions are provided for every feature type in the Standards for National Hydrography Dataset available online through &lt;http://mapping.usgs.gov/standards/&gt;.</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>Statements of horizontal positional accuracy are based on accuracy statements made for U.S. Geological Survey topographic quadrangle maps. These maps were compiled to meet National Map Accuracy Standards. For horizontal accuracy, this standard is met if at least 90 percent of points tested are within 0.02 inch (at map scale) of the true position. Additional offsets to positions may have been introduced where feature density is high to improve the legibility of map symbols. In addition, the digitizing of maps is estimated to contain a horizontal positional error of less than or equal to 0.003 inch standard error (at map scale) in the two component directions relative to the source maps. Visual comparison between the map graphic (including digital scans of the graphic) and plots or digital displays of points, lines, and areas, is used as control to assess the positional accuracy of digital data. Digital map elements along the adjoining edges of data sets are aligned if they are within a 0.02 inch tolerance (at map scale). Features with like dimensionality (for example, features that all are delineated with lines), with or without like characteristics, that are within the tolerance are aligned by moving the features equally to a common point. Features outside the tolerance are not moved; instead, a feature of type connector is added to join the features.</measDesc>
</report>
<report dimension="vertical" type="DQAbsExtPosAcc">
<measDesc>Statements of vertical positional accuracy for elevation of water surfaces are based on accuracy statements made for U.S. Geological Survey topographic quadrangle maps. These maps were compiled to meet National Map Accuracy Standards. For vertical accuracy, this standard is met if at least 90 percent of well-defined points tested are within one-half contour interval of the correct value. Elevations of water surface printed on the published map meet this standard; the contour intervals of the maps vary. These elevations were transcribed into the digital data; the accuracy of this transcription was checked by visual comparison between the data and the map.</measDesc>
</report>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="NHDStreamOrderLegacyVersionForChapter483_B">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="3437"/>
<idCodeSpace>EPSG</idCodeSpace>
<idVersion>6.12(9.3.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<eainfo>
<detailed Name="NHDStreamOrderLegacyVersionForChapter483_B">
<enttyp>
<enttypl>NHDStreamOrderLegacyVersionForChapter483_B</enttypl>
<enttypd>stream network</enttypd>
<enttypds>None</enttypds>
<enttypt>Feature Class</enttypt>
<enttypc>120779</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">0</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>Shape</attrlabl>
<attalias>Shape</attalias>
<attrtype>Geometry</attrtype>
<attwidth>0</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
<attrdef>Feature geometry.</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>ComID</attrlabl>
<attalias>ComID</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>FDate</attrlabl>
<attalias>FDate</attalias>
<attrtype>Date</attrtype>
<attwidth>8</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>Resolution</attrlabl>
<attalias>Resolution</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>GNIS_ID</attrlabl>
<attalias>GNIS_ID</attalias>
<attrtype>String</attrtype>
<attwidth>10</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>GNIS_Name</attrlabl>
<attalias>GNIS_Name</attalias>
<attrtype>String</attrtype>
<attwidth>65</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>LengthKM</attrlabl>
<attalias>LengthKM</attalias>
<attrtype>Double</attrtype>
<attwidth>8</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>ReachCode</attrlabl>
<attalias>ReachCode</attalias>
<attrtype>String</attrtype>
<attwidth>14</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>FlowDir</attrlabl>
<attalias>FlowDir</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>WBAreaComI</attrlabl>
<attalias>WBAreaComI</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>FType</attrlabl>
<attalias>FType</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>FCode</attrlabl>
<attalias>FCode</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>Enabled</attrlabl>
<attalias>Enabled</attalias>
<attrtype>SmallInteger</attrtype>
<attwidth>2</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>StreamOrde</attrlabl>
<attalias>StreamOrde</attalias>
<attrtype>SmallInteger</attrtype>
<attwidth>2</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
<attrdef>Stahler stream orders</attrdef>
<attrdefs>CSRC/NHDES</attrdefs>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd> first order stream</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
<edom>
<edomv>2</edomv>
<edomvd> second order stream</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
<edom>
<edomv>3</edomv>
<edomvd> third order stream</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
<edom>
<edomv>4</edomv>
<edomvd> fourth order stream</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>5</edomv>
<edomvd>fifth order stream</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>6</edomv>
<edomvd>sixth order stream</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>7</edomv>
<edomvd>seventh order stream</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>-97</edomv>
<edomvd> pipeline - no stream order</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
<edom>
<edomv>-98</edomv>
<edomvd> coastline - no stream order</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
<edom>
<edomv>-99</edomv>
<edomvd> "pruned" - no stream order</edomvd>
<edomvds>ESRC/NHDES</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>SHAPE_Leng</attrlabl>
<attalias>SHAPE_Leng</attalias>
<attrtype>Double</attrtype>
<attwidth>8</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Length</attrlabl>
<attalias Sync="TRUE">Shape_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
<overview>
<eaover>The information encoded about the NHHD Shapefile Extract includes a feature date, classification by type, a unique common identifier and the feature length or area. For reaches, encoded information includes reach code. Names and their identifiers in the Geographic Names Information System are assigned to most feature types. Attribute definitions can be found in the file, NHHD_Geodatabase.pdf.</eaover>
<eadetcit>The names and definitions of all feature types, characteristics, and values are in U.S. Geological Survey, 1999, Standards for National Hydrography Dataset High Resolution: Reston, Virginia, U.S. Geological Survey. The document is available online through &lt;http://mapping.usgs.gov/standards/&gt;. The National Map - Hydrography Fact Sheet is also available at: &lt;http://erg.usgs.gov/isb/pubs/factsheets/fs06002.html&gt;.</eadetcit>
</overview>
</eainfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="NHDStreamOrderLegacyVersionForChapter483_B">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
