You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if we include "clock corrected" and "not clock corrected" data (data quality flags "Q" and "D", respectively) in a SeisComp Data Structure (SDS), they both fall into the same file, which works with fdsnws-dataselect but is not very clear.
Could we take advantage of SDS's 'data type' character to eliminate this problem, by adding 'data type's 'Q' and 'M'? This is legal within the SDS definition and can be used by at least some SDS clients, for example using the sds_type parameter in obspy's client.
But it could only work if these changes are officially declared (so that other uses of this letter are not allowed) and integrated into fdsnws-dataselect. Note that the data_type 'R' is already used for response data.
Any thoughts?
Wayne
The text was updated successfully, but these errors were encountered:
Currently, if we include "clock corrected" and "not clock corrected" data (data quality flags "Q" and "D", respectively) in a SeisComp Data Structure (SDS), they both fall into the same file, which works with
fdsnws-dataselect
but is not very clear.Could we take advantage of SDS's 'data type' character to eliminate this problem, by adding 'data type's 'Q' and 'M'? This is legal within the SDS definition and can be used by at least some SDS clients, for example using the
sds_type
parameter in obspy's client.But it could only work if these changes are officially declared (so that other uses of this letter are not allowed) and integrated into
fdsnws-dataselect
. Note that the data_type 'R' is already used for response data.Any thoughts?
Wayne
The text was updated successfully, but these errors were encountered: