Hi!
I want to make an installer for the Mapsource version of a map covering
Europe completely.
The nsis option produces a *.nsi file. But when trying to build the
installer NSIS produces an error:
File: 63240417.img
Internal compiler error #12345: error mmapping file (2130809330,
On Mon, Mar 12, GerdP wrote:
1) Enhance the logic in mkgmap that guesses how the missing ways completed
the multipolygon, e.g. by adding a backtracking algorithmn (this is already
suggested in the code).
2) Enhance splitter so that it writes all points and all ways of
multipolygon to each
Am 13.03.2012 06:59, schrieb GerdP:
3) Enhance splitter to write one extra output file that contains only the
1st and last point of each way that is part of a multipolygon, and create a
method in mkgmap that looks for this data when
it doesn't find the way in the normal input. We need only the
Hello
Internal compiler error #12345: error mmapping file (2130809330,
2889216) is out of range.
Maybe this is because my map is larger than 2GB.
What can I do about it?
Yes it seems that NSIS has a 2GB limit on a single file. There are
various plugins available that allow you to split
Hi Henning,
well, I think this can be done, but I see two problems:
1) Splitter would have to write the data in OSM format, means, it has to
invent some ways, nodes and the ids for them. I think we cannot simply
invent nodes for existing OSM ways.
2) I think the data structures in splitter don't
Hi WanMil,
it's a combination of errors. OSM data is incorrect because it contains two
admin-level 4
boundaries that intersect (r1561776 and r349048) The program is incorrect
because it doesn't
tag this intersection with admin-level 2 information.
The trunk version doesn't care about
Hi WanMil,
okay, works fine for me.
Gerd
WanMil wrote
Gerd,
I have commited your patch plus the header length implementation. The
int for the record layout should give the format of the records not the
header. So I don't see a reason to change the record layout id if I just
want to
For my Europe and Germany maps I use the following NSIS template:
http://mijndev.openstreetmap.nl/~ligfietser/diverse/installer_template.nsi
Put this file installer_template.nsi in the resources subdirectory where you
run mkgmap.
If you compile the map tiles, it only creates a small install /
that's an easy but not elegant solution (in principle you just need to
comment all File commands for your map files and decide if you want to
pack the mapset files into the installer, or leave them outside). As
one first has to unzip it, well and people will not understand about
moving/copying
I agree my method isn't for dummies, but it is much quicker to see your map (it
skips the time for compression / decompression by nsis). Besides this, all
tiles are available for Linux users or Mac users (just convert the zip file
with Javawa's Mapconverter)
I agree it's quicker, as the NSIS unpacker/packer for lzma is much
(about factor 2) slower than 7zip
but also nsis lzma converted .exe can easily be unpacked by 7zip...
(rests of course the 2GB limitation)...
On 13.03.2012 15:23, Minko wrote:
I agree my method isn't for dummies, but it is
Hi Thorsten,
thanks for the qucick feedback.
Date: Tue, 13 Mar 2012 09:07:18 +0100
From: ku...@suse.de
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem with splitter
On Mon, Mar 12, GerdP wrote:
1) Enhance the logic in mkgmap that guesses how the missing ways
Hello,
I excuse in advance if this is not the good email for the question.
Recently when I route on my Etrex Vista the map is displayed over on the
purple line that shows the road to take. I am very sure that before the
purple line was over.
The problem is now routing is not utile anymore to me
Hi Gerd,
On Tue, Mar 13, Gerd Petermann wrote:
I'm not that sure option 2 will really blow up the tile size and
CPU cost. Today, most people creating a map use a very huge number
for --overlap to avoid this kind of problems. And how many multipolygons
are really that big that they go
Maybe splitter could detect, if a tile is completely inside such a
polygon and then only add a rectangle with a negative ID (or parse for
highest used node/way-ID).
At all I think, that needed diskspace isn't a huge problem, if there is
no more guessing.
Henning
Am 13.03.2012 16:06, schrieb
Hi,
the current implementation of splitter doesn't even try to detect if a polygon
contains
a split tile. In short it works like this:
a) read osm data and calculate the tile areas.
b) Close file and start reading again
c) Distribute all nodes, each node is written to a maximum of 4 different
Hi WanMil,
attached is a patch that changes the logic in BoundaryQuadTree to
solve the problem around the canarian islands.
You have to create new *.bnd files.
Gerd
http://gis.19327.n5.nabble.com/file/n5561676/missing_admlevel2.patch
missing_admlevel2.patch
--
View this message in context:
Works good for me!
Thanks!
WanMil
Hi WanMil,
attached is a patch that changes the logic in BoundaryQuadTree to
solve the problem around the canarian islands.
You have to create new *.bnd files.
Gerd
http://gis.19327.n5.nabble.com/file/n5561676/missing_admlevel2.patch
18 matches
Mail list logo
