Appendix E Required Data Formats.docx
DOCX document 10 KB Posted
- Attached to
- Thermal Opportunity Mapping
- Solicitation number
- DQ1 EFAA 2027000087 1
- Issued by
- Denver County, Denver City, Colorado
About this file
This is a technical specifications document for the Thermal Opportunity Mapping project in Colorado, outlining required data delivery formats and spatial reference standards. The contractor must deliver all spatial deliverables in formats natively compatible with ESRI software products (ArcGIS Pro, ArcGIS Enterprise, and ArcGIS Online) without requiring complex format conversions. Acceptable vector dataset formats include Esri File Geodatabase (.gdb), which is preferred for static data; Esri Shapefile (.shp) with all required sidecar files and strict 10-character field name limits; ArcGIS REST Service Endpoints, preferred for live data; and Hosted ESRI Feature Services or Feature Layers with item-level access provided to the OIT GIS Team. Raster data must be delivered as georeferenced TIFF (GeoTIFF, .tif) or similar formats natively consumed by ESRI products, with imagery layers, tiled imagery layers, elevation layers, and tile layers acceptable for raster datasets.
All 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) whenever possible. The contractor should consult with the Chief Executive Officer (CEO) if questions arise regarding finalized file formats to ensure compliance and facilitate seamless integration with existing GIS infrastructure.
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 B_ Vendor Disclosure Statement.pdf | ||
| Appendix D AI Contracting Language.docx | DOCX document | |
| Appendix F Documentation & Metadata Standards.docx | DOCX document |
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 .