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).