Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Availability WS shows restricted stations as open #181

Open
luvec opened this issue Jan 9, 2025 · 5 comments
Open

Availability WS shows restricted stations as open #181

luvec opened this issue Jan 9, 2025 · 5 comments

Comments

@luvec
Copy link

luvec commented Jan 9, 2025

Dear all,

I don't know if the includerestricted switch in the FDSN Availability WS works well. See this case:

All stations from the WB network are restricted:
https://geofon.gfz-potsdam.de/waveform/archive/network.php?ncode=WB

And yes, I cannot download the data:
https://geofon.gfz-potsdam.de/fdsnws/dataselect/1/query?network=WB&station=BUBD&start=2024-12-01T00:00:00&end=2024-12-01T00:01:00&nodata=404
Result:

Error 403: Forbidden
access denied
Usage details are available from /fdsnws/dataselect/1/
Request:
/fdsnws/dataselect/1/query?network=WB&station=BUBD&start=2024-12-01T00:00:00&end=2024-12-01T00:01:00&nodata=404
Request Submitted:
2025-01-09T13:41:34.98561
Service Version:
1.1.1

But the Availability Service is showing that the data is open:
https://geofon.gfz-potsdam.de/fdsnws/availability/1/query?network=WB&station=BUBD&channel=?HZ&includerestricted=false&start=2024-12-01T00:00:00&end=2024-12-01T00:01:00&nodata=404
Result:

#Network Station Location Channel Quality SampleRate Earliest Latest
WB BUBD CHZ D 250.0 2024-12-01T00:00:00.000000Z 2024-12-01T00:01:00.000000Z

The includerestricted switch is described in FDSN Web Service Specification as follows:

If true, all data are reported. If false, only data that can be openly accessed.

Regards,
Ludek

@jschaeff
Copy link
Collaborator

Thank you for spotting this issue. We will look into this.

@jschaeff
Copy link
Collaborator

@jbienkowski and @javiquinte I'm not sure if the problem is in the availability ws implementation or in the metadata used by availability ?

@javiquinte
Copy link
Collaborator

I'm taking a look at that and it is still not clear to me where the error comes from. The metadata is OK. I've been going through the code and cache construction looks OK. (I still haven't checked the cache itself).
I'll let you know as soon as I see something.

@petrrr
Copy link

petrrr commented Jan 16, 2025

From what I understood when looking into the database, it seems that the flag is always set to open, at least in the documents of the collection. I do not think it is possible to get the correct information from the wfcatalog documents and it cannot be determined from harvesting.

Not sure if the web application should determine the correct status?

@jschaeff
Copy link
Collaborator

@jbienkowski developped a mechanism that imports this metadata from the station webservice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants