The "if only we had more detailed maps, self-driving would work" is a fake argument. Once you have enough info to know where the fixed trouble spots are, more data will not help you. Trouble comes from unexpected moving objects.
(2004 (not 2005) DARPA Grand Challenge, where everyone did badly. CMU team tried to do it by manual pre-planning. DARPA gave out the course as a set of waypoints on a CD 2 hours before the start. CMU had a big trailer full of people at workstations to plan out the exact path in those two hours, using high resolution aerial photos. But the USMC Colonel in charge of the event foiled their scheme. Just before the event, a few of his Marines went out in the dark and put up some obstacles the vehicle would have to go around. And, sure enough, the CMU vehicle plowed right into a sheet metal fence and got stuck.[2])
What we're likely to see is bandwidth that changes drastically as you move. You'll get great bandwidth with line of sight to a nearby base station, and then it will drop off drastically as you get further away. That's inherent in using 26GHz for high bandwidth.
The likely benefit is that it becomes possible to provide enough short-range bandwidth for many people to get video-rate bandwidth in crowded areas. So people can watch the game on their phone while in the stadium.
[1] https://thehill.com/blogs/congress-blog/technology/420509-wh...
[2] http://overbot.com/grandchallenge/images/race2004/cmucrash.j...