ArcGIS REST Services Directory Login | Get Token
JSON

Layer: ODF_Flowline (ID: 10)

View In:   ArcGIS Online map viewer

Name: ODF_Flowline

Display Field: StreamName

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The Oregon </SPAN><A href="https://www.oregon.gov:443/odf/aboutodf/documents/2022-odf-private-forest-accord-report.pdf" STYLE="text-decoration:underline;"><SPAN>Private Forest Accord</SPAN></A><SPAN> and Forest Practices Act specified the methodology to develop and maintain the Statewide Flow Line data. Initial development of these data began with using best available Digital Elevation Models (DEMs) to model a synthetic stream network. Where available, lidar DEMs were resampled to a 2 meter resolution. Where lidar was not available, the National Elevation Dataset (NED, resolution of 10 meters) was used. After streams were model the Fransen fish model (Brian R. Fransen, Steven D. Duke, L. Guy McWethy, Jason K. Walter &amp; Robert E. Bilby. 2006. A Logistic Regression Model for Predicting the Upstream Extent of Fish Occurrence Based on Geographical Information Systems Data, North American Journal of Fisheries Management, 26:4, 960-975, DOI: 10.1577/M04-187.1) was applied to predict fish presence for all streams across Oregon. Historic ODF data (maintained in the ODF Statewide Streams Fish Presence dataset) was then conflated to the synthetic streams to overwrite the fish model outputs with any valid fish survey. These data were checked by Oregon Department of Forestry (ODF) and Oregon Department of Fish &amp; Wildlife (ODFW) GIS staff to meet minimum conflation success rates. Errors were identified and documented for future updates.</SPAN></P><P><SPAN>The Flow Line data will be continuously updated with fish and flow permanence surveys, following established protocols and workflows developed by ODF and ODFW. Errors in conflation with historic data, and errors in geometry from the DEM modeling will also continue to be corrected. This data should be treated as a dynamic layer, with any export product frequently updated to ensure the most current information is being used.</SPAN></P></DIV></DIV></DIV>

Copyright Text: Oregon Department of Forestry GIS (GIS Unit and Forest Resources GIS staff); Oregon Department of Fish and Wildlife Natural Resource Information Management Program; TerrainWorks

Default Visibility: false

MaxRecordCount: 2000

MaxSelectionCount: 0

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:
Drawing Info: Feature Draw Order: Advanced Query Capabilities:
HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: StreamPermanence

Fields: Types:
Capabilities: Query,Create,Uploads,Editing,Sync,ChangeTracking

Sync Can Return Changes: true

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: true

Supports Query With Historic Moment: true

Supports Coordinates Quantization: true

Child Resources:

Supported Operations:   Query   Query Analytic   Apply Edits   Add Features   Append   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata