This section explains how to create a Raster Layer in Ellipsis Drive and what to expect during processing. A short video walkthrough is available below.
Processing times may range from a few minutes to longer durations depending on dataset size and system load.
Ellipsis Drive processes tasks in a distributed queue. When demand increases, additional compute resources are allocated dynamically to maintain throughput.
Larger datasets are typically processed more efficiently per unit of data due to parallelised processing.
File upload and processing run in the background.
You can continue working while your data is being processed.
Once upload and processing have started, you may close the tab safely. The process will continue on server side.
All items in Ellipsis Drive are referred to as paths.
A path can be:
a folder
a file
a layer
Folders and files behave similarly to a standard file system.
Layers are structured containers for geospatial data and come in three types:
Vector Layer
Stores vector-based spatial data
Raster Layer
Stores raster datasets
Point cloud Layer
Stores point cloud data
Each layer is published as an interoperable web service and can be accessed by authorized users and systems.
Raster Layers support multiple files within a single layer.
There is no practical size limit for a layer.
When multiple raster files are uploaded, a mosaic is automatically created. In cases of overlap, the most recent dataset is prioritised by default.
All files within a Raster Layer must share the same resolution and number of bands to ensure consistent processing.
You can define one or more timestamps within a layer, which is useful for time-series datasets.
For best results, structure raster data into logical layers that represent a single dataset or theme.
Raster Layers support the following formats:
geotiff, img, jpeg, jp2000, gpkg, ecw, grib, netcdf
Learn more
For additional guidance on working with raster data, refer to the Working with raster data section.
Last updated
