The land polygon is defined as 0x4b
and it is the only polygon with draw-prio = 1.
The sea polygon is defined as 0x32 and it has draw-prio = 2.
I have the opposite, sea prio 1 and land 2, maybe that helps?
You could also try another polygon for land, 0x27 or an extended one like
0x10100
HI Gerd, the method I've used won't work if the polygon is thinner than the
resolution of the bitmap. I hadn't considered that it might be used on
rivers; my main testing has been on car parks, which although they may be
irregularly shaped are not normally very long and very thin (I handle river
Hi Walter,
The last commands in polygons file are
natural=sea[0x32 resolution 14]
natural=land [0x4b resolution 14]
Don't use object 0x4b in style, mkgmap should create it automatically.
Use lowest priority for 0x4b in style or define only color without
giving a priority to polygon
Hi Andrzej,
I have corrected the errors in my TYP and style,
but the sea is still not visible.
Here are my last parameters.
polygons file
natural=sea { echo mapping natural=sea }[0x32
resolution 14]# level 1
natural=land
Hi Walter,
some clarifications: object 0x4b is a special kind of polygon, it is
used as a map background and covers whole map area. You should not use
it in style, because it is created by mkgmap (except for transparent
maps). You can use polygon 0x4b in TYP to change background color of a
here is the log file
info said bb box is to big
any ideas gerd and steve
stephen
splitter.log
Description: Binary data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi all,
I've committed r417 to fix a few rare problems in splitter:
1) The initial problem reported by Stephen:
splitter printed Warning: No solution found for partition ... but did not
stop when at least one partition was ok.
2) It tries a bit harder to find a solution when it turns out
that no
Hi
i'm playing around with the PT rules in relations, as example this node [1].
The node belongs to two route relations (RE8 and RB27) and one track relation
(2324)
When i enable the rules in relations i got the labels
Unkel (Re8,re8,rb27,rb27)
my wanted result is to get only one entry per
Hi Andrzej,
your suggestion to revert back to the last working version
brought me directly to the solution.
I had 2 maps in the same directory with the same TYP.
All changes I made to the TYP of one map where ignored.
The device just took the info from the TYP of the other map.
The second
Am Mittwoch, 7. Januar 2015, 18:11:29 schrieb Bernd Weigelt:
And where is my error?
Found one of my errors, because the node belongs to four route relations.
http://www.openstreetmap.org/node/31172863
ok, thats the reason for the double entries, but how can i filter them?
Bernd
10 matches
Mail list logo
