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 will need to add some more tests in the core library to figure out what is causing some date time objects to be created without a timezone, but I've made a change to the JSON formatter that should fix this problem's symptom for the end-user.
Expectation
start_time.dt
andend_time.dt
is always formatted in the correct ISO 8601 formatResult
The format differs from location to location.
EBBR
https://avwx.rest/api/taf/EBBR
Raw TAF:
EBBR 050501Z 0506/0612 06011KT CAVOK
ELLX
https://avwx.rest/api/taf/ELLX
Raw TAF:
ELLX 050500Z 0506/0612 04010KT CAVOK
It becomes especially difficult when this time has to be parsed for different weather stations. Tools like Moment.js fail.
Furthermore, the notation for EBBR does not appear to be correct. The letter "Z" should never be added when using "+00:00".
The text was updated successfully, but these errors were encountered: