Cannot save a new file...

[RsH]

I dragged in all of the days of our trip to Ogden UT last year and have a file with 214927 points or positions. When I try to save as a GPX file I get a message that it ran out of Java Heap Space. When I try to save as a CSV file I get a null error. How do I save this new file so that I can use it in its new, complete trip, form? I am NOT a java expert and have no idea how I could increase the java heap space, nor should I need to even consider that as a raw user of RouteConverter <grin>... Yes, I know I take long trips!

[routeconverter]

I am NOT a java expert and have no idea how I could increase the java heap space, nor should I need to even consider that as a raw user of RouteConverter <grin>... Yes, I know I take long trips!

Hello Robert,

don't expect simple solutions if you're that far away from the typical usage patterns Your tracks are several hundert times longer than the typical tracks that RouteConverter users send me.

So you have to become an expert. The first interesting information is that I have limited the heap memory a RouteConverter.exe can consume to 256 MByte. Quite frankly I don't know how many GPX or NMEA positions may be processed with that but it should be enough for 20000 or 30000 positions.

To increate the heap size that RouteConverter might use, download the RouteConverter.jar version and start it with

java -mx1024m -jar RouteConverter.jar

from the command line to increase the maximum heap to 1 GByte (1024 MByte). If you like you can put the line above into a file called RC.bat and you can avoid opening the command line each time you load or save larger tracks.

I hope this helps.

[RsH]

I am NOT a java expert and have no idea how I could increase the java heap space, nor should I need to even consider that as a raw user of RouteConverter <grin>... Yes, I know I take long trips!

Hello Robert,

don't expect simple solutions if you're that far away from the typical usage patterns Your tracks are several hundert times longer than the typical tracks that RouteConverter users send me.

So you have to become an expert. The first interesting information is that I have limited the heap memory a RouteConverter.exe can consume to 256 MByte. Quite frankly I don't know how many GPX or NMEA positions may be processed with that but it should be enough for 20000 or 30000 positions.

To increate the heap size that RouteConverter might use, download the RouteConverter.jar version and start it with

java -mx1024m -jar RouteConverter.jar

from the command line to increase the maximum heap to 1 GByte (1024 MByte). If you like you can put the line above into a file called RC.bat and you can avoid opening the command line each time you load or save larger tracks.

I hope this helps.

I removed the duplicates, which cut it down to the 140,000 point area, and then it loaded <grin> so I too don't know what the limit is, other than it is between those two values. Anyway, since it worked without the duplicates from when the car was stopped, I no longer need to use the other method. Thanks anyway.