-
Notifications
You must be signed in to change notification settings - Fork 19
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
Query on last data #348
Comments
This is indeed currently not possible. I think this requires extra field(s) in the WFS services, e.g. |
any news on this issue? Maybe something to keep in mind for the next year? |
I propose to start with adding This would already allow answering questions like 'Boringen added since X', or 'Grondwatermonsters with PFAS measurements added since X', but not 'Peilmetingen added since X' (since this is not a separate service, but included in the XML download of the Grondwaterfilter service). |
Is that from the pydov point of view? |
We have history available for all tables in DOV and some of it can be consulted in the web UI too when logged in. These tables is where the timestamp of Regarding the creation date of the XML: the XML is created on the fly when it is requested, so this would not be very useful. |
The field For example to find the most recently added groundwater samples with PFAS observations, you could use something like this: from pydov.search.grondwatermonster import GrondwaterMonsterSearch
from pydov.types.grondwatermonster import GrondwaterMonster
from owslib.fes2 import SortBy, SortProperty, PropertyIsEqualTo
s = GrondwaterMonsterSearch()
return_fields = GrondwaterMonster.get_field_names()
return_fields.append('eerste_invoer')
df = s.search(
query=PropertyIsEqualTo('chemisch_PFAS', 'true'), max_features=10,
return_fields=return_fields,
sort_by=SortBy([SortProperty('eerste_invoer', 'DESC')]))
df = df[df.parametergroep == "Grondwater_chemisch_PFAS"]
|
following up on #346 , it would be useful to query the latest measurement that was added to the data series, for all measured variables. I don't think this is possible with the current backend setup? Would that be something that DOV can elaborate @marleenvd ?
The text was updated successfully, but these errors were encountered: