ToDo

ToDo List

This is a dynamic list for Lykle Voort that changes with changing priorities. This list includes items predominantly related to the database that are pending and include a request data, status and person reporting problem (WB - Willem Bouten;JS - Judy Shamoun-Baranes; EB - Edwin Baaij). When items are solved they are moved to the FINISHED section.

Public web site

1. Copy UvAGPS functions available on the flysafe server to the public server (JS, July 2011, medium priority)

Data model, processing

1. Adapt parser for new firmware (V 1.0.35) format (WB/EB, July 2011, high priority, in progress)

2. Enable uploading tables to the database (for example to our personal schemas). For example, we would like to flag gps points with behaviour classes based on our accelerometer data and then store this information so that it can be reused (in short annotate data). Is there any way you can facilitate this process. Otherwise analysis has to be rerun locally every time, which is very time consuming. (JS, april 2011, high priority)

3. Design and implement a datamodel for the output of the "tides and currents model" as soon as the data is available. (WB, July 2011, medium priority)

4. Add 2D speed to the speed calculates in the uva_tracking_speed view (rename speed to 3D_speed). (JS, July 2011, low priority)

5. Add direction to calculations in uva_tracking_speed view. (JS, July 2011, low priority)

6. Automated upload and import UvAGPS metadata which should include a web form and webservice(WB, July 2011, low priority)

7. Add function for computation of elevation (and perhaps azimuth) of sun above the horizon for each gps point. This would provide users with the possibility to determine whether a point is measured during the day, at twilight (elevation lets users decide if they want civil or nautical twilight) or at night. An example script can be found in the R script crepuscule.R which is part of the maptools toolbox and would extract the value “solarpos”. Michael Kemp can provide more information on script usage and examples (m.u.kemp@uva.nl) day start, day end to mark whether a data point is at night or during the day (JS, June 2011, low priority)

8. Verify whether there are still users using Irods (WB, June 2011)

9. Accelerometer data: based on the current data model, we cannot properly sort accelerometer measurements that are not coupled with a GPS fix, an extra field in the accelerometer table is probably needed. (JS, march 2011, very low priority)

Administration

1. List of access rights: user's rights must be set consistently to make sure that all users have the correct rights to see data (WB, april 2011, high priority);

• add a description of the user's rights fields, instead of the database names for rights (may 2011)
• add a project data table; assign projects to users or users to projects; link bird access to projects
• make sure that access to weather data is properly restricted
• Note: this account should have very limited rights, and should not be able to change the own password (otherwise one guest could make it impossible for other guests to see the site)

2. Bookkeeping: Change interface so that a user can select uvaGPS and then a particular tag (or tags with cntr shift for example) and range of dates. Currently a user can select uvaGPS and a range of dates and will receive all tags, many tags may not be relevant to the user, making it difficult to quickly assess the status (JS, March 2011, low priority, should be improved by March 2012)

Finished

• Guest account: we shoud have a guest account with very restricted access, but who can see for example birdview with the tracks of one or two ('donated') birds. (May 2011, Complete). User name = guest, password = guest, access provided to several aspects of the virtual lab and 1 gull trajectory.

• BirdView: I noticed that the upload option for kml files from a local directory includes kml only, can we extend the support to kml and kmz files? The http upload does actually support both. (solved July 2011)

• Import UvAGPS log files via standard storage facility: Data can be uploaded manually via winSCP, iRODS, and digital drop box. Dropbox is becoming the standard for all new stations and linked to the database services (implemented May 2011).

• Quality control: Users with write rights can flag data points manually in the database through pgAdmin. Data cannot be queried but must be viewed through the data viewer to edit. Currently data is manually flagged by J. Shamoun-Baranes (solved April 2011)

• QC & functions: When only a subset of data (say data approved from QC) is queried, the distance and direction functions work on the subset, there is an option to run these functions on all data - but not by default (April 2011)

• Implement generate KMZ service for UvAGPS on public server (implemented May 2011 through virtual lab)

• Metadata: Excel files are either sent to SARA and then uploaded to the database or uploaded manually (March 2011)

• List of user's rights: a script was written to quickly produce an overview of all users and their rights (12-05-2011)

• Make a readonly copy of Flysafe Wiki on public server (september 2010)

• Improve UvA GPS parser to log errors such as CRC8 in database (september 2010)

• Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts (october 2010)

• Add accelerometer calibration factors to uva_device (september 2010)