You are hereForums / Windows Software / Troubleshooting / GPX files taking very long time to import
GPX files taking very long time to import
Upon upgrading to V2.5.9, I opened a map and attempted to import a GPX file that I created previously.
On the BCN version used previously (not sure which version but downloaded ~4/2007), the previous used GPX file loaded very quickly. Now the same file is taking an extremely long time to load into BCN. The GPX file is 426K.
I looked at the directory on my SD card where the map file is located and noticed that the software is creating a file called map_file_name.db3-journal that bounces continuously from 0K to approximately 7-10K in size. When the GPX file finishes loading, this stops. Additionally, scrolling and zooming are much slower after the GPX file finishes loading.
I could be wrong, but it seems like something has changed with GPX file import on more recent BCN versions...any help/understanding on this would be appreciated.
--> When hiking/backpacking, I use a bluetooth data logger GPS to collect track information. I then download GPS data to the pocket PC, convert to GPX and import to BCN. (This minimized PPC battery use.)
Share This Page
Some things about track import have changed since April 2007. I would expect it to take somewhat longer than before but not as long as you are seeing.
I can look at with the GPX file you have if you send it to support by email.
Nathan,
Thanks for the quick response!
I did a little testing on this with PPC. I also made some small GPX files both with BCN and my GPS for comparison. Below are some observations...
So if the changes in GPX import you mention above include these temporary files, and I have a very slow SD card in terms of write speed -- these two things would probably add up to slow GPX import after I updated the software.
As a work around, it is easy enough for me to copy BCN files that I am using at a given time to PPC main memory and then transfer back after hikes/backpacking trips. I could also probably cut back on frequency of GPS data collection to reduce GPX file sizes. :)
If any of this sounds reasonable, there is probably no need for you to work with my GPX file. (I'll still send it to Support email if you want...)
Thanks, Rick
BTW - I really like this software..great work!!![/]
sadly, it's now July 2009 and this problem is still with us. Loading a gpx file still takes forever. I like BCN, but as I accumulate more gpx files, and try to swap them in and out, the program has gotten to where it is almost unusable. This needs to be the highest priority for a fix.
The mysteriously reappearing file turned out to be the right clue, although I wasn't able to reproduce that in January. I'd been looking in the wrong direction in the last month.
Although I'm not deliberately creating temporary files for each row, SQLite database engine does. While you can't completely avoid that and still have transactional safety, you can change the granularity.
A GPX file that used to take 4 minute now takes about 17 seconds to import in version 2.7.7. It is still slower than the desktop which is pretty much instantaneous.
This may not be the end of the matter but it is some progress forward.
Yes, 2.7.7 solved the problem for me! Thanks for the great support.
K