-
Notifications
You must be signed in to change notification settings - Fork 16
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
capabilities response look like it has wrong counts #84
Comments
It seems like there is something wrong with that dataset particularly. We should take a look at that. |
I happens because all records have the same lat, lon and date. And It is 3 sequence reads:
@MortenHofft Do you expect to have capabilities.total == datset.size? |
The
So probably something is wrong with the map build. |
No the total is the number of points on the map. So records with coordinates that will show. whatever that filter is. I believe it is records with |
The new UAT seems correct, but I haven’t found any significant differences in the code yet
|
This dataset https://www.gbif.org/dataset/3ad913f9-2f86-48c7-b570-3ec9f71acf88
has 1786 records all of which has coordinates without geospatial issues
https://api.gbif.org/v1/occurrence/search?dataset_key=3ad913f9-2f86-48c7-b570-3ec9f71acf88&has_coordinate=true&has_geospatial_issue=false
But the capabilities endpoint tell me there is 1 record in total.
https://api.gbif.org/v2/map/occurrence/density/capabilities.json?datasetKey=3ad913f9-2f86-48c7-b570-3ec9f71acf88
capabilities was last updpated an hour ago. the dataset was last crawled 2 days ago with state:
NOT_MODIFIED
The text was updated successfully, but these errors were encountered: