File types GriidAi can use
Current spatial and tabular file types for upload and export, plus guidance for Shapefile, CSV, and coordinate systems.
Available upload and export formats are supplied by the app configuration and may change. The current workspace's upload and export controls are the authoritative list for your account and item type.
Common formats
| Data | File type | Notes |
|---|---|---|
| Raster | GeoTIFF (.tif, .tiff) | Common for imagery, elevation, and gridded results. |
| Vector | Shapefile (.shp bundle), GeoJSON (.geojson, .json), FlatGeobuf (.fgb), KML (.kml) | Export choices depend on the item and current app configuration. |
| Vector or table | Parquet (.parquet) | GriidAi inspects the file to determine whether it contains spatial features or tabular records. |
| Table or coordinate data | CSV (.csv) | A CSV can be a table; if it includes recognized geometry or coordinate information it may be spatial. Check the imported result. |
| Multidimensional raster | Zarr (.zarr) | Available as an upload format; export is not offered for every format. |
| Multi-layer data | File Geodatabase archive (.gdb.zip) | Each available layer is handled as part of the import. |
Shapefiles and coordinate systems
A Shapefile needs its geometry and attribute components, normally .shp, .shx, and .dbf. Include .prj when you have it because it identifies the coordinate system. If GriidAi cannot determine the CRS, the item may wait for you to assign it before it can be used. Do not assign a CRS based on guesswork: assigning is different from reprojecting.
Checks before upload
For some formats, the browser checks file structure and whether spatial features are present before upload. For example, it can catch malformed or empty GeoJSON, some incomplete or empty Shapefiles, and GeoParquet files whose metadata reports no spatial rows. These checks are format-specific and do not prove that every file is valid or usable; the server inspects files again after upload. Empty table-only Parquet files can still be valid tables, even though they contain no spatial features.
What can I export?
Data export formats depend on whether the item is raster, vector, or tabular. The export dialog shows the valid choices. Some formats are upload-only, some are export-only, and some accept only certain item types.
Prepare each kind of file
| Format | Before adding it |
|---|---|
| CSV | Keep a clear header row. Include known coordinate columns or WKT geometry when the table should become spatial; a CSV without spatial information can remain a table. Check the imported result. |
| GeoJSON | Include valid feature geometries and properties. Use the upload validation messages to identify malformed or empty spatial data. |
| FlatGeobuf | Select the .fgb file; the server inspects and prepares it for use in the session. |
| GeoTIFF | Preserve its georeferencing and any relevant sidecar metadata. Check the CRS, band meanings, nodata, and units before analysis. |
| KML | Select a supported KML file. Only formats offered by the current upload controls are accepted; a similarly named compressed format is not automatically interchangeable. |
| Parquet or GeoParquet | Keep spatial metadata when present. A Parquet table without geometry is different from a spatial feature layer. |
| Shapefile | Keep matching .shp, .shx, and .dbf files together, with .prj and any useful sidecars. Select the companions together or include them in a supported ZIP upload. |
| File Geodatabase | Keep the .gdb folder and its internal files intact inside the archive. See the preparation steps below. |
| Zarr | Keep the store structure and metadata together, then select variables and dimensions using the Zarr upload controls. |
Prepare a File Geodatabase archive
- Find the complete folder whose name ends in
.gdb. - ZIP that folder with its internal structure intact. Use the
.gdb.ziparchive format accepted by the upload controls. - Add the archive through the device upload flow and review validation before starting it.
- Wait for the available layers to be inspected and processed. Review each imported layer in the catalog before analysis.
A File Geodatabase can contain several datasets. Supported feature classes, tables, and rasters depend on their contents and the available reader; not every object in a geodatabase can be assumed importable. Individual imported items can be inspected, analyzed, and exported using their own available actions.
Files, folders, and ZIP archives
You can select several files or a supported folder through the device upload controls, or drag files into the upload area. Review how the files have been grouped before uploading. An archive does not make an unsupported format supported; keep companion files together and resolve any attention items shown for the group.
Google Drive uses its own import flow and supported choices. See Google Drive import for that workflow.
Need assistance with this workflow?
Our geospatial engineering team is available to help with custom datasets, STAC queries, and algorithms.