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
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 encounte
Hi Valentijn,
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).
I tried again with max-nodes = 50 and now I have a complete map.
Looking at i
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
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
Hi Steve,
Well, that's a bit odd. If you download this area into
JOSM, it looks similar(ish) but by no means exactly the same. If you
then run that area through mkgmap and look at the result with
mapsource, it looks OK. I am wondering if the map image in the email
was made from out of date OSM da
Hi
I'm am forwarding this email, with permission, in the hope that someone
can help before I able to look at it at the weekend.
- Forwarded message from Valentijn
Date: Wed, 08 Jul 2009 10:47:43 +0100
Subject: OpenStreetMap e-mail - mkgmap bug report
Hello Steve,
Marvellous piece of work
