ArcGIS REST Services Directory
JSON

Layer: LWCFprojects_Linear_Clip (ID:0)

View In:   Map Viewer

Name: LWCFprojects_Linear_Clip

Display Field: name

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: Field descriptions:F_Elev/T_Elev: elevation fields. Base elevation value is 10, underpass value is 5, overpass value is 20Length: length in milesFWalkTime/TWalkTime: walk time fields used for network analysis. WalkTime = Length x 24YearAdd: year added to network. Generally unreliable/not updatedSides_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 roadwayCounty: Ada or Canyon CountyYear: also unreliable/not updatedFENAME: street name or pathway nameMiles: length in miles (identical to Length field)name: secondary name field. Useful in delineating Greenbelt sections or other long pathwayscitytype: amalgamation of various types designated by cities. Similar to 'name' field above, can be useful in selecting the entirety of certain pathwaystype: the primary field for determining classification of infrastructureCampus Pathway: pathways/sidewalks found in universities, colleges, and larger public schoolsBike/Ped Bridge/Underpass: any bridge or underpass specifically for bike/pedCrosswalk: striped and/or signed crosswalkDriveway: intersection of business/residential access point and sidewalk/pathway. This type is a new addition to our network and is in progressIntersection: also a new addition, this is mostly a placeholder as we determine the purpose of High-Volume Crossings and Low-Volume Crossings in our networkHigh-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 appropriateLow-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 walkabilityMicropath Connection: short pathway connections, usually within subdivisionsNon-Walkable Road: high-speed or high-volume roadways with no pedestrian infrastructure. When running walkability analyses, this type is queried outPublic 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 pathwaysShared Road: generally 2-lane rural roadway with no pedestrian infrastructure. When running walkability analyses, this type is queried outSidewalk: sidewalkWalkable Road: generally low-speed, low volume roadway with no pedestrian infrastructure but safe enough to walk. This type is included in our walkability analysesTrail Unpaved: unmaintained and sometimes unofficial trail with notable impact on connectivity. Sometimes the people know bestWalking Trail: official unpaved pathway with maintenance, but restricted to pedestrians onlycityplan: denotes the pathway's planning origin, as most of these were formerly proposed pathways in a city's bike/ped master plansurface: paved or unpaved. Sometimes updated, but not regularlywidth: pathway width. Generally unreliable/not updatedpiclink: not currently used, may eventually tie into our pathway conditions datasetpmid: unique ID for pathway segments. Only major pathways currently have PMID'slinearref: work-in-progress for our eventual switch to linear referencing

Copyright Text:

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:
Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 9/19/2024 4:29:30 PM

Schema Last Edit Date: 9/19/2024 4:29:30 PM

Data Last Edit Date: 9/19/2024 4:29:30 PM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat