1

IDENTIFICATION INFORMATION

1.1
Originator
Metro Data Resource Center
Publication date
201008
Title
Trails
1.2
Abstract
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.3Time period of content
20140425
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.7Access Constraints
None
1.8Use Constraints
See the RLIS Product Terms and Conditions
1.10
Browse graphic file name
trails
Browse graphic file description
Browse graphic file type
PNG
1.13
Filename
trails.shp
Data Set
Microsoft Windows 7 (Build 2800) Service Pack 1; ESRI ArcCatalog 10.0
2

DATA QUALITY INFORMATION

2.4Horizontal positional accuracy
2.5

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
3

SPATIAL DATA ORGANIZATION INFORMATION

3.2Direct spatial reference method
Vector
3.3
SDTS point and vector object type
Line
Point and vector object count
17,000 +/-
3.4
Raster object type
Grid cell
Row count
Column count
4

SPATIAL REFERENCE INFORMATION

4.1

Horizontal Coordinate System

Grid coordinate system name
NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601
SPCS zone identifier
5076
Planar distance units
International foot
Horizontal datum name
D_North_American_1983_HARN
5

ENTITY AND ATTRIBUTE INFORMATION

5.2Overview description
Related data files and field descriptions follow:
Table NameColumnSample Domain ValueDefinition
Trails.dbf ----Attributes and descriptions associated with trails
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 permitted
Yes Permitted
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
Motorized--Motorized Use - Motorized use allowed, seasonal or prohibited yearlong on the trail or segment
Motorized Use is allowed Motorized use is allowed on this trail or segment
Motorized Use is allowed seasonally Motorized use is allowed on a seasonal basis
Motorized Use is prohibited Motorized use is not allowed on this trail or segment
Accessible--Accessibility Status - Accessibility guideline compliance status for trail or segment that are designed for pedestrian use
Accessible Trail meets current accessibility guidelines (ADA and Access Board Interpretation/Guidelines)
Ineligible Trail determined ineligible to meet current trail accessibility guidelines
Not Accessible Trail does not meet accessibility guidelines
Not Evaluated Trail not evaluated for accessibility
Rating--Non-RLIS - Difficulty Rating - Relative difficulty rating of the trail or trail segment
Easiest A trail requiring limited skill with little challenge to travel - mostly level; adequate width; minor crossings, well marked
More Difficult A trail requiring some skill and challenge to travel. Minor ascent/descent; narrow passages; heights; natural crossings; length
Most Difficult A trail requiring a high degree of skill and challenge to travel. Significant ascent/descents; scrambling crossings; some bouldering, extensive length from trail head to trail access
Special/Technical Capability Rapids above level 2 for canoes or 3 for Kayaks, climbing gear, cold weather gear suggested
Varies Difficulty depends on environmental conditions, floods, ice, snow etc.
Width--Width - Average width range (e.g. 1-4, 5-9) of the trail or segment in feet. Do not include the trail shoulder. Future trails have null value.
1-5 feet Width of trail is 1-5 feet
10-14 feet Width of trail is 10-14 feet
15+ feet Width of trail is 15 feet or greater
6-9 feet Width of trail is 6-9 feet
Unknown Width of trail is unknown
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 Existing earth
Other Other surface types including paver block, geo grid, etc
Snow Snow (min coverage 75% of the snow season)
Water Water
Length--Length - Open for user to enter the length of the trail segment. Length units are in feet and are limited to two decimal places.
YearOpen--Non-RLIS - Year Opened - Year the trail was made available for public use (YYYY)
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 - Identification system to be created by Metro that will allow for linking to other GIS tables or related databases
Status--Status - Current physical state of the trail
Conceptual Concept level alignments of trails not yet adopted in local plans, i.e., CIP, TSP, RTP, MTIP, and/or STIP.
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 Trail alignment is adopted in local plans, i.e., CIP, TSP, RTP, MTIP, and/or STIP.
Restricted Trail is open to the public, but access is restricted - ex by permit or reservation only
Restricted_Private Trail exists but is privately owned and may not be open to the public
Unknown Status of the trail unknown
State--State - State or territory where the trail or trail segment exists. Use two character US postal code.
County--County - County where the majority of the trail or trail segment physically resides. Use proper county or parish name.
CityMuni--City or Municipality - City or municipality that contains the trail, or trail segment, or main access point; Use proper city name or town; for long trails indicate the city/town near primary trail or trail segment access point; If trail segment occurs outside any city limits, then use "Unincorporated"
Park_ID--Non-RLIS - Park_ID - RLIS Parks Inventory ID number of park that trail or trail segment is located within
ParkID--Non-RLIS - ParkID - Alpha-numeric identification number of park that trail or trail segment is located within
SystemType--Functional Class - Hierarchical classification by purpose and function. This represents a departure from classifying facilities by design. This functional classification hierarchy is analogous to a roadway classification system (interstate highways, arterials, collectors, local streets).
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."
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.
National Inter-state trails, e.g. "Pacific Crest Trail" or "Columbia River Water Trail."
Other The "Other" value is reserved primarily for GIS trail features that don't necessarily exist on the ground but serve to connect trail segments to the GIS routable streets network.
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."
Unknown Unknown
Shared Name--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--Trail System Name - Name of regional trail, major trail system, or park the trail or segment is a part of, e.g., "Fanno Creek Greenway", "Mountain Park Homeowners Association Trails", "Forest Park."
AgencyType--Agency Type - Type of managing organization
County Managed by county government or agency
Federal Managed by federal government or agency
Municipal Managed by municipal government or agency
Park District Managed by a special park district, e.g., THPRD
Park District Managed by a special park district, e.g., THPRD
Private - HOA Managed by a private home owner association
Private - NP 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
Bike Network--Used for querying trails segments for bike network
No Do not include segment in bike network
No exception Do not include segment in bike network, even if the segment has all other flags consistent from standard "to include" query
Yes Include segment in bike network
Yes exception Include segment in bike network, even if the segment has other flags inconsistent from standard "to include" query
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 permitted
Yes Permitted
Editor--Non-RLIS - Person or organization who made the edit
DataSource--Non-RLIS - Source where the data layer originated
EditDate--Non-RLIS - Last date that the GIS feature was added/modified
ParkTrail--Non-RLIS - Park Trail - Trails/paths internal to parks or natural areas usually for visitor circulation or experience
No Trail is not within a park or natural area. Typically, this includes trails in public right-of-way, trails on campuses, trails in planned developments, and trails along corridors, such as rail-trails, levee trails, freeway trails, etc.
Yes Part of an internal trail system within a public or private park or natural area. Does not include linear trail corridors that are outside a park or natural area, even if the trail is managed by a park agency.
OnStreetBike--On Street Bike - Designated route or portion of street for bike usage. Bikes in bike lanes or shared roadway.
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.
Portage--Mode: Portage - Portage modes of travel are permitted and appropriate considering the design, character and management of the trail segment
N/A Not a water trail
No Not permitted
Yes Permitted
WCraft_Non--Mode: Motorized Watercraft - Non-motorized watercraft are permitted and appropriate considering the design, character and management of the trail segment
N/A Not water
No Not permitted
Yes Permitted
WCraft_Mtr--Mode: Motorized Watercraft - Motorized watercraft are permitted and appropriate considering the design, character and management of the trail segment
N/A Not water
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
6

DISTRIBUTION INFORMATION

6.1
Contact organization
Metro Data Resource Center
Address
600 NE Grand Ave.
City
Portland
State or province
OR
Postal code
97232
Contact voice telephone
503 797-1742
Contact facsimile telephone
503 797-1909
Contact electronic mail address
drc@oregonmetro.gov
6.3Distribution liability
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.
7

METADATA REFERENCE INFORMATION

7.1
Metadata Date
20140425
7.4
Contact person
Max Woodbury
Contact voice telephone
503-797-1563
Contact facsimilie telephone
503-797-1909
Contact electronic mail address
max.woodbury@oregonmetro.gov
7.5Metadata standard name
FGDC Content Standards for Digital Geospatial Metadata
7.6Metadata standard version
FGDC-STD-001-1998