Hi,
I am getting the splitter from svn, compiling and running it unter
Windows XP SP3 using JDK 1.6.0_25. There are 2 problems if I am using a
splitter version newer than r161 (tryed until r167 so far).
1.) germany.osm.pbf from geofabrik cannot be split
--
Le 03/03/2011 00:36, Michael Prinzing a écrit :
Hi,
> 1.) germany.osm.pbf from geofabrik cannot be split
> --
>
> MAP occupancy: 1
> Elapsed time: 22m 2s Memory: Current 1484MB (1144MB used, 340MB free) Max
> 1484MB
> Elapsed time: 24m 2s Memo
On Wed, Mar 2, 2011 at 5:36 PM, Michael Prinzing wrote:
> Hi,
>
> I am getting the splitter from svn, compiling and running it unter
> Windows XP SP3 using JDK 1.6.0_25. There are 2 problems if I am using a
> splitter version newer than r161 (tryed until r167 so far).
>
>
> 1.) germany.osm.pbf fro
On Thu, 03 Mar 2011 00:36:10 +0100, Michael Prinzing wrote:
>2.) File containing contour data cannot be processed
>
The problem that the splitter did not finish with only a single thread
is solved now, but the problem with the splitter crashing
On Thu, 3 Mar 2011 21:16:26 -0600, Scott Crosby wrote:
>On Wed, Mar 2, 2011 at 5:36 PM, Michael Prinzing wrote:
>> I am getting the splitter from svn, compiling and running it unter
>> Windows XP SP3 using JDK 1.6.0_25. There are 2 problems if I am using a
>> splitter version newer than r161 (try
On Fri, Mar 4, 2011 at 6:12 PM, Michael Prinzing wrote:
> On Thu, 3 Mar 2011 21:16:26 -0600, Scott Crosby wrote:
>>On Wed, Mar 2, 2011 at 5:36 PM, Michael Prinzing wrote:
>
>
> If the node IDs are starting at 2073741824 (= 2^30 + 1e09) there is
> still an exception. It happens immediately when t
Hi Micheal,
I tried your data to verify that it can be processed with my patched version
in the memory_optimization branch. Unfortunately it seems that splitter has
another problem not related to memory or high node id values:
During the 1st phase, the program stops reading nodes too early. Result
