I have noticed that the default style allocates code 0x07 to both bridleways and service roads. This means they come out looking the same on devices (I identified this in the field on my GPSmap60CSx, and confirmed it with MapSource and Basecamp, before finding it in the 'lines' file). In my view, it would be better to use either 0x16 (footway/path) or 0x0a (track) for bridleway, with appropriate permissions. But would this have routing implications? (I am a walker, not a rider or cyclist, so I'm not directly concerned about routing.) I can of course modify my copy of the 'lines' file, but is there a case for changing the default? Roger -- ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------
Roger Calvert wrote:
In my view, it would be better to use either 0x16 (footway/path) or 0x0a (track) for bridleway, with appropriate permissions. But would this have routing implications?
FWIW I've always used 0x16 for bridleways and it has not impacted foot or car routing. Cheers, Andy
+1 We use 0x16 in the adapted default style for Lambertus Generic Routable (new style) too.
On Sun, Apr 07, 2013 at 12:16:12PM +0200, Minko wrote:
+1 We use 0x16 in the adapted default style for Lambertus Generic Routable (new style) too.
OK, I will change it in a few days, unless there is objection from someone. BTW, highway=proposed was being generated as a highway until yesterday. I added {delete highway; delete junction} action for it in order to get rid of warnings about broken roundabout flare roads, when a proposed roundabout was in the middle of a conventional 4-way intersection. Marko
Just a thought. If I wanted to remove the possibility of using a none-routable line type in my style file for routable lines; would routing still work if you just used a single line type for routing purposes? This could point to a transparent line in the type file and would need a continue statement after defining the road class and speed, then use an overlay later on to show the actual symbol to use for that line which could be in the extended set. It would make the compilation of the map a bit longer, but could remove some frustration when adding a new line type to a map when a none-routable line type is chosen. Roger, like you I am a walker, but I love being able to auto-route down footways, bridleways as well as roads in Mapsource/Basecamp for the ease of generating long circular walks with just a couple of handfuls of mouse clicks. Geoff. -----Original Message----- From: MarkoMäkelä Sent: Sunday, April 07, 2013 5:47 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] Default style for Bridleway On Sun, Apr 07, 2013 at 12:16:12PM +0200, Minko wrote:
+1 We use 0x16 in the adapted default style for Lambertus Generic Routable (new style) too.
OK, I will change it in a few days, unless there is objection from someone. BTW, highway=proposed was being generated as a highway until yesterday. I added {delete highway; delete junction} action for it in order to get rid of warnings about broken roundabout flare roads, when a proposed roundabout was in the middle of a conventional 4-way intersection. Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (5)
-
Geoff Sherlock -
Marko Mäkelä -
Minko -
Roger Calvert -
SomeoneElse