Closed jameswilburlewis closed 5 months ago
Thanks! I was curious if this was a design choice, but I believe the micro-second precision was a relic of this function once returning the regular python "datetime" object.
I'm pretty sure everything will be fine if we now have it return nanoseconds. It does look like the unit tests need to be updated though, specifically test_parse_cdfepoch16 fails simply because its more precise now
The newest version of to_datetime has this feature in it, thanks!
Feel free to reopen this though if you're still seeing the warning in 1.3.0
to_datetime() currently returns numpy datetime64 objects with microsecond precision. This causes warnings when passing them to the xarray DataArray constructor. See: https://github.com/MAVENSDC/cdflib/issues/236
Changing to nanosecond precision eliminates the warnings.