← Back to catalogue
Published

Astronomical Observation

vr.wm-spc-003 · wm-spc-003-astronomical-observation

Describe one archive-scoped astronomical observation record, its acquisition evidence, independently identified products and their provenance.

World Models Physical world and living systems PHY.SPC.OBS

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 6 findings · 12 questions

Observation setup How and when the observation was made.

Instrument and pointing

Facility, instrument and target of the exposure.

Facility and instrument

The observatory, telescope, instrument and configuration used.

  1. Which facility, telescope and instrument made the observation?
  2. Which filter, band, mode or spectral setting was used?

Target and time

Pointing, field and timing of the observation.

  1. Which coordinates and field of view were observed, and in which reference frame?
  2. What were the start time, exposure time and time system?
Data products and provenance What was produced and how.

Products and processing

Raw and processed products with their calibration.

Product levels

Raw, calibrated and derived products from the observation.

  1. Which product levels exist, from raw to derived catalogue?
  2. Which pipeline version and calibration files produced each level?

Quality

Conditions and quality flags affecting the data.

  1. Which observing conditions and quality flags are recorded?
  2. Are artefacts such as satellite trails or cosmic rays flagged?
Access and attribution Who may use the data and how it is credited.

Rights and credit

Proprietary period, programme and citation.

Programme and access

The observing programme and its proprietary period.

  1. Which programme and principal investigator does the observation belong to?
  2. When does the proprietary period end and the data become public?

Linked bodies

The celestial bodies identified in the data.

  1. Which catalogued bodies were identified in the observation, and how?
  2. Which publications cite the observation?

Classifiers Filled

Family
World Models
Category
Physical world and living systems
Entry kind
entity
Navigation path
NAV.PHY.SPC.OBS
Domain
PHY.SPC.OBS
Industry
Cross-industry
Tags
astronomicalobservationphy.spc.obs

What it is Filled

An astronomical observation is a recorded measurement of the sky made with a telescope or detector, such as an image, spectrum, time series or event detection, together with its data products and the provenance that explains how they were obtained and processed. It is distinct from the celestial body observed: one body has many observations, and one observation can cover many bodies.

In scope

  • Master observation identity, programme and acquisition context, target assertions and measured coverage
  • Time, spatial and spectral coordinates, measurement qualifiers, quality assessments and product links
  • Calibration and processing provenance, archive lifecycle, access, attribution and authorized projections

Out of scope

  • Celestial-body, observatory, instrument and programme master records; orbital or physical-body models
  • Scheduling or commanding instruments, running pipelines, issuing discovery alerts or autonomously changing archive access
  • Simulation-only products as acquired observations; an entire survey catalogue as one acquisition; instrument-specific numerical calibration algorithms

Why it exists Filled

Describe one archive-scoped astronomical observation record, its acquisition evidence, independently identified products and their provenance.

Distinguishing features Filled

  • It records a measurement event and its products, not the celestial body itself.
  • Provenance from instrument settings to pipeline version is part of the record.
  • Proprietary periods restrict access for a time before data becomes public.
  • Distinct from a satellite mission or programme, which plans and operates the observing facility.

What robots and AI may and may not do Filled

Must not

  • Access or redistribute data during its proprietary period without the principal investigator's permission.
  • Remove provenance or quality flags from products.
  • Announce a discovery or transient on unverified data as confirmed.
  • Alter archived raw data instead of producing new processed versions.

Only with a human decision

  • Reporting a new discovery or transient to the official clearing house.
  • Releasing proprietary data early.

May

  • Search archives and retrieve public observation products with their provenance.
  • Cross-match observations with catalogues of celestial bodies.
  • Report the calibration, pipeline version and quality flags of a product.
  • Cite observations and programmes as the archive requests.

Moral aspects Filled

  • Proprietary periods protect the work of observing teams, while public release serves the wider community.
  • Credit for discoveries depends on accurate provenance and citation.
  • Observing sites often lie on land of significance to local and indigenous communities.

Who is affected

  • Observing teams and principal investigators
  • Archive users and researchers
  • Communities near observatory sites

Owners Filled

Steward

The observatory or mission archive answers for the observation record, its products and its release.

Roles

Archive custodian
Maintain record identity, grouping policy and stewardship authority
Observation contributor
Supply evidenced acquisition and instrument context within delegated scope
Calibration and quality reviewer
Assess product lineage, flags and scientific limitations
Access and records officer
Assess recipient scopes, release exceptions, retention and disposal
Research consumer
Use authorized projections and preserve attribution and limitation notices

Master systems

  • Observatory science archive
  • Virtual observatory registry
  • Observing proposal system

Links to other meta-models Filled

references

  • WM-SPC-002 - Optional qualified body association. Reject subtype inheritance from the registry parent; unidentified fields and calibration acquisitions remain valid.
  • WM-SPC-001 - Optional observing platform or orbit-context reference. Neighbor bindings require boundary and version review; no dynamics or control is imported.

