|CSV||Comma Separated Values||Import, Export, ...||Can contain WKT and GeoJSON geometry columns.|
|Shapefile||Esri Shapefile||Import||Multiple files per dataset: |
|glTF||GL Transmission Format||-||Visualize in 3D Layer|
|Zip||Archive format||Import||Contains multiple datasets, or shapefile(s)|
|Excel||Excel Spreadsheets||Microsoft Excel formats, Office Open XML.|
|KML||Keyhole Markup Language||OGC standard based on Google Earth markup|
|GPX||GPS eXchange Format||XML schema for waypoints, tracks and routes from GPS receivers.|
|TCX||Training Center XML||Garmin format, GPS tracks with additional information.|
The following badges are used on the documentation page of each format to indicate which Studio Platform features support that format:
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.
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.
Updated 2 months ago