| ArcGIS REST Services Directory |
| Home > services > Revised_LWCF_projects_Linear (FeatureServer) | | API Reference |
Field descriptions:
F_Elev/T_Elev: elevation fields. Base elevation value is 10, underpass value is 5, overpass value is 20
Length: length in miles
FWalkTime/TWalkTime: walk time fields used for network analysis. WalkTime = Length x 24
YearAdd: year added to network. Generally unreliable/not updated
Sides_walk: number of sidewalks. Especially relevant when sidewalk linework follows road centerline. All Pathways and Micropaths have value of 1, sidewalk linework that follows existing sidewalk exactly has value of 1. Sidewalk linework that follows road centerline will have value of 2 when sidewalks exist on both sides of roadway
County: Ada or Canyon County
Year: also unreliable/not updated
FENAME: street name or pathway name
Miles: length in miles (identical to Length field)
name: secondary name field. Useful in delineating Greenbelt sections or other long pathways
citytype: amalgamation of various types designated by cities. Similar to 'name' field above, can be useful in selecting the entirety of certain pathways
type: the primary field for determining classification of infrastructure
Campus Pathway: pathways/sidewalks found in universities, colleges, and larger public schools
Bike/Ped Bridge/Underpass: any bridge or underpass specifically for bike/ped
Crosswalk: striped and/or signed crosswalk
Driveway: intersection of business/residential access point and sidewalk/pathway. This type is a new addition to our network and is in progress
Intersection: also a new addition, this is mostly a placeholder as we determine the purpose of High-Volume Crossings and Low-Volume Crossings in our network
High-Volume Crossing: unsigned crossings of high-speed, high-volume roads. We are in the process of removing most of these from our network, though there are situations where they are appropriate
Low-Volume Crossing: unsigned crossings of low-speed, low-volume roads. Also in progress, these help show potential areas of conflict where allowing the sidewalk linework to continue through the intersection would be disingenuous to how the walkable network calculates walkability
Micropath Connection: short pathway connections, usually within subdivisions
Non-Walkable Road: high-speed or high-volume roadways with no pedestrian infrastructure. When running walkability analyses, this type is queried out
Public Multiuse Pathway: paved or unpaved pathway with official signage and maintenance. Includes Boise River Greenbelt, Ridge to Rivers trail system, and all other regional pathways and major subdivision pathways
Shared Road: generally 2-lane rural roadway with no pedestrian infrastructure. When running walkability analyses, this type is queried out
Sidewalk: sidewalk
Walkable Road: generally low-speed, low volume roadway with no pedestrian infrastructure but safe enough to walk. This type is included in our walkability analyses
Trail Unpaved: unmaintained and sometimes unofficial trail with notable impact on connectivity. Sometimes the people know best
Walking Trail: official unpaved pathway with maintenance, but restricted to pedestrians only
cityplan: denotes the pathway's planning origin, as most of these were formerly proposed pathways in a city's bike/ped master plan
surface: paved or unpaved. Sometimes updated, but not regularly
width: pathway width. Generally unreliable/not updated
piclink: not currently used, may eventually tie into our pathway conditions dataset
pmid: unique ID for pathway segments. Only major pathways currently have PMID's
linearref: work-in-progress for our eventual switch to linear referencing