Name: Planning Areas

Display Field: PlanAreaName

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Authoratative data source for OSMP area planning efforts including Integrated Site Plans. In addition to the ISPs, this feature class contains historical data as described below.</SPAN></P><P><SPAN>This feature class contains features from two different sources, demarcated in the field AreaType. ‘Open Space Area Management Plan’ signifies areas planned for in Area Management Plans (AMPs) by the City of Boulder Open Space Department prior to its 2001 merger with the Mountain Parks division of the Parks and Recreation Department. ‘OSMP Management Area Plan / Trail Study Area Plan’ signifies Management Areas (MAs) planned for as Trail Study Area (TSA) studies. MAs were a collection of area-specific boundaries established in the Open Space North Boulder Valley Area Management Plan and retained through the 2001 Open Space / Mountain Parks merger. MAs were later succeeded by four larger TSA boundaries—North, West, South, and East—with the adoption of the 2005 Visitor Master Plan (VMP).</SPAN></P><P><SPAN>Two of the nine MAs, Eldorado Mountain / Doudy Draw and Marshall Mesa / Southern Grasslands, had plans completed for them prior to plans created for the four TSA boundaries established in the VMP. The polygons contained in this feature class were copied from an old feature class of unknown providence that was found in a personal geodatabase in an old archive folder in \\osmpmap\data\. The feature class appears to be reliable and seems to borrow much of its geometry from the OSMP Properties (now a parcel fabric) feature class, but it has not been verified. This is the only seemingly-unmodified geometry (i.e., it has not been buffered, etc.) of the management areas known to exist after searching by RIS and P&amp;DS staff. Furthermore, the archived data contained ten polygons to represent these nine MAs because one of these MAs, Mountain Parks North TSA, contains two non-contiguous areas; the two polygons for these respective areas were merged into a single multi-part feature.</SPAN></P><P><SPAN>AMP polygons were created by the Temporary Planning Technician pursuant to a request by the Planning Supervisor. The two polygons—North Boulder Valley and South Boulder Creek—were created by different means.</SPAN></P><UL><LI><P><SPAN>The North Boulder Valley AMP defined the planning area as a collection of Open Space properties. Many of these features are not contiguous. The list of properties outlined in the report were selected and copied from the OSMP Properties parcel fabric and dissolved into a single, multi-polygon feature.</SPAN></P><P><SPAN /></P></LI><LI><P><SPAN>The South Boulder Creek AMP was not defined as a collection of Open Space lands and was instead an area encompassing Open Space land and land in-between. As no legal definition of the boundaries could be found, the polygon was digitized from the best available map within the plan. The polygon traces the roads that the plan follows, although there are segments of the boundary that do not appear to conform to any roads, property lines, or county parcel lines; in some segments, the boundary appears to skip from one road to another, and some segments do not follow any obvious cartographic feature. As-such, the South Boulder Creek boundary is sometimes a best-approximation of the feature. While there may not necessarily be any more accurate representation that can be drawn, this boundary is nonetheless more suitable for cartographic purposes and less suitable for analysis.</SPAN></P></LI></UL></DIV></DIV></DIV>

Copyright Text: Planning Supervisor: Mark Gershman, Planning & Design Services Supervisor Planning Data Steward: Charlie Philbrick, GIS Analyst I GIS Supervisor: John Morley Planning Technician: Harris Kalat

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

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 3053387.1225672215
YMin: 1207590.5736427307
XMax: 3103293.189749643
YMax: 1286736.49999623
Spatial Reference: 2876  (2876)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Link ( type: esriFieldTypeString, alias: Link, length: 250 )
• PlanAreaName ( type: esriFieldTypeString, alias: PlanAreaName, length: 100 )
• ProjectType ( type: esriFieldTypeString, alias: ProjectType, length: 100 )
• Status ( type: esriFieldTypeString, alias: Status, length: 50 )
• WorkingFolder ( type: esriFieldTypeString, alias: WorkingFolder, length: 200 )
• DateTo ( type: esriFieldTypeDate, alias: DateTo, length: 8 )
• Display ( type: esriFieldTypeString, alias: Display, length: 3 )
• DateFrom ( type: esriFieldTypeDate, alias: DateFrom, length: 8 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )

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

  Iteminfo   Thumbnail   Metadata