Draft of station XML schema. Top-level type for Station XML. Required fields are Source (network ID of the institution sending the message) and 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 message. Station container. Includes one or more epochs. This type represents a station epoch. An organization that does not keep track of station epochs should just include one 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 boundaries. Common name used to refer to this station. Long description of the station's location, e.g. "20 miles west of Highway 40." Type of installation. Type of instrumentation. Type of vault, e.g. WWSSN, tunnel, transportable array, etc. Type of rock and/or geologic formation. Station structure type, as defined in V0. Connector reference orientation or structure/array reference orientation (see V0 definition). Local velocity model or V30 value. Equipment currently used by all channels in 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) the station was created. Datetime (UTC) the station was terminated or will be terminated. A blank value should be assumed to mean that the station is still active indefinitely. Total number of channels recorded at this station. URI of this stations dataless SEED volume. URI of any type of external report, such as IRIS data reports. This container describes a channel and at least one of its epochs. Datetime (UTC) this channel was first created. Datetime (UTC) this channel was terminated or will be terminated. If blank, the channel should be assumed to be active. URI of any type of external report, such as IRIS data reports. Station and network codes used to identify a station. IRIS network code. Alphanumeric station code. Network number, used by some networks. Station number, used by some networks. This complex type describes time windows. It is used as a base type for station and channel epochs. This type contains a URI and description for external data that users may want to reference in Station XML. Covers SEED blockette 52 and the response blockettes. Latitude coordinates of this channel's sensor. Longitude coordinates 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. Sensor's north, east, and vertical offsets in meters. Corresponds to V0 real header parameters 50-52. 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. A tolerance value, measured in seconds per sample, used as a threshold for time error detection in data from the channel. Record length of data from this channel, expressed as an exponent of 2. For example, if the blocklength is 256, use the value 8. Corresponds to V0 integer header parameter 35? Channel gain. Corresponds to SEED blockette 58 for stage 0. Corresponds to SEED real parameter 41. In Volts. Corresponds to V0 real header paramter 23. Full scale sensing capability. Corresponds to V0 real parameter 44. Pre-trigger memory recording time (secs). Corresponds to V0 real header parameter 24. Post-detrigger recording time (secs). Corresponds to V0 real header parameter 25. Datalogger complex type. It extends the equipment type. Covers recorder/datalogger parameters in V0. Total number of channels datalogger can record. Corresponds to V0 integer header parameter 34. Number of channels recorded by this datalogger. Channel response. Covers SEED blockettes 53 to 56. Choose one of these responses. There should be one response per stage. The gain at the stage of the encapsulating response element. Corresponds to SEED blockette 58. Response spectrum values. Corresponds to the spectrum section in the V0 headers. Sa spectrum value at a certain period for 5% damping. Corresponds to V0 real header parameters 70-76. Stage sequence number. This is used in all the response SEED blockettes and in V0 parameter 60. Describing the type of stage. Used in SEED response blockettes. Corresponds to SEED blockette 55. Pass response, containing corner frequency and roll off. Gain and sensitivity values. Corresponds to SEED blockette 58. Container for log entries. Container for a comment or log entry. Complex poles and zeros. Corresponds to SEED blockette 53. Generic response. Corresponds to SEED blockette 56. Corresponds to V0 parameters 60-62 (Filter/processing parameters)? Response of a non-linear sensor. Corresponds to SEED blockette 52. Corresponds to SEED blockette 54. 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 coordinates. Type for longitude coordinates. Instrument azimuth, measured 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. Complex numbers used as poles or zeros in channel response. Representation of a person's contact information. A person can belong to multiple agencies and have multiple email addresses and phone numbers. Laplace transform analog response, in rad/sec. Analog response in Hz. Composite (currently undefined) Digital (Z-transform)