[mkgmap-dev] mapnik typ file and barrier=wall

Wed Feb 5 10:15:10 GMT 2020

Hi all

I've also just checked this.

With a typ-file that ensures all lines in range 0x01..0x3f have a
representation, Basecamp shows nothing for:
0x17
0x2c
0x30-3f

whereas my eTrex devices show them all.

I can re-assign barrier to 0x2d, and I'd planned to use 0x2c for
"Course of old Railway", but, for these 2, Joris says:
"breaks car-routing".

@joris what are the circumstances where this happens? These will be non
-routing lines - will this cause the problem?

The other possibilities for these 2 are 0x2a/b, which gpsMapEdit call
Marine Boundary/Marine Hazard.

Then we've used up lines that Basecamp can show in what I hope is the
non-routing range. There are still some unused between 0x0d .. 0x13.

Concerning the range 0x40-0xFF:
0x51... look the same as 0x01... but with a direction label (eg
NW/S/...) on the line on my eTrex. However code in mkgmap uses the top
2 bits of the typ in some circumstances (for direction and long
-encoding) and forcing them to be set crashes mkgmap. I'm not sure if
this is a defined Garmin usage and I gave up investigating.

Ticker

On Mon, 2020-02-03 at 19:23 +0000, Gerd Petermann wrote:
> OK,
> 
> let's wait for Tickers response. IIGTR the rendering of barriers was
> introduced with r4279:
> http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4279
> 
> Gerd
> 
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag
> von Joris Bo <jorisbo at hotmail.com>
> Gesendet: Montag, 3. Februar 2020 19:23
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] mapnik typ file and barrier=wall
> 
> Hi
> 
> To share other (i don't know why) issues I once encountered.
> 
> 0x17    Does not show a line. Don't use : maybe only be used as
> transparent overlay feature
> 0x2c    If used: Lines are visible but breaks car-routing
> 0x2d    If used: Lines are visible but breaks car-routing
> 0x10201 Don't use
> 0x10202 Don't use
> 0x10b05 to 0x10b1f      No lines visible
> 
> 
> 
> Kind regards
> Joris
> 
> 
> -----Oorspronkelijk bericht-----
> Van: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> Namens Joris
> Bo
> Verzonden: maandag 3 februari 2020 19:16
> Aan: Development list for mkgmap <mkgmap-dev at lists.mkgmap.org.uk>
> Onderwerp: Re: [mkgmap-dev] mapnik typ file and barrier=wall
> 
> Hi
> 
> A comment line in my sources says: 20181219 Don't know why but lines
> are not visible. Do not use
> 
> 
> 
> -----Oorspronkelijk bericht-----
> Van: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> Namens Gerd
> Petermann
> Verzonden: zondag 2 februari 2020 09:51
> Aan: mkgmap-dev at lists.mkgmap.org.uk
> Onderwerp: [mkgmap-dev] mapnik typ file and barrier=wall
> 
> Hi TYP experts,
> 
> it seems that line type 0x17 (barrier=wall) is not visible in
> Basecamp?
> 
> Gerd
> 
> 
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev