OpenStreetMap logo OpenStreetMap

I drive a Tesla Model 3 around Canberra suburbs. When it uses Traffic Aware Cruise Control, it apparently relies on OSM data rather than the speed limit signs. This can lead to situations where TACC will use an incorrect speed limit (eg. 80 km/h in a 60 km/h zone). See osm.org/way/668268353#map=19/-35.24389/149.13545&layers=TD How can such speed limit data be kept accurate and up to date? This is what I aim to find out.

See also https://www.youtube.com/watch?v=t9kMHt_Pf6A

Location: Verona, Watson, Canberra, District of Canberra Central, Australian Capital Territory, 2602, Australia
Email icon Bluesky Icon Facebook Icon LinkedIn Icon Mastodon Icon Telegram Icon X Icon

Discussion

Comment from n76 on 1 April 2020 at 21:18

On that video it seems it took a year from the OSM edit until it showed up on the car’s nav system. To me that means either Tesla is really, really slow at pulling in new data from OSM or that Tesla is not using OSM data at all.

To your question about keeping speed limit data accurate and current: It is typically done by volunteers and you know your area best. So when you see a speed limit in OSM that is wrong you fix it as soon as you can.

I use either OsmAnd (which has a monthly release of new maps) or maps.me (which has an irregular release of maps but is usually about once a month) so from the time I see something I fixed get updated can be from a few days to just under two months depending on when I made the change and when those organizations pull data from OSM.

Log in to leave a comment