GerdP wrote:
> ... Still not solved by this patch:
> - Memory usage depends on the highest node id in the data.
> - Node id > Integer.MAX_VALUE do not work (not a problem at this moment)
> If this small patch is okay for you, I can provide a bigger one that also
> fixes these issues, but touches many more files ...

I'm also interested in this additional fixes.
Reason: I want to integrate elevation lines.

Regards Klaus



--
View this message in context: 
http://gis.638310.n2.nabble.com/PATCH-splitter-memory-usage-tp6958659p6973800.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Reply via email to