Another nav. stupidity report

[NineElectrics]

Normally, I don’t post these, as there are a ton of them and I don’t have much time. This one irked me more than usual, though.

This time, between Vantage, WA and Ellensburg, the nav. tried to route me off I-90 onto a small, rural road network for dozens of miles, and then did it once more. There was nothing wrong with I-90 according to Google Maps (which is my primary mode of navigation on the Rivian) so I ignored these repeated requests to lengthen my journey and stayed on I-90. Indeed, it turns out that the road was perfectly fine, with no evidence of past accidents, and almost no traffic.

That saved me a lot of time, because the speed limit of I-90 is 70 mph, and the speed limit for the recommended Vantage Highway is 35 mph!

There must be hiccups in the data, because it did t take long for Rivian to reroute me correctly both times once I blew by their terrible off ramp recommendations. This is the problem with Rivian: the data is full of problems and nobody is being paid to correct them. Errors probably number in the tens of thousands for the US alone. Whereas, Apple and Google can use GPS data from their billions of phones to automatically fix errors in most cases, as well as respond to accidents and transient road closures.

Always run Apple or Google navigation alongside the Rivian nav. Because there is no CarPlay, I mount my phone on the dash.

Sponsored

 

[Riviot]

What was your charge when you got to Ellensburg? It could've been trying to slow you down to get you there with a higher charge, or stop you by the Petrified Logs State Park level 2 charger. I've had it do that to me when getting to Ellensburg with <50 miles.

 

[shrink]

One of my more egregious Nav errors. Asked Rivian to look at it. They said nothing was wrong.

On my R1S, my car location also lurches forward maybe 100 feet (?) then come back to about the right location every time it stops. Rivian tried to blame it on tall buildings interfering with the GPS signal. Such lurching does not happen on my R1T.

I set another service appointment for these errors. I consider them a potential safety issue - especially if one tries to change lanes suddenly and dangerously to follow an erroneous re-route in an unfamiliar area.

 

[Steve A.]

Always run Apple or Google navigation alongside the Rivian nav. Because there is no CarPlay, I mount my phone on the dash.

Whatever they are using for traffic data blows which is why I always use Waze on my phone as well. In Waze we trust!

 

[dgennetten]

...which makes me want to post a query: what are the best dash phone mount solutions for R1's?

 

[COdogman]

Is Rivian being bribed by small localities to route us through in a literal tourist trap? ?

(Yes, I’m trying to get this theory mentioned in national news)

 

[sevengroove]

One of my more egregious Nav errors. Asked Rivian to look at it. They said nothing was wrong.

On my R1S, my car location also lurches forward maybe 100 feet (?) then come back to about the right location every time it stops. Rivian tried to blame it on tall buildings interfering with the GPS signal. Such lurching does not happen on my R1T.

I set another service appointment for these errors. I consider them a potential safety issue - especially if one tries to change lanes suddenly and dangerously to follow an erroneous re-route in an unfamiliar area.

This has happened to me consistently since day 1 in my R1S. Every time I stop at a traffic light it thinks I am 100ft further than I actually am. Curious to hear what your service tech has to say.
Oops, missed the part where they said nothing was wrong. Sigh.

 

[Big_Ike]

Normally, I don’t post these, as there are a ton of them and I don’t have much time. This one irked me more than usual, though.

This time, between Vantage, WA and Ellensburg, the nav. tried to route me off I-90 onto a small, rural road network for dozens of miles, and then did it once more. There was nothing wrong with I-90 according to Google Maps (which is my primary mode of navigation on the Rivian) so I ignored these repeated requests to lengthen my journey and stayed on I-90. Indeed, it turns out that the road was perfectly fine, with no evidence of past accidents, and almost no traffic.

That saved me a lot of time, because the speed limit of I-90 is 70 mph, and the speed limit for the recommended Vantage Highway is 35 mph!

There must be hiccups in the data, because it did t take long for Rivian to reroute me correctly both times once I blew by their terrible off ramp recommendations. This is the problem with Rivian: the data is full of problems and nobody is being paid to correct them. Errors probably number in the tens of thousands for the US alone. Whereas, Apple and Google can use GPS data from their billions of phones to automatically fix errors in most cases, as well as respond to accidents and transient road closures.

Always run Apple or Google navigation alongside the Rivian nav. Because there is no CarPlay, I mount my phone on the dash.

Appreciate your post. I was in San Diego a couple of weekends ago and the Nav sent me east via CA-94. I just figured there was a problem on I-8 and went on the "Adventure". I had my daughter check the CA 511 website and there were no reported issues on I-8.

As I rationalized it later, I figured I had made a wrong turn and the nav was compensating for my stupidity - which still may be the case! Or the nav just took me for a ride!

I would recommend CA-94 if you have the time. It was beautiful country.

 

[ZenTurtle]

My biggest complaint in the Bay Area is that traffic info on Rivian is highly inaccurate, Google/Apple always predict accurate arrival time, Rivian often wrong by 20-30min. Route choice often wrong (for traffic)
Very unsettling and unsafe to fiddle with my phone when u have a huge useless screen in the car.
Have CarPlay in my Bolt EV and miss it every time I drive the R1T

 

[csharp]

Not sure this is a Rivian problem as much as a Mapbox problem.

 

[Steve A.]

Not sure this is a Rivian problem as much as a Mapbox problem.

The Rivian problem is the refusal to support Android Auto and Apple CarPlay which renders the issue moot!

 

[azbill]

Not sure this is a Rivian problem as much as a Mapbox problem.

It is Rivians problem that they chose Mapbox.

 

[csharp]

The Rivian problem is the refusal to support Android Auto and Apple CarPlay which renders the issue moot!

It is Rivians problem that they chose Mapbox.

Whole-heartedly agree that we need AA and ACP. My point was if you contact Rivian to complain about the map messing up like in the OP, they send you to Mapbox.

 

[jjswan33]

Yeah I agree that Rivian NAV is still not a premium or even good solution, I don't trust it. Between having it tell me I need to charge to range numbers my truck isn't capable of or having me charge for hours at 50kW level chargers even know faster chargers are nearby or worst of all it having me navigate hours out of the way and adding charges when a direct route exists well within my range.

All that said they are working on it, I expect it will get better. Yes I would love CP but doesn't seem like that is coming sOOn. I thought ABRP would be an upgrade, so far I am not so sure. At least they added the google POIs which are best in class.

 

[WorldComposting]

My biggest complaint in the Bay Area is that traffic info on Rivian is highly inaccurate, Google/Apple always predict accurate arrival time, Rivian often wrong by 20-30min. Route choice often wrong (for traffic)
Very unsettling and unsafe to fiddle with my phone when u have a huge useless screen in the car.
Have CarPlay in my Bolt EV and miss it every time I drive the R1T

I had the same thing happen on my trip to the Outer Banks. We stopped to charge and when we got back in the car it was saying 2 hours and waze was saying 3 hours. It seemed to think there was no traffic on the beach roads. Waze even changed and added time where as the Rivian nav kept saying we would be there at the same time.

I'm not saying we need AA or CP but they really need to work on the Navigation to make it somewhat comparable!

Sponsored