Appendix E Required Data Formats.docx
DOCX document 10 KB Posted
- Attached to
- Thermal Opportunity Mapping
- Solicitation number
- DQ1 EFAA 2027000087 3
- Issued by
- Denver County, Denver City, Colorado
About this file
Appendix E of the Thermal Opportunity Mapping contract opportunity for the State of Colorado specifies required data formats for all spatial deliverables. The contractor must deliver finalized vector datasets in at least one of four formats natively consumable by standard ESRI software products (ArcGIS Pro, ArcGIS Enterprise, and ArcGIS Online) without requiring complex conversions or transformation scripts. The preferred format for static data is Esri File Geodatabase (.gdb), with data organized as feature classes or raster images within a single geodatabase. Alternative formats include Esri Shapefile (.shp) with all required sidecar files and strict adherence to 10-character field name limits, ArcGIS REST Service Endpoints for live data sources, and Hosted ESRI Feature Services with item-level access provided to the OIT GIS Team through group sharing or direct ownership transfer. For raster data delivered as standalone files, georeferenced TIFF (GeoTIFF, .tif) or similar ESRI-native formats are required.
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) wherever possible. Imagery layers, tiled imagery layers, elevation layers, and tile layers may be provided for raster datasets. The contractor is directed to contact the CEO immediately if questions arise regarding finalized file formats to ensure compliance with project requirements and successful integration into ESRI systems.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Appendix B_ Vendor Disclosure Statement.pdf | ||
| Appendix F Documentation & Metadata Standards.docx | DOCX document | |
| Amendment #2 DQ EFAA 27-87 Thermal Opportunity Mapping.docx | DOCX document | |
| Appendix C_Vendor Accessibility Checklist.docx | DOCX document | |
| Appendix D AI Contracting Language.docx | DOCX document | |
| Amend # 1 Vendor Q&A DQ EFAA 2027-87 Thermal Opportunity Mapping.pdf | ||
| DQ EFAA 27-87 Thermal Opportunity Mapping.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 .