Re: [mkgmap-dev] Wrong rendering Layer=1

Supplement : I have looked in original Garmin CityNavigator NT 2018 and Topo Espania: in both maps the layers are rendered wrong. Always the 0x1 is toplevel thomas -- Von: "Gerd Petermann" Datum: Sonntag, 25.

Re: [mkgmap-dev] Wrong rendering Layer=1

Yes I have understand your suggestion. And created a small SanIsidro.osm. Inside are only 2 ways, tagged as bridge=yes and layer=1. This 2 ways are placed at the end of osm.file. Then created a map with option --preserve-element-order . But it looks wrong. I maked 2. test : have changed the

Re: [mkgmap-dev] Wrong rendering Layer=1

Hi Thomas, what I wanted to suggest is to use --preserve-element-order and change the order of the two ways in the osm file. Without --preserve-element-order the order is not predictable, but might be the same as with the option. Gerd Von: mkgmap-dev

Re: [mkgmap-dev] Wrong rendering Layer=1

Hi Gerd, i have tested now --preserve-element-order . You are right. This does not help. The result is similar to without --preserve-element-order. thomas -- Von: "Gerd Petermann" Datum: Sonntag, 25. Februar 2018

Re: [mkgmap-dev] Wrong rendering Layer=1

Hi Thomas, my understanding is that this was already tried in the past, without success. You can test it with a test osm file containing only two ways. When you use --preserve-element-order mkgmap should write them in the order of the OSM file. It is better to use a small file for those tests so

Re: [mkgmap-dev] Wrong rendering Layer=1

Hi Arndt, sorry, I replied to Thomas' post but addressed you. Gerd Von: mkgmap-dev im Auftrag von Arndt Röhrig Gesendet: Sonntag, 25. Februar 2018 19:05:53 An: Development list for mkgmap

Re: [mkgmap-dev] Wrong rendering Layer=1

Hi Gerd,sorry, i have no idea.My workaround for oneway arrows is, to set them to 0x01 and don´t use 0x02-0x03 for other highways.openfietsmap set relations to 0x02. The relations are allways over the other ways.ArndtGerd Petermann hat am 25. Februar 2018 um 17:50 geschrieben:Hi Arndt,many OSM

Re: [mkgmap-dev] Wrong rendering Layer=1

Some time ago we have introduced the teature 'order-by-decreasing-area'. Maybee a similar arangement helps. Order all lines ,(related to streets) in range of layer . Highest layer at last ? thomas -- Von: "Gerd Petermann"

Re: [mkgmap-dev] Wrong rendering Layer=1

Hi Arndt, many OSM applications evaluate tags like bridge and layer. The default style doesn't even evaluate bridge or layer, since we don't know a way to tell Garmin software a draw order of lines. This is just a special problem with the (old) Garmin img format. Maybe there is a way to change

Re: [mkgmap-dev] Wrong rendering Layer=1

I am wondering, why we write tag=bridge and tag layer=anywhat, when mkgamp does ignore bridge=yes and layer=1. All the work, to tset this tag is seenless.? thomas Von: Arndt Röhrig Datum: Sonntag, 25. Februar 2018 14:52 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Wrong rendering

[mkgmap-dev] Commit r4129: correction: some rules with style functions were ignored

Version mkgmap-r4129 was committed by gerd on Sun, 25 Feb 2018 correction: some rules with style functions were ignored rules like a=* & is_closed()=true {...} were ignored because ExpressionArranger changed them to is_closed()=true & a=* {...} Style functions are not indexable and therefore

Re: [mkgmap-dev] Wrong rendering Layer=1

Hi,imho there is no draw prio possible with lines. Solid has no effect. Only typ 0x01, 0x02, 0x03 and perhaps 0x04 will be draw always over the other lines. I used it for one-way-arrows.Arndt"osm@pinns" hat am 25. Februar 2018 um 15:21 geschrieben: HiLayering of lines does not

Re: [mkgmap-dev] Wrong rendering Layer=1

Hi Layering of lines does not seem to be supported by Garmin - I have seen many Topos where bridges are completely ignored. Using a TYP file you can often force lines to have a draworder by making them solid - solid has often a higher draworder than lines with bitmaps. I'm not sure whether

Re: [mkgmap-dev] line rule not being triggered

Hi Gerd Thanks Gerd, that should be commited. I tried adding a test for isSolved() at the end of the ExpressionArranger and several tests failed. So there may be other problems, but it seems to me that it is isSolved() that has the problem. Needs more investigation. The current problem was

[mkgmap-dev] Wrong rendering Layer=1

Hi , maybee I found a bug in rendering layer's. I have prepared a small SanIsidro.osm.pbf and the resulting gmap with FID 982, created with mkgmap-r4127, Download : http:\\img2ms.de/Downloads\WrongLayerSanIsidro.rar . The error is, that the highway ID=217.806.076 is rendered over the bridge

Re: [mkgmap-dev] line rule not being triggered

Hi Gerd That fixes the problem Thanks Ticker On Sun, 2018-02-25 at 07:11 +, Gerd Petermann wrote: > Hi, > > the problem is in the ExpressionArranger, it changes the order of the > terms in > man_made=* & is_closed()=true {add area=yes; echotags 'mm'} > to > is_closed()=true & man_made=*