search

FDSN / OBS-standards

A repository for the discussion an development for Ocean Bottom Seismology standards
1 stars 0 forks source link

Location codes to specify time-shifted data #4

Open joelsimon opened 3 months ago

joelsimon commented 3 months ago

[1] Do we want to use location codes to indicate whether or not data are time corrected (as opposed using, e.g., "Q" and "D" quality flags)?

[2] If location codes are used, what is the convention? Is using 00-49 (00 being the de facto "default" location) to specify time-corrected (as opposed to raw) potentially confusing?

WayneCrawford commented 3 months ago

I personally don't like using location codes for this... I left it in the docs in case there are others who think it is the best available idea.

There is no great solution in miniSEED, but I find a clear protocol for DataQuality codes better. The biggest problem being that SeisComp Data Structure does not distinguish filenames for different dataquality codes, meaning that, if you provide both raw and corrected data, they must be stuffed into the same file at the data center. This is what we do at the Epos-France (ex-RESIF) data center and the FDSN web services are smart enough to provide the highest-level dataquality unless specifically requested otherwise (ArcLink isn't though, I've been told).