Hi Andrzej,
What bothers me is that such a polygon in an *.mp file will suppress the
generated rectangular 0x4b shape
but with osm input it would still be added unless you use --transparent which
will also set a flag in the TRE header
(PoiDisplayFlags)
I think it would be no problem to have a r
Hi Ticker,
can you explain this a bit, please?
I don't understand what RW8 means, but it seems that you have many named
barriers in your area?
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Montag, 27. März 2017 14:59:26
An: mkgmap-dev@lis
Version mkgmap-r3871 was committed by gerd on Tue, 28 Mar 2017
merge the if-then branch
It brings three changes:
1) It adds if-then-else syntax for styles, might be useful for doing this:
if (mkgmap:option:routing=car) then
include "inc/car-rules";
end
2) It adds the new option --style-op
I have this in my style - as a change from default style- works nicely:
#RWB barrier=bollard | barrier=bus_trap | barrier=gate [0x660f
resolution 24]
#RWB barrier=block | barrier=cycle_barrier | barrier=stile |
barrier=kissing_gate [0x660f resolution 24]
#RWB get lots of Unnamed Pillar.
#RWB Also
Version mkgmap-r3870 was committed by gerd on Mon, 27 Mar 2017
code cleanup, no functional change: reduce duplicated code for different OSM
formats, get rid of PrecompSeaElementSaver
to be continued.
There should be no need for classes like Osm5PrecompSeaDataSource
or O5mBinBoundaryDataSource,
