Networks API query
Fazio Vincent
I'd like to know more about the 'networks' API. I cannot find the documentation or the source code.
i.e.
https://www.fdsn.org/ws/networks/1/query<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fdsn.org%2Fws%2Fnetworks%2F1%2Fquery&data=05%7C01%7Crobert.pickle%40anu.edu.au%7Cdeadf9607896422270a608daabe13eb4%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638011281728834131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=G%2B%2F5Iv6gMQvanDkfo%2FjdTOJRJcc%2BLYzdo0TlJ3BlVx4%3D&reserved=0>
What are its parameters?
Is there any detailed documentation?
If there isn't any documentation, can you point me to the source code?
Why is the information in:
https://www.fdsn.org/ws/networks/1/query<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fdsn.org%2Fws%2Fnetworks%2F1%2Fquery&data=05%7C01%7Crobert.pickle%40anu.edu.au%7Cdeadf9607896422270a608daabe13eb4%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638011281728834131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=G%2B%2F5Iv6gMQvanDkfo%2FjdTOJRJcc%2BLYzdo0TlJ3BlVx4%3D&reserved=0>
so limited, when there are web pages such as
https://www.fdsn.org/networks/detail/6C_2015/<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fdsn.org%2Fnetworks%2Fdetail%2F6C_2015%2F&data=05%7C01%7Crobert.pickle%40anu.edu.au%7Cdeadf9607896422270a608daabe13eb4%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638011281728834131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vsuaUjxTzI3%2F6h%2FWgeFlokqMCGTPgATfJiozzUcwgo8%3D&reserved=0>
which have much more information??
Is there a machine readable (e.g. JSON) version of
https://www.fdsn.org/networks/detail/6C_2015/<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fdsn.org%2Fnetworks%2Fdetail%2F6C_2015%2F&data=05%7C01%7Crobert.pickle%40anu.edu.au%7Cdeadf9607896422270a608daabe13eb4%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638011281728834131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vsuaUjxTzI3%2F6h%2FWgeFlokqMCGTPgATfJiozzUcwgo8%3D&reserved=0> ?
Cheers,
Vincent.
Vincent Fazio
Senior Engineer
Minerals | CSIRO
vincen...@csiro.au<mailto:vincen...@csiro.au> | 03 9545 8780
Private Bag 10, Clayton South VIC 3169
CSIRO acknowledges the Traditional Owners of the land, sea and waters, of the area that we live and work on across Australia. We acknowledge their continuing connection to their culture and we pay our respects to their Elders past and present.
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.
CSIRO Australia's National Science Agency | csiro.au
Marcelo Belentani de Bianchi
The service you are searching is the station service. Its documentation is
here:
https://fdsn.org/webservices/fdsnws-station-1.1.pdf
The returned output follows the station XML format, with alternative csv
format for basic information.
regards,
Marcelo Bianchi
--
Pesquisador (Docente)
Centro de Sismologia / IAG / USP
http://www.moho.iag.usp.br/ ~ http://www.iag.usp.br/geofisica
Rua do Matão, 1226, office D-211
+55 (11) 9820-10-930 ~ +55 (11) 3091-4743
Em sex., 9 de dez. de 2022 às 10:51, Fazio Vincent (via FDSN) <
fdsn-gene...@lists.fdsn.org> escreveu:
> I am interested in building a metadata profile of some FDSN networks using a script.
>
>
>
> I'd like to know more about the 'networks' API. I cannot find the documentation or the source code.
>
>
>
> i.e.
>
> https://www.fdsn.org/ws/networks/1/query <https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fdsn.org%2Fws%2Fnetworks%2F1%2Fquery&data=05%7C01%7Crobert.pickle%40anu.edu.au%7Cdeadf9607896422270a608daabe13eb4%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638011281728834131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=G%2B%2F5Iv6gMQvanDkfo%2FjdTOJRJcc%2BLYzdo0TlJ3BlVx4%3D&reserved=0>
>
>
>
> What are its parameters?
>
> Is there any detailed documentation?
>
> If there isn't any documentation, can you point me to the source code?
>
>
>
> Why is the information in:
>
>
>
> https://www.fdsn.org/ws/networks/1/query <https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fdsn.org%2Fws%2Fnetworks%2F1%2Fquery&data=05%7C01%7Crobert.pickle%40anu.edu.au%7Cdeadf9607896422270a608daabe13eb4%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638011281728834131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=G%2B%2F5Iv6gMQvanDkfo%2FjdTOJRJcc%2BLYzdo0TlJ3BlVx4%3D&reserved=0>
>
>
>
> so limited, when there are web pages such as
>
>
>
> https://www.fdsn.org/networks/detail/6C_2015/ <https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fdsn.org%2Fnetworks%2Fdetail%2F6C_2015%2F&data=05%7C01%7Crobert.pickle%40anu.edu.au%7Cdeadf9607896422270a608daabe13eb4%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638011281728834131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vsuaUjxTzI3%2F6h%2FWgeFlokqMCGTPgATfJiozzUcwgo8%3D&reserved=0>
>
>
>
> which have much more information??
>
>
>
> Is there a machine readable (e.g. JSON) version of
>
>
>
> https://www.fdsn.org/networks/detail/6C_2015/ <https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fdsn.org%2Fnetworks%2Fdetail%2F6C_2015%2F&data=05%7C01%7Crobert.pickle%40anu.edu.au%7Cdeadf9607896422270a608daabe13eb4%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638011281728834131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vsuaUjxTzI3%2F6h%2FWgeFlokqMCGTPgATfJiozzUcwgo8%3D&reserved=0> ?
>
>
>
>
>
> Cheers,
>
>
>
> Vincent.
>
>
>
>
>
>
>
> *Vincent Fazio*
>
> Senior Engineer
>
> Minerals | CSIRO
>
> *vincen...@csiro.au <vincen...@csiro.au>* | 03 9545 8780
>
> Private Bag 10, Clayton South VIC 3169
>
>
>
> CSIRO acknowledges the Traditional Owners of the land, sea and waters, of
> the area that we live and work on across Australia. We acknowledge their
> continuing connection to their culture and we pay our respects to their
> Elders past and present.
>
>
>
> The information contained in this email may be confidential or privileged.
> Any unauthorised use or disclosure is prohibited. If you have received this
> email in error, please delete it immediately and notify the sender by
> return email. Thank you. To the extent permitted by law, CSIRO does not
> represent, warrant and/or guarantee that the integrity of this
> communication has been maintained or that the communication is free of
> errors, virus, interception or interference.
>
>
>
> *CSIRO *Australia’s National Science Agency | csiro.au
>
>
>
> ----------------------
> FDSN General Mailing List
> Topic home: http://www.fdsn.org/message-center/topic/fdsn-general/ |
> Unsubscribe: fdsn-general...@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/
>
Fazio Vincent
Thank you for the information.
Are you able to answer the second part of my query?
i.e. Is there a machine readable version of web pages such as:
https://www.fdsn.org/networks/detail/6C_2015/ ?
I am looking for detailed information about each network, but this is not provided by your API as described in your StationXML document.
If I use https://www.fdsn.org/ws/networks/1/query all I can see is start_date, end_date, doi, name, fdsn_code - only 5 metadata fields!
But https://www.fdsn.org/networks/detail/6C_2015/ has much more information: description, deployment region, website, operated by etc. etc.
Best regards,
Vincent.
Michael Turnbull
For some time now I have had an FDSN Web Service client application
available at http://cqsrg.org/psn/fdsnws/. I have used this web page for
some years now for personal collection of seismic event waveform data.
Although it has been developed with specific interest in the Australian
broader region, it is generic and can be configured for Worldwide use.
Comments and feedback are welcomed; and, if you find that such a web page
could be of use to you or your organisation, I would be happy to share the
XHTML code with suitably credentialed entities. If anyone is interested in
joint development and improvement please contact me.
Regards
Michael Lloyd Turnbull BAppSc(Distinction) QUT, MAppSc CQU.
Adjunct Research Fellow, CQUniversity Australia (CQU).
Member of the Australian Earthquake Engineering Society (Since 1997).
Foundation Member of the Seismological Association of Australian (SAA)
619 Horsecamp Road
Horse Camp, Qld. 4671
Telephone: (07) 41576538
This email (including any attachments) may contain confidential
and/or legally privileged information and is intended only to be
read or used by the addressee. If you are not the intended
original addressee, any use, distribution, disclosure or copying of this
email is strictly prohibited.
Confidentiality and legal privilege attached to this email (including
any attachments) are not waived or lost by reason of its mistaken
delivery to you. If you have received this email in error, please
delete it and notify us immediately by telephone or email.
Marcelo Belentani de Bianchi
Well, indeed there are two different services to use, the /ws for FDSN
registry information, as documented in this page:
https://www.fdsn.org/datacenters/help/#web-service-api
Also, note that on /ws level, there is /ws/datacenters and /ws/networks
levels,
At each datacenter there is the /fdsnws/ service, that runs on may
different servers around the world, and supports the detailed output as
desired, for example,
https://services.iris.edu/fdsnws/station/1/query?net=BL&format=text
or the full stuff at
https://services.iris.edu/fdsnws/station/1/query?net=BL
for this last service you can define the granulariy of data, from network
to instrumnet response, but probably the level you want is the station,
that would list the stations inside each network with its atrribute.
I guess that you will need to use both of those services to build all
needed information.
regards, Marcelo
i.e. Is there a machine readable version of web pages such as:
>
> https://www.fdsn.org/networks/detail/6C_2015/ ?
>
> I am looking for detailed information about each network, but this is not
> provided by your API as described in your StationXML document.
>
> If I use https://www.fdsn.org/ws/networks/1/query all I can see is
> start_date, end_date, doi, name, fdsn_code - only 5 metadata fields!
>
> But https://www.fdsn.org/networks/detail/6C_2015/ has much more
> information: description, deployment region, website, operated by etc. etc.
>
> Best regards,
>
> Vincent.
>
> ----------------------
> FDSN General Mailing List
>
Fazio Vincent
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.
Rob Casey
Hi Fazio-
Sorry for the late reply. I can see one element of confusion from the Web Services page on the FDSN site.
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
> ----------------------
> FDSN General Mailing List
> Topic home: http://www.fdsn.org/message-center/topic/fdsn-general/ | Unsubscribe: fdsn-general...@lists.fdsn.org
>
Adam Clark
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
Fazio Vincent
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
vincen...@csiro.au | 03 9545 8780