ArcGIS REST Services Directory Login | Get Token
JSON

Layer: Park Trail (ID: 0)

Name: Park Trail

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: Description: These trails represent the walking, hiking, biking, or ADA-accessible paths in parks and natural areas. The following are the types of trails included within this feature class: Accessible Trail- ADA-accessibleBridge- A bridge crosses over a parkGreenway- These are "ProposedGreenways" that aim to connect all the natural areas within San MarcosHike/Bike Trail- A trail that one may hike or bike if they wishPark Access Road- A cross between a road and a trail that leads up to the entrance of a natural areaFor GPS process and accuracy details as well as collection dates for the trails, see the metadata for EditedInspections.SMINSPECT.pkTrail_QCFor further notes on the updating of Purgatory trails after their Spring 2017 QC, please see the images in Arcfile/Maps/Katie/Parks/SMGA/Purgatory. They are "April 2017 re-hike notes" and "April 2017 re-hike notes part 2." In June 2017, the remainder of Purgatory was GPSed by the IT GIS Analyst. These trails were drawn into production by the IT GIS Analyst on 6/28/2017. On this same day, Joel Barks of the San Marcos Greenbelt Alliance confirmed that Nimrod is closer to Ripheus than the EditedInspections.SMINSPECT.pkTrail_QC indicates. The IT GIS Analyst accidentally hiked a renegade in that pkTrail_QC layer, so she drew the northern arch of Nimrod closer to Ripheus as indicated by Joel, the aerial imagery, and as is visible in the field. (The trail markers get confusing out there. Even for the SMGA guys.) Joel also confirmed that although the trail marker poles in the field indicate the existence of an "Ovid," there are only Ovid East and Ovid West. The gap in the GPS layer pkTrail_QC was solved by Joel, and dictated to Katie. So she filled it in according to him, and also based off our old data, as it was a short distance.

Copyright Text:

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

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