Avoid duplication in request body.

[jpjones76]

Avoid duplication in request body.

[jpjones76]

Thank you for the report. I'm looking into this now.

[jpjones76]

OK, I found the problem. The bad news is that it's definitely an issue with GeoNet. Marine replicated this bug in ObsPy earlier today. The good news is that I know how to fix it. Amazingly enough, my blind guess about the cause is correct:

When GeoNet changes a channel's parameters, they record a startDate attribute for the new XML element, but there's no endDate attribute added to the old element. However, it seems that a channel element with noendDate is considered valid in the time range -∞:+∞; for example, your query for 2016 returns some channel elements with a startDate of November 2017. I did an identical query through their webpage and got exactly the same results.

Workaround: I can add a control loop to SeisIO that retains one unique entry per channel, based on startDate . This might be messy because I need to test each channel ID for uniqueness, then loop over each group of IDs to create an array of endDate values, then retain the element that's correct for the query window.

Do you know anyone at GeoNet? Could you encourage them to add endDate values to their station XML? I ask because it's easy to imagine a "use case" where this breaks research: suppose a program reads station XML until the first match of each channel. That's OK for normal station XML, but would yield Geonet parameters that are outdated and therefore wrong. Now suppose one's research requires correcting to true ground velocity, and the "wrong" parameters include a gain...

(I thought of this because I encountered a very similar "use case" with Win32 data in 2016: JMA, Nagoya University, and HiNet each had their own parameter file for the two JMA stations on Mt. Ontake. No two parameter files agreed. The gain of each seismic channel varied from file to file by ~50%; the gain of each infrasound channel varied by 3-4 orders of magnitude. No one knew which parameters were current.)

I'll add a fix to SeisIO in a few days. At the moment I'm trying to learn why the Julia ecosystem didn't update SeisIO to v0.3.0.

[jpjones76]

Hi, I implemented a rewrite of FDSN_sta_xml tonight that should include a very clean workaround for this problem. Are you still having this issue, or is it now fixed?

[kura-okubo]

Hello, Thank you for updating the module. I will retry the downloading in a couple of days and will reply to you. Best regards,

…

On Jul 17, 2019, at 4:03 AM, Joshua Jones ***@***.***> wrote: Hi, I implemented a rewrite of FDSN_sta_xml tonight that should include a very clean workaround for this problem. Are you still having this issue, or is it now fixed? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#15?email_source=notifications&email_token=AE2LIGKZKZFRUQMIXN6FYJLP73G4LA5CNFSM4HWZDXRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2DMG5Q#issuecomment-512148342>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE2LIGK6JJMLDERMO6Z4BNLP73G4LANCNFSM4HWZDXRA>.