Why does the default typ not render cycleways?
Just a quick question: when I compile with default style and typ, cycleways are not rendered. I need to use, say, mapnik.txt to see them. So far as my very limited understanding reaches, the default style has highway=cycleway [0x11 road_class=0 road_speed=1 resolution 23] garmin type 0x11. So far so good (and mapnik picks that up). But the default typ seems to ignore 0x11, although I cannot find that specification just now. Have I missed something? Why don't the defaults render things so significant as cycleways? This seems to have been the case for at least a year. ael
Hi ael, the "default typ" is the one that comes with the firmware of the Garmin device. On my Oregon 600 the type 0x11 is also not rendered very well, maybe it is rendered as white line or not at all, not sure what it is. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von ael <witwall3@disroot.org> Gesendet: Sonntag, 27. November 2022 16:23 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: [mkgmap-dev] Why does the default typ not render cycleways? Just a quick question: when I compile with default style and typ, cycleways are not rendered. I need to use, say, mapnik.txt to see them. So far as my very limited understanding reaches, the default style has highway=cycleway [0x11 road_class=0 road_speed=1 resolution 23] garmin type 0x11. So far so good (and mapnik picks that up). But the default typ seems to ignore 0x11, although I cannot find that specification just now. Have I missed something? Why don't the defaults render things so significant as cycleways? This seems to have been the case for at least a year. ael _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Sun, Nov 27, 2022 at 04:13:44PM +0000, Gerd Petermann wrote:
Hi ael,
the "default typ" is the one that comes with the firmware of the Garmin device. On my Oregon 600 the type 0x11 is also not rendered very well, maybe it is rendered as white line or not at all, not sure what it is.
Thanks for the reply. I didn't realise that. If the default is not extended, I think the documentation for mkgmap ought to mention that a explicit typ is needed, especially for newcomers as I suggested in another reply. ael
Hi 0x11 is rendered as a thin black line on my eTrex HCx and a white line on my eTrex 30x Ticker On Sun, 2022-11-27 at 17:35 +0000, ael wrote:
On Sun, Nov 27, 2022 at 04:13:44PM +0000, Gerd Petermann wrote:
Hi ael,
the "default typ" is the one that comes with the firmware of the Garmin device. On my Oregon 600 the type 0x11 is also not rendered very well, maybe it is rendered as white line or not at all, not sure what it is.
Thanks for the reply. I didn't realise that. If the default is not extended, I think the documentation for mkgmap ought to mention that a explicit typ is needed, especially for newcomers as I suggested in another reply.
ael
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Sun, Nov 27, 2022 at 08:56:49PM +0000, Ticker Berkin wrote:
Hi
0x11 is rendered as a thin black line on my eTrex HCx and a white line on my eTrex 30x
Checked carefully on my etrex 20 and see that the default is actually a white line: I missed it because I was checking a cycle path on a white background. My basic problem is that I did not realise that mkgmap by default left the firmware to its own devices... ael
participants (3)
-
ael -
Gerd Petermann -
Ticker Berkin