Slot: Per-Value Uncertainty Column (value_uncertainty_column)

Name of the column carrying per-value uncertainty (e.g. pm_se, tmax_stderr). Its semantics (uncertainty type, units) live in the Uncertainty microschema. Null with reason for products whose per-value uncertainty exists upstream but is not surfaced.

Tier: recommended

Why this slot matters

Products like Daymet ship per-value standard errors that most pipelines silently drop. Without this binding, downstream analyses cannot find or propagate the measurement error attached to each value, and dropped uncertainty is indistinguishable from uncertainty that never existed.

In plain terms

Some datasets include a "plus or minus" column next to each value — an estimate of how far off each number might be. This slot names that column so the uncertainty travels with the data instead of being lost.

URI: envar:slot/value_uncertainty_column

Applicable Classes

Name	Description	Modifies Slot
DataLayout	How the companion data file (CSV / parquet) is laid out and how this record's...	no

Properties

Type and Range

Property	Value
Range	String
Domain Of	DataLayout

Cardinality and Requirements

Property	Value

Examples

Value
tmax_stderr

Identifier and Mapping Information

Annotations

property	value
tier	recommended
justification	Products like Daymet ship per-value standard errors that most pipelines silently drop. Without this binding, downstream analyses cannot find or propagate the measurement error attached to each value, and dropped uncertainty is indistinguishable from uncertainty that never existed.
explanation	Some datasets include a "plus or minus" column next to each value — an estimate of how far off each number might be. This slot names that column so the uncertainty travels with the data instead of being lost.
covered_by	None

Schema Source

• from schema: https://w3id.org/linkml/microschemas/envar

Mappings

Mapping Type	Mapped Value
self	envar:value_uncertainty_column
native	envar:value_uncertainty_column

LinkML Source

name: value_uncertainty_column
annotations:
  tier:
    tag: tier
    value: recommended
  justification:
    tag: justification
    value: Products like Daymet ship per-value standard errors that most pipelines
      silently drop. Without this binding, downstream analyses cannot find or propagate
      the measurement error attached to each value, and dropped uncertainty is indistinguishable
      from uncertainty that never existed.
  explanation:
    tag: explanation
    value: Some datasets include a "plus or minus" column next to each value — an
      estimate of how far off each number might be. This slot names that column so
      the uncertainty travels with the data instead of being lost.
  covered_by:
    tag: covered_by
    annotations:
      omop_gaia:
        tag: omop_gaia
        annotations:
          extent:
            tag: extent
            value: absent
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: No per-value uncertainty column on external_exposure; the OMOP
              stack carries no measurement-error column for the value.
      degauss:
        tag: degauss
        annotations:
          extent:
            tag: extent
            value: absent
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: DeGAUSS's daymet CSV carries the value only, no per-value standard-error
              column.
      amadeus:
        tag: amadeus
        annotations:
          extent:
            tag: extent
            value: absent
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: Amadeus's gridmet_tmmx.csv carries no per-value uncertainty column.
      cher:
        tag: cher
        annotations:
          extent:
            tag: extent
            value: partial
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: table_column_dictionary column tagged Meta value (info about a
              Value column)
          note:
            tag: note
            value: 'C-HER''s Meta value tag could carry a per-value uncertainty column
              referencing its Value column, but none is asserted here. Conservative:
              partial.'
      codata:
        tag: codata
        annotations:
          extent:
            tag: extent
            value: out_of_layer
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: A per-value uncertainty column binding is instance-layer layout,
              outside CODATA's conceptual scope.
description: Name of the column carrying per-value uncertainty (e.g. `pm_se`, `tmax_stderr`).
  Its semantics (uncertainty type, units) live in the Uncertainty microschema. Null
  with reason for products whose per-value uncertainty exists upstream but is not
  surfaced.
title: Per-Value Uncertainty Column
examples:
- value: tmax_stderr
from_schema: https://w3id.org/linkml/microschemas/envar
rank: 1000
domain_of:
- DataLayout
range: string