Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This layer is a route system of rivers, streams, canals and other watercourses. Routes are based on stream name or longest path and measured in feet from the stream mouth to the headwaters. A unique 13-digit code,</SPAN></SPAN><SPAN><SPAN>or ‘longitude latitude identifier’ (LLID)</SPAN></SPAN><SPAN><SPAN>, is used to identify streams. LLID is based on the geographic coordinates of the location of the stream mouth, as originally represented in WDFW “str24” (1:24,000 scale or higher resolution hydrography). LLIDs maintain the link to many legacy datasets. </SPAN></SPAN></P><P><SPAN><SPAN>LLID codes were transferred from “str24” by snapping the upstream and downstream points of each str24 route to NHDFlowlines then tracing the network to create NHD events. These events were merged into routes and measures calculated by feature length. Topology checks were performed (must not overlap, must not self-overlap, must be covered by NHDFlowlines, must be single-part). Some exceptions to topology rules were allowed due to differences between NHDFlowlines and “str24” that need to be resolved.</SPAN></SPAN></P><P><SPAN>Additional LLID routes were added to accommodate new fish distributions from the </SPAN><SPAN><SPAN>Statewide Washington Integrated Fish Distribution</SPAN></SPAN></P><P><SPAN>(SWIFD) data integration process.</SPAN></P><P><SPAN>The majority of str24 LLID routes are represented in LLID_Routes, however LLIDs have not been assigned to aproximately 45% of NHDFlowlines.</SPAN></P><P /><P><SPAN>There are multiple LLID systems used in Washington State:</SPAN></P><P><SPAN>There are several different LLID systems used by Washington State agencies. It is important for users to be aware of these differences when working with other datasets and know the LLID source.</SPAN></P><P><SPAN>Development of “str24” was initiated in 2000. The starting point was the hydrography layer released by Washington State Department of Natural Resources (DNR) as part of the Data96 initiative. DFW and DNR managed their hydrography layers separately and over time, significant differences have occurred, including different LLID assignments.</SPAN></P><P><SPAN><SPAN>The </SPAN></SPAN><SPAN>Pacific NW Hydrography Framework Project (PNWHF) is a federally sponsored effort to develop hydrography as a framework theme in the Pacific Northwest and was the focal point for development of NHD, however, the convention for LLID stream routing system adopted by PNWHF is inconsistent with WDFW. Washington State Department of Ecology (ECY) used the PNWHF LLID routing to transform existing data to NHD but there are no plans to maintain LLID in the NHD structure. </SPAN></P><P><SPAN><SPAN>StreamNet, a fisheries data project of the Pacific States Marine Fisheries Commission, uses WDFW LLIDs.</SPAN></SPAN></P><P><SPAN>Because of the importance of LLID to DFW business needs, the agency will maintain LLID_Routs as a layer with geometry coincident with NHDFlowlines.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: Taxlot Parcel boundaries for Mason County. This dataset has multiple originators. The WhoCreated attribute field specifies the originator. For parcels with the ESU attribute, please refer to the parts of this metadata file specific to Inside Oregon Enterprises, Engineering Support Unit. For parcels with the Whiteshield attribute, please refer to the parts of this metadata file specific to WhiteShield, Inc.
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). The National Wetlands Inventory - Version 2, Surface Waters and Wetlands Inventory was derived by retaining the wetland and deepwater polygons that compose the NWI digital wetlands spatial data layer and reintroducing any linear wetland or surface water features that were orphaned from the original NWI hard copy maps by converting them to narrow polygonal features. Additionally, the data are supplemented with hydrography data, buffered to become polygonal features, as a secondary source for any single-line stream features not mapped by the NWI and to complete segmented connections. Wetland mapping conducted in WA, OR, CA, NV and ID after 2012 and most other projects mapped after 2015 were mapped to include all surface water features and are not derived data. The linear hydrography dataset used to derive Version 2 was the U.S. Geological Survey's National Hydrography Dataset (NHD). Specific information on the NHD version used to derive Version 2 and where Version 2 was mapped can be found in the 'comments' field of the Wetlands_Project_Metadata feature class. Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps. This dataset should be used in conjunction with the Wetlands_Project_Metadata layer, which contains project specific wetlands mapping procedures and information on dates, scales and emulsion of imagery used to map the wetlands within specific project boundaries.</SPAN></P></DIV></DIV>