Data Formats

Supported Formats

FileFormatSupportComments
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 SpreadsheetsBetaBetaMicrosoft Excel formats, Office Open XML.
KMLKeyhole Markup LanguageBetaBetaOGC standard based on Google Earth markup
GPXGPS eXchange FormatBetaBetaXML schema for waypoints, tracks and routes from GPS receivers.
TCXTraining Center XMLBetaBetaGarmin format, GPS tracks with additional information.

Feature Matrix

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

BadgeFeature
StudioStudioData format can be imported into Studio.
StudioStudioData format can be exported from Studio.
SDKSDKData format can be uploaded via Studio APIs.
SDKSDKData format can be downloaded via Studio APIs.
StudioStudioData 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.


Sign In