DocumentationRecipesReferenceChangelog
Log In
Documentation

Uploading Geospatial assets

To import assets into your Geospatial project, you can follow the standard procedures for uploading or synchronizing assets.
Refer to our Managing Assets documentation for a complete guide.

Below are the specifics to keep in mind when working with geospatial data.

Uploading assets

When uploading assets directly, ensure your files meet the format and size requirements for geospatial workflows.

  • Supported file formats:
    Geospatial projects support GeoTIFF-based formats, including .tif, .jp2, and .ntf.

  • Recommended file size:
    Geospatial projects are not restricted to the 1GB limit that applies to standard image projects. However, for optimal performance, we recommend keeping files under 5GB.

  • Multi-layered assets: You can upload multiple files as individual layers of the same asset, allowing you to work with different processing levels or sensor types within a unified labeling interface. To learn how to upload multi-layered assets, refer to our SDK tutorial.

Note: Larger files are supported thanks to dynamic tiling and streaming, but performance may vary based on connection speed and system resources.

Synchronizing assets from a cloud storage bucket

📗

For help configuring cloud storage buckets to load your COG files into the platform, refer to our documentation:

File format requirement:
Image files in your bucket must be in the Cloud Optimized GeoTIFF (COG) format. You can convert a standard GeoTIFF to a COG using GDAL.

COGs allow the viewer to fetch only the visible portions of the image on demand, which is essential for working with large-scale imagery efficiently.

Here’s an example script using gdal_translate with common options for cloud efficiency:

gdal_translate input.tif output_cog.tif \
  -of COG \
  -co COMPRESS=DEFLATE \
  -co LEVEL=9 \
  -co RESAMPLING=AVERAGE \
  -co BLOCKSIZE=512

Explanation:

  • -of COG: Specifies the output format as Cloud Optimized GeoTIFF.
  • -co COMPRESS=DEFLATE: Applies DEFLATE compression to reduce file size.
  • -co LEVEL=9: Sets the maximum compression level (higher is more compressed, but may take longer).
  • -co RESAMPLING=AVERAGE: Specifies how overviews (pyramid layers) are generated; AVERAGE is a good default for continuous data like satellite imagery.
  • -co BLOCKSIZE=512: Sets the tile size for internal tiling (e.g., 512x512 pixels), improving random access and performance in web/cloud environments.