FDSN StationXML schema. Designed as an XML representation of SEED
metadata, the schema maps to the most important and commonly used structures of SEED
2.4. When definitions and usage are underdefined the SEED manual should be referred
to for clarification.
Top-level type for Station XML. Required field are Source (network ID
of the institution sending the message) and one or more Network containers or one or
more Station containers.
Network ID of the institution sending the
message.
Name of the institution sending this
message.
Name of the software module that generated this document.
This is the address of the query that generated the document,
or, if applicable, the address of the software that generated this document.
The schema version compatible with the document.
This type represents the Network layer, all station metadata is
contained within this element. The official name of the network or other descriptive
information can be included in the Description element. The Network can contain 0 or
more Stations.
TotalNumberStations the total number of stations
contained in this network, including inactive or terminated
stations.
SelectedNumberStations the total number of stations
in this network that were selected by the query that produced this
document, even if the stations do not appear in the document. (This
might happen if the user only wants a document that goes contains
only information at the Network level.)
This type represents a Station epoch. It is common to only have a
single station epoch with the station's creation and termination dates as the epoch
start and end dates.
These fields describe the location of the station
using geo-political entities (country, city,
etc.).
Type of vault, e.g. WWSSN, tunnel, transportable
array, etc.
Type of rock and/or geologic
formation.
Equipment used by all channels at a
station.
An operating agency and associated contact persons. If
there multiple operators, each one should be encapsulated within an
Operator tag. Since the Contact element is a generic type that
represents any contact person, it also has its own optional Agency
element.
Datetime (UTC) when the station was first
installed.
Datetime (UTC) when the station was terminated or will
be terminated. A blank value should be assumed to mean that the
station is still active.
Total number of channels recorded at this
station.
Number of channels recorded at this station and
selected by the query that produced this
document.
URI of any type of external report, such as IRIS data
reports or dataless SEED volumes.
Equivalent to SEED blockette 52 and parent element for the related the
response blockettes.
URI of any type of external report, such as data
quality reports.
Datetime (UTC) when the station was first
installed.
Datetime (UTC) when the station was terminated or will
be terminated. A blank value should be assumed to mean that the
station is still active.
Latitude coordinate of this channel's
sensor.
Longitude coordinate of this channel's
sensor.
Elevation of the sensor.
The local depth or overburden of the instrument's
location. For downhole instruments, the depth of the instrument
under the surface ground level. For underground vaults, the distance
from the instrument to the local ground level
above.
Azimuth of the sensor in degrees from north,
clockwise.
Dip of the instrument in degrees, down from
horizontal
The type of data this channel collects. Corresponds to
channel flags in SEED blockette 52. The SEED volume producer could
use the first letter of an Output value as the SEED channel
flag.
The storage format of the recorded data (e.g.
SEED).
A tolerance value, measured in seconds per sample,
used as a threshold for time error detection in data from the
channel.
Complex type for sensitivity and frequency ranges.This complex type
can be used to represent both overall sensitivities and individual stage gains. The
FrequencyRangeGroup is an optional construct that defines a pass band in Hertz (
FrequencyStart and FrequencyEnd) in which the SensitivityValue is valid within the
number of decibels specified in FrequencyDBVariation.
A scalar that, when applied to the data values, converts the
data to different units (e.g. Earth units)
The frequency (in Hertz) at which the Value is
valid.
Variation in decibels within the specified
range.
Sensitivity and frequency ranges. The FrequencyRangeGroup is an
optional construct that defines a pass band in Hertz (FrequencyStart and
FrequencyEnd) in which the SensitivityValue is valid within the number of decibels
specified in FrequencyDBVariation.
The units of the data as input from the perspective
of data acquisition. After correcting data for this response, these
would be the resulting units.
The units of the data as output from the perspective
of data acquisition. These would be the units of the data prior to
correcting for this response.
The frequency range for which the SensitivityValue is
valid within the dB variation specified.
This field contains a string that should serve as a unique
resource identificator. This identificator can be interpreted diferently
depending on the datacenter/software that generated the document. Also, we
recomend to use something like GENERATOR:Meaningful ID. As a common behaviour
equipment with the same ID should contains the same information/be derived from
the same base instruments.
This complex type represents channel response and covers SEED
blockettes 53 to 56.
A choice of response types. There should be one response per
stage.
StageSensitivity is the gain at the stage of the encapsulating
response element and corresponds to SEED blockette 58. In the SEED
convention, stage 0 gain represents the overall sensitivity of the channel.
In this schema, stage 0 gains are allowed but are considered deprecated.
Overall sensitivity should be specified in the InstrumentSensitivity
element.
Stage sequence number. This is used in all the response SEED
blockettes.
Container for log entries.
Container for a comment or log entry. Corresponds to SEED blockettes
31, 51 and 59.
Response: complex poles and zeros. Corresponds to SEED blockette
53.
Response: FIR filter. Corresponds to SEED blockette 61. FIR filters
are also commonly documented using the CoefficientsType element.
Response: coefficients for FIR filter. Laplace transforms or IIR
filters can be expressed using type as well but the PolesAndZerosType should be used
instead. Corresponds to SEED blockette 54.
Response: list of frequency, amplitude and phase values. Corresponds
to SEED blockette 55.
Response: expressed as a polynomial (allows non-linear sensors to be
described). Corresponds to SEED blockette 62. Can be used to describe a stage of
acquisition or a complete system.
Corresponds to SEED blockette 57.
Expressing uncertainties or errors with a positive and a negative
component. Both values should be given as positive integers, but minus_error is
understood to actually be negative.
Representation of floating-point numbers used as
measurements.
A time value in seconds.
Base latitude type. Because of the limitations of schema, defining
this type and then extending it to create the real latitude type is the only way to
restrict values while adding datum as an attribute.
Type for latitude coordinate.
Type for longitude coordinate.
Instrument azimuth, degrees clockwise from North.
Instrument dip in degrees down from horizontal. Together azimuth and
dip describe the direction of the sensitive axis of the instrument.
Extension of FloatType for distances, elevations, and
depths.
This is a group of elements that represent sample rate. If this group
is included, then SampleRate, which is the sample rate in samples per second, is
required. SampleRateRatio, which is expressed as a ratio of number of samples in a
number of seconds, is optional. If both are included, SampleRate should be
considered more definitive.
Sample rate in samples per second.
Sample rate expressed as number of samples in a number of
seconds.
Complex numbers used as poles or zeros in channel
response.
Integers greater than or equal to 0.
Representation of a person's contact information. A person can belong
to multiple agencies and have multiple email addresses and phone
numbers.
Description of a site location using name and optional geo-political
boundaries (country, city, etc.).
The commonly used name of this station, equivalent to the
SEED blockette 50, field 9.
A longer description of the location of this station, e.g.
"NW corner of Yellowstone National Park" or "20 miles west of Highway 40."
The town or city closest to the station.
The state, province, or region of this
site.
This type contains a URI and description for external data that users
may want to reference in StationXML.
A type to document units. Corresponds to SEED blockette
34.
Name of units, e.g. "M/S", "V", "PA".
Description of units, e.g. "Velocity in meters per second",
"Volts", "Pascals".
The BaseFilterType is derived by all filters.
The units of the data as input from the perspective of data
acquisition. After correcting data for this response, these would be the
resulting units.
The units of the data as output from the perspective of data
acquisition. These would be the units of the data prior to correcting for
this response.
Same meaning as Equipment:resourceId.
A name given to this filter.
Instrument sensitivities, or the complete system sensitivity,
can be expressed using either a sensitivity value or a polynomial. The
information can be used to convert raw data to Earth at a specified
frequency or within a range of frequencies.
The total sensitivity for a channel, representing the
complete aquisition system expressed as a scalar. Equivalent to SEED
stage 0 gain with (blockette 58) with the ability to specify a frequency
range.
The total sensitivity for a channel, representing the
complete aquisition system expressed as a polynomial. Equivalent to SEED
stage 0 polynomial (blockette 62).
A base node type for derivation from: Network, Station and Channel
types.
A code used for display or association, alternate to the
SEED-compliant code.
A previously used code if different from the current
code.