Fix datetime for LPA

[Ben-Hodgkiss]

Overview

We have seen from an LPA a strange occurrence with datetime. The endpoint has the dates formatted as YYYY-MM-DDTHH:MM:SS. This is an accepted date that should be converted. However, before it reaches the python code, it is being converted (perhaps by ogr2ogr) into YYYY/MM/DD HH:MM:SS. This is currently not accepted.

Tech Approach

• Amend digital-land-python and the unit tests to accept this datetime format. @eveleighoj has already created a test in a branch here when we were investigating this.
• Investigate whether this is happening for ogr2ogr conversion and if we can process the dates as a string prior to this conversion.

Acceptance Criteria

• [x] The St Albans tree dataset processes with no "real date" issues.
• [x] Test cases are built to ensure that the ogr2ogr date format is accepted by the pipeline.
• [x] An investigation has been completed into the ogr2ogr conversion to try and have the pipeline process the raw date from the endpoint and not the converted one. This may require new tickets in the backlog.
• [x] @Ben-Hodgkiss is informed once St Albans is working correctly - he can then inform the Providers team that this is fixed.

[ssadhu-sl]

The time formats accepted in the date.py has "%Y/%m/%d %H:%M:%S%z" which expects a timezone offset at the end. But the endpoint provided by LPA has no timezone so the format fit for it would be "%Y/%m/%d %H:%M:%S".

[ssadhu-sl]

very similar issue: https://github.com/OSGeo/gdal/issues/2403