[mkgmap-dev] Runways on highways
From Marko Mäkelä marko.makela at iki.fi on Sun Jun 6 20:45:12 BST 2010
Someone notified me that this highway that serves as a temporary runway during military exercises is not being considered for routing: http://www.openstreetmap.org/browse/way/45772320 aeroway = runway highway = primary name = Turuntie ref = 41 The obvious reason is that in styles/default/lines, aeroway=runway comes before any highway=* tags. I confirmed the non-routeability on my Edge 705, and my fix sort of worked: Index: resources/styles/default/lines =================================================================== --- resources/styles/default/lines (revision 1652) +++ resources/styles/default/lines (working copy) @@ -8,8 +8,8 @@ # and http://wiki.openstreetmap.org/wiki/Mkgmap/help/Custom_styles # for more information. -aeroway=runway [0x27 resolution 20] -aeroway=taxiway [0x27 resolution 24] +aeroway=runway [0x27 resolution 20 continue] +aeroway=taxiway [0x27 resolution 24 continue] # Contours take their name from the elevation setting. contour=elevation & contour_ext=elevation_minor I would have preferred to see the runway on top of the highway, but the Edge 705 rendered only the highway. In other words, the Garmin line for the aeroway=runway object is just wasting memory. QLandkarteGT showed both lines on top of each other. I think that we should just move the aeroway=* rules below highway=* so that any highways that serve as temporary airfields will be translated as highways. Any objections to that? Are there any aeroway=* that are also tagged as highway=service, for example? Should they require some special treatment? Marko
- Previous message: [mkgmap-dev] splitter coordinates
- Next message: [mkgmap-dev] Runways on highways
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list