Fix microsecond date/time parsing #65
Conversation
|
This request will create a complex merge history (below). Can it be simplified? E.g. close this request, check out the current “develop” branch, make the change, then make a pull request?
From: Steven Ring [mailto:notifications@github.com] When using Tile.from_csv_record(record) the parse_datetime() does not capture the microsecond element of the timestamp. This cause problems for downstream processing where applications (e.g. WOfS) rely on the full timestamp as an identifier. The alternative of extracting this info from NBAR filenames is not appealing. The AGDC uses a variety of date/time formats roughly aligned to (but not all compatible with) ISO8601. The proposed function uses a regex to match all formats so far encountered by the author. You can view, comment on, or merge this pull request online at: Commit Summary
File Changes
Patch Links:
— Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks. |
|
Hi Wenjun, I'm happy to do that. The complexity arose because my fork was out of date and I had to merge a cheers On Tue, Jun 9, 2015 at 10:57 AM, Wenjun Wu notifications@github.com wrote:
Steven Ring |
|
Closing to tidy-up history |
When using
Tile.from_csv_record(record)theparse_datetime()does not capture the microsecond element of the timestamp. This cause problems for downstream processing where applications (e.g. WOfS) rely on the full timestamp as an identifier. The alternative of extracting this info from NBAR filenames is not appealing.The AGDC uses a variety of date/time formats roughly aligned to (but not all compatible with) ISO8601. The proposed function uses a regex to match all formats so far encountered by the author.