IDENTIFICATION INFORMATION

Regional Trails data set created by combining 31 different data sets and verified with orthophotography where applicable.

Purpose

Regional Trails to be published quarterly for RLIS Lite and provide trail information for various needs. This data set was created specifically for off-road trails and paths, though there are some regional connections that are on-street.

Supplemental information

The schema was created by following the National Recreation & Park Association (NRPA) GIS Model for trails to set a standard among data providers.

1.3

Time period of content

20161028

1.4

Progress

Complete

Maintenance/update frequency

Continually

1.5

Spatial domain

Description

Clackamas County, Multnomah County, and Washington County, Oregon

West bounding coordinate

-123.486073179

East bounding coordinate

-121.651005666

North bounding coordinate

45.4616758499

South bounding coordinate

44.885714569

1.6

Theme keyword thesaurus

None

Theme keyword

Trails, Pathways, Paths, Pedestrian, Walkways

Place keyword thesaurus

None

Place keyword

Portland, Multnomah County, Washington County, Clackamas County, Oregon

1.7

Access Constraints

None

1.8

Use Constraints

This database and GIS data are made available under the Open Database License (ODbL v1) and Database Content License (DbCL v1). See http://www.oregonmetro.gov/rlis-live.

DATA QUALITY INFORMATION

Lineage

Process Description

Existing Trails: 31 Data sources provided a base to begin verifying alignment with aerial orthophotography. Attribute data was populated from these source layers. Where there was no attribute data provided, there was thorough research conducted to try and populate the records. Unknown values were used when there was no other information available.

Process date

20100801

Process Description

Future Trails Added: The old RLIS regional planned trails data was incorporated into the new NRPA GIS database. Now all of the trails are maintained in the same database.

Process date

20110201

Process Description

TRAILID field changed from a string to an interger and re-populated in increments of one.

Process date

20140801

Process Description

Added field MTSCOTTLP: Field to flag if a segment is part of the "Mount Scott Loop".

Process date

20150331

Process Description

LAST_EDIT field has now been included in the data set. This field will provide a timestamp of when a segment was last edited.

Trail managed by private non-profit organization, for example a land trust, conservancy, etc

Private - other

Managed by a private individual, business or commercial entity

School District

Managed by a school district

Special District

Managed by a special district government, e.g., Metro, Clean Water Services

State

Managed by state government or agency

Unknown

Managing agency unknown

AgencyName

--

Managing Agency - Organization with legal right to control or regulate the access to and use of the trail

On Street Bike

--

On Street Bike - Designed to indicate if a bike use trail follows the path of a street or is one on the street.

N/A

"Mode: Road Bike" equals "N/A" or "No". Includes segments that are not designed for or do not allow bikes.

No

Bikes use a separated facility, either within road right of way, or in separate right of way. This includes two-way paths at least 8 feet wide running parallel to streets in the same right of way, a.k.a., sidepaths. Separation between bikes and car travel lanes should include grade separation, such as curbs, and a planting strip.

Yes

Bikes share the street or road with cars. Not limited to public right-of-way. This could include several facility types, including bike lanes, bike boulevards, shared roadways, sharrows, signed connections, or cycletracks. Does not include sidewalks or sidepaths that are shared with pedestrians.

Nonmotorized Watercraft

--

Mode: Motorized Watercraft - Non-motorized watercraft are permitted and appropriate considering the design, character and management of the trail segment

N/A

Not designed for watercraft use.

No

Not permitted

Yes

Permitted

Equestrian

--

Mode: Equestrian - Equestrian, pack & saddle modes of travel are permitted and appropriate considering the design, character and management of the trail segment

N/A

Not designed for horses, i.e., paved and/or too narrow.

No

Not permitted

Yes

Permitted

UKN

Unknown

MtnBike

--

Mode: Mountain Bike - Mountain bicycle modes of travel are permitted and appropriate considering the design, character and management of the trail segment

N/A

Not designed for mountain bikes, i.e., paved.

No

Not appropriate

Yes

Appropriate

UKN

Unknown

RoadBike

--

Mode: Road Bike - Bicycling modes of travel are permitted and appropriate considering the design, character and management of the trail segment. (Could include electric bike or Segway type transport)

