This data layer was developed to support Denver's Food Retail Expansion to Support Health (FRESH) program. This layer will be stored on the City and County of Denver Spatial Database Engine (SDE) server. The data will be maintained on the SDE by the Office of Economic Development. It will be distributed through the SDE and the Denver Open Data Catalog. Data will be updated as time and resources permit, as data falls out of date, or through annual/bi-annual scheduled maintenance.Denver FRESH representatives will monitor Denver GIS requirements and submit current FRESH data layers to City SDE as applicable. Published data will comply with the City and County of Denver’s requirements and Denver Environmental Health’s GIS Cartographic Standards as described in the data layer’s metadata file. Data sources that originate outside the City must be cited. City data beyond normal base layers should have the sources stated, or if the layer is “unusual” or time sensitive then the source and year should be stated.

This data set represents the extent of the Denver Basin aquifer system in Colorado.

Dataset

This dataset was created by LPK1

Released under CC BY-SA 3.0

Contents

This dataset represents police districts within the boundaries of the City and County of Denver. This data was derived from data in the City of Denver Open Data Catalog (http://data.denvergov.org). The data and related materials are made available through Esri (http://www.esri.com) and are intended for educational purposes only (see Access and Use Constraints section).

This map includes data that represents parks, golf courses, and recreation centers within the boundaries of the City and County of Denver. This data was derived from data in the City of Denver Open Data Catalog (http://data.denvergov.org). The data and related materials are made available through Esri (http://www.esri.com) and are intended for educational purposes only (see Access and Use Constraints section).

In 2004, the U.S. Geological Survey initiated a large-scale regional study of the Denver Basin aquifer system to evaluate the hydrologic effects of continued pumping and document an updated groundwater-flow model useful for appraisal of hydrologic conditions (Paschke, 2011). This data release includes spatial datasets used as input for a three-dimensional groundwater-flow model of the Denver Basin aquifer system. Spatial datasets were developed for six Denver Basin bedrock aquifers and five intervening confining units including, from oldest to youngest, the Laramie-Fox Hills aquifer (KLF), Laramie confining unit (KLC), lower Arapahoe aquifer (LKA), Arapahoe confining unit (KAC), upper Arapahoe aquifer (UKA), Denver lower confining unit (TKDLC), Denver aquifer (TKD), Denver upper confining unit (TKDUC), lower Dawson aquifer (LTDW), Dawson confining unit (TDWC), and upper Dawson aquifer (UTDW). Maps of the base altitude and lateral extent of each aquifer were developed for the 11 aquifer and confining units to define the hydrogeologic framework for the model. The BasePoints.zip folder contains 11 point shapefiles of the data points for altitude of the base of each bedrock aquifer and confining unit and one shapefile with locations of wells in the Denver Basin having geophysical logs ("PP1770_seo_geologs_points"). The "BaseContours.zip" folder contains 11 polyline shapefiles of generalized lines of equal base altitude for each bedrock aquifer and confining unit derived from the base-altitude points, and the "Extents.zip" folder contains 11 polygon shapefiles representing the extent of each aquifer and confining unit. Maps of silt-plus-sand thickness were developed for the six bedrock aquifers and were used to estimate hydraulic conductivity and specific yield in the groundwater-flow model. The "SandPoints.zip" folder contains six point shapefiles of data points for silt-plus-sand thickness of each bedrock aquifer, and the "SandContours.zip" folder contains six polyline shapefiles of generalized lines of equal silt-plus-sand thickness derived from the silt-plus-sand thickness points. Shapefiles in the zipped folders are named using the abbreviation or name of the aquifer or confining unit as shown on Table A2 of Paschke (2011).

The databases contain continuous sensor information as well as time stamped equivalent reference data.

This dataset is associated with the following publication: Feinberg, S., R. Williams, G. Hagler, J. Rickard, R. Brown, D. Garver, G. Harshfield, P. Stauffer, E. Mattson, R. Judge, and S. Garvey. Long-term evaluation of air sensor technology under ambient conditions in Denver, Colorado. Atmospheric Measurement Techniques. Copernicus Publications, Katlenburg-Lindau, GERMANY, 11(8): 4605-4615, (2018).

This map includes data that represents historic landmarks and historic landmark districts within the boundaries of the City and County of Denver. The data in this map was derived from data in the City of Denver Open Data Catalog (http://data.denvergov.org). The data and related materials are made available through Esri (http://www.esri.com) and are intended for educational purposes only (see Access and Use Constraints section).

The data shared here are presented in: Knight, K.L.; Hou, G.; Bhaskar, A.S.; Chen, S. Assessing the Use of Dual-Drainage Modeling to Determine the Effects of Green Stormwater Infrastructure on Roadway Flooding and Traffic Performance. Water 2021, 13, 1563. https://doi.org/10.3390/w13111563

Summary:

I. INPUT FILES

Input data including: stormwater data, DEM, study area outline, service requests, recurring flood locations, precipitation data, and streamflow data. Project files including Pre GSI model, 4 GSI scenario models, and validation model. Pre- and post-processing scripts including: LID application spreadsheet, stormwater data correction, 1D and 2D output data processing. Includes description of labeling method for output data files. The coordinate system of all project files and output data: NAD83 Colorado Central State Plane (US feet)

Stormwater network data (storm manholes, storm inlets, storm sewer mains, streams, and storm water detention and water quality areas) was acquired from the City and County of Denver Open Data catalog (https://www.denvergov.org/opendata)

DEM data (1-meter and 3-meter resolution) was acquired from the National Elevation Dataset (NED) using the United States Geologic Survey (USGS) The National Map (TNM) Download Client (https://apps.nationalmap.gov/downloader/#/)

Study area outline and the bounding layer that delineates roadways from surrounding area are in NAD83 Colorado Central State Plane (US Feet).

Other landuse data (building outlines, impervious area, street centerlines) was acquired from the City and County of Denver Open Data catalog (https://www.denvergov.org/opendata).

Street polygons were produced from the street centerlines data and a buffer representing 1/2 the street width determined from the street centerline attributes of lane numbers and roadway type.

Citizen service requests and known areas of recurring flooding datasets are not publically available, for more information contact Dr. Aditi Bhaskar

Precipitation data was downloaded from USGS at 5 raingages. data files include date, time, and 5-minute precipitation data in inches.

Streamflow data was downloaded from USGS 06711575. Data files include date, time, and 5-minute streamflow data in cubic feet per second.

The LID inputs for each subcatchment utilized a single representative 'GSI unit' based on the design of a street planter bioswale from the City and County of Denver Ultra Urban Report. The LID input for each subcatchment for 1%, 2.5%, 3.5%, and 5% GSI scenarios are included in the table. There are no LIDs applied to the Pre GSI or Validation scenarios.

II. PCSWMM FILES

PCSWMM project files include the '.inp' file and the relevant project file folder that contains the input layers for each PCSWMM project. The name of the project file folder and the '.inp' file are the same and need to be located in the same folder to run simulations. Input layers in the project file folders can be edited and viewed in ArcMap as well, but it is not recommended to directly edit PCSWMM input layers in ArcMap. Rather, create a copy of the desired layer, edit in ArcMap, open the copy in PCSWMM, and update the PCSWMM input layer using the 'import GIS/CAD' tool.

III. MATLAB FILES

The raw stormwater network data from the City and County of Denver was filled and corrected using the methods summarized in Appendix A of the Thesis document. The purpose of this data pre-processing was to fill and correct the missing stormwater network data and convert all known data into the proper formatting for input into PCSWMM. All data is projected into NAD83 Colorado Central State Plane (US feet) coordinate system and clipped to the study boundary.

The hydrograph outputs from the above scenarios were processed using MATLAB. The output streamflow data for each scenario was compared to the observed hydrograph at USGS streamgage 06711575. Additionally, the calibration and validation model outputs were analyzed compared to the observed streamflow data including statistical analysis. All precipitation data is in inches; all streamflow data is in cubic feet per second.

IV. ROAD NETWORK

These are data used for the GIS road network in the traffic modeling by Guangyang Hou (guangyanghou1986@gmail.com).

This supports the article entitled "Understanding spatiotemporal patterns and drivers of urban flooding using municipal reports". This resource includes the R codes and data (imperviousness, rainfall, flood reports, topography, census data) used for the analysis.

This resource contains information from the “City of Denver Open Data Catalog” (http://data.denvergov.org).

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.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

The U.S. Geological Survey developed this dataset as part of the Colorado Front Range Infrastructure Resources Project (FRIRP). One goal of the FRIRP was to provide information on the availability of those hydrogeologic resources that are either critical to maintaining infrastructure along the northern Front Range or that may become less available because of urban expansion in the northern Front Range. This dataset extends from the Boulder-Jefferson County line on the south, to the middle of Larimer and Weld Counties on the North. On the west, this dataset is bounded by the approximate mountain front of the Front Range of the Rocky Mountains; on the east, by an arbitrary north-south line extending through a point about 6.5 kilometers east of Greeley. This digital geospatial dataset consists of digitized water-level-elevation contours.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

This dataset represents historic landmark districts within the boundaries of the City and County of Denver. This data was derived from data in the City of Denver Open Data Catalog (http://data.denvergov.org). The data and related materials are made available through Esri (http://www.esri.com) and are intended for educational purposes only (see Access and Use Constraints section).

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2010 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

These topographic/bathymetric digital elevation models (DEMs) were collected and compiled to characterize erosion and deposition in the Colorado River and in an adjacent zone of laterally recirculating flow (eddy) during both average flow conditions and during a controlled flood that occurred in March 2008. The objectives of the study were to measure changes sandbar morphology that occurred during changes in discharge associated with the controlled flood. These data were collected between February 6 and March 31, 2008 in a 1-mile study reach on the Colorado River within Grand Canyon National Park beginning 44.5 miles downstream from Lees Ferry, Arizona. These data were collected by the USGS Grand Canyon Monitoring and Research Center with cooperators from Northern Arizona University and funding provided by the Glen Canyon Dam Adaptive Management Program. All bathymetric data were collected with a multibeam sonar system (Reson Seabat 8124 sonar with TSS MAHRSS reference system for ...

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. Linear Water Features includes single-line drainage water features and artificial path features that run through double-line drainage features such as rivers and streams, and serve as a linear representation of these features. The artificial path features may correspond to those in the USGS National Hydrographic Dataset (NHD). However, in many cases the features do not match NHD equivalent feature and will not carry the NHD metadata codes. These features have a MAF/TIGER Feature Classification Code (MTFCC) beginning with an "H" to indicate the super class of Hydrographic Features.

This dataset comprises a collection of tabular data and graphical images supporting the U.S. Geological Survey's National Oil and Gas Assessment (NOGA) for Denver Basin Province (039). The dataset includes detailed information on crude oil and natural gas production, including volumetric and descriptive data such as cumulative production, remaining reserves, and known recoverable volumes. Historical data covering field-discovery dates, well completion dates, exploration objectives, and well depths are also provided. Data sources include commercial databases along with supplemental information from various federal and state agencies. No proprietary data is included in this. The dataset is presented in multiple formats, including .pdf files for graphical images and .tab files for tabular data, encompassing eco-regional, federal land, ownership parcels, and state-wise data distributions.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.