A verified data state is the processing state of a dataset that has passed through a verification process.1
SWEET, the ontology that supplies the term, declares it a subclass of its generic data state and links it to a verification process through the had-process relation.1 The ontology gives no definition text, and its own label carries the spelling “verifed”.1
Earth observation practice separates two neighbouring ideas, calibration and validation. CEOS defines validation as the process of assessing by independent means the quality of the data provided, and its working group exists to secure long-term confidence in the accuracy and quality of Earth observation data and products.23 A NASA assessment framework separately speaks of verifying that mission performance is consistent with the sensor’s stated performance.4
Verified is therefore a statement about what check a dataset has undergone, not a guarantee of correctness. The retained sources do not establish that SWEET’s verification process is the same as CEOS validation, nor which agency tags products as verified, and they give no criteria for granting the state.14
Footnotes
-
ESIP SWEET, “stateDataProcessing.ttl”. https://raw.githubusercontent.com/ESIPFed/sweet/master/src/stateDataProcessing.ttl ↩ ↩2 ↩3 ↩4
-
FAO, “VI. Calibration and Validation of Space-Based Observations”. https://www.fao.org/4/ac654e/ac654e08.htm ↩
-
CEOS, “WGCV”. https://ceos.org/ourwork/workinggroups/wgcv/ ↩
-
NASA, “Joint Earth Observation Mission Quality Assessment Framework Optical Guidelines”. https://science.nasa.gov/wp-content/uploads/2026/05/joint-optical-guidelines-jul2025-signed.pdf?emrc=976ba4 ↩ ↩2