ArcGIS REST Services Directory Login | Get Token
JSON

Layer: Pedestrian and Bicycle Gaps (ID: 47)

Name: Pedestrian and Bicycle Gaps

Display Field: SPEC_TYPE

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: Field DefinitionsID Number Arranged to correspond to the gap’s demand scoreGap TypePedestrian and bicycle gap – no trail or sidewalk existsBicycle gap – only sidewalk existsGap StatusCurrent gap – gap currently exists, and is of immediate concernFuture gap – gap along a future road, or gap on a rural area slated for growth, or both.Demand ScoreEleven criteria were used to determine the existing demand for all gaps. Road volume, speed, and number of lanes were not applied to the score of gaps along MnDOT and local roads. Dual Bicycle and pedestrian gaps were weighted double. The 11 criteria are:PopulationEmploymentShopping and ServicesHouseholds without VehiclesSchools TransitYoung and Old PopulationRBTNRoad VolumeRoad LanesSpeed LimitOwnershipThe ownership of the adjacent roadway, or the agency defining the gap if the gap is not located along a roadway, such as a greenway gap.Regional Bicycle Transportation Network (RBTN)The RBTN, defined by the Metropolitan Council, designation of the gap.Tier 1 AlignmentTier 2 AlignmentTier 1 CorridorTier 2 CorridorRegional SystemWhether the gap is part of Dakota County’s planned regional greenway systemGap WeightEach number represents the relation of a gap to the other side of a road1 – Sidewalk, trail other side2 – No trail/sidewalk, trail other side 3 – Sidewalk both sides4 – Sidewalk, no trail/sidewalk other side5 – No trail/sidewalk, sidewalk other side6 – No trail/sidewalk both sidesCounty PlannedA gap line recognizes the existence of a trail gap, and not whether the County plans on completing it. This field was created to define the cases where it has been determined that the cost of a trail is prohibitively expensive due to ROW needs and other factors. MunicipalityThe city or town the gap is located in.

Copyright Text:

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata