I've noticed that since I'm based in Japan, when I grab my audiomoths in the morning for example, and try to upload my files via the uploader, I get told "filename with future date is not permitted". I assume that in 24 hours I will be permitted to upload, since the latest timezones on Earth will then have passed the recording dates, but I thought perhaps this was a technical oversight on the side of Arbimon? Perhaps it should permit timestamps from the furthest advanced timezone on the Earth as opposed to just based on UTC or something?
This project - https://arbimon.org/p/takakuradai-bird-song/overview
As predicted, I was able to upload the files later on in the day. But, as expected, I am again being prevented by the Arbimon Uploader for this next morning’s recordings.
Here is a file that was recorded at 5:30AM (UTC+9, Japan Standard Time) this morning via my audiomoth. It is currently 8:55 AM JST (UTC+9).
For example, my current timezone is UTC+7 (April 25, at 11:55am) and my filename is 20240425_045600 or 20240425_115600. I won't be able to upload my file (see future filename error) but if my filename is 20240425_045300 then I can upload it. It looks like I can upload file with filename 7 hours before the current time. I think this is what happened to the user.
We have to check on how we calculate the current time of each site.
koonchaya
commented
4 months ago
Original post: https://rfcx.slack.com/archives/C03FD1WD02J/p1713792058353759 @carlybatist
File example https://rfcx.slack.com/files/U04HL3HL6JX/F070F4JUM35/20240424_053000.wav
Additional detail
For example, my current timezone is UTC+7 (April 25, at 11:55am) and my filename is 20240425_045600 or 20240425_115600. I won't be able to upload my file (see future filename error) but if my filename is 20240425_045300 then I can upload it. It looks like I can upload file with filename 7 hours before the current time. I think this is what happened to the user. We have to check on how we calculate the current time of each site.