Today I stumbled across a UR which predates the invention of the internet. Sadly, no GPS.
https://www.waze.com/en-GB/livemap?zoom=17&lat=51.60601&lon=-0.06464
:lol:
Interesting… Normally when Waze gets something which ought to have a timestamp but where the data is missing, it defaults to the traditional null/blank/zero Unix epoch of 01/01/1970 00:00 - you see this on the start date of closures entered via the app.
Here though, the timestamp value has somehow managed to get set to a non-zero value, but which is still well and truly wrong. Based on the consecutive IDs allocated to this UR (8097526) and the one just to the east (8097527) which is correctly timestamped at 04/11/2016 18:45:38, plus the fact that both URs are “wrong driving direction” types, I’d hazard a guess they were both submitted by the same user, in which case this apparently ancient one may just have been the result of an app/network glitch preventing it from being submitted correctly, with the user then resending the same report details having moved a bit further down the road…
Never seen that before so I think Twister is right and it’s likely to be a glitch at time of submission.
PS Both reports are down to a new emergency access only gate installed in Worcester Avenue which I’ve now mapped as well as another in the area on Love Lane. Feel free to close the UR and any others that pop up in the next few days.
Found another one of these. Curiously, it’s dated about six months after the Unix epoch. https://www.waze.com/editor/?env=usa&lon=-73.99338&lat=40.71905&zoom=6&mode=0&segments=62706154&mapUpdateRequest=6376410
