Closed timadriaens closed 1 year ago
It's just a question of tradeoff indeed. We could trigger a download starting from 2000 for example. This will reduce the size of the data when we will include more species.l in case it would be a critical problem (see #213 )
As we are going to broaden up the species list, we should not exclude other kind of observations as machine observations.
I am in favour to improve the download query.
yes, I think that is a good idea, it will automatically make the list of datasets shorter and more relevant (focus more on 'living datasets').
Implemented on dev, let's test this!
Thanks @niconoe. It seems we filtered out ~2.8k observations. On dev alert tool:
Data import: #448 -> 57.896 observations Data import: #449 -> 55.118 observations
Yep, please note that for now those datasets still appear in the filters because of #222. But the more I think of it, the more I think we can be a bit more aggressive and actually remove those empty datasets for the system.
Yes, noticed that on the devtools, I think it would be best to remove them (as also people would not be able to select occurrences on those).
Yes, @niconoe, I agree on it. Being a little aggressive is good sometimes 🤣
@niconoe: Is this done? I mean, did you implement https://github.com/riparias/gbif-alert/issues/215#issuecomment-1525598760? We can close this then.
@damianooldoni: I just implemented #222, so we can now close this!
Hi, as this represents an early alert tool, imo, some datasets on gbif with occurrences for Belgium are actually not that relevant (I have not checked them all):