Name: LLID_Routes

Display Field: Stream_Name

Type: Feature Layer

Geometry Type: esriGeometryPolyline

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>

Service Item Id: c7aa67bae64b46b3bfdf836ed38cc3f2

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -1.372869846929186E7
YMin: 5965415.864826593
XMax: -1.3672912530563338E7
YMax: 6005797.820512188
Spatial Reference: 102100  (3857)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [115, 178, 255, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: false
Supports Query With Current User: true

HasZ: false

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• LLID ( type: esriFieldTypeString, alias: LLID, length: 13 )
• Stream_Name ( type: esriFieldTypeString, alias: Stream_Name, length: 50 )
• GNIS_ID ( type: esriFieldTypeString, alias: GNIS_ID, length: 8 )
• GNIS_StreamName ( type: esriFieldTypeString, alias: GNIS_StreamName, length: 50 )
• Shape_Length ( type: esriFieldTypeDouble, alias: Shape_Length )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata