Every rendered layer carries the full metadata of the scene behind it. The Metadata section — the first collapsible section of the result panel — lays it out, so you always know exactly what you’re looking at: which acquisition, how cloudy, at what sun angle, on which orbit.
Like the other result-panel sections, Metadata always describes the first active chip — the insight currently rendered on top of the Globe. Change which layer is on top and the fields update to that scene.
Alongside the metadata, this section is also where the run’s Images, opacity and re-run controls live — those are covered in Scenes, Run Cards & Re-runs. Here we focus on the metadata itself.
What’s shown #
The panel lists the instrument and insight, then the scene’s fields. A sensible default set is shown, and you can reveal the rest. The fields fall into a few groups:
Acquisition & identity
- Date, Platform, Constellation, Processing level, Instrument mode, GSD (ground sample distance), Scene ID.
Quality & coverage (as a percentage of the scene)
- Clouds, Coverage (of your AOI), Snow, Water, Vegetation, Moisture, No data.
Sun & viewing geometry (degrees)
- Sun zenith, Sun azimuth, Sun elevation, View azimuth, Off-nadir, Incidence angle.
Radar (SAR) scenes
- Polarizations, Polarization mode, Frequency band, Orbit direction, Range / Azimuth resolution, Range / Azimuth looks.
Spatial reference
- EPSG, Bands, Bounding box, Geometry, Scene center.
Why it matters #
- Sun geometry (azimuth/zenith) is what powers the Hillshadow mask in AOI Data — and it’s why terrain shadows fall where they do in your image.
- Clouds and AOI coverage tell you at a glance whether a scene is worth analyzing before you spend effort on it.
- Orbit direction and the SAR fields matter when you compare radar acquisitions — same-orbit scenes are comparable; mixing ascending and descending isn’t.
Every value here is the scene’s own metadata; it travels with any export you make (turn on Include metadata when exporting to keep it alongside the file).