aligned

  • ObsCore 1.1 - Discovery alignment only; field-level mapping and errata verification remain incomplete.
  • FITS 4.0 - Candidate representation and coordinate mapping; this model neither requires all products to be FITS nor claims format conformance.
  • IVOA Provenance 1.0 - Selected entity/activity/input/output concepts; no executable provenance service claim.
  • IVOA Identifiers 2.0 - Preserve qualified dataset identity without making location or DOI mandatory.
  • DataLink 1.1 - Typed link and error projection; advertised operations confer no execution authority.
  • PROV-O 2013 - Conceptual attribution and revision mapping, not scientific truth certification.
  • Characterisation 1.13 - Axis and coverage alignment for applicable products, not a replacement for a catalogue model.

neighbor

  • WM-SPC-002 Celestial Body - Registry parent is a navigation lead, not scientific subtype inheritance. An observation can contain no identified body or many candidate bodies; one body can be linked from many observations.
  • WM-SPC-001 Space Object / Orbit - Spacecraft and orbit references can describe the observing platform or context. Their dynamics and control are outside this record.
  • Observation products and acquisition events - Use separate record, event, dataset and representation identifiers. Composite or reprocessed products are linked through derivation without redefining their input observations.
  • Observing programme and instrument - Reference programme authority and configuration snapshots; no schedule, command interface or equipment ownership is inherited.
  • Simulation and catalogue products - A simulated comparison product may be referenced with its origin explicitly classified. Derived source associations remain assertions and cannot create a confirmed celestial-body master.

parent

  • WM-SPC-002

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • An observation is identified by the archive's observation or dataset identifier together with the facility and programme identifier.
  • Virtual observatory resources carry IVOA identifiers, and products often carry DOIs.
  • FITS headers record the identifiers, instrument and timing of each file.

Direct properties required Filled

  • Exposure time in seconds and start time in a stated time system.
  • Wavelength or frequency band in nanometres, micrometres or hertz.
  • Field of view and pixel scale in arcminutes and arcseconds.
  • Angular resolution or seeing in arcseconds under recorded conditions.
  • Limiting magnitude or flux sensitivity in the stated photometric system.

Recognition required Filled

  • An observation product is recognized by its file format and headers, typically FITS or VOTable, with instrument and pointing metadata.
  • Often confused with a simulated image, an artist's impression or a catalogue derived from many observations.

Capabilities and actions required Filled

  • Observations can be scheduled, executed, calibrated, archived, released and cross-matched.
  • Products can be reprocessed with new pipelines while raw data stays unchanged.

Hazards and failure modes required Filled

  • False detections from instrument artefacts or satellite trails.
  • Misattribution of discoveries when provenance is lost.
  • Premature release of proprietary data.

Standards and interfaces required Filled

  • FITS file format.
  • IVOA ObsCore and Table Access Protocol for archive queries.
  • VOTable for tabular results.

Context of use required Filled

  • Used in astronomy research, survey science, planetary defence and education.
  • Access follows the data policies of each observatory or mission.

Sources Filled

  1. Observation Data Model Core Components and its Implementation in TAP - International Virtual Observatory Alliance
  2. Definition of the Flexible Image Transport System - International Astronomical Union FITS Working Group
  3. IVOA Provenance Data Model - model description - International Virtual Observatory Alliance
  4. IVOA Identifiers - International Virtual Observatory Alliance
  5. IVOA DataLink - International Virtual Observatory Alliance
  6. PROV-O: The PROV Ontology - World Wide Web Consortium
  7. Data Access Policy for ESO Data held in the ESO Science Archive Facility - European Southern Observatory
  8. Data Model for Astronomical DataSet Characterisation - International Virtual Observatory Alliance
  9. Date and Time on the Internet: Timestamps - Internet Engineering Task Force
  10. Definition of the Flexible Image Transport System (FITS), version 4.0 (IAU FITS Working Group)
  11. Observation Data Model Core Components (ObsCore) (International Virtual Observatory Alliance)
  12. IVOA Identifiers (International Virtual Observatory Alliance)

Open questions

  • Complete source HTTP checks, full ObsCore and errata review, source-version checks and applicability review for the chosen archive profile.
  • Develop instrument-specific schemas and validated handling of native time scales, coordinate conversion, calibration, uncertainty and quality vocabularies.
  • Build fixtures for unnamed fields, failed acquisition, multi-observation products, missing lineage, time-scale mismatch, restricted metadata, withdrawn products and lossy export.
  • Restore independent external review before canonical or publishable-draft promotion.
  • Independent second-provider review is absent; local self-audit cannot substitute for it.
  • Direct HTTP source checks are not run because the sandbox blocks them. Browser retrieval is partial, especially ObsCore full text and errata; current versions and profile applicability remain unverified.
  • Nested instance schemas, coordinate transformations, numerical calibration and uncertainty propagation are not implemented.
  • Instrument-specific flags, interferometric and multi-messenger profiles, alert exchange and catalogue schemas require separate work.
  • Executable FITS, ObsTAP, DataLink and provenance conformance plus cross-archive fixtures and versioned neighbor bindings remain incomplete.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-spc-003-astronomical-observation/spec.yaml, ver-cy/world-models/card-supplements/wm-spc-003-astronomical-observation.json