<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20250103</CreaDate>
<CreaTime>09274500</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<imsContentType export="False">002</imsContentType>
<itemName Sync="TRUE">STRM_LOC_PT_web</itemName>
</itemProps>
<coordRef>
<type Sync="TRUE">Geographic</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Angular Unit: Degree (0.017453)</csUnits>
<peXml Sync="TRUE">&lt;GeographicCoordinateSystem xsi:type='typens:GeographicCoordinateSystem' 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;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],AUTHORITY[&amp;quot;EPSG&amp;quot;,4269]]&lt;/WKT&gt;&lt;XOrigin&gt;-400&lt;/XOrigin&gt;&lt;YOrigin&gt;-400&lt;/YOrigin&gt;&lt;XYScale&gt;999999999.99999988&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;8.98315284119521e-09&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;LeftLongitude&gt;-180&lt;/LeftLongitude&gt;&lt;WKID&gt;4269&lt;/WKID&gt;&lt;LatestWKID&gt;4269&lt;/LatestWKID&gt;&lt;/GeographicCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<SyncDate>20260422</SyncDate>
<SyncTime>10023100</SyncTime>
<ModDate>20260422</ModDate>
<ModTime>10023100</ModTime>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<mdContact>
<editorSource>external</editorSource>
<editorDigest>5a5e623f2f1754e1ac1730244bffa682caeb0e82</editorDigest>
<rpIndName>Scott Kiefer</rpIndName>
<rpOrgName>Bureau of Land Management (BLM), Oregon State Office</rpOrgName>
<rpPosName>GS0301 - Geographic Information System Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="True"/>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>skiefer@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<displayName>Name: Scott Kiefer
Organization: Bureau of Land Management (BLM), Oregon State Office
Position: GIS Specialist
Role: Unknown</displayName>
<displayName>Name: Scott Kiefer
Organization: Bureau of Land Management (BLM), Oregon State Office
Position: GIS Specialist
Role: Unknown</displayName>
<editorSave>True</editorSave>
<displayName>Name: Scott Kiefer
Organization: Bureau of Land Management (BLM), Oregon State Office
Position: GS0301 - Geographic Information System Specialist
Role: Unknown</displayName>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20260422</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>Eric Hiebenthal</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Data Management Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>503-808-6340</voiceNum>
<faxNum>503-808-6419</faxNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>ehiebent@blm.gov</eMailAdd>
</cntAddress>
<cntInstr>contact instructions</cntInstr>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<resFees>Contact distributor.</resFees>
<planAvDtTm date="unknown"/>
<ordInstr>Data are only available through the Oregon/Washington State office of the Bureau of Land Management.</ordInstr>
</distorOrdPrc>
<distorFormat>
<formatName>Arc GIS</formatName>
<formatVer>Feature Class</formatVer>
<formatSpec>Winzip</formatSpec>
<fileDecmTech>Winzip</fileDecmTech>
<formatTech>Arc GIS, Winzip</formatTech>
</distorFormat>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>https://gbp-blm-egis.hub.arcgis.com/pages/oregon</linkage>
</onLineSrc>
</distTranOps>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<placeKeys>
<thesaName>
<resTitle>BLM-STATE</resTitle>
</thesaName>
<keyword>Oregon</keyword>
<keyword>Washington</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>BLM-THEME</resTitle>
</thesaName>
<keyword>Geospatial</keyword>
<keyword>Hydrology</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>NONE</resTitle>
</thesaName>
<keyword>Monitoring</keyword>
<keyword>Monitoring Points</keyword>
<keyword>Sample Points</keyword>
<keyword>Samples</keyword>
<keyword>Stream Location</keyword>
</themeKeys>
<idCitation>
<citRespParty>
<rpIndName>U.S. Department of the Interior, Bureau of Land Management (BLM)</rpIndName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<resTitle>BLM OR Stream Location Sample Point</resTitle>
<date>
<pubDate>2026-04-22</pubDate>
</date>
<citRespParty>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Portland, Oregon</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</idCitation>
<idAbs>STRM_LOC_PT: The Stream Location Points dataset represents field collected spatial locations and basic information about the physical characteristics of a stream network, including inception points (stream origins), periodicity and continuity transitions, stream confluences, and complex stream courses.</idAbs>
<idPurp>This dataset records field collected data points regarding the physical characteristics of a stream network. In turn, these data points help inform a more accurate spatial depiction of the linear stream location, which are updated in the USGS National Hydrography Dataset (NHD). These data points also inform the attribute transitions for periodicity and continuity, which are in turn depicted on the linear features in the NHD data and the Hydrography Events datasets respectively.</idPurp>
<idCredit>Bureau of Land Management (BLM), Oregon State Office</idCredit>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>Gerald Stevens</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GS0301 - GIS Specialist (HYDR-APPS)</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6480</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>2965 P.O. Box</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>gstevens@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</resMaint>
<searchKeys>
<keyword>Geospatial</keyword>
<keyword>Hydrology</keyword>
<keyword>inlandWaters</keyword>
<keyword>Monitoring</keyword>
<keyword>Monitoring Points</keyword>
<keyword>Oregon</keyword>
<keyword>Sample Points</keyword>
<keyword>Samples</keyword>
<keyword>Stream Location</keyword>
<keyword>Washington</keyword>
</searchKeys>
<resConst>
<LegConsts>
<useLimit>The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, or for general or scientific purposes, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM.</useLimit>
<othConsts>Generally releasable. However, the data must be reviewed prior to release to assure that no protected data is contained within the dataset.</othConsts>
</LegConsts>
</resConst>
<resConst>
<Consts>
<useLimit>These data are provided by Bureau of Land Management (BLM) 'as is' and might contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the sources from which they were derived, and both scale and accuracy may vary across the data set. These data might not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification. DATA STEWARD APPROVAL: Mike Brown, state data steward for STRM_LOC_PT, approved the use of this dataset on October 28, 2020.</useLimit>
</Consts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<envirDesc>ESRI Arc Catalog 10.4</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-125</westBL>
<eastBL>-116</eastBL>
<southBL>41.5</southBL>
<northBL>49.5</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2026-04-22</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<suppInfo>BLM (Bureau of Land Management) A published revision of the Department Manual’s Part 305: Departmental Science Effects, Chapter 3: Integrity of Scientific and Scholarly Activities (305 DM 3), effective December 16, 2014, is available online at http://elips.doi.gov/ELIPS/DocView.aspx?id=4056. Scholarly information considered in Departmental decision making must be robust, of the highest quality, and the result of as rigorous scientific and scholarly processes as can be achieved. Most importantly, it must be trustworthy. This policy helps us to achieve that standard (http://www.doi.gov/scientificintegrity/index.cfm)</suppInfo>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL>-125</westBL>
<eastBL>-116</eastBL>
<northBL>49</northBL>
<southBL>42</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<resConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>Non Classified</classSys>
<handDesc>None</handDesc>
</SecConsts>
</resConst>
<tpCat>
<TopicCatCd value="012"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
<maintNote>Last metadata review date: 20221208</maintNote>
</mdMaint>
<mdConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>Non classified</classSys>
<handDesc>None</handDesc>
</SecConsts>
</mdConst>
<mdConst>
<Consts>
<useLimit>These data are provided by Bureau of Land Management (BLM) 'as is' and might contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the sources from which they were derived, and both scale and accuracy may vary across the data set. These data might not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification.</useLimit>
</Consts>
</mdConst>
<mdConst>
<LegConsts>
<othConsts>Generally releasable. However, the data must be reviewed prior to release to assure that no protected data is contained within the dataset.</othConsts>
</LegConsts>
</mdConst>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQTopConsis">
<evalMethDesc>o Description: Sub-class of Sample Point in the Sampling group. o Geometry: Simple point features. o Topology: No topology enforced. Points may be coincident. o Integration Requirements: o Point locations representing stream origins (inception), seeps/springs, wetlands, non-flowing bodies of water (e.g., lakes, reservoirs, pools, or ponds), stream confluences, complex stream courses, non-stream channels, and periodicity help inform the spatial location or attribute information of the USGS National Hydrography Dataset (NHD) datasets. In most instances, the location or attribute information of the NHD Waterbody, Flowline, and Point datasets should be modified to match the Stream Location Point. o Point locations describing changes of continuity help inform the attribute information in the Hydrography Events datasets. The Hydrography Events dataset for continuity (STRM_CONTINUITY_ARC) should be updated based on the Stream Location Point. o All points inform that the stream was verified in the field. The Hydrography Events dataset for stream verification (STRM_VER_ARC) should be updated based on the Stream Location Point. o Coincident points are allowed in this dataset. Editors should check for and delete unintentional duplicate records, i.e., stacked records with the same attribution.</evalMethDesc>
</report>
<report type="DQConcConsis">
<measDesc>o Description: Sub-class of Sample Point in the Sampling group. o Geometry: Simple point features. o Topology: No topology enforced. Points may be coincident. o Integration Requirements: o Point locations representing stream origins (inception), seeps/springs, wetlands, non-flowing bodies of water (e.g., lakes, reservoirs, pools, or ponds), stream confluences, complex stream courses, non-stream channels, and periodicity help inform the spatial location or attribute information of the USGS National Hydrography Dataset (NHD) datasets. In most instances, the location or attribute information of the NHD Waterbody, Flowline, and Point datasets should be modified to match the Stream Location Point. o Point locations describing changes of continuity help inform the attribute information in the Hydrography Events datasets. The Hydrography Events dataset for continuity (STRM_CONTINUITY_ARC) should be updated based on the Stream Location Point. o All points inform that the stream was verified in the field. The Hydrography Events dataset for stream verification (STRM_VER_ARC) should be updated based on the Stream Location Point. o Coincident points are allowed in this dataset. Editors should check for and delete unintentional duplicate records, i.e., stacked records with the same attribution.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>Data is updated annually, after field season or as needed. Also, it is archived annually, at the end of the fiscal year.</measDesc>
</report>
<report type="DQQuanAttAcc">
<measDesc>Required attributes have an accuracy of at least ninety percent. Sample points require a high level of positional accuracy (generally within 50 feet) in order to be useful for intended purposes. A sample point represents the location of specific measurement of a particular resource at a point in time. The resource being measured may not even exist in a different (even if nearby) location. It may be critical that a point is located on one side or the other of a stream or road. There may be many sample points close together and different Global Positioning System (GPS) locations obtained with every visit. Accurate location is critical to being able to distinguish points that are supposed to be different from points that are supposed to be in the same location</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>Unknown</measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>Data is input to feature class by BLM field staff.</stepDesc>
<stepDateTm date="unknown">Unknown</stepDateTm>
<stepProc>
<rpIndName>Dana Baker-Alum</rpIndName>
<rpOrgName>BLM</rpOrgName>
<rpPosName>Senior GIS Applications Developer</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6320</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>dbakerallum@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<dataSource>
<srcDesc>BLM</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
</dataSource>
<dataSource>
<srcDesc>BLM</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
</dataSource>
<dataSource>
<srcDesc>BLM District Offices</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>Various</resTitle>
<resAltTitle>Various</resAltTitle>
<date>
<pubDate date="unknown"/>
</date>
<citRespParty>
<rpOrgName>BLM</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
</dataSource>
<prcStep>
<stepDesc>1 - Develop cross-walk to new Stream Locations Points schema: The following point features retained their classification if STRM_LOC_TYPE was equal to: Confluence, Course, and Inception The following point features were reclassified from STRM_LOC_TYPE = 'Other' to one of the following new point types: Dry draw/swale, Lake/Reservoir/Pool/Pond, Lake/Reservoir/Pool/Pond, No Stream, Seep/spring, Wetland, Unstable area. The existing text values captured in the COMMENTS field were used to identify and manually reclassify these features. These changes were reviewed by district hydrologists to verify the accuracy of the modified dataset. Those features that did not fit into the modified dom_STRM_LOC_TYPE retained their classification of STRM_LOC_TYPE = 'Other'. The attribution of STRM_LOC_TYPE = 'Continuity' or STRM_LOC_TYPE = 'Periodicity' points that were spatially coincident (i.e., overlapping) with other Stream Location Points was retained in the overlapping point. These duplicate points (n=493) were subsequently removed from the dataset. Points where STRM_LOC_TYPE = 'Continuity' or STRM_LOC_TYPE = 'Periodicity' points that were not overlapping other Stream Location Points were reclassified to STRM_LOC_TYPE = 'Course' (n=79). 2 - All features were manually reviewed to determine if corresponding edits to the hydrography had already occurred. If NHD_EDITS = 'No', this serves as a flag to notify editors that edits to the hydrography may be needed. 3 - The following quality control (QC) checks were conducted to ensure data integrity: All Stream Location Points must have a SAMPLE_TYPE equal to 'Stream Location Point' When STRM_LOC_TYPE is equal to ‘Inception’, then STRM_SRVY_LOC must be populated with ‘Upper extent’. When STRM_LOC_TYPE is equal to ‘Confluence’, then STRM_SRVY_LOC must be populated with ‘Mid-point’. When STRM_LOC_TYPE is not equal to ‘Wetland’ or ‘Lake/Reservoir/Pool/Pond’, then POINT_TYPE must be populated with ‘Center’. When STRM_LOC_TYPE is equal to ‘Wetland’ or ‘Lake/Reservoir/Pool/Pond’, then POINT_TYPE may be optionally populated with ‘Center’ or 'Perimeter'. When STRM_LOC_TYPE is equal to ‘No stream’ or ‘Unstable area’, then STRM_SRVY_LOC must be populated with ‘Non-stream/Not applicable’. When STRM_LOC_TYPE is equal to ‘Inception’, ‘Course point’, ‘Confluence’, ‘Seep/spring’, ‘Dry draw/swale’, or ‘Other’, then STRM_FLOW, and STRM_CONTINUITY may be optionally populated. When STRM_LOC_TYPE is equal to ‘Other’, then the COMMENTS field must be populated with a detailed description of the feature being recorded.</stepDesc>
<stepDateTm>2020-04-30</stepDateTm>
<stepProc>
<rpIndName>Matthew Groce</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(208) 373-3959</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>mgroce@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="STRM_LOC_PT_web">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="004"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="4269"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.5(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<eainfo>
<detailed Name="STRM_LOC_PT_web">
<enttyp>
<enttypl Sync="TRUE">STRM_LOC_PT_web</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
<enttypd>The Stream Location Points dataset represents field collected spatial locations and basic information about the physical characteristics of a stream network.</enttypd>
<enttypds>BLM</enttypds>
</enttyp>
<attr>
<attrlabl>OBJECTID</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<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>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SAMPLE_TYPE</attrlabl>
<attalias>Sample Type</attalias>
<attrdef>The reason for taking the sample at this location. “Stream Location” is the only valid value for this dataset. “Stream Location” is a single domain value in the larger Sample Type domain. It is important to populate this field correctly so that the field is attributed correctly when this data is combined with the parent and/or other sub-classes of the sample point dataset(s).</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Stream Location</edomv>
<edomvd>Stream Location</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>STRM_LOC_TYPE</attrlabl>
<attalias>Stream Location Type</attalias>
<attrdef>The purpose for recording a Stream Location Point, including:
a) Inception Point - The inception point, or stream origin, is the point where flow first appears on the land with enough force to disturb the substrate creating a lasting sign of flow (Nadeau 2015). The inception point is the beginning of the channel or the most upslope expression of well-defined bed and banks, and bed-forms showing annual scour or deposition. Stream origins are often wetlands, springs, seeps or headcuts. When the stream location type is inception point:
• Professional judgement at the time of the survey is the basis for delineation.
• Field verification can happen at any time of the year. Late winter through spring (February-June) is the preferred period because it is easier to see and hear higher flows, flow may extend to the inception point, and reduced vegetation cover makes channels more visible.
• If a surveyor suspects the re-emergence of flow from a spatially interrupted reach, continue upslope until there is no evidence of a channel with well-defined bed and banks, and bed-forms showing annual scour or deposition.
b) Confluence - Location where two or more streams join to form a single channel.
c) Course point - The actual location of the stream channel, typically captured for complex courses.
d) No stream - mapped or modeled stream channel that is not present, as verified by field surveys.
e) Seep/spring - a location where groundwater emerges onto the land surface, sometimes just a trickle after a rain event and sometimes in a continuous flow.
f) Dry draw/swale - a slight depression in the landscape that serves as a vegetated flow path, but lacks differentiation between bed and bank and may contain standing water or an ephemeral stream
g) Wetland - low-lying areas where water covers the soil or is present for an extended period.
h) Lake/Reservoir/Pool/Pond - large body of non-flowing surface water that can occur naturally or be man-made.
i) Unstable area - area above or adjacent to stream channel that is likely to deliver material (e.g., sediment and wood) to the stream upon failure.
j) Other - other field collected information about locations within a stream network</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Inception Point</edomv>
<edomvd>Inception Point</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Confluence</edomv>
<edomvd>Confluence</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Course Point</edomv>
<edomvd>Course Point</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>No Stream</edomv>
<edomvd>No Stream</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Seep/Spring</edomv>
<edomvd>Seep/Spring</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Dry Draw/Swale</edomv>
<edomvd>Dry Draw/Swale</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Wetland</edomv>
<edomvd>Wetland</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Lake/Reservoir/Pool/Pond</edomv>
<edomvd>Lake/Reservoir/Pool/Pond</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Unstable Area</edomv>
<edomvd>Unstable Area</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Other</edomv>
<edomvd>Other</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>POINT_TYPE</attrlabl>
<attalias>Point Type</attalias>
<attrdef>Specifies where the point is being taken in relation to the feature being recorded.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Center</edomv>
<edomvd>Center - A point corresponding to the geometric center of the feature.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Perimeter</edomv>
<edomvd>Perimeter - A point, that may be part of a series of points, representing the outline of the area feature</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>SRVY_LOC</attrlabl>
<attalias>Survey Location</attalias>
<attrdef>The physical location of the surface water feature along the stream channel. Stream Location Points that do not correspond directly on a stream should be recorded as Non-stream/NA.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Upper extent</edomv>
<edomvd>Upper extent – Upper extent of a stream feature or a transition in periodicity/ continuity</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Mid-point</edomv>
<edomvd>Mid-point – Mid-point data capture</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Lower extent</edomv>
<edomvd>Lower extent – Lower extent of a stream feature or a transition in periodicity/continuity</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Non-stream/NA</edomv>
<edomvd>Non-stream/NA – Point does not fall on a stream or survey location is not applicable</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>STRM_FLOW</attrlabl>
<attalias>Stream Periodicity</attalias>
<attrdef>Captures the transition point of the temporal expression of stream flow. A stream reach may be: a) Perennial - Perennial streams generally have a well-defined channel that contains water continuously during a year of normal rainfall, often with the streambed located below the water table for most of the year. Groundwater supplies the baseflow for perennial streams, but flow is also supplemented by stormwater runoff and snowmelt. b) Intermittent - Intermittent streams contain water for only part of the year, typically during winter and spring when the streambed may be below the water table and/or when snowmelt from surrounding uplands provides sustained flow. Streamflow may vary greatly with stormwater runoff. c) Ephemeral - Ephemeral streams flow only in direct response to large precipitation events or stormwater runoff. An ephemeral stream may or may not have a well-defined channel, the stream bed is always above the water table, and stormwater runoff is the primary source of water. While the periodicity of a stream is determined by the dominant or the most representative features within a reach, the distinction between perennial, intermittent, and ephemeral channels is often dependent on a wide range of temporal and spatial scales. Ephemeral and intermittent streams are common in the semiarid landscapes of eastern Oregon and have distinctly different characteristics from the perennial streams that are found in the wetter, more humid climate of western Oregon. While the stream flow definitions provided above give a broad understanding of these terms, relevant terminology within local Resource Management Plans should be consulted. Application of local management plans ensures that stream periodicity attribution is in alignment with land use allocations and overall management direction.
In the Oregon Forest Practices Act, a key distinction between perennial and intermittent streams is that the former is defined as a stream that normally has summer surface flow after July 15, whereas the latter is defined as a stream that normally does not have summer surface flow after July 15. Although the stream survey date in itself won’t affect a stream’s periodicity, it can influence the surveyor who may or may not be able to key in on the biologic and/or geomorphic stream flow indicators used to determine the flow status of streams, which are often inconspicuous and may not be well defined at all locations or may not be evident at all times.</attrdef>
<attrdefs>BLM</attrdefs>
<attscale Sync="TRUE">0</attscale>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attrdomv>
<edom>
<edomv>Perennial</edomv>
<edomvd>Perennial – Stream that contains flowing water, generally on a year-round basis</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Intermittent</edomv>
<edomvd>Intermittent – Stream that contains flowing water for only part of the year, typically during winter and spring</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Ephemeral</edomv>
<edomvd>Ephemeral – Stream that flows during and shortly after large precipitation events</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>STRM_CONTINUITY</attrlabl>
<attalias>Stream Continuity</attalias>
<attrdef>Captures the transition point of the spatial expression of a stream channel.
A stream channel may be:
a) Continuous - Continuous channels are well-defined throughout the reach. In a continuous perennial stream, most of the stream flows at or above the stream bed. In a continuous intermittent stream, most of the stream expresses channel characteristics (evidence of flow and/or deposition) on the stream bed. Water, or evidence of water, may be found flowing or in pools. Continuous flow in a reach may go subsurface for short distances at certain times of the year.
b) Interrupted - Interrupted channels have portions where a defined channel is not evident. Most of an interrupted stream is expressed beneath the ground’s surface. Perennial or intermittent flow, if spatially interrupted, is nearly or entirely subsurface. Evidence of scour and/or deposition is nearly or entirely absent. Headwater streams with dramatic changes in gradient (high to low) or highly permeable substrate can flow subsurface and reappear downstream when the gradient increases again or ground water surfaces. Channels with well-defined beds and banks, and bed-forms showing annual scour or deposition may not be present in areas of spatial interruption, but these areas connect defined upstream and downstream channels. Spatial interruption can be caused by both natural and artificial disruptions.
Stream Location Points capturing interrupted or spatially intermittent stream reaches should be treated differently than Stream Location Points that represent locations of a mapped or modeled stream channel that field surveys have verified is not present (i.e., Stream Location Type is ‘No stream’).
Stream Location Points capturing interrupted or spatially intermittent stream reaches help inform the spatial location or attribute information of the NHD datasets. These locations should be treated differently than Stream Location Points that represent locations of a mapped or modeled stream channel that field surveys have verified is not present (i.e., Stream Location Type is ‘No stream’) and do not inform the NHD.
Although continuity can change on the microscale (feet), the continuity of a channel is determined by the dominant or most representative expression in the reach (usually tens or hundreds of feet).</attrdef>
<attrdefs>BLM</attrdefs>
<attscale Sync="TRUE">0</attscale>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attrdomv>
<edom>
<edomv>Continuous</edomv>
<edomvd>Continuous – flowing water forms a channel with defined bed/banks and evidence of annual scour and deposition</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Interrupted</edomv>
<edomvd>Interrupted – portions of the channel are not evident or well-defined</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>PROJ_NM</attrlabl>
<attalias>Project Name</attalias>
<attrdef>The name of the associated project to the point that is being measured, monitored, or otherwise sampled.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>LASTVISIT_DT</attrlabl>
<attalias>Visit Date</attalias>
<attrdef>The last date that a sample was taken or measured at this point.
When the data is collected in a field mobile collection application, the value in this field will be automatically populated on import of the data to ArcGIS from the Created Date field, which uses GMT (UTC), as it is assumed that the field visit date is the same as the date the data was captured in the database. The Last Visit Date value can be modified prior to submitting the data to the database. When the data is entered in an ArcGIS desktop application, this field will not be automatically populated from the Created Date as it is assumed that the field visit date is not the same as the date the data was captured in the database.
The default value for this field is 1/1/8888.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom>Examples: 6/24/2008, 1/1/1998, 9/1/2001</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>LASTVISIT_DT_ACC</attrlabl>
<attalias>Visit Date Accuracy</attalias>
<attrdef>Describes the accuracy of the LASTVISIT_DT date field. The default value for this field is "Day."</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">7</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Day</edomv>
<edomvd>Day - Only the exact day, month, and year is known.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Month</edomv>
<edomvd>Month - Only the exact month and year is known.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Year</edomv>
<edomvd>Year - Only the exact year is known.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Unknown</edomv>
<edomvd>Unknown - The accuracy of the date is unknown</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>NHD_EDITS</attrlabl>
<attalias>NHD Edits</attalias>
<attrdef>Indicates whether edits to the NHD Flowline, NHD Point, NHD Waterbody, or NHD Area datasets have been completed.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Y</edomv>
<edomvd>Yes</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>N</edomv>
<edomvd>No</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NA</edomv>
<edomvd>Not Applicable</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>COORD_SRC</attrlabl>
<attalias>Coordinate Source</attalias>
<attrdef>The actual source of the GIS coordinates for the points. If the point is copied from another theme, and already has COORD_SRC, it should be reviewed and may need to be changed for use in this dataset.
When the data is collected in a field mobile collection application, the value in this field will be automatically calculated. The field will calculate the quality of the GPS coordinate source used.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">7</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>CADNSDI</edomv>
<edomvd>CADNSDI - Lines from or snapped to the CADNSDI dataset</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>CFF</edomv>
<edomvd>CFF - Lines duplicated or buffered from Cartographic Feature Files (USFS)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DEM</edomv>
<edomvd>DEM - Digital Elevation Model (30m or better accuracy) used for creation of contours</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DGPS</edomv>
<edomvd>DGPS - Feature obtained from a Global Positioning System device with Real Time Correction (SBAS)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DIS</edomv>
<edomvd>DIS - Lines generated to connect discontinuous features</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DLG</edomv>
<edomvd>DLG - Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DOQ</edomv>
<edomvd>DOQ - Screen digitized linework over digital orthophotography backdrop (DOQ, NAIP, OSIP, or others)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DRG</edomv>
<edomvd>DRG - Screen digitized linework over Digital Raster Graphic backdrop</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>GCD</edomv>
<edomvd>GCD - Lines snapped to Geographic Coordinate Database Points</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>GPS</edomv>
<edomvd>GPS - Lines obtained from a Global Positioning System device</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>IMG</edomv>
<edomvd>IMG - Linework derived from interpretation of satellite or other non-photographic imagery</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>LiDAR</edomv>
<edomvd>LiDAR - LiDAR points, lines, or polygons generated through interpretation or analysis.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MAP</edomv>
<edomvd>MAP - Digitized coordinates from hardcopy map or onto a map backdrop</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MTP</edomv>
<edomvd>MTP - Lines duplicated from Digital Master Title Plat</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SOURCEL</edomv>
<edomvd>SOURCEL - Coordinates duplicated from a BLM GIS source layer.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SOURCEX</edomv>
<edomvd>SOURCEX - Source Layer from non-BLM GIS</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SRV</edomv>
<edomvd>SRV - Survey methods were used to create the linework (e.g., COGO)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>TIGER</edomv>
<edomvd>TIGER - Tiger Data</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>TRS</edomv>
<edomvd>TRS - Coordinates only given as a legal description (township, range, section)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>UNK</edomv>
<edomvd>UNK - Unknown coordinate source</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WOD</edomv>
<edomvd>WOD - WODDB Photogrammetric</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>ACCURACY_FT</attrlabl>
<attalias>Accuracy (ft)</attalias>
<attrdef>How close, in feet, the spatial GIS depiction is to the actual location on the ground. There are several factors to consider in GIS error: scale and accuracy of map-based sources, accuracy of GPS equipment, and the skill level of the data manipulators. A value of “0” indicates no entry was made. This is the correct value when the COORD_SRC is another GIS theme (Digital Line Graphs (DLG), Geographic Coordinate Database (GCD), and Digital Elevation Model (DEM)) because the accuracy is determined by that theme. However, if COORD_SRC is MAP (digitized from a paper map) or GPS, a value of “0” indicates a missing value that should be filled in either with a non-zero number or “-1.” A value of “-1” indicates that the accuracy is unknown, and no reliable estimate can be made.
When the data is collected in a field mobile collection application, the value in this field will be automatically calculated. The field will calculate the estimated GPS accuracy to the 95% confidence interval to meet the National Standard for Spatial Data Accuracy (NSSDA) requirements. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom>Examples: 3 (for high accuracy GPS), 40 (best possible for USGS 24K topo map), 200</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SAMPLE_GUID</attrlabl>
<attalias>Sample Unique Identifier</attalias>
<attrdef>Unique identifier for the Sample Point feature class. The field is used to link table records to sample points.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">GUID</attrtype>
<attwidth Sync="TRUE">38</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom>Example: {C36B32EA-88D2-4ACA-9B20-1199A6FADA49}</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>GLOBALID</attrlabl>
<attalias>GlobalID</attalias>
<attrdef>An alpha-numeric code that serves as the universal and unique identifier for each feature within the feature class or table of a geodatabase. Software generated value. A field of type UUID (Universal Unique Identifier) in which values are automatically assigned by the geodatabase when a row is created. This field is not editable and is automatically populated when it is added for existing data.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrtype Sync="TRUE">GlobalID</attrtype>
<attwidth Sync="TRUE">38</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
<attalias Sync="TRUE">SHAPE</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
<overview>
<eaover>Attributes are provided that give basic information about source, type, and accuracy of the line data. More information may be found in the data standard if available: https://www.blm.gov/about/data/oregon-data-management</eaover>
</overview>
</eainfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="STRM_LOC_PT_web">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="1"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
