GBIF API changes

Tags: #<Tag:0x00007fa104ba93f0> #<Tag:0x00007fa104ba9170>


Hi all rgbif users out there (including pygbif users, if any)

GBIF wants to get feedback on proposed changes to their API with regard to the eventDate field, as well as related fields day, month, and year.

Give any feedback here Or discuss here, and I can relay information over there

There are two questions at hand:


I lean towards making eventDate contain date ranges, which it currently doesn’t. Does anyone have strong objections against this?

day/month/year fields

I vote to get rid of day, month, and year fields, but would anyone not like this? Does anyone use these fields?

definition of eventDate

Another issue is this: That is, how is eventDate defined. Any thoughts on this?


Yes, I agree, I’ve wondered about these fields for a while. I can’t think of any back compatibility issues, though they may exist.
If this change is made Darwin Core should insist on ISO 8601, rather than just recommending it. This is one field where flexibility is no use to anyone.
You didn’t mention dwc:endDayOfYear and dwc:startDayOfYear. Is there a reason to keep these?


Are you saying you want those or you want to get rid of them? Note that this discussion only concerns the API (see

This is strictly related to the response of the API.


I don’t see any reason to keep them. I can’t quite think why they were there in the first place.


@qgroom Again, do you mean remove them from the Darwin Core dump files? Or from the API? Those field are not in the API anyway.