When all you have is a timestamp datatype, everything works like a timestamp. There are obviously some improvements to me made, like doing all conversions from a fixed reference timezone (it would seem the dates were encoded in GMT+2, are rendered correctly in the portal, and rendered at GMT in the API). Really though, all dates in biodiversity data need complex range representations to capture the messiness of the data. Getting that to the point where it is usable is a huge challenge though.

- Alex

On 11/30/2015 05:37 AM, Roderic Page wrote:
This may be related to http://dev.gbif.org/issues/browse/POR-1508 but it looks like “eventDate” is consistently incorrect in every API call I make, e.g. http://api.gbif.org/v1/occurrence/891423484 returns:

“eventDate”:"2002-04-11T22:00:00.000+0000”

when the verbatim date is 2002-04-12

The web version of the record http://www.gbif.org/occurrence/891423484 has the correct date, together with a time (12:00:00 AM) that seems to be based on no evidence at all (it’s always puzzled me why GBIF reports spuriously precise date and time strings on the web page).

Regards

Rod

---------------------------------------------------------
Roderic Page
Professor of Taxonomy
Institute of Biodiversity, Animal Health and Comparative Medicine
College of Medical, Veterinary and Life Sciences
Graham Kerr Building
University of Glasgow
Glasgow G12 8QQ, UK

Email:  Roderic.Page@glasgow.ac.uk
Tel:  +44 141 330 4778
Skype:  rdmpage
Facebook:  http://www.facebook.com/rdmpage
LinkedIn:  http://uk.linkedin.com/in/rdmpage
Twitter:  http://twitter.com/rdmpage
Blog:  http://iphylo.blogspot.com
ORCID:  http://orcid.org/0000-0002-7101-9767



_______________________________________________
API-users mailing list
API-users@lists.gbif.org
http://lists.gbif.org/mailman/listinfo/api-users