[mkgmap-dev] [PATCH]splitter memory usageFrom GerdP gpetermann_muenchen at hotmail.com on Tue Nov 8 21:43:29 GMT 2011
toc-rox wrote: > > > 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 > I fear I don't understand why elevation lines are a problem for version 181 so maybe my version will not work with that as well. What do I have to test to verify it? Gerd -- View this message in context: http://gis.638310.n2.nabble.com/PATCH-splitter-memory-usage-tp6958659p6976044.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
- Previous message: [mkgmap-dev] [PATCH]splitter memory usage
- Next message: [mkgmap-dev] value (string) handling via style file
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list