Thread: Networks API query

Hi Vincent,

As Rob mentioned, some of the information shown on the /networks page is collected from other places, so it probably won't ever be directly exposed in a web service. (One bit in particular is the stations that are part of the network, this comes from the data centers that hold a network's data and FDSN doesn't have direct access to this -- the FDSN data is more on the administrative side.)

We are working on an updated version of the existing web service, which should show more detailed information, but the details are still being worked out. I'm attaching a current draft of the information that might be exposed here -- this is preliminary and subject to change, but it hopefully this provides some sense of what is likely to come.

Cheers,
Adam

On Dec 12, 2022, at 6:21 AM, Rob Casey <rob.casey<at>earthscope.org> wrote:


Hi Fazio-

Sorry for the late reply. I can see one element of confusion from the Web Services page on the FDSN site.

https://www.fdsn.org/ws/

It lists the networks interface by its query interface only, instead of directing users to the doc landing page, which is here.

https://www.fdsn.org/ws/networks/

As you can see, this web service is really only for a high level listing of networks, and doesn't present the rendered set of information that you see in the /networks/detail pages. The FDSN web services were not built for that kind of extraction.

If you are wanting to get the information as-rendered, you're going to have to do some work in creating a web scraper that can process JavaScript rendered material. The source HTML you get back doesn't actually contain much in the way of data as it gets rendered on the fly in your client.

If you're wanting to piece together details from various web service sources, then it's a matter of figuring out what it is you want for detail.

For instance, the FDSN networks listing has a close association to the IRIS Fedcatalog, which can show more detail, including the data center the stations can be found at.

http://service.iris.edu/irisws/fedcatalog/1/query?net=IU&format=text&includeoverlaps=true&nodata=404

As far as source code, we generally do not share out our server-side code as it contains references to internal resources and processes that we want to keep under wraps. We might be able to answer specific questions about the code, though.

Let us know just what metadata you are looking for and we will do our best to help. What in the network metadata do you seek?

Regards,

-Rob

On Dec 11, 2022, at 7:12 PM, Fazio Vincent (via FDSN) <fdsn-general-bounce<at>lists.fdsn.org> wrote:

Hi Marcelo,

Thanks for the information, but I have looked at both the /ws and the /fdsnws interfaces and as far as I can see neither have the detailed network metadata that I can see in "https://www.fdsn.org/networks".

All I can see is a lot of station metadata, but little network metadata. I am happy to be proved wrong.

Do you know where I can find the source code for "https://www.fdsn.org/networks" ?

Cheers,

Vincent.

----------------------
FDSN General Mailing List
Topic home: http://www.fdsn.org/message-center/topic/fdsn-general/ | Unsubscribe: fdsn-general-unsubscribe<at>lists.fdsn.org

Sent from the FDSN Message Center (http://www.fdsn.org/message-center/)
Update subscription preferences at http://www.fdsn.org/account/profile/

Hi Rob & Adam,

Thanks very much for your detailed authoritative replies.

I am interested in creating a detailed ISO19115-3 XML geonetwork (https://www.geonetwork-opensource.org/) catalogue record for each AusPASS (http://auspass.edu.au) network using machine readable interfaces.

I was interested in your source code to see how easy it was for me to contribute code for a machine readable interface, but it looks like you have that task well in hand.

The "example.json" file you sent is exactly what I was hoping use one day.

If I was to suggest an improvement, it would be to add an "ORCID" field for each researcher, so they can be identified more reliably and accurately

e.g.

{
"givenName": "Tyler",
"familyName": "Newton",
"institution": {
"name": "University of Oregon"
},
"ORCID", " https://orcid.org/0000-0002-1560-6553"
}


Any idea of a rough timeframe for the deployment of the improved network level API?

I suppose I'll write a web scaper script to tide me over until the new API is deployed at http://auspass.edu.au ?

Cheers,

Vincent.

Vincent Fazio
Senior Engineer
Minerals  |  CSIRO 
vincent.fazio<at>csiro.au  |  03 9545 8780

-----Original Message-----
From: Rob Casey <rob.casey<at>earthscope.org>
Sent: Tuesday, 13 December 2022 1:21 AM
To: Fazio, Vincent (Mineral Resources, Clayton) <Vincent.Fazio<at>csiro.au>; fdsn-general<at>lists.fdsn.org
Cc: Adam Clark <adam.clark<at>earthscope.org>
Subject: Re: [fdsn-general] Networks API query


Hi Fazio-

Sorry for the late reply. I can see one element of confusion from the Web Services page on the FDSN site.

https://www.fdsn.org/ws/

It lists the networks interface by its query interface only, instead of directing users to the doc landing page, which is here.

https://www.fdsn.org/ws/networks/

As you can see, this web service is really only for a high level listing of networks, and doesn't present the rendered set of information that you see in the /networks/detail pages. The FDSN web services were not built for that kind of extraction.

If you are wanting to get the information as-rendered, you're going to have to do some work in creating a web scraper that can process JavaScript rendered material. The source HTML you get back doesn't actually contain much in the way of data as it gets rendered on the fly in your client.

If you're wanting to piece together details from various web service sources, then it's a matter of figuring out what it is you want for detail.

For instance, the FDSN networks listing has a close association to the IRIS Fedcatalog, which can show more detail, including the data center the stations can be found at.

http://service.iris.edu/irisws/fedcatalog/1/query?net=IU&format=text&includeoverlaps=true&nodata=404

As far as source code, we generally do not share out our server-side code as it contains references to internal resources and processes that we want to keep under wraps. We might be able to answer specific questions about the code, though.

Let us know just what metadata you are looking for and we will do our best to help. What in the network metadata do you seek?

Regards,

-Rob

On Dec 11, 2022, at 7:12 PM, Fazio Vincent (via FDSN) <fdsn-general-bounce<at>lists.fdsn.org> wrote:

Hi Marcelo,

Thanks for the information, but I have looked at both the /ws and the /fdsnws interfaces and as far as I can see neither have the detailed network metadata that I can see in "https://www.fdsn.org/networks".

All I can see is a lot of station metadata, but little network metadata. I am happy to be proved wrong.

Do you know where I can find the source code for "https://www.fdsn.org/networks" ?

Cheers,

Vincent.

----------------------
FDSN General Mailing List
Topic home: http://www.fdsn.org/message-center/topic/fdsn-general/ | Unsubscribe: fdsn-general-unsubscribe<at>lists.fdsn.org

Sent from the FDSN Message Center (http://www.fdsn.org/message-center/)
Update subscription preferences at http://www.fdsn.org/account/profile/