Just noticed that this is still happening (and it's happening right now since we are at the end of month again...).
Looking at the code, it seems that the issue comes directly from the server side. The server returns a ux: null in the trend array after metar which is why all the wrong time have exactly the same value, howOld treated it as 0... The returned time is in fact the time since Unix epoch....
The point should be location near the city area in the north.
And especially for the problem with superimposed text, here is another screenshot :
As you can see two location texts are superimposed on the same location.
No Need to be harsh there you Know windy updates are Hard to make and you need to be aware that this site tries to be as accurate as possible. And if you dont like it just go back to your crappy weather websites that you enjoy
The solution is may be here :
Change the units in the website, on the wind colour scale. Then the modification is automatically applied to the phone app and widget.
The 22nd General Conference on Weights and Measures declared in 2003 that "the symbol for the decimal marker shall be either the point on the line or the comma on the line".
Different countries use different symbols as decimal separators
You say: "This also makes the meter conversion inaccurate."
As I can see, there is no inaccuracy for KPLU runway length.
3650 ft = 1113 m , also 3,650 ft = 1,113 m or 3.650 ft = 1.113 m
I don't think that someone could ever imagine of a runway length of three and a half feet!