Data Formats

Supported Formats

CSVComma Separated ValuesImport, Export, ...Can contain WKT and GeoJSON geometry columns.
GeoJSONGeographic JavaScript Object NotationImport, Export, ...
JSONJavaScript Object NotationImportCan contain geospatial information, see below.
ShapefileEsri ShapefileImportMultiple files per dataset: .shp, .dbf, .cpg and .prj. (Zipped shapefiles are supported).
glTFGL Transmission Format-Visualize in 3D Layer
ZipArchive formatImportContains multiple datasets, or shapefile(s)
ExcelExcel SpreadsheetsBetaMicrosoft Excel formats, Office Open XML.
KMLKeyhole Markup LanguageBetaOGC standard based on Google Earth markup
GPXGPS eXchange FormatBetaXML schema for waypoints, tracks and routes from GPS receivers.
TCXTraining Center XMLBetaGarmin format, GPS tracks with additional information.
FlatGeobufFlatGeobufImportA performant binary encoding for geographic data.
PMTilesPMTilesImportFormat for storing tiled data addressed by Z/X/Y coordinates in a single (big) archive file.

Supported Services / Protocols

Cloud-Optimized GeoTiffsSTAC metadata with electro-optical/raster extensions-Satellite/raster and visualization
Mapbox Vector TilesTileJSON, MVTImport, ExportVector tile visualization
WMSXML, JPEG, PNG, ...Dynamic WMS visualization (optimized for the viewport)

Feature Matrix

The following badges are used on the documentation page of each format to indicate which Studio Platform features support that format:

StudioData format can be imported into Studio.
StudioData format can be exported from Studio.
SDKData format can be uploaded via Studio APIs.
SDKData format can be downloaded via Studio APIs.
StudioData format can be used as an external URL in maps.

Geospatial Columns

To perform geospatial analytics or visualization, a dataset must contain one or more columns with geospatial information.

For formats that are not required to contain geospatial information, such as CSV and JSON, the Studio platform looks at columns to determine if any explicit or implicit geospatial data is present:

  • Explicit geospatial data (columns containing longitude/latitude, polygons etc).
  • Implicit geospatial information (columns containing e.g. zip codes or census tracts, H3 indices, etc).

Note that datasets without geospatial information can still be loaded. Such datasets can for instance be joined with other datasets that do contain geospatial columns.

Coordinate Reference Systems

Unless stated otherwise, Studio expects Latitude-Longitude EPSG:4326 -- WGS84 coordinates to be used in all supported file formats, specified using longitude and latitude units in decimal degrees. A third elevation coordinates in meters is also usually acceptable.

For Shapefiles, additional coordinate reference systems are supported. Projection information in the .prj file will be read and coordinates will be converted to EPSG:4326 during import.