Error loading kml file

Hi,

trying to load a kml file generated by www.poi66.com I get an "Error loading file".

After that when touching the touchscreen OruxMaps get an java.lang.OutOfMemoryError in Bitmap.java, called from aid.handleMessage(Sourcefile 91).

The kml file is 4MB big so I can see how that happens

RichZ wrote:Hi,

trying to load a kml file generated by www.poi66.com I get an "Error loading file".

After that when touching the touchscreen OruxMaps get an java.lang.OutOfMemoryError in Bitmap.java, called from aid.handleMessage(Sourcefile 91).

The kml file is 4MB big so I can see how that happens

Hi

It should not happen with android version> 4.0.
But it is possible with older versions, there is an important limitation of memory on these devices

orux

orux wrote:
Hi

It should not happen with android version> 4.0.
But it is possible with older versions, there is an important limitation of memory on these devices

orux

yes, it is a 2.3.x device.

However I noticed that even when I split the file to parts around 300K there are still plenty of problems and oruxmaps seems to require more memory than with much larger kml files from other sources.
Any ideas if specific kml constructs could be using up more memory than expected? The entries look pretty bloated for my eye.

poi66.com also can export to following formats:
* Tomtom POI OV2
* Tomtom POI ASC
* Tomtom ITN ITN
* Google Earth KML
* Google Earth KMZ
* EasyGps GPX
* OziExplorer RTE
* OziExplorer PLT
* MioMap MIO
* Excel (NL) XLS
* Excel (UK/US) XLS
* Fugawi GPS TXT
* Navigon RTE
* Kompass Verlag TK
* Overlay OVL
* MagicMaps IKT
* Garmin Nuvi CSV
* Garmin CRS CRS
* !BETA! MioMapv3/IGo UPD
* !SOON! Sygic UPI

which ones would be best to try?

I have now tried the csv format and used gpsbabel to convert to a fairly celan and minimal kml file. Still impossible to load the file.

I am concluding that the underlying xml parsing library has a severe memory leak. Frequently the crashes occur some time after a kml file has been loaded.

Loading 1000 simple points corrsponding to approximately 40-50K packed information should never cause out of memory problems.