3 counties indexed. ArcGIS FeatureServer and MapServer URLs, with supported search fields per layer.
| County | Endpoints | Searchable fields | Status | Action |
|---|---|---|---|---|
| Denver County | 1 | Parcel ID · County Name (filter: 'Denver') · County FIPS Code (filter: '031') +3 | LIVE | OPEN |
| El Paso County | 1 | Parcel ID · County Name (filter: 'El Paso') · County FIPS Code (filter: '041') +3 | LIVE | OPEN |
| Jefferson County | 1 | Parcel ID · County Name (filter: 'Jefferson') · County FIPS Code (filter: '059') +3 | LIVE | OPEN |
Colorado runs a true statewide parcel composite maintained by the Governor's Office of Information Technology (OIT) GIS Program. A single FeatureServer endpoint — gis.colorado.gov/public/rest/services/Address_and_Parcel/Colorado_Public_Parcels/FeatureServer/0 — covers all 64 counties. You select a county by filtering countyName or the 3-digit countyFips. This is the same architectural pattern as New York's statewide ITS layer, and it is similarly unusual: most western states leave parcel publication entirely to individual counties.
Colorado OIT operates the statewide composite under the Colorado Geographic Information Systems Program. County assessors submit parcel records to the program; OIT integrates them into the composite and publishes updates as counties submit them. The cadence varies by county — the dateReceived field on each record reflects when that county's latest submission was ingested. Field names in the composite are normalized: owner appears as 'owner' and 'owner2', address as 'situsAdd', 'sitAddCty', 'sitAddZip'. This normalization is the clearest difference from Illinois or Arizona, where you must learn a different field schema per county. The tradeoff is attribute depth: Colorado's composite carries 34 fields, fewer than many dedicated county layers. For deeper building characteristics or legal descriptions, individual county GIS portals often have more.
Colorado OIT uses the 3-digit county portion of the FIPS code in the countyFips field, not the full 5-digit federal code. Denver is '031' (not '08031'), El Paso is '041' (not '08041'), Jefferson is '059' (not '08059'). Either countyName or countyFips works as a filter, but if you're building a query from a FIPS lookup table that stores the 5-digit code, strip the leading '08' before querying. Both predicates produce the same record set; countyName is easier to read and less error-prone.
Denver County and the City of Denver are the same entity under Colorado law. In the statewide composite, countyName='Denver' and sitAddCty='Denver' will often match the same records, but the countyName field is what scopes the query to Denver County parcels. There are no separate city and county filters to worry about, and no incorporated suburbs that need separate treatment — Denver city limits are Denver county limits.
The composite carries 'owner' and 'owner2' with no further decomposition (no separate first/last/company fields). Owner LIKE queries work and are confirmed live for all three atlas counties. The composite does not carry assessment-level identifiers like an APN equivalent — parcel_id is the identifier, formatted as a county-specific string. Legal descriptions are present in legalDesc but are often truncated in the composite layer; the originating county's own GIS service will have the full text.
Consolidated city-county, Denver metro core (FIPS 08031). Filter with countyName='Denver' or countyFips='031'. Owner queries confirmed live with real Denver addresses. Includes saleDate, salePrice, apprValTot, zoningCode, and zoningDesc fields.
Colorado Springs metro (~730,000 residents, FIPS 08041). Second most populous county. Same statewide composite endpoint, filter countyName='El Paso'. Owner query confirmed returning real El Paso results. Note: no relation to El Paso County, Texas.
Denver's western suburbs — Lakewood, Arvada, Golden (~582,000 residents, FIPS 08059). Filter countyName='Jefferson' or countyFips='059'. Owner query confirmed (e.g., 'SMITH STEVEN W' at a Littleton address). Gateway county for Rocky Mountain foothills parcel research.
All three atlas counties use the same endpoint; only the countyName filter changes. Denver owner search: ?where=countyName='Denver' AND UPPER(owner) LIKE UPPER('%25SMITH%25')&outFields=parcel_id,owner,situsAdd,sitAddCty,zoningCode,apprValTot&returnGeometry=false&f=json. El Paso: ?where=countyName='El Paso' AND UPPER(owner) LIKE UPPER('%25SMITH%25')&outFields=parcel_id,owner,situsAdd,sitAddCty&returnGeometry=false&f=json. Address lookup across the state: ?where=UPPER(situsAdd) LIKE UPPER('%25MAIN ST%25') AND countyFips='059'&outFields=parcel_id,owner,situsAdd,sitAddCty&returnGeometry=false&f=json.
Last updated 2026-05-24.
3 Colorado counties are indexed in the UrbanKit atlas with verified public REST endpoints: Denver, El Paso, and Jefferson. Each exposes an owner-name field you can search directly on the public layer.
Denver, El Paso, and Jefferson expose an owner-name field on the public REST layer. Denver, for example, uses the owner field — a case-insensitive search is ?where=UPPER(owner)%20LIKE%20UPPER('%25SMITH%25')&outFields=*&f=json. Open a county's page here for its full field list and a ready-to-run sample query.
Denver publishes parcels at https://gis.colorado.gov/public/rest/services/Address_and_Parcel/Colorado_Public_Parcels/FeatureServer/0 — a FeatureServer (layer 0). It indexes by Parcel ID, County Name (filter: 'Denver'), County FIPS Code (filter: '031'), and Situs Address. Owner-name search: UPPER(owner) LIKE UPPER('%25SMITH%25').
Colorado's indexed counties (Denver, El Paso, and Jefferson) publish ArcGIS FeatureServer layers — the newer ArcGIS Online-hosted format. FeatureServer supports the /query operation for owner, parcel-ID, and address lookups.
Listing missing or moved? Tell us — we verify and update weekly.