Hi Carlos,
the tricky part here is that -tdbfile is enabled by default. I don't remember
why this was done, and I don't know why it is not documented, but you can use
--no-tdbfile to overwrite the default.
Gerd
Von: mkgmap-dev im Auftrag von Carlos
Dá
According to options file, --overview-mapname and --overview-mapnumber
parameters should only have an effect "If --tdbfile is enabled...", but
they seem to be always taken into account regardless of --tdbfile, as
can be checked with command: java -jar mkgmap.jar --gmapsupp
--overview-mapname=t
Hi Gerd
I think this might be the reason why you backed out the Polish
inner/outer definition changes:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2019q1/029478.html
Maybe there needs to be an option to say how multiple DATA{sameLevel}
should be handled:
a/ first outer, following inners.
b/ ou
Hi Ticker,
reg. polish input: There was code based on the documentation and I removed it
again. Don't remember why, see changes for r4269 and r4272 and
http://gis.19327.n8.nabble.com/Artifacts-in-final-map-MP-gt-IMG-conversion-tc5932812.html
The current code is really too complex. A lot of the c
Hi Gerd
Looking at the Polish format (cGPSmapper-UsrMan-v02.4.pdf), my
understanding is that a polygon definition with multiple Data#
statements at the same level defines a single outer with multiple
inners (Page 20 and 74/5).
Touching inner or outer rings is a slightly different problem and, I
t
Hi Ticker,
I don't know what data we see when MultipolygonRelation is used with polish
input, but I am sure that there is no info about roles.
I also thought about using the info about the area size as a quick indicator
before doing complex tests.
The missing unit tests are my real problem. I'
