Data

GRACE Level-2 Data Products

Keep data products explicit, versioned, and auditable. This page defines the data vocabulary used by the website and visualization software, from GSM coefficients to gridded EWH and basin-scale TWSA diagnostics.

Level-2 GSM coefficients

Monthly Stokes coefficients from HUST-Grace2024, CSR RL06, GFZ RL06, JPL RL06, or comparable GRACE/GRACE-FO products. The workflow keeps center, release, lmax, month tag, and missing-month status visible.

Correction products

Degree-1 geocenter terms, SLR-based C20/C30 replacement, GIA correction, mean-field baseline removal, and background-field alignment are treated as explicit preprocessing inputs.

Gridded EWH / TWSA products

Corrected and filtered spherical harmonics are synthesized into equivalent-water-height grids for map preview, basin averaging, annual amplitude, semi-annual amplitude, and trend analysis.

Reference and validation data

CSR Mascon, GLDAS-Noah, basin masks, land/ocean masks, coastline buffers, and Hydroweb altimetry are used as independent checks for filtered products.

Product lineage

LayerProductRequired metadata
Raw inputGSM spherical harmonicscenter, release, lmax, month, background model, missing flag
Preprocessed anomalycorrected ΔC/ΔSdegree-1 source, C20/C30 source, GIA model, baseline period
Filtered branchGAUSS / FAN / PnMm / DDK / HSAFfilter family, radius/order, HSAF parameters, product tag
Application productEWH grid and basin TWSA seriesunit, grid spacing, mask, leakage/scaling rule, statistics

Immutable input

Raw Level-2 files and replacement products are read-only. Derived products are written to versioned output folders.

Traceable metadata

Every figure, grid, and basin series should be traceable to the exact configuration and product tag that generated it.

External consistency

Mascon products, hydrological models, and altimetry records are used to check signal behavior after filtering and leakage correction.

Data boundary

This page documents product structure and processing rules. Large raw datasets and derived scientific outputs should stay outside the website repository unless their distribution terms and file-size policy are clear.