Skip to main content

Upload Data

Use Upload data to import hyperspectral imagery and its supporting files. Clarity groups recognized files into import packages before it uploads anything.

Import a downloaded package​

  1. On the Files page, select New > Upload data.
  2. Review Target location. Imports default to the active project's root or, without a project, the global root. Select Change to choose another permitted folder.
  3. Drop the downloaded folder into the dialog, or select Add files and add the complete file bundle.
  4. Review every planned package. Resolve packages marked Review or Needs cube inspection and check which source files Clarity will retain or exclude.
  5. Select Upload. The button remains disabled until every planned package is uploadable, the destination is ready, and no destination-name collision or client check blocks the import.

After upload completes, processing continues in the background. The Files row can show Importing… or Importing layers until the image is ready. Review the row if it changes to Import failed or Import cancelled.

Files to include​

Upload the provider bundle as delivered. Sidecars can contain wavelengths, georeferencing, scale factors, or other metadata needed to interpret the image. The planner decides whether each file is used, retained for provenance, or excluded.

ENVI​

Include the ASCII .hdr header and its binary data file. Common data extensions are .raw, .dat, .img, and .hsi; some ENVI data files have no extension. The header and data file normally share a base name.

If the product includes image-geometry (IGM) data, also include its IGM header and data pair.

GeoTIFF​

Include the .tif, .tiff, or .geotiff image and any provider metadata or other sidecars. A metadata file is optional for manual GeoTIFF mapping, but a recognized provider package may need it for reliable interpretation.

HE5 and HDF5 products​

Tanager imports accept .he5 or .h5 products. Include the accompanying files from the provider bundle. If a Tanager metadata JSON accompanies the product, Clarity recognizes it but does not need to upload it because the image file contains the import metadata.

Unknown HE5 or HDF5 structures are not automatically importable. They must match a supported product profile.

NetCDF products​

Clarity can recognize supported NetCDF products with .nc, .nc4, or .cdf extensions. A generic or unknown NetCDF structure is not uploadable unless it matches a supported source profile.

Shapefiles​

Include all components with the same base name. Manual mapping requires .shp, .shx, and .dbf; include .prj when available, along with any other sidecars delivered with the shapefile.

Overlay images​

Manual overlay-image mapping accepts a PNG image and optional metadata.

Read the import plan​

Package status describes whether the package can proceed:

  • Ready: the required assets are present and the package is uploadable.
  • Review: the package needs a mapping or another decision.
  • Needs cube inspection: a multidimensional source needs its cube, variables, or dimensions reviewed.
  • Retained: the planner recognized source material but did not create an image import from it.

Each asset also shows its storage treatment:

  • Used: required to materialize the imported image.
  • Retained or Retain: kept with the source package for provenance or later review.
  • Excluded: not uploaded by default.
  • Not uploadable: cannot be sent through the current plan.

Unsupported or unassigned files do not become managed files merely because they were selected. Check the plan instead of assuming every file in the browser selection will be uploaded.

Source files and validation​

Source-file rows show the filename, size, and retention status. Retain means that the file is kept for provenance or later review; retention alone does not mean its contents are used to calibrate the image. Files excluded by default show a reason when it affects your upload decision.

Some packages can be recognized from filenames and extensions before their raster data is uploaded. Large rasters receive lightweight local checks first; full raster validation runs after upload. Ready means the package can proceed to import, not that calibration or full validation has already completed.

Include the provider's metadata with the imagery. For supported GeoTIFF metadata formats, Clarity reads the XML or JSON contents to identify the source and uses image references in that metadata to match files. Otherwise it uses a matching filename or a single unambiguous image in the same folder. Recognized metadata is an import input, not just a retained sidecar.

Missing, invalid, or ambiguous metadata requires review. Use Map files to assign the correct image and metadata roles or select a supported source. The resolved sensor and file roles are carried into the upload; processing-level classification still runs on the backend.

Repair an incorrect grouping​

Use manual mapping only when automatic grouping is incomplete or incorrect. Choose the matching template, name the import, and assign files to its required and optional roles. For example, an ENVI mapping needs a Header and Data; a shapefile mapping needs .shp, .shx, and .dbf.

Return to the plan after editing the mapping and confirm that the package is Ready before selecting Upload.