Bogus waypoint

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Record a track (start, move a little, stop)
2. Zoom all the way out to the world map

What is the expected output? What do you see instead?
I'd see just the track I recorded.
Instead I see a waypoint at 0,0 (or -1, -1 - not sure)
A screenshot is attached.

Consequence:
When uploading to Google Maps, the map zooms to the bounding box of the track + 
this waypoint, which gives a bad upload experience.

Analysis/proposed fix:
Apparently this is the waypoint inserted at the start of recording, which is 
never getting updated. This is already in the released version of the app, 
meaning we need to do two things: first, start updating it as we should for new 
tracks. Second, we need to update existing tracks (which can be done by either 
changing the DB version with a fix-once update to tracks, or by updating tracks 
as they're opened - I prefer the first).

Original issue reported on code.google.com by rdama...@google.com on 21 Feb 2011 at 9:58

Attachments:

• bogus-waypoint.png

[GoogleCodeExporter]

Btw, I just realized the previous upload code had a workaround to skip this 
waypoint, I'm adding it again to unblock the uploading code release (thus 
lowering the priority here), but the drawing should also skip it if that's 
really the case, plus it should get updated properly.

Original comment by rdama...@google.com on 21 Feb 2011 at 10:02

• Added labels: Priority-High
• Removed labels: Priority-Critical

[GoogleCodeExporter]

Fix here:
http://code.google.com/r/sandordornbush-bug2/source/detail?r=5e3ade180564e4d14f2
77ccc175497df098e6001

I'm not sure if fixes all use cases, eg export, upload etc.  This hides it from 
the map view.

Original comment by sandordo...@google.com on 23 Feb 2011 at 12:55

[GoogleCodeExporter]

Original comment by sandordo...@google.com on 23 Feb 2011 at 3:22

• Changed state: Fixed