It seems like people are using "new nav" and "new maps" interchangeably, but I think they are independent updates. My car was delivered with new maps, but I didn't get Navigation Beta until a couple days ago.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Here it is the new Tesla Maps ( coming this weekend? )
- Thread starter BigD0g
- Start date
-
- Tags
- tesla maps vahalla
chispas
Member
The new maps came with a new backend and new routing (navigation) algorithm, in the release notes, we can see how Tesla call that the new navigation. The Tesla "traffic info" adds more data to the new system but the system was already there.
Just wanted to add an anecdotal endorsement of the new routing engine. Today, coming from Palo Alto going to Solano County, I decided to compare Waze and the new Tesla routing engine. Waze estimated the trip would take about two hours in afternoon traffic, and provided a route across the Dumbarton Bridge. Tesla routed through San Francisco, across the Bay Bridge and estimated about 1 hour 40 minutes for the route. I took Tesla's preferred route and watched Waze along the way. Waze initially estimate the ETA to be 6:15 p.m. for the route Tesla had planned; Tesla estimated the ETA to be 5:40 p.m. Tesla's ETA remained fairly consistent, dropping to 5:30 p.m. toward the end, which is when I arrived. Waze's ETA converged with Tesla's very slowly and was still off by about 20 minutes quite late into the drive.
Ultimately, Tesla's routing was much more accurate regarding the ETA of the path it chose and seems to have saved me about 30 minutes (assuming Waze was correct in its initial assessment of how long the Dumbarton Bridge route would have taken). Of course, this is one trip and could be a fluke, but I now have much more confidence in Tesla's routing and I encourage others to try similar experiments to see if Tesla's new engine can consistently perform as well as (or better than!?) Waze.
Ultimately, Tesla's routing was much more accurate regarding the ETA of the path it chose and seems to have saved me about 30 minutes (assuming Waze was correct in its initial assessment of how long the Dumbarton Bridge route would have taken). Of course, this is one trip and could be a fluke, but I now have much more confidence in Tesla's routing and I encourage others to try similar experiments to see if Tesla's new engine can consistently perform as well as (or better than!?) Waze.
aesculus
Still Trying to Figure This All Out
Driving in the Bay Area is sort of a crap shoot for delays in many cases. All it takes is one fender bender to throw everything akilter.
I wonder if WAZE uses some sort of statistical analysis/machine learning to predict the likelihood of a traffic delay vs just the averages for a given time of the day?
Agree it's a crap shoot around here. One possibility is that Tesla routing consistently underestimates the time to take a route and just got lucky this time because traffic cleared up. I think this is not the case because on my drive this morning, Tesla and Waze proposed the same route with respect to major highways (Waze proposed a side road detour at one point, but as soon as I skipped it it reverted to the route Tesla preferred and actually estimated the new route was faster than Waze's original proposal) and Tesla estimated a later arrival time by about 6 minutes. Ultimately, Tesla was closer on the ETA, but given the distance I was travelling, I can't credit Tesla much for this because traffic certainly changed over time. All that said, I now have two ~60-mile drives in Bay Area traffic where Tesla was on par with or possibly better than Waze. Again, just anecdotal and very small sample, but so far new routing is night and day compared to the old routing.
Feature Request: I would like an option to avoid gravel roads. I am not sure if any navigation/mapping system has this option.
It might be a Midwest issue but Tesla KC brought me up test car with last Thursday. I helped the Customer Experience Specialist avoid the direct route along a gravel road but it rerouted her to the next gravel road instead of going an extra 45 seconds out of the way on a paved road.
It might be a Midwest issue but Tesla KC brought me up test car with last Thursday. I helped the Customer Experience Specialist avoid the direct route along a gravel road but it rerouted her to the next gravel road instead of going an extra 45 seconds out of the way on a paved road.
Dumb question: how do I get the new maps/nav to acknowledge carpool lane and express lane access in the Bay Area ? Waze has a means to turn that on, but I'm not convinced the new Tesla maps are doing that - it routes me along ways I know would be longer and could be avoided by sticking to a nearby carpool/express lane.
@MasterT @suraj1194 Have you sent your request for that feature to the email address in the release notes?
It does not appear to be a feature yet unfortunately. But it is at least somewhat aware of HOV lanes. Once I took the HOV flyover from 880 to 237 and it correctly understood that I cannot legally leave the HOV lane for 3 more exits. It rerouted me to take that 3rd exit and do a U-turn and get back on 237 to get to my destination, which is technically/legally the right thing to do.
I didn't see that there was an email address in the release notes. But in my defense, as I posted elsewhere on the forum, the 17" screen rebooted on me when I got in the car the day it first downloaded the new nav software and announced it on the screen, just as I started reading it. I never looked at the notes since then. Thank you very much for the advice!@MasterT @suraj1194 Have you sent your request for that feature to the email address in the release notes?
That's exactly where I had issues with believing that the map is aware of HOV/express lanes. I take 237W from 880S and this morning it instead told me to keep going further and take Tasman. I stuck to 237 express lane instead.
Well, I notice that it never ever instructs you to take the express flyovers, so I think that's somehow excluded in the routing engine. It's just, if you do it yourself, it seems to react in a way that suggests it's aware of the concept.
Yes it does reroute me when it realizes I'm on the express ramp, but that's a fairly useless capability. I'm going to follow @MP3Mike's advice and become one more party emailing their contact address asking for this capability. There's a huge difference between HOV-aware and non-HOV routes here in the bay area during rush hour, as we all know...
Don't get me wrong, I completely agree. Tesla also is in a unique position to actually know whether or not you're in the HOV lane, potentially. Waze these days tries to be HOV-aware but honestly 90% of the time I don't comply with what it tells me to do, based off the traffic I'm observing, and it's none the wiser.
aesculus
Still Trying to Figure This All Out
Is this with the new maps? The reason I ask is that this was my first test case. The old maps would send me down a rutted dirt/mud road to save 1 minute of time. The new maps take the paved route.
Xenoilphobe
Well-Known Member
Similar threads
