Volcanic ash time stamp - error on landing page?
Closed this issue · 3 comments
problem
The time stamp on the volcanic ash landing page is not the same as the time stamp on the impact report.
Landing page says report on 2017-11-27 was at 12:00
But impact report says 27-Nov-2017 08:00
proposed solution
Time stamp on landing page and report are the same. In this case I believe 0800hrs (Bali Time ) is the correct time.
We just need to have a consensus on this one.
The time shown on landing page is your local time, so it probably seen as in Australia. While on the report it was using WIB (Waktu Indonesia Barat/Western Indonesia Time), so it's not Bali Time.
I can change it, but we should agree first about the behaviour. Did we use WIB for everything? Then we should also enforce user that we use WIB, even if the event is in Bali (Bali is not in WIB zone).
Hi @lucernae
I have made an executive decision (and checked with @RikkiWeber ). This is our preference for handing time zones.
In the form the use should be asked for the event time - this can be in the past or future.
The user should also be asked for the time zone of the event - this will not always be WIB or the user location.
This information must go on the report header and on the landing page and will be used in the file name.
For now the only one using WIB consistently will be Flood realtime - we should still be explicit (ie say what it is).
Event time and event time zone are critical when we have scenarios that will expire.
Implemented on staging.