Select to view content in your preferred language

ArcPad 10.0 R2 large tracklog re-drawing extremely slowly

2395
2
08-25-2011 12:54 AM
JohnLucas
Deactivated User
I have an application which requires the tracklog to  log 1 per second for up to 10 hours. This was never a problem in ArcPad 8 but in 10 it takes up to 2-3 minutes to redraw.
when moving the screen needs to refresh so the tracklog never actually completes the redraw.
Loading the file as a normal layer has it displaying instantaneously.

I've tried it on a number of computers with the same result.  any ideas.

Cheers

jlucas
Tags (3)
0 Kudos
2 Replies
EddieViljoen
Deactivated User
Hi John

I had exactly the same problem, and the only way that I could fix this was by implementing my own (text-file) tracklock, where I append the track points.

Fortunately I did not have to display it on Arcpad as it is captured, so the append to text file is very quick.

Eddie
0 Kudos
TimHopper
Frequent Contributor
There are a few bugs logged on this behavior.  I'll explain the nuts and bolts below.

Back towards ArcPad 7.1.1 there was a substantial amount of available memory given to the tracklog.  This caused the tracklog to draw extremely fast.  What was found, however, was that the location of the GPS cursor was lagging behind the location of your actual gps position.

To make the location of the gps cursor as accurate as possible, some of that memory which was once allocated to the tracklog was moved to the gps cursor.  This caused both the cursor and tracklog to display in the exact location where you are.

The problem here is that the reduction in available memory for the tracklog has caused it to draw at a slower rate.

The development team is working on different possibilities for improving this performance but also keeping the location of these items as accurate as possible.

In the meantime, I'd take a look at an applet that Gareth recently created that's up on the resource center.

How to archive GPS Tracklog

This applet will archive the tracklog once an hour (or however often you'd prefer) to a new shapefile.  The less points there are in the current tracklog, the faster the tracklog draws.  You could then create a model (or something similar) to merge these shapefiles back in the office.  Yes, you'll only be able to see up to an hour's worth of the tracklog, but it should display at a faster rate.

Hope this helps.
0 Kudos