Sensors and RGB defaults
Associate imagery with its acquisition instrument to apply consistent, sensor-specific RGB defaults. Review imported sensor identity, adjust an association when needed, and choose defaults suited to the instrument's bands.
The sensor-aware import and RGB defaults described here are part of the 0.100 release candidate. Controls depend on your permissions and environment.
Review an imported sensor
Include provider metadata when uploading imagery. For ENVI,
an explicit sensor type can identify a configured sensor by its import name.
An unrecognized explicit name can create a sensor record. Images without a
declared sensor remain unassigned; Clarity does not identify their sensor from
band count or wavelength shape alone.
Select the image source in Explorer and open Inspector > Details > Sensor. Review the association and choose the correct sensor when needed. Use Manage sensors beside that field to inspect records. The display name is the user-facing label; the import name identifies matching source metadata.
Understand RGB defaults
New RGB generation uses the available default in this order:
- Sensor default.
- Tenant default when the sensor inherits it.
- Platform default when the tenant inherits it.
Sensor association identifies the instrument; calibration and processing level come from the image's data and provenance. Defaults must be compatible with the input's bands and wavelengths. Inspect the resolved preset and channels in RGB Explorer instead of assuming every image from a sensor has identical coverage.
Tenant administrators can change Tenant default and Sensor default in the sensor's RGB defaults controls. Other accounts see them as read-only. Compare RGB approaches uses an assigned image to show examples; selecting an example is separate from changing the default.
Changing a default guides subsequent generation. Review existing saved composites separately rather than expecting automatic regeneration.