Open kkappler opened 3 years ago
Will need to go through all methods for add_station, add_run, add_channel ... to test if a new channel wants to be added, if the metadata are the same.
If the metadata is not the same what to do, give the user the ability to update, overwrite, make new
what should be the default (overwrite or update)
@timronan @kkappler We should also move this to mth5/clients/make_mth5
I put a table listing data that I have worked with in the past couple of months which maybe helpful as a template.
Note that when reading the table with pd.read_csv() supplying the argument
parse_dates=['start time (UTC)', 'end time (UTC)']
will make those columns readin as datetime objects, i.e.
df = pd.read_csv(csv_filename, parse_dates=['start time (UTC)', 'end time (UTC)'])
Most of the datasets are NCEDC, but there is an IRIS example as well. It would nice if we could curate these (and others) as test cases and that way when specific issues pop up we can isolate by refering to a test_case table.
Here is some rough pseudocode for a Requested Function:
This is a conceptual sketch of a method that we would want to expand on in future.
There are some classes that could be used to do a lot of this.
Namely: aurora/aurora/sandbox/io_helpers/fdsn_dataset_config.py