Hi Mark,
(Let me introduce myself: hi, I'm the original problem submitter :)
Mark Burton schreef:
Well, that's a bit odd. If you download this area into
JOSM, it looks similar(ish) but by no means exactly the same.
Yep, that's what I did last night: open just the area around the problem
site
Clarification:
Valentijn Sessink schreef:
running splitter like in my script, then just building a map of the
isolated map number 1 produces the same results
... produces a wrong map is what I meant to say.
Valentijn
___
mkgmap-dev mailing list
Mark,
Mark Burton schreef:
I grabbed the source as you suggested but could not successfully
create a map when the splitter had max-nodes = 100. One of the
tiles failed in mkgmap (exception - NET1 offset too big, I think).
Shame on me. Yes, the offset too large was just what I encountered
Hi,
I promise to never again turn assertions off.
Yes, unless you are desperate to save time, I would always keep
assertions turned on. After all, mkgmap is a work in progress and it's
bound to have issues - some of which the assertions will catch.
The real issue here is surely why aren't we
Version 1082 was commited by markb on 2009-07-09 17:25:22 +0100 (Thu, 09 Jul
2009)
Added --keep-going option to continue processing when a job fails.
Actually, this was the default behaviour before but it would be better
for the default to be that the application quits unless you specify
this
I had several problems with the rendering of multipolygons on my Garmin
Mobile XT. So I made a small patch. See attachment.
Problem 1:
Simple holes in a polygon are rendered correctly, but if the inner polygon
has additional tags then this information is not rendered. In my example
(Chiemsee in
Nop schrieb:
But now the real problem starts: How do I use the contour functions?
You say: - Now the OSM styling engine is used to set labels, types
resolution of the contour lines.
How does this work? What rules are required? How can I distinguish
between minor and major lines, I did
