What about suburban streets? Yeah, I don't understand that distinction except perhaps NoA city means can navigate down town Manhattan. Sure, if it can do that I trust it can do rural and suburban areas. It pretty much works fine for me in my neck of the woods except for reading speed limit signs, which often don't match geocoded speed limits, stop signs, left or right turns at intersections, be there a stop sign, light, or yield sign.
I think suburban streets will be included in "automatic driving on city streets".
As an aside, it is SAE autonomous level convo I am off, not definition of feature complete which I have familiarity with given 45+ years in software development.
Honestly, defining the level of autonomy for Autopilot may become increasingly blurry and difficult. It is likely in my opinion that as Tesla keeps adding new features with driver supervision, that we will see Autopilot become more and more like FSD while still technically being L2 because of the driver supervision. In other words, Autopilot may be L2 all the way until it suddenly becomes L5.
Look at the progression so far with AP:
Auto Steer + TACC is textbook L2. The SAE even uses Lane Keeping (Auto Steer) and Adaptive Cruise Control (TACC) has examples of L2.
NOA starts to take AP a little bit beyond classic L2 in terms of features. NOA can decide to make a lane change based on the driving environment and execute that lane change on its own as long as the driver has their hands on the wheel. That's a bit more than just a classic L2 that just helps with lane keeping and speed control. Yet, NOA still has nags and requires the driver to pay attention (watch for that stalled car!) So it has functionality beyond a basic L2 ADAS but is still L2.
Now what about when "automatic driving on city streets" is released? Like NOA, it will presumably be able to decide to make lane changes, respond to traffic lights and stop signs, make turns at intersections based on nav directions. It will start to look a lot like self-driving. It will definitely be doing more than your basic L2 ADAS. Yet, it will require nags and driver attention at first. So it will still technically be L2 even though it is doing all the driving with hopefully no driver intervention.
The final stage will be when Tesla has validated the system with millions of miles, perfected the features, made sure it can handle issues like stalled cars and other issues safely. At that point, Tesla will remove the nags and deploy robotaxis. So a system that acted like FSD but was labelled L2 because of nags will suddenly be L5 when the nags are removed.
At least, that is how see the deployment of FSD features to be like.
I would have thought NoA city would not exist as when they reach that drop NoA completely and say FSD. But then AP includes NoA but won't include NoA city, so perhaps that is the distinction.
Yes, I think it would make sense if Tesla simply replaced the words "navigate on autopilot" with the words "full self-driving" in the blue box in the driver display when FSD has reached L5. From an UI perspective, that would make sense. It would be a convenient way of telling the driver that they are now in FSD mode. The UI would still be the same. You would still have the single blue line like NOA and a blue box in the navigation to toggle it on or off. When I talk about NOA on city streets, I am really talking about the UI. It seems to me like Tesla designed the NOA UI like the blue center line and the blue box in the navigation that is automatically toggled on as the bridge between AP and FSD. I think we can see the NOA UI design was intended to pave the way for the UI for FSD. Another data point to support this idea is the fact that Tesla moved NOA into the "new FSD" column.