This dataset depicts the spatial extent of RELINQUISHED (former) easement data collected by Public Works - Survey. Easement data in this layer include, but are not limited to: sidewalk easements, other right-of-way easements, storm water and sanitary easements not depicted by Wastewater Management Division, other utility easements, access easements, and other conservation easements. Attribute information for this layer includes easement type, grantor/grantee, date of easement, the document(s) establishing the easement, and the document(s) relinquishing the easement.
The easements in this layer date primarily from 1994 to the present although easements before 1994 may also be portrayed in this layer. These easements are not depicted on the City Engineering quarter-section maps.
This layer represents light rail station locations and areas of transit oriented development (TOD).
This data is compiled from various sources by Community Planning and Development (CPD) for Transit Oriented Development (TOD) planning analysis. This is not legal data.
These data contain railroad owner and track rights information.
RTD Route locations within the Denver Metropolitan Area.
The physical location where passengers can board and depart buses.
RTD Park-N-Ride locations within the Denver Metropolitan Area.
This dataset contains three categories of data. First, it includes information regarding the project(s) authorizing the sampling. Second, it includes information regard the location and depth of sampling with respect to city addressing, street grid, and local landmarks. Finally, the dataset includes the results of sampling, including soil typing and characterization, lab test results of the soils, and depth to water under the road surface.
This dataset contains tree canopy polygons for the City and County of Denver for the year 2018.
The City and County of Denver's Street Route features constructed from the City's Street Centerline layer. Route geometry is the continuous street length until it stops at a \"T\" intersection or a street end. The route name contains \"W\" or a \"S\" for streets containing a West or South directional (respectively) within the street name. The routes are numbered and increase from Broadway - to the East and again to the West. Route numbering also begins at Elsworth - increasing to the North and again to the South
Location of Department of Environmental Health (DEH) in-stream sampling locations along the South Platte River and are based on macroinvertebrate sampling performed from 1996-2003. These desginations apply only to locations that are designated as \"glide\" sites. This is a subset of those sites listed in the ENV_BENTHICSITES_P layer.
This layer contains information on where the house districts in Colorado are, the names of the representatives that serve each district, and the party affiliation of each representative. The original shapefile is a product of the 2011 Colorado State Reapportionment Commission. DenverGIS later modified this file to match to Denver Streets and Boundarys. Schema changes were enacted to remove unnecessary fields. Updated in 2023.
This layer contains information on where the Senate districts in Colorado are, the names of the representatives that serve each district, and the party affiliation of each representative. The original shapefile is a product of the 2011 Colorado State Reapportionment Commission. DenverGIS later modified this file to match to Denver Streets and Boundarys. Schema changes were enacted to remove unnecessary fields. Updated on 2023
There are two sources for the subdivision boundary layer. The first is a legacy shapefile of subdivision boundaries which was created and edited separately from the subdivision lots and ownership parcel layers. Due to the independent creation and maintenance of these layers, it is common to see line data separation between subdivision boundaries, lots, and parcels where no legal separation exists. Editing of this dataset more or less ceased at the end of 2010.Beginning in January 2011, new subdivisions have been created and maintained using the ESRI Parcel Fabric data model. In addition, as conditions permit, older subdivisions are re-drawn to original plat and/or City-resurveyed dimensions, and added to the Parcel Fabric dataset. When these older subdivisions are added to the Parcel Fabric, the legacy shapefile representation of the subdivision boundary is deleted.For display on the City website and download from the Open Data Catalog, these two sources are combined into one subdivision layer. Subdivisions based on the Parcel Fabric data model will have a SYSTEM_START_DATE value of January 2011 or later, and will be consistent with underlying lot and parcel data.
Traffic signals within and near the City and County of Denver
This dataset contains tree canopy polygons for the City and County of Denver for the year 2020.
2010 Census Block Group polygons with attributes for tree canopy cover, potential tree planting spaces, and land cover classification summaries.
Metro Denver City boundary polygons with attributes for tree canopy cover, potential tree planting spaces, and land cover classification summaries.
Polygon representation of 8 land use classifications: agriculture, commercial, industrial, mixed uses, multi-family residential, open space, public-quasi public, and single family residential.
This layer was created as described in ordinances referenced in Denver Municipal Code. Upon consideration of a recommendation that an ordinance be enacted for the purpose of preserving and protecting the health, safety and general welfare of the people of the city and their property therein situate, the council finds:
Data set depicts the historic locations of street car tracks within Denver.
The Alleys of the City and County of Denver. This dataset contains centerlines representing alley locations. This dataset was originally produced by R and S Digital, Goodland, Kansas. Extensively updated and maintained by the City and County of Denver's GIS Department. Additionally the layer has been joined to Public Works Street Maintenance Alley Inventory to increase value of the layer.
This metadata describes the stereocompiled paved sidewalks and paved trails polygons feature of DRCOG Denver Region Urbanized Project Area. The feature was compiled from the Denver Regional Aerial Photography Project (DRAPP) 2020 Aerial Imagery Acquisition and Production. This 1\"=100' scale imagery is comprised of 4-band RGBIR color orthoimagery with a GSD (Ground Sample Distance) of 0.5'. Imagery was collected with the Leica ADS40 and ADS80 digital sensors and processed with Leica XPro software. Imagery is projected in State Plane Coordinate System, Colorado central zone using the Lambert Conformal Conic map projection parameters. Horizontal and vertical datums are NAD83(11) and NAVD88(GEOID12A) respectively.
Contributing structures within designated Denver Historic Districts. These are identified in the ordinance that establishes a Historic District - ONLY those which are specifically listed within the district ordinance are included.
Locations of Head Start program administrative offices within the City and County of Denver.
The Intersection Nodes of the City and County of Denver, Colorado. The City and County of Denver's intersection features. This dataset contains points representing the intersections of streets. These normally occur at the end of blocks or where the street changes name. Streets crossing rail lines or structures may also result in an intersection point.
This dataset denotes the approximate locations of historical fill areas within the City and County of Denver (CCoD) and with within approximately three-quarters of a mile of the CCoD boundaries. The data was developed in 1997 by Pinyon Environmental Engineering Resources, Inc. (Pinyon) who at the request of CCoD completed an Historical Fill Area Evaluation using documents and research involving several regional and national sources listed in the Lineage, Process Step 1\" section of this document. Locations of historical fill areas are approximations and should not be used for detailed planning or engineering purposes.
An Index of the Existing Waste Water Plat Maps for the City and County of Denver.
Tree canopy delineations developed using LiDAR Point Cloud Data produced by FEMA in 2014, NAIP Imagery from 2013, and high resolution orthoimagery from 2014. Produced using and object-based classification method.
Block Group level data from the American Community Survey; 5 year average, years 2017-2021. The data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a census. Results should be considered estimates. Margin of error data provided where appropriate. See American Community Survey website for additional information.
Census Tract level data from the American Community Survey; 5 year average, years 2017-2021. The data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a census. Results should be considered estimates. Margin of error data provided where appropriate. See American Community Survey website for additional information.
Neighborhood level data from the derived from the American Community Survey; 5 year average, years 2017-2021. Data was aggregated at the census tract level, and the summarized into neighborhoods. This information was then joined with Community Planning and Developments Neighborhoods layer. This data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a census. Results should be considered estimates. Since this data was internally derived by the City and County of Denver from census tract level data, Margin of Error statistics from the census tract data could not be accurately aggregated for the neighborhood level data. Therefore, the Margin of Error data is not provided with this data set. Users should use caution as data values are estimates.
This document specifies a set\r\nof ArcGIS Online (AGOL) standards that provides a consistent and maintainable\r\nstructure for data stewards and users to follow, which will help to ensure the\r\nintegrity of the data, as well as data sharing, integration, and compatibility\r\nwithin the City and County of Denver’s Geographic Information System (GIS). The\r\nobjective of these standards is to assist agencies responsible for the\r\ncreation, maintenance, and distribution of ArcGIS Online (AGOL) datasets by\r\nreducing the efforts and costs of data sharing, data development, and data\r\nmaintenance.
\r\n\r\nGeospatial data are valuable\r\nassets that support the business needs of the city and public. Creation and\r\nmaintenance of accurate and complete geospatial datasets improves the quality,\r\naccuracy, efficiency, and responsiveness of government services. Maintaining a\r\nhigh-level of geospatial data quality is imperative. Each AGOL dataset shall\r\ncomply with the standards described in this document. This document includes\r\n(1) user standards, (2) data standards, (3) metadata standards (4) sharing\r\nstandards, (5) group standards, (6) annual audit standards, (7) security\r\nstandards, (8) branding standards, and (9) accessibility standards.
\r\n\r\nThese standards will be\r\ncontinually monitored and reviewed both for compliance among data users and for\r\ntheir effectiveness, benefits, and adverse impacts. The providers and users of\r\ndata will be regularly consulted regarding the work they undertake to comply\r\nwith the standards, whether additional workload is created to use the data\r\nbased on the standard, and the magnitude of that workload.
\r\n\r\nA goal of these standards is\r\nto improve work efficiency in the long term; not to create an increased and\r\nunnecessary workload.
", "keyword": [ "ODC" ], "issued": "2023-09-08T15:10:53.000Z", "modified": "2024-05-14T21:45:36.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS—The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::agol-standards" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=be535ebb3c6243edbfc89dce330cbace", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/apps/geospatialDenver::arcpro-training", "title": "ArcPro Training", "description": "The ArcPro Training is a basic training sent as a standard for all new ArcPro users.
Topics and concepts include migrating from ArcMap, maps/scenes, symbology, labels, sharing, and geoprocessing.
Includes training videos, resource links, and tutorials.
", "keyword": [ "ODC" ], "issued": "2023-03-24T19:18:48.000Z", "modified": "2024-05-14T21:45:36.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "ACCESS CONSTRAINTS: None. USE CONSTRAINTS: The City and County of Denver is not responsible and shall not be liable to the user for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use of the data/information provided. NOT FOR ENGINEERING PURPOSES", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/apps/geospatialDenver::arcpro-training" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://storymaps.arcgis.com/stories/be535ebb3c6243edbfc89dce330cbace" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=3d1dd6c37ef9403fafc57798ccb4aa16&sublayer=337", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::american-community-survey-tracts-2016-2020", "title": "American Community Survey Tracts (2016-2020)", "description": "Census Tract level data from the American Community Survey; 5 year average, years 2016-2020. The data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a census. Results should be considered estimates. Margin of error data provided where appropriate. See American Community Survey website for additional information.", "keyword": [ "ODC" ], "issued": "2022-04-19T15:06:05.000Z", "modified": "2024-05-14T17:51:05.287Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "-105.1100,39.6144,-104.5994,39.9135", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::american-community-survey-tracts-2016-2020" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_POP_AMERCMTYSVY20162020TRACT_A/FeatureServer/337" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/3d1dd6c37ef9403fafc57798ccb4aa16/csv?layers=337" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/3d1dd6c37ef9403fafc57798ccb4aa16/shapefile?layers=337" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/3d1dd6c37ef9403fafc57798ccb4aa16/geojson?layers=337" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/3d1dd6c37ef9403fafc57798ccb4aa16/kml?layers=337" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/3d1dd6c37ef9403fafc57798ccb4aa16/filegdb?layers=337" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/3d1dd6c37ef9403fafc57798ccb4aa16/featureCollection?layers=337" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/3d1dd6c37ef9403fafc57798ccb4aa16/excel?layers=337" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/3d1dd6c37ef9403fafc57798ccb4aa16/geoPackage?layers=337" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/3d1dd6c37ef9403fafc57798ccb4aa16/sqlite?layers=337" } ], "theme": [ "geospatial" ] }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=c0e92f0f055443a8a4c9d9254f8e2e7b&sublayer=341", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::american-community-survey-blk-grp-2016-2020", "title": "American Community Survey Blk Grp (2016-2020)", "description": "Block Group level data from the American Community Survey; 5 year average, years 2016-2020. The data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a census. Results should be considered estimates. Margin of error data provided where appropriate. See American Community Survey website for additional information.", "keyword": [ "ODC" ], "issued": "2022-04-19T15:00:14.000Z", "modified": "2024-05-14T17:52:57.628Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "-105.1100,39.6144,-104.5994,39.9135", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::american-community-survey-blk-grp-2016-2020" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_POP_AMERCMTYSVY20162020BLKGP_A/FeatureServer/341" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c0e92f0f055443a8a4c9d9254f8e2e7b/csv?layers=341" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c0e92f0f055443a8a4c9d9254f8e2e7b/shapefile?layers=341" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c0e92f0f055443a8a4c9d9254f8e2e7b/geojson?layers=341" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c0e92f0f055443a8a4c9d9254f8e2e7b/kml?layers=341" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c0e92f0f055443a8a4c9d9254f8e2e7b/filegdb?layers=341" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c0e92f0f055443a8a4c9d9254f8e2e7b/featureCollection?layers=341" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c0e92f0f055443a8a4c9d9254f8e2e7b/excel?layers=341" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c0e92f0f055443a8a4c9d9254f8e2e7b/geoPackage?layers=341" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c0e92f0f055443a8a4c9d9254f8e2e7b/sqlite?layers=341" } ], "theme": [ "geospatial" ] }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=f298a05190724b0aaf7f6a76f260aa7d&sublayer=298", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::equity-index-2020-neighborhood", "title": "Equity Index 2020 - Neighborhood", "description": "Indicators Included in IndexSocioeconomic IndicatorsPercent of population in poverty (2014-2018 American Community Survey)Percent population 25 and older without a high school diploma (2014-2018 American Community Survey)Built Environment IndicatorsPark Access – Percent of units within 10-minute walk of park (Denver Parks and Recreation, 2019)Food access – Percent population within 10-minute walk (based on walkshed/walk network) to a full-service grocery storePopulation estimates from 2010 census, food stores from 2020 listAccess to CarePercent of women who did not receive prenatal care in the first trimester (Vital Records, 2017)Percent of Adults who Delayed Medical Care Due to Cost (2014-2017 - CDPHE Community Estimates Behavioral Risk Factor Surveillance System)MorbidityPercent Childhood obesity (2014-2016, BMI Surveillance System)Percent Adult depression (2016, Colorado Health Observation Regional Data Service)MortalityYears of Average Life expectancy (2011-2015, U.S. Area Life Expectancy Estimates Project)Index Score Calculation Methodology:Each indicator was updated to its most recent year/year range.The percentage or rate/prevalence for each indicator at the neighborhood level was added to a spreadsheetNote that each indicator was put in the spreadsheet in its 'negative' form - so that a higher percentage is the worse outcome; this was done so that ranking and scoring could be done in the same direction and to keep with the previous version of the index where a low score indicates more inequity, and a high score indicates less inequity (see Step 3 about ranking to learn more)The percentage/raw data spreadsheet was loaded into Stata, then grouped, ranked, and scoredThe indicators for each sub-index were ranked separately by neighborhood, then each grouped into quintilesThe quintile group became the 'score' for each indicator. The scores for each indicator were averaged together to get the sub-index scoresOnce each sub-index score is created, all sub-index scores were averaged together to get the overall equity index score per neighborhoodA spreadsheet is exported from Stata and loaded into ArcGIS ProThe spreadsheet was matched to the neighborhood boundary shapefileEach sub-index, as well as the overall index scores, were mapped and saved as layer files", "keyword": [ "ODC" ], "issued": "2020-10-22T14:59:16.000Z", "modified": "2024-05-14T16:54:30.690Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "-105.1100,39.6144,-104.5994,39.9135", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::equity-index-2020-neighborhood" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_HLTH_EQUITYINDEX2020NBHD_A/FeatureServer/298" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f298a05190724b0aaf7f6a76f260aa7d/csv?layers=298" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f298a05190724b0aaf7f6a76f260aa7d/shapefile?layers=298" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f298a05190724b0aaf7f6a76f260aa7d/geojson?layers=298" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f298a05190724b0aaf7f6a76f260aa7d/kml?layers=298" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f298a05190724b0aaf7f6a76f260aa7d/filegdb?layers=298" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f298a05190724b0aaf7f6a76f260aa7d/featureCollection?layers=298" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f298a05190724b0aaf7f6a76f260aa7d/excel?layers=298" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f298a05190724b0aaf7f6a76f260aa7d/geoPackage?layers=298" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f298a05190724b0aaf7f6a76f260aa7d/sqlite?layers=298" } ], "theme": [ "geospatial" ] }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=fc1434c125424ed8bdd81f1a16952a21&sublayer=340", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::american-community-survey-nbrhd-2016-2020", "title": "American Community Survey Nbrhd (2016-2020)", "description": "Neighborhood level data from the derived from the American Community Survey; 5 year average, years 2016-2020. Data was aggregated at the census tract level, and the summarized into neighborhoods. This information was then joined with Community Planning and Developments Neighborhoods layer. This data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a census. Results should be considered estimates. Since this data was internally derived by the City and County of Denver from census tract level data, Margin of Error statistics from the census tract data could not be accurately aggregated for the neighborhood level data. Therefore, the Margin of Error data is not provided with this data set. Users should use caution as data values are estimates.", "keyword": [ "ODC" ], "issued": "2022-04-19T15:03:37.000Z", "modified": "2024-05-14T17:52:10.514Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "-105.1100,39.6144,-104.5994,39.9135", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::american-community-survey-nbrhd-2016-2020" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_POP_AMERCMTYSVY20162020NBRHD_A/FeatureServer/340" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/fc1434c125424ed8bdd81f1a16952a21/csv?layers=340" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/fc1434c125424ed8bdd81f1a16952a21/shapefile?layers=340" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/fc1434c125424ed8bdd81f1a16952a21/geojson?layers=340" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/fc1434c125424ed8bdd81f1a16952a21/kml?layers=340" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/fc1434c125424ed8bdd81f1a16952a21/filegdb?layers=340" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/fc1434c125424ed8bdd81f1a16952a21/featureCollection?layers=340" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/fc1434c125424ed8bdd81f1a16952a21/excel?layers=340" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/fc1434c125424ed8bdd81f1a16952a21/geoPackage?layers=340" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/fc1434c125424ed8bdd81f1a16952a21/sqlite?layers=340" } ], "theme": [ "geospatial" ] }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=02d177c9e8c543c8aa881eddb0a8381f&sublayer=208", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::city-facilities", "title": "City Facilities", "description": "Location of City and County of Denver owned and insured facilities.
This data includes all 13 Community Network boundaries and their names.
This dataset shows the locations of Demolition permits as extracted from the Accela database. The permits with a permit type 'DEMO' are extracted and mapped on a daily basis. The geographic location is determined from a link to the city's address database. Some permits who do not have valid city addresses are located at 0,0, off the map. The issue date is extracted and shows the date at which the permit was paid. Currently, this data only shows the permits Issued after June 7, 2015, the date Accela went live. To view previous permits, see the layer CV_LOC_DEMOANDSPECIAL_P.
This dataset shows the locations of Commercial Construction permits as extracted from the Accela database. The permits with a permit type of 'COMMCON' are extracted and mapped on a daily basis. The geographic location is determined from a link to the city's address database. Some permits who do not have valid city addresses are located at 0,0, off the map. The issue date is extracted and shows the date at which the permit was paid. Currently, this data only shows the permits Issued after June 7, 2015, the date Accela went live. To view previous permits, see the layer CV_LOC_COMMERCIAL_P.
This dataset shows the locations of Residential Construction permits as extracted from the Accela database. The permits with a permit type of 'RESCON' are extracted and mapped on a daily basis. The geographic location is determined from a link to the city's address database. Some permits who do not have valid city addresses are located at 0,0, off the map. The issue date is extracted and shows the date at which the permit was paid. Currently, this data only shows the permits Issued after June 7, 2015, the date Accela went live. To view previous permits, see the layer CV_LOC_RESIDENTIAL_P.
Data are derived using the following process, all included in one python script: Records are extracted from the Oracle database used by Accela. They are then converted to a feature class and loaded into SDE where they are replicated to appropriate servers for publication. These data include medical center, recreational store, grow center, infused product manufacturer, and testing center licensed facilities. The tabular data include the Business Name, Business File Number (BFN), License Name, License Issue Date, License Expiration Date, Application Date, License Status, State License Number and Expiration Date, Facility Address, Location method (Accela), Council District, Police District and Census Tract in which the facility is located.
The business liquor licenses layer contains an address point where an active liquor license issued in the City and County of Denver. The layer is updated daily by overlying Denver Excise and License liquor license data with police and council districts, as well as census tracts.
Parcels within the City and County of Denver as they are represented graphically.
Description: Each point represents a residential health complaint. Data Source is Accela Residential Health Complaint Data which is updated daily. The purpose of this dataset is to merge Accela Residential Health complaint data with geolocation data used to accurately map complaint and violation data as well as to disaggregate it by neighborhood and city council district on two public-facing Residential Health Power BI dashboards. Data is imported from Accela, merged with relevant tables and cleaned to get holistic complaint data. Data goes through quality assurance checks with team once a month. The dataset is then joined with latitude, longitude, neighborhood, and city council district geo location data and published to AGOL daily. Retention policy is 4 years. Data quality is Good.
This layer shows the locations of street occupancy permits extracted from the Accela permit database. The dataset includes expired, currently active, and future scheduled permits. A single permit may encompass multiple closures across several street segments and affect different portions of the street—such as the sidewalk, a turn lane, or all lanes. The data is maintained by the Department of Transportation and Infrastructure and processed daily by the Technology Services GIS group.
Traffic accidents in the City and County of Denver. The data is based on the National Incident Based Reporting System (NIBRS). The data is dynamic, which allows for additions, deletions and/or modifications at any time, resulting in more accurate information in the database. Due to continuous data entry, the number of records in subsequent extractions are subject to change. Accident data is updated Monday through Friday.
This data layer comprises active addresses found in the Denver Address Database. Addresses included in this file may or not be mailable addresses.
License_Number - The license number (sometimes referred to as a business file number) associated to the license application.
License_Type - The type of license applied for with the Excise and Licenses in the City and County of Denver.
License_Sub_Type - The sub type of the license applied for with the Excise and Licenses in the City and County of Denver, if any.
License_Status - The status of the license application.
Entity_Name - The entity name as applied for with Excise and Licenses.
Trade_Name - The trade name as indicated in the application. This is often blank for individual license applications.
Submitted_Date - The original date the application was submitted to Excise and Licenses in the City and County of Denver.
This dataset includes criminal offenses in the City and County of Denver for the previous five calendar years plus the current year to date. The data is based on the National Incident Based Reporting System (NIBRS) which includes all victims of person crimes and all crimes within an incident. The data is dynamic, which allows for additions, deletions and/or modifications at any time, resulting in more accurate information in the database. Due to continuous data entry, the number of records in subsequent extractions are subject to change. Crime data is updated Monday through Friday.
The information provided here regarding public safety in Denver are offered as a courtesy by the City and County of Denver. By downloading this data, you acknowledge that you have read and understand the Disclaimer below and agree to be bound by it. Certain information is omitted, in accordance with legal requirements and as described more fully in this Disclaimer.
All materials contained on this site are distributed and transmitted \"as is,\" without any representation as to completeness or accuracy and without warranty or guarantee of any kind. The City and County of Denver is not responsible for any error or omission on this site or for the use or interpretation of the results of any research conducted here.
These are business licenses whose current status is 'Active'
The zoning boundaries layer is an integral part of the planning and zoning data in the City and County of Denver Geographic Information System. This data is used by the Planning Department in case review, enforcement, and long range planning. GIS data layers are accessed by personnel in most City departments for basic applications such as viewing, querying, and map output production.
This data layer represents zone map amendment boundaries for the City and County of Denver, Colorado.
Includes plans that were identified historically as several types including Planned Building Groups (PBG), DP, MPBG, PD, etc.NOT included in these plans are General Development Plans (GDP), which are contained in a separate layer (PLAN_GENDEVPLAN_A) and Planned Unit Developments (PUD), which are identified within the Zoning layer (ZONE.ZONING_A).Since 2014 plan types are generically identified as Site Development Plans (SDP) which are defined as: Those plans representing projects that have gone through the Site Development Plan process (essentially zoning entitlements, ROW improvements, Stormwater/Wastewater infrastructure review, etc) and received an approval allowing the applicant to apply for building permits. The recordation provides 18 months of entitlement to their approved plan for the reviewing agencies. An approved SDP does NOT constitute building permit approval.Plans included may have a Status of \"Recorded\" (Recorded in the office of the Clerk and Recorder), which include a link to a digital copy of the plan, or \"Under-Review\" - which are not yet recorded (or may never be recorded) and do not include a link to the plan document.
Sec. 41-19 of the Revised Municipal Code (RMC) provides that Neighborhood Organizations be informed of actions that may be of interest such as zoning and liquor license hearings. Each organization must comply with the guidelines of the ordinance. The organization must re-register with the city each year. RNOs in the city’s official RNO database have active registrations and are listed with an “Active” status. Organizations that fail to renew by January 31 are marked “Inactive,” are excluded from the city’s official RNO database, and remain only as historical records for reference.
This layer displays ordinances and resolutions relating to City and County right-of-way. Included are dedications. These actions are not depicted on City Surveyor's office linens, and are dated 1996 to the present. ROW ordinances older than 1996 but missing from the linens are also digitized in this layer.
This layer marks the locations of in-stream sample locations along Cherry Creek and The South Platte River and are based on macroinvertebrate sampling performed from 1996-2003. These designations also apply to in-stream water quality monitoring locations.
Public Works - Development Engineering Services Transportation Review Engineer. This is the Engineer that is the lead for the Transportation review for this particular geographic area. Listed are the Senior Engineer and and Area Engineer for the Transportation Reviewer Area.
The solid waste collection areas align with parcel boundaries and are used to identify which routes serve property addresses.
City and County of Denver Wastewater Management Storm Facility Data - Storm Outfalls.
City and County of Denver Wastewater Management Storm Facility Data - Storm Sewer Mains.
City and County of Denver Wastewater Management Storm Facility Data - Storm Sewer Mains.
City and County of Denver Wastewater Management Storm Facility Data - Storm Outfalls.
City and County of Denver Wastewater Management Storm Facility Data - Storm Sewer Mains.
City and County of Denver Wastewater Management Storm Facility Data - Storm Detention and Water Quality Facilities.
City and County of Denver Wastewater Management Sanitary Facility Data - Sanitary Sewer Mains.
Areas which have specific sign design guidelines / comprehensive site plans per Zone Code Section 10.10.3.3
This data is a polygon representation of recreational courts or other playing surfaces such as basketball, tennis, handball, bocce, sand volleyball, horseshoepits, and lawn bowling in parks, golf courses, and other areas maintained by the Department of Parks and Recreation in the City and County of Denver.
This layer displays ordinances and resolutions relating to City and County right-of-way (ROW). Included are vacations. These actions are not depicted on City Surveyor's office linens, and are dated 1996 to the present. ROW ordinances older than 1996 but missing from the linens are also digitized in this layer.
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org).
Since 2022, CASR added requirements for the buildings to reach a certain level of energy efficiency in their building by 2030. The most recent dataset shows the annual benchmarking data for the 3,000 buildings that have to comply, but it also now includes what their energy use intensity target is for 2030 (with interim check-ins in 2025 and 2027). The basic performance requirements are covered on this page: Performance Requirements - City and County of Denver (denvergov.org)
", "keyword": [ "ODC" ], "issued": "2026-09-22T22:25:16.000Z", "modified": "2026-09-22T22:28:15.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::energize-denver-2025-master-dataset" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=8174a75527d0464fa49d24be32646bb1&sublayer=145", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::street-centerlines", "title": "Street Centerlines", "description": "The streets and alleys of the City and County of Denver, Colorado. This dataset is continually undergoing change as they occur within the city. To determine the last change made on a particular street, consult the Editdate field for the particular road segment.
This dataset is polygon representation of parks, golf courses, and recreation managed by the Department of Parks and Recreation in the City and County of Denver. Data is based on parcel ownership and does not include other areas maintained by the department such as medians and parkways.
This dataset included procurement card transactions made to vendors by the City and County of Denver for the current year to date and previous years. The datasets are refreshed each day with the previous business day's transactions. New travel datasets cannot be provided from August 2017 due to confidentiality concerns however, historic travel datasets will be maintained.
Notice: In August 2017, the city implemented a new financial system which created new Expense categories and prompted some expenses to roll in to different or new categories. When viewing 2017 data you may have to look at several Expense categories for a complete picture. Procurement data from August 2017 to December 2017 are in a separate file. When viewing 2017 procurement data, you will need two files.
Disclaimer: The City and County of Denver is committed to the highest levels of data security and privacy, therefore not all payment transactions will be displayed. Payment transactions that are confidential are excluded from the data. Protected information such as social security numbers, banking information, and personal data are excluded from payment transaction details. Payments to retirement and health care providers include employee contributions. The data contained on this website is unaudited and is for informational purposes only. It is not the intent of the site to provide information that may be used to determine or influence the financial decisions of any website user.
For transaction inquiries, email CTLGeneralAccounting@denvergov.org
Author: City and County of Denver - CTL General Accounting
Author Email: CTLGeneralAccounting@denvergov.org
Maintainer: City and County of Denver - CTL General Accounting
Maintainer Email: CTLGeneralAccounting@denvergov.org
These datasets include accounts payable payments and procurement card transactions made to vendors by the City and County of Denver for the current year to date. These datasets include accounts payable payments and procurement card transactions made to vendors by the City and County of Denver for the current year to date and previous years. The datasets are refreshed each day with the previous business day's transactions. New travel datasets cannot be provided from August 2017 due to confidentiality concerns however, historic travel datasets will be maintained.
Notice: In August 2017, the city implemented a new financial system which created new Expense categories and prompted some expenses to roll in to different or new categories. When viewing 2017 data you may have to look at several Expense categories for a complete picture. Procurement data from August 2017 to December 2017 are in a separate file. When viewing 2017 procurement data, you will need two files.
Disclaimer: The City and County of Denver is committed to the highest levels of data security and privacy, therefore not all payment transactions will be displayed. Payment transactions that are confidential are excluded from the data. Protected information such as social security numbers, banking information, and personal data are excluded from payment transaction details. Payments to retirement and health care providers include employee contributions. The data contained on this website is unaudited and is for informational purposes only. It is not the intent of the site to provide information that may be used to determine or influence the financial decisions of any website user.
This dataset is point representation of recreation centers and program offices for the Department of Parks and Recreation in the City and County of Denver.
The Office of Emergency Management's warning siren dataset. This coverage contains the locations and attribute data for all warning sirens within the City and County of Denver.
Sirens are placed to provide uniform coverage throughout the City and County of Denver, including DIA. The vendor, Federal Signal, developed computer models that took into account topography, atmospheric conditions, structures, and other factors to determine the optimal placement of the sirens. Once the general area was determined; field work finalized suitable areas for exact siren placement. The intent was to avoid obstruction by buildings, locations where the solar panels are blocked by trees, and also to avoid locations such as the front yard of a residential property.
Geographic boundaries created to assign staff to Public Works Engineering, Regulatory, and Analytics Transportation Reviewer Areas.
This dataset is a polyline representation of the centerline of trails and side walks used for recreational purposes in parks, golf courses, and other areas maintained by the Department of Denver Parks and Recreation. Some trail information is shown outside the City and County of Denver for context and reference,
This dataset is a polygon representation of playgrounds in parks and other areas maintained by the Department of Parks and Recreation in the City and County of Denver.
This layer shows the Neighborhood Inspection Services (NIS) areas used to organize and assign inspectors across the City and County of Denver. The boundaries help ensure consistent coverage and efficient response to property maintenance and zoning concerns citywide.
Neighborhood Inspection Services helps keep Denver neighborhoods safe and well-maintained by responding to complaints, educating property owners, and enforcing city codes related to property maintenance and land use. Inspectors address common issues such as outdoor storage, parking, lawn and fence maintenance, sidewalk safety, inoperable vehicles, yard and garage sales, home businesses, excessive animals, and construction without required permits.
The Department of Public Works of the City and County of Denver performs many functions including Construction Engineering Inspection. This geographic dataset represents the Construction Engineering Inspection Districts.
City and County of Denver Wastewater Management Storm Facility Data - Storm Outfalls.
This feature class is a point database with that shows where the tie books are located and has fields that can be used to link to the scanned images of the tiebooks.
Detailed historical campaign finance data for\ncandidates, independent expenditures and political action committees.
", "keyword": [], "issued": "2024-10-14T21:50:39.000Z", "modified": "2024-12-19T22:47:40.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::denver-campaign-finance-data" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=109a5215ac034ec08c7f25f3cd64a3b6&sublayer=286", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::sanitary-manholes", "title": "Sanitary Manholes", "description": "City and County of Denver Wastewater Management Sanitary Facility Data - Sanitary Manholes.
General Development Plans (GDPs) are provided for large, complex or phased development projects in the mixed-use zone districts, including T-MU-30 and in some cases C-MU, R-MU, or OS-1. They are intended to anticipate a development program and the necessary infrastructure systems (road network, drainage, parks and open space, utilities) that will support the conceptual development. GDPs bridge the gap between comprehensive planning and site development plans by looking at proposed development at a scale more specific than area plans or Blueprint Denver, but more generally than a building or building group.
Large Development Framework Plans (LDF's) are provided for large, complex or phased development projects. They are intended to anticipate a development program and the necessary infrastructure systems (road network, drainage, parks and open space, utilities) that will support the development. IMPs bridge the gap between comprehensive planning and site development plans by looking at proposed development at a scale more specific than area plans or Blueprint Denver, but more generally than a building or building group.
Infrastructure Master Plans (IMPs) are provided for large, complex or phased development projects. They are intended to anticipate a development program and the necessary infrastructure systems (road network, drainage, parks and open space, utilities) that will support the development. IMPs bridge the gap between comprehensive planning and site development plans by looking at proposed development at a scale more specific than area plans or Blueprint Denver, but more generally than a building or building group.
A Regulating Plan is used to apply allowed building types, building heights and land uses to specific street frontages and specific blocks and / or zone lots within a zone district. A regulating Plan is also a vehicle for the designation of Primary Streets and Side Streets in advance of site development to increase the predictability and certainty of future development under this Code. A Regulating Plan is an optional step and process in all Zone Districts except in the M-GMX Zone District. An approved Regulating Plan provides a binding plan that narrows the broad flexibility otherwise allowed in the Zone District as site specific development proceeds within the subject area.
All Regulatory Plans must be researched individually to determine the implications it conveys to the underlying zone district.
Design Review is required through the establishment of Design Standards and Guidelines through several zoning districts as well as seperate rules and regulations applied to certain properties throughout the City. Design Standards and Guidelines are frequently established through the General Development Plan process and encouraged through small area plan recommendations.
Each point record contains data about the document, name of the image file for the document and path to the file. When available, project number, reception number, grantor, grantee, ¼ section, date mapped, date verified, comments, and description are provided. There is also a field called “feature_ID” which is used to capture a key ID to be used to link this data to the Wastewater Easements (multiple feature classes) Layer.
The annexation layer displays the areal extents of the annexations of the City and County of Denver from 1864 to the present.
Boundaries as defined by ordinance for City and County of Denver Local Maintenance Districts. A Local Maintenance District (LMD) is formed when a group of neighbors, especially businesses, wish to upgrade the streetscape with special features like special pedestrian lights, benches, flowers, and other such amenities. Properties benefitting by the district pay special assessments to maintain these items. This map shows the boundaries that are defined by a legal description in the ordinance that creates each LMD. It is used by Development Review staff to advise developers about the existence of the LMD and the probability that they will be required to contribute to the annual assessment.NOTE: BENEFITED PROPERTIES, ALSO DEFINED BY ORDINANCE, ARE NOT MAPPED IN THIS LAYER!
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/maps/5f6f15cf7a864195a318b7d8c27af4f1" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=d72c6f301a604829bfaeb3ba4d4375f2&sublayer=79", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::quarter-section", "title": "Quarter Section", "description": "The City Engineering Quarter Section Map Index contains information regarding City Engineering quarter section numbers and Public Land Survey System (PLSS) information for each quarter section in the City and County of Denver, as well as a few of the surrounding section quarters. For each quarter section of the PLSS in the City and County of Denver, the City Engineering (later the City Surveyor's office) developed and maintained a linen sheet depicting subdivision, lot, ordinance, and easement data in that quarter section. Using Broadway and Colfax Avenue as the dividing lines, the CCD is broken into four quadrants, and the quarter sections for each quadrant are numbered beginning with 1.
NOTE: Maintenance of these quarter section sheets was discontinued after 1996 due to the development of the CCD GIS.
This dataset is an index of Public Land Survey System (PLSS) lines within the City and County of Denver. It is similar to the other Township-Range-Section layers available on the CCD GIS except:
1) this dataset contains quarter-section and sixteenth-section lines, and
2) the extent of this dataset is limited to GPS-derived and calculated land corner positions, and does not extend as far as the other TRS layers.
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org).
Since 2022, CASR added requirements for the buildings to reach a certain level of energy efficiency in their building by 2030. The most recent dataset shows the annual benchmarking data for the 3,000 buildings that have to comply, but it also now includes what their energy use intensity target is for 2030 (with interim check-ins in 2025 and 2027). The basic performance requirements are covered on this page: Performance Requirements - City and County of Denver (denvergov.org)
", "keyword": [ "ODC", "2024" ], "issued": "2026-08-13T18:05:33.000Z", "modified": "2026-08-13T18:07:36.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::energize-denver-2024-master-dataset" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=28844a7e682b49e1af0e50aa78f5dc0c&sublayer=246", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::small-cell-nodes", "title": "Small Cell Nodes", "description": "The small cell nodes are comprehensive for each carrier’s entire small cell program in CCD. The data is used by CCD for two maps, an internal map and an external, public facing map. The data is updated as we receive new applications with the and data from the carriers. The data is used to facilitate a quicker CCD review/approval process, provide public information to our citizens and media, and to assist applicants to develop their proposed locations in accordance with the Small Cell Design Guidelines.
This layer identifies locations of transit signals in the City and County of Denver. The data includes details about the signals that are used to supplement the planning efforts of the Transit Team.
This layer identifies locations of transit only lanes in the City and County of Denver. The data includes details about the lanes that are used to supplement the planning efforts of the Transit Team.
This is a sidewalk layer initially collected in 2022 by RAS (Roadway Asset Services). This data is split by parcel areas to represent separate sidewalk for each property. This linear frontage will be used to assess taxes. This data also includes general condition information. This layer will be used to manage sidewalks as an asset and represents an inventory of sidewalks in Denver. The future intent is to keep it updated with sidewalk improvements, additions and repairs.
DOTI routinely monitors and collects parking restrictions and occupancy data that is used for planning efforts. The data help DOTI make informed decisions about where to implement changes to accommodate the citizens of Denver as best as possible.
Vision Zero is an international movement to eliminate traffic deaths. Streets on the High Injury Network (HIN) have disproportionately high rates of traffic deaths and serious injuries. DOTI prioritizes these streets for targeted safety improvements. In 2023, DOTI revised the methodology for placing streets on the HIN. Using Esri’s High Injury Network Locator in the Traffic Crash Analysis Toolbox to analyze crash data from 2016-2021, the Vision Zero team broke Denver’s most dangerous streets into two tiers. Together, Tier 1 and Tier 2 streets account for 56% of all crashes. This update keeps all streets from the original HIN, adds 21 new roadway miles, and provides a two tiered ranking to prioritize investments in safety infrastructure.
A point representation of parking meters in the City and County of Denver. This dataset was created from Global Positioning System (GPS) source data.
Locations of the Office of Economic Development Workforce Centers and other City and County of Denver workforce resource offices.
Residential Care Facilities large and small, Homeless Shelters, Community Corrections and Transitional Housing within the City and County of Denver.
Denver Public Libraries within the City and County of Denver. The data includes patronage and circulation for the previous calendar year.
Head Start program Delegate Center locations within the City and County of Denver.
A polygon representation to assist in the stratification of data for purposes of developing automated valuation market models.
This dataset is used for 2025 re-valuation of Assessment Attached Housing - condominium real properties, market models.
A polygon representation to assist in the stratification of data for purposes of developing automated valuation market models.
The surveyor boundaries generally refer to NE, NW, SE, and SW quadrants of the City with special areas as assigned to the surveyor with the most knowldege of that area, such as Stapleton, Gates, Lowry, and Belleview Station. Areas were last updated on 2015-01-09
.
A polygon representation to assist in the stratification of data for purposes of developing automated valuation market models.
This dataset represents existing land use by parcel. The dataset was compiled from Assessor parcel records by generalizing their land use classifications into categories specific to planning. This layer is typically updated every 2 years in coordination with DRAPP imagery. However, periodic updated will occur on an as need basis for select areas of priority.
A high-quality multimodal transportation system is made up of several networks, each of which serves a particular transportation mode that moves people and goods from place to place. A high-quality multimodal transportation system is made up of pedestrian, bike, and transit networks, each of which serves a particular transportation mode that moves people and goods from place to place. Blueprint Denver identifies Pedestrian Enhanced areas. These are areas where there is a focus on creating vibrant, walkable places with wider, enhanced sidewalks. Bicycle priority streets will prioritize comfort and convenience for people biking. Transit priority streets allow transit to be rapid and reliable with special attention to accessible, safe and enhanced transit stops and stations. For more details see the Denver Blueprint plan on denvergov.org
The adopted version of the Denver Blueprint Plan showing future street types.
An adopted version of the Blueprint Denver Plan showing future places, neighborhood context, and growth areas.
This dataset is a point representation of the location of indoor and outdoor aquatic facilities located in parks and other areas maintained by the Department of Parks and Recreation in the City and County of Denver.
This dataset is a polygon representation of skate parks located in parks and other areas maintained by the Department of Parks and Recreation in the City and County of Denver.
This dataset is a point representation of permanent restroom facilities in parks and other areas maintained by the Department of Parks and Recreation in the City and County of Denver.
This dataset is a point representation of permitted picnic areas in parks and other areas maintained by the Department of Parks and Recreation in the City and County of Denver.
This dataset is polygon representation of designated parkways managed by the Department of Parks and Recreation in the City and County of Denver. Data is based on the right of way boundary and then buffered to graphically represent the area affected by the setback regulations.
This dataset is a polygon representation of the Landscape Typologies within parks owned and maintained by DPR with the City and County of Denver (CCD). The Landscape Typology mapping and assessment effort was not comprehensive and did not include all areas maintained by DPR but focused on parks with natural vegetation communities.
The general methodology for vegetation community mapping and scoring was as follows:
DPR maintenance boundaries were used for park extents.
Impervious surfaces, planting beds, and ball fields were clipped from the boundary.
Vegetation communities were delineated using high-resolution aerial imagery. Polygons were mapped at a scale of 1/4th acre for upland areas and 1/6th acre for riparian areas.
Vegetation community types and extents were field verified and adjusted as needed.
Field data collection included recording the percent cover by each strata (trees, shrubs, forbs, and grasses), the two dominant vegetation species for each strata and their total cover, and the two dominant noxious weeds and their total cover. Additionally qualitative and semi-quantitative parameters were also scored in the field for each park that was assessed.
Function (FUNC_PERCENT) was calculated by summing scores from each assessed parameter and dividing by the total possible score to get a normalized functional score. FUNCTION is based on the following thresholds:
Excellent: 86-100
Good: 70-85
Fair: 50-69
Poor: <50
Restoration Score (RESTORATION SCORE PERCENT) was calculated by summing scores from each assessed ecological parameter (DIVERSITY SCORE, WILFLIFE SCORE, POLLINATOR HABITAT SCORE, NOXIOUS POPULATION SCORE, and INVASIVE WEED SCORE) and dividing by the total possible score to get a normalized restoration functional score.
CUSP POLYGONS are polygons within +/- 2 points of a higher or lower function (FUNC_PERCENT). CUSP PRIORITY was assigned based on the type of cusp (risk of falling to lower function or ability to increase to higher function):
Excellent à Good: Low Priority (1)
Good à Excellent: Low Priority (1)
Good à Fair: High Priority (5)
Fair à Good: Moderate Priority (3)
Fair à Poor: High Priority (5)
Poor à Fair: High Priority (5)
This dataset is a point representation of municipal golf courses maintained by the Department of Parks and Recreation in the City and County of Denver.
This dataset is a point representation of the location of fountains, water features, art, interactive features in parks or other areas maintained by the Department of Parks and Recreation within the City and County of Denver.
This data is polygon representation of dog off leash areas within parks or other areas maintained by the Department of Parks and Recreation.
This dataset is a polygon representation of the location and orientation of athletic fields in parks or other areas maintained by the Department of Parks and Recreation within the City and County of Denver.
This dataset is an index of Public Land Survey System (PLSS) Township, Range, and Section lines containing the City and County of Denver.
This dataset is an index of Public Land Survey System (PLSS) Townships, Ranges, and Sections containing the City and County of Denver.
A polygonal representation of the Assessment Map Index for the City and County of Denver.
Contains polygon features that represent the Parcel or, in some instances, the building footprint of designated historic landmark structures. Historic Structures are established by city ordinance as approved by city council. Ordinance information is contained in the feature attributes. This layer contains polygons that represent the area designated as historic property defined by the legal description in the ordinance. All certian property contained within the defined area, together with all improvements, are designated as a Structure for Preservation.
Contains points that identify Landmark structure locations. Structures are established by city ordinance as approved by city council. Ordinance information is contained in the feature attributes.
A citywide comprehensive field survey of buildings in order to identify structures with historic significance. Each surveyed site provides key information about the building and eligibilyt for historic status. This data is created by the Discover Denver project at Historic Denver who conduct feildwork to complete comprehensive surveys of each site. Denver Community Planning and Development's (CPD) Landmark Preservation team partner with Discover Denver to help curate this data and make it avaiable via a web application and Denver's Open Data Catalog.
This dataset is a point feature representing range points within the City and County of Denver. Range points are termini for range lines, which serve as offsets to right-of-way lines and block lines. Range points are typically located below surface streets.
This dataset contains National Geodetic Survey (NGS) High-Accuracy Reference Network (HARN) points commonly used by the Public Works survey group.
This dataset contains location and monument data for Public Land Survey System land corners lying within the City and County of Denver, and in selected areas of interest. These corners define the endpoints of PLSS section lines, quarter section lines, and other \"aliquot parts\" of the PLSS.
This layer respresents the locations of Denver Human Services' in-person and office locations for assistance. Services provided vary by location.
Visual representation of the approximate boundaries of field surveys.
This dataset contains vertical benchmark data for the City and County of Denver. Monumentation for this dataset includes U.S. Coast and Geodetic Survey (USCGS), National Geodetic Survey (NGS), and City and County of Denver (CCD) benchmarks. Elevations for bench marks are typically determined by standard differential leveling activity. NGS High-Accuracy Reference Network (HARN) points are portrayed in the ENG_SRVNGSHARN_P dataset.
This map data layer represents the building inspection boundaries for electrical inspections for the City and County of Denver, Colorado. The building inspection boundaries data layer is changed only when a inspection boundary and/or inspector assigned to a particular district has changed.
Geographic boundaries created to assign staff for the review of development plans.
ROWS conducts construction inspections to ensure compliance with City and County of Denver construction requirements. The ROWS inspectors operate within defined inspection district boundaries and this data allows the inspection team to visualize project locations and better manage individual workloads.
Mapping of the current PWDES projects (from CityView database) to overlay with other project datasets such as Capital Improvement Projects (CIP) and Transportation Collaboration Group (TCG).
Enterprise Zone area as of January 1, 2016 in the City and County of Denver. The State of Colorado Office of Economic Development required that all jurisdictions with Enterprise Zones use updated criteria to redesignate their Enterprise Zone boundaries, to be effective January 1, 2016.
The child care facility layer contains an address point where an active child care license issued in the City and County of Denver. The layer is updated daily by extracting records from the Accela database and using coordinates stored therein to place them on a map.
Mapping locations of the Public Art collection for the City and County of Denver.
Department of Transportation and Infrastructure (DOTI) - Development Engineering Services Wastewater Review Engineer Areas. This is the Engineer that is the lead for the Wastewater review for this particular geographic area. Lead Engineer is the Senior Engineer for the area and Staff Engineer is the Engineer or Staff Engineer that is Wastewater reviewer.
Data to be used for a web service allowing the Customer-Relationship Management (CRM) 311 operator to assign a service request based upon a specified Denver Address Database (DAD) address coordinate point. The coordinate point will then overlay the Investigation areas (polygon) layer to determine the engineer responsible for the investigation area. Engineering assignment document is generated for a response to the Traffic Signal, Sign or Marking issue.
This superceds four previous datasets: Traffic Sign and Marking Investigation Areas, Traffic Sign and Marking Plan Review Areas, Traffic Signal Investigation Areas and the Method for Handling Traffic (MHT) Engineer.
Public Works - Development Services Sewer Use and Drainage Permit (SUDP) Reviewer Areas. This dataset provides SUDP reviewer area boundary delineations and associated attributes. The associated tabular data includes the lead engineer and staff reviewer with contact information for the assigned reviewer area.
The Street Sweeping Schedule Areas and boundaries for the Public Works Street Maintenance Division. The tabular data includes the months of the year when street sweeping will occur, week of the defined month, days within the defined week, whether or not the schedule is posted along the street and the Street Sweep Schedule unique identifier.
The solid waste collection arrows are used to show route directions.
The City and County of Denver's Public Works Right of Way Enforcement (PWROWE) Patrol Beats features. This dataset contains polygon features representing areas of patrol for PWROWE.
This map data layer represents the engineering plan review boundaries for the City and County of Denver's Public Works Right-of-Way Services. The boundaries data layer is changed only when a review area and/or engineer assigned to a particular area has changed.
This map data layer represents the building inspection boundaries for plumbing inpsections for the City and County of Denver, Colorado. The building inspection boundaries data layer is changed only when a inspection boundary and/or inspector assigned to a particular district has changed.
An estimate of the demand for walking in different areas of the City and County of Denver based on two data variables known to contribute to high levels of walking: population density and employment density. Population density (population per square mile) is sourced from the 2020 Census. Employment density (employment per square mile) is sourced from the Longitudinal Employer-Household Dynamics (LEHD) Origin-Destination Employment Statistics (LODES) Version 7. Population and employment density are added together to generate a combined density value. This combined value is grouped into 10 value groupings using the Quantile method in ArcGIS. The 10 value groupings are then assigned a Pedestrian Demand Index Score (1 – 10), which is displayed by Traffic Analysis Zone. The higher the score, the higher the estimated demand for walking. Note: Due to geographic problems inherent in the 2010 Census block group data, used as the base geographic unit to combine employment and population data, results should be considered estimates.
This layer shows the Zoning Inspection Districts used to organize and assign zoning inspectors throughout the City and County of Denver. These districts support consistent coverage and efficient scheduling of zoning inspections related to business licenses and Certificates of Occupancy (COs).
Zoning inspectors verify that properties comply with approved zoning plans and permits before businesses open or occupy a space. Inspections confirm that site conditions, building use, parking, landscaping, lighting, signage, fencing, outdoor storage, and other exterior and interior elements match what was approved through zoning.
Zoning inspections support business licensing, CO and Temporary Certificate of Occupancy (TCO) approvals, and ongoing zoning compliance. This layer supports inspector assignment, coordination, and workload planning for zoning-related inspections citywide.
Metro Districts are formed by:
1. Approval by City Council of the district's service plan, which is the document that governs the district's actions;
2. A petition signed by 30% or 200 of the electors of the District, whichever is less is approved by the District court and an election is ordered; and
3. Approval of the District by the electors within the District.
Subareas within the District may be formed.
C. Governance.
A metropolitan district is governed by a five member board of directors. A director must be an \"elector\" of such district, defined as a person who, at the time, is registered to vote in the State and: (I) who has been a resident of the district for not less than thirty days; or (II) who, or whose spouse, owns taxable real or personal property situated within the boundaries of the district, whether said person resides within the district or not. There is no City appointment. The board is responsible for the administration of the district, annual budgeting and levying of taxes,
rates, and charges sufficient to pay operating costs and debt service of the district.
D. Powers.
1. Common Powers. All special districts have the following powers:
a. To have a perpetual existence;
b. To have and use a corporate seal;
c. To sue and be sued;
d. To enter into contracts and agreements affecting the affairs of the special district;
e. To borrow money and incur indebtedness and to issue notes or issue bonds evidencing such
indebtedness;
f. To acquire, sell and lease property;
g. To manage, control and supervise all the business and affairs of the special district, including all
construction, operation and maintenance of special district improvements;
h. To fix, charge and collect fees, rates, tolls, penalties or charges for services, programs or facilities
furnished by the special district.
i. To furnish services and facilities outside the boundaries of the special district.
j. To adopt, amend, and enforce bylaws and rules and regulations for carrying on the business, objects
and affairs of the special district.
2. Additional Powers Depending Upon Type of District:
a. Metropolitan Districts: In addition to the common powers, metropolitan districts have the following powers:
to enter into contracts with public utilities and municipalities for street lighting service;
to erect and maintain traffic and safety controls and devices, providing fire protection, parks or recreation, water or water and sanitation service;
This map data layer represents the building inspection boundaries for mechanical inspections for the City and County of Denver, Colorado. The building inspection boundaries data layer is changed only when a inspection boundary and/or inspector assigned to a particular district has changed.
The percentage of the 2019 population that is low-to-moderate income in each Census 2010 Block Group, as calculated by the US Department of Housing and Urban Development (HUD) is provided in this data layer. For more information on HUD's methodology, visit: https://www.hudexchange.info/manage-a-program/acs-low-mod-summary-data/
Note: Tract level data is no longer to be used for determining eligibility for use of CDBG funds.
GIDs are allowed to construct, install or acquire any public improvement except solid waste disposal improvements and services. They may assess ad valorem taxes and charge rates, tolls and charges for services or facilities. The may issue general obligation and revenue bonds. Debt in excess of $5,000 must be approved by the electors within the district. They may operate district improvements.They are initiated by a petition filed with the City Clerk, signed by the lesser of 30% or 200 electors owning taxable real or personal property within the district. Subareas within the district may be formed. The City Council is the board of directors of the district. By ordinance, an advisory board may be created to oversee the GID.
Excise and License - Business License Inspector district boundaries of the City and County of Denver.
Geographic boundaries created to assign staff to Public Works Engineering, Regulatory, and Analytics Wastewater Reviewer Areas.
Geographic boundaries created to assign staff to Public Works Engineering, Regulatory, and Analytics Materials Reviewer Areas.
This layer uses City Council District boundraries to create areas of responsibility for the OCBE City Building Team. There are four (4) total areas:
Area 1: City Council Districts 1 and 9
Area 2: City Council Districts 5, 8, and 11
Area 3: City Council Districts 2, 3, and 7
Area 4: City Council Districts 4, 6, 10
This map data layer represents the building inspection boundaries for construction inspections for the City and County of Denver, Colorado. The building inspection boundaries data layer is changed only when a inspection boundary and/or inspector assigned to a particular district has changed.
An organizational petition shall be signed by persons who own real or personal property in the service areaof the district having an assessed value of not less than 50% of the assessed value of all real and personal property in the district, and who own at least 50% of the acreage in the district as filed in the City Clerk and City Council offices.City Council approves the petition by ordinance, organizing the BID and defining the boundaries
This dataset is point representation of trees managed by the Department of Parks and Recreation in the City and County of Denver. Data is based GPS locations..
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org).
Since 2022, CASR added requirements for the buildings to reach a certain level of energy efficiency in their building by 2030. The most recent dataset shows the annual benchmarking data for the 3,000 buildings that have to comply, but it also now includes what their energy use intensity target is for 2030 (with interim check-ins in 2025 and 2027). The basic performance requirements are covered on this page: Performance Requirements - City and County of Denver (denvergov.org)
", "keyword": [ "ODC", "2024" ], "issued": "2025-10-31T20:27:07.000Z", "modified": "2026-07-27T20:09:52.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::energize-denver-2023-final-master-data-set" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=5e7ce4f28b4b408aac59de8d7950adbf&sublayer=450", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::open-data-bike-facilities", "title": "Open Data Bike Facilities", "description": "Public-facing view of current and proposed bicycle facilities in the City and County of Denver. This dataset was developed as part of the Denver Moves: Bikes plan update in 2025. It includes information about existing bikeways, upgrades recommended for existing bikeways, and future bikeways recommended through the planning process. More details about the plan can be found here.
", "keyword": [ "ODC" ], "issued": "2026-07-10T03:47:33.000Z", "modified": "2026-09-18T15:45:22.008Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "-105.1100,39.6146,-104.7338,39.8428", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::open-data-bike-facilities" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/Denver_Bicycle_Facilities_ODC/FeatureServer/450" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/5e7ce4f28b4b408aac59de8d7950adbf/csv?layers=450" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/5e7ce4f28b4b408aac59de8d7950adbf/shapefile?layers=450" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/5e7ce4f28b4b408aac59de8d7950adbf/geojson?layers=450" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/5e7ce4f28b4b408aac59de8d7950adbf/kml?layers=450" } ], "theme": [ "geospatial" ] }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=001f24fa963244108a3dea9920c1c86c&sublayer=397", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::fema-floodplain-cross-sections", "title": "FEMA Floodplain Cross Sections", "description": "The National Flood Hazard Layer (NFHL) data incorporates all Digital Flood Insurance Rate Map(DFIRM) databases published by FEMA, and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. The DFIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper Flood Insurance Rate Maps(FIRMs). The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The NFHL data are derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The specifications for the horizontal control of DFIRM data are consistent with those required for mapping at a scale of 1:12,000. The NFHL data contain layers in the Standard DFIRM datasets except for S_Label_Pt and S_Label_Ld. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all DFIRMs and corresponding LOMRs available on the publication date of the data set.
The National Flood Hazard Layer (NFHL) data incorporates all Digital Flood Insurance Rate Map(DFIRM) databases published by FEMA, and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. The DFIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper Flood Insurance Rate Maps(FIRMs). The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The NFHL data are derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The specifications for the horizontal control of DFIRM data are consistent with those required for mapping at a scale of 1:12,000. The NFHL data contain layers in the Standard DFIRM datasets except for S_Label_Pt and S_Label_Ld. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all DFIRMs and corresponding LOMRs available on the publication date of the data set.
Historic Districts as established by city ordinance. Ordinance information is contained in the feature attributes.
The National Flood Hazard Layer (NFHL) data incorporates all Digital Flood Insurance Rate Map(DFIRM) databases published by Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. The DFIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper Flood Insurance Rate Maps(FIRMs). The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The NFHL data are derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The specifications for the horizontal control of DFIRM data are consistent with those required for mapping at a scale of 1:12,000. The NFHL data contain layers in the Standard DFIRM datasets except for S_Label_Pt and S_Label_Ld. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all DFIRMs and corresponding LOMRs available on the publication date of the data set.
The National Flood Hazard Layer (NFHL) data incorporates all Digital Flood Insurance Rate Map(DFIRM) databases published by Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. The DFIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper Flood Insurance Rate Maps(FIRMs). The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The NFHL data are derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The specifications for the horizontal control of DFIRM data are consistent with those required for mapping at a scale of 1:12,000. The NFHL data contain layers in the Standard DFIRM datasets except for S_Label_Pt and S_Label_Ld. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all DFIRMs and corresponding LOMRs available on the publication date of the data set.
The National Flood Hazard Layer (NFHL) data incorporates all Digital Flood Insurance Rate Map(DFIRM) databases published by Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. The DFIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper Flood Insurance Rate Maps(FIRMs). The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The NFHL data are derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The specifications for the horizontal control of DFIRM data are consistent with those required for mapping at a scale of 1:12,000. The NFHL data contain layers in the Standard DFIRM datasets except for S_Label_Pt and S_Label_Ld. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all DFIRMs and corresponding LOMRs available on the publication date of the data set.
The National Flood Hazard Layer (NFHL) data incorporates all Digital Flood Insurance Rate Map(DFIRM) databases published by Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. The DFIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper Flood Insurance Rate Maps(FIRMs). The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The NFHL data are derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The specifications for the horizontal control of DFIRM data are consistent with those required for mapping at a scale of 1:12,000. The NFHL data contain layers in the Standard DFIRM datasets except for S_Label_Pt and S_Label_Ld. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all DFIRMs and corresponding LOMRs available on the publication date of the data set.
The National Flood Hazard Layer (NFHL) data incorporates all Digital Flood Insurance Rate Map(DFIRM) databases published by Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. The DFIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper Flood Insurance Rate Maps(FIRMs). The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The NFHL data are derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The specifications for the horizontal control of DFIRM data are consistent with those required for mapping at a scale of 1:12,000. The NFHL data contain layers in the Standard DFIRM datasets except for S_Label_Pt and S_Label_Ld. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all DFIRMs and corresponding LOMRs available on the publication date of the data set.
This data set contains the name, address, phone number, and website of each HIV health care provider that received Part A Ryan White CARE grant funds.
Developed from CDPHE dataset found at https://data-cdphe.opendata.arcgis.com/. Data has been clipped and modified to only include points within The City and County of Denver.
From the CDPHE Dataset:
Point geometry feature class representing known regulated health facilities in Colorado, developed using address information obtained directly from the Health Facilities and Emergency Medical Services Division of the Colorado Department of Public Health and Environment. Coordinate locations (latitude/longitude) are derived using the known street addresses of health facilities. This file is developed and regularly updated for use in emergency response activities and exercises within the Colorado Department of Public Health and Environment. Updated October 2025,
Areas of limited food access represent living units in Denver that are more than a 10-minute walk to a full-service grocery store. The 10-minute walk walksheds were developed alongside the Denver Sidewalk Network at a walking speed of half a mile in 10-minutes.
Full-service grocery store is defined by The Department of Public Health and the Environment Food System Team using Food Retail Location This layer estimates neighborhood access based on living units within the 10-minute walkshed rather than using the proportion of the total neighborhood population within the walkshed, which better accounts for where people actually live within a neighborhood. It was joined with the most recent ACS Common Data Indicators provided by CPD (ACS 2018-2022).
This layer is updated annually and the Data Steward is Roxanne Eidom in The Department of Public Health and the Environment.
Dataset maintained by the Denver Department of Public Health and Environment (DDPHE), Food in Communities (FIC) team. Data steward: Paola Babb
This feature layer is maintained by Denver Department of Public Health and Environment and is a combination of data available through Hunger Free Colorado and ground truthing by the DDPHE CBH Food Systems Team. The data stewards are Paola Babb and Jessika Brenin. It displays food retail locations in Denver.
The dataset displays the locations of food pantries classified as traditional of non-traditional, food banks, and food distributors.
Data set comes from Hunger Free Colorado anon-profit that supports connecting people to food resources. They review food access points across the state on a yearly basis. The data set was filtered by Denver County and specifically looking at what FIC classified as a Food Bank, Food Pantry, and Mobile Pantry.
Retention policy: Retained as long as data remains relevant for food systems planning and analysis.
Update cadence: Updated annually
Data quality: Good
Terms of Use: This dataset is intended for planning, analysis, and informational purposes. DDPHE is not liable for decisions made based on this dataset.
Dataset maintained by the Denver Department of Public Health and Environment (DDPHE), Food in Communities (FIC) team. Data steward: Jessika Brenin
Processing steps include compiling data from MHF and other sources, standardizing location and attribute fields, removing duplicates, and validating site information where possible.
This dataset includes locations of farmers markets and farm stands across Denver to support analysis of local food access and distribution channels.
Data sources include:
Farmers market (including mobile market) data consolidated by DDPHE staff from multiple sources into a single master dataset.
Retention policy: Retained as long as data remains relevant for food systems planning and analysis.
Update cadence: Updated annually
Data quality: Good
This dataset categorizes food access points as follows:
Farmers Markets: Public market where local farmers, and food producers sell fresh produce, meats, dairy, baked goods, and other locally grown products directly to community.
Mobile Farmer's Market: Traveling market (often a truck, van, or bus) that is equipped to sell fresh food such as fruits, vegetables, and pantry staples.
Terms of Use: This dataset is intended for planning, analysis, and informational purposes. DDPHE is not liable for decisions made based on this dataset.
Dataset maintained by DDPHE/SSBO, on behalf of Food in Communities. Data steward: Jessika Brenin (foodincommunities@gmail.com).
This dataset shows locations of food growing spaces across Denver to provide users with knowledge about and support analysis of the local food producing landscape.
Data was compiled from partners (Denver Urban Gardens, Grow Local Colorado, SustainED, Healthy Food for Denver's Kids, Denver Public Schools, Mile High Farmers, Uproot CO, Commun, Mo'Betta Green, Lost Greens Farm). Location and attribute fields were standardized. Duplications were removed. Site information was validated as much as possible.
Food Growing Spaces are defined with the following categories:
Gardens (Agricultural land producing food for use by a single entity.)
Public Community Garden: spaces producing food that is split into plots, with individual plot \"\"owners\"\" independently tending to and benefiting from their plot(s). Anyone can become a plot owner.
Organizational Garden: spaces producing food for direct use only by one organization and its clients.
School Garden (a specific type of Organizational Garden): spaces at a school producing food for direct use within that school's cafeteria, for distribution to families at that school, or for educational purposes of students at that school. May be indoor or outdoor food growing spaces.
Farm: spaces producing food for sale or donation to many individuals, households, or organizations through on-site or off-site distribution channels. May be indoor or outdoor food growing spaces.
Food Forest: Food-producing land in the form of a forest ecosystem; often with a multi-layered, perennial, permaculture design; often for use by and accessible to the public.
Retention policy: Retained as long as data remains relevant for food systems planning and analysis.
Date of Last Update: April 2026
Update cadence: Updated annually
Data quality: Fair
Terms of Use: This dataset is intended for planning, analysis, and informational purposes. DDPHE is not liable for decisions made based on this dataset.
Dataset maintained by the Denver Department of Public Health and Environment (DDPHE), Community & Behavioral Health (CBH) Food Systems Team. Data steward: Paola Babb.
This dataset represents food retail locations across Denver and includes information on participation in federal and state nutrition assistance programs such as the Supplemental Nutrition Assistance Program (SNAP), Double Up Food Bucks (DUFB) and the Women Infant and Children Supplement Nutrition program (WIC). It is used to assess healthy food retail access and inform planning, policy, and investment strategies.
Data sources include:
DDPHE Public Health Investigations Team: Active food retail license data.
State SNAP and WIC authorized retailer lists.
Nourish Colorado: Double Up Food Bucks (DUFB) participating retailers.
Processing steps include extracting active licensed food retail locations, standardizing and cleaning datasets, and combining the data with SNAP/WIC/DUFB retailer participation data, classifying retailers by type, and validating records where possible.
Retail locations are classified into four categories:
Category 4: Large Supermarkets and Other Grocery (>15,000 sq ft) - Includes warehouse clubs and supercenters (e.g., King Soopers, Safeway, Walmart, Costco, Sprouts, Whole Foods).
Category 3: Small Supermarkets and Other Grocery (<15,000 sq ft) - Includes smaller grocery stores and large specialty stores (e.g., Trader Joe’s, Natural Grocers, Lowe’s Mercado, Leevers Locavore).
Category 2: Specialty Food Stores - Includes meat markets, produce markets, seafood markets, and cultural/ethnic markets (e.g., carnicerías, neighborhood markets, butchers).
Category 1: Convenience Stores - Includes corner stores, gas station markets, and pharmacies that sell food (e.g., CVS, Walgreens, 7-Eleven).
Terms of Use: This dataset is intended for planning, analysis, and informational purposes. DDPHE is not liable for decisions made based on this dataset.
Developed from CDPHE dataset found at https://data-cdphe.opendata.arcgis.com/. Data has been clipped and modified to only include points within The City and County of Denver.
From the CDPHE Dataset:
Point geometry feature class representing designated trauma centers and assigned trauma levels in Colorado, developed directly from address information obtained directly from the Health Facilities and Emergency Medical Services Division (CDPHE).
Point geometry feature class representing designated trauma centers in Colorado, developed directly from address information obtained directly from the Health Facilities and Emergency Medical Services Division of the Colorado Department of Public Health and Environment. Coordinate locations (latitude/longitude) were derived from the known street addresses of trauma centers using a combination of MapMarker geocoding software and Google Earth imagery locations. This file was developed for use in activities and exercises within the Colorado Department of Public Health and Environment. This dataset was last updated in April 2019.
Developed from CDPHE dataset found at https://data-cdphe.opendata.arcgis.com/. Data has been clipped and modified to only include points within The City and County of Denver and Nursing Homes.
From the CDPHE Dataset:
Point geometry feature class representing known regulated health facilities in Colorado, developed using address information obtained directly from the Health Facilities and Emergency Medical Services Division of the Colorado Department of Public Health and Environment. Coordinate locations (latitude/longitude) are derived using the known street addresses of health facilities. This file is developed and regularly updated for use in emergency response activities and exercises within the Colorado Department of Public Health and Environment. Updated October 2025.
Developed from CDPHE dataset found at https://data-cdphe.opendata.arcgis.com/. Data has been clipped and modified to only include points within The City and County of Denver and Hospitals.
From the CDPHE Dataset:
Point geometry feature class representing known regulated health facilities in Colorado, developed using address information obtained directly from the Health Facilities and Emergency Medical Services Division of the Colorado Department of Public Health and Environment. Coordinate locations (latitude/longitude) are derived using the known street addresses of health facilities. This file is developed and regularly updated for use in emergency response activities and exercises within the Colorado Department of Public Health and Environment. October 2025.
Developed from CDPHE dataset found at https://data-cdphe.opendata.arcgis.com/. Data has been clipped and modified to only include points within The City and County of Denver and Federally Qualified Health Centers.
From the CDPHE Dataset:
Point geometry feature class representing known regulated health facilities in Colorado, developed using address information obtained directly from the Health Facilities and Emergency Medical Services Division of the Colorado Department of Public Health and Environment. Coordinate locations (latitude/longitude) are derived using the known street addresses of health facilities. This file is developed and regularly updated for use in emergency response activities and exercises within the Colorado Department of Public Health and Environment. Updated October 2025.
Developed from CDPHE dataset found at https://data-cdphe.opendata.arcgis.com/. Data has been clipped and modified to only include points within The City and County of Denver.
From the CDPHE Dataset:
Point geometry feature class representing known Emergency Medical Services (EMS) and Ambulance agencies in Colorado, developed directly from address information obtained directly from the Health Facilities and Emergency Medical Services Division of the Colorado Department of Public Health and Environment. Coordinate locations (latitude/longitude) were derived from the known street addresses of agencies using a combination of MapMarker geocoding software and Google Earth imagery locations. This file was developed for use in activities and exercises within the Colorado Department of Public Health and Environment. Updated April 2019.
This dataset represents key food insecurity indicators at the City Council District level using data from the Denver Food Insecurity Survey which was conducted by DDPHE in the fall of 2025.
The dataset includes key data points related to adult and child food insecurity, financial tradeoffs, and use of nutrition assistance programs. When a district is selected, key data points are displayed to provide a snapshot of food insecurity conditions within that district.
Processing steps included cleaning and aggregating the survey data, assigning responses to council districts based on geographic identifiers.
Update cadence: Updated as new survey data becomes available.
Data quality: Good.
Dataset maintained by the Denver Department of Public Health and Environment (DDPHE), Community & Behavioral Health (CBH) Food Systems Team. Data steward: Paola Babb and Carolina Ramirez.
The 2025 Food Insecurity survey was administered during a period of economic and policy disruption, including federal SNAP benefit delays during a government shutdown. These conditions may have influenced responses and highlight the sensitivity of food security. Findings indicate that food insecurity in Denver remains widespread, with 37% of adults reporting cutting or skipping meals due to cost, more than double the rate reported in 2024.
Full set of questions corresponding to data in this dataset:
Food Insecurity Measures
T2. Relative to other concerns you have for your household, how important of an issue is hunger?
T3. In the last twelve months, did you or other adults in your household ever cut the size of your meals or skip meals because there wasn't enough money for food?
T4. How often did you or other adults in your household cut the size of your meals or skip meals? (Asked to respondents who either them or other adults in household have cut or skipped meals)
Child Food Insecurity Measures
T6. In the past twelve months, did you cut the size of your child/children’s meals or skip meals because there wasn't enough money for food? (Among respondents who have a child in the household)
T7. How often did this happen? (Among respondents who have a child and had to cut the size or skip meals)
T8. In the past twelve months, did any of the children ever not eat for a whole day because there wasn't enough money for food? (Among respondents who have a child and had to cut the size or skip meals)
Food Access and Shopping Experiences
T12. In the past 12 months, have you needed to cut back or adjust spending on any of the following to afford food? (Select all that apply)
T13. How often do you delay paying bills to ensure you have enough money for food?
Food and Nutrition Assistance
T17. If you received WIC or SNAP, about how much of your household’s food needs did these benefits cover? (Asked to respondents who children or parents received WIC benefits, or someone in the household received SNAP/EBT benefits.
Terms of Use: This dataset is intended for planning, analysis, and informational purposes. Results should be interpreted within the context of survey timing and methodology. DDPHE is not liable for decisions made based on this dataset.
The Street Sweeping District boundaries for the Public Works Street Maintenance Division.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for service request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for service request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested information/service |
| 18 | Division | Animal Care and Control | Text | 20 | Division within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::311-service-requests-2024" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=5bdb9b3033d74782a4c410e548887ede", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::311-service-requests-2025", "title": "311 Service Requests 2025", "description": "{{description}}", "keyword": [ "ODC" ], "issued": "2026-05-06T17:10:52.000Z", "modified": "2026-05-06T17:12:57.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::311-service-requests-2025" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=47752f42297c4ed1b17887f2d4cd1ad9&sublayer=108", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::police-precincts", "title": "Police Precincts", "description": "The Denver Police Precincts boundaries for the Denver Police Department.
The Denver Police Districts boundaries for the Denver Police Department.
A point layer of Fire Stations within the City and County of Denver.
This dataset should be used as a reference to locate the various Denver Fire Districts found within the boundaries of the City and County of Denver.
This metadata describes the stereocompiled paved sidewalks and paved trails polygons feature of DRCOG Denver Region Urbanized Project Area. The feature was compiled from the Denver Regional Aerial Photography Project (DRAPP) 2020 Aerial Imagery Acquisition and Production. This 1\"=100' scale imagery is comprised of 4-band RGBIR color orthoimagery with a GSD (Ground Sample Distance) of 0.5'. Imagery was collected with the Leica ADS40 and ADS80 digital sensors and processed with Leica XPro software. Imagery is projected in State Plane Coordinate System, Colorado central zone using the Lambert Conformal Conic map projection parameters. Horizontal and vertical datums are NAD83(11) and NAVD88(GEOID12A) respectively.The layer has since been taken over for the Department of Transportation and Infrastructure to continue with updates.
The Statistical Neighborhood boundaries were developed in 1970 by the Community Renewal Program (CRP) which was administered by the current Denver Department of Community Planning and Development. Statistical Neighborhoods are typically combinations of census tracts. Geographic place names, such as Windsor and Mar Lee, were assigned to each area and reflect commonly used names of subdivisions and historical parts of the city.
The Area Plans feature class represents the boundaries of each neighborhood plan, assessment, or study that has been completed or is In Progress. The boundary is shown as described and/or depicted in each of documents. These documents are identified as adopted by City Council, the Planning Board, or not applicable. This feature class has been created by the Community Planning and Development's GIS section.
City and County of Denver Wastewater Management Storm Facility Data - Storm Drainage Collection System Boundaries developed for the 2014 Storm Drainage Master Plan. Storm Drainage Collection System Basins defined by the existing storm drainage collection system catchments for minor storm conveyance designs. This layer represents the smallest subset of basins.
City and County of Denver Wastewater Management Storm Facility Data - Storm Drainage Collection System Boundaries developed for the 2014 Storm Drainage Master Plan. Storm Drainage Collection System Basins defined by the existing storm drainage collection system catchments for minor storm conveyance designs. This layer represents the major basins.
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::2025-water-quality-data" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=5a5f101431554a14b713dee51bf02c34", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::2024-denver-ghg-inventory", "title": "2024 Denver GHG Inventory", "description": "These datasets are the greenhouse gas inventories for the City and County of Denver and are reflective of community-wide emissions.
", "keyword": [ "ODC", "2024" ], "issued": "2026-01-29T18:39:36.000Z", "modified": "2026-01-29T18:42:33.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::2024-denver-ghg-inventory" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=241f108996844aaeaed7a383f41c4dad", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::2023-denver-ghg-inventory", "title": "2023 Denver GHG Inventory", "description": "These datasets are the greenhouse gas inventories for the City and County of Denver and are reflective of community-wide emissions.
", "keyword": [ "ODC" ], "issued": "2025-07-30T16:36:38.000Z", "modified": "2026-01-29T18:42:22.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::2023-denver-ghg-inventory" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=0d178821889442bb8e614f8aa1d8b2fa&sublayer=206", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::tree-canopy-2006", "title": "Tree Canopy 2006", "description": "Tree canopy delineations, captured from QuickBird 2 foot pixel satellite imagery, using automated feature extraction from the near infra-red band.
The purpose of this layer is to provide an accurate representation of impervious surfaces in the City and County of Denver. This layer combines Stormwater Billing impervious surfaces with Planimetric impervious surfaces; allowing for a comprehensive, city-wide, impervious surface layer. This layer is a compilation of two independent sources of impervious surface data. The data is provided by both the City and County of Denver’s Wastewater Management Division-Customer Service (WMD-CS) and Kucera International Inc. The WMD-CS data represents areas digitized for all stormwater billing inspections after December 2002 and contains impervious surface delineations of each inspected property. These features are updated daily by WMD-CS field investigators and GIS personnel. The planimetric data, supplied by Kucera International Inc, defines the stereocompiled features of the DRCOG Denver Region Urbanized Project Area. The features were compiled from the Denver Regional Aerial Photography Project (DRAPP) 2016/2018/2020 Aerial Imagery Acquisition and Production. This 1\"=100' scale imagery is comprised of 4-band RGBIR color orthoimagery with a GSD (Ground Sample Distance) of 0.5'. Imagery was collected with the Leica ADS40 and ADS80 digital sensors and processed with Leica XPro software. Imagery is projected in State Plane Coordinate System, Colorado central zone using the Lambert Conformal Conic map projection parameters. Horizontal and vertical datums are NAD83(11) and NAVD88(GEOID12A) respectively. The planimetric features are generally updated every two years.
Land area of Denver Public Schools locations. Updated for school year 2025-2026
*Includes Public schools area outside the city boundary within 1000'
These data are the common data fields from the American Community Survey agreed upon by the Data Indicators GIS Subcommittee. The data source is Census Tract level data from the American Community Survey; 5 year average, years 2017-2021. The original census tract group boundaries have been adjusted to various Denver GIS data layers to increase the spatial accuracy of this data. Although every effort was made to ensure the accurate rectification of the data, due to geographic problems inherent in the original 2010 census block group data, errors may exist. The data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a complete census. Data should be considered estimates and a margin of error table is located on the city network that can be used in conjunction with this dataset.
Land area of private school locations. Updated for school year 2025-2026
Includes non-public schools outside the city boundary to 1000'
Non-Public Elementary and Secondary schools. Affiliation and Number of students attributed when known.
Updated for 2025-2026 School Year
Public School Locations. Includes Denver public schools (DPS) and other public schools such as charter schools administered by other school districts or independent entities. Private schools are maintained in a separate layer.
Includes Public schools outside the city boundary to 1000'
Updated for school year 2025-2026
This is the\r\ncomplete list of covered buildings from 5,000 up to 24,999 sq ft that are\r\nsubject to separate requirements under the Energize Denver Ordinance. The Climate Action, Sustainability, &\r\nResiliency team manages compliance with the Energize Denver regulatory\r\nprogram that requires buildings under 25,000 square feet and to choose a path\r\nto compliance based on either of the below options but are not required to\r\nsubmit energy data on an annual basis.
\r\n\r\nBuildings 5,000 to 24,999 sq. ft.,\r\ndo not have to send annual Benchmarking Reports or meet an energy use intensity\r\nperformance requirement. Instead, these buildings have two options* to comply\r\nwith Energize Denver:
\r\n\r\nOR
\r\n\r\n*Building owners do not have to do both\r\noptions, only one is required for compliance.
Find more information here.These datasets are the greenhouse gas inventories for the City and County of Denver and are reflective of community-wide emissions.
", "keyword": [ "ODC" ], "issued": "2025-07-30T16:26:13.000Z", "modified": "2025-07-30T16:27:12.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::2022-denver-ghg-inventory" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=274ae79d34c644d3ba0363c01c7ea206&sublayer=26", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::energize-denver-2021-final-master-dataset", "title": "Energize Denver 2021 Final Master Dataset", "description": "These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org)
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org)
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org)
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org)
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with\nthe Energize Denver regulatory program that requires buildings 25,000 square\nfeet and larger to submit their energy benchmarking data once a year. Building\nenergy use is entered into a national benchmarking software database and submitted\nit to CASR annually. The basic benchmarking requirements are covered on this\npage: BenchmarkingRequirements - City and County of Denver (denvergov.org)
", "keyword": [ "ODC" ], "issued": "2024-05-08T18:07:30.000Z", "modified": "2024-07-08T15:51:43.417Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org)
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org).
Since 2022, CASR added requirements for the buildings to\nreach a certain level of energy efficiency in their building by 2030. The most\nrecent dataset shows the annual benchmarking data for the 3,000 buildings that\nhave to comply, but it also now includes what their energy use intensity target\nis for 2030 (with interim check-ins in 2025 and 2027). The basic performance\nrequirements are covered on this page: Performance\nRequirements - City and County of Denver (denvergov.org)
", "keyword": [ "ODC" ], "issued": "2024-05-08T18:09:07.000Z", "modified": "2024-07-08T15:52:30.835Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "keyword": [ "ODC" ], "issued": "2024-10-21T14:44:53.000Z", "modified": "2026-08-07T19:16:18.936Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "-105.3337,39.5613,-104.6711,39.9009", "license": "The Department of Transportation and Infrastructure (DOTI) through its Strategic Transportation Plan, Denver Moves Everyone, has developed a comprehensive inventory of all proposed and active transportation projects in the City and County of Denver. This inventory includes transportation recommendations identified by past planning efforts such as Neighborhood Planning Initiative (NPI) plans, multimodal network plans, area plans, and corridor studies. This dataset will be updated at least annually as additional projects are identified from on-going and future planning efforts.
", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::denver-proposed-transportation-projects" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/Denver_Proposed_Transportation_Projects/FeatureServer/420" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/bd613ae0a5284e2294031bcdd4283f8a/csv?layers=420" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/bd613ae0a5284e2294031bcdd4283f8a/shapefile?layers=420" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/bd613ae0a5284e2294031bcdd4283f8a/geojson?layers=420" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/bd613ae0a5284e2294031bcdd4283f8a/kml?layers=420" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/bd613ae0a5284e2294031bcdd4283f8a/filegdb?layers=420" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/bd613ae0a5284e2294031bcdd4283f8a/featureCollection?layers=420" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/bd613ae0a5284e2294031bcdd4283f8a/excel?layers=420" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/bd613ae0a5284e2294031bcdd4283f8a/geoPackage?layers=420" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/bd613ae0a5284e2294031bcdd4283f8a/sqlite?layers=420" } ], "theme": [ "geospatial" ] }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=ff6c84d8881647ca97b439971ad20a72&sublayer=0", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::311-service-requests-2023", "title": "311 Service Requests 2023", "description": "ACCESS CONSTRAINTS: None. USE CONSTRAINTS: The City and County of Denver is not responsible and shall not be liable to the user for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use of the data/information provided. NOT FOR ENGINEERING PURPOSES
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for service request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for service request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested information/service |
| 18 | Division | Animal Care and Control | Text | 20 | Division within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
", "keyword": [ "ODC" ], "issued": "2025-02-20T21:23:06.000Z", "modified": "2025-02-20T21:41:48.054Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "-105.1101,39.6144,-104.7338,39.8415", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::snow-routes" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_TRANS_SNOWROUTE_L/FeatureServer/310" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8af7559b35f74fc5ae19bb40f23666dc/csv?layers=310" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8af7559b35f74fc5ae19bb40f23666dc/shapefile?layers=310" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8af7559b35f74fc5ae19bb40f23666dc/geojson?layers=310" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8af7559b35f74fc5ae19bb40f23666dc/kml?layers=310" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8af7559b35f74fc5ae19bb40f23666dc/filegdb?layers=310" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8af7559b35f74fc5ae19bb40f23666dc/featureCollection?layers=310" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8af7559b35f74fc5ae19bb40f23666dc/excel?layers=310" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8af7559b35f74fc5ae19bb40f23666dc/geoPackage?layers=310" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8af7559b35f74fc5ae19bb40f23666dc/sqlite?layers=310" } ], "theme": [ "geospatial" ] }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=c4daff503b754b97a06994521de96b8f&sublayer=416", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::sidewalks-asset", "title": "Sidewalks Asset", "description": "Sidewalk assets are a linear GIS layer used as a CCD-owned dataset to track sidewalk inventory and condition.", "keyword": [ "ODC" ], "issued": "2024-08-06T13:00:08.000Z", "modified": "2025-02-04T14:01:21.419Z", "publisher": { "name": "Roadway Asset Services (RAS), https://www.roadwayassetservices.com/" }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "-105.1098,39.6142,-104.7338,39.8415", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::sidewalks-asset" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_TRANS_SIDEWALKASSET_L/FeatureServer/416" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c4daff503b754b97a06994521de96b8f/csv?layers=416" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c4daff503b754b97a06994521de96b8f/shapefile?layers=416" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c4daff503b754b97a06994521de96b8f/geojson?layers=416" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c4daff503b754b97a06994521de96b8f/kml?layers=416" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c4daff503b754b97a06994521de96b8f/filegdb?layers=416" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c4daff503b754b97a06994521de96b8f/featureCollection?layers=416" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c4daff503b754b97a06994521de96b8f/excel?layers=416" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c4daff503b754b97a06994521de96b8f/geoPackage?layers=416" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/c4daff503b754b97a06994521de96b8f/sqlite?layers=416" } ], "theme": [ "geospatial" ] }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=cb2e466f1fdf48ba8b3625939cb7d021&sublayer=0", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2024-procurement-card", "title": "2024 Procurement Card", "description": "DOTI provides snow response services to approximately 2,050 lane miles of main streets, or most streets with stripes, utilizing a fleet of 70 large plows, and plows around schools to provide safe zones for school children.
This dataset included accounts payable payments made to vendors by the City and County of Denver for the current year to date and previous years. The datasets are refreshed each day with the previous business day's transactions. New travel datasets cannot be provided from August 2017 due to confidentiality concerns however, historic travel datasets will be maintained.
Notice: In August 2017, the city implemented a new financial system which created new Expense categories and prompted some expenses to roll in to different or new categories. When viewing 2017 data you may have to look at several Expense categories for a complete picture. Procurement data from August 2017 to December 2017 are in a separate file. When viewing 2017 procurement data, you will need two files.
Disclaimer: The City and County of Denver is committed to the highest levels of data security and privacy, therefore not all payment transactions will be displayed. Payment transactions that are confidential are excluded from the data. Protected information such as social security numbers, banking information, and personal data are excluded from payment transaction details. Payments to retirement and health care providers include employee contributions. The data contained on this website is unaudited and is for informational purposes only. It is not the intent of the site to provide information that may be used to determine or influence the financial decisions of any website user.
For transaction inquiries, email CTLGeneralAccounting@denvergov.org
Author: City and County of Denver - CTL General Accounting
Author Email: CTLGeneralAccounting@denvergov.org
Maintainer: City and County of Denver - CTL General Accounting
Maintainer Email: CTLGeneralAccounting@denvergov.org
", "keyword": [ "ODC" ], "issued": "2024-05-08T18:20:49.000Z", "modified": "2024-07-08T15:44:37.542Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2023-checkbook" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_checkbook_2023/FeatureServer/39" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/641303d7be0b445e9069f3b8ae8a1292/csv?layers=39" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/641303d7be0b445e9069f3b8ae8a1292/shapefile?layers=39" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/641303d7be0b445e9069f3b8ae8a1292/geojson?layers=39" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/641303d7be0b445e9069f3b8ae8a1292/kml?layers=39" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/641303d7be0b445e9069f3b8ae8a1292/filegdb?layers=39" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/641303d7be0b445e9069f3b8ae8a1292/featureCollection?layers=39" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/641303d7be0b445e9069f3b8ae8a1292/excel?layers=39" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/641303d7be0b445e9069f3b8ae8a1292/geoPackage?layers=39" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/641303d7be0b445e9069f3b8ae8a1292/sqlite?layers=39" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=ca9c7de83aff4c07b770c22e91e68a00", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/documents/geospatialDenver::denver-affordable-housing-dashboard", "title": "Denver Affordable Housing Dashboard", "description": "Market Conditions, Affordable Housing Map, and Definitions & Data Notes.Sidewalk ramps delineated from 2022 aerial imagery. CAPTURE CRITERIA: Sidewalk ramps are compiled in 2D. This feature includes the point location of sidewalk ramps. Ramps do not have to connect to other layers (e.g. sidewalk centerlines). Ramps do not have to be ADA accessible to be captured (imagery resolution is not high enough to discern this characteristic). CHANGE FEATURES: This dataset is an update to previously collected data. Features were originally delineated from 2014 aerial imagery, updated in 2016, 2018, 2020, and then again in 2022 to create this dataset. Examples of change that are captured include but are not limited to: new features, change in attribution, and modifications that reach or exceed the threshold for initial collection of this feature. Additions refer not only to truly new features in the built environment but also to features that are added based on a larger extent of capture. Please refer to extent shapefiles for 2014, 2016, 2018, 2020, and 2022 feature captures before doing change analysis. Modifications are marked even if only a small portion of the feature has been changed. A separate change layer is available to show only those features that were delineated in 2022. SOURCE DATA: This feature was compiled from DRCOG 2022 Denver Regional Aerial Photography Project (DRAPP) imagery. This imagery is 4-band RGBIR color orthoimagery with a GSD (Ground Sample Distance) of 0.5 foot for 3-inch imagery, 1 foot for 6-inch imagery, and 2 feet for 12-inch imagery. Imagery was collected in the spring with a Vexcel Ultracam Eagle aerial sensor. Imagery is projected in the State Plane Coordinate System, Colorado Central Zone using the Lambert Conformal Conic map projection parameters. Horizontal and vertical datums are NAD83(11) and NAVD88(GEOID12A), respectively.
Building roofprints delineated from 2022 aerial imagery. CAPTURE CRITERIA: Building roofprint polygons are stereocompiled in 3D. Outlines of permanent, visible structures are captured at the corners of the roof (eave). Buildings with area greater than or equal to 48 square feet and over 5 feet in height are collected. Arms and indentations must be 2.5 feet or greater to be captured. Canopies, carport covers, and sheds are included. For multi-level commercial and/or industrial buildings, each level is captured as a unique record if the building is greater than or equal to 1000 square feet and the multi-level roof levels are greater than or equal to 400 square feet in area and over 5 feet in height. Each polygon is a separate record. Polygons that are part of the same building have the same building ID. For pitched roofs, the highest point is used to determine the building height. The lowest point is the common lowest point if the building is multi-level. ATTRIBUTION: Unique ID, Height (feet), Ground Elevation (feet), Building Type (Residential, Commercial, Industrial, Medical, Public, Garage/Shed, Parking Structure, Tank, Foundation/Ruin, Miscellaneous). Building addresses are available for project partners, courtesy of BuildingFootprintsUSA. CHANGE FEATURES: This dataset is an update to previously collected data. Features were originally delineated from 2014 aerial imagery, updated in 2016, 2018, 2020, and then again in 2022 to create this dataset. Examples of change that are captured include but are not limited to: new features, change in attribution, and modifications that reach or exceed the threshold for initial collection of this feature. Additions refer not only to truly new features in the built environment but also to features that are added based on a larger extent of capture. Please refer to extent shapefiles for 2014, 2016, 2018, 2020, and 2022 feature captures before doing change analysis. Modifications are marked even if only a small portion of the feature has been changed. A separate change layer is available to show only those features that were delineated in 2022. SOURCE DATA: This feature was compiled from DRCOG 2022 Denver Regional Aerial Photography Project (DRAPP) imagery. This imagery is 4-band RGBIR color orthoimagery with a GSD (Ground Sample Distance) of 0.5 foot for 3-inch imagery, 1 foot for 6-inch imagery, and 2 feet for 12-inch imagery. Imagery was collected in the spring with a Vexcel Ultracam Eagle aerial sensor. Imagery is projected in the State Plane Coordinate System, Colorado Central Zone using the Lambert Conformal Conic map projection parameters. Horizontal and vertical datums are NAD83(11) and NAVD88(GEOID12A), respectively.
The Department of Transportation & Infrastructure (DOTI) developed the DOTI Equity Index to prioritize areas of need and capital allocation for projects. The Transportation Mobility Planning Division uses the Equity Index to determine Denver’s Priority Areas for Transportation Equity. The resulting data model uses a data-driven approach to evaluate areas of inequity by performing a weighted overlay analysis using demographic indicators that correlate with more historic disinvestment, which also indicates a higher reliance on active transportation and transit systems. The equity index is intended to be used with supplemental data to help provide a better overall picture for any given program. For example, the Vision Zero program will also use safety and vehicle crash data in unison with the equity index to help prioritize investment locations.
The Equity Index is comprised of the following seven demographic characteristics:
Race & Ethnicity
Income & Poverty
Education Level
Populations of Age 65+
Households with No Vehicle
Female Heads of Household
People with Disabilities
Denver’s Residential Snow Plow Program was created during the blizzards of 2006-07 to keep residential streets, or side streets, passable. The program covers about 1,260 center lane miles of residential streets, utilizing a fleet of 4x4 pickup trucks with plows.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
| 311 SERVICE DATA METADATA | |||||
| Abstract: | This table provides a description of each of the data elements contained in the 311 Customer Service Requests data files. | ||||
| Pos | Field Name | Example | Column Type | Length | Description |
| 1 | Case Summary | Problem with Barking Dogs | Text | 80 | General summary of request |
| 2 | Case Status | Closed | Text | 10 | Current status of request |
| 3 | Case Source | Phone | Text | 20 | Source of request |
| 4 | Case Created Date | 01/01/2013 | Date | 10 | Date request was made |
| 5 | Case Created Dttm | 01/01/2013 10:22 | Dttm | 16 | Date and time request was made |
| 6 | Case Closed Date | 01/01/2013 | Date | 10 | Date request was resolved |
| 7 | Case Closed Dttm | 01/01/2013 15:10 | Dttm | 16 | Date and time request was resolved |
| 8 | First Call Resolution | Y | Text | 1 | Was request resolved by 311 Call Center? |
| 9 | Customer Zip Code | 80202 | Text | 10 | Zip Code of requestor |
| 10 | Incident Address 1 | 123 Elm St | Text | 55 | Street Address related to service request |
| 11 | Incident Address 2 | Apt. 205 | Text | 55 | Secondary address for service request |
| 12 | Incident Intersection 1 | N Speer Blvd | Text | 50 | Cross street 1 related to service request |
| 13 | Incident Intersection 2 | Wewatta St | Text | 50 | Cross street 2 related to service request |
| 14 | Incident Zip Code | 80202 | Text | 12 | Zip Code for service request |
| 15 | Longitude | 80237 | Text | 11 | GIS Longitudinal coordinate of Address for sercie request |
| 16 | Latitude | 3114 | Text | 20 | GIS Latitudinal coordinate of Address for sercie request |
| 17 | Agency | Environment Health | Text | 20 | City Agency responsible for requested informtion/service |
| 18 | Division | Animal Care and Control | Text | 20 | Divison within the Agency responsible for requested information/service |
| 19 | Major Area | Animal Control | Text | 20 | Major work area within the Division responsible for requested information/service |
| 20 | Type | Complaint | Text | 20 | Type of request (Information, Service, etc) |
| 21 | Topic | Barking Dog | Text | 20 | Topic of the request |
| 22 | Council District | 10 | Text | 30 | Indicates which Council District the Incident Address resides |
| 23 | Police District | Single Family Residential | Text | 30 | Indicates which Police District the Incident Address resides |
| 24 | Neighborhood | 3 | Text | 30 | Indicates which City Neighborhood the Incident Address resides |
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
This dataset included accounts payable payments made to vendors by the City and County of Denver for the current year to date and previous years. The datasets are refreshed each day with the previous business day's transactions. New travel datasets cannot be provided from August 2017 due to confidentiality concerns however, historic travel datasets will be maintained.
Notice: In August 2017, the city implemented a new financial system which created new Expense categories and prompted some expenses to roll in to different or new categories. When viewing 2017 data you may have to look at several Expense categories for a complete picture. Procurement data from August 2017 to December 2017 are in a separate file. When viewing 2017 procurement data, you will need two files.
Disclaimer: The City and County of Denver is committed to the highest levels of data security and privacy, therefore not all payment transactions will be displayed. Payment transactions that are confidential are excluded from the data. Protected information such as social security numbers, banking information, and personal data are excluded from payment transaction details. Payments to retirement and health care providers include employee contributions. The data contained on this website is unaudited and is for informational purposes only. It is not the intent of the site to provide information that may be used to determine or influence the financial decisions of any website user.
For transaction inquiries, email CTLGeneralAccounting@denvergov.org
Author: City and County of Denver - CTL General Accounting
Author Email: CTLGeneralAccounting@denvergov.org
Maintainer: City and County of Denver - CTL General Accounting
Maintainer Email: CTLGeneralAccounting@denvergov.org
", "keyword": [ "ODC" ], "issued": "2024-05-08T18:19:56.000Z", "modified": "2024-07-08T15:40:33.214Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2022-checkbook" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_checkbook_2022/FeatureServer/38" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/b8b1aaf546344ced89797e60dc6f5cda/csv?layers=38" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/b8b1aaf546344ced89797e60dc6f5cda/shapefile?layers=38" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/b8b1aaf546344ced89797e60dc6f5cda/geojson?layers=38" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/b8b1aaf546344ced89797e60dc6f5cda/kml?layers=38" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/b8b1aaf546344ced89797e60dc6f5cda/filegdb?layers=38" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/b8b1aaf546344ced89797e60dc6f5cda/featureCollection?layers=38" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/b8b1aaf546344ced89797e60dc6f5cda/excel?layers=38" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/b8b1aaf546344ced89797e60dc6f5cda/geoPackage?layers=38" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/b8b1aaf546344ced89797e60dc6f5cda/sqlite?layers=38" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=2eaca84771fb4cd4be9dae369c79845b&sublayer=37", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2021-checkbook", "title": "2021 Checkbook", "description": "This dataset included accounts payable payments made to vendors by the City and County of Denver for the current year to date and previous years. The datasets are refreshed each day with the previous business day's transactions. New travel datasets cannot be provided from August 2017 due to confidentiality concerns however, historic travel datasets will be maintained.
Notice: In August 2017, the city implemented a new financial system which created new Expense categories and prompted some expenses to roll in to different or new categories. When viewing 2017 data you may have to look at several Expense categories for a complete picture. Procurement data from August 2017 to December 2017 are in a separate file. When viewing 2017 procurement data, you will need two files.
Disclaimer: The City and County of Denver is committed to the highest levels of data security and privacy, therefore not all payment transactions will be displayed. Payment transactions that are confidential are excluded from the data. Protected information such as social security numbers, banking information, and personal data are excluded from payment transaction details. Payments to retirement and health care providers include employee contributions. The data contained on this website is unaudited and is for informational purposes only. It is not the intent of the site to provide information that may be used to determine or influence the financial decisions of any website user.
For transaction inquiries, email CTLGeneralAccounting@denvergov.org
Author: City and County of Denver - CTL General Accounting
Author Email: CTLGeneralAccounting@denvergov.org
Maintainer: City and County of Denver - CTL General Accounting
Maintainer Email: CTLGeneralAccounting@denvergov.org
", "keyword": [ "ODC" ], "issued": "2024-05-08T18:19:01.000Z", "modified": "2024-07-08T15:40:20.126Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2021-checkbook" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_checkbook_2021/FeatureServer/37" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/2eaca84771fb4cd4be9dae369c79845b/csv?layers=37" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/2eaca84771fb4cd4be9dae369c79845b/shapefile?layers=37" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/2eaca84771fb4cd4be9dae369c79845b/geojson?layers=37" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/2eaca84771fb4cd4be9dae369c79845b/kml?layers=37" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/2eaca84771fb4cd4be9dae369c79845b/filegdb?layers=37" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/2eaca84771fb4cd4be9dae369c79845b/featureCollection?layers=37" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/2eaca84771fb4cd4be9dae369c79845b/excel?layers=37" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/2eaca84771fb4cd4be9dae369c79845b/geoPackage?layers=37" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/2eaca84771fb4cd4be9dae369c79845b/sqlite?layers=37" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=f32887a90fb84ab590af1c45d377f55c&sublayer=27", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2021-water-quality-table", "title": "2021 Water Quality Table", "description": "This dataset included accounts payable payments made to vendors by the City and County of Denver for the current year to date and previous years. The datasets are refreshed each day with the previous business day's transactions. New travel datasets cannot be provided from August 2017 due to confidentiality concerns however, historic travel datasets will be maintained.
Notice: In August 2017, the city implemented a new financial system which created new Expense categories and prompted some expenses to roll in to different or new categories. When viewing 2017 data you may have to look at several Expense categories for a complete picture. Procurement data from August 2017 to December 2017 are in a separate file. When viewing 2017 procurement data, you will need two files.
Disclaimer: The City and County of Denver is committed to the highest levels of data security and privacy, therefore not all payment transactions will be displayed. Payment transactions that are confidential are excluded from the data. Protected information such as social security numbers, banking information, and personal data are excluded from payment transaction details. Payments to retirement and health care providers include employee contributions. The data contained on this website is unaudited and is for informational purposes only. It is not the intent of the site to provide information that may be used to determine or influence the financial decisions of any website user.
For transaction inquiries, email CTLGeneralAccounting@denvergov.org
Author: City and County of Denver - CTL General Accounting
Author Email: CTLGeneralAccounting@denvergov.org
Maintainer: City and County of Denver - CTL General Accounting
Maintainer Email: CTLGeneralAccounting@denvergov.org
", "keyword": [ "ODC" ], "issued": "2024-05-08T18:17:56.000Z", "modified": "2024-07-08T15:35:14.648Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2020-checkbook" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_checkbook_2020/FeatureServer/36" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8751b6eced9b423f8b93799a0c0ddf57/csv?layers=36" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8751b6eced9b423f8b93799a0c0ddf57/shapefile?layers=36" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8751b6eced9b423f8b93799a0c0ddf57/geojson?layers=36" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8751b6eced9b423f8b93799a0c0ddf57/kml?layers=36" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8751b6eced9b423f8b93799a0c0ddf57/filegdb?layers=36" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8751b6eced9b423f8b93799a0c0ddf57/featureCollection?layers=36" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8751b6eced9b423f8b93799a0c0ddf57/excel?layers=36" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8751b6eced9b423f8b93799a0c0ddf57/geoPackage?layers=36" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/8751b6eced9b423f8b93799a0c0ddf57/sqlite?layers=36" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=6fbaa0f572ef43bbb4d1435c121ef82c&sublayer=55", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2021-procurement-card", "title": "2021 Procurement Card", "description": "This dataset included accounts payable payments made to vendors by the City and County of Denver for the current year to date and previous years. The datasets are refreshed each day with the previous business day's transactions. New travel datasets cannot be provided from August 2017 due to confidentiality concerns however, historic travel datasets will be maintained.
Notice: In August 2017, the city implemented a new financial system which created new Expense categories and prompted some expenses to roll in to different or new categories. When viewing 2017 data you may have to look at several Expense categories for a complete picture. Procurement data from August 2017 to December 2017 are in a separate file. When viewing 2017 procurement data, you will need two files.
Disclaimer: The City and County of Denver is committed to the highest levels of data security and privacy, therefore not all payment transactions will be displayed. Payment transactions that are confidential are excluded from the data. Protected information such as social security numbers, banking information, and personal data are excluded from payment transaction details. Payments to retirement and health care providers include employee contributions. The data contained on this website is unaudited and is for informational purposes only. It is not the intent of the site to provide information that may be used to determine or influence the financial decisions of any website user.
For transaction inquiries, email CTLGeneralAccounting@denvergov.org
Author: City and County of Denver - CTL General Accounting
Author Email: CTLGeneralAccounting@denvergov.org
Maintainer: City and County of Denver - CTL General Accounting
Maintainer Email: CTLGeneralAccounting@denvergov.org
", "keyword": [ "ODC" ], "issued": "2024-05-08T18:16:58.000Z", "modified": "2024-07-08T15:29:44.914Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2019-checkbook" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_checkbook_2019/FeatureServer/35" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f26c0c60db124862978f6fbb65505e2d/csv?layers=35" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f26c0c60db124862978f6fbb65505e2d/shapefile?layers=35" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f26c0c60db124862978f6fbb65505e2d/geojson?layers=35" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f26c0c60db124862978f6fbb65505e2d/kml?layers=35" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f26c0c60db124862978f6fbb65505e2d/filegdb?layers=35" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f26c0c60db124862978f6fbb65505e2d/featureCollection?layers=35" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f26c0c60db124862978f6fbb65505e2d/excel?layers=35" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f26c0c60db124862978f6fbb65505e2d/geoPackage?layers=35" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/f26c0c60db124862978f6fbb65505e2d/sqlite?layers=35" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=c4066bb671984043880e70359722b3af&sublayer=18", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2018-water-quality-data", "title": "2018 Water Quality Data", "description": "This dataset included accounts payable payments made to vendors by the City and County of Denver for the current year to date and previous years. The datasets are refreshed each day with the previous business day's transactions. New travel datasets cannot be provided from August 2017 due to confidentiality concerns however, historic travel datasets will be maintained.
Notice: In August 2017, the city implemented a new financial system which created new Expense categories and prompted some expenses to roll in to different or new categories. When viewing 2017 data you may have to look at several Expense categories for a complete picture. Procurement data from August 2017 to December 2017 are in a separate file. When viewing 2017 procurement data, you will need two files.
Disclaimer: The City and County of Denver is committed to the highest levels of data security and privacy, therefore not all payment transactions will be displayed. Payment transactions that are confidential are excluded from the data. Protected information such as social security numbers, banking information, and personal data are excluded from payment transaction details. Payments to retirement and health care providers include employee contributions. The data contained on this website is unaudited and is for informational purposes only. It is not the intent of the site to provide information that may be used to determine or influence the financial decisions of any website user.
For transaction inquiries, email CTLGeneralAccounting@denvergov.org
Author: City and County of Denver - CTL General Accounting
Author Email: CTLGeneralAccounting@denvergov.org
Maintainer: City and County of Denver - CTL General Accounting
Maintainer Email: CTLGeneralAccounting@denvergov.org
", "keyword": [ "ODC" ], "issued": "2024-05-08T18:15:58.000Z", "modified": "2024-07-08T15:29:30.254Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2018-checkbook" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_checkbook_2018/FeatureServer/34" }, { "@type": "dcat:Distribution", "title": "CSV", "format": "CSV", "mediaType": "text/csv", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/e3fd8ff006c74f1b9081e3064eb05a1e/csv?layers=34" }, { "@type": "dcat:Distribution", "title": "Shapefile", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/e3fd8ff006c74f1b9081e3064eb05a1e/shapefile?layers=34" }, { "@type": "dcat:Distribution", "title": "GeoJSON", "format": "GeoJSON", "mediaType": "application/vnd.geo+json", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/e3fd8ff006c74f1b9081e3064eb05a1e/geojson?layers=34" }, { "@type": "dcat:Distribution", "title": "KML", "format": "KML", "mediaType": "application/vnd.google-earth.kml+xml", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/e3fd8ff006c74f1b9081e3064eb05a1e/kml?layers=34" }, { "@type": "dcat:Distribution", "title": "File Geodatabase", "format": "ZIP", "mediaType": "application/zip", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/e3fd8ff006c74f1b9081e3064eb05a1e/filegdb?layers=34" }, { "@type": "dcat:Distribution", "title": "Feature Collection", "format": "TXT", "mediaType": "text/plain", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/e3fd8ff006c74f1b9081e3064eb05a1e/featureCollection?layers=34" }, { "@type": "dcat:Distribution", "title": "Excel", "format": "XLSX", "mediaType": "application/vnd.ms-excel", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/e3fd8ff006c74f1b9081e3064eb05a1e/excel?layers=34" }, { "@type": "dcat:Distribution", "title": "GeoPackage", "format": "GPKG", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/e3fd8ff006c74f1b9081e3064eb05a1e/geoPackage?layers=34" }, { "@type": "dcat:Distribution", "title": "SQLite Geodatabase", "format": "GDB", "mediaType": "application/geopackage+sqlite3", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/api/download/v1/items/e3fd8ff006c74f1b9081e3064eb05a1e/sqlite?layers=34" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=3b20f1a66dc44fc6b9268bf38acb14b4&sublayer=15", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::2017-water-quality-data", "title": "2017 Water Quality Data", "description": "The Denver Police Station and facility locations for the Denver Police Department.
Location of Denver Sheriff's offices. Tabular data includes the location name as defined by the Sheriff's Office, street address, additional information to assist the public in locating the sheriff's office, office phone numbers, primary and secondary email address, hours of operation, additional office description information, services available at specified location, and an image name associated with the sheriff's office.
What is ArcGIS Online?
Access to the City and County of Denver AGOL is provided to those who meet the access requirements.
", "keyword": [ "ODC" ], "issued": "2023-03-20T14:13:11.000Z", "modified": "2024-06-18T16:50:51.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "ACCESS CONSTRAINTS: None. USE CONSTRAINTS: The City and County of Denver is not responsible and shall not be liable to the user for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use of the data/information provided. NOT FOR ENGINEERING PURPOSES", "distribution": [ { "@type": "dcat:Distribution", "title": "ArcGIS Hub Dataset", "format": "Web Page", "mediaType": "text/html", "accessURL": "https://opendata-geospatialdenver.hub.arcgis.com/apps/geospatialDenver::arcgis-online-agol-training" }, { "@type": "dcat:Distribution", "title": "ArcGIS GeoService", "format": "ArcGIS GeoServices REST API", "mediaType": "application/json", "accessURL": "https://storymaps.arcgis.com/stories/ad8d5c4fb39342fb92e033f2541fd4ce" } ], "theme": "" }, { "@type": "dcat:Dataset", "identifier": "https://www.arcgis.com/home/item.html?id=f730804d9eb34dcca40c161e504367a8&sublayer=34", "landingPage": "https://opendata-geospatialdenver.hub.arcgis.com/datasets/geospatialDenver::election-precincts", "title": "Election Precincts", "description": "The City and County of Denver's current election precincts. The original election precinct boundaries have been adjusted to the Denver GIS census block coverage to increase the spatial accuracy of this data. Although every effort was made to ensure the accurate rectification of the data, due to geographic problems inherent in the original 2010 census block data, errors may exist.
This dataset represents existing land use by parcel. The dataset was compiled from Assessor parcel records by generalizing their land use classifications into categories specific to planning.
The Climate Action, Sustainability & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: Benchmarking Requirements - City and County of Denver (denvergov.org)
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
The Climate Action, Sustainability & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: Benchmarking Requirements - City and County of Denver (denvergov.org)
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
The Climate\nAction, Sustainability & Resiliency team manages compliance with\nthe Energize Denver regulatory program that requires buildings 25,000 square\nfeet and larger to submit their energy benchmarking data once a year. Building\nenergy use is entered into a national benchmarking software database and submitted\nit to CASR annually. The basic benchmarking requirements are covered on this\npage: Benchmarking\nRequirements - City and County of Denver (denvergov.org)
", "keyword": [ "ODC" ], "issued": "2024-05-28T19:19:54.000Z", "modified": "2024-05-30T19:05:39.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
The Climate\nAction, Sustainability & Resiliency team manages compliance with\nthe Energize Denver regulatory program that requires buildings 25,000 square\nfeet and larger to submit their energy benchmarking data once a year. Building\nenergy use is entered into a national benchmarking software database and submitted\nit to CASR annually. The basic benchmarking requirements are covered on this\npage: Benchmarking\nRequirements - City and County of Denver (denvergov.org)
", "keyword": [ "ODC" ], "issued": "2024-05-28T19:38:57.000Z", "modified": "2024-05-30T19:05:09.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
The Climate\nAction, Sustainability & Resiliency team manages compliance with\nthe Energize Denver regulatory program that requires buildings 25,000 square\nfeet and larger to submit their energy benchmarking data once a year. Building\nenergy use is entered into a national benchmarking software database and submitted\nit to CASR annually. The basic benchmarking requirements are covered on this\npage: Benchmarking\nRequirements - City and County of Denver (denvergov.org)
", "keyword": [ "ODC" ], "issued": "2024-05-28T19:34:23.000Z", "modified": "2024-05-30T19:04:50.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
The Climate\nAction, Sustainability & Resiliency team manages compliance with\nthe Energize Denver regulatory program that requires buildings 25,000 square\nfeet and larger to submit their energy benchmarking data once a year. Building\nenergy use is entered into a national benchmarking software database and submitted\nit to CASR annually. The basic benchmarking requirements are covered on this\npage: Benchmarking\nRequirements - City and County of Denver (denvergov.org
", "keyword": [ "ODC" ], "issued": "2024-05-28T19:08:21.000Z", "modified": "2024-05-30T19:04:34.000Z", "publisher": { "name": "geospatialDENVER: Putting Denver on the map." }, "contactPoint": { "@type": "vcard:Contact", "fn": "The_City_and_County_of_Denver", "hasEmail": "{{orgContactEmail}}" }, "accessLevel": "public", "spatial": "", "license": "USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
These are the complete benchmarking datasets from reporting year 2016 onward with energy usage for all buildings covered under the City and County of Denver’s Energy Benchmarking Ordinance. The Climate Action, Sustainability, & Resiliency team manages compliance with the Energize Denver regulatory program that requires buildings 25,000 square feet and larger to submit their energy benchmarking data once a year. Building energy use is entered into a national benchmarking software database and submitted it to CASR annually. The basic benchmarking requirements are covered on this page: BenchmarkingRequirements - City and County of Denver (denvergov.org).
USE CONSTRAINTS — The City and County of Denver is not responsible and shall not be liable to any user or recipient for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use. ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AND THE RECIPIENT HEREBY WAIVES ANY AND ALL SUCH WARRANTIES, INCLUDING, BUT NOT LIMITED TO, ANY WARANTY AS TO THE ACCURACY OR COMPLETENESS OF THE INFORMATION AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use, reproduction or dissemination of the data/information provided. NOT FOR ENGINEERING PURPOSES.
This layer contains the extent of City Engineer Official Resurvey maps. These maps were created by the City Engineers office from approximately 1889 to approximately 1949. Resurveys were recorded as pages in the Engineers Subdivision plat book. Each polygon in the dataset represents a resurvey page from the City Engineers Subdivision plat book.
This coverage describes the groundwater elevation beneath the City and County of Denver at one foot intervals.
Points on Cherry Creek, the South Platte River, and other tributaries where water samples are taken by Denver Environmental Health (DEH) personnel for the purpose of water quality monitoring and analysis.
The content are bridges and retaining walls owned by the City and County of Denver; as well as non-City and County of Denver (CCD) owned structures within the CCD boundary. Non-CCD owned structure are identified by LEGACY_ID containing NONCCD.
This layer shows the location of Department of Motor Vehicles (DMV) offices within Denver. The data were collected by the Motor Vehicles Division of the City and County of Denver
This dataset represents existing land use by parcel. The dataset was compiled from Assessor parcel records by generalizing their land use classifications into categories specific to planning.
Downtown Denver Historic District as established by city ordinance #972 of 2000.
This coverage describes the groundwater elevation beneath the City and County of Denver at five foot intervals.
A linear representation of the City and County of Denver's jurisdictional boundary. Linear attributes include survey course number and the method by which each course of the boundary was digitized. This dataset also includes all enclaves administered by other jurisdications that are located within the City and County of Denver's boundary.
A polygonal representation of the City and County of Denver's jurisdictional boundary. This datasets also includes all enclaves administered by other jurisdications that are located within the City and County of Denver's boundary.
This layer contains Denver's City Council Districts as they were defined during the redistricting process approved on April 30, 2012. These districts were adopted in 2012 via Ordinance 242; Council Bill 286. This layer also contains records for the at-large candidates (to be consistent with previous City Council District layers).The Denver's City Council districts are effective for the municipal election on May 7, 2019, and for any general or special council election held thereafter. The resulting elected Council District representatives take office; and representation of constituents within the new boundaries begins on July 15, 2019. Newly elected representatives names publish on that date.
Based upon the Neighborhoods layer from Community Planning and Development. This layer is a duplicate of that layer, but with additional demographic information compiled from the 2010 US Census. Although every effort was made to ensure that blocks were assigned to their proper neighborhoods, due to geographic problems inherent in the original 2010 census block data, errors may exist. This data-set includes the housing and population data from redistricting file P.L. 94-171 of the 2010 census. The data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary.
These data are the common data fields from the American Community Survey agreed upon by the Data Indicators GIS Subcommittee. The data source is Census Tract level data from the American Community Survey; 5 year average, years 2017-2021. Data was aggregated at the census tract level, and the summarized into neighborhoods. This information was then joined with Community Planning and Developments Neighborhoods layer. This data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a census. Results should be considered estimates and be used for high level planning purposes only.Since this data was internally derived by the City and County of Denver from census tract level data, Margin of Error statistics from the census tract data could not be accurately aggregated for the neighborhood level data. Therefore, the Margin of Error data is not provided with this data set. Users should use caution as data values are estimates.
These data are the common data fields from the American Community Survey agreed upon by the Data Indicators GIS Subcommittee. The data source is Census Tract level data from the American Community Survey; 5 year average, years 2016-2020. Data was aggregated at the census tract level, and the summarized into neighborhoods. This information was then joined with Community Planning and Developments Neighborhoods layer. This data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a census. Results should be considered estimates and be used for high level planning purposes only.Since this data was internally derived by the City and County of Denver from census tract level data, Margin of Error statistics from the census tract data could not be accurately aggregated for the neighborhood level data. Therefore, the Margin of Error data is not provided with this data set. Users should use caution as data values are estimates.
These data are the common data fields from the American Community Survey agreed upon by the Data Indicators GIS Subcommittee. The data source is Census Tract level data from the American Community Survey; 5 year average, years 2016-2020. The original census tract group boundaries have been adjusted to various Denver GIS data layers to increase the spatial accuracy of this data. Although every effort was made to ensure the accurate rectification of the data, due to geographic problems inherent in the original 2010 census block group data, errors may exist. The data-set does not contain data for any enclaves administered by other jurisdictions that are located within the City and County of Denver's boundary. This data is a sample, not a complete census. Data should be considered estimates and a margin of error table is located on the city network that can be used in conjunction with this dataset.
A polyonal representation of subdivided lot boundaries located within the City and County of Denver.