ArcGIS REST Services Directory
JSON

Layer: Project Locations - Lines (ID:1)

View In:   Map Viewer

Name: Project Locations - Lines

Display Field: ID_NUMBER

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description:

Field Definitions

  1. ID Number

    Arranged to correspond to the gap’s demand score

  2. Gap Type

    1. Pedestrian and bicycle gap – no trail or sidewalk exists

    2. Bicycle gap – only sidewalk exists

  3. Gap Status

    1. Current gap – gap currently exists, and is of immediate concern

    2. Future gap – gap along a future road, or gap on a rural area slated for growth, or both.

  4. Demand Score

    Eleven 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:

    1. Population

    2. Employment

    3. Shopping and Services

    4. Households without Vehicles

    5. Schools

    6. Transit

    7. Young and Old Population

    8. RBTN

    9. Road Volume

    10. Road Lanes

    11. Speed Limit

  5. Ownership

    The 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.

  6. Regional Bicycle Transportation Network (RBTN)

    The RBTN, defined by the Metropolitan Council, designation of the gap.

    1. Tier 1 Alignment

    2. Tier 2 Alignment

    3. Tier 1 Corridor

    4. Tier 2 Corridor

  7. Regional System

    Whether the gap is part of Dakota County’s planned regional greenway system

  8. Gap Weight

    Each number represents the relation of a gap to the other side of a road

    1. 1 – Sidewalk, trail other side

    2. 2 – No trail/sidewalk, trail other side

    3. 3 – Sidewalk both sides

    4. 4 – Sidewalk, no trail/sidewalk other side

    5. 5 – No trail/sidewalk, sidewalk other side

    6. 6 – No trail/sidewalk both sides

  9. County Planned

    A 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.

  10. Municipality

The city or town the gap is located in.



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: FID

Unique ID Field:

Global ID Field:

Type ID Field: CIP_Year

Fields:
Types:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 7/12/2022 1:36:10 PM

Schema Last Edit Date: 7/12/2022 1:36:10 PM

Data Last Edit Date: 7/12/2022 1:36:10 PM

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