You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found this tool very helpful lately, thank you for this, and your other, work on open data and code!
I am using the image upload tool to upload 1453 images, to an image collection asset of monthly time series from January 1901 to December 2021. In some of the uploaded images, I am seeing that the time stamp is not getting set as the CSV specifies.
To help illustrate this issue, I have attached a CSV; it contains the wrong (as reflected in the uploaded image) and right (as specified in the CSV, derived from the year and month in the id_no column) timestamps, for a subset of the timeseries where this issue shows up.
Trailing 0's dropped when the value has more than 12 digits.
But trailing 0's added sometimes too.
How to fix this issue, and would that be on the upload tool or on the EE end?
I don't know Python much, but I nevertheless tried looking through the code to see if I can help troubleshoot this. I spotted some trimming of the system:time_start string based on its length (lines 168-173 here), but not really sure if it has anything to do with this.
The text was updated successfully, but these errors were encountered:
I have found this tool very helpful lately, thank you for this, and your other, work on open data and code!
I am using the image upload tool to upload 1453 images, to an image collection asset of monthly time series from January 1901 to December 2021. In some of the uploaded images, I am seeing that the time stamp is not getting set as the CSV specifies.
To help illustrate this issue, I have attached a CSV; it contains the wrong (as reflected in the uploaded image) and right (as specified in the CSV, derived from the year and month in the id_no column) timestamps, for a subset of the timeseries where this issue shows up.
wrong_timestamps_subset.csv
Trailing 0's dropped when the value has more than 12 digits.
But trailing 0's added sometimes too.
How to fix this issue, and would that be on the upload tool or on the EE end?
I don't know Python much, but I nevertheless tried looking through the code to see if I can help troubleshoot this. I spotted some trimming of the
system:time_start
string based on its length (lines 168-173 here), but not really sure if it has anything to do with this.The text was updated successfully, but these errors were encountered: