On Sun, Nov 27, 2022 at 08:56:49PM +, 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
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 +, ael wrote:
> On Sun, Nov 27, 2022 at 04:13:44PM +, Gerd Petermann wrote:
> > Hi ael,
> >
> > the "default typ" is the one that comes with the firmware of the
On Sun, Nov 27, 2022 at 04:13:44PM +, 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
im Auftrag von ael
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 t
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
