From 57b7891e75cc5b069954e4545a71c7f78697852e Mon Sep 17 00:00:00 2001 From: Brendan Jurd Date: Fri, 11 Mar 2022 11:51:38 +1100 Subject: unitconvert: round to nearest date when converting to yyyymmdd. This resolves an issue where converting from a low-precision decimalyear to yyyymmdd gave the wrong result, due to mjd_to_yyyymmdd() truncating away the fractional time component. This commit changes the behaviour of mjd_to_yyyymmdd() to round to the nearest date, instead of truncating. Refs #1483 --- docs/source/operations/conversions/unitconvert.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'docs') diff --git a/docs/source/operations/conversions/unitconvert.rst b/docs/source/operations/conversions/unitconvert.rst index f1488d9a..13ca9228 100644 --- a/docs/source/operations/conversions/unitconvert.rst +++ b/docs/source/operations/conversions/unitconvert.rst @@ -158,6 +158,16 @@ Time units In the table below all time units supported by PROJ are listed. + .. note:: + + When converting time units from a date-only format (`yyyymmdd`), PROJ + assumes a time value of 00:00 midnight. When converting time units + to a date-only format, PROJ rounds to the *nearest* date at 00:00 + midnight. That is, any time values less than 12:00 noon will round to + 00:00 on the same day. Time values greater than or equal to 12:00 noon + will round to 00:00 on the following day. + + +--------------+-----------------------------+ | Label | Name | +==============+=============================+ -- cgit v1.2.3