Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This feature class contains the three types of designated access location point data that are managed by OSMP: Trailheads (TH), Access Points (AP) and Access to Recreational Features (ARF). These data can be queried out using the 'AccessType' field. </SPAN></P><P><SPAN /></P><P><SPAN>Data contained in this file shows all designated THs, APs and ARFs. Two access points (Old Mesa and Lion''s Lair at Sunshine Canyon) are sensitive data and should not be displayed to the public. There are also several access points in this dataset that have not been officially designated yet. They have an 'AccessID' of '1003', '1004 and '1005' and are excluded from the dataset along with archived data using the following query: CURRENT_TIMESTAMP between DateFrom and DateTo. The query should be used at all times.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This spatial view displays current Trail Closures as enacted by Open Space & Mountain Parks.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This layer is the authoritative source for Trails in the OSMP System. These data represent OSMP's designated trails. All trails in this dataset are also managed by OSMP, even though some trails are actually owned by other agencies. </SPAN></P><P><SPAN><SPAN>Trails that are displayed have Display = Yes and the current date falls between DateFrom and Date To.</SPAN></SPAN></P><P><SPAN><SPAN>In general, each trail has been broken up into segments, between junctions. The unique ID for each trail segment is within the "RID" field, which is unique over time. This means the RID of a trail segment can change over time, for example when a new alignment occurs. Each trail segment has a unique ID, within the "SegmentID" field, that never changes over time.</SPAN></SPAN></P><P><SPAN><SPAN>All trails are routes and have directionality and measures associated with them. The measures are based on the field measured trail length. Field measured trail length is stored in the "MeasuredFeet" field and GIS trail length is stored in the "shape.length" field. If there was no measured feet calculated it will read -9999. Currently the "Mileage" field is based on GIS trail length and not the field measured length. These data are topologically connected to the Trail Junctions feature class.</SPAN></SPAN></P><P><SPAN><SPAN>When a segment is replaced, it is not removed. The DateFrom and DateTo are filled in to indicated it has been retired.</SPAN></SPAN></P><P><SPAN><SPAN>This FC relates to the trailtblDogRegulations to display detailed dog regulations, based on RID. Maintained in the FC are fields to indicate whether horses and bikes are allowed on each segment. This FC also relates to the trailtblTrailClassDesignedUse and trailtblManagedUse to display detailed trail manegment objectives, based on RID.</SPAN></SPAN></P><P><SPAN><SPAN>Data are primarily managed and edited by the Trails Research coordinator. Starting in 2019, 1/5 of the system is surveyed every year and any changes in alingnments are made. Surveys are done using HETAP (High Efficiency Trail Assesment Program). Throughout the year any new trails that open are added once they have been surveyed. </SPAN></SPAN></P><P><SPAN><SPAN>The trails that are current and designed for display are copied over to GISProd3 each year. </SPAN></SPAN></P><P><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Contains polygons that delineate trail maintenance zones. Each zone has a designated trail crew leader. Polygons were created by Greg Seabloom and updated in 2017 by Chad Brotherton. Zones are also used to delineate annual surveys for trail condition monitoring. </SPAN></P></DIV></DIV></DIV>