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

Better handling of event_date in occurrence csv #345

Closed
bwakkie opened this issue Apr 4, 2024 · 2 comments
Closed

Better handling of event_date in occurrence csv #345

bwakkie opened this issue Apr 4, 2024 · 2 comments

Comments

@bwakkie
Copy link

bwakkie commented Apr 4, 2024

Can you split the event_date in better parts in the occurrence csv's year, month and day?

e.g.

event_date, event_date_till?

at least adding a year_till month_till and day_till to not lose the rage?

year, year_till
month, month_till
day, day_till
hour, hour_till
minute, minute_till
seconds, seconds_till

@ManonGros
Copy link

@bwakkie Isn't the information in the eventDate field enough?

Note that most of the fields in the GBIF downloads, including the the eventDate and year, month and day fields are defined in the Darwin Core Standard: https://dwc.tdwg.org/terms/. Perhaps it would make sense to suggest the addition of new fields in the framework of the Darwin Core community? https://github.com/tdwg/dwc/issues

@MattBlissett
Copy link
Member

The year, month and day fields are filled in only if the whole range of the eventDate covers a single year, month and/or day. This is working as intended, as specified by Darwin Core.

I don't see the benefit to additional fields, as the information is already present in eventDate.

@MattBlissett MattBlissett closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2024
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