I'd be interested to know if anyone else is experiencing this:

Since the 25.12 map update, I've been getting consistent errors with single carriageway NSL roads. They're either identified as 20 or 30 rather than 60 MPH, with the resulting bongs & flashing warnings. I'd hoped that the next map update would sort it, but 26.2 has arrived & still the same. This is on a '25 SEL Edition with Columbus.

The odd thing is it only seems to happen when turning into an NSL road from a fixed speed limit. If a road transitions from fixed to NSL, the system correctly identifies that. Even weirder is in one example, I turn from a 40 MPH to NSL & it's identified as 30 MPH, turn again into another NSL & it's identified as 20 MPH. So in this instance there's no signs involved as the limit hasn't changed, which implies that it's duff map data.

Unsurprisingly, emailing Skoda was as productive as if I'd asked the cat...

I've found that, even in places where there are no traffic signs, the speed limit indication is markedly different if you have traffic sign recognition enabled. I know this, because I had a month's free trial of TSR, but was glad when it ended.

With TSR it seems to be accessing a second on-line data set, different from the sat nav one. I was getting all sorts of phantom limits showing for which there were absolutely no signs for the camera to spot - mainly 50 mph on motorways for sections where there had presumably been roadworks in the past.

If you do have TSR, it may be this second data set that's causing the problems, which would explain why an update to the sat nav data doesn't help.

When my TSR trial ended, I found the normal sat nav data to be much more reliable.

Interesting. Just had a quick look at the settings & can't see an option to turn it off, annoyingly.

Edited 31 March31 Mar by Rbz5416

Google maps tends to be better, but it still has lags when limits have changed and Google hasn't updated. It is frustrating when Google has one limit, you car shows a different limit, and you know from the road signage that they are both wrong.

Had it happen again today but this time on a transition. The odd thing about this is it corrected after a couple of hundred yards. There were roadworks there recently, well a couple of months ago, so I'm suspecting that I have two issues. Road sign recognition isn't working, although there's no indication of that & the GPS map data is stale.

Edited 31 March31 Mar by Rbz5416