Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process for Getting Miniseed From IRIS and Submitting StationXML to IRIS #31

Open
kkappler opened this issue Mar 31, 2021 · 4 comments
Open
Assignees
Labels
enhancement New feature or request Time Series Actions dealing with time series objects

Comments

@kkappler
Copy link
Collaborator

No description provided.

@kkappler
Copy link
Collaborator Author

kkappler commented Jun 3, 2021

Karl is pulling miniseed data from ROVER with some commands from Tim. These commands yield local mseed files but there are a couple of issues:

  1. In my specific case (PKD) there are some hacks needed for channel codes.
  2. I would like to be able to control where the file lands or have programmatic access to the files that arrive.  I think I need a tutorialand is ready to add it to MTH5

So, lets choose another dataset (Earthscope) and make a dataset summary and then we can take that dataset summary to Tim and get ROVER commands for it, and setup to have programatic access to the resultant files.

@kkappler kkappler transferred this issue from kujaku11/mt_metadata Jun 10, 2021
@kkappler
Copy link
Collaborator Author

@kujaku11 had the question about: "How do the miniseeds arrive when a request spans more than one epoch?" Jared has tested receiving data into MTH5 via miniseed, but his only examples were for continuous data;

@timronan To run some tests on what happens when you request miniseed for data that has a gap.
Also, does the size of the gap matter? Nan-filling? etc.

@kkappler
Copy link
Collaborator Author

The fundamental method to access data_availability and to simultaneously build queries for a run can use this form:

wget "https://service.iris.edu/fdsnws/availability/1/query?format=text&net=BK&sta=PKD&cha=BQ2&starttime=2004-09-25T00:00:00&endtime=2004-09-30T00:00:00&orderby=nslc_time_quality_samplerate&includerestricted=false&merge=samplerate,quality&nodata=404" --output-document rover.txt

Note that the url can be made by:
rover_query_url()

And then we can make
cmd = f'wget "{url}" --output-document rover.txt'
execute_subprocess(cmd)

But we can probably find a python interface that will directly dump the wget output into a dataframe.

@kujaku11
Copy link
Owner

We can also look at Obspy, they have tools to get the StationXML and the miniseed files (client.get_waveforms) for this, the user just needs to know network and station, etc.

@kujaku11 kujaku11 added enhancement New feature or request Time Series Actions dealing with time series objects labels Jun 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Time Series Actions dealing with time series objects
Projects
None yet
Development

No branches or pull requests

2 participants