Marginal_Land (FeatureServer)

View In: ArcGIS JavaScript ArcGIS Online Map Viewer

Service Description: <div style='text-align:Left;'><div><div>Marginally used land was defined and example areas initially identified in aerial imagery by the Food in Communities team. Additional samples for model training were created and identified by the Public Health GIS Analyst.Model had to be run in 3 "chunks" of aerial data area due to resource constraints. Outputs from these 3 areas were mosaiced to form 1 single image with overlap between the 3 areas (overlap created by including overlap image tiles between the 3 mosaiced areas). The full area analyzed includes the "metro" area - generally East of 470 and North of Chatfield Reservoir. Originally analyzed against 2022 aerial data because 2024 was not available at analysis start. Object detection results where further analyzed as follows: <ul><li>merge the 3 outputs into single output and erase impervious surfaces</li><li>intersect on parcels, then dissolve this result on parcel PIN number. </li><li>calculate sum marginal land area within each parcel</li><li>join this result to each of the following, using Parcel PIN number: <ul><li>parks from POI layer, libraries, schools, and places of worship (all of these must first be spatially joined to Parcel)</li><li>polygon park and polygon open space layers which have assigned parcel PINs making up the park or open space area (will result in multiple parcels assigned to each park or open space)</li></ul></li></ul>Not all areas identified as marginally used land will have a park, library, school, or open space area associated with them. The "source" field tells the user what, if any association exists. For more information on this process contact healthdata@jeffco.usStatic dataset. Created August 2025Projected to State Plane, Colorado Central FIPS0502, NAD83 (US feet)</div></div></div>

All Layers and Tables

Has Versioned Data: true

MaxRecordCount: 2000

Supported Query Formats: JSON

Supports Query Data Elements: true

Layers:

Marginal Land (121)

Description: Marginally used land was defined and example areas initially identified in aerial imagery by the Food in Communities team. Additional samples for model training were created and identified by the Public Health GIS Analyst.Model had to be run in 3 "chunks" of aerial data area due to resource constraints. Outputs from these 3 areas were mosaiced to form 1 single image with overlap between the 3 areas (overlap created by including overlap image tiles between the 3 mosaiced areas). The full area analyzed includes the "metro" area - generally East of 470 and North of Chatfield Reservoir. Originally analyzed against 2022 aerial data because 2024 was not available at analysis start. Object detection results where further analyzed as follows: merge the 3 outputs into single output and erase impervious surfacesintersect on parcels, then dissolve this result on parcel PIN number. calculate sum marginal land area within each parceljoin this result to each of the following, using Parcel PIN number: parks from POI layer, libraries, schools, and places of worship (all of these must first be spatially joined to Parcel)polygon park and polygon open space layers which have assigned parcel PINs making up the park or open space area (will result in multiple parcels assigned to each park or open space)Not all areas identified as marginally used land will have a park, library, school, or open space area associated with them. The "source" field tells the user what, if any association exists. For more information on this process contact healthdata@jeffco.usStatic dataset. Created August 2025Projected to State Plane, Colorado Central FIPS0502, NAD83 (US feet)

Service Item Id: dacbc21a0a364cd78c522be564bf68a2

Copyright Text: Jefferson County Public Health, Jefferson County Assessors Office

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 Append Extract Changes Get Estimates