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

Count data 2018 is missing from summer geese gbif dataset #170

Open
SanderDevisscher opened this issue Feb 11, 2020 · 9 comments
Open

Count data 2018 is missing from summer geese gbif dataset #170

SanderDevisscher opened this issue Feb 11, 2020 · 9 comments
Assignees

Comments

@SanderDevisscher
Copy link

https://www.gbif.org/dataset/2b2bf993-fc91-4d29-ae0b-9940b97e3232

@SanderDevisscher
Copy link
Author

The data is present in Recorder => update script should be run

@peterdesmet
Copy link
Member

@DimEvil can you tackle this?

@DimEvil
Copy link
Contributor

DimEvil commented Mar 5, 2020

I don't see the problem. There are counts from year=2018
Last publication: 2019-10-15
Was the import of the data correct? I notice many 0-counts
@SanderDevisscher

@SanderDevisscher
Copy link
Author

@DimEvil in recorder zitten duidelijk meer dan 44 occurences

@SanderDevisscher
Copy link
Author

SanderDevisscher commented Mar 5, 2020

Was the import of the data correct? I notice many 0-counts

Many 0-counts is to be expected with simultaantelling. The observers get a list of 12 species on which the oberserver needs to pay extra attention. Species not observed in an area creates a 0-count.

@SanderDevisscher
Copy link
Author

I checked in recorder and in the INBO - zomerganzen survey there are 280 occurences with at least 1 individual counted during simultaantelling. So somewhere something goes wrong!!

@SanderDevisscher
Copy link
Author

SanderDevisscher commented Mar 6, 2020

Last publication: 2019-10-15

Data of counts were uploaded into recorder the 29th of October.

@DimEvil
Copy link
Contributor

DimEvil commented Mar 13, 2020

SPATIAL_REF which is published as verbatimLatitude and or verbatimLongitude is not always in the same format recorded in Recorder.
This needs to be correct before we can publish the data, because this value is (in Lambert) is used to check if the data was recorded in Belgium or the Netherlands.
Simple fix: we also publish the data originating from the netherlands
Other fix: make sure SPATIAL_REF is consistent (in Lambert) in the whole dataset.

@SanderDevisscher
Copy link
Author

SanderDevisscher commented Mar 13, 2020

Other fix: make sure SPATIAL_REF is consistent (in Lambert) in the whole dataset.

I checked, they are in the frontend

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

3 participants