data availability in StationXML

[Philip Crotwell]

Is it worth expanding the data availability in the next StationXML to
include multiple data centers? For example, suppose:
dataCenterA
has metadata for all of network XX
has waveforms for station XX.AAA but not XX.BBB
has information of data availability for station XX.BBB at dataCenterB

dataCenterB
has waveforms for station XX.BBB

Then it would be useful to the client when getting metadata about network
XX from dataCenterA to learn about the availability of waveforms at
dataCenterB for XX.BBB.

Perhaps DataAvailabilityType should be expanded to include a service
reference, maybe as an xlink:href attribute? Their can already be multiple
DataAvailability elements allowing multiple datacenters.

thanks
Philip

[Stephane Zuzlewski]

Maintaining inventory information for other data centers sounds like a
complicated proposition ...

Stephane

On 8/5/15 12:32 PM, Philip Crotwell wrote:
> Hi

> ----------------------
> FDSN Working Group II (http://www.fdsn.org/message-center/topic/fdsn-wg2-data/)
>
> Sent via IRIS Message Center (http://www.fdsn.org/message-center/)
> Update subscription preferences at http://www.fdsn.org/account/profile/

--
------------------------------------------------------------------
Stephane Zuzlewski University of California, Berkeley
step...@seismo.berkeley.edu Berkeley Seismological Laboratory
Office: 510-664-9029 (Thu) 215 McCone Hall # 4760
Fax: 510-643-5811 Berkeley, CA 94720-4760
Remote: 209-724-9540 (Mon,Tue,Wed,Fri)

[Chad Trabant]

> On Aug 5, 2015, at 12:32 PM, Philip Crotwell <crot...@seis.sc.edu> wrote:
>
> Hi
>
> Is it worth expanding the data availability in the next StationXML to include multiple data centers? For example, suppose:

Not a bad idea from the user's perspective but this would require any given data center to know the availability at other centers that have the data. So far there is not much exchange of that information.

While I'm a supporter of having data availability noted in StationXML, more detailed time series availability probably belongs elsewhere. I think this is a feature that a future FDSN federation system should address.

Chad

[Chad Trabant]

The IRIS Federator does not know about actual time series availability, only metadata.

It would be great it more data centers (beyond the DMC and NCEDC) would include availability information in their StationXML and also support the 'matchtimeseries' parameter. These features would be useful for users but also for things like federation systems built on top of the station service. Even just the data extents would be useful. But, alas, many implementations do not support such reporting.

Chad

> On Aug 5, 2015, at 12:57 PM, Philip Crotwell <crot...@seis.sc.edu> wrote:
>
> Complicated, yes, but already being done by the IRIS fedcatalog service I think.
> http://service.iris.edu/irisws/fedcatalog/1/ <http://service.iris.edu/irisws/fedcatalog/1/>
>
> There would be no requirement that the output of one datacenter include availability for another, but would allow it.
>
> Philip

>
>
> On Wed, Aug 5, 2015 at 3:40 PM, Stephane Zuzlewski <step...@seismo.berkeley.edu <mailto:step...@seismo.berkeley.edu>> wrote:
>
> Maintaining inventory information for other data centers sounds like a complicated proposition ...
>
>
> Stephane
>
>
> On 8/5/15 12:32 PM, Philip Crotwell wrote:
>> Hi
>>
>> Is it worth expanding the data availability in the next StationXML to include multiple data centers? For example, suppose:
>> dataCenterA
>> has metadata for all of network XX
>> has waveforms for station XX.AAA but not XX.BBB
>> has information of data availability for station XX.BBB at dataCenterB
>>
>> dataCenterB
>> has waveforms for station XX.BBB
>>
>> Then it would be useful to the client when getting metadata about network XX from dataCenterA to learn about the availability of waveforms at dataCenterB for XX.BBB.
>>
>> Perhaps DataAvailabilityType should be expanded to include a service reference, maybe as an xlink:href attribute? Their can already be multiple DataAvailability elements allowing multiple datacenters.
>>
>> thanks
>> Philip
>>
>>
>> ----------------------

>> FDSN Working Group II (http://www.fdsn.org/message-center/topic/fdsn-wg2-data/ <http://www.fdsn.org/message-center/topic/fdsn-wg2-data/>)
>>
>> Sent via IRIS Message Center (http://www.fdsn.org/message-center/ <http://www.fdsn.org/message-center/>)
>> Update subscription preferences at http://www.fdsn.org/account/profile/ <http://www.fdsn.org/account/profile/>

>
> --
> ------------------------------------------------------------------
> Stephane Zuzlewski University of California, Berkeley

> step...@seismo.berkeley.edu <mailto:step...@seismo.berkeley.edu> Berkeley Seismological Laboratory
> Office: 510-664-9029 <tel:510-664-9029> (Thu) 215 McCone Hall # 4760
> Fax: 510-643-5811 <tel:510-643-5811> Berkeley, CA 94720-4760
> Remote: 209-724-9540 <tel:209-724-9540> (Mon,Tue,Wed,Fri)

[Chad Trabant]

Personally I have always interpreted the DataAvailabilty part as specific to the data center that generated the document, meaning that the data would be available from that same center's fdsnws-dataselect service.

In the documentation of that DataAvailabilty schema it says that the information should be considered transient and that the details may or may not be retained when synchronizing metadata between centers.

Chad

> On Aug 5, 2015, at 2:03 PM, Philip Crotwell <crot...@seis.sc.edu> wrote:
>
>
> OK, scratch that idea.
>
> Just to be clear, if a StationXML document comes from
> http://service.example.org/fdsnws/station/1/ <http://service.example.org/fdsnws/station/1/>
> then is it required that all DataAvailability elements must correspond to
> http://service.example.org/fdsnws/dataselect/1/ <http://service.example.org/fdsnws/dataselect/1/>
> or does it just mean that example.org <http://example.org/> somehow makes that data available?
>
> thanks

> Philip
>
>
> On Wed, Aug 5, 2015 at 4:08 PM, Chad Trabant <ch...@iris.washington.edu <mailto:ch...@iris.washington.edu>> wrote:
>
> The IRIS Federator does not know about actual time series availability, only metadata.
>
> It would be great it more data centers (beyond the DMC and NCEDC) would include availability information in their StationXML and also support the 'matchtimeseries' parameter. These features would be useful for users but also for things like federation systems built on top of the station service. Even just the data extents would be useful. But, alas, many implementations do not support such reporting.
>
> Chad
>

[Philip Crotwell]

[Philip Crotwell]

Complicated, yes, but already being done by the IRIS fedcatalog service I
think.
http://service.iris.edu/irisws/fedcatalog/1/

There would be no requirement that the output of one datacenter include

availability for another, but would allow it.

Philip

On Wed, Aug 5, 2015 at 3:40 PM, Stephane Zuzlewski <

step...@seismo.berkeley.edu> wrote:

> Stephane Zuzlewski University of California, Berkeley...@seismo.berkeley.edu Berkeley Seismological Laboratory

[Philip Crotwell]

OK, scratch that idea.

Just to be clear, if a StationXML document comes from
http://service.example.org/fdsnws/station/1/

then is it required that all DataAvailability elements must correspond to
http://service.example.org/fdsnws/dataselect/1/

or does it just mean that example.org somehow makes that data available?

thanks
Philip

On Wed, Aug 5, 2015 at 4:08 PM, Chad Trabant <ch...@iris.washington.edu>

wrote:

>
> The IRIS Federator does not know about actual time series availability,
> only metadata.
>
> It would be great it more data centers (beyond the DMC and NCEDC) would
> include availability information in their StationXML and also support the
> 'matchtimeseries' parameter. These features would be useful for users but
> also for things like federation systems built on top of the station
> service. Even just the data extents would be useful. But, alas, many
> implementations do not support such reporting.
>
> Chad
>
> On Aug 5, 2015, at 12:57 PM, Philip Crotwell <crot...@seis.sc.edu> wrote:
>
> Complicated, yes, but already being done by the IRIS fedcatalog service I
> think.
> http://service.iris.edu/irisws/fedcatalog/1/
>

> There would be no requirement that the output of one datacenter include
> availability for another, but would allow it.
>
> Philip
>
>
> On Wed, Aug 5, 2015 at 3:40 PM, Stephane Zuzlewski <

> step...@seismo.berkeley.edu> wrote:
>
>>
>> Maintaining inventory information for other data centers sounds like a
>> complicated proposition ...
>>
>>
>> Stephane
>>
>>
>> On 8/5/15 12:32 PM, Philip Crotwell wrote:
>>
>> Hi
>>
>> Is it worth expanding the data availability in the next StationXML to
>> include multiple data centers? For example, suppose:
>> dataCenterA
>> has metadata for all of network XX
>> has waveforms for station XX.AAA but not XX.BBB
>> has information of data availability for station XX.BBB at dataCenterB
>>
>> dataCenterB
>> has waveforms for station XX.BBB
>>
>> Then it would be useful to the client when getting metadata about network
>> XX from dataCenterA to learn about the availability of waveforms at
>> dataCenterB for XX.BBB.
>>
>> Perhaps DataAvailabilityType should be expanded to include a service
>> reference, maybe as an xlink:href attribute? Their can already be multiple
>> DataAvailability elements allowing multiple datacenters.
>>
>> thanks
>> Philip
>>
>>
>> ----------------------

>> FDSN Working Group II (http://www.fdsn.org/message-center/topic/fdsn-wg2-data/)
>>
>> Sent via IRIS Message Center (http://www.fdsn.org/message-center/)
>> Update subscription preferences at http://www.fdsn.org/account/profile/
>>
>>

>> --
>> ------------------------------------------------------------------
>> Stephane Zuzlewski University of California, Berkeley...@seismo.berkeley.edu Berkeley Seismological Laboratory
>> Office: 510-664-9029 (Thu) 215 McCone Hall # 4760
>> Fax: 510-643-5811 Berkeley, CA 94720-4760
>> Remote: 209-724-9540 (Mon,Tue,Wed,Fri)

>>
>>
>
> ----------------------
> FDSN Working Group II (
> http://www.fdsn.org/message-center/topic/fdsn-wg2-data/)
>
> Sent via IRIS Message Center (http://www.fdsn.org/message-center/)
> Update subscription preferences at http://www.fdsn.org/account/profile/
>
>
>
>

> ----------------------
> FDSN Working Group II (