Hi,
in case you have trouble with reproducing the problem, there is java option
-XX:-HeapDumpOnOutOfMemoryError. Uli can run splitter with this option and
then send you produced hprof file which you can open in MemoryAnalyzer or
jhat. There you will see all allocated objects, what takes most
Hi Uli,
please tell me also how you create the file containing iceland.
If you have kept the log files, please send them also.
Gerd
--
View this message in context:
http://gis.19327.n5.nabble.com/splitter-improvements-tp5735718p5735727.html
Sent from the Mkgmap Development mailing list
Hello Jiri,
thanks for the hint. I tried that in the past, but the dump was far too large
and jhat always crashed. All versions r225 to r231 allocate millions of small
objects.
Will see if it helps now.
Gerd
Date: Wed, 14 Nov 2012 11:02:03 +0100
From: jiri.klem...@gmail.com
To:
Hi Uli,
thanks for the hint. I just found out that the error is in the
problem-list-generator. It use the wrong test to detect whether a way is a
problem candidate or not.
As a result, it adds far too many ways to the list.
Gerd
Date: Tue, 13 Nov 2012 18:15:43 +0100
From:
Hi,
MemoryAnalyzer is much more memory effective than jhat. It usually needs
about the same amount of memory as is size of heap dump.
--
Jiri
On Wed, Nov 14, 2012 at 11:15 AM, Gerd Petermann
gpetermann_muenc...@hotmail.com wrote:
Hello Jiri,
thanks for the hint. I tried that in the past,
Hi Gerd,
this is the way i create the germany + 50km + iceland .osm.pbf-file:
First step is download from geofabrik (only about once a month):
..\bin\wget --no-cache http://download.geofabrik.de/openstreetmap/europe.osm.pbf
Then i cut the interesting area(s), i'll attach the corresponding
In running a macro I have used many times before with a new download
from geofabrik, splitter gave me the following error. (I realise that
there is no need to split the file in this particular case, but it has
never caused problems before.) I am not sure of the version of splitter
I am using,
Hello Roger,
you are running an out-aged version of splitter. Please update to the latest
stable version: r202
http://www.mkgmap.org.uk/splitter/
Ciao,
Gerd
Roger Calvert wrote
In running a macro I have used many times before with a new download
from geofabrik, splitter gave me the
Hi Gerd,
i just tried it once again using splitter-r231.
This is the error, that occurs:
23.000.000 ways processed... id=175802045
24.000.000 ways processed... id=184296766
Stats for MultiTileProcessor pass 2 endMap Pass2 end
SparseBitSet problemRels 173576 (917000 bytes)
SparseBitSet
UliBär (Gmail) wrote
Hi Gerd,
i just tried it once again using splitter-r231.
Hi Uli,
I fixed the error with r232 which I've just committed.
Thanks for reporting !
Gerd
--
View this message in context:
http://gis.19327.n5.nabble.com/splitter-improvements-tp5735785p5735791.html
Sent
Hi all,
if you are testing the --keep-complete or the --problem-list option,
please update to r232.
The older versions in the branch are known to have stupid bugs causing
extreme memory needs (and possibly long run times).
Example: the DACH extract is now handled on a 32bit machine with
Thanks, Gerd. That solved the problem.
I have another, more general, query: will the improvements currently
being made to Splitter to handle problem polygons remove or reduce the
need for pre-compiled sea (whose purpose seems to be to prevent flooding
resulting from faulty coastlines) in
Hi Uli,
I fixed the error with r232 which I've just committed.
Thanks for reporting !
Gerd
Hi Gerd,
you're welcome! :)
Only minutes ago splitter-r232 just flew thru the germany+ dataset on
a 32-bit-environment using -Xmx1376m without a single problem!
The problem-candidates-list sizes
Hello Roger,
I really don't know. If I got that right, flooding is caused by different
reasons:
1) wrong OSM data
2) incomplete OSM data caused by splitting planet using e.g. osmosis or other
tools
3) incomplete OSM data caused by splitter
Even with a perfect error free splitter you will
Sounds like a release candidate ... I will run some tests with it.
Klaus
--
View this message in context:
http://gis.19327.n5.nabble.com/splitter-r232-tp5735799p5735825.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
___
Hi,
On Wed, Nov 14, GerdP wrote:
Hi all,
if you are testing the --keep-complete or the --problem-list option,
please update to r232.
The older versions in the branch are known to have stupid bugs causing
extreme memory needs (and possibly long run times).
Example: the DACH extract
Hello Thorsten,
Thorsten Kukuk wrote
But for europe, 6000M are no longer enough, I'm currently
trying it with more memory.
please send me both logs.
Gerd
--
View this message in context:
http://gis.19327.n5.nabble.com/splitter-r232-tp5735799p5735831.html
Sent from the Mkgmap Development
El 12/11/12 16:41, Carlos Dávila escribió:
El 12/11/12 11:36, Steve Ratcliffe escribió:
Hi
Any idea why these differences happen and how to fix them? Why some
POI/Countries are not found?
I will have a look at your map and see if anything could be changed
to make it
What about reading o5m Files an writing pbf with r232 ?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
fla...@googlemail.com wrote
What about reading o5m Files an writing pbf with r232 ?
___
mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Maybe I don't understand the question. This works fine with r232.
Hi
Mapsource and the devices do work very differently when it comes to
searching and it is possible that there is nothing that can be done
easily.
I'm aware of such differences, but I had not faced a case like this one
before, with missing countries (can't type Cuba on nuvi 300 address
El 14/11/12 23:41, Steve Ratcliffe escribió:
With maps created before r2335, are the POIs findable on both
mapsource and the device or missing on both?
Too late for me tonight. Will check tomorrow and report.
___
mkgmap-dev mailing list
Hi Klaus,
Sounds like a release candidate ... I will run some tests with it.
not yet, but test results regarding the output are welcome.
I am working on an improvement regarding memory usage in the MultiTileAnalyzer,
so performance tests can wait.
I plan to add a restriction regarding
23 matches
Mail list logo
