NOTE: At this time, tracks and LineString are persisted in a file system. This may remain feasible since this data is generally loaded into memory and only changes slowly. After all, it's a map.
- Investigate the variable length fields in MySQL. This will hold Encoded Points and Encoded Levels. Interested to know typical length and maximum length. I've got 1210 points in the Century ride. Not sure how big the encoded points and levels strings are.
- Does serializing the object and storing in as a binary make sense?
- How do we hold elevation data?
- Select the EncodedTrack fields to be persisted.
page revision: 3, last edited: 06 Nov 2015 14:23