Not sure if this is the correct forum, apologies if not...

Just wondering if anyone knows what the source(s) of information are for the speed limit display on the virtual cockpit display? Clearly the vehicle is reading whatever signage it can see with the forward-facing camera - but presumably there are other data sources coming into play? I'm finding that it's very good at reading signs as I pass them - but also very good at forgetting about a sign that I've just gone past, and falling back onto whatever database it's referencing which doesn't know about a lot of the 20mph speed limits which are now in force in Wales!

If you don't get answers from here I'd try the Superb forum for 2024 model. I've no idea, I assumed it would be working off some sort of TwatNav system by now rather than the hit 'n' miss camera system, not that the also hit 'n' miss TwatNav system should be relied on rather than the driver keeping their biologically systems fully engaged including their electronic system of their brain.

On England's 3rd-world roads many road signs have disappeared partially or fully by the overgrowth, a human can see and recognise them but not the camera systems.

It's the digitised road speed on the map.

Ah Wales... where I'm sat. If it's mib2 high columbus or mib3 it's Here Maps. They updated all the roads on the system. For mib2 high you need to update the maps. Connect services for mib3 would do it for you but if out of contract MartiniBs files pinned.

SD card based mib2. Use the latest maps, these are TomTom equally they updated the digital roads like HereMaps from the Welsh Government map file where they agreed the speeds limits with each LA.

So I'd say you are using old maps. TSR will override the digitised road speed but once you pass onto a new digital segment on the map it will take the map speed. Hence it will revert if you are using old maps.

Check out MartiniBs pinned map updates. If mib1. May be more tricky. I have pointed people to a mib1 2023 update where it's possible it may have the new Welsh speeds. Mib1 update you have to use a teething approach which is used on Seat's. Works on Skoda as well. Since the Welsh speeds came in, in 2023 and the latest mib1 for Audi which can be used is 2023... might not be in it. You'd have to check. Whether there will be an Audi 2024 release pass. The files are compatible with a small edit.

Edited 12 June12 Jun by Tell

I'm using the latest 2025/26 MIB2 Amundsen map which has multiple incorrect speed limits, one example is the housing estate where I live shows as 20mph even though there are no signs changing it from the 30mph on the access road.

Where do errors like this get reported?

BTW I'm in England.

That's TomTom not on top if it.

Try

http://www.tomtom.com/mapshare/tools

They are reluctant to take users speed suggestions though preferring their survey cars. Wales they have the Welsh Government marked up map.

Edited 12 June12 Jun by Tell

11 hours ago, Tell said:

If it's mib2 high columbus or mib3 it's Here Maps. They updated all the roads on the system. For mib2 high you need to update the maps. Connect services for mib3 would do it for you but if out of contract MartiniBs files pinned.

Which of these would I have in a 2024 Superb L&K? Have seen lots of mentions of different infotainment system designations, but there doesn't seem to be a "this is the one you've got" kind of guide...

9 hours ago, gareth71 said:

Which of these would I have in a 2024 Superb L&K? Have seen lots of mentions of different infotainment system designations, but there doesn't seem to be a "this is the one you've got" kind of guide...

2024 means it's a mib3 since that is what was fitted to 2020- models, mib2 generally 2015-19. If you have connected services working with mib3 then the maps should auto update. Annual fee or free if you do it yourself. Some people manage not to have connect service set up correctly with mib3 and in that case the maps don't update. The update release can be read off the infotainment system.

If we are talking about Welsh 20mph speed limits that date and maps not being updated could leave it reflecting the old speed limits. Certainly the Welsh speed limits are in the database for the last year or so. Mib3 maps use Here Maps cartography. It's that team that have put the road speeds in using the Wales Government's negotiated speeds and agreed speed limits with the local authorities oublished on a public map. The later play, parse the parcel with these but they had the final say by agreement with the Welsh Government. Some local authorities in Wales pretend they were mandated. No they could change them back to 30 mph, if they so wished based on local knowledge of what speed they thought was suitable for that road.

The manual update is shown on this link:... note the map is designated yyyy.mm. Thus if your system is above 2024.06 then you have newer maps and connect services is running fine. If it's 2023... something or other your maps won't be updated with the Welsh road speeds. It was in the 2024 maps when the Welsh speeds got into them. My mib2 high started donging that I was speeding as I left the village from start up without reading any traffic signs.

Edited 13 June13 Jun by Tell