N/A

Not designed for road bikes, i.e., not paved.

No

Not appropriate

Yes

Appropriate

UKN

Unknown

Hike

--

Mode: Pedestrian - Hiking, walking, running modes of travel are permitted and appropriate considering the design, character and management of the trail segment

N/A

Not designed for pedestrian use

No

Not permitted

Yes

Permitted

UKN

Unknown

Accessible

--

Accessibility Status - Accessibility guideline compliance status for trail or segment that are designed for pedestrian use

Width - Average width range (e.g. 1-4, 5-9) of the trail or segment in feet. Does not include the trail shoulder. Future trails have null value.

1-5 feet

Width of trail is 1-5 feet

6-9 feet

Width of trail is 6-9 feet

10-14 feet

Width of trail is 10-14 feet

Unknown

Width of trail is unknown

15+ feet

Width of trail is 15 feet or greater

TrlSurface

--

Trail Surface - The predominant surface type the user would expect to encounter on the trail

Chunk Wood

Shredded/chipped wood or bark

Decking

Boardwalks, recycled material, etc.

Hard Surface

Asphalt, concrete, or similar

Imported Material

Imported aggregates, clay, gravel, crushed rock, shell, sand, etc

Native Material

Existing earth

Stairs

Stairs or steps.

Water

Water

Unknown

Unknown

Status

--

Status - Current physical state of the trail

Conceptual

The alignment of the trail has not been determined through a master plan or schematic design process.

Decommissioned

Trail has been removed from service

Open

Trail is open to the public, free of charge

Open_Fee

Trail is open to the public, access fee is charged

Planned

The alignment of the trail has been determined and adopted through a master plan process.

Restricted_Private

Trail exists but is privately owned and may not be open to the public

Unknown

Status of the trail unknown

Under Construction

Trail is currently under construction.

County

--

County - County where the majority of the trail or trail segment physically resides. Use proper county or parish name.

SystemType

--

Functional Class - Hierarchical classification by purpose and function. This is analogous to a roadway classification system (interstate highways, arterials, collectors, local streets).

Local

Sometimes called "Local Access Trails" or "Neighborhood Trails", these provide connections to local features such as parks, community centers, and schools, and include most paths within parks, natural areas, planned developments, and campuses, as well as public stairways, alleys, and narrow ROWs.

Community

Also known as "Community Connector Trails", these are typically much longer than Local trails though not as long as Regional trails. Community Trails link important land uses and areas of interest within a single jurisdiction. Examples are Tigard's "Pathfinder-Genesis Trail", Portland's "Columbia Blvd Trail", or Gresham's "Butler Creek Greenway."

Regional

Regional trails tend to be multi-jurisdictional, exceptionally long, and connect to regionally significant features such as Forest Park or the Tualatin River. Examples are the Gresham-Fairview Trail, Hillsdale to Lake Oswego Trail, or the Wildwood Trail.

State

Also known as "Inter-regional Trails," "State" trails connect to destinations outside the region, e.g., "Banks-Vernonia Trail" or "Willamette River Water Trail."

The Other value is reserved for GIS trail features that do not exist on the ground but serve to connect trail segments to the GIS routable streets network.

SharedName

--

Shared Name - Other name that the trail or trail segment is know by when the trail/segment is part of more than one route

SystemName

--

System Name - Name of the regional trail if the segment is part of the regional trails and greenways system plan.

TrailName

--

Trail Name - Proper name of the trail or trail segment. No abbreviations. Access, connector, and spur trail names should use the same name as the main trail, appended with the appropriate suffix, e.g., "Springwater Corridor - connector." Adjacent street names may be used for trail segments in road rights-of-way.

TrailID

--

Trail ID - Unique identification number for each trail segment.

Milage

--

Length of segment in miles.

Fortymloop

--

Flag to indicate if the segment is part of the 40-mile loop

Last_Edit

--

Date of the last time the feature has been edited, including attribute or geometry changes.

The information in this file was derived from digital databases on Metro's GIS. Care was taken in the creation of this file. Metro cannot accept any responsibility for errors, omissions, or positional accuracy. There are no warranties, expressed or implied.