Oh okay I will have to search futher then, must have missed a place.

I correct myself, only one Xbk appears in the name.

Hi Felix, I downloaded the openmtbmap of Italy dated 05.02.2026 and installed on my computer with contourlines and elevetion data and with desktop TYP, but the problem is not resolved as you can see on the attached screenshot: the path is not highlighted with crosses as I had proposed since it was a path forbidden to bicycles, even the name remained duplicated.

I have updated some rules, could you please download after tomorrow midday the new map of Italy (compiled today or tomorrow) and report if it’s fixed. I do hope so (also the double xbk xbk should be reduced to only a single xbk in the name). I just started the server to compile new maps so today they likely will not be online yet.

Yes, the path is on Aosta Valley in Italy. I think that even other user would be interested in Italy, Switzerland, France and other states where the montain bike is not forbidden everywhere to see the paths and tracks forbidden for bicycles visualy marked on your maps. Thank you.

In this case I don’t render it but show it’s in the name because in Austria or Germany maps would become unusable. Is this Italy? I think maybe I should make a rule to keep it in Italy, Switzerland and France where a bicyle=no actually makes sense unlike other countries like Germany and Austria where it’s pure politics as mountainbiking is forbidden anyhow.

In Alps map: on openstreetmap a highway=path with bicycle=no, sac_scale=mountain_hiking, trail_visibility=excellent that it’s part of a route=hiking with network=lwn ref=2 not showing with the cross symbol on Basecamp (see attachment). I think in any case that with the attribute bicycle=no you have to render the highways=* always with the cross symbol (if possible in red color); this is very important to me, especially in the field to avoid paths forbidden to bikes.

It depends on the combination – can you give me an example which tags there are alltogether. In some places I decide to omit the crosses – but it could be a bug too in my rules.

On Basecamp/Mapsource I find the search works well – the problem is that every GPS device by Garmin works a bit differently. I don’t see problems on outdoor units like Edge 1040 concerning the city/village/places search. I’m not realy sure what happens there in Iraq – I doubt I can solve it. I more or less use similar categories according to population vs Garmin does. I do think however that a problem maybe that in Middle East / Iraq few of those places have a population tag. In most parts of the western world they exist and I model my maps according to this tag quite heavily. I cannot do different treatment according to countries as this would increase complexity too much in this point. So I guess it’s either a data problem in OSM (missing population tag) or a Nuvi/Drivesmart problem.