Outdated map data survives map update

[daganzdaanda]

The OsmAnd standard map for Deutschland, Bayern, Schwaben (Germany, Bavaria, Swabia?) has some outdated map data. I noticed this about 4 months ago when OsmAnd was showing the wrong speed limit on a road, and I saw the correct speed was already tagged in OSM for about a year. I moved the geometry a bit and changed some other little things, hoping this would trigger an update for the next monthly map release, but it has not.

Is there a simple way to check what speed limit OsmAnd's map has for a way? (Like the data layer on osm.org?)
I think there may be some other old artefacts in the area, maybe a diff update was corrupted a long while ago. How could this be fixed? Can someone trigger a complete "reload" for this map?

I also tried deleting the map from my phone and reloading, without a result. Also the Live-Updates did not change the error.

Not sure if this should have been an issue -- let me know and I will open an issue instead.

[dmpr0]

Hello! Thank you for the feedback.
Could you please provide the coordinates of the place so we can check it?

[daganzdaanda]

Thanks, I sent you my settings file.
If it's hard to find the problem, maybe I should just de-install OsmAnd and try with a new installation?
Thanks again for your effort!

[dmpr0]

Hi! We have received your files, but there’s only a Browse map profile that doesn't have Navigation. Could you please export the profile that you use for Navigation?

[daganzdaanda]

OK, I sent the navigation profile.

[DmitryAlexei]

There is an issue with routing that does not fully support maxspeed:forward / maxspeed:backward and may provide flaky results in real-life situations.
#18566

Probably the same problem with displaying maxspeed limits in widgets during real navigation. It depends on the navigation starting point.

[daganzdaanda]

Thanks a lot to you all for the investigation, and also the infos by email. It makes sense that the speed limit may be incorrect or missing when driving without navigation, since the app does not yet handle direction like that.