Appendix E Required Data Formats.docx
DOCX document 10 KB Posted
- Attached to
- Thermal Opportunity Mapping
- Solicitation number
- DQ1 EFAA 2027000087 2
- Issued by
- Denver County, Denver City, Colorado
About this file
This is a data format specification document for the Colorado Thermal Opportunity Mapping state and local contract opportunity, establishing technical requirements for spatial data deliverables to be provided by the contractor. The project requires all spatial deliverables to be natively consumable within standard ESRI software products including ArcGIS Pro, ArcGIS Enterprise, and ArcGIS Online without requiring complex format conversions or transformation scripts. Contractors must deliver finalized vector datasets in at least one of the following formats: Esri File Geodatabase (.gdb), which is preferred for static data and should organize feature classes or raster images within a single geodatabase; Esri Shapefile (.shp) with all required sidecar files and field names strictly conforming to 10-character limits with no spaces or invalid characters; ArcGIS REST Service Endpoint, preferred for live data when no further processing is required; or Hosted ESRI Feature Service or Feature Layer, preferred for live data with item-level access to the OIT GIS Team through group sharing, collaboration, or direct item ownership transfer.
Raster data provided in standalone format must be delivered in georeferenced TIFF (GeoTIFF, .tif extension) or similar formats natively consumed by ESRI products. Imagery layers, tiled imagery layers, elevation layers, and tile layers may also be provided for raster datasets. Spatial datasets must be delivered in either WGS 1984 (geographic coordinate system, EPSG:4326) or WGS 1984 Web Mercator Auxiliary Sphere (projected coordinate system, EPSG:3857) wherever possible. The document specifies that contractors should contact the CEO immediately with any questions regarding finalized file formats to ensure compliance with project requirements.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DQ EFAA 27-87 Thermal Opportunity Mapping.docx | DOCX document | |
| Appendix C_Vendor Accessibility Checklist.docx | DOCX document | |
| Appendix F Documentation & Metadata Standards.docx | DOCX document | |
| Appendix D AI Contracting Language.docx | DOCX document | |
| Amend # 1 Vendor Q&A DQ EFAA 2027-87 Thermal Opportunity Mapping.pdf | ||
| Appendix B_ Vendor Disclosure Statement.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Appendix E: Required Data Formats All spatial deliverables must be natively consumable within standard ESRI software products (ArcGIS Pro, ArcGIS Enterprise, and ArcGIS Online) without requiring complex spatial format conversions or data transformation scripts before publishing.
The Contractor shall deliver the finalized vector dataset in at least one (1) of the following formats:
· Esri File Geodatabase (.gdb) [PREFERRED FOR STATIC DATA] - Data delivered as feature classes or raster images/mosaics organized within a single File Geodatabase.
· Esri Shapefile (.shp) - Must include all required sidecar files (.shp, .shx, .dbf, .prj, .cpg, and .shp.xml). Field names must conform strictly to 10-character limits and contain no spaces or invalid characters.
· ArcGIS REST Service Endpoint [PREFERRED FOR LIVE DATA] - If data is coming from a simple REST Endpoint and does not require further processing, a REST URL can be provided. Vector and raster data can be shared from this location.
· Hosted ESRI Feature Service / Feature Layer [PREFERRED FOR LIVE DATA] - If data is an ArcGIS Online Hosted Feature Service, the contractor must provide item-level access to the OIT GIS Team via group sharing, Collaboration, or direct item ownership transfer. Imagery layers, tiled imagery layers, elevation layers, and tile layers may also be provided for raster datasets.
Raster Data Note: If raster data is to be provided in a standalone format, it must be in georeferenced TIFF (GeoTIFF, .tif extension) or a similar format that is natively consumed by ESRI products.
If there are questions about finalized file formats, please converse with CEO as quickly as possible.
Spatial Reference:
Wherever possible, spatial datasets must be delivered in either WGS 1984 (geographic coordinate system, EPSG:4326) or WGS 1984 Web Mercator Auxiliary Sphere (projected coordinate system, EPSG:3857).
File details come from the government source that posted it. Updated .