-
Notifications
You must be signed in to change notification settings - Fork 6
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
Comments
Thank you for spotting this issue. We will look into this. |
@jbienkowski and @javiquinte I'm not sure if the problem is in the availability ws implementation or in the metadata used by availability ? |
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). |
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? |
@jbienkowski developped a mechanism that imports this metadata from the station webservice. |
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:
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:
The includerestricted switch is described in FDSN Web Service Specification as follows:
Regards,
Ludek
The text was updated successfully, but these errors were encountered: