1 / 15

Station Metadata: What do I Need?

Learn why metadata is important for managing seismic data and discover the steps for building metadata for your network and stations. This tutorial uses the example of GSN station II.SUR in South Africa.

dwightw
Download Presentation

Station Metadata: What do I Need?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Station Metadata:What do I Need? Dr. Mary Templeton IRIS Data Management Center Managing Data from Seismic Networks August 20-26, 2017 Pretoria, South Africa

  2. Why is Metadata Important? • To use data, you need to know where and how it was recorded: • x,y,z,t • How do you translate the time series to ground motion? • Direction of motion recorded • Amplitude scaling • Phase shifting • The data format must be understood • Metadata is easiest to record before it’s forgotten

  3. Steps for Building Metadata • Register your network and station names • Networks: http://www.fdsn.org/networks/request/ • You now have the ability to provide or request the FDSN creates a Digital Object Identifier (DOI) for you network • Stations: http://www.isc.ac.uk/registries/registration/ • Create a dataless SEED volume • Enter network information • Enter information for a single station • Optional: Add additional stations using the first as a “clone”

  4. What do I Need?Example: II.SUR.00.BH{12Z} • Network information • FDSN network code (network ID) • Operating institution (network operator)

  5. What do I Need? • Station information • Registered station code (station name) • Station long name (site description) • Station information • Location of the station and it’s sensors • Latitude (degrees from -90 to +90) • Longitude (degrees from -180 to +180) • Elevation (ground surface and sensor in m) • Depth (surface elevation – sensor elevation in m)

  6. What do I Need? • Station information • Sensor wiring convention • Normal: upward ground motion produces a positive Z amplitude; Zdip is -90 (most earthquake sensors) • Reverse: upward ground motion produces a negative Z amplitude; Zdip is +90 (industry geophones) • Sensor channel orientations • Angle from magnetic north to each horizontal channel (azimuth in degrees from 0 to 360)

  7. What do I Need? • Station information • Sample rate • 20 • Sensor long-period corner • 360 s (STS-1) • Sensor gain • 2400 V/m/s (STS-1 nominal gain)

  8. What do I Need? SH? (40 sps) BH? (40 sps) Is the nominal sensor gain larger or smaller than 200 V/m/s? H L SL? (40 sps) B,H,C,F S,E,D,G

  9. What do I Need? • Station information • Instrument response • Sensor • Sensitivity • Poles and zeros • A0 normalization factor • Datalogger • Preamplifier gain • Bit weight (A/D scale factor) • FIR coefficients for your field acquisition settings • other

  10. ORIf your instruments are in the Nominal Response Library…http://ds.iris.edu/NRL/

  11. …you will need • Station information • Instrument response • Sensor • Manufacturer • Model • Other

  12. …you will need • Station information • Instrument response • Datalogger • Manufacturer • Model • Preamplifier gain • Sample rate • Other

  13. What do I Need? • Station information • Optional • Text description of instrumentation • Instrument serial numbers • Comments documenting timing and other data problems

  14. What do I Need? • And Finally…. • Time span (epoch) for which this information is valid (YYYY,JJJ,HH:MM:SS.ffff) • If any of this metadata changes, a new epoch needs to be created with updated metadata • Epochs must not overlap in time - you must close the previous epoch (edit the end time) whenever you add a new epoch for the same channel.

  15. After the Break… …we’ll use metadata for GSN station II.SUR (Sutherland, South Africa) to learn how to create a Dataless SEED volume using the program PDCC.

More Related