2. StationXML Reference¶
<Network> required¶
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.
Example: <Network code=”IU” startDate=2016-01-27T13:00:00>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
code |
string |
yes |
2-char network code |
code=IU |
startDate |
dateTime |
no |
network start date |
startDate=1988-01-01T00:00:00 |
endDate |
dateTime |
no |
network end date |
endDate=1988-01-01T00:00:00 |
sourceID |
anyURI |
no |
A data source identifier in URI form |
sourceID=’http://some/path’ |
restrictedStatus |
NMTOKEN |
no |
open, closed, partial |
restrictedStatus=open |
alternateCode |
string |
no |
A code used for display or association, alternate to the SEED-compliant code. |
alternateCode=IX |
historicalCode |
string |
no |
historical network code |
historicalCode=IX |
<Description>¶
Description of the Network
type:string
Example: <Description> This is the network description </Description>
<Identifier>¶
A type to document persistent identifiers. Identifier values should be specified without a URI scheme (prefix), instead the identifer type is documented as an attribute.
type:string
Example: <Identifier> identifier </Identifier>
<Comment>¶
Container for a comment or log entry. Corresponds to SEED blockettes 31, 51 and 59.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
id |
CounterType |
no |
An id for this comment |
id=12345 |
subject |
string |
no |
A subject for this comment |
subject=’Routine maintenance’ |
Sample
<Comment id=12345 subject="Routine maintenance">
<Value>This is a comment</Value>
<BeginEffectiveTime></BeginEffectiveTime>
<EndEffectiveTime></EndEffectiveTime>
<Author>
</Author>
</Comment
<Value> required¶
type: string
Example: <Value> The actual comment goes here. </Value>
<BeginEffectiveTime>¶
type: dateTime
Example: <BeginEffectiveTime> 1998-02-27T13:00:00 </BeginEffectiveTime>
<EndEffectiveTime>¶
type: dateTime
Example: <EndEffectiveTime> 2016-01-27T13:00:00 </EndEffectiveTime>
<Author>¶
Representation of a person’s contact information. A person can belong to multiple agencies and have multiple email addresses and phone numbers.
<Name>¶
type:string
Example: <Name> Alfred E. Neuman </Name>
<Agency>¶
type:string
Example: <Agency> Mad Magazine, Inc. </Agency>
<Email>¶
type:string
Example: <Email> a.neuman@gmail.com </Email>
<DataAvailability>¶
A description of time series data availability. This information should be considered. transient and is primarily useful as a guide for generating time series data requests The information for a DataAvailability:Span may be specific to the time range used in a request that resulted in the document or limited to the availability of data withing the request range. These details may or may not be retained when synchronizing metadata between data centers.
<Extent>¶
A type for describing data availability extents, the earliest and latest data available. No. information is included about the continuity of the data is included or implied.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
start |
dateTime |
yes |
extent start date |
start=1988-01-01T00:00:00 |
end |
dateTime |
yes |
extent end date |
end=1988-01-01T00:00:00 |
<Span>¶
A type for describing data availability spans, with variable continuity. The time range described. may be based on the request parameters that generated the document and not necessarily relate to. continuity outside of the range. It may also be a smaller time window than the request depending. on the data characteristics.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
start |
dateTime |
yes |
extent start date |
start=1988-01-01T00:00:00 |
end |
dateTime |
yes |
extent end date |
end=1988-01-01T00:00:00 |
numberSegments |
integer |
yes |
The number of continuous time series segments contained in the specified time range. A value of 1 indicates that the time series is continuous from start to end. |
numberSegments=3 |
maximumTimeTear |
decimal |
no |
The maximum time tear (gap or overlap) in seconds between time series segments in the specified range. |
maximumTimeTear=0.012 |
<Operator>¶
<Agency> required¶
type: string
Example: <Agency> Albuquerque Seismic Lab </Agency>
<Contact>¶
Representation of a person’s contact information. A person can belong to multiple agencies and have multiple email addresses and phone numbers.
<Name>¶
type:string
Example: <Name> Alfred E. Neuman </Name>
<Agency>¶
type:string
Example: <Agency> Mad Magazine, Inc. </Agency>
<Email>¶
type:string
Example: <Email> a.neuman@gmail.com </Email>
<Website>¶
type:anyURI
<TotalNumberStations>¶
<SelectedNumberStations>¶
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <FDSNStationXML xmlns="http://www.fdsn.org/xml/station/1" schemaVersion="1.1"> <Source>IRIS-DMC</Source> <Module>IRIS converter | version: </Module> <ModuleURI>https://seiscode.iris.washington.edu/projects/stationxml-converter/wiki</ModuleURI> <Created>2019-12-14T23:20:56.779Z</Created>
<Station>¶
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.
Example: <Station code=”ANMO”>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
code |
string |
yes |
3-5 char station code |
code=ANMO |
startDate |
dateTime |
no |
network start date |
startDate=1988-01-01T00:00:00 |
endDate |
dateTime |
no |
network end date |
endDate=1988-01-01T00:00:00 |
sourceID |
anyURI |
no |
A data source identifier in URI form |
sourceID=’http://some/path’ |
restrictedStatus |
NMTOKEN |
no |
open, closed, partial |
restrictedStatus=open |
alternateCode |
string |
no |
A code used for display or association, alternate to the SEED-compliant code. |
alternateCode=ANM |
historicalCode |
string |
no |
historical network code |
historicalCode=ALQ |
<Description>¶
Description of the Station
type:string
Example: <Description> This is the station description </Description>
<Identifier>¶
Identifier values should be specified without a URI scheme (prefix), instead the identifer type is documented as an attribute.
type:string
Example: <Identifier> identifier </Identifier>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
type |
string |
no |
Type of identifier |
type=some_type |
<Comment>¶
Container for a comment or log entry. Corresponds to SEED blockettes 31, 51 and 59.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
id |
CounterType |
no |
An id for this comment |
id=12345 |
subject |
string |
no |
A subject for this comment |
subject=’Routine maintenance’ |
Sample
<Comment id=12345 subject="Routine maintenance">
<Value>This is a comment</Value>
<BeginEffectiveTime></BeginEffectiveTime>
<EndEffectiveTime></EndEffectiveTime>
<Author>
</Author>
</Comment
<Value> required¶
type: string
Example: <Value> The actual comment goes here. </Value>
<BeginEffectiveTime>¶
type: dateTime
Example: <BeginEffectiveTime> 1998-02-27T13:00:00 </BeginEffectiveTime>
<EndEffectiveTime>¶
type: dateTime
Example: <EndEffectiveTime> 2016-01-27T13:00:00 </EndEffectiveTime>
<Author>¶
Representation of a person’s contact information. A person can belong to multiple agencies and have multiple email addresses and phone numbers.
<Name>¶
type:string
Example: <Name> Alfred E. Neuman </Name>
<Agency>¶
type:string
Example: <Agency> Mad Magazine, Inc. </Agency>
<Email>¶
type:string
Example: <Email> a.neuman@gmail.com </Email>
<DataAvailability>¶
A description of time series data availability. This information should be considered. transient and is primarily useful as a guide for generating time series data requests The information for a DataAvailability:Span may be specific to the time range used in a request that resulted in the document or limited to the availability of data withing the request range. These details may or may not be retained when synchronizing metadata between data centers.
<Extent>¶
A type for describing data availability extents, the earliest and latest data available. No. information is included about the continuity of the data is included or implied.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
start |
dateTime |
yes |
extent start date |
start=1988-01-01T00:00:00 |
end |
dateTime |
yes |
extent end date |
end=1988-01-01T00:00:00 |
<Span>¶
A type for describing data availability spans, with variable continuity. The time range described. may be based on the request parameters that generated the document and not necessarily relate to. continuity outside of the range. It may also be a smaller time window than the request depending. on the data characteristics.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
start |
dateTime |
yes |
extent start date |
start=1988-01-01T00:00:00 |
end |
dateTime |
yes |
extent end date |
end=1988-01-01T00:00:00 |
numberSegments |
integer |
yes |
The number of continuous time series segments contained in the specified time range. A value of 1 indicates that the time series is continuous from start to end. |
numberSegments=3 |
maximumTimeTear |
decimal |
no |
The maximum time tear (gap or overlap) in seconds between time series segments in the specified range. |
maximumTimeTear=0.012 |
<Operator>¶
<Agency> required¶
type: string
Example: <Agency> Albuquerque Seismic Lab </Agency>
<Contact>¶
Representation of a person’s contact information. A person can belong to multiple agencies and have multiple email addresses and phone numbers.
<Name>¶
type:string
Example: <Name> Alfred E. Neuman </Name>
<Agency>¶
type:string
Example: <Agency> Mad Magazine, Inc. </Agency>
<Email>¶
type:string
Example: <Email> a.neuman@gmail.com </Email>
<Website>¶
type:anyURI
<Latitude> required¶
Station latitude coordinate.
type: double where: -90.0 <= Latitude < 90.0
Example: <Latitude unit=”DEGREES” datum=”WGS84”>34.9459</Latitude>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
|
datum |
NMTOKEN |
no |
datum used |
datum=WGS84 |
<Longitude> required¶
Station longitude coordinate.
type: double where: -180.0 <= Longitude < 180.0
Example: <Longitude unit=”DEGREES” datum=”WGS84”>-106.4572</Longitude>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
|
datum |
NMTOKEN |
no |
datum used |
datum=WGS84 |
<Elevation> required¶
Station elevation
type: double
Example: <Elevation unit=”METERS”>1850.0</Elevation>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
<Site>¶
These fields describe the location of the station using geopolitical entities (country, city, etc.)
<Name> required¶
type:string
Example: <Site> Albuquerque, New Mexico </Site>
<Description>¶
type:string
Example: <Description> A hot and desolate place </Description>
<Town>¶
type:string
Example: <Town> Albuquerque </Town>
<County>¶
type:string
Example: <County> Bernalillo County </County>
<Region>¶
type:string
Example: <Region> Southwest </Region>
<Country>¶
type:string
Example: <Country> U.S.A. </Country>
<WaterLevel>¶
Elevation of the water surface in meters for underwater sites, where 0 is sea level.
type: double
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
<Vault>¶
Description of station vault.
type: string
<Geology>¶
Description of station geology.
type: string
<Equipment>¶
Equipment used by all channels at a station.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
resourceId |
string |
no |
This field contains a string that should serve as a unique resource identifier. This identifier can be interpreted differently depending on the datacenter/software that generated the document. Also, we recommend 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. |
<Type>¶
Type of equipment
type: string
<Description>¶
Description of equipment
type: string
<Manufacturer>¶
Manufacturer of equipment
type: string
<Vendor>¶
Vendor of equipment
type: string
<SerialNumber>¶
Serial number of equipment
type: string
<InstallationDate>¶
Installation date of equipement
type: dateTime
<RemovalDate>¶
Removal date of equipement
type: dateTime
<CalibrationDate>¶
Calibration date of equipement
type: dateTime
<CreationDate>¶
<TerminationDate>¶
<TotalNumberChannels>¶
<SelectedNumberChannels>¶
<Channel>¶
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.
Example: <Station code=”ANMO”>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
code |
string |
yes |
3-5 char station code |
code=ANMO |
startDate |
dateTime |
no |
network start date |
startDate=1988-01-01T00:00:00 |
endDate |
dateTime |
no |
network end date |
endDate=1988-01-01T00:00:00 |
sourceID |
anyURI |
no |
A data source identifier in URI form |
sourceID=’http://some/path’ |
restrictedStatus |
NMTOKEN |
no |
open, closed, partial |
restrictedStatus=open |
alternateCode |
string |
no |
A code used for display or association, alternate to the SEED-compliant code. |
alternateCode=ANM |
historicalCode |
string |
no |
historical network code |
historicalCode=ALQ |
<Description>¶
Description of the Station
type:string
Example: <Description> This is the station description </Description>
<Identifier>¶
Identifier values should be specified without a URI scheme (prefix), instead the identifer type is documented as an attribute.
type:string
Example: <Identifier> identifier </Identifier>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
type |
string |
no |
Type of identifier |
type=some_type |
<Comment>¶
Container for a comment or log entry. Corresponds to SEED blockettes 31, 51 and 59.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
id |
CounterType |
no |
An id for this comment |
id=12345 |
subject |
string |
no |
A subject for this comment |
subject=’Routine maintenance’ |
Sample
<Comment id=12345 subject="Routine maintenance">
<Value>This is a comment</Value>
<BeginEffectiveTime></BeginEffectiveTime>
<EndEffectiveTime></EndEffectiveTime>
<Author>
</Author>
</Comment
<Value> required¶
type: string
Example: <Value> The actual comment goes here. </Value>
<BeginEffectiveTime>¶
type: dateTime
Example: <BeginEffectiveTime> 1998-02-27T13:00:00 </BeginEffectiveTime>
<EndEffectiveTime>¶
type: dateTime
Example: <EndEffectiveTime> 2016-01-27T13:00:00 </EndEffectiveTime>
<Author>¶
Representation of a person’s contact information. A person can belong to multiple agencies and have multiple email addresses and phone numbers.
<Name>¶
type:string
Example: <Name> Alfred E. Neuman </Name>
<Agency>¶
type:string
Example: <Agency> Mad Magazine, Inc. </Agency>
<Email>¶
type:string
Example: <Email> a.neuman@gmail.com </Email>
<DataAvailability>¶
A description of time series data availability. This information should be considered. transient and is primarily useful as a guide for generating time series data requests The information for a DataAvailability:Span may be specific to the time range used in a request that resulted in the document or limited to the availability of data withing the request range. These details may or may not be retained when synchronizing metadata between data centers.
<Extent>¶
A type for describing data availability extents, the earliest and latest data available. No. information is included about the continuity of the data is included or implied.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
start |
dateTime |
yes |
extent start date |
start=1988-01-01T00:00:00 |
end |
dateTime |
yes |
extent end date |
end=1988-01-01T00:00:00 |
<Span>¶
A type for describing data availability spans, with variable continuity. The time range described. may be based on the request parameters that generated the document and not necessarily relate to. continuity outside of the range. It may also be a smaller time window than the request depending. on the data characteristics.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
start |
dateTime |
yes |
extent start date |
start=1988-01-01T00:00:00 |
end |
dateTime |
yes |
extent end date |
end=1988-01-01T00:00:00 |
numberSegments |
integer |
yes |
The number of continuous time series segments contained in the specified time range. A value of 1 indicates that the time series is continuous from start to end. |
numberSegments=3 |
maximumTimeTear |
decimal |
no |
The maximum time tear (gap or overlap) in seconds between time series segments in the specified range. |
maximumTimeTear=0.012 |
<Operator>¶
<Agency> required¶
type: string
Example: <Agency> Albuquerque Seismic Lab </Agency>
<Contact>¶
Representation of a person’s contact information. A person can belong to multiple agencies and have multiple email addresses and phone numbers.
<Name>¶
type:string
Example: <Name> Alfred E. Neuman </Name>
<Agency>¶
type:string
Example: <Agency> Mad Magazine, Inc. </Agency>
<Email>¶
type:string
Example: <Email> a.neuman@gmail.com </Email>
<Website>¶
type:anyURI
<Latitude> required¶
Station latitude coordinate.
type: double where: -90.0 <= Latitude < 90.0
Example: <Latitude unit=”DEGREES” datum=”WGS84”>34.9459</Latitude>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
|
datum |
NMTOKEN |
no |
datum used |
datum=WGS84 |
<Longitude> required¶
Station longitude coordinate.
type: double where: -180.0 <= Longitude < 180.0
Example: <Longitude unit=”DEGREES” datum=”WGS84”>-106.4572</Longitude>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
|
datum |
NMTOKEN |
no |
datum used |
datum=WGS84 |
<Elevation> required¶
Station elevation
type: double
Example: <Elevation unit=”METERS”>1850.0</Elevation>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
<Site>¶
These fields describe the location of the station using geopolitical entities (country, city, etc.)
<Name> required¶
type:string
Example: <Site> Albuquerque, New Mexico </Site>
<Description>¶
type:string
Example: <Description> A hot and desolate place </Description>
<Town>¶
type:string
Example: <Town> Albuquerque </Town>
<County>¶
type:string
Example: <County> Bernalillo County </County>
<Region>¶
type:string
Example: <Region> Southwest </Region>
<Country>¶
type:string
Example: <Country> U.S.A. </Country>
<WaterLevel>¶
Elevation of the water surface in meters for underwater sites, where 0 is sea level.
type: double
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
<Vault>¶
Description of station vault.
type: string
<Geology>¶
Description of station geology.
type: string
<Equipment>¶
Equipment used by all channels at a station.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
resourceId |
string |
no |
This field contains a string that should serve as a unique resource identifier. This identifier can be interpreted differently depending on the datacenter/software that generated the document. Also, we recommend 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. |
<Type>¶
Type of equipment
type: string
<Description>¶
Description of equipment
type: string
<Manufacturer>¶
Manufacturer of equipment
type: string
<Vendor>¶
Vendor of equipment
type: string
<SerialNumber>¶
Serial number of equipment
type: string
<InstallationDate>¶
Installation date of equipement
type: dateTime
<RemovalDate>¶
Removal date of equipement
type: dateTime
<CalibrationDate>¶
Calibration date of equipement
type: dateTime
<CreationDate>¶
<TerminationDate>¶
<TotalNumberChannels>¶
<SelectedNumberChannels>¶
<Response>¶
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.
Example: <Station code=”ANMO”>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
code |
string |
yes |
3-5 char station code |
code=ANMO |
startDate |
dateTime |
no |
network start date |
startDate=1988-01-01T00:00:00 |
endDate |
dateTime |
no |
network end date |
endDate=1988-01-01T00:00:00 |
sourceID |
anyURI |
no |
A data source identifier in URI form |
sourceID=’http://some/path’ |
restrictedStatus |
NMTOKEN |
no |
open, closed, partial |
restrictedStatus=open |
alternateCode |
string |
no |
A code used for display or association, alternate to the SEED-compliant code. |
alternateCode=ANM |
historicalCode |
string |
no |
historical network code |
historicalCode=ALQ |
<Description>¶
Description of the Station
type:string
Example: <Description> This is the station description </Description>
<Identifier>¶
Identifier values should be specified without a URI scheme (prefix), instead the identifer type is documented as an attribute.
type:string
Example: <Identifier> identifier </Identifier>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
type |
string |
no |
Type of identifier |
type=some_type |
<Comment>¶
Container for a comment or log entry. Corresponds to SEED blockettes 31, 51 and 59.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
id |
CounterType |
no |
An id for this comment |
id=12345 |
subject |
string |
no |
A subject for this comment |
subject=’Routine maintenance’ |
Sample
<Comment id=12345 subject="Routine maintenance">
<Value>This is a comment</Value>
<BeginEffectiveTime></BeginEffectiveTime>
<EndEffectiveTime></EndEffectiveTime>
<Author>
</Author>
</Comment
<Value> required¶
type: string
Example: <Value> The actual comment goes here. </Value>
<BeginEffectiveTime>¶
type: dateTime
Example: <BeginEffectiveTime> 1998-02-27T13:00:00 </BeginEffectiveTime>
<EndEffectiveTime>¶
type: dateTime
Example: <EndEffectiveTime> 2016-01-27T13:00:00 </EndEffectiveTime>
<Author>¶
Representation of a person’s contact information. A person can belong to multiple agencies and have multiple email addresses and phone numbers.
<Name>¶
type:string
Example: <Name> Alfred E. Neuman </Name>
<Agency>¶
type:string
Example: <Agency> Mad Magazine, Inc. </Agency>
<Email>¶
type:string
Example: <Email> a.neuman@gmail.com </Email>
<DataAvailability>¶
A description of time series data availability. This information should be considered. transient and is primarily useful as a guide for generating time series data requests The information for a DataAvailability:Span may be specific to the time range used in a request that resulted in the document or limited to the availability of data withing the request range. These details may or may not be retained when synchronizing metadata between data centers.
<Extent>¶
A type for describing data availability extents, the earliest and latest data available. No. information is included about the continuity of the data is included or implied.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
start |
dateTime |
yes |
extent start date |
start=1988-01-01T00:00:00 |
end |
dateTime |
yes |
extent end date |
end=1988-01-01T00:00:00 |
<Span>¶
A type for describing data availability spans, with variable continuity. The time range described. may be based on the request parameters that generated the document and not necessarily relate to. continuity outside of the range. It may also be a smaller time window than the request depending. on the data characteristics.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
start |
dateTime |
yes |
extent start date |
start=1988-01-01T00:00:00 |
end |
dateTime |
yes |
extent end date |
end=1988-01-01T00:00:00 |
numberSegments |
integer |
yes |
The number of continuous time series segments contained in the specified time range. A value of 1 indicates that the time series is continuous from start to end. |
numberSegments=3 |
maximumTimeTear |
decimal |
no |
The maximum time tear (gap or overlap) in seconds between time series segments in the specified range. |
maximumTimeTear=0.012 |
<Operator>¶
<Agency> required¶
type: string
Example: <Agency> Albuquerque Seismic Lab </Agency>
<Contact>¶
Representation of a person’s contact information. A person can belong to multiple agencies and have multiple email addresses and phone numbers.
<Name>¶
type:string
Example: <Name> Alfred E. Neuman </Name>
<Agency>¶
type:string
Example: <Agency> Mad Magazine, Inc. </Agency>
<Email>¶
type:string
Example: <Email> a.neuman@gmail.com </Email>
<Website>¶
type:anyURI
<Latitude> required¶
Station latitude coordinate.
type: double where: -90.0 <= Latitude < 90.0
Example: <Latitude unit=”DEGREES” datum=”WGS84”>34.9459</Latitude>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
|
datum |
NMTOKEN |
no |
datum used |
datum=WGS84 |
<Longitude> required¶
Station longitude coordinate.
type: double where: -180.0 <= Longitude < 180.0
Example: <Longitude unit=”DEGREES” datum=”WGS84”>-106.4572</Longitude>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
|
datum |
NMTOKEN |
no |
datum used |
datum=WGS84 |
<Elevation> required¶
Station elevation
type: double
Example: <Elevation unit=”METERS”>1850.0</Elevation>
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
<Site>¶
These fields describe the location of the station using geopolitical entities (country, city, etc.)
<Name> required¶
type:string
Example: <Site> Albuquerque, New Mexico </Site>
<Description>¶
type:string
Example: <Description> A hot and desolate place </Description>
<Town>¶
type:string
Example: <Town> Albuquerque </Town>
<County>¶
type:string
Example: <County> Bernalillo County </County>
<Region>¶
type:string
Example: <Region> Southwest </Region>
<Country>¶
type:string
Example: <Country> U.S.A. </Country>
<WaterLevel>¶
Elevation of the water surface in meters for underwater sites, where 0 is sea level.
type: double
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
unit |
string |
no |
unit of latitude |
unit=DEGREES |
plusError |
double |
no |
plus error in latitude |
plusError=0.1 |
minusError |
double |
no |
minus error in latitude |
minusError=0.1 |
measurementMethod |
string |
no |
method of measurement |
<Vault>¶
Description of station vault.
type: string
<Geology>¶
Description of station geology.
type: string
<Equipment>¶
Equipment used by all channels at a station.
attribute |
type |
required |
description |
example |
|---|---|---|---|---|
resourceId |
string |
no |
This field contains a string that should serve as a unique resource identifier. This identifier can be interpreted differently depending on the datacenter/software that generated the document. Also, we recommend 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. |
<Type>¶
Type of equipment
type: string
<Description>¶
Description of equipment
type: string
<Manufacturer>¶
Manufacturer of equipment
type: string
<Vendor>¶
Vendor of equipment
type: string
<SerialNumber>¶
Serial number of equipment
type: string
<InstallationDate>¶
Installation date of equipement
type: dateTime
<RemovalDate>¶
Removal date of equipement
type: dateTime
<CalibrationDate>¶
Calibration date of equipement
type: dateTime