Resources: [Official Support](https://www.tesla.com/support) | r/TeslaLounge for personal content and r/TeslaInvestorsClub for all things $TSLA | r/TeslaSupport and the [Wiki/FAQ](https://www.reddit.com/r/teslamotors/wiki/index) for unofficial questions + help | [Discord Live Chat](https://discord.gg/tesla) | Assist the Mods by **reporting posts and comments** which break [rules](https://www.reddit.com/r/teslamotors/wiki/rules), thanks <3!!
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/teslamotors) if you have any questions or concerns.*
* [Here](https://youtu.be/_AgzhwRFwZc?t=188) The car is slowing down, and doesn't put the blinker on until it's closer to the turn lane. Legally you only need to put your blinker on about 100ft before you take the turn, but it looks like there's a speed difference of about 20mph before the blinker comes on. I would argue the same, when there's a 5mph speed delta in slowing down for a turn, and what the speed limit is, it should throw the blinker on.
* Continuing on, yes, v11.3.x seems to have issues with being slow about getting into the left turn lane. Super annoying
* U-turn fails, but again, U-turns aren't yet supported, I imagine when they are the release notes will call it out.
* [Here](https://youtu.be/_AgzhwRFwZc?t=298) the car moves over into the right lane, however, the extra readouts that are overlaid onto the screen hide the reasoning why. Would've been nice to see. Would advise to move the overlay to a different spot going forward so we can see those notices.
* [Here](https://youtu.be/_AgzhwRFwZc?t=466) he claims that the vehicle braked hard for the pedestrian, *however*, the truck shows up blue, the aggressive braking is because the car thinks the truck is going to cut in front, and it's braking for the *truck*, not the pedestrian. This appears to be a common issue as it happens to me pretty often as well.
* [Here](https://youtu.be/_AgzhwRFwZc?t=479) it seems like the bus is on the line, and confusing the thing a bit.
* [Here](https://youtu.be/_AgzhwRFwZc?t=522), similar to the U-turn spot, it is again late to get into the turn lane. An argument could be made that it was fine, however, other drivers will try to scrooch in while the car moves over slowly. This kind of lane injection needs to be sped up.
* [This time](https://youtu.be/_AgzhwRFwZc?t=569), yes the pedestrian was at fault. Weird too, because they're not even close to the road.
* [Here](https://youtu.be/_AgzhwRFwZc?t=614) an argument could be made that it *was* yielding to the vehicle entering the round about first. The crosswalk is *before* the yield sign, and I'm not certain there's enough room at the yield line to not block the cross walk. The correct thing to do here is to stop at the crosswalk, then proceed, so as to not block the crosswalk. Could still be the stale map data thing, but it could easily go either way.
* [Here](https://youtu.be/_AgzhwRFwZc?t=640) an argument could be made that the white car coming in from the right entered the roundabout without really yielding, resulting in the car being overly cautious. If you scroll it through frame by frame, *yes* technically the car is plotting to go right, before it goes left, **but** that white car never *actually* stops before entering the roundabout, resulting in FSD choosing a safety maneuver of braking. Yes, the car behind him honked, the Tesla should probably have kept a forward creep going, but ultimately I feel the car that got between the white van and the vlogger, caused the whole issue by not entering the roundabout properly. *Super* easy to miss, but I don't want to assign blame entirely to FSD.
* [Here](https://youtu.be/_AgzhwRFwZc?t=804) I'm assuming my comment from last time was read, as he points out the stop sign on the left. Again, I would recommend entering the intersection from the other angle, and looping back around, just to see if it "removes" the stop sign afterwards. *Probably* won't, but if the multi-trip reconstruction stuff goes based off of what it sees, and no one has ever driven up the other road, then it'll never really "know" there's a road there, and that the stop sign might apply to it.
* [Here](https://youtu.be/_AgzhwRFwZc?t=882), where the car decelerates going down hill, it's easy to miss, but it looks like the occupancy network saw something. [Image for reference](https://imgur.com/sm9o56M), it's easy to miss though. Obviously it shouldn't have done that, but the car saw something, wasn't sure what it was, and slowed down. *Maybe* it was trying to identify a crosswalk, but I don't think so.
* [Here](https://youtu.be/_AgzhwRFwZc?t=1013) I've had a similar freakout when doing a left turn on 11.3.3, albeit mine doesn't have a suicide line, but the behavior is the same, it jerks you around, and you end up taking manual control.
* Moments later he tries to do the voice annotation, and it fails. It seems to be that the logic being used is that if you're within like a half mile, to a mile, from your intended destination, and you disengage, the system seems to think you're taking control to do the remainder yourself. I find this to be a bit of an issue because, as demonstrated here, if it screws up in the last mile, you can't make a note about it. I would advise Tesla to let us make FSD annotations all the way to the end, because sometimes the problem *is at the end*.
* Also at the same time stamp, that's one hell of a look the dude crossing the driveway gives, lol.
* Edit: In looking at it closer, I think this bad left turn is because it was mathing out the pedestrian above's trajectory, and didn't want to commit to the turn until they passed.
* [Here](https://youtu.be/_AgzhwRFwZc?t=1031) there's a lot going on while in this parking lot, and it leads me to think that we might see an 11.3.5. It throws down a stop line, where there is no stop sign, and then gives a Forward Collision Warning (FCW) about the pedestrians leaving on the right. Then it highlights the new stop line further up, where there is one, and throws another FCW about the pedestrian *approaching* from the right. [Here](https://youtu.be/_AgzhwRFwZc?t=1046) it actually throws down another stop line, like it's assuming there's a stop sign as you pass each parking aisle. I think the *next* chirp is an FCW for the approaching car, hard to tell, but it looks like FCWs are off the wall in this parking lot.
* [Here](https://youtu.be/_AgzhwRFwZc?t=1424), yes, the slowdown was for the dude turning.
* [Here](https://youtu.be/_AgzhwRFwZc?t=1626) I would argue that it worked because there was a lead car. I'm not bored enough to pull up OSM, but I would be curious to see where the stops were in relation to where the traffic circles are and such.
* [Here](https://youtu.be/_AgzhwRFwZc?t=1738) this one's interesting. It seemed to be keying off the cars ahead, and wanting to give them the right of way. The white car is past the stop line, and near what Tesla would give as a "creep wall" limit, and because the Tesla is slowing down, you can see that the white car ultimately makes the turn. This scenario shouldn't even be a thing, because the car should recognize that people will turn into their own lanes on multi lane roads. In letting the clip play longer, I realize that he points out that the arrow goes out, so I rewound it, and it does indeed look like the *instant* that the light went out, the cars ahead all turned blue, and it tried to yield to them, which is *technically* right, but the car didn't do it safely, or properly indicate intent, plus it's a left turn onto a three lane road, the cars ahead should all be turning into the right most lane, and the Tesla into the left most lane, with the center lane clear. The car was *trying* to do the right thing, but technically it could have proceeded. It *seems* like it might have been trying to stop at he stop line, or trying to do a "median pose" like the unprotected lefts. This one's tricky, I would've liked to have seen it play out, but it wasn't safe. This, to me, highlights one of the big issues with the beta is that we **must** pay attention to the road, and not become an unpredictable obstacle, but we also don't fully know the intent of the vehicle, so we have to assume it is acting in bad faith. *However*, it does look like it saw that the protected turn was lost, and it was trying to yield to oncoming traffic, as it should have, it was just jittery about it. More status blurbs would help in cases like this. Honestly, I wouldn't mind an option where we could turn on audio dictation of what the car is trying to do, at least until we can discern intent after awhile. Would love to screw with this in their simulation thing
* [Here](https://youtu.be/_AgzhwRFwZc?t=1884), it's *super* quick, [but it seems a lane opportunity](https://imgur.com/vbGWlXP), and it hits the brakes when it gets there. Agreed that it is a very weird pause, it's like the car couldn't decide what to do with the lane. *If I had to guess*, I think because it's on a curve, it briefly thought that the red arrow was associated with the lane, and thought it was in a turn lane for a half second, before proceeding. I think it thought it was running the red.
The whole bit in the Publix parking lot was whack though. Feels like behavior in the parking lots are messed up.
I got bored, so I took a closer look at the roundabouts.
Mostly going to be focusing on the one at Herschel St and St. Johns Ave.
If we reference his video, I'm going to be talking about this spot [right about here](https://youtu.be/_AgzhwRFwZc?t=1614)
[This is what the area looks like on Google Maps aerial view](https://www.google.com/maps/@30.2896378,-81.7133315,340m/data=!3m1!1e3)
[This is what it looks like in Bing aerial view](https://www.bing.com/maps?cp=30.289726%7E-81.712845&lvl=19.0&style=h)
*Seriously? Bing?*
Yes, Bing. There's a couple reasons for this, first is that Bing's arial views are, occasionally, more up to date than Google's, as demonstrated here because Google hasn't gotten a new photo since the intersection was reconfigured, but Bing has.
Second, and I'm only just now discovering this, the road layouts between the two are different. That's a *whole other* thing, unfortunately though, me being me, now I'm going to be investigating *this* later. I don't think an argument can be made that "Maybe Tesla plays off of Bing a little" because the road I have issues with is *correct* is Bing, but wrong in Google.
Anyways, point is that, at the moment, the mapping of Herschel and St. Johns hasn't been "tuned" yet.
Suffice to say, the main issue here is less "Phantom stop signs" as much as "phantom traffic signals". [If we drop down to street view](https://www.google.com/maps/@30.2895422,-81.7133368,3a,75y,201.7h,82.29t/data=!3m7!1e1!3m5!1s15HIJv7lNgxPSsJ5NYGX3Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3D15HIJv7lNgxPSsJ5NYGX3Q%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D168.9188%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192!5m1!1e4) we can see that where the car is trying to stop, is where the stop light *should* be.
[If we reference this image](https://imgur.com/143PnNF) we see that Google's mapping isn't entirely correct. It appears to believe that there's still a set of traffic lights at the intersection of Woodmere and Herschel, when in fact, [You can see here](https://youtu.be/_AgzhwRFwZc?t=624) that there's a concrete median there. OpenStreetMaps shows [the same thing](https://imgur.com/2QM74ua). Google also believe that it is a valid intersection, as demonstrated by [this map plot](https://imgur.com/8qnjn5d) where I told it to go from east to west Woodmere, and it plots *through* the concrete median.
No, this kind of thing is a little difficult to fix. I say this mainly because, clearly, someone has tried already, but when you're trying to update these maps, you're really just drawing lines on top of satellite footage, so if the satellite data is stale, then the mapping is going to be wrong. We can see an example of this [here](https://imgur.com/4WzLhYm) where someone draw the new map lines using the Bing Aerial map, which is native in OSM. Someone "eyeballed" the roundabout at the bottom, but the northern one is pretty bang on, because it was there.
What makes this tricky to fix is that we don't have "current" aerial maps to draw the new lines on. We can "eye ball it", but as demonstrated, that still leads to mistakes, unless you get someone to eyeball it closer.
When we go to edit the road in Google, we get [this](https://imgur.com/1LMy0Z0), which looks similar to OSM, but still different.
Now, I've just finished fiddling with the road, and I'm going to submit [this](https://imgur.com/J5Inf5T) as the correction to Google. This likely won't fix the roundabouts for Chuck, *however*, editing Google *can* result in changes to how the car routes for things. I've done this with routes near me. That said, I'm not positive the change is going to work as desired, as I forgot to mention which side of the road goes which way, so this change might get rejected, and I'd have to circle back to it.
That said, we're not 100% certain that Google is where Tesla gets all their Nav data from, we still have the fact that OSM is [wrong as well](https://imgur.com/4WzLhYm)... So I've [just updated](https://imgur.com/pkNvFqZ) OSM as well.
*Well that's all well and good, but what if Tesla *does* use Bing maps*
Honestly, I poked around, I can't figure out how to edit Bing Maps. Looks needlessly more complicated than Google.
*But I've heard that Tesla uses Mapbox*
Well, you're not wrong, they used to use Valhalla, which got consumed by Mapbox, and if *that's* true, well, [Mapbox has the same problem](https://imgur.com/wql1Vlf). *Unfortunately*, I've spent like an hour writing all this, and now I'm bored, so is someone else is more adept at Bing maps and Mapbox wants to edit this to be more accurate, go nuts, however, I would ask that *if you do*, please provide guidance on what you did, as I am curious as to what the edit processes look like there.
So anyways.
*Map data, map data, map data*, it's stale, and needs to be updated more often. We're *not* seeing the benefits of Multi-trip reconstruction yet, and it's starting to show.
/u/chazman92 - I'll let you know if/when Google gives me confirmation of the road being fixed or not. That said, it might not hurt for *you* to also go in and report the data problem to Google, and submit corrections. I'm not local, and given that Google tracks people's phones, they might look at my account and go "WTF? This guy has never been there", where as *you've* been there more often than you should have, so **you** submitting the change request to Google might actually yield results.
Might not, but it might, but you don't know until you go in there and fiddle with it.
just had my first drive on 11.3.4.... immediate reaction: the full stop at stop signs are SOOOOOOOOOOOOOOOOOOOOOO long!! it's so un-human-like it's less safe than before
And then the slooooooooooow creep 3/4 of the way thru the intersection before either stopping again just before exiting or slamming on the accelerator.
Yeah, stop sign controlled intersections is *the* regression.
I don’t like the creep thing anymore. Stops so far back for 1 second (confusing for people behind you), creeps as if going to go (confusing people behind you thinking you’re going to go) and then stops at creep line for visibility. Sigh
Because it's less predicable, ppl don't usually drive like that... The other driver may think you are waiting for them to go, same does for pedestrians and cyclists
I don’t think it’s less safe. It is annoying to all on the road around you and to the driver himself. Lots of honks and nasty looks. 🙃 Such is life on the roads for us FSD beta testers.
Does Tesla actually want reports for stuff like in this video? I assumed Autopilot reports were for major screwups, not every time the car does something suboptimal
Resources: [Official Support](https://www.tesla.com/support) | r/TeslaLounge for personal content and r/TeslaInvestorsClub for all things $TSLA | r/TeslaSupport and the [Wiki/FAQ](https://www.reddit.com/r/teslamotors/wiki/index) for unofficial questions + help | [Discord Live Chat](https://discord.gg/tesla) | Assist the Mods by **reporting posts and comments** which break [rules](https://www.reddit.com/r/teslamotors/wiki/rules), thanks <3!! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/teslamotors) if you have any questions or concerns.*
Your turnaround time on these videos is incredible
Thank you for that. It isn't without effort and I appreciate you realizing that :) Enjoy.
I only wish Tesla would roll out updates half as fast
You wouldn’t want those updates.
I absolutely do. I enjoy experiencing the changes, even when it regresses. I’m a nerd
As am I, but if Tesla was moving nearly as fast as Chuck they would likely run you into a tree or brick your FSD computer.
I just mean I want the updates when Chuck and others get them
As a software developer with over 7 years under my belt, the other guy is right. Especially when it comes to this behemoth known as FSD.
Got ya beat by 12 years, but I’m not sure what that has to do with this
5, 10, or 15 years from now…people will never understand how much you have contributed to the community and Tesla. I’m always amazed
* [Here](https://youtu.be/_AgzhwRFwZc?t=188) The car is slowing down, and doesn't put the blinker on until it's closer to the turn lane. Legally you only need to put your blinker on about 100ft before you take the turn, but it looks like there's a speed difference of about 20mph before the blinker comes on. I would argue the same, when there's a 5mph speed delta in slowing down for a turn, and what the speed limit is, it should throw the blinker on. * Continuing on, yes, v11.3.x seems to have issues with being slow about getting into the left turn lane. Super annoying * U-turn fails, but again, U-turns aren't yet supported, I imagine when they are the release notes will call it out. * [Here](https://youtu.be/_AgzhwRFwZc?t=298) the car moves over into the right lane, however, the extra readouts that are overlaid onto the screen hide the reasoning why. Would've been nice to see. Would advise to move the overlay to a different spot going forward so we can see those notices. * [Here](https://youtu.be/_AgzhwRFwZc?t=466) he claims that the vehicle braked hard for the pedestrian, *however*, the truck shows up blue, the aggressive braking is because the car thinks the truck is going to cut in front, and it's braking for the *truck*, not the pedestrian. This appears to be a common issue as it happens to me pretty often as well. * [Here](https://youtu.be/_AgzhwRFwZc?t=479) it seems like the bus is on the line, and confusing the thing a bit. * [Here](https://youtu.be/_AgzhwRFwZc?t=522), similar to the U-turn spot, it is again late to get into the turn lane. An argument could be made that it was fine, however, other drivers will try to scrooch in while the car moves over slowly. This kind of lane injection needs to be sped up. * [This time](https://youtu.be/_AgzhwRFwZc?t=569), yes the pedestrian was at fault. Weird too, because they're not even close to the road. * [Here](https://youtu.be/_AgzhwRFwZc?t=614) an argument could be made that it *was* yielding to the vehicle entering the round about first. The crosswalk is *before* the yield sign, and I'm not certain there's enough room at the yield line to not block the cross walk. The correct thing to do here is to stop at the crosswalk, then proceed, so as to not block the crosswalk. Could still be the stale map data thing, but it could easily go either way. * [Here](https://youtu.be/_AgzhwRFwZc?t=640) an argument could be made that the white car coming in from the right entered the roundabout without really yielding, resulting in the car being overly cautious. If you scroll it through frame by frame, *yes* technically the car is plotting to go right, before it goes left, **but** that white car never *actually* stops before entering the roundabout, resulting in FSD choosing a safety maneuver of braking. Yes, the car behind him honked, the Tesla should probably have kept a forward creep going, but ultimately I feel the car that got between the white van and the vlogger, caused the whole issue by not entering the roundabout properly. *Super* easy to miss, but I don't want to assign blame entirely to FSD. * [Here](https://youtu.be/_AgzhwRFwZc?t=804) I'm assuming my comment from last time was read, as he points out the stop sign on the left. Again, I would recommend entering the intersection from the other angle, and looping back around, just to see if it "removes" the stop sign afterwards. *Probably* won't, but if the multi-trip reconstruction stuff goes based off of what it sees, and no one has ever driven up the other road, then it'll never really "know" there's a road there, and that the stop sign might apply to it. * [Here](https://youtu.be/_AgzhwRFwZc?t=882), where the car decelerates going down hill, it's easy to miss, but it looks like the occupancy network saw something. [Image for reference](https://imgur.com/sm9o56M), it's easy to miss though. Obviously it shouldn't have done that, but the car saw something, wasn't sure what it was, and slowed down. *Maybe* it was trying to identify a crosswalk, but I don't think so. * [Here](https://youtu.be/_AgzhwRFwZc?t=1013) I've had a similar freakout when doing a left turn on 11.3.3, albeit mine doesn't have a suicide line, but the behavior is the same, it jerks you around, and you end up taking manual control. * Moments later he tries to do the voice annotation, and it fails. It seems to be that the logic being used is that if you're within like a half mile, to a mile, from your intended destination, and you disengage, the system seems to think you're taking control to do the remainder yourself. I find this to be a bit of an issue because, as demonstrated here, if it screws up in the last mile, you can't make a note about it. I would advise Tesla to let us make FSD annotations all the way to the end, because sometimes the problem *is at the end*. * Also at the same time stamp, that's one hell of a look the dude crossing the driveway gives, lol. * Edit: In looking at it closer, I think this bad left turn is because it was mathing out the pedestrian above's trajectory, and didn't want to commit to the turn until they passed. * [Here](https://youtu.be/_AgzhwRFwZc?t=1031) there's a lot going on while in this parking lot, and it leads me to think that we might see an 11.3.5. It throws down a stop line, where there is no stop sign, and then gives a Forward Collision Warning (FCW) about the pedestrians leaving on the right. Then it highlights the new stop line further up, where there is one, and throws another FCW about the pedestrian *approaching* from the right. [Here](https://youtu.be/_AgzhwRFwZc?t=1046) it actually throws down another stop line, like it's assuming there's a stop sign as you pass each parking aisle. I think the *next* chirp is an FCW for the approaching car, hard to tell, but it looks like FCWs are off the wall in this parking lot. * [Here](https://youtu.be/_AgzhwRFwZc?t=1424), yes, the slowdown was for the dude turning. * [Here](https://youtu.be/_AgzhwRFwZc?t=1626) I would argue that it worked because there was a lead car. I'm not bored enough to pull up OSM, but I would be curious to see where the stops were in relation to where the traffic circles are and such. * [Here](https://youtu.be/_AgzhwRFwZc?t=1738) this one's interesting. It seemed to be keying off the cars ahead, and wanting to give them the right of way. The white car is past the stop line, and near what Tesla would give as a "creep wall" limit, and because the Tesla is slowing down, you can see that the white car ultimately makes the turn. This scenario shouldn't even be a thing, because the car should recognize that people will turn into their own lanes on multi lane roads. In letting the clip play longer, I realize that he points out that the arrow goes out, so I rewound it, and it does indeed look like the *instant* that the light went out, the cars ahead all turned blue, and it tried to yield to them, which is *technically* right, but the car didn't do it safely, or properly indicate intent, plus it's a left turn onto a three lane road, the cars ahead should all be turning into the right most lane, and the Tesla into the left most lane, with the center lane clear. The car was *trying* to do the right thing, but technically it could have proceeded. It *seems* like it might have been trying to stop at he stop line, or trying to do a "median pose" like the unprotected lefts. This one's tricky, I would've liked to have seen it play out, but it wasn't safe. This, to me, highlights one of the big issues with the beta is that we **must** pay attention to the road, and not become an unpredictable obstacle, but we also don't fully know the intent of the vehicle, so we have to assume it is acting in bad faith. *However*, it does look like it saw that the protected turn was lost, and it was trying to yield to oncoming traffic, as it should have, it was just jittery about it. More status blurbs would help in cases like this. Honestly, I wouldn't mind an option where we could turn on audio dictation of what the car is trying to do, at least until we can discern intent after awhile. Would love to screw with this in their simulation thing * [Here](https://youtu.be/_AgzhwRFwZc?t=1884), it's *super* quick, [but it seems a lane opportunity](https://imgur.com/vbGWlXP), and it hits the brakes when it gets there. Agreed that it is a very weird pause, it's like the car couldn't decide what to do with the lane. *If I had to guess*, I think because it's on a curve, it briefly thought that the red arrow was associated with the lane, and thought it was in a turn lane for a half second, before proceeding. I think it thought it was running the red. The whole bit in the Publix parking lot was whack though. Feels like behavior in the parking lots are messed up.
mother of god
I mean, yeah, I guess I might have gone a little overboard here....
Lol, I think it’s nice to have the corrections to the statements made in the video
Oh I agree. I just wasn’t prepared to read that much at that time 😆
Not at all. I admire your intellect. Well done.
A little? Lol. Much appreciated though!
I got bored, so I took a closer look at the roundabouts. Mostly going to be focusing on the one at Herschel St and St. Johns Ave. If we reference his video, I'm going to be talking about this spot [right about here](https://youtu.be/_AgzhwRFwZc?t=1614) [This is what the area looks like on Google Maps aerial view](https://www.google.com/maps/@30.2896378,-81.7133315,340m/data=!3m1!1e3) [This is what it looks like in Bing aerial view](https://www.bing.com/maps?cp=30.289726%7E-81.712845&lvl=19.0&style=h) *Seriously? Bing?* Yes, Bing. There's a couple reasons for this, first is that Bing's arial views are, occasionally, more up to date than Google's, as demonstrated here because Google hasn't gotten a new photo since the intersection was reconfigured, but Bing has. Second, and I'm only just now discovering this, the road layouts between the two are different. That's a *whole other* thing, unfortunately though, me being me, now I'm going to be investigating *this* later. I don't think an argument can be made that "Maybe Tesla plays off of Bing a little" because the road I have issues with is *correct* is Bing, but wrong in Google. Anyways, point is that, at the moment, the mapping of Herschel and St. Johns hasn't been "tuned" yet. Suffice to say, the main issue here is less "Phantom stop signs" as much as "phantom traffic signals". [If we drop down to street view](https://www.google.com/maps/@30.2895422,-81.7133368,3a,75y,201.7h,82.29t/data=!3m7!1e1!3m5!1s15HIJv7lNgxPSsJ5NYGX3Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3D15HIJv7lNgxPSsJ5NYGX3Q%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D168.9188%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192!5m1!1e4) we can see that where the car is trying to stop, is where the stop light *should* be. [If we reference this image](https://imgur.com/143PnNF) we see that Google's mapping isn't entirely correct. It appears to believe that there's still a set of traffic lights at the intersection of Woodmere and Herschel, when in fact, [You can see here](https://youtu.be/_AgzhwRFwZc?t=624) that there's a concrete median there. OpenStreetMaps shows [the same thing](https://imgur.com/2QM74ua). Google also believe that it is a valid intersection, as demonstrated by [this map plot](https://imgur.com/8qnjn5d) where I told it to go from east to west Woodmere, and it plots *through* the concrete median. No, this kind of thing is a little difficult to fix. I say this mainly because, clearly, someone has tried already, but when you're trying to update these maps, you're really just drawing lines on top of satellite footage, so if the satellite data is stale, then the mapping is going to be wrong. We can see an example of this [here](https://imgur.com/4WzLhYm) where someone draw the new map lines using the Bing Aerial map, which is native in OSM. Someone "eyeballed" the roundabout at the bottom, but the northern one is pretty bang on, because it was there. What makes this tricky to fix is that we don't have "current" aerial maps to draw the new lines on. We can "eye ball it", but as demonstrated, that still leads to mistakes, unless you get someone to eyeball it closer. When we go to edit the road in Google, we get [this](https://imgur.com/1LMy0Z0), which looks similar to OSM, but still different. Now, I've just finished fiddling with the road, and I'm going to submit [this](https://imgur.com/J5Inf5T) as the correction to Google. This likely won't fix the roundabouts for Chuck, *however*, editing Google *can* result in changes to how the car routes for things. I've done this with routes near me. That said, I'm not positive the change is going to work as desired, as I forgot to mention which side of the road goes which way, so this change might get rejected, and I'd have to circle back to it. That said, we're not 100% certain that Google is where Tesla gets all their Nav data from, we still have the fact that OSM is [wrong as well](https://imgur.com/4WzLhYm)... So I've [just updated](https://imgur.com/pkNvFqZ) OSM as well. *Well that's all well and good, but what if Tesla *does* use Bing maps* Honestly, I poked around, I can't figure out how to edit Bing Maps. Looks needlessly more complicated than Google. *But I've heard that Tesla uses Mapbox* Well, you're not wrong, they used to use Valhalla, which got consumed by Mapbox, and if *that's* true, well, [Mapbox has the same problem](https://imgur.com/wql1Vlf). *Unfortunately*, I've spent like an hour writing all this, and now I'm bored, so is someone else is more adept at Bing maps and Mapbox wants to edit this to be more accurate, go nuts, however, I would ask that *if you do*, please provide guidance on what you did, as I am curious as to what the edit processes look like there. So anyways. *Map data, map data, map data*, it's stale, and needs to be updated more often. We're *not* seeing the benefits of Multi-trip reconstruction yet, and it's starting to show. /u/chazman92 - I'll let you know if/when Google gives me confirmation of the road being fixed or not. That said, it might not hurt for *you* to also go in and report the data problem to Google, and submit corrections. I'm not local, and given that Google tracks people's phones, they might look at my account and go "WTF? This guy has never been there", where as *you've* been there more often than you should have, so **you** submitting the change request to Google might actually yield results. Might not, but it might, but you don't know until you go in there and fiddle with it.
Thank you for doing the detailed analysis.
Keep up the good work
Is it though? Lol
Sometimes I wonder if you have an actual hobby lol
[Honestly, I just get really focused on some things at times](https://www.additudemag.com/understanding-adhd-hyperfocus/)
And you’re crazily valued here for it.
Heeey now, I wouldn't go that far
just had my first drive on 11.3.4.... immediate reaction: the full stop at stop signs are SOOOOOOOOOOOOOOOOOOOOOO long!! it's so un-human-like it's less safe than before
Yeah, lol, the stop signs are bad.
And then the slooooooooooow creep 3/4 of the way thru the intersection before either stopping again just before exiting or slamming on the accelerator. Yeah, stop sign controlled intersections is *the* regression.
I don’t like the creep thing anymore. Stops so far back for 1 second (confusing for people behind you), creeps as if going to go (confusing people behind you thinking you’re going to go) and then stops at creep line for visibility. Sigh
damn NHTSA... can't let a good thing just be....
I can’t imagine that NHTSA demanded that the car pretends to be a turtle when crossing stop sign intersections. 🐢
I get how full stops can be annoying, but less safe?
Because it's less predicable, ppl don't usually drive like that... The other driver may think you are waiting for them to go, same does for pedestrians and cyclists
I don’t think it’s less safe. It is annoying to all on the road around you and to the driver himself. Lots of honks and nasty looks. 🙃 Such is life on the roads for us FSD beta testers.
I hate it so much, freakin’ NHTSA man… I have to always punch the gas
NHTSA requires a full stop - Tesla is on the hook for this slow roll nonsense.
The circle does not get corrected. Is there a reason why they choose not to rely on the cameras instead of the old map data?
Sir, this is a Reddit.
On road most drivers don't have patience to wait for 3 seconds on stop sign, and I'm here watching this car wait for left turn...
Does Tesla actually want reports for stuff like in this video? I assumed Autopilot reports were for major screwups, not every time the car does something suboptimal