-
Notifications
You must be signed in to change notification settings - Fork 2
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
WFS - some remarks #268
Comments
I answer the question I think I can know the answer: I will add soon the Dutch name of species. I will try to do it on Admin panel of production. In this way @niconoe can add it. Absences are not harvested from GBIF so we don't have them. What we still have are observations which are actually management actions, so the species is present but then removed/eradicated. |
Please don't forget to add the scientific (latin) name. Thanks |
@filipmahieu: to answer your last question: the WFS server is also available on the production site, the URL is: https://alert.riparias.be/api/wfs/observations Hopefully I'll find time soon to implement your other remarks. |
Hey @filipmahieu, I've been able to make some progress on this issue today. The results is already visible on https://gbif-alert-demo.thebinaryforest.net/ and will soon be on the RIPARIAS prod site. Changes/answers:
Details about the fields after the update: Can you tell us if this works for you? Also I'd be interested in knowing which fields you actually don't use. I initially included everything but later realised some things should probably be kept internal. But I don't dare removing data, knowing you might use it in your own scripts. |
Ok, I cannot see the changes yet in the WFS's (dev or production). |
Don't worry about 'our scripts' because the automatic download at night downloads it all from scratch. |
Thanks for the feedback, @filipmahieu!
|
We thank you allready for the efforts made to have a WFS! |
Hi @filipmahieu: indeed, we use the "complex fields" possibilities of WFS to provide details about the species and the dataset, apparently this feature is not well supported in QGIS, making things impractical. I'll update the WFS server to avoid this issue. |
Hi, referring to #272 , we'd like to test if the asked not-use of 'complex fields' would solve our issue that the WFS does not work in our automatic download tool. So solving this issue could use another one too here. |
I just added the field and deployed the changes to both servers (test and production). I'll send you the species list by mail immediately. Tell me if all that works for you now! |
We are able now to download each night the data and implement a legend (with speciesid). Thanks. |
On the development-site a (new) wfs was made (see issue 65): https://dev-alert.riparias.be/api/wfs/observations .
We wish to add some remarks:
It is thus stil the development-site. Can there also be created a wfs on the production-site?
The text was updated successfully, but these errors were encountered: