Product latency¶
All products provide daily temporal resolution with observations referenced to local noon conditions.
| Tier | Latency | Description |
|---|---|---|
| Standard | ~4 days | Optimal satellite data ingestion |
| NRT (Near-Real-Time) | ~1 day | Early delivery, superseded by standard data |
| Forecast | ~13-day horizon | Forward-looking estimates from the SOF-D weather model |
Product variants by tier¶
| Product | Standard | NRT | Forecast |
|---|---|---|---|
| D-MSSM (6 km) | d-mssm | d-mssm-nrt | d-mssm-fc |
| D-ESSM (500 m) | d-essm | d-essm-nrt | d-essm-fc |
| D-HSSM (100 m) | d-hssm | d-hssm-nrt | d-hssm-fc |
The feed field in all API responses identifies the data tier: "standard", "nrt", or "fc".
Combined queries¶
Standard, NRT, and forecast tiers can be queried together using the + syntax to create seamless time series. See Combined product queries for details.
Versioning¶
Processing versions follow a vMA.mi scheme in filenames (e.g., v0201) and a vMA.mi.patch scheme in file metadata (e.g., v02.01.98):
Major versions (
MA) indicate substantial algorithm or processing changesMinor versions (
mi) reflect incremental improvements or correctionsPatch numbers appear in metadata attributes (
release_tag,input_data_version) but not in filenames
The version is encoded in every filename and in the release_tag global attribute of NetCDF files.
Further details: Spire’s High-Resolution Soil Moisture Data Now Delivered in Under 24 Hours