DTC Trails Composite (v1.6), Deschutes County, OR

Oct 10, 2022 (Last modified Feb 24, 2023)
Open in Map
Open in Map
Description:
The DTC trails composite combines location and attribute data from several recreational trails datasets in order to provide a single inventory of all known trails in Deschutes County (OR), and to represent those trails using a common standardized set of field names.

A list of the datasets used to create this composite is provided below, ordered by the general priority used when the same trail was represented in multiple data sources, and/or trail segments were partially coincident.

Data Sources:

1. USFS National Forest System Trails (2022)
Dataset URL: https://databasin.org/datasets/2e972055733e4e80be0900c2f3c0c298
Trails included: All USFS trails were included in the composite.

2. Oregon State Parks Trails (2022)
Dataset URL: https://databasin.org/datasets/c1cf79536261487f82eef9891445c715
Trails included: All Oregon State Parks Trails were included in the composite (attributes from intersecting trails in the City of Bend dataset were spatially joined).

3. City of Bend Trails (Bend Parks and Recreation - All Trails), (2020)
Dataset URL: https://databasin.org/datasets/4a3fe46de9c34fba9f7cfd00e97f19a0
Trails included: Trails were included if they were not Oregon State Park trails, and were not represented or partially coincident with a trail in the USFS dataset. Any trail segment that was already represented in, or partially coincident with, a USFS trail was manually removed in an editing session.

4. USGS National Transportation Dataset Geodatabase (2021)
Dataset URL: https://databasin.org/datasets/336757f8b4d84368b05cdc8354f97a28
Trails included: All non-USFS trails were included with the following exceptions:
Trail with PERMANENT_IDENTIFIER = 'f87378ca-7edd-41ff-9462-5eb5b163ea25'. The name of this trail is Connector Trail. The geometry on this trail was of poor quality and this trail is partially coincident with a trail in the City of Bend dataset. In addition, any trails within one meter of a trail in the BLM dataset was removed (as these were assumed to represent the same trail).

5. BLM Trails (OR GTRN Publication Trails Line, 2022)
https://databasin.org/datasets/efbe2d2a42764fe3bec497cd828c0233
Trails included: Non-USFS Trails that fell completely outside of an 800m buffer created around the merged trails created from the sources above.

The " original_trails_dataset_source " field indicates which of the source datasets the trail originated from.

Additional information on the methods and processing steps used to combine the source data can be found at the following URL:
https://docs.google.com/document/d/1MZWd5_1pOD2zXRcdY-2Bqqy06LqoyD-vVZnzlR7MsIo/edit

In addition to merging the linear geometry of the trails in the source data, a common set of field names was also created and populated based on the information stored in the source data fields. The rules and logic used to determine how a particular field was populated can be examined in the python script at the following URL (please request permission to view):

https://github.com/mikegough/USFS-OR-and-WA-Trails/blob/326721dcac059853f7e3702131ea1648757d85eb/create_trail_composite_with_standardized_fields.py

A list of all the original field names and the mapping used to assign values to the composite fields can be found in the spreadsheet at the following URL:

https://docs.google.com/spreadsheets/d/1HNaqolwFwNmAlSZo5uH4glwPt6KunesqMwKo7we1_fE/edit#gid=977082183

As a final step, trail segments in the composite having the same name were dissolved into a single linear feature. The values in the other composite fields were preserved in the output by calculating identical values in each field for all trail segments having the same name. This was done using one of three approaches.

1. Find True (if the field value for any trail segments are true, the value for all trail segments are true)

Example: if bikers are allowed on any of the segments, all segments will receive a field value of 1 to indicate that the trail does allow bikers.

Field performed on:

"stream_crossing", "hiker", "biker", "pack_saddle", "four_wheel_drive", "atv", "motorcycle", "motorized", "accessibility_status", "national_trail_designation"

2. Longest Length (Keep the field value associated with the longest trail segment)

Example: if a given trail (line segments having the same name) has one segment that is 5 miles of Asphalt, and another segment that has 2 miles of Natural, this function will recalculate the the value in the surface field to be Asphalt for each segment since the trail is mostly Asphalt.

Fields performed on:

"surface", "width_ft", "grade", "type", "status", "special_mgmt_area"

3. Concatenate (Concatenate all the field values from the trail segments)

Example: if a trail has two line segments and one of them has an owner of "USFS" and the other has an owner of "BLM", this function will recalculate the ownership field for both line segments to be "USFS, BLM"

Fields performed on:
"ownership", "notes"

Version History:

1.6
Dissolve trail segments based on name using one of three approaches to preserve the additional composite fields (refer to the description or methods)

1.5
Added the stream_crossing field (this was previously calculated and added at a later stage to the EEMS input reporting units).

1.4
Use USGS national trails dataset which has more trails and more useful fields than the state (Oregon) version, including user types and motorized.

1.3
Fix values in motorized field. Previously the values in the motorized field equaled 1 where the values in the original TERRA_MOTORIZED field was 'Y' or 'N
Data Provided By:
Conservation Biology Institute
Content date:
2020-01-01T00:00:00 - 2022-09-12T00:00:00
Contact Organization:
Conservation Biology Institute
Contact Person(s):
Use Constraints:
This dataset was created by the Conservation Biology Institute and has been provided for use in accordance with the terms set forth in the contract agreement. Attribution is required for redistribution in any medium or format. Refer to the conditions of use policy in the contract agreement for any additional restrictions or limitations. Note that this dataset does not contain trails from data sources not listed in the description. It is therefore likely not a complete inventory of all trails in Deschutes County, OR.
Layer:
Layer Type:
Currently Visible Layer:
All Layer Options:
Layers in this dataset are based on combinations of the following options. You may choose from these options to select a specific layer on the map page.
Description:
Spatial Resolution:
Credits:
Citation:
Purpose:
Methods:
References:
Other Information:
Time Period:
Layer Accuracy:
Attribute Accuracy:
FGDC Standard Metadata XML
Click here to see the full FGDC XML file that was created in Data Basin for this layer.
Original Metadata XML
Click here to see the full XML file that was originally uploaded with this layer.
This dataset is visible to everyone
Dataset Type:
Layer Package
Tags:
transportation, composite, eems, trails, state parks, deschutes county, recreation, dtc, oregon, state park trails, oprd, bend, trail
Downloaded by 1 Member
Included in 1 Private Map

About the Uploader

Conservation Biology Institute

We provide advanced conservation science, technology, and planning to empower our partners in solving the world’s critical ecological challenges