ArcGIS REST Services Directory Login
JSON | SOAP

Open_Space_Trails (FeatureServer)

View In: ArcGIS JavaScript   ArcGIS Online Map Viewer

Service Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>These data represent the trails owned and managed by JCOS.</SPAN></P><P><SPAN>Data Type: Line</SPAN></P><P><SPAN>Sensitive: No</SPAN></P><P><SPAN>Source of Origin: JCOS</SPAN></P><P><SPAN>Creation Means</SPAN><SPAN>: JCOS creates and maintains trail data through a combination of GPS data collection, heads-up digitizing, and a combination of the two methods.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>Original Projection: NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet (WKID: 2232)</SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Business Rules:</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>1. Features are segmented by trail name, at intersections (including intersections with NonJCOSTrails, and where Park Association changes (indicated by Park Association_FK field).</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>2. A new GIS_ID_PK is created for each new segment.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>3. A new GIS_ID_PK is created for one new segment resulting from a split, one feature will retain original GIS_ID_PK.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>4. Fully attribute Trail_Difficulty_Rating, User_Type, and Concept fields (no Nulls).</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>5. Trail junctions with 'triangles' must contain vegetation within the triangle. Otherwise, the intersection will be a 'T'.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Guidelines:</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>1. Avoid trail segments shorter than 15 feet.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>2. Digitization direction should be outward from the main trailhead.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>

All Layers and Tables

Has Versioned Data: false

MaxRecordCount: 2000

Supported Query Formats: JSON

Supports Query Data Elements: true

Layers: Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>These data represent the trails owned and managed by JCOS.</SPAN></P><P><SPAN>Data Type: Line</SPAN></P><P><SPAN>Sensitive: No</SPAN></P><P><SPAN>Source of Origin: JCOS</SPAN></P><P><SPAN>Creation Means</SPAN><SPAN>: JCOS creates and maintains trail data through a combination of GPS data collection, heads-up digitizing, and a combination of the two methods.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>Original Projection: NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet (WKID: 2232)</SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Business Rules:</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>1. Features are segmented by trail name, at intersections (including intersections with NonJCOSTrails, and where Park Association changes (indicated by Park Association_FK field).</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>2. A new GIS_ID_PK is created for each new segment.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>3. A new GIS_ID_PK is created for one new segment resulting from a split, one feature will retain original GIS_ID_PK.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>4. Fully attribute Trail_Difficulty_Rating, User_Type, and Concept fields (no Nulls).</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>5. Trail junctions with 'triangles' must contain vegetation within the triangle. Otherwise, the intersection will be a 'T'.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Guidelines:</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>1. Avoid trail segments shorter than 15 feet.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>2. Digitization direction should be outward from the main trailhead.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>

Service Item Id: 00dca05ae60448d7ae2e24b6d086f485

Copyright Text: Jefferson County Open Space (JCOS)

Spatial Reference: 102654  (2232)  LatestVCSWkid(0)


Initial Extent: Full Extent: Units: esriFeet

Document Info: Enable Z Defaults: false

Supports ApplyEdits With Global Ids: false

Support True Curves : true

Only Allow TrueCurve Updates By TrueCurveClients : true

Supports Return Service Edits Option : true

Supports Dynamic Layers: false

Child Resources:   Info   Query Data Elements   Relationships

Supported Operations:   Query   Query Contingent Values   QueryDomains   Extract Changes