[GraphHopper] New version 0.2 questions

[Peter K]

Hey,

they should be cleaned up automatically, so yes, you are safe to remove 
them. There is a bug for windows - which OS are you using?

Regards,
Peter.

> Thank you for your answer Peter.
>
> After generation there are two generated file with a name something
> like  "tmpLatitude" and "tmpLongitude" with size of about 150MB each.
> They seem to be temporary file used for graph generation. I removed
> these files and rooting continue working.
> Can I safely do that for each other graph?
>
> Regards.
>
>
> 2013/11/21 Peter K <peathal at yahoo.de <mailto:peathal at yahoo.de>>
>
>     Hi Max,
>
>     the settings in config.properties is obviously only for the
>     creation of the graph. As on Android you only have 32MB ...
>
>     If you look in the Android code you see the call
>     graphhopper.forMobile() which calls setMemoryMapped() which is
>     equivalent to MMAP_STORE in the config.properties
>
>     BTW: MMAP_STORE_SYNC is a bit slower and only necessary if you
>     want to use the MMAP option for the server to guarantee
>     read-thread safety
>
>
>     > Maybe I need to increase memory JVM with*/-Xmx../. *option for
>     pass the lack of memory heap at graph generation step ?
>
>     If you increase it it should work. e.g. via
>
>     export JAVA_OPTS="-Xmx..."; ./graphhopper.sh ...
>
>
>     Regards,
>     Peter.
>
>
>>     Hello,
>>
>>     I tested the new version 0.2 on my Android device.
>>     So I was forced to generate new graph because of the new version
>>     of node (V2)
>>
>>     I want to understand the difference between the two following
>>     option in config file:
>>
>>     */# graph.dataaccess=MMAP_STORE_SYNC/*
>>     */graph.dataaccess=RAM_STORE/*
>>
>>     I tested to generate /France/ graph (which is big) with
>>     */graph.dataaccess=RAM_STORE/* but the process stoped because of
>>     lack of memory heap...
>>
>>     So i change this property to */graph.dataaccess=MMAP_STORE_SYNC/*
>>     and the process finished correctly and the graph works and my
>>     Android device. The time for generate was approximatly 50minutes
>>     (I7 dual core and SSD) for information.
>>
>>     So I want to know if this option only impact graph generation and
>>     not impact runtime execution?
>>     If there is runtime impact (speed or something else) can I
>>     use /graph.dataaccess=RAM_STORE /for android with big graph like
>>     the one for France?
>>     /
>>     /
>>     Maybe I need to increase memory JVM with*/-Xmx../. *option for
>>     pass the lack of memory heap at graph generation step ?
>>
>>     Otherwise good Job, GPS exact routing is perffect :)
>>     Waiting for perfect thing with turn restriction ;)
>>
>>     Regards.
>>
>>     Max
>>
>>
>>
>>
>>
>>     _______________________________________________
>>     GraphHopper mailing list
>>     GraphHopper at openstreetmap.org <mailto:GraphHopper at openstreetmap.org>
>>     https://lists.openstreetmap.org/listinfo/graphhopper
>
>
>     _______________________________________________
>     GraphHopper mailing list
>     GraphHopper at openstreetmap.org <mailto:GraphHopper at openstreetmap.org>
>     https://lists.openstreetmap.org/listinfo/graphhopper
>
>
>
>
> _______________________________________________
> GraphHopper mailing list
> GraphHopper at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/graphhopper