Data requirements
- Track as georss 2.0 (http://cyber.law.harvard.edu/rss/rss.html)
- One track per channel
- Track name in title
- Track name in filename (without spaces)
- Track line symbology in category (somehow)
- One entry per narrative entry (with interpolated position)
- One entry per requested position (with interpolated position)
- Exercise data as kml (http://code.google.com/apis/kml/documentation/kml_tags_21.html#polygon)
- File layout & utilisation as illustrated at http://www.gliffy.com/publish/1316907/
Business requirements
- Select what data to export (tracks, annotations)
- Using visible property (existing)
- Select period of data to export
- Using visible property (filter to time period, existing)
- Select frequency to export track data
- Using drop-down menu (in wizard)
- Select target directory
- Using file-system browser (in wizard)
- Offer to zip them up
- Using tick-box. We need to get a filename if we do (in wizard)
Data tests
- Empty layers object
- Two tracks, some narratives, some annotations
- All tracks, all narratives, all annotations. Check all data present.
- Hide one track, Hide some points, hide some narrative entries, hide some annotations. Export them. Check data
- One track. 15 minute fixes. Narrative entries at 1,5,10,22 minute times.
- Check correct interpolation.
Download in other formats: