logo separator

[mkgmap-dev] memory requirements for generating planet bounds

From GerdP gpetermann_muenchen at hotmail.com on Thu Feb 14 20:24:44 GMT 2013

Hi Thorsten,

this reminds me on the osmid_v1.patch using fastutil.jar
It is esp. usefull in this case because the memory requirements are caused
by
the huge number of coords.

@Steve: Do you still plan to add it ?

Gerd 


Thorsten Kukuk wrote
> Hi,
> 
> On Thu, Feb 14, Rich wrote:
> 
>> as per 
>> http://wiki.openstreetmap.org/wiki/Mkgmap/help/options#Using_preprocessed_bounds_for_the_address_index 
>> , i tried to generate bounds myself from a planet boundary extract 
>> (prepared with osmconvert/osmfilter like in the instructions on the same 
>> page).
>> 
>> java -cp mkgmap.jar 
>> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryPreprocessor 
>> 
> <inputfile>
>  
> <boundsdirectory>
>> 
>> that run out of the heap space of 2300 megs. before i try experimenting 
>> further, how much heap space is required for creating planet bounds from 
>> boundary extract ? :)
> 
> You need at least 8GB of free RAM. And I would suggest Sun/Oracle Java,
> not IBM Java or openjdk.
> 
>   Thorsten
> 
> -- 
> Thorsten Kukuk, Project Manager/Release Manager SLES
> SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev at .org

> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev





--
View this message in context: http://gis.19327.n5.nabble.com/memory-requirements-for-generating-planet-bounds-tp5749408p5749453.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.


More information about the mkgmap-dev mailing list