Discrepancy between tracks.numpoints and the real number of track points

[GoogleCodeExporter]

What steps will reproduce the problem?
1. select _id,numpoints,startid,stopid,numpoints from tracks;
2. select trackid,count(*) from trackpoints group by trackid;
3. Compare results from 1) and 2).

In every single case, the number in tracks is off by a few percent.  For long 
tracks with >5000 points we are talking here about 50-200 missing points.

Good news is that startid and stopid seem to be accurate.

Original issue reported on code.google.com by ba...@google.com on 12 Dec 2010 at 9:43

[GoogleCodeExporter]

Setting as large work since this is the type of issue that's annoying to debug.

Original comment by rdama...@google.com on 30 Apr 2011 at 6:01

• Added labels: Component-Persistence, Work-Large

[GoogleCodeExporter]

Original comment by jshih@google.com on 9 Dec 2011 at 9:16

[GoogleCodeExporter]

This is expected. In the trackpoints table, we insert separators when distance 
> max recording distance. These separators do not increment numpoints in tracks 
table.

Original comment by jshih@google.com on 9 Aug 2012 at 9:56

• Changed state: Intended