The part release of the manual one for the last period is: (doesnt include all of Europe yet... so you'd update manually with the one above if connected services was not working or configured.

YY.MM is the serial designation on the unit.

1 hour ago, Tell said:

2024 means it's a mib3

Thanks for all that info. Deffo MIB3, then! Car reports "navigation database: 25.5" and no updates currently available, so looks like it's as up-to-date as it can be. Connectivity services working fine as far as I can tell.

I guess the problem is with the Here Maps data set, then. On the whole it seems to be correct - but there are definitely a small number of locations in my home area where the speed limit derived from the mapping data overrides that detected by the front-facing camera, and is clearly incorrect (pre-Sept '23 limit). Surely there must be a way of offering up user-submitted corrections to Here Maps for obvious mistakes like this (especially when it affects a fundamental feature of the car such as speed limit warnings and Travel Assist)? Waze is my nav app of choice (in fact I'm also a map editor for them), and for the very, very few instances of incorrect speed limits on the Waze map it's very easy to submit a correction which is acted upon very quickly. If Waze can manage that, surely Here Maps must be able to?

1 hour ago, gareth71 said:

Thanks for all that info. Deffo MIB3, then! Car reports "navigation database: 25.5" and no updates currently available, so looks like it's as up-to-date as it can be. Connectivity services working fine as far as I can tell.

I guess the problem is with the Here Maps data set, then. On the whole it seems to be correct - but there are definitely a small number of locations in my home area where the speed limit derived from the mapping data overrides that detected by the front-facing camera, and is clearly incorrect (pre-Sept '23 limit). Surely there must be a way of offering up user-submitted corrections to Here Maps for obvious mistakes like this (especially when it affects a fundamental feature of the car such as speed limit warnings and Travel Assist)? Waze is my nav app of choice (in fact I'm also a map editor for them), and for the very, very few instances of incorrect speed limits on the Waze map it's very easy to submit a correction which is acted upon very quickly. If Waze can manage that, surely Here Maps must be able to?

Yes you'll be on connect services OK withn25.05.

There is a way of offering up user corrections. You need a Heremaps login and you do it through their portal

mapcreator.here.com/

The mobile app of it allows you to upload the evidence via a photo. May help.

Generally the camera recognition works well except where the council put the 20mph speed limits in on side roads and it sees the sign as going past. The signs need to be a bit further down the road. Only effect of the speed limits coming in and grumpy people thinking they don't apply to them.

I did do my bit where you could enter the village here on an unauthorised farm track. Council had left the old sign up of 30, got that changed so no excuses for those taking the short cut. The radar signs had been turned off that we had a whip around for. Got that reprogrammed.

Heremaps has more stringent validation process than Google and Waze being run by a proper cartography company.

The official 20mph roads in Wales are here.

https://datamap.gov.wales/maps/roads-affected-by-changes-to-the-speed-limit-on-re/

This is what was examined to update the Here Maps roads. Use to do health planning in a department that did gravity modelling for services planning. When the NHS use to build things and not close them down. So our analysts would pour over maps, travel times, timetables etc as part of siting work, ambulance stations, regional centres etc. Was heartened to hear that HereMaps geographers went over the Welsh Government files. Assorted notices also go in on road speed changes so they go back to them as well. Published road plans for road developments. The survey cars for precise road position on A roads etc for self drive cars... they are set up for that. The architectures stuff. Regenerative predictivd breaking is another one. Being mere mathematical modellers we like to make sure the geographers do it correctly 🤣.

As you know the 20mph limits are being revisited in Wales so that process will be repeated.

1 hour ago, gareth71 said:

Thanks for all that info. Deffo MIB3, then! Car reports "navigation database: 25.5" and no updates currently available, so looks like it's as up-to-date as it can be. Connectivity services working fine as far as I can tell.

I guess the problem is with the Here Maps data set, then. On the whole it seems to be correct - but there are definitely a small number of locations in my home area where the speed limit derived from the mapping data overrides that detected by the front-facing camera, and is clearly incorrect (pre-Sept '23 limit). Surely there must be a way of offering up user-submitted corrections to Here Maps for obvious mistakes like this (especially when it affects a fundamental feature of the car such as speed limit warnings and Travel Assist)? Waze is my nav app of choice (in fact I'm also a map editor for them), and for the very, very few instances of incorrect speed limits on the Waze map it's very easy to submit a correction which is acted upon very quickly. If Waze can manage that, surely Here Maps must be able to?

1 hour ago, gareth71 said:

Thanks for all that info. Deffo MIB3, then! Car reports "navigation database: 25.5" and no updates currently available, so looks like it's as up-to-date as it can be. Connectivity services working fine as far as I can tell.

I guess the problem is with the Here Maps data set, then. On the whole it seems to be correct - but there are definitely a small number of locations in my home area where the speed limit derived from the mapping data overrides that detected by the front-facing camera, and is clearly incorrect (pre-Sept '23 limit). Surely there must be a way of offering up user-submitted corrections to Here Maps for obvious mistakes like this (especially when it affects a fundamental feature of the car such as speed limit warnings and Travel Assist)? Waze is my nav app of choice (in fact I'm also a map editor for them), and for the very, very few instances of incorrect speed limits on the Waze map it's very easy to submit a correction which is acted upon very quickly. If Waze can manage that, surely Here Maps must be able to?

1 hour ago, Tell said:

There is a way of offering up user corrections. You need a Heremaps login and you do it through their portal

mapcreator.here.com/

Have checked that out, and it's odd. There's one particular section of road where something is obviously wrong - the A5119 trunk road through the village of Sychdyn, Flintshire. Coming southbound into the 20 limit, the car 'sees' the 20 sign and indicates the correct limit - but just a few yards later the displayed limit changes to 30 (incorrect since Sept 2023). However, that road in Here Maps looks to have a 20 limit correctly set - so where's the 30 information coming from?

3 minutes ago, gareth71 said:

Have checked that out, and it's odd. There's one particular section of road where something is obviously wrong - the A5119 trunk road through the village of Sychdyn, Flintshire. Coming southbound into the 20 limit, the car 'sees' the 20 sign and indicates the correct limit - but just a few yards later the displayed limit changes to 30 (incorrect since Sept 2023). However, that road in Here Maps looks to have a 20 limit correctly set - so where's the 30 information coming from?

Unless it's reading it off some small sign somewhere. You get those bin stickers and it's not on the digital map in Herecreator ?.

I think you might find a toggle to turn off TSR. One in mib2 for a test drive. Dynamic sign recognition.

The other one that started to effect me a couple of years back it decided the local street was 5 mph. I put that down to slight misalignment where it reckoned you were off road. Always when I turned into the street getting home. Dong. I got Here Maps to look at that found nothing.

Mib2 high auto recalibrates it's position if the maps are reloaded. So by driving a route few hundred yards through bends it places the car back on the map. Interesting one when you see it. Did that with the latest maps that I loaded up. We had a 5mph limit for quarter of a mile. Then learned from GPS and the road contour so then behaved itself. That issue has gone. It was the recalibration.

I have had this one in France, reading the traffic signs off the back of lorries you are following on the Calais / Dunkerque road. The only place it does that one.

The Heremaps creator database you see is the development database, whilst the production database is different, so they might be out of synch in that area. Sometimes you get two roads on top of each other. Which need to be weedled out. Previous edit error and what appears to be an AI system going off on one which can take a few days to straighten out.

So a few things to check. You might have a report something wrong icon. The systems they sell for lorry navigation etc have report issues from the cab. They get pulled up into the Here Maps validation. A select few were allowed to validate and change the source materiel, then it became apparent that the select few were not much good and that features was removed, so I did see everything their validation teams saw at one stage. They were hoping to get validation on the cheap.

Might be your issue falls into the one the production database needs to be looked at if the development database isn't showing it. If it's not a TSR misread or misalignment.

The other thing is Vag contracts out the development of the mib3 files from the cartography. If the programmers misunderstood the source files then cartography doesn't work. In the first year they had the postcode controids pointing off road. The postcode is matched to the road but they were taking you to an offroad centroid. They were interpreting the files in a GIS market research method than navigation. In Heremaps house numbers are allocated to a centroid to the building and the navigation point on the road. You walk from there. The postcode only guys were getting taken off road. That's been corrected now in mib3.

1 hour ago, Tell said:

Unless it's reading it off some small sign somewhere.

That's the odd thing - at this one location where I'm consistently seeing the error, there's no signage which could possibly be confusing the system.

https://maps.app.goo.gl/ZRmM79xPLgndkvY26

The only difference between the date of that StreetView image and now is that the 30 signs and road marking now reflect the 20 limit. The car correctly reads those signs. Within a few yards, though - before the speed camera that you can see just after the crossroads sign a little further down the road - the system determines that the limit is actually 30 (and does so consistently). Here Maps have the 20mph limit correctly mapped. So where's the incorrect data being picked up from?

It's either the development database you are looking at is correct but the production database which is either what is loaded in the car or held centrally doesn't tally. Either it's been subsequently sorted but the cars system doesn't reflect that or the production database has drifted from the development one ie. They have not taken the correction put into the development database so the production one is out.

Last edits were done by the Here Maps Team in October 2024. It's a precision road so small adjustments are not allowed so it locked down from movement.

It's conceivable that if it was changed in October 2024 it would not get into the shipped files for six months or so. 25.05 was your map in the car. I'd give it till Xmas 2025 to see whether it passes through or take it up with Here Maps.