70/100

Moderate evidence

GainPublished recordClimateGood Space

Satellite and Atmospheric Data Fusion for Improved Characterization of Thermodynamic Profiles

Truvace record
TRV-2026-2539raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
398d66c6c043…check it

Abstract This paper presents Total Atmospheric Characterization–Thermodynamics (TAC-Thermo), a global artificial intelligence (AI) data fusion system to improve satellite-retrieved thermodynamic profiles with a focus on data-sparse regions. TAC-Thermo uses available satellite retrievals and numerical weather prediction model output to upscale satellite-retrieved temperature and moisture profiles that can capture thermodynamic features (up to ∼12 km) on sigma vertical coordinate levels (i.e., 1.0–0.2). TAC-Thermo…

The gain

In a validation against radiosonde soundings, the TAC-Thermo AI system had smaller dewpoint temperature errors than NUCAPS and the GFS at every sigma level, and filled in sounding data where radiosondes are absent.

What this doesn’t fix

The gridded product was examined for only a 24-hour period, and its temperature errors were close to, not clearly below, the best NUCAPS and GFS values.

Sources

1 on file
  1. Peer-reviewed2026-10-01

Cite this record

v1

Truvace Impact Record TRV-2026-2539, v1: “Satellite and Atmospheric Data Fusion for Improved Characterization of Thermodynamic Profiles.” Truvace, 2026-11-12. /record/TRV-2026-2539 (accessed on the day you copy it). sha256 398d66c6c0433009…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1398d66c6c043…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2539 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.