Misplaced, but appropriate comments

Twice in two days I’ve seen URs come up with comments regarding an issue (one map error related, one just a usual front/back of the address issue) where the comment was placed on a drive in the Los Angeles area, while the point being referenced was 20 miles/35 miles to the East.

Is there some mechanism in the client that stores reports and uploads them later if there’s a data connection problem?

Here’s where one happened, in L.A. near Culver City, while the nearest U-Haul I could find on Holt was in Pomona or Ontario. The drive is heading basically straight down La Brea, with a slight detour into a parking lot- maybe they’d just gotten off the I-10 coming from Pomona/Ontario and stopped in the parking lot to make the report? It even looks like they pulled into a spot right next to the UR balloon. Does this seem likely? If so, why wouldn’t they have reported it at the location? (Forgot?) Also I note that this is dated May 24, but I would almost swear it wasn’t there yesterday.

https://www.waze.com/editor/?zoom=5&lat=34.01897&lon=-118.35571&showturn=138653&endshow=&layers=BFTFFTTTTTTTFTTTTTTTTTFTT&segments=4793923

The previous one, just east of downtown L.A., is below, and the user comment pretty much tells the story.Search on the address and you’ll find the point in question is 20 miles eastward (and see that the problem is a missing turn restriction on an unfinished road), in La Verne . Surely, it’s possible the user just got off the 101S and is just posting something that must have happened at least an hour earlier, but that seems unlikely to me. Not much drive trace, just a little on the 4th street bridge, and a spot at the point of bubbleage. This one just came up yesterday, and that’s when I first saw it.

https://www.waze.com/editor/?zoom=5&lat=34.04069&lon=-118.23113&showturn=138653&endshow=&layers=BFTFFTTTTFTTFTTTTTTTTTFTT&segments=4749508

I have screenshots, if the URs are missing.
Is this a known issue, and I’m bad at searching?

For both of them I would mark “Not identified” because we do not have enough information, we do not have the start of the drive nor the end of the drive (to be absolute), and all we can do is hope they come on to the forum to ask the question of why…

I have seen these myself. This typically happens when the driver initially looks at their overall route. They see a problem at the end of the navigation turn list or on the map, so they mark the problem there at the beginning of their trip. I guess they don’t realize we only see about a mile of their route and nothing else about their trip. As jemay said there is nothing you can do in these cases so mark “not identified”.

I also added a bit on this issue in the Wiki in the UR Article.

Thanks for the comments, guys.
Found another one yesterday.

My only comment is that one of these actually can be fixed because of the excellent description the user left, so that will be taken care of and marked Solved.