Hello Stephan, ad 1) it is caused by assignment of house numbers to the nearest road. I think I understand the problem even I am not sure how to solve it at the moment.
ad 2) we may try to separate footway from existing road types. We will try it on the map first and not in the routing, i.e. they will still be part of "Other Roads". For that category we have now this mapping of tags: 'footway': (8,5), 'track':(8,5), 'path':(8,5), 'cycleway':(8,10), 'pedestrian':(8,5), 'steps':(8,2), 'construction':(8,10), 'bridleway':(8,5), 'unsurfaced':(8,15) Should I move there some other tag too? thanks Martin p.s. we have very limited set of road types so it is not simple to add much more ...
although I have not done any forther investigation about more ways to be handled as "other roads" (need more map examples?) you should try to do the change about displaying footways.
Maybe when you have a prototype of that, take a schreenshot when Navigator displays an area with many footways, and we as users can evaluate that (and say thank you to you :-) )
Hi Stephan, here is the test view in Andorra (lat=42.544567, lon=1.518986), where are both footway and steps (stairs). Unfortunately the new models will collide with existing (boat ferry and rail ferry) so we will not update configuration files in application until most of the existing data are converted. After October OSM update you will see data like this: Footway and Stairs with old configuration if you change your album.style and teleatlas.map you will get view like Footway and Stairs with new configuration. If you use the new configuration with old (current) data you may not notice it but ferries will be visible only in detail, which is not good. regards Martin