Datetimes are a bit tricky; FWS has not been the greatest at handling this in the past. The issue is that while Mongo supports ISODate objects, JSON does not have a standard format for dates. The best policy would probably have been for FWS to use Mongo’s ISODate throughout such that the dates stored would be rich objects that could be converted easily between time zones (by the application). For a mix of reasons, this is not always the case and FWS sometimes includes string representations of UTC time.
You can certainly convert on the application side; FWS does this in its serializers via the “reconstitute_dates” method, which can turn string representations into Python date objects. However, everything is still converted client side.
If there’s any specific change that could be made to help this process, please let me know
On Monday, April 20, 2015 at 11:14:57 AM UTC-7, [email protected] wrote:
Time is off in a weird way when I run work flows.
MongoDB as I understand is UTC only and it does not care about anything else. So it is up to application to adjust for timezone differences.
Mon Apr 20 14:09:48 EDT 2015
same as mongo
Is there anything I can do to get conversion going between UTC and EDT?