What NISAR delivers over this AOI — the complete observation inventory for the documented archive query

Zero-assumption rule. Nothing here was pre-selected as "relevant", and no observation is labeled with an application. Q2 lists every NISAR collection returned by the documented CMR query at the archive snapshot shown in the header — all providers, all processing levels — and every granule of each over this AOI with its full radar configuration (zero counts included). Q3 renders every geocoded 2-D layer found inside the opened granules, data and QA alike. Q5 states what does not exist here — that is part of the inventory too. Products that cannot be drawn on a map (raw radar, complex SLC) are shown with the reason — never dropped silently. Product maturity is whatever the archive says (PROVISIONAL / BETA = pre-validation processing). Only after this inventory is reviewed does any question of physical interpretation or comparison to ground measurements begin — deliberately not on this page.

Q1 · Where does NISAR actually observe? — boundary, sites, every opened footprint

Monitoring sites are drawn by status (solid = active, hollow = suspended). Footprints: solid-edged = acquisitions whose pixels are rendered in Q3 (bright = reference date, faint = sample dates); grey dashed = products opened for structure only (Q5 states why their values are not mappable).

Acquisition timeline — every granule date, per collection

One row per collection with data here; every dot is one granule (filled = ascending pass, hollow = descending; hover for date, direction, track).

Q2 · What radar configuration was used? — every acquisition, CMR's own fields

Per collection: every granule with direction (A/D), track, frame, absolute orbit, polarization (frequency A / B), range bandwidth (MHz), and size. These are CMR's structured metadata fields, cross-checked against the granule filename — disagreements would be flagged, none were found.

Q3 · What numerical fields exist in the geocoded pixel grids? — the pixel atlas

For each rasterized product family, several acquisitions were opened (reference = most recent covering the most monitoring sites — every geocoded layer rendered, including processing & calibration grids; sample = dates spread across the archive — measurement grids rendered). Displayed rasters are strided visualizations, not every native pixel — native pixel values are preserved and exposed through the zoom viewer and the reference-pixel inspector. Hover any pixel for its value (and lon/lat). Each layer states its native posting, the displayed stride, the effective displayed resolution, and its no-data fraction; no-data pixels are transparent, never zero. Color is display-scaled only (the 1–99 percentile stretch printed under each ramp) — hover values are the reconstructed physical values; do not use color intensity for quantitative comparison. Click any plot to open the zoom viewer — scroll to zoom down to individual cells (grid lines appear, with the exact ground size of each drawn cell and a live scale bar), see each site's true native-resolution cell footprint drawn to scale, and ▶ animate the layer across the opened dates where the grids share a projection (dates on a different track/projection are listed as not animatable rather than silently warped).

Q4 · What derived and ancillary products exist here?

Q5 · What is UNAVAILABLE here? — absences are part of the inventory

Per-site NISAR reference-pixel inspector

For every monitoring site: the native-resolution NISAR cell whose center is nearest the site's stored reference coordinate — a reference-coordinate probe, not an areal measurement of the DWR site footprint — in every rasterized layer of every opened date: exact value(s), the cell's true ground footprint, and its no-data status. Values are sampled from the full-resolution files, not from the displayed (strided) grids. This is the chain product → layer → pixel → value → date → quality per site.

Full dataset trees — everything inside each opened file

Every dataset in each granule (path · shape · dtype · the file's own units/description; scalar values shown inline). This is the complete answer to "what does this product's file contain" — nothing summarized away.