Legenda Mappa

 

Polilinee (Highways):

Spiegazione: Ci sono in totale 4 modelli di visualizzazione. Tuttavia le colorazioni sono sempre le stesse per "thin""wide" and "clas". Si differenziano solamente per lo spessore delle linee per adattarsi al meglio ai differenti GPS. Il layout mapsource/Qlandkarte GT  (d'ora in avanti "trad") invece ha colori differenti, con meno contrasto. Di conseguenza in questa legenda per le polilinee (Strade) ci sono sempre 2 esempi. Uno che utilizza il layout "trad" (in alto), e uno usando il layout "clas" sotto).

Si prega di notare, visto che questa domanda salta fuori spesso, che vengono prese in considerazione molte variabili come il tracktype, smoothness o surface. Se volete conoscere la chiave principale che ne regola la rappresentazione siete pregati di leggere il codice sorgente dei fogli di stile (vedi FAQ).

Main Highways "trad" layoutMain highways "clas" layout

 

I sentieri con attributi riferiti alla mtb o alla sac_scale (clicca l'immagine per ingrandire)

Ways with mtb attributes - "clas" layout

 

Linee e strade aggiuntive  (clicca l'immagine per ingrandire)

Additional ways and lines - "trad" layoutAdditonal ways and lines "clas" layout

 

Punti di Interesse

Ristoranti e Negozi

 

Sport e Turismo

 

Municipali ed altri POI

 

Aree

Uso del terreno:

 

Sport e Luoghi Pubblici:

 

Natura e Turismo

 

Abbreviazioni ed Attributi Strade:

M12 / Mr34 -- il primo numero indica il mtb:scale, il secondo numero il mtb:scale:uphill. "r" indica una strada che fa parte di una percorso mtb. Vedere:http://wiki.openstreetmap.org/wiki/Key:mtb:scale
G1 -- tracktype=grade1 Tipo Track= Grado1 Vedere: http://wiki.openstreetmap.org/wiki/Tracktype
T2 -- sac_scale=T2 (Escursioni in montagna) Vedere: http://wiki.openstreetmap.org/wiki/Key:sac_scale

Xbk --bicycle=no Bicicletta Vietata
Cr Or Mr -- route=bicycle / route=mtb See: http://wiki.openstreetmap.org/wiki/relation:route

Vedere: http://wiki.openstreetmap.org/wiki/Key:highway

Pri=primary / primary_link
Sec=secondary
Ter=tertiary
Cw=cycleway
Min=minor
Unsf=unsurfaced
Uncl=unclassified
Living=living_street
Pdstrn=pedestrian
Trk=track
Pth=path
Ft=footway
Fp=footpath
Brdlw=bridleway
Rd=road
Byw=byway
Ser=service

 

Cyclelane/Cycletrack

Vedere: http://wiki.openstreetmap.org/wiki/Key:cycleway

Bklane=cycleway=lane
Bktrk - cycleway=track
Opp - cycleway=opposite
Opptrk - cycleway=opposite_track

 

52 comments to Legenda Mappa

  • Mig369

    Hi extremecarver,

    I just downloaded the newest Europe-Map (non-unicode). Now there is an Area on the Map with new Symbols, which were new to me (see Attachement).
    Via Openstreetmap.org I came to the conclusion, thats mayby information:guidepost.

    Now I was wondering, if these knots are wrong in OSM or if its some issue with the openMTBMap, because the Symbols look a bit messy on the Map. As you can see they are visible till 1.5km-Zoom and make this fuzzy look…
    Here’s one of the nodes as example: https://www.openstreetmap.org/node/8207087273

    kind regards and happy easter,
    Mig369

    • extremecarver

      I’m gonna check this. Should not happen this way – looks like the symbol for bicycle knot points in NL.

    • extremecarver

      Well I checked it now – the problem here IMHO is wrong tagging.
      https://wiki.openstreetmap.org/wiki/Key:lcn_ref

      Are these actually lcn_ref node points? As a quick measure I just added a rule to delete all lcn_ref & network_type=destination (don’t know what the heck that kind of network type is – as it’s not documented).

      Plus in general I’ve taken out all those nodes from resolution 21 (1000/1500m) and only start showing them from resolution 22 (700m) instead. Plus for guidepost & mtb=yes/bicycle=yes I’ve changed the symbol to be less obvious. I don’t think they need to be that visible (and degraded from 23 to 24, so 200m instead of 300m).

    • extremecarver

      here is another one of these: https://www.openstreetmap.org/node/275914838

      Not sure how to filter that one out – network:type=node_network

    • Mig369

      Danke für die schnelle Antwort! (Hab erst nicht geblickt, dass man auch auf Deutsch schreiben kann 😉 )
      Ich stecke in OSM allerdings nicht so tief drin, wenns um Relations und Netzwerke geht. Mir scheint das Tagging auf Basis dieser Anleitung gemacht worden zu sein.
      https://wiki.openstreetmap.org/wiki/DE:Bicycle/Fahrradrouten_kartieren#Fahrradknotenpunktnetzwerk
      Gleichzeitig scheint aber lcn_ref ja veraltet und durch die Relations abgelöst worden zu sein.

      Ich habe den Ersteller der Nodes mal dazu angeschrieben, vielleicht kann er etwas dazu sagen.

      • Mig369

        Habe schon Rückmeldung vom Ersteller Karthoo erhalten:

        “Hallo Mig,

        Da habe ich ein neues Tagging für das MTB-Netz Hornisgrinde-Ortenau ausprobiert, da das Netz vorher in Form von nicht-existierenden Rundwegen und schrecklichen Sammelrelationen gemappt war. Zunächst hatte ich an den Routen und Knotenpunkten network:type=node_network getaggt, was ich aber mittlerweile geändert habe, da das nicht ganz korrekt ist. Ich habe dann network:type=destination angefügt, was noch nicht dokumentiert ist. An manchen Knoten, an denen auch Knotenpunkte des Wanderwegenetzes des SWV sind, ist weiterhin network:type=node_network getaggt, also bitte nicht einfach löschen.”

        Vielleicht hilft das ja zum Verständnis.

        • extremecarver

          Bitte schreib ihm, dass er den Tag lcn_ref entfernen soll, wenn es kein echter Knotenpunkt mit Nummer ist. Und Routen müssen einfach, auch wenn es kompliziert ist – als Relationen eingetragen werden. Und für Wanderweg Relationen gilt das genauso. Die Punkte so sind im Tagging nicht mit echten Knotenpunkten unterscheidbar – daher bitte korrigieren. Man kann Sachen etwas anders taggen – aber dann muss es klar unterscheidbar sein von bestehenden Tagging Schemata – und dass ohne neue Tags/Keys zu erfinden. Wenn dort natürlich echte Knotenpunkte sind – mit Schild auf dem die Nummer klar erkennbar ist von weitem (keine Schildnumer oder Nummer die man nur aus 1m Abstand entziffern kann) – dann ist das Tagging korrekt. Aber das scheint hier ja nicht der Fall zu sein außer ich irre mich.

          Zumindest anhand dieser Auflistung gibt es in Bayern ja keine echten Knotenpunkte: https://de.wikipedia.org/wiki/Knotenpunktbezogene_Wegweisung
          Der Tag lcn_ref darf aber nur dafür verwendet werden.

        • extremecarver

          Ich bin jetzt etwas unsicher – es gibt in einem Teil von Baden Württemberg inzwischen wirklich ein Knotenpunktsystem – Knoten 1-70, aber ich bin ziemlich sicher eben nicht dort wo er die Knoten eingetragen hat, was ja auch in Bayern ist.
          Das Problem dabei – wer / wieso auch immer hat beschlossen diese Routen als rcn einzutragen – was sie meiner Meinung nach definitiv nicht sind. Ich hab die jetzt zu lcn degradiert – was aber ziemlich kompliziert war.

  • maiksen

    I am using the maps also for hiking. I was wondering if it is possible to include way markers (Wegmarkierungen) like a red diamond or red circle in the layout?

    • extremecarver

      Hi Maiksen – no I cannot include them. It would need to many line types – but there aren’t than many free line types. And including them as a POI I find it not optimal either. I don’t feel Garmin map format is made for it.

  • AK77

    [edit] – die Darstellung liegt wohl daran, dass bei “fine_gravel” die graue Linie vom Radweg dargestellt wird, bei “compacted” das ursprünglich gewohnte braun.

    • extremecarver

      Bei compacted gehe ich in etwa von tracktype=grade 3 aus – daher braun. Bei fine_gravel von grade1 (nur falls keine anderen Werte da sind – wie smoothness oder tracktype).

  • AK77

    sieht so aus als wären die Linien für cycleway and footway durcheinander geraten. Designated footway mit cycling=yes wird bei mir mit grauer, unterbrochener Linie dargestellt. Vorher war’s irgendwie braun, soweit ich mich erinnere.

  • graf.fd@gmx.de

    Hallo Community,

    ich habe die openmtbmap.org Europa Karte unter Windows installiert und teilweise auf mein Garmin Montana 610 übertragen/installiert, was einwandfrei funktioniert hat.
    Beim Starten des Montana 610 erschein nun die Fehlermeldung “Can’t authenticate Maps. Contact content seller for help”.
    Mit OK kann ich zwar bestätigen und das Gerät startet.
    Jedoch finde ich unter “Karten” die installierten Teile der Europa Karte nicht.

    Wie kann ich den Fehler beheben?

    Vielen Dank und Grüße
    Friedl

  • ErikMM

    Is there a way to know which trails are hiking only, vs a trail where bikes are allowed? What about mountain biking only trails, as rare as that is? These are both rather important issues for the future of mtb access and the way in which the public interfaces with mountain bikers. Thanks

    • extremecarver

      Hi Erik – In general if something is explicitly forbidden – then XXX black crosses will be used – else you have to know the default of the country you are in. E.g. Switzerland allowed, Austria forbidden, Germany (complicated – depends on the Bundesland), Italy allowed and so on. And yes – in countries like Austria we are always riding illegal. In some places it’s tolerated, in others we risk fines of over 1000€ – but that applies to everything that is not officially a street open for all vehicles – or a cycleway. Even tracks/dirt roads are forbidden for mtbiking in Austria.

      • I suppose I’ll mark Austria off my list of places to ride. My concern at this juncture is in vacation planning and in general doing my best to ride only open trails as to not risk foreign fines, violence, and jail. Before flying and driving hours to discover a sign that says “no bikes,” taking risks on an unsigned route, or trying to locate a website in a foreign langue to determine if something open, it would be nice to know by looking at a track’s color or some indicator that bikes are allowed. I realize the status of trails change from closed to open, or the reverse, so accuracy not be perfect, but something is better than nothing. At this time I rely on MTB Projects and Trail Forks, which aren’t perfect as sometimes hiking only and illegal trails slip past moderators, and they don’t show “all” the trails nor all intersections. The safe bet is to stick to the more popular and well known routes to know what is open, but I was hoping Openmtb would have some insights on trail legality for places and connectors not shown by these other apps etc. At any rate, thanks, the Iceland map is great.

        • extremecarver

          Well for Austria you are therefore only allowed on those trails – where you see the black route indicator – and it would make no sense at all to clutter up the map by showing that all those nice trails are not allowed to be ridden. An yes – much better go to Italy, Switzerland or France for mtbiking in the Alps. Not only is it allowed – you will also be wellcome outside of bikeparks/trailpark ghettos that we have in Austria. This does not mean you cannot ride mtb in Austria – the chance to get fined is very low – maybe 500 small fines (you pay 100€ and promise not to ever ride there anymore) – and 10-20 big fines (over 1000€) per year – with loads of mtbikers. I live in Austria and ride here all the time – for holidays I never stay here however but go mainly to Switzerland (best parks, best maintained, and often lifts included in the “Kurtaxe” – plus everyone wellcomes you). And I never stick to mtb routes -as they are plain boring for 90% are forest roads not trails (and if trail super easy)

  • inarav43

    Hallo Felix, da ich in der Kartenlegende nicht fündig wurde, meine Frage:
    was bedeuten die blauen Rechtecke mit weissem Pfeil und kann man diese eventuell ausblenden, da sie meiner Meinung die Ansicht erheblich beeinträchtigen. Danke und Grüße Inarav

    • extremecarver

      Ui – so ist das wirklich übel. Im Prinzip bedeuten die hier geht die Straße/Weg weiter und gehört noch gemapped. Normalerweise sieht man so Pfeile sehr selten – dass eine Gegend damit zu zugekleistert ist habe ich noch nie gesehen. Du müsstest im .typ-file mit einem typfile editor (laufen nur unter Windows, bzw am Mac/Linux via WineHD) den Pfeil zu einem einzelnen 1Pixel kleinen Punkt abändern (ganz unsichtbar klappt nicht immer – hängt vom Gerät ab).

      Ist das nur in einer Gegend so übel – oder im ganzen Land (welches Land?). Wenn das ganze Land so zugepflastert ist, könnte ich da per Regel einfach alle Pfeile entfernen – weil so macht das ja keinen Sinn.

  • Christoph Rohland

    Auf meinem Edge 800 ist das Grün der MTB Trails kaum von Schwarz zu unterscheiden. Gibt es eine Möglichkeit ein helleres Grün einzustellen?

    • extremecarver

      du müsstest das .typ File der Karte verändern – ist aber etwas komplizierter (etwa mit MapTK – das verwende ich – oder dem kostenpflichtigen TypWiz)

      • Christoph Rohland

        Ich hab den typviewer benutzt. Mit #00CA00 als Farbe für MTB tracks kann ich sie deutlich besser von normalen Tracks unterscheiden. Außerdem habe ich den Hintergrund von MTB3-5 weiß statt transparent gemacht.

  • VORON_SPb

    Hello! I’ve noticed a problem in rendering of your map in Garmin, while having some bad experience in recent Belarus cycling trip.

    Many unpaved roads in OSM have only 2 properties: highway=track & surface=unpaved. With the Openmtbmap, the Garmin device renders such road as “G2 Trk”. This is incorrect, as G2 implies “quite good road”, while in reality this road may be truly horrible (drawn across the swamp using the satellite imagery, and actually passable only on tractor or tank).

    I’d suggest putting the G* tags on road only if there are appropriate “tracktype” or “smoothness” tags, not basing only on surface=unpaved (which may mean every kind of surface in reality).

    • extremecarver

      okay- well in Western Europe that usually works quite well – and I’m not sure what other default I should chose – none also does not seem fitting. maybe display it like G3 or G4?
      For other surface tags this works more reliable – but es unpaved is very broad.

      • VORON_SPb

        I believe that such rules will make sense:
        1. highway=track -> “Trk”
        2. highway=track, surface=* -> “Trk” (except asphalt, paving_stones and concrete:plates which shall be “G1 Trk”).

        I don’t know the present rules, but obviously, if there is no tracktype or smoothness tag, any kinds of unpaved surface shall not automatically assign G* tag.

        I can give you some photos of that aerial-drawn “G2” roads, where the actual smoothness was horrible or very_horrible. 🙂

        • extremecarver

          well – I will disable it for unpaved, because it is really not very good. However I will keep some others – on velomap the tracktypes added are a bit lower – e.g. compacted gets tracktype=2 – that is because with wide enough tyres (e.g. 1.75″ and not some race tyres <1.3″) I do believe surfaces like compacted are ressembling more a tracktype=1 – however with thin tyres it is more like 2.
          At least according to the sample images given here I think that fits: https://wiki.openstreetmap.org/wiki/Key:surface
          tracktype!=* & surface=asphalt {add tracktype=1}
          tracktype!=* & surface=concrete {add tracktype=1}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=sett {add tracktype=1}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=compacted {add tracktype=1}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=dirt {add tracktype=3}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=mud {add tracktype=4}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=sand {add tracktype=4}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=earth {add tracktype=3}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=ground {add tracktype=3}
          tracktype!=* & surface=gravel {add tracktype=2}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=grass {add tracktype=4}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=pebblestone {add tracktype=2}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=grass_paver {add tracktype=3}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=paving_stones {add tracktype=1}
          mtb:scale!=* & tracktype!=* & sac_scale!=* & surface=paved {add tracktype=1}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=”dirt road” {add tracktype=2}
          mtb:scale!=* & sac_scale!=* & tracktype!=* & surface=dirt_road {add tracktype=2}

          • VORON_SPb

            I’m not fully agreed. I use the 29×2.35″ tyres, but often the compacted (in theory) surface means LOTS of sand (alternating with washboard), and that’s definitely not G1.

            See the gravel roads in Iceland (and in ex-USSR of course), they are “compacted”, but in the meantime may be difficult to pass even on MTB.

            • extremecarver

              so you would rather put them as g2 for openmtbmap, and g3 for velomap?

              • VORON_SPb

                You know, in absolute best possible case that may be G1/G2, but that’s quite rare outside the highly developed countries. In most cases that would be G2/G3. But quite often – down to G3/G4 (difficult to ride on MTB, impossible on other bikes). And in all cases that technically will be “compacted” surface.

                If you don’t look at tracktype and smoothness tags while assigning the G tag, that would be better to set G2/G3 on compacted roads and none on unpaved roads.

                • extremecarver

                  No – the rule is to only use surface if neither tracktype, smoothness nor sac_scale nor mtb:scale is available – else it’s dropped. In central Europa compacted is usually pretty good, but it’s not very common – or mostly also tracktype mapped. I will decrease it to G3 for openmtbmap and G4 for velomap.

                  • VORON_SPb

                    OK. Also the same solution (downgrading from G2/G3 to G3/G4) may be applied to gravel surface. In many cases it’s really rough and barely rideable on road bike. But unlike the compacted surface, large ponds or sand-covered areas rarely appear there.

                    But I don’t understand, why using the different G tags for the same road in Velomap and MTB Map? I thought that the track grade is absolute value, not relative. I mean that MTB can easily ride on G1-G3, and with difficulties on G4. The road bike can easily ride on G1-G2 and with difficulties on G3.

                  • extremecarver

                    why different – because in VeloMap it’s worse if you encounter worse condition than you expect due to the type of bike. Usually gravel is the typical G2 track though. But yes to keep it safe I will put it as G3 for Velomap.
                    And yes tracktype or smoothness is absolute – but how I interpret surface to tracktype is not.

                  • VORON_SPb

                    I use the OpenMTBmap for family bicycle touring. Mostly unpaved roads (thus asphalt-oriented navigation of Velomap is not suitable), 15 kgs on the front rack and handlebar, 17+ kgs my son, 5 kgs the bicycle seat. So I also don’t like finding the road worse than it was tagged on map. 🙂

  • pietbmw2

    hello
    can you tell on what scale these maps are??
    can’t really find it on the site , or don’t see it right now

    thanks
    piet

    • extremecarver

      On windows it’s at the top of the download list – on OSx they are hard to find – correct. CTRL-F “legend” – it’s listed under the europe countries maps with name legend.
      and well – scale doesn’t matter…

  • gbal

    Hi Felix.
    I find on Europe Map some Highway set as UCL. It seems to me that they correspond to UNCL (Unclassified) attribute mentioned in this document: http://wiki.openstreetmap.org/wiki/Key:highway
    Am I right?
    Ciao

  • gbal

    follows my previous post

  • gbal

    I could add only one pict instead the declared 3.
    Then I add the other two on next posts.

  • gbal

    Hi Felix,
    have a happy new year in first.
    I’m writing about a track type you assigned to a trail that I followed with my MTB last 31/12/2016.
    The track is classified as XBK (no bicycle or prohibited bicycle) but I saw this is instead an allowed track for the MTB because this is one of the training routes of the local MTB School as you can see on the enclosed pictures.
    Just to localize the tile or zone I show also the coordinates of a summit I reached.
    Regards
    Giulio (gbal)

  • solitone

    I’ve noticed that when the value in incline tag is numeric, mtb:scale:uphill is not rendered–i.e. if incline=15% or incline=-10%, there is no indication as to the incline on the map, even if mtb:scale:uphill is set. It works when inline=up or incline=down, though.

  • solitone

    Regarding mapping paths in OSM, when a path is not allowed to bicycles but only to pedestrians, can I use “access=no, foot=yes”, or is it better to specify “access=no, bicycles=no, foot=yes”? “bicycles=no” would be redundant, as I would already have “access=no”, but what do you think?

    • extremecarver

      Well – you should only map bicycle=no if it is explicitly forbidden (by a streetsign). access=no & foot=yes would mean the same essentially – but I won’t map the crosses to tell it’s forbidden – because I assume it’s illegal but mostly tolerated to still mtb. I.e. in Austria if mtbiking is not explicitely allowed – it is forbidden everywhere – so we have to break the law if we want to mtbike.

      • solitone

        So are you telling that bicycle=no is not rendered? I put it on a path that has an explicit sign, but I don’t see anything different from all other paths on the map, as if this tag is not actually considered.

        • extremecarver

          it depends on other tags. For pathes I usually put it in name only – not on the map as crosses. I should probably change that to only not show in Gemany and Austria – but do show in other countries.

Leave a Reply