14. Metadata#
pycsamt.metadata holds the format-neutral metadata objects that
describe how a transfer function came to be, independently of
whether it is currently stored as EDI, EMTF XML, or an in-memory
TFBundle. A station’s coordinates, the
instrument that recorded it, the channels and orientation that give a
\(2\times2\) impedance matrix physical meaning, who processed it
and with what remote reference, and how good the result actually is
are all scientific facts about the measurement – not serialization
details of one file format. Keeping them in one reusable package
means EDI workflows, the EMTF XML reader/writer, and forward-modelling
priors all share the same classes instead of each format inventing its
own metadata hierarchy.
Use this section when you need to build, inspect, or round-trip any of
these objects directly – constructing a SurveyMeta
for a new campaign, comparing two InstrumentMeta
presets, or reading what a DataQuality
flag actually means. When you only need the effect these objects have
on a concrete workflow, see Site Tools for station-level EDI
and EMTF-XML metadata editing, or EMTF for how
ProvenanceMeta,
SiteLayout, and
OrientationMeta map onto EMTF
XML’s <Provenance>, <SiteLayout>, and <Orientation>
elements. For the complete callable reference, see
pycsamt.metadata.