ISO Quality Scope

From Earth Science Information Partners (ESIP)

How ISO Does It

ISO 19115 includes a Scope object that allows the specification of what elements in a dataset are described by some other object. This scope can be specified using the ScopeCode list, which is required, a spatial and temporal extent (optional), and a Description that provides more detail.

DQ_Scope
+ level: MD_ScopeCode
+ extent [0..1] : EX_Extent
+ levelDescription [0..*] : MD_ScopeDescription

EX_Extent
describes the spatial and temporal extent of the quality section.

MD_ScopeDescription
+ attributes : Set<GF_AttributeType>
+ features : Set<GF_FeatureType>
+ featureInstances : Set<GF_FeatureType>
+ attributeInstances : Set<GF_AttributeType>
+ dataset : CharacterString
+ other : CharacterString

MD_ScopeCode
+ attribute
+ attributeType
+ collectionHardware
+ collectionSession
+ dataset
+ series
+ nonGeographicDataset
+ dimensionGroup
+ feature
+ featureType
+ propertyType
+ fieldSession
+ software
+ service
+ model
+ tile

Where are ScopeCodes?
metadata/hierarchy_level
dataQualityInfo/scope
metadataMaintenance/updateScope

ESIP Response

  • Ken Casey - All datasets we handle are like this. Exploring "Rich Inventory" and want to track results in a structured way, i.e. ISO 19115
  • Deborah Smith - some datasets, currently don't do
  • Jeff Arnfield - particularly with respect to the station metadata we receive / manage
  • Henry - the data quality varies, but we do not say it
  • Daniel Jacob
  • Ed Armstrong - Data quality can vary dramatically. Some users want the "bad" data.
  • Gao Chen, Kleb - NASA LARC - We need both data/measurment uncertainty and measurement consistency.
  • Rudy Husar