Issues

Use EPSG codes, rather than coordinate_system classification, and free text reference_frame, to define the coordinate system.
FDSN/DAS-metadata#50 · opened on Sep 21, 2026
Ensure global uniqueness of cable_id and fiber_id
FDSN/DAS-metadata#49 · opened on Sep 21, 2026
Add fields for: Timing & time quality parameters, cable manufacturer, response calibration, ADC conversion configuration parameters
FDSN/DAS-metadata#48 · opened on Sep 21, 2026
move location (coordinate) uncertainties from channel group to channel level
FDSN/DAS-metadata#47 · opened on Sep 21, 2026
overview_metadata, network_code
FDSN/DAS-metadata#46 · opened on Sep 21, 2026
overview_metadata, country
FDSN/DAS-metadata#45 · opened on Sep 21, 2026
principal_investigator: add (optional) orcid attribute
FDSN/DAS-metadata#44 · opened on Sep 18, 2026
Move firmware_version from interrogator to acquisition
FDSN/DAS-metadata#43 · opened on Sep 18, 2026
Standardize units, rather than indicating them
FDSN/DAS-metadata#42 · opened on Sep 18, 2026
optional FDSN stream identifier for channel
FDSN/DAS-metadata#41 · opened on Sep 18, 2026
coordinate naming
FDSN/DAS-metadata#40 · opened on Sep 18, 2026
Modelling of channel(s) metadata
FDSN/DAS-metadata#39 · opened on Sep 17, 2026
1
Timing accuracy and synchronization information
FDSN/DAS-metadata#28 · opened on May 6, 2026 · Next release
1
Clarification on description
FDSN/DAS-metadata#7 · opened on Nov 14, 2024 · Future consideration
Optical path?
FDSN/DAS-metadata#5 · opened on Nov 14, 2024 · Future consideration
1
Potential new entries for Metadata + other comments/ideas
FDSN/DAS-metadata#3 · opened on Nov 14, 2024 · Future consideration