https://wiki.e-ecology.nl/api.php?action=feedcontributions&feedformat=atom&user=Bartecology - User contributions [en]2026-04-06T10:08:31ZUser contributionsMediaWiki 1.30.0https://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=375UvAGPS2011-01-12T13:48:38Z<p>Bart: /* UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user if not 0<br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
== UVA_ACC_START102 or UVA_ACC_START_LIMITED ==<br />
<br />
General acceleration entry associated with a set of accelerations. Added in Firmware 1.0.2.7 because there line numbers were introduced for acceleration lines so that these lines can be tracked. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|line_counter||integer||||||Number of lines associated with this set of accelerations<br />
|-<br />
|timesynced||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps Synced)<br />
|-<br />
|accii||integer||||||Accelero measurement interval<br />
|-<br />
|accsn||integer||||||Number of samples (0-65536)<br />
|-<br />
|f||smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|userflag||integer||||||Flagged as inacceptable by user if not 0<br />
|-<br />
|satellites_used||smallint||||||<br />
|-<br />
|positiondop||float||||||<br />
|-<br />
|speed_accuracy||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
== UVA_WARNING102 or UVA_WARNING_LIMITED ==<br />
<br />
Since firmware version 1.0.2.7 this table was added as catchall for tags that don occur very often (C10, C20) or errors that occur during parsing. <br />
For example all CRC failures can be selected with : <br />
<br />
select * from gps.uva_warning102 <br />
where warning = 'CRC8 failure'<br />
order by device_info_serial;<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||integer||PK||NOT NULL||<br />
|-<br />
|filename||text||PK||NOT NULL||UvAGPS log filename <br />
|-<br />
|linenumber||integer||PK||NOT NULL||linenumber in file <br />
|-<br />
|warning||text||||||The warming message or tag<br />
|-<br />
|line||text||||||The actual line in the file <br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the '''userflag''' are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=374UvAGPS2011-01-12T13:35:09Z<p>Bart: /* UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user if not 0<br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
== UVA_ACC_START102 or UVA_ACC_START_LIMITED ==<br />
<br />
General acceleration entry associated with a set of accelerations. Added in Firmware 1.0.2.7 because there line numbers were introduced for acceleration lines so that these lines can be tracked. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|line_counter||integer||||||Number of lines associated with this set of accelerations<br />
|-<br />
|timesynced||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps Synced)<br />
|-<br />
|accii||integer||||||Accelero measurement interval<br />
|-<br />
|accsn||integer||||||Number of samples (0-65536)<br />
|-<br />
|f||smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|userflag||integer||||||Flagged as inacceptable by user if not 0<br />
|-<br />
|satellites_used||smallint||||||<br />
|-<br />
|positiondop||float||||||<br />
|-<br />
|speed_accuracy||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the '''userflag''' are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=373UvAGPS2011-01-12T12:14:36Z<p>Bart: /* UVA_TRACKING or UVA_TRACKING_LIMITED */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user if not 0<br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|userflag||integer||||||Flagged as inacceptable by user if not 0<br />
|-<br />
|satellites_used||smallint||||||<br />
|-<br />
|positiondop||float||||||<br />
|-<br />
|speed_accuracy||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the '''userflag''' are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=372UvAGPS2011-01-12T12:14:17Z<p>Bart: /* UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user if not 0<br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|userflag||integer||||||Flagged as inacceptable by user if not 0<br />
|-<br />
|satellites_used||smallint||||||<br />
|-<br />
|positiondop||double||||||<br />
|-<br />
|speed_accuracy||double||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the '''userflag''' are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=371UvAGPS2011-01-12T12:13:28Z<p>Bart: /* UVA_TRACKING or UVA_TRACKING_LIMITED */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user<br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|userflag||integer||||||Flagged as inacceptable by user if not 0<br />
|-<br />
|satellites_used||smallint||||||<br />
|-<br />
|positiondop||double||||||<br />
|-<br />
|speed_accuracy||double||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the '''userflag''' are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=370UvAGPS2011-01-12T12:10:07Z<p>Bart: /* UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user<br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the '''userflag''' are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=369UvAGPS2011-01-12T12:09:28Z<p>Bart: /* UVA_TRACKING_DATA or UVA_TRACKING_LIMITED */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|userflag||Integer||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the '''userflag''' are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=368UvAGPS2011-01-12T12:08:52Z<p>Bart: /* UVA_TRACKING_DATA or UVA_TRACKING_LIMITED */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|userflag||text||Integer||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the '''userflag''' are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=ToDo&diff=367ToDo2010-12-24T10:14:22Z<p>Bart: /* ToDo List */</p>
<hr />
<div>== ToDo List == <br />
<br />
<br />
* View/function to identify foraging trips <br />
<br />
* Update speed function to account for userflag (december 2010) <br />
<br />
* Create Flagging facility for invalid tracking data (december 2010) <br />
<br />
* Fix UvAGPS KMZ generator (color range, symbol selection) (november 2010)<br />
<br />
* Make a readonly copy of Flysafe Wiki on public server (september 2010) <br />
<br />
* Improve UvA GPS parser to log errors such as CRC8 in database (september 2010) <br />
<br />
* Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts ( october 2010)<br />
<br />
* Import UvAGPS log files via standard storage facility ( november 2010) <br />
<br />
* Implement generate KML service for for UvAGPS on public server (october 2010) <br />
<br />
* Define and implement service to flag invalid GPS tracks (november 2010)<br />
<br />
* Add accelerometer calibration factors to uva_device (september 2010)<br />
<br />
* Import UvAGPS metadata. (november 2010)</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=366UvAGPS2010-12-24T10:13:56Z<p>Bart: /* get_uvagps_track_speed */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|quality||text||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the '''userflag''' are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=365UvAGPS2010-12-24T10:13:29Z<p>Bart: /* get_uvagps_track_distance_direction */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|quality||text||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the userflag are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the '''userflag''' has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=364UvAGPS2010-12-24T10:13:09Z<p>Bart: /* get_uvagps_track_distance_direction */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|quality||text||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the userflag are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
In this function the records where the userflag has been set are discarded. To see these records a additional boolean argument for '''show raw data''' should be added like :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606, true); <br />
</pre><br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=363UvAGPS2010-12-24T10:10:00Z<p>Bart: /* get_uvagps_track_speed */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|quality||text||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
In these functions the records that have been flagged as invalid by setting the userflag are not token into account and discarded. <br />
If it is required get the speed for all records a additional boolean argument for '''get raw data''' can be given. i.e.<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00', true);<br />
<br />
select * from gps.get_uvagps_track_speed(119, true);<br />
</pre><br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=ToDo&diff=362ToDo2010-12-23T11:33:11Z<p>Bart: /* ToDo List */</p>
<hr />
<div>== ToDo List == <br />
<br />
<br />
* View/function to identify foraging trips <br />
<br />
* Update speed function to account for userflag <br />
<br />
* Create Flagging facility for invalid tracking data (december 2010) <br />
<br />
* Fix UvAGPS KMZ generator (color range, symbol selection) (november 2010)<br />
<br />
* Make a readonly copy of Flysafe Wiki on public server (september 2010) <br />
<br />
* Improve UvA GPS parser to log errors such as CRC8 in database (september 2010) <br />
<br />
* Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts ( october 2010)<br />
<br />
* Import UvAGPS log files via standard storage facility ( november 2010) <br />
<br />
* Implement generate KML service for for UvAGPS on public server (october 2010) <br />
<br />
* Define and implement service to flag invalid GPS tracks (november 2010)<br />
<br />
* Add accelerometer calibration factors to uva_device (september 2010)<br />
<br />
* Import UvAGPS metadata. (november 2010)</div>Barthttps://wiki.e-ecology.nl/index.php?title=Usage&diff=361Usage2010-12-09T12:36:29Z<p>Bart: /* Uploading UvAGPS log files */</p>
<hr />
<div>== General ==<br />
<br />
<br />
== Database Issues == <br />
<br />
* [[ Connecting to the Flysafe database ]]<br />
<br />
* [[ Useful Queries ]]<br />
<br />
== Website Issues ==<br />
<br />
== Various == <br />
<br />
=== Uploading UvAGPS log files === <br />
<br />
<br />
* Goto [https://irods.grid.sara.nl/~ https://irods.grid.sara.nl/~] <br />
<br />
* Goto the '''uvagps''' directory<br />
<br />
* Upload your UvAGPS files logfiles or zipped logfiles directly in that directory <br />
<br />
* If the files have been processed correctly they are moved to the '''~/uvagps/processed''' directory<br />
<br />
* If the processing failed they are moved to the '''~/uvagps/failed''' directory, together with a error log.<br />
<br />
* If nothing happens within an hour check that the uploaded files (and the ~/uvagps directory) are also owned by the '''uvagps_parser''' user.<br />
<br />
<br />
The files should be processed every hour. If the files have been processed the data is loaded in the master database at '''services.flysafe.sara.nl'''. That database is not accessible for everyone.<br />
<br />
The data is being copied to the mirror database on '''public.flysafe.sara.nl''' every night at 2:30 (Amsterdam time) if new files haven been processed, so it can take a day before the uploads of your files are visible on '''public.flysafe.sara.nl'''.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Usage&diff=360Usage2010-12-09T12:33:51Z<p>Bart: /* Uploading UvAGPS log files */</p>
<hr />
<div>== General ==<br />
<br />
<br />
== Database Issues == <br />
<br />
* [[ Connecting to the Flysafe database ]]<br />
<br />
* [[ Useful Queries ]]<br />
<br />
== Website Issues ==<br />
<br />
== Various == <br />
<br />
=== Uploading UvAGPS log files === <br />
<br />
<br />
* Goto [https://irods.grid.sara.nl/~ https://irods.grid.sara.nl/~] <br />
<br />
* Goto the '''uvagps''' directory<br />
<br />
* Upload your UvAGPS files logfiles or zipped logfiles directly in that directory <br />
<br />
* If the files have been processed correctly they are moved to the '''~/uvagps/processed''' directory<br />
<br />
* If the processing failed they are moved to the '''~/uvagps/failed''' directory, together with a error log.<br />
<br />
* If nothing happens within an our check that the uploaded files (and the ~/uvagps directory) alre also owned by the '''uvagps_parser''' user.<br />
<br />
<br />
If the files have been processed data is loaded in the master database at '''services.flysafe.sara.nl'''. That database is not accessible for everyone.<br />
<br />
The data is being copied to the mirror database on '''public.flysafe.sara.nl''' every night at 2:30 (Amsterdam time) if new files haven been processed, so it can take a day before the uploads of your files are visible on '''public.flysafe.sara.nl'''.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Usage&diff=359Usage2010-12-09T12:26:17Z<p>Bart: /* Uploading UvAGPS log files */</p>
<hr />
<div>== General ==<br />
<br />
<br />
== Database Issues == <br />
<br />
* [[ Connecting to the Flysafe database ]]<br />
<br />
* [[ Useful Queries ]]<br />
<br />
== Website Issues ==<br />
<br />
== Various == <br />
<br />
=== Uploading UvAGPS log files === <br />
<br />
<br />
* Goto [https://irods.grid.sara.nl/~ https://irods.grid.sara.nl/~] <br />
<br />
* Goto the '''uvagps''' directory<br />
<br />
* Upload your UvAGPS files logfiles or zipped logfiles directly in that directory <br />
<br />
* If the files have been processed correctly they are moved to the '''~/uvagps/processed''' directory<br />
<br />
* If the processing failed they are moved to the '''~/uvagps/failed''' directory, together with a error log.<br />
<br />
* If nothing happens within an our check that the uploaded files (and the ~/uvagps directory) alre also owned by the '''uvagps_parser''' user.<br />
<br />
<br />
If the files have been processed data is loaded in the master database at '''services.flysafe.sara.nl'''. That database is not accessible for everyone.<br />
<br />
The Mirror database on '''public.flysafe.sara.nl''' is being copied every night at 2:30 if new files haven been processed, so it can take a day before the uploads of your files <br />
are visible on '''public.flysafe.sara.nl'''.</div>Barthttps://wiki.e-ecology.nl/index.php?title=ToDo&diff=358ToDo2010-11-25T10:35:31Z<p>Bart: /* ToDo List */</p>
<hr />
<div>== ToDo List == <br />
<br />
* Create Flagging facility for invalid tracking data <br />
<br />
* View/function to identify foraging trips <br />
<br />
* Fix UvAGPS KMZ generator (color range, symbol selection) (november 2010)<br />
<br />
* Make a readonly copy of Flysafe Wiki on public server (september 2010) <br />
<br />
* Improve UvA GPS parser to log errors such as CRC8 in database (september 2010) <br />
<br />
* Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts ( october 2010)<br />
<br />
* Import UvAGPS log files via standard storage facility ( november 2010) <br />
<br />
* Implement generate KML service for for UvAGPS on public server (october 2010) <br />
<br />
* Define and implement service to flag invalid GPS tracks (november 2010)<br />
<br />
* Add accelerometer calibration factors to uva_device (september 2010)<br />
<br />
* Import UvAGPS metadata. (november 2010)</div>Barthttps://wiki.e-ecology.nl/index.php?title=ToDo&diff=357ToDo2010-11-24T13:40:08Z<p>Bart: /* ToDo List */</p>
<hr />
<div>== ToDo List == <br />
<br />
* Fix UvAGPS KMZ generator (color range, symbol selection) <br />
<br />
* Create Flagging facility for invalid tracking data <br />
<br />
* View/function to identify foraging trips <br />
<br />
* Make a readonly copy of Flysafe Wiki on public server (september 2010) <br />
<br />
* Improve UvA GPS parser to log errors such as CRC8 in database (september 2010) <br />
<br />
* Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts ( october 2010)<br />
<br />
* Import UvAGPS log files via standard storage facility ( november 2010) <br />
<br />
* Implement generate KML service for for UvAGPS on public server (october 2010) <br />
<br />
* Define and implement service to flag invalid GPS tracks (november 2010)<br />
<br />
* Add accelerometer calibration factors to uva_device (september 2010)<br />
<br />
* Import UvAGPS metadata. (november 2010)</div>Barthttps://wiki.e-ecology.nl/index.php?title=Usage&diff=356Usage2010-11-24T11:58:03Z<p>Bart: </p>
<hr />
<div>== General ==<br />
<br />
<br />
== Database Issues == <br />
<br />
* [[ Connecting to the Flysafe database ]]<br />
<br />
* [[ Useful Queries ]]<br />
<br />
== Website Issues ==<br />
<br />
== Various == <br />
<br />
=== Uploading UvAGPS log files === <br />
<br />
<br />
* Goto [https://irods.grid.sara.nl/~ https://irods.grid.sara.nl/~] <br />
<br />
* Goto the '''uvagps''' directory<br />
<br />
* Upload your UvAGPS files logfiles or zipped logfiles directly in that directory <br />
<br />
* If the files have been processed correctly they are moved to the '''~/uvagps/processed''' directory<br />
<br />
* If the processing failed they are moved to the '''~/uvagps/failed''' directory, together with a error log.<br />
<br />
* If nothing happens within a hour check that the uploaded files (and the ~/uvagps directory) alre also owned by the '''uvagps_parser''' user.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Usage&diff=355Usage2010-11-24T11:52:01Z<p>Bart: /* Uploading UvAGPS log files */</p>
<hr />
<div>== General ==<br />
<br />
=== Uploading UvAGPS log files === <br />
<br />
<br />
* Goto [https://irods.grid.sara.nl/~ https://irods.grid.sara.nl/~] <br />
<br />
* Goto the '''uvagps''' directory<br />
<br />
* Upload your UvAGPS files logfiles or zipped logfiles directly in that directory <br />
<br />
* If the files have been processed correctly they are moved to the '''~/uvagps/processed''' directory<br />
<br />
* If the processing failed they are moved to the '''~/uvagps/failed''' directory, together with a error log.<br />
<br />
* If nothing happens within a hour check that the uploaded files (and the ~/uvagps directory) alre also owned by the '''uvagps_parser''' user.<br />
<br />
== Database Issues == <br />
<br />
* [[ Connecting to the Flysafe database ]]<br />
<br />
* [[ Useful Queries ]]<br />
<br />
== Website Issues ==</div>Barthttps://wiki.e-ecology.nl/index.php?title=Usage&diff=354Usage2010-11-24T11:51:32Z<p>Bart: /* Uploading UvAGPS log files */</p>
<hr />
<div>== General ==<br />
<br />
=== Uploading UvAGPS log files === <br />
<br />
<br />
* Goto [https://irods.grid.sara.nl/~ https://irods.grid.sara.nl/~] <br />
<br />
* Got to the '''uvagps''' directory<br />
<br />
* Upload your UvAGPS files logfiles or zipped logfiles directly in that directory <br />
<br />
* If the files have been processed correctly they are moved to the '''~/uvagps/processed''' directory<br />
<br />
* If the processing failed they are moved to the '''~/uvagps/failed''' directory, together with a error log.<br />
<br />
* If nothing happens within a hour check that the uploaded files (and the ~/uvagps directory) alre also owned by the '''uvagps_parser''' user.<br />
<br />
== Database Issues == <br />
<br />
* [[ Connecting to the Flysafe database ]]<br />
<br />
* [[ Useful Queries ]]<br />
<br />
== Website Issues ==</div>Barthttps://wiki.e-ecology.nl/index.php?title=Usage&diff=353Usage2010-11-24T11:50:03Z<p>Bart: /* General */</p>
<hr />
<div>== General ==<br />
<br />
=== Uploading UvAGPS log files === <br />
<br />
<br />
* Goto [https://irods.grid.sara.nl/~] <br />
<br />
* Got to the '''uvagps''' directory<br />
<br />
* Upload your UvAGPS files logfiles or zipped logfiles directly in that directory <br />
<br />
* If the files have been processed correctly they are moved to the '''~/uvagps/processed''' directory<br />
<br />
* If the processing failed they are moved to the '''~/uvagps/failed''' directory, together with a error log.<br />
<br />
== Database Issues == <br />
<br />
* [[ Connecting to the Flysafe database ]]<br />
<br />
* [[ Useful Queries ]]<br />
<br />
== Website Issues ==</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=352UvAGPS2010-11-04T09:42:47Z<p>Bart: /* UvAGPS Data Model */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
Not everybody has access to all data. For most users access is limited to "limited" views that only give access to selected devices. <br />
<br />
== UVA_TRACKING_DATA or UVA_TRACKING_LIMITED ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|quality||text||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE or UVA_DEVICE_LIMITED == <br />
<br />
To be able to track the different firmware versions and specific properties for the different devices the UVA_DEVICE table was added. This table also includes essential information needed to calibrate the accelerometers. For more information see [[UvAGPS|Accelerometer calibration]]<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL || Serial number of tag<br />
|- <br />
| firmware_version || text |||| NOT NULL || Firmware version installed on tag<br />
|-<br />
| device_mass || double |||||||Mass of tag (g)<br />
|-<br />
| x_s|| double |||||||Calibration sensitivity of accelerometer in the x-axis <br />
|-<br />
| y_s|| double |||||||Calibration sensitivity of accelerometer in the y-axis <br />
|-<br />
| z_s|| double |||||||Calibration sensitivity of accelerometer in the z-axis <br />
|-<br />
| x_o|| double |||||||Calibration offset of accelerometer in the x-axis <br />
|-<br />
| y_o|| double |||||||Calibration offset of accelerometer in the y-axis <br />
|-<br />
| z_o|| double |||||||Calibration offset of accelerometer in the z-axis <br />
|-<br />
|}<br />
<br />
== UVA_COMM101 or UVA_COMM_LIMITED== <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
== UVA_SETTINGS101 or UVA_SETTINGS_LIMITED == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 or UVA_TRACKING_LIMITED==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 or UVA_ACCELERATION_LIMITED == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 or UVA_ENERGY_LIMITED ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING or UVA_TRACKING_LIMITED == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED or UVA_TRACKING_SPEED_LIMITED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.<br />
<br />
= Accelerometer calibration =<br />
<br />
The accelerometer measures the acceleration in 3D (20 times per second). Acceleration is caused by gravity (static component) and by a change in speed (dynamic component). <br />
When the logger is static in horizontal position (solar cells up), gravity (green arrow) shows a heave (vertical acceleration, z) of +1 g (1 g = 9.81 m.s<sup>-2</sup>) while surge and heave are both 0. When the front of the logger is vertically pointing down (forward acceleration, x), surge is +1g and when it is rolled to the right (sidewards acceleration, y) sway is +1g. Due to gravity, the pitch of a logger is thus translated into the values of heave, surge and sway (or z, x, y).<br />
<br />
However, the values are measured in mV instead of g. Before delivering the GPS-loggers, they have been calibrated at UvA. The acceleration (A) expressed in g is calculated from the measured value (M) and the calibration factors offset (''O'') and sensitivity (''S'').<br />
<br />
Thus acceleration for heave (z), surge (x) and sway (y) is calculated as:<br />
A<sub>z</sub> = (M<sub>z</sub>-O<sub>z</sub>)/S<sub>z</sub> ; A<sub>x</sub> = (M<sub>x</sub>-O<sub>x</sub>)/S<sub>x</sub>; A<sub>y</sub> = (M<sub>y</sub>-O<sub>y</sub>)/S<sub>y</sub> ; <br />
<br />
The values of ''O'' (in general ranging from 0-60, sometimes even 300) and ''S'' (ranging from 1300-1450) are available in the device table of the data base. If not available, use the factory defaults ''O'' = 0 and ''S'' = 1365.<br />
<br />
{|<br />
| [[File:accelero1.png|300px]]||[[File:accelero2.png|300px]]|<br />
|}<br />
<br />
In the figure above heave (z) is shown in green, surge(x) in red and sway (y) in blue, all values are expressed in g (on the y-axis).</div>Barthttps://wiki.e-ecology.nl/index.php?title=Setting_up_a_connection_to_the_e-Ecology_database&diff=351Setting up a connection to the e-Ecology database2010-11-04T09:36:24Z<p>Bart: /* Setting up an ODBC connection */</p>
<hr />
<div>= Connecting to the FlySafe database via Access or other relational database programs=<br />
Judy Shamoun-Baranes / Bart Heupers<br />
Last updated: November 4, 2010<br />
<br />
<br />
=General Information=<br />
<br />
The Flysafe database is a spatial postgreSQL ([http://www.postgresql.org/-http://www.postgresql.org/]). <br />
<br />
PGAdmin can be used to browse and query data. If you use pgadmin you do not need to set up an ODBC connection.<br />
<br />
Database can also be called from other programs by installing an ODBC driver for postgreSQL and establishing a "User Data Source" [http://www.postgresql.org/ftp/odbc/versions/msi/-http://www.postgresql.org/ftp/odbc/versions/msi/]<br />
<br />
In order to access the database your IP address must be sent to Bart Heupers who will provide a user name and password. For organizations an IP range can also be given.<br />
<br />
Resticted flysafe server information<br />
<br />
server : services.flysafe.sara.nl or analysis.flysafe.sara.nl<br />
port : 5432<br />
ssl : required<br />
<br />
The public server is at <br />
<br />
server : public.flysafe.sara.nl<br />
port : 5432<br />
ssl : required<br />
<br />
The tracking data can be found in schema '''gps'''. However these instructions can be followed for any of the data included in the flysafe database.<br />
<br />
=Setting up an ODBC connection=<br />
<br />
ODBC (Open Database connectivity) is a standard method of sharing data between databases and other programs. ODBC drivers use SQL to gain access to data from sources outside the program. Therefore, in order to connect between your database and other programs you must set up an ODBC connection. <br />
Step 1: Download and install an ODBC driver for postgreSQL.<br />
[http://www.postgresql.org/ftp/odbc/versions/msi/-http://www.postgresql.org/ftp/odbc/versions/msi/]<br />
Step 2: Set up ODBC connection<br />
<br />
<br />
Do the following:<br />
# go to '''start | Control panel | Administrative tools | Data sources (ODBC)'''<br />
# go to '''User DSN''' (first tab in Data sources)<br />
# click '''ADD'''<br />
# in window '''create''' '''new data source''' select '''PostgreSQL ANSI''' click '''FINISH'''<br />
# The '''ODBC Driver setup''' window opens. '''Data source name''': give your data source a name (eg GPS). Keep it simple, easily identifiable, this is the name you will use to identify your database from other applications, this will be the '''ODBC driver name'''.<br />
# In the same window fill in the following information: '''database''' ''flysafe'', '''Server''' ''services.flysafe.sara.nl'' or ''public.flysafe.sara.nl'', '''User Name''' your user name, '''SSL Mode''' ''require'', '''Port''' ''5432'', '''Password''' your password. When the window is completed click '''SAVE'''<br />
# Back in the '''User DSN''' window you should now see your ODBC driver you just named, click '''OK'''<br />
After completing these steps many other programs will now recognize your database and be able to communicate with it<br />
<br />
=Connecting to Access=<br />
You can now connect to the database via access. You have two options. One is to import the data, once this is done your database is not automatically updated but does not require a link to the database.<br />
<br />
The second option (described below) is to create a dynamic link to the database (you must be connected to the network) in this case you are always viewing data that is in the actual SARA database.<br />
<br />
# Open a new database in Access<br />
# go to '''file | Get external data | Link tables'''<br />
# in '''files of type''' select '''ODBC databases'''<br />
# in '''select data source''' click on tab '''Machine Data Source'''<br />
# select the data source name you created when setting up the ODBC connection (eg GPS) click '''OK'''<br />
# Select the tables you want to import click OK<br />
<br />
You now have access to your selected tables in the database. Have fun.<br />
<br />
<br />
Original document [[ Media:Connect_flysafe.doc ]]</div>Barthttps://wiki.e-ecology.nl/index.php?title=Setting_up_a_connection_to_the_e-Ecology_database&diff=350Setting up a connection to the e-Ecology database2010-11-04T09:35:42Z<p>Bart: </p>
<hr />
<div>= Connecting to the FlySafe database via Access or other relational database programs=<br />
Judy Shamoun-Baranes / Bart Heupers<br />
Last updated: November 4, 2010<br />
<br />
<br />
=General Information=<br />
<br />
The Flysafe database is a spatial postgreSQL ([http://www.postgresql.org/-http://www.postgresql.org/]). <br />
<br />
PGAdmin can be used to browse and query data. If you use pgadmin you do not need to set up an ODBC connection.<br />
<br />
Database can also be called from other programs by installing an ODBC driver for postgreSQL and establishing a "User Data Source" [http://www.postgresql.org/ftp/odbc/versions/msi/-http://www.postgresql.org/ftp/odbc/versions/msi/]<br />
<br />
In order to access the database your IP address must be sent to Bart Heupers who will provide a user name and password. For organizations an IP range can also be given.<br />
<br />
Resticted flysafe server information<br />
<br />
server : services.flysafe.sara.nl or analysis.flysafe.sara.nl<br />
port : 5432<br />
ssl : required<br />
<br />
The public server is at <br />
<br />
server : public.flysafe.sara.nl<br />
port : 5432<br />
ssl : required<br />
<br />
The tracking data can be found in schema '''gps'''. However these instructions can be followed for any of the data included in the flysafe database.<br />
<br />
=Setting up an ODBC connection=<br />
<br />
ODBC (Open Database connectivity) is a standard method of sharing data between databases and other programs. ODBC drivers use SQL to gain access to data from sources outside the program. Therefore, in order to connect between your database and other programs you must set up an ODBC connection. <br />
Step 1: Download and install an ODBC driver for postgreSQL.<br />
[http://www.postgresql.org/ftp/odbc/versions/msi/-http://www.postgresql.org/ftp/odbc/versions/msi/]<br />
Step 2: Set up ODBC connection<br />
<br />
<br />
Do the following:<br />
# go to '''start | Control panel | Administrative tools | Data sources (ODBC)'''<br />
# go to '''User DSN''' (first tab in Data sources)<br />
# click '''ADD'''<br />
# in window '''create''' '''new data source''' select '''PostgreSQL ANSI''' click '''FINISH'''<br />
# The '''ODBC Driver setup''' window opens. '''Data source name''': give your data source a name (eg GPS). Keep it simple, easily identifiable, this is the name you will use to identify your database from other applications, this will be the '''ODBC driver name'''.<br />
# In the same window fill in the following information: '''database''' ''flysafe'', '''Server''' ''services.flysafe.sara.nl'', '''User Name''' your user name, '''SSL Mode''' ''require'', '''Port''' ''5432'', '''Password''' your password. When the window is completed click '''SAVE'''<br />
# Back in the '''User DSN''' window you should now see your ODBC driver you just named, click '''OK'''<br />
After completing these steps many other programs will now recognize your database and be able to communicate with it<br />
<br />
=Connecting to Access=<br />
You can now connect to the database via access. You have two options. One is to import the data, once this is done your database is not automatically updated but does not require a link to the database.<br />
<br />
The second option (described below) is to create a dynamic link to the database (you must be connected to the network) in this case you are always viewing data that is in the actual SARA database.<br />
<br />
# Open a new database in Access<br />
# go to '''file | Get external data | Link tables'''<br />
# in '''files of type''' select '''ODBC databases'''<br />
# in '''select data source''' click on tab '''Machine Data Source'''<br />
# select the data source name you created when setting up the ODBC connection (eg GPS) click '''OK'''<br />
# Select the tables you want to import click OK<br />
<br />
You now have access to your selected tables in the database. Have fun.<br />
<br />
<br />
Original document [[ Media:Connect_flysafe.doc ]]</div>Barthttps://wiki.e-ecology.nl/index.php?title=Useful_Queries&diff=338Useful Queries2010-09-27T09:44:58Z<p>Bart: </p>
<hr />
<div>A query to determine the total distance a bird has flown is : <br />
<br />
select sum(distance)/1000 as total_distance<br />
from gps.get_uvagps_track_speed('''<ID>''');<br />
<br />
or for a fixed time period :<br />
<br />
select sum(distance)/1000 as total_distance<br />
from gps.get_uvagps_track_speed('''<ID>''', '2010-01-01 00:00:00', '2011-01-01 00:00:00');<br />
<br />
<br />
If you want to do this for all ID's at the same time you can do something like :<br />
<br />
select device_info_serial, (select sum(distance)/1000<br />
from gps.get_uvagps_track_speed(device_info_serial, '2010-01-01 00:00:00', '2011-01-01 00:00:00')) as total_distance<br />
from gps.uva_device<br />
<br />
For limited users :<br />
<br />
select device_info_serial, (select sum(distance)/1000<br />
from gps.get_uvagps_track_speed(device_info_serial, '2010-01-01 00:00:00', '2011-01-01 00:00:00')) as total_distance<br />
from gps.uva_device_limited<br />
<br />
<br />
<br />
The GROUP BY clause in SQL can be used to count the total number of measurements for each device :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking<br />
group by device_info_serial; <br />
<br />
and for limited users :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking_limited<br />
group by device_info_serial; <br />
<br />
<br />
If you want to count the number of measurements with valid GPS fixes you can add a where clause :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking <br />
where latitude is not null <br />
group by device_info_serial;<br />
<br />
If you to see want both the count of valid and invalid GPS fixes per device you can do something like :<br />
<br />
select device_info_serial, latitude is not null as valid, count(*) <br />
from gps.uva_tracking <br />
group by device_info_serial, valid <br />
order by device_info_serial, valid;<br />
<br />
and for limited users: <br />
<br />
select device_info_serial, latitude is not null as valid, count(*) <br />
from gps.uva_tracking_limited <br />
group by device_info_serial, valid <br />
order by device_info_serial, valid;</div>Barthttps://wiki.e-ecology.nl/index.php?title=Useful_Queries&diff=337Useful Queries2010-09-27T09:43:59Z<p>Bart: /* Useful Queries */</p>
<hr />
<div><br />
A query to determine the total distance a bird has flown for a time period is : <br />
<br />
select sum(distance)/1000 as total_distance<br />
from gps.get_uvagps_track_speed('''<ID>''');<br />
<br />
or <br />
<br />
select sum(distance)/1000 as total_distance<br />
from gps.get_uvagps_track_speed('''<ID>''', '2010-01-01 00:00:00', '2011-01-01 00:00:00');<br />
<br />
<br />
If you want to do this for all ID's at the same time you can do something like :<br />
<br />
select device_info_serial, (select sum(distance)/1000<br />
from gps.get_uvagps_track_speed(device_info_serial, '2010-01-01 00:00:00', '2011-01-01 00:00:00')) as total_distance<br />
from gps.uva_device<br />
<br />
For limited users :<br />
<br />
select device_info_serial, (select sum(distance)/1000<br />
from gps.get_uvagps_track_speed(device_info_serial, '2010-01-01 00:00:00', '2011-01-01 00:00:00')) as total_distance<br />
from gps.uva_device_limited<br />
<br />
<br />
<br />
The GROUP BY clause in SQL can be used to count the total number of measurements for each device :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking<br />
group by device_info_serial; <br />
<br />
and for limited users :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking_limited<br />
group by device_info_serial; <br />
<br />
<br />
If you want to count the number of measurements with valid GPS fixes you can add a where clause :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking <br />
where latitude is not null <br />
group by device_info_serial;<br />
<br />
If you to see want both the count of valid and invalid GPS fixes per device you can do something like :<br />
<br />
select device_info_serial, latitude is not null as valid, count(*) <br />
from gps.uva_tracking <br />
group by device_info_serial, valid <br />
order by device_info_serial, valid;<br />
<br />
and for limited users: <br />
<br />
select device_info_serial, latitude is not null as valid, count(*) <br />
from gps.uva_tracking_limited <br />
group by device_info_serial, valid <br />
order by device_info_serial, valid;</div>Barthttps://wiki.e-ecology.nl/index.php?title=Useful_Queries&diff=336Useful Queries2010-09-27T09:41:58Z<p>Bart: /* Useful Queries */</p>
<hr />
<div>= Useful Queries = <br />
<br />
A query to determine the total distance a bird has flown for a time period is : <br />
<br />
select sum(distance)/1000 as total_distance<br />
from gps.get_uvagps_track_speed('''<ID>''');<br />
<br />
or <br />
<br />
select sum(distance)/1000 as total_distance<br />
from gps.get_uvagps_track_speed('''<ID>''', '2010-01-01 00:00:00', '2011-01-01 00:00:00');<br />
<br />
<br />
If you want to do this for all ID's at the same time you can do something like :<br />
<br />
select device_info_serial, (select sum(distance)/1000<br />
from gps.get_uvagps_track_speed(device_info_serial, '2010-01-01 00:00:00', '2011-01-01 00:00:00')) as total_distance<br />
from gps.uva_device(_limited)<br />
<br />
<br />
The GROUP BY clause in SQL can be used to count the total number of measurements for each device :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking(_limited) <br />
group by device_info_serial; <br />
<br />
If you want to count the number of measurements with valid GPS fixes you can add a where clause :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking <br />
where latitude is not null <br />
group by device_info_serial;<br />
<br />
If you to see want both the count of valid and invalid GPS fixes per device you can do something like :<br />
<br />
select device_info_serial, latitude is not null as valid, count(*) <br />
from gps.uva_tracking <br />
group by device_info_serial, valid <br />
order by device_info_serial, valid;</div>Barthttps://wiki.e-ecology.nl/index.php?title=Useful_Queries&diff=335Useful Queries2010-09-27T09:41:45Z<p>Bart: /* Useful Queries */</p>
<hr />
<div>= Useful Queries = <br />
<br />
A query to determine the total distance a bird has flown for a time period is : <br />
<br />
select sum(distance)/1000 as total_distance<br />
from gps.get_uvagps_track_speed('''<ID>''');<br />
<br />
or <br />
<br />
select sum(distance)/1000 as total_distance<br />
from gps.get_uvagps_track_speed('''<ID>''', '2010-01-01 00:00:00', '2011-01-01 00:00:00');<br />
<br />
<br />
If you want to do this for all ID's at the same time you can do something like :<br />
<br />
select device_info_serial, (select sum(distance)/1000<br />
from gps.get_uvagps_track_speed(device_info_serial, '2010-01-01 00:00:00', '2011-01-01 00:00:00')) as total_distance<br />
from gps.uva_device(_limited)<br />
<br />
<br />
The GROUP BY clause in SQL can be used to count the total number of measurements for each device :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking(_limited) <br />
group by device_info_serial; <br />
<br />
If you want to count the number of measurements with valid GPS fixes you can add a where clause :<br />
<br />
select device_info_serial, count(*) <br />
from gps.uva_tracking <br />
where latitude is not null <br />
group by device_info_serial;<br />
<br />
If you to see want both the count of valid and invalid GPS fixes per device you can do something like :<br />
<br />
select device_info_serial, latitude is not null as valid, count(*) <br />
from gps.uva_tracking <br />
group by device_info_serial, valid <br />
order by device_info_serial, valid;<br />
<br />
<br />
Ik zal dit in de WIKI zetten .<br />
<br />
Met vriendelijke groet,<br />
<br />
<br />
<br />
Bart Heupers</div>Barthttps://wiki.e-ecology.nl/index.php?title=Usage&diff=334Usage2010-09-27T09:32:55Z<p>Bart: /* Database Issues */</p>
<hr />
<div>== General == <br />
<br />
<br />
<br />
== Database Issues == <br />
<br />
* [[ Connecting to the Flysafe database ]]<br />
<br />
* [[ Useful Queries ]]<br />
<br />
== Website Issues ==</div>Barthttps://wiki.e-ecology.nl/index.php?title=Useful_Queries&diff=333Useful Queries2010-09-27T09:32:22Z<p>Bart: Created page with "= Useful Queries = Judy had al een query om de totale afstand te bepalen voor een ID. Dat was : select sum(distance)/1000 as total_distance from gps.get_uvagps_track_speed(35..."</p>
<hr />
<div>= Useful Queries = <br />
<br />
<br />
Judy had al een query om de totale afstand te bepalen voor een ID. Dat was :<br />
<br />
select sum(distance)/1000 as total_distance<br />
from gps.get_uvagps_track_speed(355);<br />
<br />
<br />
Als je dat voor alle ID’s tegelijk wilt doen krijg je bijvoorbeeld iets van : <br />
<br />
select device_info_serial, (select sum(distance)/1000<br />
from gps.get_uvagps_track_speed(device_info_serial)) as total_distance<br />
from gps.uva_device<br />
<br />
dat duurt even.<br />
<br />
Ik kan me voorstellen dat je dat alleen voor een bepaalde tijdsperiode wilt zien. Dan heb je bijvoorbeeld :<br />
<br />
select device_info_serial, (select sum(distance)/1000<br />
from gps.get_uvagps_track_speed(device_info_serial, '2010-01-01 00:00:00', '2011-01-01 00:00:00')) as total_distance<br />
from gps.uva_device<br />
<br />
<br />
2)<br />
<br />
In SQL heb je de GROUP BY clause, die het mogelijk maakt om aggregaties zoals som, aantal, gemiddelde, te groeperen volgens bepaalde criteria zoals ID <br />
<br />
Het totaal aantal positiemetingen per ID is dan :<br />
<br />
select device_info_serial, count(*) from gps.uva_tracking group by device_info_serial;<br />
<br />
Als je alleen de valide metingen met gps fix wilt hebben voeg je nog een conditie toe waar de latitude niet null is <br />
<br />
select device_info_serial, count(*) from gps.uva_tracking where latitude is not null group by device_info_serial;<br />
<br />
<br />
Een als je zowel het aantal meteingen met gps fix als zonder wilt zien per device kun je iets doen als :<br />
<br />
<br />
select device_info_serial, latitude is not null as valid, count(*) from gps.uva_tracking group by device_info_serial, valid order by device_info_serial, valid;<br />
<br />
<br />
Ik zal dit in de WIKI zetten .<br />
<br />
Met vriendelijke groet,<br />
<br />
<br />
<br />
Bart Heupers</div>Barthttps://wiki.e-ecology.nl/index.php?title=ToDo&diff=329ToDo2010-09-15T15:37:38Z<p>Bart: /* ToDo List */</p>
<hr />
<div>== ToDo List == <br />
<br />
* Make a readonly copy of Flysafe Wiki on public server (september 2010) <br />
<br />
* Improve UvA GPS parser to log errors such as CRC8 in database (september 2010) <br />
<br />
* Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts ( october 2010, waiting for matlab scripts )<br />
<br />
* Import UvAGPS log files via standard storage facility ( ??) <br />
<br />
* Implement generate KML service for for UvAGPS on public server (october 2010) <br />
<br />
* Define and implement service to flag invalid GPS tracks (november 2010)<br />
<br />
* Add accelerometer calibration factors to uva_device (september 2010)<br />
<br />
* Import UvAGPS metadata. (When received after <br />
<br />
*</div>Barthttps://wiki.e-ecology.nl/index.php?title=ToDo&diff=328ToDo2010-09-15T15:33:25Z<p>Bart: /* ToDo List */</p>
<hr />
<div>== ToDo List == <br />
<br />
* Make a readonly copy of Flysafe Wiki on public server (september 2010) <br />
<br />
* Improve UvA GPS parser to log errors such as CRC8 in database (september 2010) <br />
<br />
* Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts ( october 2010, waiting for matlab scripts )<br />
<br />
* Import UvAGPS log files via standard storage facility ( ??) <br />
<br />
* Implement generate KML service for for UvAGPS on public server (october 2010) <br />
<br />
* Define and implement service to flag invalid GPS tracks (november 2010)</div>Barthttps://wiki.e-ecology.nl/index.php?title=ToDo&diff=327ToDo2010-09-15T15:13:31Z<p>Bart: </p>
<hr />
<div>== ToDo List == <br />
<br />
* Make a readonly copy of Flysafe Wiki on public server <br />
<br />
* Improve UvA GPS parser to log errors such as CRC8 in database<br />
<br />
* Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts <br />
<br />
* Import UvAGPS log files via standard storage facility<br />
<br />
*</div>Barthttps://wiki.e-ecology.nl/index.php?title=File:MediaWikiRefCard.pdf&diff=326File:MediaWikiRefCard.pdf2010-09-15T15:12:41Z<p>Bart: </p>
<hr />
<div></div>Barthttps://wiki.e-ecology.nl/index.php?title=ToDo&diff=325ToDo2010-09-15T15:09:28Z<p>Bart: New page: == ToDo List == * Make a readonly copy of Flysafe Wiki on public server * Improve UvA GPS parser to log errors such as CRC8 in database * Implement service to create graphs for U...</p>
<hr />
<div>== ToDo List == <br />
<br />
* Make a readonly copy of Flysafe Wiki on public server <br />
<br />
* Improve UvA GPS parser to log errors such as CRC8 in database<br />
<br />
* Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts <br />
<br />
* Import UvAGPS log files via standard storage facility<br />
<br />
*</div>Barthttps://wiki.e-ecology.nl/index.php?title=E-Ecology_Documentation_and_Guidance&diff=324E-Ecology Documentation and Guidance2010-09-15T15:05:16Z<p>Bart: </p>
<hr />
<div>[[ Usage ]] <br />
<br />
[[ Flysafe Data Model ]]<br />
<br />
[[ Services ]]<br />
<br />
[[ ToDo ]]<br />
<br />
== Getting started ==<br />
<br />
New to MediaWiki? Print out this [[Media:MediaWikiRefCard.pdf|quick reference card]], or find out more at the [[mediawikiwiki:Main Page|MetaWiki website]].<br />
<br />
[[MediaWiki References]]</div>Barthttps://wiki.e-ecology.nl/index.php?title=Argos_Data_Model&diff=323Argos Data Model2010-03-01T12:32:26Z<p>Bart: /* get_argosgps_track_distance_direction */</p>
<hr />
<div>== GPS Data Model == <br />
<br />
Last updated January 5, 2010 Bart Heupers - [[ UvAGPS ]] moved to special page<br />
<br />
Updated January 22, 2008 Judy Shamoun-Baranes <br />
<br />
'''FLYSAFE TRACKING DATABASE'''<br />
<br />
The tracking database will include data from several species. Some species are trapped and then monitored during the breeding season while others are trapped during the winter season. Information is collected on each tracked bird, including biometric measurements. These measurements may be collected more than once. During the breeding season information is also collected about the gull breeding colony itself, location of nests, state of breeding (number of eggs and juveniles) and then juveniles themselves are marked and measured (although not tracked).<br />
<br />
In addition, PTTs are often tested before they are actually placed on the birds. This information is also important during analysis and particularly to establish accuracy of data. This data should also be stored in the database. Therefore it is important that this information is stored properly in the database<br />
<br />
Units and descriptions should be filled in for all measurements<br />
<br />
One way of looking at this structure is considering 3 categories of tables: <br />
<br />
# '''lookup tables''' (information stored once) <br />
# '''session tables''' (stored occasionally) <br />
# '''observations''' – highest frequency of information.<br />
<br />
Primary keys are noted by bold italic text. Foreign keys are noted by italic text in the Field column.<br />
<br />
Microwave, will under no circumstances provide information about their checksum calculations. If feasible, SARA will duplicate the procedure and include a flag in the representing the microwave filtered data.<br />
<br />
'''TECHNICAL INFORMATION FROM TAGS'''<br />
<br />
<br />
== DEVICE_INFO ==<br />
<br />
Table including technical information about tag hardware. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL||serial number of PTT provided by Argos and used for communication with Argos satellite<br />
|-<br />
|serial ||int4||||NOT NULL||serial number of tag from manufacturer<br />
|-<br />
|weight ||int4||||NOT NULL||Unit = grams<br />
|-<br />
|type ||text||||NOT NULL||<br />
|-<br />
|manufacturer ||text||||||Device manufacturer<br />
|-<br />
|hexadecimal_id||text||||||Hexadecimal address, unique for each tag<br />
|-<br />
|PAN_id||Text||||||Personal area network ground based tags communicates with<br />
|-<br />
|Base_station_id||Int4||||||base station ground based tag communicates with<br />
|-<br />
|Remarks||text||||||<br />
|}<br />
<br />
== TRACK_SESSION == <br />
<br />
This table includes information about each measurement session and enables inclusion of data from new species and also from the test phase of different tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4 ||PK||NOT NULL||unique ID for each usage of a PTT so test and bird with same ptt_id are two separate IDs/indexes<br />
|-<br />
|''pttid''||int4 ||FK||NOT NULL||Link to DEVICE_INFO table<br />
|-<br />
|''ring_number''||text ||FK||||link to individual table – tests do not have a ring_number<br />
|-<br />
|start_date ||timestamptz||||||Date/time (Local) when tracking begins<br />
|-<br />
|start_latitude ||float8||||NOT NULL||latitude where tracking begins, unit = dec degress<br />
|-<br />
|start_longitude ||float8||||NOT NULL||longitude where tracking begins, unit = dec degrees<br />
|-<br />
|start_altitude||Float8||||||Unit = m, include when known, important for testing<br />
|-<br />
|end_date||timestamptz||||||End of session if known<br />
|-<br />
|time_window ||text||||||<br />
|-<br />
|time_steps ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|location ||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
== GPS_TRACKING_DATA ==<br />
<br />
Tracking data from GPS sensors on PTT/GPS tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||degrees<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|alt_status||text||||||<br />
|-<br />
|quality||text||||||Quality information from sensor<br />
|-<br />
|user_QC||text||||||Data flagged as unacceptable by user<br />
|-<br />
|parser_QC||text||||||Data flagged as unacceptable by Microwave parser<br />
|-<br />
|location||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
<br />
Note : <br />
<br />
The parser_QC value can be 1, 2,3,4, 99, or 100. If it 1 the data is OK. If it is 2 or 3 or 4 some form of error correction has been <br />
performed by the Microwave parser. And if it is 100 no error correction was possible. For reliable results it is advised only to use <br />
records with parser_QC values of 1<br />
<br />
== ARGOS_TRACKING_DATA ==<br />
<br />
Tracking data from Argos sensors<br />
<br />
{|border=1<br />
|'''Field'''||'''Type '''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4 ||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|fix ||text||||||<br />
|-<br />
|latitude1 ||float8||||||<br />
|-<br />
|longitude1 ||float8||||||<br />
|-<br />
|latitude2 ||float8||||||<br />
|-<br />
|longitude2 ||float8||||||<br />
|-<br />
|msgcount ||int4||||||<br />
|-<br />
|frequency ||float8||||||<br />
|-<br />
|average_ti ||float8||||||<br />
|-<br />
|satellite ||text||||||<br />
|-<br />
|max_str ||text||||||<br />
|-<br />
|location1 ||geometry||||||postgreSQL geometry<br />
|-<br />
|location2 ||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== PTT_ENGINEERING_DATA ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''tx_date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|'''satellite_id'''||text ||PK||NOT NULL||<br />
|-<br />
|ptt_date_time ||timestamp||||||GMT<br />
|-<br />
|activity||int4||||||<br />
|-<br />
|tx_count||int4||||||<br />
|-<br />
|temperature||float8||||||<br />
|-<br />
|battery_voltage||float8||||||<br />
|-<br />
|gps_fix_time||int4||||||<br />
|-<br />
|satellite_count||int4||||||<br />
|-<br />
|hours_reset||int4||||||<br />
|-<br />
|hours_since_gps_fix||int4||||||<br />
|-<br />
|mortality_gt||int4||||||<br />
|-<br />
|seasonal_gt||int4||||||<br />
|-<br />
|shunt||int4||||||<br />
|-<br />
|}<br />
<br />
<br />
In addition the views GPS_TRACKING_SESSION, ARGOS_TRACKING_SESSION, PTT_ENGINEERING_SESSION are which adds the correct track_session.id to the GPS_TRACKING_DATA, ARGOS_TRACKING_DATA and PTT_ENGINEERING_DATA table data.<br />
<br />
<br />
'''BIOLOGICAL INFORMATION'''<br />
<br />
== INDIVIDUAL ==<br />
<br />
Table includes information used to identify an individual<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ring_number'''||text||PK||NOT NULL||metal ring number<br />
|-<br />
|Id||int4||PK||NOT NULL ||auto-insert, unique ID for each individual organism <br />
|-<br />
|''NEST_INFO_id''||int4||FK||||link to NEST_INFO, not all specimens are linked to a nest<br />
|-<br />
|nest_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|species_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|ring_number||text||||NOT NULL||metal ring number<br />
|-<br />
|color_code||text||||||code for color ring without punctuation<br />
|-<br />
|species||text||||NOT NULL||Scientific name (at least genus)<br />
|-<br />
|sex||text||||||update if or when known<br />
|-<br />
|''FATE_CODEE_id''||textInt4||FK||||Link to FATE_CODE<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== FATE_code == <br />
<br />
{|border=1<br />
|Field ||Type||Key||Constraints||Comments<br />
|-<br />
|'''Id'''||'''Int4'''||'''PK'''||||'''auto-insert'''<br />
|-<br />
|code ||int4||PK||NOT NULL||<br />
|-<br />
|description||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== MEASUREMENT ==<br />
<br />
Metadata Provided by Sovon is needed to describe how these measurements are taken.<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4||PK||NOT NULL||auto-insert, unique ID for each observation<br />
|-<br />
|''ring_number''||text||FK||||link to individual<br />
|-<br />
|catch_datetime ||timestamp||||||Local time<br />
|-<br />
|release_datetime||timestamp||||||Local time<br />
|-<br />
|mass ||float8||||||grams<br />
|-<br />
|age ||text||||||AD = adult, JUV = juvenile<br />
|-<br />
|wing_length ||float8||||||<br />
|-<br />
|bill_length1 ||float8||||||<br />
|-<br />
|bill_length2 ||float8||||||<br />
|-<br />
|bill_height1 ||float8||||||<br />
|-<br />
|bill_height2 ||float8||||||<br />
|-<br />
|tarsus_length ||float8||||||<br />
|-<br />
|total_head||float8||||||<br />
|-<br />
|observer ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|}<br />
<br />
===Catch_datetime & release_datetime===<br />
<br />
During ringing of juveniles only the date was recorded and not the time. Birds were all released the same day. Ringing and measuring small chicks in the nest took about 2-5 minutes. Colour ringing and sampling of the larger chicks (from 4 July onwards) took about half an hour (rounding up several chicks and banding, sampling and releasing them together). To avoid leaving fields blank, a standard catch time was noted at 12:00 and a release time of 12:15 before July 4 and 12:30 from July 4 and onwards. ''''comments by Kees Oosterbeek''''<br />
<br />
== NEST_INFO ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|''id''||int4||PK ||NOT NULL||<br />
|-<br />
|Species||text||||||<br />
|-<br />
|latitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|longitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|year||Int4||||||Year of breeding season<br />
|-<br />
| "location"||geometry||||||postgreSQL geometry<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== NEST_OBSERVATION ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||''''''Comments''''''<br />
|-<br />
|''id''||''int4''||PK||NOT NULL ||Auto-insert, unique ID for each observation<br />
|-<br />
|''NEST_INFO_id''||''int4''||FK||NOT NULL ||<br />
|-<br />
|date||timestamptz ||||NOT NULL||<br />
|-<br />
|number_egg||int4||||||<br />
|-<br />
|number_young||int4||||||<br />
|-<br />
|pipping||text||||||Activity in egg (peeping or signs of hatching)<br />
|-<br />
|attended||text||||||Activity on nest<br />
|-<br />
|observer||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|}<br />
<br />
=Comments:=<br />
<br />
<br />
<br />
<br />
== Graphical Data Model == <br />
<br />
[[Image:Gps_datamodel.png ]]<br />
<br />
<br />
= Argos GPS functions = <br />
<br />
== get_argosgps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meter/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial. <br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows. <br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_argosgps_track_speed(41745);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. Because PostGIS does not calculate the heading we don't use PostGIS here.<br />
<br />
== get_argosgps_track_distance ==<br />
<br />
Compute distance (meters) for Argos GPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances from nest<br />
<br />
select * from gps.get_argosgps_track_distance(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
== get_argosgps_track_distance_direction ==<br />
<br />
Compute distance (meters) and direction (degrees) for Argos GPS tracks from arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, 53.23348333,4.91656)<br />
<br />
<br />
-- Get distances from nest<br />
create temporary table nest as<br />
( select n.latitude, n.longitude from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 );<br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, (select latitude from nest), (select longitude from nest));<br />
<br />
</pre><br />
<br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Argos_Data_Model&diff=322Argos Data Model2010-03-01T12:31:37Z<p>Bart: /* get_argosgps_track_distance_direction */</p>
<hr />
<div>== GPS Data Model == <br />
<br />
Last updated January 5, 2010 Bart Heupers - [[ UvAGPS ]] moved to special page<br />
<br />
Updated January 22, 2008 Judy Shamoun-Baranes <br />
<br />
'''FLYSAFE TRACKING DATABASE'''<br />
<br />
The tracking database will include data from several species. Some species are trapped and then monitored during the breeding season while others are trapped during the winter season. Information is collected on each tracked bird, including biometric measurements. These measurements may be collected more than once. During the breeding season information is also collected about the gull breeding colony itself, location of nests, state of breeding (number of eggs and juveniles) and then juveniles themselves are marked and measured (although not tracked).<br />
<br />
In addition, PTTs are often tested before they are actually placed on the birds. This information is also important during analysis and particularly to establish accuracy of data. This data should also be stored in the database. Therefore it is important that this information is stored properly in the database<br />
<br />
Units and descriptions should be filled in for all measurements<br />
<br />
One way of looking at this structure is considering 3 categories of tables: <br />
<br />
# '''lookup tables''' (information stored once) <br />
# '''session tables''' (stored occasionally) <br />
# '''observations''' – highest frequency of information.<br />
<br />
Primary keys are noted by bold italic text. Foreign keys are noted by italic text in the Field column.<br />
<br />
Microwave, will under no circumstances provide information about their checksum calculations. If feasible, SARA will duplicate the procedure and include a flag in the representing the microwave filtered data.<br />
<br />
'''TECHNICAL INFORMATION FROM TAGS'''<br />
<br />
<br />
== DEVICE_INFO ==<br />
<br />
Table including technical information about tag hardware. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL||serial number of PTT provided by Argos and used for communication with Argos satellite<br />
|-<br />
|serial ||int4||||NOT NULL||serial number of tag from manufacturer<br />
|-<br />
|weight ||int4||||NOT NULL||Unit = grams<br />
|-<br />
|type ||text||||NOT NULL||<br />
|-<br />
|manufacturer ||text||||||Device manufacturer<br />
|-<br />
|hexadecimal_id||text||||||Hexadecimal address, unique for each tag<br />
|-<br />
|PAN_id||Text||||||Personal area network ground based tags communicates with<br />
|-<br />
|Base_station_id||Int4||||||base station ground based tag communicates with<br />
|-<br />
|Remarks||text||||||<br />
|}<br />
<br />
== TRACK_SESSION == <br />
<br />
This table includes information about each measurement session and enables inclusion of data from new species and also from the test phase of different tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4 ||PK||NOT NULL||unique ID for each usage of a PTT so test and bird with same ptt_id are two separate IDs/indexes<br />
|-<br />
|''pttid''||int4 ||FK||NOT NULL||Link to DEVICE_INFO table<br />
|-<br />
|''ring_number''||text ||FK||||link to individual table – tests do not have a ring_number<br />
|-<br />
|start_date ||timestamptz||||||Date/time (Local) when tracking begins<br />
|-<br />
|start_latitude ||float8||||NOT NULL||latitude where tracking begins, unit = dec degress<br />
|-<br />
|start_longitude ||float8||||NOT NULL||longitude where tracking begins, unit = dec degrees<br />
|-<br />
|start_altitude||Float8||||||Unit = m, include when known, important for testing<br />
|-<br />
|end_date||timestamptz||||||End of session if known<br />
|-<br />
|time_window ||text||||||<br />
|-<br />
|time_steps ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|location ||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
== GPS_TRACKING_DATA ==<br />
<br />
Tracking data from GPS sensors on PTT/GPS tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||degrees<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|alt_status||text||||||<br />
|-<br />
|quality||text||||||Quality information from sensor<br />
|-<br />
|user_QC||text||||||Data flagged as unacceptable by user<br />
|-<br />
|parser_QC||text||||||Data flagged as unacceptable by Microwave parser<br />
|-<br />
|location||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
<br />
Note : <br />
<br />
The parser_QC value can be 1, 2,3,4, 99, or 100. If it 1 the data is OK. If it is 2 or 3 or 4 some form of error correction has been <br />
performed by the Microwave parser. And if it is 100 no error correction was possible. For reliable results it is advised only to use <br />
records with parser_QC values of 1<br />
<br />
== ARGOS_TRACKING_DATA ==<br />
<br />
Tracking data from Argos sensors<br />
<br />
{|border=1<br />
|'''Field'''||'''Type '''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4 ||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|fix ||text||||||<br />
|-<br />
|latitude1 ||float8||||||<br />
|-<br />
|longitude1 ||float8||||||<br />
|-<br />
|latitude2 ||float8||||||<br />
|-<br />
|longitude2 ||float8||||||<br />
|-<br />
|msgcount ||int4||||||<br />
|-<br />
|frequency ||float8||||||<br />
|-<br />
|average_ti ||float8||||||<br />
|-<br />
|satellite ||text||||||<br />
|-<br />
|max_str ||text||||||<br />
|-<br />
|location1 ||geometry||||||postgreSQL geometry<br />
|-<br />
|location2 ||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== PTT_ENGINEERING_DATA ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''tx_date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|'''satellite_id'''||text ||PK||NOT NULL||<br />
|-<br />
|ptt_date_time ||timestamp||||||GMT<br />
|-<br />
|activity||int4||||||<br />
|-<br />
|tx_count||int4||||||<br />
|-<br />
|temperature||float8||||||<br />
|-<br />
|battery_voltage||float8||||||<br />
|-<br />
|gps_fix_time||int4||||||<br />
|-<br />
|satellite_count||int4||||||<br />
|-<br />
|hours_reset||int4||||||<br />
|-<br />
|hours_since_gps_fix||int4||||||<br />
|-<br />
|mortality_gt||int4||||||<br />
|-<br />
|seasonal_gt||int4||||||<br />
|-<br />
|shunt||int4||||||<br />
|-<br />
|}<br />
<br />
<br />
In addition the views GPS_TRACKING_SESSION, ARGOS_TRACKING_SESSION, PTT_ENGINEERING_SESSION are which adds the correct track_session.id to the GPS_TRACKING_DATA, ARGOS_TRACKING_DATA and PTT_ENGINEERING_DATA table data.<br />
<br />
<br />
'''BIOLOGICAL INFORMATION'''<br />
<br />
== INDIVIDUAL ==<br />
<br />
Table includes information used to identify an individual<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ring_number'''||text||PK||NOT NULL||metal ring number<br />
|-<br />
|Id||int4||PK||NOT NULL ||auto-insert, unique ID for each individual organism <br />
|-<br />
|''NEST_INFO_id''||int4||FK||||link to NEST_INFO, not all specimens are linked to a nest<br />
|-<br />
|nest_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|species_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|ring_number||text||||NOT NULL||metal ring number<br />
|-<br />
|color_code||text||||||code for color ring without punctuation<br />
|-<br />
|species||text||||NOT NULL||Scientific name (at least genus)<br />
|-<br />
|sex||text||||||update if or when known<br />
|-<br />
|''FATE_CODEE_id''||textInt4||FK||||Link to FATE_CODE<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== FATE_code == <br />
<br />
{|border=1<br />
|Field ||Type||Key||Constraints||Comments<br />
|-<br />
|'''Id'''||'''Int4'''||'''PK'''||||'''auto-insert'''<br />
|-<br />
|code ||int4||PK||NOT NULL||<br />
|-<br />
|description||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== MEASUREMENT ==<br />
<br />
Metadata Provided by Sovon is needed to describe how these measurements are taken.<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4||PK||NOT NULL||auto-insert, unique ID for each observation<br />
|-<br />
|''ring_number''||text||FK||||link to individual<br />
|-<br />
|catch_datetime ||timestamp||||||Local time<br />
|-<br />
|release_datetime||timestamp||||||Local time<br />
|-<br />
|mass ||float8||||||grams<br />
|-<br />
|age ||text||||||AD = adult, JUV = juvenile<br />
|-<br />
|wing_length ||float8||||||<br />
|-<br />
|bill_length1 ||float8||||||<br />
|-<br />
|bill_length2 ||float8||||||<br />
|-<br />
|bill_height1 ||float8||||||<br />
|-<br />
|bill_height2 ||float8||||||<br />
|-<br />
|tarsus_length ||float8||||||<br />
|-<br />
|total_head||float8||||||<br />
|-<br />
|observer ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|}<br />
<br />
===Catch_datetime & release_datetime===<br />
<br />
During ringing of juveniles only the date was recorded and not the time. Birds were all released the same day. Ringing and measuring small chicks in the nest took about 2-5 minutes. Colour ringing and sampling of the larger chicks (from 4 July onwards) took about half an hour (rounding up several chicks and banding, sampling and releasing them together). To avoid leaving fields blank, a standard catch time was noted at 12:00 and a release time of 12:15 before July 4 and 12:30 from July 4 and onwards. ''''comments by Kees Oosterbeek''''<br />
<br />
== NEST_INFO ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|''id''||int4||PK ||NOT NULL||<br />
|-<br />
|Species||text||||||<br />
|-<br />
|latitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|longitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|year||Int4||||||Year of breeding season<br />
|-<br />
| "location"||geometry||||||postgreSQL geometry<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== NEST_OBSERVATION ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||''''''Comments''''''<br />
|-<br />
|''id''||''int4''||PK||NOT NULL ||Auto-insert, unique ID for each observation<br />
|-<br />
|''NEST_INFO_id''||''int4''||FK||NOT NULL ||<br />
|-<br />
|date||timestamptz ||||NOT NULL||<br />
|-<br />
|number_egg||int4||||||<br />
|-<br />
|number_young||int4||||||<br />
|-<br />
|pipping||text||||||Activity in egg (peeping or signs of hatching)<br />
|-<br />
|attended||text||||||Activity on nest<br />
|-<br />
|observer||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|}<br />
<br />
=Comments:=<br />
<br />
<br />
<br />
<br />
== Graphical Data Model == <br />
<br />
[[Image:Gps_datamodel.png ]]<br />
<br />
<br />
= Argos GPS functions = <br />
<br />
== get_argosgps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meter/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial. <br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows. <br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_argosgps_track_speed(41745);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. Because PostGIS does not calculate the heading we don't use PostGIS here.<br />
<br />
== get_argosgps_track_distance ==<br />
<br />
Compute distance (meters) for Argos GPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances from nest<br />
<br />
select * from gps.get_argosgps_track_distance(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
== get_argosgps_track_distance_direction ==<br />
<br />
Compute distance (meters) and direction (degrees) for Argos GPS tracks from arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, 53.23348333,4.91656)<br />
<br />
<br />
-- Get distances from nest<br />
create temporary table nest as<br />
( select n.latitude, n.longitude from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 );<br />
<br />
select * from gps.get_argosgps_track_distance(41745, (select latitude from nest), (select longitude from nest));<br />
<br />
</pre><br />
<br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Argos_Data_Model&diff=321Argos Data Model2010-03-01T12:13:27Z<p>Bart: /* get_argosgps_track_distance_direction */</p>
<hr />
<div>== GPS Data Model == <br />
<br />
Last updated January 5, 2010 Bart Heupers - [[ UvAGPS ]] moved to special page<br />
<br />
Updated January 22, 2008 Judy Shamoun-Baranes <br />
<br />
'''FLYSAFE TRACKING DATABASE'''<br />
<br />
The tracking database will include data from several species. Some species are trapped and then monitored during the breeding season while others are trapped during the winter season. Information is collected on each tracked bird, including biometric measurements. These measurements may be collected more than once. During the breeding season information is also collected about the gull breeding colony itself, location of nests, state of breeding (number of eggs and juveniles) and then juveniles themselves are marked and measured (although not tracked).<br />
<br />
In addition, PTTs are often tested before they are actually placed on the birds. This information is also important during analysis and particularly to establish accuracy of data. This data should also be stored in the database. Therefore it is important that this information is stored properly in the database<br />
<br />
Units and descriptions should be filled in for all measurements<br />
<br />
One way of looking at this structure is considering 3 categories of tables: <br />
<br />
# '''lookup tables''' (information stored once) <br />
# '''session tables''' (stored occasionally) <br />
# '''observations''' – highest frequency of information.<br />
<br />
Primary keys are noted by bold italic text. Foreign keys are noted by italic text in the Field column.<br />
<br />
Microwave, will under no circumstances provide information about their checksum calculations. If feasible, SARA will duplicate the procedure and include a flag in the representing the microwave filtered data.<br />
<br />
'''TECHNICAL INFORMATION FROM TAGS'''<br />
<br />
<br />
== DEVICE_INFO ==<br />
<br />
Table including technical information about tag hardware. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL||serial number of PTT provided by Argos and used for communication with Argos satellite<br />
|-<br />
|serial ||int4||||NOT NULL||serial number of tag from manufacturer<br />
|-<br />
|weight ||int4||||NOT NULL||Unit = grams<br />
|-<br />
|type ||text||||NOT NULL||<br />
|-<br />
|manufacturer ||text||||||Device manufacturer<br />
|-<br />
|hexadecimal_id||text||||||Hexadecimal address, unique for each tag<br />
|-<br />
|PAN_id||Text||||||Personal area network ground based tags communicates with<br />
|-<br />
|Base_station_id||Int4||||||base station ground based tag communicates with<br />
|-<br />
|Remarks||text||||||<br />
|}<br />
<br />
== TRACK_SESSION == <br />
<br />
This table includes information about each measurement session and enables inclusion of data from new species and also from the test phase of different tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4 ||PK||NOT NULL||unique ID for each usage of a PTT so test and bird with same ptt_id are two separate IDs/indexes<br />
|-<br />
|''pttid''||int4 ||FK||NOT NULL||Link to DEVICE_INFO table<br />
|-<br />
|''ring_number''||text ||FK||||link to individual table – tests do not have a ring_number<br />
|-<br />
|start_date ||timestamptz||||||Date/time (Local) when tracking begins<br />
|-<br />
|start_latitude ||float8||||NOT NULL||latitude where tracking begins, unit = dec degress<br />
|-<br />
|start_longitude ||float8||||NOT NULL||longitude where tracking begins, unit = dec degrees<br />
|-<br />
|start_altitude||Float8||||||Unit = m, include when known, important for testing<br />
|-<br />
|end_date||timestamptz||||||End of session if known<br />
|-<br />
|time_window ||text||||||<br />
|-<br />
|time_steps ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|location ||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
== GPS_TRACKING_DATA ==<br />
<br />
Tracking data from GPS sensors on PTT/GPS tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||degrees<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|alt_status||text||||||<br />
|-<br />
|quality||text||||||Quality information from sensor<br />
|-<br />
|user_QC||text||||||Data flagged as unacceptable by user<br />
|-<br />
|parser_QC||text||||||Data flagged as unacceptable by Microwave parser<br />
|-<br />
|location||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
<br />
Note : <br />
<br />
The parser_QC value can be 1, 2,3,4, 99, or 100. If it 1 the data is OK. If it is 2 or 3 or 4 some form of error correction has been <br />
performed by the Microwave parser. And if it is 100 no error correction was possible. For reliable results it is advised only to use <br />
records with parser_QC values of 1<br />
<br />
== ARGOS_TRACKING_DATA ==<br />
<br />
Tracking data from Argos sensors<br />
<br />
{|border=1<br />
|'''Field'''||'''Type '''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4 ||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|fix ||text||||||<br />
|-<br />
|latitude1 ||float8||||||<br />
|-<br />
|longitude1 ||float8||||||<br />
|-<br />
|latitude2 ||float8||||||<br />
|-<br />
|longitude2 ||float8||||||<br />
|-<br />
|msgcount ||int4||||||<br />
|-<br />
|frequency ||float8||||||<br />
|-<br />
|average_ti ||float8||||||<br />
|-<br />
|satellite ||text||||||<br />
|-<br />
|max_str ||text||||||<br />
|-<br />
|location1 ||geometry||||||postgreSQL geometry<br />
|-<br />
|location2 ||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== PTT_ENGINEERING_DATA ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''tx_date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|'''satellite_id'''||text ||PK||NOT NULL||<br />
|-<br />
|ptt_date_time ||timestamp||||||GMT<br />
|-<br />
|activity||int4||||||<br />
|-<br />
|tx_count||int4||||||<br />
|-<br />
|temperature||float8||||||<br />
|-<br />
|battery_voltage||float8||||||<br />
|-<br />
|gps_fix_time||int4||||||<br />
|-<br />
|satellite_count||int4||||||<br />
|-<br />
|hours_reset||int4||||||<br />
|-<br />
|hours_since_gps_fix||int4||||||<br />
|-<br />
|mortality_gt||int4||||||<br />
|-<br />
|seasonal_gt||int4||||||<br />
|-<br />
|shunt||int4||||||<br />
|-<br />
|}<br />
<br />
<br />
In addition the views GPS_TRACKING_SESSION, ARGOS_TRACKING_SESSION, PTT_ENGINEERING_SESSION are which adds the correct track_session.id to the GPS_TRACKING_DATA, ARGOS_TRACKING_DATA and PTT_ENGINEERING_DATA table data.<br />
<br />
<br />
'''BIOLOGICAL INFORMATION'''<br />
<br />
== INDIVIDUAL ==<br />
<br />
Table includes information used to identify an individual<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ring_number'''||text||PK||NOT NULL||metal ring number<br />
|-<br />
|Id||int4||PK||NOT NULL ||auto-insert, unique ID for each individual organism <br />
|-<br />
|''NEST_INFO_id''||int4||FK||||link to NEST_INFO, not all specimens are linked to a nest<br />
|-<br />
|nest_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|species_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|ring_number||text||||NOT NULL||metal ring number<br />
|-<br />
|color_code||text||||||code for color ring without punctuation<br />
|-<br />
|species||text||||NOT NULL||Scientific name (at least genus)<br />
|-<br />
|sex||text||||||update if or when known<br />
|-<br />
|''FATE_CODEE_id''||textInt4||FK||||Link to FATE_CODE<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== FATE_code == <br />
<br />
{|border=1<br />
|Field ||Type||Key||Constraints||Comments<br />
|-<br />
|'''Id'''||'''Int4'''||'''PK'''||||'''auto-insert'''<br />
|-<br />
|code ||int4||PK||NOT NULL||<br />
|-<br />
|description||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== MEASUREMENT ==<br />
<br />
Metadata Provided by Sovon is needed to describe how these measurements are taken.<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4||PK||NOT NULL||auto-insert, unique ID for each observation<br />
|-<br />
|''ring_number''||text||FK||||link to individual<br />
|-<br />
|catch_datetime ||timestamp||||||Local time<br />
|-<br />
|release_datetime||timestamp||||||Local time<br />
|-<br />
|mass ||float8||||||grams<br />
|-<br />
|age ||text||||||AD = adult, JUV = juvenile<br />
|-<br />
|wing_length ||float8||||||<br />
|-<br />
|bill_length1 ||float8||||||<br />
|-<br />
|bill_length2 ||float8||||||<br />
|-<br />
|bill_height1 ||float8||||||<br />
|-<br />
|bill_height2 ||float8||||||<br />
|-<br />
|tarsus_length ||float8||||||<br />
|-<br />
|total_head||float8||||||<br />
|-<br />
|observer ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|}<br />
<br />
===Catch_datetime & release_datetime===<br />
<br />
During ringing of juveniles only the date was recorded and not the time. Birds were all released the same day. Ringing and measuring small chicks in the nest took about 2-5 minutes. Colour ringing and sampling of the larger chicks (from 4 July onwards) took about half an hour (rounding up several chicks and banding, sampling and releasing them together). To avoid leaving fields blank, a standard catch time was noted at 12:00 and a release time of 12:15 before July 4 and 12:30 from July 4 and onwards. ''''comments by Kees Oosterbeek''''<br />
<br />
== NEST_INFO ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|''id''||int4||PK ||NOT NULL||<br />
|-<br />
|Species||text||||||<br />
|-<br />
|latitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|longitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|year||Int4||||||Year of breeding season<br />
|-<br />
| "location"||geometry||||||postgreSQL geometry<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== NEST_OBSERVATION ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||''''''Comments''''''<br />
|-<br />
|''id''||''int4''||PK||NOT NULL ||Auto-insert, unique ID for each observation<br />
|-<br />
|''NEST_INFO_id''||''int4''||FK||NOT NULL ||<br />
|-<br />
|date||timestamptz ||||NOT NULL||<br />
|-<br />
|number_egg||int4||||||<br />
|-<br />
|number_young||int4||||||<br />
|-<br />
|pipping||text||||||Activity in egg (peeping or signs of hatching)<br />
|-<br />
|attended||text||||||Activity on nest<br />
|-<br />
|observer||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|}<br />
<br />
=Comments:=<br />
<br />
<br />
<br />
<br />
== Graphical Data Model == <br />
<br />
[[Image:Gps_datamodel.png ]]<br />
<br />
<br />
= Argos GPS functions = <br />
<br />
== get_argosgps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meter/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial. <br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows. <br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_argosgps_track_speed(41745);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. Because PostGIS does not calculate the heading we don't use PostGIS here.<br />
<br />
== get_argosgps_track_distance ==<br />
<br />
Compute distance (meters) for Argos GPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances from nest<br />
<br />
select * from gps.get_argosgps_track_distance(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
== get_argosgps_track_distance_direction ==<br />
<br />
Compute distance (meters) and direction (degrees) for Argos GPS tracks from arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, 53.23348333,4.91656)<br />
<br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Argos_Data_Model&diff=320Argos Data Model2010-03-01T11:59:06Z<p>Bart: /* get_argosgps_track_distance_direction */</p>
<hr />
<div>== GPS Data Model == <br />
<br />
Last updated January 5, 2010 Bart Heupers - [[ UvAGPS ]] moved to special page<br />
<br />
Updated January 22, 2008 Judy Shamoun-Baranes <br />
<br />
'''FLYSAFE TRACKING DATABASE'''<br />
<br />
The tracking database will include data from several species. Some species are trapped and then monitored during the breeding season while others are trapped during the winter season. Information is collected on each tracked bird, including biometric measurements. These measurements may be collected more than once. During the breeding season information is also collected about the gull breeding colony itself, location of nests, state of breeding (number of eggs and juveniles) and then juveniles themselves are marked and measured (although not tracked).<br />
<br />
In addition, PTTs are often tested before they are actually placed on the birds. This information is also important during analysis and particularly to establish accuracy of data. This data should also be stored in the database. Therefore it is important that this information is stored properly in the database<br />
<br />
Units and descriptions should be filled in for all measurements<br />
<br />
One way of looking at this structure is considering 3 categories of tables: <br />
<br />
# '''lookup tables''' (information stored once) <br />
# '''session tables''' (stored occasionally) <br />
# '''observations''' – highest frequency of information.<br />
<br />
Primary keys are noted by bold italic text. Foreign keys are noted by italic text in the Field column.<br />
<br />
Microwave, will under no circumstances provide information about their checksum calculations. If feasible, SARA will duplicate the procedure and include a flag in the representing the microwave filtered data.<br />
<br />
'''TECHNICAL INFORMATION FROM TAGS'''<br />
<br />
<br />
== DEVICE_INFO ==<br />
<br />
Table including technical information about tag hardware. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL||serial number of PTT provided by Argos and used for communication with Argos satellite<br />
|-<br />
|serial ||int4||||NOT NULL||serial number of tag from manufacturer<br />
|-<br />
|weight ||int4||||NOT NULL||Unit = grams<br />
|-<br />
|type ||text||||NOT NULL||<br />
|-<br />
|manufacturer ||text||||||Device manufacturer<br />
|-<br />
|hexadecimal_id||text||||||Hexadecimal address, unique for each tag<br />
|-<br />
|PAN_id||Text||||||Personal area network ground based tags communicates with<br />
|-<br />
|Base_station_id||Int4||||||base station ground based tag communicates with<br />
|-<br />
|Remarks||text||||||<br />
|}<br />
<br />
== TRACK_SESSION == <br />
<br />
This table includes information about each measurement session and enables inclusion of data from new species and also from the test phase of different tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4 ||PK||NOT NULL||unique ID for each usage of a PTT so test and bird with same ptt_id are two separate IDs/indexes<br />
|-<br />
|''pttid''||int4 ||FK||NOT NULL||Link to DEVICE_INFO table<br />
|-<br />
|''ring_number''||text ||FK||||link to individual table – tests do not have a ring_number<br />
|-<br />
|start_date ||timestamptz||||||Date/time (Local) when tracking begins<br />
|-<br />
|start_latitude ||float8||||NOT NULL||latitude where tracking begins, unit = dec degress<br />
|-<br />
|start_longitude ||float8||||NOT NULL||longitude where tracking begins, unit = dec degrees<br />
|-<br />
|start_altitude||Float8||||||Unit = m, include when known, important for testing<br />
|-<br />
|end_date||timestamptz||||||End of session if known<br />
|-<br />
|time_window ||text||||||<br />
|-<br />
|time_steps ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|location ||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
== GPS_TRACKING_DATA ==<br />
<br />
Tracking data from GPS sensors on PTT/GPS tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||degrees<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|alt_status||text||||||<br />
|-<br />
|quality||text||||||Quality information from sensor<br />
|-<br />
|user_QC||text||||||Data flagged as unacceptable by user<br />
|-<br />
|parser_QC||text||||||Data flagged as unacceptable by Microwave parser<br />
|-<br />
|location||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
<br />
Note : <br />
<br />
The parser_QC value can be 1, 2,3,4, 99, or 100. If it 1 the data is OK. If it is 2 or 3 or 4 some form of error correction has been <br />
performed by the Microwave parser. And if it is 100 no error correction was possible. For reliable results it is advised only to use <br />
records with parser_QC values of 1<br />
<br />
== ARGOS_TRACKING_DATA ==<br />
<br />
Tracking data from Argos sensors<br />
<br />
{|border=1<br />
|'''Field'''||'''Type '''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4 ||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|fix ||text||||||<br />
|-<br />
|latitude1 ||float8||||||<br />
|-<br />
|longitude1 ||float8||||||<br />
|-<br />
|latitude2 ||float8||||||<br />
|-<br />
|longitude2 ||float8||||||<br />
|-<br />
|msgcount ||int4||||||<br />
|-<br />
|frequency ||float8||||||<br />
|-<br />
|average_ti ||float8||||||<br />
|-<br />
|satellite ||text||||||<br />
|-<br />
|max_str ||text||||||<br />
|-<br />
|location1 ||geometry||||||postgreSQL geometry<br />
|-<br />
|location2 ||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== PTT_ENGINEERING_DATA ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''tx_date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|'''satellite_id'''||text ||PK||NOT NULL||<br />
|-<br />
|ptt_date_time ||timestamp||||||GMT<br />
|-<br />
|activity||int4||||||<br />
|-<br />
|tx_count||int4||||||<br />
|-<br />
|temperature||float8||||||<br />
|-<br />
|battery_voltage||float8||||||<br />
|-<br />
|gps_fix_time||int4||||||<br />
|-<br />
|satellite_count||int4||||||<br />
|-<br />
|hours_reset||int4||||||<br />
|-<br />
|hours_since_gps_fix||int4||||||<br />
|-<br />
|mortality_gt||int4||||||<br />
|-<br />
|seasonal_gt||int4||||||<br />
|-<br />
|shunt||int4||||||<br />
|-<br />
|}<br />
<br />
<br />
In addition the views GPS_TRACKING_SESSION, ARGOS_TRACKING_SESSION, PTT_ENGINEERING_SESSION are which adds the correct track_session.id to the GPS_TRACKING_DATA, ARGOS_TRACKING_DATA and PTT_ENGINEERING_DATA table data.<br />
<br />
<br />
'''BIOLOGICAL INFORMATION'''<br />
<br />
== INDIVIDUAL ==<br />
<br />
Table includes information used to identify an individual<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ring_number'''||text||PK||NOT NULL||metal ring number<br />
|-<br />
|Id||int4||PK||NOT NULL ||auto-insert, unique ID for each individual organism <br />
|-<br />
|''NEST_INFO_id''||int4||FK||||link to NEST_INFO, not all specimens are linked to a nest<br />
|-<br />
|nest_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|species_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|ring_number||text||||NOT NULL||metal ring number<br />
|-<br />
|color_code||text||||||code for color ring without punctuation<br />
|-<br />
|species||text||||NOT NULL||Scientific name (at least genus)<br />
|-<br />
|sex||text||||||update if or when known<br />
|-<br />
|''FATE_CODEE_id''||textInt4||FK||||Link to FATE_CODE<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== FATE_code == <br />
<br />
{|border=1<br />
|Field ||Type||Key||Constraints||Comments<br />
|-<br />
|'''Id'''||'''Int4'''||'''PK'''||||'''auto-insert'''<br />
|-<br />
|code ||int4||PK||NOT NULL||<br />
|-<br />
|description||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== MEASUREMENT ==<br />
<br />
Metadata Provided by Sovon is needed to describe how these measurements are taken.<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4||PK||NOT NULL||auto-insert, unique ID for each observation<br />
|-<br />
|''ring_number''||text||FK||||link to individual<br />
|-<br />
|catch_datetime ||timestamp||||||Local time<br />
|-<br />
|release_datetime||timestamp||||||Local time<br />
|-<br />
|mass ||float8||||||grams<br />
|-<br />
|age ||text||||||AD = adult, JUV = juvenile<br />
|-<br />
|wing_length ||float8||||||<br />
|-<br />
|bill_length1 ||float8||||||<br />
|-<br />
|bill_length2 ||float8||||||<br />
|-<br />
|bill_height1 ||float8||||||<br />
|-<br />
|bill_height2 ||float8||||||<br />
|-<br />
|tarsus_length ||float8||||||<br />
|-<br />
|total_head||float8||||||<br />
|-<br />
|observer ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|}<br />
<br />
===Catch_datetime & release_datetime===<br />
<br />
During ringing of juveniles only the date was recorded and not the time. Birds were all released the same day. Ringing and measuring small chicks in the nest took about 2-5 minutes. Colour ringing and sampling of the larger chicks (from 4 July onwards) took about half an hour (rounding up several chicks and banding, sampling and releasing them together). To avoid leaving fields blank, a standard catch time was noted at 12:00 and a release time of 12:15 before July 4 and 12:30 from July 4 and onwards. ''''comments by Kees Oosterbeek''''<br />
<br />
== NEST_INFO ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|''id''||int4||PK ||NOT NULL||<br />
|-<br />
|Species||text||||||<br />
|-<br />
|latitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|longitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|year||Int4||||||Year of breeding season<br />
|-<br />
| "location"||geometry||||||postgreSQL geometry<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== NEST_OBSERVATION ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||''''''Comments''''''<br />
|-<br />
|''id''||''int4''||PK||NOT NULL ||Auto-insert, unique ID for each observation<br />
|-<br />
|''NEST_INFO_id''||''int4''||FK||NOT NULL ||<br />
|-<br />
|date||timestamptz ||||NOT NULL||<br />
|-<br />
|number_egg||int4||||||<br />
|-<br />
|number_young||int4||||||<br />
|-<br />
|pipping||text||||||Activity in egg (peeping or signs of hatching)<br />
|-<br />
|attended||text||||||Activity on nest<br />
|-<br />
|observer||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|}<br />
<br />
=Comments:=<br />
<br />
<br />
<br />
<br />
== Graphical Data Model == <br />
<br />
[[Image:Gps_datamodel.png ]]<br />
<br />
<br />
= Argos GPS functions = <br />
<br />
== get_argosgps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meter/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial. <br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows. <br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_argosgps_track_speed(41745);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. Because PostGIS does not calculate the heading we don't use PostGIS here.<br />
<br />
== get_argosgps_track_distance ==<br />
<br />
Compute distance (meters) for Argos GPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances from nest<br />
<br />
select * from gps.get_argosgps_track_distance(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
== get_argosgps_track_distance_direction ==<br />
<br />
Compute distance (meters) and direction (degrees) for Argos GPS tracks from arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances and direction to nest<br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=319UvAGPS2010-03-01T11:58:34Z<p>Bart: /* get_uvagps_track_distance */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
== UVA_TRACKING_DATA ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|quality||text||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE == <br />
<br />
To be able to track the different firmware versions for the different devices the UVA_DEVICE table was added.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|- <br />
| firmware_version || text |||| NOT NULL ||<br />
|}<br />
<br />
== UVA_COMM101 == <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
<br />
== UVA_SETTINGS101 == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 ==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
<br />
== get_uvagps_track_distance_direction ==<br />
<br />
<br />
Compute distance (meters) and direction (degrees) for UvAGPS tracks from arbitrary point in lat/long or geometry location<br />
<br />
Example usage: <br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance_direction(119, 52.1897017, 6.1996606); <br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. The direction is the direction from the given point.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Argos_Data_Model&diff=318Argos Data Model2010-02-25T16:44:12Z<p>Bart: /* get_argosgps_track_distance_direction */</p>
<hr />
<div>== GPS Data Model == <br />
<br />
Last updated January 5, 2010 Bart Heupers - [[ UvAGPS ]] moved to special page<br />
<br />
Updated January 22, 2008 Judy Shamoun-Baranes <br />
<br />
'''FLYSAFE TRACKING DATABASE'''<br />
<br />
The tracking database will include data from several species. Some species are trapped and then monitored during the breeding season while others are trapped during the winter season. Information is collected on each tracked bird, including biometric measurements. These measurements may be collected more than once. During the breeding season information is also collected about the gull breeding colony itself, location of nests, state of breeding (number of eggs and juveniles) and then juveniles themselves are marked and measured (although not tracked).<br />
<br />
In addition, PTTs are often tested before they are actually placed on the birds. This information is also important during analysis and particularly to establish accuracy of data. This data should also be stored in the database. Therefore it is important that this information is stored properly in the database<br />
<br />
Units and descriptions should be filled in for all measurements<br />
<br />
One way of looking at this structure is considering 3 categories of tables: <br />
<br />
# '''lookup tables''' (information stored once) <br />
# '''session tables''' (stored occasionally) <br />
# '''observations''' – highest frequency of information.<br />
<br />
Primary keys are noted by bold italic text. Foreign keys are noted by italic text in the Field column.<br />
<br />
Microwave, will under no circumstances provide information about their checksum calculations. If feasible, SARA will duplicate the procedure and include a flag in the representing the microwave filtered data.<br />
<br />
'''TECHNICAL INFORMATION FROM TAGS'''<br />
<br />
<br />
== DEVICE_INFO ==<br />
<br />
Table including technical information about tag hardware. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL||serial number of PTT provided by Argos and used for communication with Argos satellite<br />
|-<br />
|serial ||int4||||NOT NULL||serial number of tag from manufacturer<br />
|-<br />
|weight ||int4||||NOT NULL||Unit = grams<br />
|-<br />
|type ||text||||NOT NULL||<br />
|-<br />
|manufacturer ||text||||||Device manufacturer<br />
|-<br />
|hexadecimal_id||text||||||Hexadecimal address, unique for each tag<br />
|-<br />
|PAN_id||Text||||||Personal area network ground based tags communicates with<br />
|-<br />
|Base_station_id||Int4||||||base station ground based tag communicates with<br />
|-<br />
|Remarks||text||||||<br />
|}<br />
<br />
== TRACK_SESSION == <br />
<br />
This table includes information about each measurement session and enables inclusion of data from new species and also from the test phase of different tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4 ||PK||NOT NULL||unique ID for each usage of a PTT so test and bird with same ptt_id are two separate IDs/indexes<br />
|-<br />
|''pttid''||int4 ||FK||NOT NULL||Link to DEVICE_INFO table<br />
|-<br />
|''ring_number''||text ||FK||||link to individual table – tests do not have a ring_number<br />
|-<br />
|start_date ||timestamptz||||||Date/time (Local) when tracking begins<br />
|-<br />
|start_latitude ||float8||||NOT NULL||latitude where tracking begins, unit = dec degress<br />
|-<br />
|start_longitude ||float8||||NOT NULL||longitude where tracking begins, unit = dec degrees<br />
|-<br />
|start_altitude||Float8||||||Unit = m, include when known, important for testing<br />
|-<br />
|end_date||timestamptz||||||End of session if known<br />
|-<br />
|time_window ||text||||||<br />
|-<br />
|time_steps ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|location ||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
== GPS_TRACKING_DATA ==<br />
<br />
Tracking data from GPS sensors on PTT/GPS tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||degrees<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|alt_status||text||||||<br />
|-<br />
|quality||text||||||Quality information from sensor<br />
|-<br />
|user_QC||text||||||Data flagged as unacceptable by user<br />
|-<br />
|parser_QC||text||||||Data flagged as unacceptable by Microwave parser<br />
|-<br />
|location||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
<br />
Note : <br />
<br />
The parser_QC value can be 1, 2,3,4, 99, or 100. If it 1 the data is OK. If it is 2 or 3 or 4 some form of error correction has been <br />
performed by the Microwave parser. And if it is 100 no error correction was possible. For reliable results it is advised only to use <br />
records with parser_QC values of 1<br />
<br />
== ARGOS_TRACKING_DATA ==<br />
<br />
Tracking data from Argos sensors<br />
<br />
{|border=1<br />
|'''Field'''||'''Type '''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4 ||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|fix ||text||||||<br />
|-<br />
|latitude1 ||float8||||||<br />
|-<br />
|longitude1 ||float8||||||<br />
|-<br />
|latitude2 ||float8||||||<br />
|-<br />
|longitude2 ||float8||||||<br />
|-<br />
|msgcount ||int4||||||<br />
|-<br />
|frequency ||float8||||||<br />
|-<br />
|average_ti ||float8||||||<br />
|-<br />
|satellite ||text||||||<br />
|-<br />
|max_str ||text||||||<br />
|-<br />
|location1 ||geometry||||||postgreSQL geometry<br />
|-<br />
|location2 ||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== PTT_ENGINEERING_DATA ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''tx_date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|'''satellite_id'''||text ||PK||NOT NULL||<br />
|-<br />
|ptt_date_time ||timestamp||||||GMT<br />
|-<br />
|activity||int4||||||<br />
|-<br />
|tx_count||int4||||||<br />
|-<br />
|temperature||float8||||||<br />
|-<br />
|battery_voltage||float8||||||<br />
|-<br />
|gps_fix_time||int4||||||<br />
|-<br />
|satellite_count||int4||||||<br />
|-<br />
|hours_reset||int4||||||<br />
|-<br />
|hours_since_gps_fix||int4||||||<br />
|-<br />
|mortality_gt||int4||||||<br />
|-<br />
|seasonal_gt||int4||||||<br />
|-<br />
|shunt||int4||||||<br />
|-<br />
|}<br />
<br />
<br />
In addition the views GPS_TRACKING_SESSION, ARGOS_TRACKING_SESSION, PTT_ENGINEERING_SESSION are which adds the correct track_session.id to the GPS_TRACKING_DATA, ARGOS_TRACKING_DATA and PTT_ENGINEERING_DATA table data.<br />
<br />
<br />
'''BIOLOGICAL INFORMATION'''<br />
<br />
== INDIVIDUAL ==<br />
<br />
Table includes information used to identify an individual<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ring_number'''||text||PK||NOT NULL||metal ring number<br />
|-<br />
|Id||int4||PK||NOT NULL ||auto-insert, unique ID for each individual organism <br />
|-<br />
|''NEST_INFO_id''||int4||FK||||link to NEST_INFO, not all specimens are linked to a nest<br />
|-<br />
|nest_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|species_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|ring_number||text||||NOT NULL||metal ring number<br />
|-<br />
|color_code||text||||||code for color ring without punctuation<br />
|-<br />
|species||text||||NOT NULL||Scientific name (at least genus)<br />
|-<br />
|sex||text||||||update if or when known<br />
|-<br />
|''FATE_CODEE_id''||textInt4||FK||||Link to FATE_CODE<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== FATE_code == <br />
<br />
{|border=1<br />
|Field ||Type||Key||Constraints||Comments<br />
|-<br />
|'''Id'''||'''Int4'''||'''PK'''||||'''auto-insert'''<br />
|-<br />
|code ||int4||PK||NOT NULL||<br />
|-<br />
|description||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== MEASUREMENT ==<br />
<br />
Metadata Provided by Sovon is needed to describe how these measurements are taken.<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4||PK||NOT NULL||auto-insert, unique ID for each observation<br />
|-<br />
|''ring_number''||text||FK||||link to individual<br />
|-<br />
|catch_datetime ||timestamp||||||Local time<br />
|-<br />
|release_datetime||timestamp||||||Local time<br />
|-<br />
|mass ||float8||||||grams<br />
|-<br />
|age ||text||||||AD = adult, JUV = juvenile<br />
|-<br />
|wing_length ||float8||||||<br />
|-<br />
|bill_length1 ||float8||||||<br />
|-<br />
|bill_length2 ||float8||||||<br />
|-<br />
|bill_height1 ||float8||||||<br />
|-<br />
|bill_height2 ||float8||||||<br />
|-<br />
|tarsus_length ||float8||||||<br />
|-<br />
|total_head||float8||||||<br />
|-<br />
|observer ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|}<br />
<br />
===Catch_datetime & release_datetime===<br />
<br />
During ringing of juveniles only the date was recorded and not the time. Birds were all released the same day. Ringing and measuring small chicks in the nest took about 2-5 minutes. Colour ringing and sampling of the larger chicks (from 4 July onwards) took about half an hour (rounding up several chicks and banding, sampling and releasing them together). To avoid leaving fields blank, a standard catch time was noted at 12:00 and a release time of 12:15 before July 4 and 12:30 from July 4 and onwards. ''''comments by Kees Oosterbeek''''<br />
<br />
== NEST_INFO ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|''id''||int4||PK ||NOT NULL||<br />
|-<br />
|Species||text||||||<br />
|-<br />
|latitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|longitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|year||Int4||||||Year of breeding season<br />
|-<br />
| "location"||geometry||||||postgreSQL geometry<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== NEST_OBSERVATION ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||''''''Comments''''''<br />
|-<br />
|''id''||''int4''||PK||NOT NULL ||Auto-insert, unique ID for each observation<br />
|-<br />
|''NEST_INFO_id''||''int4''||FK||NOT NULL ||<br />
|-<br />
|date||timestamptz ||||NOT NULL||<br />
|-<br />
|number_egg||int4||||||<br />
|-<br />
|number_young||int4||||||<br />
|-<br />
|pipping||text||||||Activity in egg (peeping or signs of hatching)<br />
|-<br />
|attended||text||||||Activity on nest<br />
|-<br />
|observer||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|}<br />
<br />
=Comments:=<br />
<br />
<br />
<br />
<br />
== Graphical Data Model == <br />
<br />
[[Image:Gps_datamodel.png ]]<br />
<br />
<br />
= Argos GPS functions = <br />
<br />
== get_argosgps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meter/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial. <br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows. <br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_argosgps_track_speed(41745);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. Because PostGIS does not calculate the heading we don't use PostGIS here.<br />
<br />
== get_argosgps_track_distance ==<br />
<br />
Compute distance (meters) for Argos GPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances from nest<br />
<br />
select * from gps.get_argosgps_track_distance(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
== get_argosgps_track_distance_direction ==<br />
<br />
Compute distance (meters) and direction (degrees) for Argos GPS tracks from arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances and direction to nest<br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Distances and direction are calculated with spherical correction with the Haversine formula as described here. The direction is the direction from the given point.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Argos_Data_Model&diff=317Argos Data Model2010-02-25T16:40:55Z<p>Bart: /* get_argosgps_track_distance */</p>
<hr />
<div>== GPS Data Model == <br />
<br />
Last updated January 5, 2010 Bart Heupers - [[ UvAGPS ]] moved to special page<br />
<br />
Updated January 22, 2008 Judy Shamoun-Baranes <br />
<br />
'''FLYSAFE TRACKING DATABASE'''<br />
<br />
The tracking database will include data from several species. Some species are trapped and then monitored during the breeding season while others are trapped during the winter season. Information is collected on each tracked bird, including biometric measurements. These measurements may be collected more than once. During the breeding season information is also collected about the gull breeding colony itself, location of nests, state of breeding (number of eggs and juveniles) and then juveniles themselves are marked and measured (although not tracked).<br />
<br />
In addition, PTTs are often tested before they are actually placed on the birds. This information is also important during analysis and particularly to establish accuracy of data. This data should also be stored in the database. Therefore it is important that this information is stored properly in the database<br />
<br />
Units and descriptions should be filled in for all measurements<br />
<br />
One way of looking at this structure is considering 3 categories of tables: <br />
<br />
# '''lookup tables''' (information stored once) <br />
# '''session tables''' (stored occasionally) <br />
# '''observations''' – highest frequency of information.<br />
<br />
Primary keys are noted by bold italic text. Foreign keys are noted by italic text in the Field column.<br />
<br />
Microwave, will under no circumstances provide information about their checksum calculations. If feasible, SARA will duplicate the procedure and include a flag in the representing the microwave filtered data.<br />
<br />
'''TECHNICAL INFORMATION FROM TAGS'''<br />
<br />
<br />
== DEVICE_INFO ==<br />
<br />
Table including technical information about tag hardware. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL||serial number of PTT provided by Argos and used for communication with Argos satellite<br />
|-<br />
|serial ||int4||||NOT NULL||serial number of tag from manufacturer<br />
|-<br />
|weight ||int4||||NOT NULL||Unit = grams<br />
|-<br />
|type ||text||||NOT NULL||<br />
|-<br />
|manufacturer ||text||||||Device manufacturer<br />
|-<br />
|hexadecimal_id||text||||||Hexadecimal address, unique for each tag<br />
|-<br />
|PAN_id||Text||||||Personal area network ground based tags communicates with<br />
|-<br />
|Base_station_id||Int4||||||base station ground based tag communicates with<br />
|-<br />
|Remarks||text||||||<br />
|}<br />
<br />
== TRACK_SESSION == <br />
<br />
This table includes information about each measurement session and enables inclusion of data from new species and also from the test phase of different tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4 ||PK||NOT NULL||unique ID for each usage of a PTT so test and bird with same ptt_id are two separate IDs/indexes<br />
|-<br />
|''pttid''||int4 ||FK||NOT NULL||Link to DEVICE_INFO table<br />
|-<br />
|''ring_number''||text ||FK||||link to individual table – tests do not have a ring_number<br />
|-<br />
|start_date ||timestamptz||||||Date/time (Local) when tracking begins<br />
|-<br />
|start_latitude ||float8||||NOT NULL||latitude where tracking begins, unit = dec degress<br />
|-<br />
|start_longitude ||float8||||NOT NULL||longitude where tracking begins, unit = dec degrees<br />
|-<br />
|start_altitude||Float8||||||Unit = m, include when known, important for testing<br />
|-<br />
|end_date||timestamptz||||||End of session if known<br />
|-<br />
|time_window ||text||||||<br />
|-<br />
|time_steps ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|location ||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
== GPS_TRACKING_DATA ==<br />
<br />
Tracking data from GPS sensors on PTT/GPS tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||degrees<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|alt_status||text||||||<br />
|-<br />
|quality||text||||||Quality information from sensor<br />
|-<br />
|user_QC||text||||||Data flagged as unacceptable by user<br />
|-<br />
|parser_QC||text||||||Data flagged as unacceptable by Microwave parser<br />
|-<br />
|location||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
<br />
Note : <br />
<br />
The parser_QC value can be 1, 2,3,4, 99, or 100. If it 1 the data is OK. If it is 2 or 3 or 4 some form of error correction has been <br />
performed by the Microwave parser. And if it is 100 no error correction was possible. For reliable results it is advised only to use <br />
records with parser_QC values of 1<br />
<br />
== ARGOS_TRACKING_DATA ==<br />
<br />
Tracking data from Argos sensors<br />
<br />
{|border=1<br />
|'''Field'''||'''Type '''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4 ||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|fix ||text||||||<br />
|-<br />
|latitude1 ||float8||||||<br />
|-<br />
|longitude1 ||float8||||||<br />
|-<br />
|latitude2 ||float8||||||<br />
|-<br />
|longitude2 ||float8||||||<br />
|-<br />
|msgcount ||int4||||||<br />
|-<br />
|frequency ||float8||||||<br />
|-<br />
|average_ti ||float8||||||<br />
|-<br />
|satellite ||text||||||<br />
|-<br />
|max_str ||text||||||<br />
|-<br />
|location1 ||geometry||||||postgreSQL geometry<br />
|-<br />
|location2 ||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== PTT_ENGINEERING_DATA ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''tx_date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|'''satellite_id'''||text ||PK||NOT NULL||<br />
|-<br />
|ptt_date_time ||timestamp||||||GMT<br />
|-<br />
|activity||int4||||||<br />
|-<br />
|tx_count||int4||||||<br />
|-<br />
|temperature||float8||||||<br />
|-<br />
|battery_voltage||float8||||||<br />
|-<br />
|gps_fix_time||int4||||||<br />
|-<br />
|satellite_count||int4||||||<br />
|-<br />
|hours_reset||int4||||||<br />
|-<br />
|hours_since_gps_fix||int4||||||<br />
|-<br />
|mortality_gt||int4||||||<br />
|-<br />
|seasonal_gt||int4||||||<br />
|-<br />
|shunt||int4||||||<br />
|-<br />
|}<br />
<br />
<br />
In addition the views GPS_TRACKING_SESSION, ARGOS_TRACKING_SESSION, PTT_ENGINEERING_SESSION are which adds the correct track_session.id to the GPS_TRACKING_DATA, ARGOS_TRACKING_DATA and PTT_ENGINEERING_DATA table data.<br />
<br />
<br />
'''BIOLOGICAL INFORMATION'''<br />
<br />
== INDIVIDUAL ==<br />
<br />
Table includes information used to identify an individual<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ring_number'''||text||PK||NOT NULL||metal ring number<br />
|-<br />
|Id||int4||PK||NOT NULL ||auto-insert, unique ID for each individual organism <br />
|-<br />
|''NEST_INFO_id''||int4||FK||||link to NEST_INFO, not all specimens are linked to a nest<br />
|-<br />
|nest_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|species_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|ring_number||text||||NOT NULL||metal ring number<br />
|-<br />
|color_code||text||||||code for color ring without punctuation<br />
|-<br />
|species||text||||NOT NULL||Scientific name (at least genus)<br />
|-<br />
|sex||text||||||update if or when known<br />
|-<br />
|''FATE_CODEE_id''||textInt4||FK||||Link to FATE_CODE<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== FATE_code == <br />
<br />
{|border=1<br />
|Field ||Type||Key||Constraints||Comments<br />
|-<br />
|'''Id'''||'''Int4'''||'''PK'''||||'''auto-insert'''<br />
|-<br />
|code ||int4||PK||NOT NULL||<br />
|-<br />
|description||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== MEASUREMENT ==<br />
<br />
Metadata Provided by Sovon is needed to describe how these measurements are taken.<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4||PK||NOT NULL||auto-insert, unique ID for each observation<br />
|-<br />
|''ring_number''||text||FK||||link to individual<br />
|-<br />
|catch_datetime ||timestamp||||||Local time<br />
|-<br />
|release_datetime||timestamp||||||Local time<br />
|-<br />
|mass ||float8||||||grams<br />
|-<br />
|age ||text||||||AD = adult, JUV = juvenile<br />
|-<br />
|wing_length ||float8||||||<br />
|-<br />
|bill_length1 ||float8||||||<br />
|-<br />
|bill_length2 ||float8||||||<br />
|-<br />
|bill_height1 ||float8||||||<br />
|-<br />
|bill_height2 ||float8||||||<br />
|-<br />
|tarsus_length ||float8||||||<br />
|-<br />
|total_head||float8||||||<br />
|-<br />
|observer ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|}<br />
<br />
===Catch_datetime & release_datetime===<br />
<br />
During ringing of juveniles only the date was recorded and not the time. Birds were all released the same day. Ringing and measuring small chicks in the nest took about 2-5 minutes. Colour ringing and sampling of the larger chicks (from 4 July onwards) took about half an hour (rounding up several chicks and banding, sampling and releasing them together). To avoid leaving fields blank, a standard catch time was noted at 12:00 and a release time of 12:15 before July 4 and 12:30 from July 4 and onwards. ''''comments by Kees Oosterbeek''''<br />
<br />
== NEST_INFO ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|''id''||int4||PK ||NOT NULL||<br />
|-<br />
|Species||text||||||<br />
|-<br />
|latitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|longitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|year||Int4||||||Year of breeding season<br />
|-<br />
| "location"||geometry||||||postgreSQL geometry<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== NEST_OBSERVATION ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||''''''Comments''''''<br />
|-<br />
|''id''||''int4''||PK||NOT NULL ||Auto-insert, unique ID for each observation<br />
|-<br />
|''NEST_INFO_id''||''int4''||FK||NOT NULL ||<br />
|-<br />
|date||timestamptz ||||NOT NULL||<br />
|-<br />
|number_egg||int4||||||<br />
|-<br />
|number_young||int4||||||<br />
|-<br />
|pipping||text||||||Activity in egg (peeping or signs of hatching)<br />
|-<br />
|attended||text||||||Activity on nest<br />
|-<br />
|observer||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|}<br />
<br />
=Comments:=<br />
<br />
<br />
<br />
<br />
== Graphical Data Model == <br />
<br />
[[Image:Gps_datamodel.png ]]<br />
<br />
<br />
= Argos GPS functions = <br />
<br />
== get_argosgps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meter/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial. <br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows. <br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_argosgps_track_speed(41745);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. Because PostGIS does not calculate the heading we don't use PostGIS here.<br />
<br />
== get_argosgps_track_distance ==<br />
<br />
Compute distance (meters) for Argos GPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances from nest<br />
<br />
select * from gps.get_argosgps_track_distance(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.<br />
<br />
== get_argosgps_track_distance_direction ==<br />
<br />
Compute distance (meters) and direction (degrees) for Argos GPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances and direction to nest<br />
<br />
select * from gps.get_argosgps_track_distance_direction(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre></div>Barthttps://wiki.e-ecology.nl/index.php?title=ECMWF&diff=316ECMWF2010-01-25T16:44:12Z<p>Bart: /* ANALYSIS */</p>
<hr />
<div>== ECMWF == <br />
<br />
Datamodel for the tables in the ECMWF schema. <br />
<br />
Data is created by the ECMWF and retrieved from the KNMI ftp site as GRIB files. The original GRIB files can also be retrieved from the flysafe server from :<br />
<br />
[https://flysafe-pps.grid.sara.nl/archive/knmi/ecmwf/ ECMWF Data Archive]<br />
<br />
More information about the parameters in these GRIB files can be retrieved from the [http://www.ecmwf.int/services/dissemination/3.1/Products_in_GRIB_code.html ECMWF website].<br />
<br />
== INVARIABLE == <br />
<br />
The INVARIABLE table contains data that is invariant over time. <br />
<br />
{|border=1<br />
|'''LATITUDE''' || degrees * 100 to make this a integer<br />
|-<br />
|'''LONGITUDE''' || degrees * 100 to make this a integer<br />
|-<br />
|Z || 129 Z Geopotential surface/model orography <br />
|-<br />
|LSM || 172 LSM Land sea mask <br />
|-<br />
|LOCATION || Latitude/longitude as GIS location <br />
|}<br />
<br />
<br />
The GIS LOCATION is only added to this table. This is because always the same values for latitude and longitude are used and then if the GIS location is required for the ANALYSIS or FORECAST tables it can be retrieved by joining to this table on the LATITUDE, LONGUTUDE fields.<br />
<br />
== FORECAST and UVA_FORECAST == <br />
<br />
The FORECAST table contains predicted values in steps of 3 hours till 72 hours ahead. The MODELTS is the timestamp for which this prediction applies. Two times a day new Forecast GRIB files will arrive. The newer FORECAST data that arrives for the same timestamp will overwrite the older data.<br />
<br />
The FORECAST (and UVA_FORECAST) table itself is a master table that does not contain any data. The inherited tables <br />
FORECAST<YEAR><MONTH> contain the data, but the master FORECAST or UVA_FORECAST table can be used to SELECT the data. <br />
<br />
Data till 2009-09 is owned by the UvA and can be accessed by anybody with ECMWF_READ rights by using the FORECAST_UVA table. The FORECAST table itself also references data after 2009-09 that is owned by RNLAF for which special access rights ECMWF_RNLAF_READ are required. <br />
<br />
{|border=1<br />
|'''MODELTS'''||Time for which this forecast applies = model run + step hours<br />
|-<br />
|'''LATITUDE'''||degrees * 100 to make this a integer<br />
|-<br />
|'''LONGITUDE'''||degrees * 100 to make this a integer<br />
|-<br />
|STEP||model step (smaller is more recent forecast)<br />
|-<br />
|SSRD||169 SSRD surface solar radiation downwards accumulated <br />
|-<br />
|TP||228 TP total precipitation accumulated <br />
|-<br />
|SP||134 SP surface pressure <br />
|-<br />
|BLH||159 BLH boundary layer height <br />
|-<br />
|TCC||164 TCC total cloud coverage <br />
|-<br />
|U10||165 10U 10 meters wind U-component <br />
|-<br />
|V10||166 10V 10 meters wind V-component <br />
|-<br />
|T2||167 2T 2 metres air temperature <br />
|-<br />
|D2||168 2D 2 metres dew point temperature <br />
|-<br />
|LCC||186 LCC low cloud coverage <br />
|-<br />
|''Pressure level 1000''||<br />
|-<br />
|T_1000||130 T temperature <br />
|-<br />
|U_1000||131 U U-wind component <br />
|-<br />
|V_1000||132 V V-wind component <br />
|-<br />
|GH_1000||156 GH geopotential height <br />
|-<br />
|R_1000||157 R relative humidity <br />
|-<br />
|''Pressure level 925''||<br />
|-<br />
|T_925 real||130 T temperature <br />
|-<br />
|U_925 real||131 U U-wind component <br />
|-<br />
|V_925 real||132 V V-wind component <br />
|-<br />
|GH_925 real||156 GH geopotential height <br />
|-<br />
|R_925 real||157 R relative humidity <br />
|-<br />
|''Pressure level 850''||<br />
|-<br />
|T_850||130 T temperature <br />
|-<br />
|U_850 real||131 U U-wind component <br />
|-<br />
|V_850 real||132 V V-wind component <br />
|-<br />
|GH_850 real||156 GH geopotential height <br />
|-<br />
|R_850 real||157 R relative humidity <br />
|-<br />
|''Pressure level 700''||<br />
|-<br />
|T_700 real||130 T temperature <br />
|-<br />
|U_700 real||131 U U-wind component <br />
|-<br />
|V_700 real||132 V V-wind component <br />
|-<br />
|GH_700 real||156 GH geopotential height <br />
|-<br />
|R_700 real||157 R relative humidity <br />
|}<br />
<br />
== ANALYSIS and UVA_ANALYSIS ==<br />
<br />
The ANALYSIS and UVA_ANALYSIS table contains values from the Analysis GRIB files at 18, 00, 06 and 12 UTC<br />
<br />
Data till 2009-09 is owned by the UvA and can be accessed by anybody with ECMWF_READ rights by using the ANALYSIS_UVA table. The ANALYSIS table itself also references data after 2009-09 that is owned by RNLAF for which special access rights ECMWF_RNLAF_READ are required. <br />
<br />
<br />
{|border=1<br />
|'''MODELTS'''||Time for which this forecast applies = model run<br />
|-<br />
|'''LATITUDE'''||degrees * 100 to make this a integer<br />
|-<br />
|'''LONGITUDE'''||degrees * 100 to make this a integer<br />
|-<br />
|SP||134 SP surface pressure <br />
|-<br />
|TCC||164 TCC total cloud coverage <br />
|-<br />
|U10||165 10U 10 meters wind U-component <br />
|-<br />
|V10||166 10V 10 meters wind V-component <br />
|-<br />
|T2||167 2T 2 metres air temperature <br />
|-<br />
|D2||168 2D 2 metres dew point temperature <br />
|-<br />
|LCC||186 LCC low cloud coverage <br />
|-<br />
|''Pressure level 1000''||<br />
|-<br />
|T_1000||130 T temperature <br />
|-<br />
|U_1000||131 U U-wind component <br />
|-<br />
|V_1000||132 V V-wind component <br />
|-<br />
|GH_1000||156 GH geopotential height <br />
|-<br />
|R_1000||157 R relative humidity <br />
|-<br />
|Pressure level 925||<br />
|-<br />
|T_925||130 T temperature <br />
|-<br />
|U_925||131 U U-wind component <br />
|-<br />
|V_925||132 V V-wind component <br />
|-<br />
|GH_925||156 GH geopotential height <br />
|-<br />
|R_925||157 R relative humidity <br />
|-<br />
|Pressure level 850||<br />
|-<br />
|T_850||130 T temperature <br />
|-<br />
|U_850||131 U U-wind component <br />
|-<br />
|V_850||132 V V-wind component <br />
|-<br />
|GH_850||156 GH geopotential height <br />
|-<br />
|R_850||157 R relative humidity <br />
|-<br />
|Pressure level 700||<br />
|-<br />
|T_700||130 T temperature <br />
|-<br />
|U_700||131 U U-wind component <br />
|-<br />
|V_700||132 V V-wind component <br />
|-<br />
|GH_700||156 GH geopotential height <br />
|-<br />
|R_700||157 R relative humidity<br />
|}<br />
<br />
== COMBINED == <br />
<br />
If you want to use Analysis data if available for a timestimp but otherwise Forecast, the COMBINED VIEW can be used. If a ANALYSIS value is available for a timestamp and latitude/longitude the ANALYSIS value will be used, otherwise the FORECAST value is given.<br />
<br />
== Historical data == <br />
<br />
In addition ongoing process of adding ECMWF data since November 11 2007, a historical data set has been loaded. That historical dataset is stored in additional inherited tables FORECASTHISTORY and<br />
ANALYSISHISTORY which inherit from FORECAST and ANALYSIS respectively. <br />
<br />
The FORECASTHISTORY does not always contain TP (228 TP total precipitation accumulated). Instead of this it contains the following values :<br />
<br />
{|border=1<br />
|LSP||142 LSP Large scale precipitation<br />
|-<br />
|CP||143 CP Convective precipitation<br />
|}<br />
<br />
The historical dat sets span the following periods and locations <br />
<br />
{|border=1 <br />
|'''Start'''||'''End'''||'''Area'''||'''Grid'''<br />
|-<br />
|2007-01-01||2007-11-15||62degN 10degW 335degN 20degE||0.25x0.25deg<br />
|-<br />
|2003-02-15||2003-06-15||62degN 10degW 335degN 20degE||0.5x0.5deg<br />
|-<br />
|2005-01-01||2006-12-31||62degN 10degW 335degN 20degE||0.5x0.5deg<br />
|}<br />
<br />
== Helpful Functions == <br />
<br />
<br />
The following functions have been defined in Postgres to select the nearest gridpoint in spacetime for the ECMWF analysis and forecast tables. <br />
<br />
<br />
These are '''ecmwf.forecast_nearest''' and '''ecmwf.analysis_nearest''' and they take a latitude, longitude and timestamp as parameter. <br />
<br />
<br />
They can be used in the following way:<br />
<br />
select * from ecmwf.forecast_nearest( 52.35983, 5.615, timestamp '2008-05-19 13:34:00');<br />
<br />
select * from ecmwf.analysis_nearest( 52.35983, 5.615, timestamp '2008-05-19 13:34:00');<br />
<br />
These function can for example be used in a join as follows :<br />
<br />
SELECT g.ptt_id<br />
, g.date_time<br />
, g.latitude<br />
, g.longitude<br />
, g.speed<br />
, g.course<br />
, g.altitude<br />
, (ecmwf.forecast_nearest( g.latitude, g.longitude,g.date_time)).*<br />
FROM gps.gps_tracking_data g<br />
, gps.individual i<br />
, gps.track_session t<br />
WHERE g.ptt_id = t.ptt_id <br />
AND g.date_time >= t.start_date <br />
AND i.ring_number = t.ring_number <br />
AND g.parser_qc = 1 <br />
AND g.ptt_id = 41745 <br />
AND g.latitude <> 0<br />
ORDER BY g.date_time;<br />
<br />
<br />
Although these functions were converted to PLPgSQL to speed them up, a faster ways to retrieve the same data is with (thanks to Floris Sluiters): <br />
<br />
SELECT ptt_id, date_time, latitude, longitude, speed, course, altitude, (x::ecmwf.forecast).*<br />
FROM (SELECT <br />
g.*<br />
,((SELECT f <br />
FROM ecmwf.forecast f<br />
WHERE f.latitude = round(g.latitude * 100 / 25)::integer * 25<br />
AND f.longitude = round(g.longitude * 100 / 25)::integer * 25<br />
AND f.modelts = TIMESTAMP 'epoch' + round(EXTRACT(EPOCH FROM g.date_time) <br />
/ (60*60*3))::integer * INTERVAL '3 hours' limit 1)::ecmwf.forecast) as x <br />
FROM gps.gps_tracking_data g<br />
, gps.individual i<br />
, gps.track_session t<br />
WHERE g.ptt_id = t.ptt_id <br />
AND g.date_time >= t.start_date <br />
AND i.ring_number = t.ring_number <br />
AND g.parser_qc = 1 <br />
AND g.ptt_id = 41745<br />
AND g.latitude <> 0<br />
ORDER BY g.date_time) t<br />
<br />
=== Interpolation ===<br />
<br />
The following functions are added so thast simple linear interpolation for a specific point in space and time can be done in Postgres. <br />
<br />
These are '''ecmwf.forecast_interpolate''' and '''ecmwf.analysis_interpolate''' and they take a latitude, longitude and timestamp as parameter. <br />
<br />
They can be used in the same way:<br />
<br />
select * from ecmwf.forecast_interpolate( 52.35983, 5.615, timestamp '2008-05-19 13:34:00');<br />
<br />
select * from ecmwf.analysis_interpolate( 52.35983, 5.615, timestamp '2008-05-19 13:34:00');<br />
<br />
And they can also be used in joins as above. These functions select the 8 surrounding points in latitude, longitude and date_time and interpolate linear in latitude, longitude and date_time successively. The '''interpolate''' functions are much slower then the '''nearest''' functions.</div>Barthttps://wiki.e-ecology.nl/index.php?title=ECMWF&diff=315ECMWF2010-01-25T16:42:25Z<p>Bart: /* FORECAST */</p>
<hr />
<div>== ECMWF == <br />
<br />
Datamodel for the tables in the ECMWF schema. <br />
<br />
Data is created by the ECMWF and retrieved from the KNMI ftp site as GRIB files. The original GRIB files can also be retrieved from the flysafe server from :<br />
<br />
[https://flysafe-pps.grid.sara.nl/archive/knmi/ecmwf/ ECMWF Data Archive]<br />
<br />
More information about the parameters in these GRIB files can be retrieved from the [http://www.ecmwf.int/services/dissemination/3.1/Products_in_GRIB_code.html ECMWF website].<br />
<br />
== INVARIABLE == <br />
<br />
The INVARIABLE table contains data that is invariant over time. <br />
<br />
{|border=1<br />
|'''LATITUDE''' || degrees * 100 to make this a integer<br />
|-<br />
|'''LONGITUDE''' || degrees * 100 to make this a integer<br />
|-<br />
|Z || 129 Z Geopotential surface/model orography <br />
|-<br />
|LSM || 172 LSM Land sea mask <br />
|-<br />
|LOCATION || Latitude/longitude as GIS location <br />
|}<br />
<br />
<br />
The GIS LOCATION is only added to this table. This is because always the same values for latitude and longitude are used and then if the GIS location is required for the ANALYSIS or FORECAST tables it can be retrieved by joining to this table on the LATITUDE, LONGUTUDE fields.<br />
<br />
== FORECAST and UVA_FORECAST == <br />
<br />
The FORECAST table contains predicted values in steps of 3 hours till 72 hours ahead. The MODELTS is the timestamp for which this prediction applies. Two times a day new Forecast GRIB files will arrive. The newer FORECAST data that arrives for the same timestamp will overwrite the older data.<br />
<br />
The FORECAST (and UVA_FORECAST) table itself is a master table that does not contain any data. The inherited tables <br />
FORECAST<YEAR><MONTH> contain the data, but the master FORECAST or UVA_FORECAST table can be used to SELECT the data. <br />
<br />
Data till 2009-09 is owned by the UvA and can be accessed by anybody with ECMWF_READ rights by using the FORECAST_UVA table. The FORECAST table itself also references data after 2009-09 that is owned by RNLAF for which special access rights ECMWF_RNLAF_READ are required. <br />
<br />
{|border=1<br />
|'''MODELTS'''||Time for which this forecast applies = model run + step hours<br />
|-<br />
|'''LATITUDE'''||degrees * 100 to make this a integer<br />
|-<br />
|'''LONGITUDE'''||degrees * 100 to make this a integer<br />
|-<br />
|STEP||model step (smaller is more recent forecast)<br />
|-<br />
|SSRD||169 SSRD surface solar radiation downwards accumulated <br />
|-<br />
|TP||228 TP total precipitation accumulated <br />
|-<br />
|SP||134 SP surface pressure <br />
|-<br />
|BLH||159 BLH boundary layer height <br />
|-<br />
|TCC||164 TCC total cloud coverage <br />
|-<br />
|U10||165 10U 10 meters wind U-component <br />
|-<br />
|V10||166 10V 10 meters wind V-component <br />
|-<br />
|T2||167 2T 2 metres air temperature <br />
|-<br />
|D2||168 2D 2 metres dew point temperature <br />
|-<br />
|LCC||186 LCC low cloud coverage <br />
|-<br />
|''Pressure level 1000''||<br />
|-<br />
|T_1000||130 T temperature <br />
|-<br />
|U_1000||131 U U-wind component <br />
|-<br />
|V_1000||132 V V-wind component <br />
|-<br />
|GH_1000||156 GH geopotential height <br />
|-<br />
|R_1000||157 R relative humidity <br />
|-<br />
|''Pressure level 925''||<br />
|-<br />
|T_925 real||130 T temperature <br />
|-<br />
|U_925 real||131 U U-wind component <br />
|-<br />
|V_925 real||132 V V-wind component <br />
|-<br />
|GH_925 real||156 GH geopotential height <br />
|-<br />
|R_925 real||157 R relative humidity <br />
|-<br />
|''Pressure level 850''||<br />
|-<br />
|T_850||130 T temperature <br />
|-<br />
|U_850 real||131 U U-wind component <br />
|-<br />
|V_850 real||132 V V-wind component <br />
|-<br />
|GH_850 real||156 GH geopotential height <br />
|-<br />
|R_850 real||157 R relative humidity <br />
|-<br />
|''Pressure level 700''||<br />
|-<br />
|T_700 real||130 T temperature <br />
|-<br />
|U_700 real||131 U U-wind component <br />
|-<br />
|V_700 real||132 V V-wind component <br />
|-<br />
|GH_700 real||156 GH geopotential height <br />
|-<br />
|R_700 real||157 R relative humidity <br />
|}<br />
<br />
== ANALYSIS ==<br />
<br />
The ANALYSIS table contains values from the Analysis GRIB files at 18, 00, 06 and 12 UTC<br />
<br />
{|border=1<br />
|'''MODELTS'''||Time for which this forecast applies = model run<br />
|-<br />
|'''LATITUDE'''||degrees * 100 to make this a integer<br />
|-<br />
|'''LONGITUDE'''||degrees * 100 to make this a integer<br />
|-<br />
|SP||134 SP surface pressure <br />
|-<br />
|TCC||164 TCC total cloud coverage <br />
|-<br />
|U10||165 10U 10 meters wind U-component <br />
|-<br />
|V10||166 10V 10 meters wind V-component <br />
|-<br />
|T2||167 2T 2 metres air temperature <br />
|-<br />
|D2||168 2D 2 metres dew point temperature <br />
|-<br />
|LCC||186 LCC low cloud coverage <br />
|-<br />
|''Pressure level 1000''||<br />
|-<br />
|T_1000||130 T temperature <br />
|-<br />
|U_1000||131 U U-wind component <br />
|-<br />
|V_1000||132 V V-wind component <br />
|-<br />
|GH_1000||156 GH geopotential height <br />
|-<br />
|R_1000||157 R relative humidity <br />
|-<br />
|Pressure level 925||<br />
|-<br />
|T_925||130 T temperature <br />
|-<br />
|U_925||131 U U-wind component <br />
|-<br />
|V_925||132 V V-wind component <br />
|-<br />
|GH_925||156 GH geopotential height <br />
|-<br />
|R_925||157 R relative humidity <br />
|-<br />
|Pressure level 850||<br />
|-<br />
|T_850||130 T temperature <br />
|-<br />
|U_850||131 U U-wind component <br />
|-<br />
|V_850||132 V V-wind component <br />
|-<br />
|GH_850||156 GH geopotential height <br />
|-<br />
|R_850||157 R relative humidity <br />
|-<br />
|Pressure level 700||<br />
|-<br />
|T_700||130 T temperature <br />
|-<br />
|U_700||131 U U-wind component <br />
|-<br />
|V_700||132 V V-wind component <br />
|-<br />
|GH_700||156 GH geopotential height <br />
|-<br />
|R_700||157 R relative humidity<br />
|}<br />
<br />
== COMBINED == <br />
<br />
If you want to use Analysis data if available for a timestimp but otherwise Forecast, the COMBINED VIEW can be used. If a ANALYSIS value is available for a timestamp and latitude/longitude the ANALYSIS value will be used, otherwise the FORECAST value is given.<br />
<br />
== Historical data == <br />
<br />
In addition ongoing process of adding ECMWF data since November 11 2007, a historical data set has been loaded. That historical dataset is stored in additional inherited tables FORECASTHISTORY and<br />
ANALYSISHISTORY which inherit from FORECAST and ANALYSIS respectively. <br />
<br />
The FORECASTHISTORY does not always contain TP (228 TP total precipitation accumulated). Instead of this it contains the following values :<br />
<br />
{|border=1<br />
|LSP||142 LSP Large scale precipitation<br />
|-<br />
|CP||143 CP Convective precipitation<br />
|}<br />
<br />
The historical dat sets span the following periods and locations <br />
<br />
{|border=1 <br />
|'''Start'''||'''End'''||'''Area'''||'''Grid'''<br />
|-<br />
|2007-01-01||2007-11-15||62degN 10degW 335degN 20degE||0.25x0.25deg<br />
|-<br />
|2003-02-15||2003-06-15||62degN 10degW 335degN 20degE||0.5x0.5deg<br />
|-<br />
|2005-01-01||2006-12-31||62degN 10degW 335degN 20degE||0.5x0.5deg<br />
|}<br />
<br />
== Helpful Functions == <br />
<br />
<br />
The following functions have been defined in Postgres to select the nearest gridpoint in spacetime for the ECMWF analysis and forecast tables. <br />
<br />
<br />
These are '''ecmwf.forecast_nearest''' and '''ecmwf.analysis_nearest''' and they take a latitude, longitude and timestamp as parameter. <br />
<br />
<br />
They can be used in the following way:<br />
<br />
select * from ecmwf.forecast_nearest( 52.35983, 5.615, timestamp '2008-05-19 13:34:00');<br />
<br />
select * from ecmwf.analysis_nearest( 52.35983, 5.615, timestamp '2008-05-19 13:34:00');<br />
<br />
These function can for example be used in a join as follows :<br />
<br />
SELECT g.ptt_id<br />
, g.date_time<br />
, g.latitude<br />
, g.longitude<br />
, g.speed<br />
, g.course<br />
, g.altitude<br />
, (ecmwf.forecast_nearest( g.latitude, g.longitude,g.date_time)).*<br />
FROM gps.gps_tracking_data g<br />
, gps.individual i<br />
, gps.track_session t<br />
WHERE g.ptt_id = t.ptt_id <br />
AND g.date_time >= t.start_date <br />
AND i.ring_number = t.ring_number <br />
AND g.parser_qc = 1 <br />
AND g.ptt_id = 41745 <br />
AND g.latitude <> 0<br />
ORDER BY g.date_time;<br />
<br />
<br />
Although these functions were converted to PLPgSQL to speed them up, a faster ways to retrieve the same data is with (thanks to Floris Sluiters): <br />
<br />
SELECT ptt_id, date_time, latitude, longitude, speed, course, altitude, (x::ecmwf.forecast).*<br />
FROM (SELECT <br />
g.*<br />
,((SELECT f <br />
FROM ecmwf.forecast f<br />
WHERE f.latitude = round(g.latitude * 100 / 25)::integer * 25<br />
AND f.longitude = round(g.longitude * 100 / 25)::integer * 25<br />
AND f.modelts = TIMESTAMP 'epoch' + round(EXTRACT(EPOCH FROM g.date_time) <br />
/ (60*60*3))::integer * INTERVAL '3 hours' limit 1)::ecmwf.forecast) as x <br />
FROM gps.gps_tracking_data g<br />
, gps.individual i<br />
, gps.track_session t<br />
WHERE g.ptt_id = t.ptt_id <br />
AND g.date_time >= t.start_date <br />
AND i.ring_number = t.ring_number <br />
AND g.parser_qc = 1 <br />
AND g.ptt_id = 41745<br />
AND g.latitude <> 0<br />
ORDER BY g.date_time) t<br />
<br />
=== Interpolation ===<br />
<br />
The following functions are added so thast simple linear interpolation for a specific point in space and time can be done in Postgres. <br />
<br />
These are '''ecmwf.forecast_interpolate''' and '''ecmwf.analysis_interpolate''' and they take a latitude, longitude and timestamp as parameter. <br />
<br />
They can be used in the same way:<br />
<br />
select * from ecmwf.forecast_interpolate( 52.35983, 5.615, timestamp '2008-05-19 13:34:00');<br />
<br />
select * from ecmwf.analysis_interpolate( 52.35983, 5.615, timestamp '2008-05-19 13:34:00');<br />
<br />
And they can also be used in joins as above. These functions select the 8 surrounding points in latitude, longitude and date_time and interpolate linear in latitude, longitude and date_time successively. The '''interpolate''' functions are much slower then the '''nearest''' functions.</div>Barthttps://wiki.e-ecology.nl/index.php?title=UvAGPS&diff=314UvAGPS2010-01-22T10:19:49Z<p>Bart: /* get_uvagps_track_distance */</p>
<hr />
<div>= UvAGPS Data Model =<br />
<br />
For different versions of the UvAGPS firmware different tables are used. For firmware version v0.9.3.6 till v1.0.0.X the tables UVA_ENGINEERING_DATA and UVA_TRACKING_DATA are used. But in the new firmware versions 1.0.1.4 till 1.0.2.4 so much information was added that new tables were introduced. However for the most important tracking tables a view is created so that all similar tracking for all types of firmware can be seen in one view. That is the UVA_TRACKING view. <br />
<br />
All tables, views and functions are also in the GPS schema.<br />
<br />
== UVA_TRACKING_DATA ==<br />
<br />
Tracking data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|h_accuracy||float8||||||Horizontal accuracy (m)<br />
|-<br />
|v_accuracy||float8||||||Vertical accuracy (m)<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|x_acceleration||Float8||||||x axis acceleration (m/s<sup>2</sup>2) movement to right is + and to left is -<br />
|-<br />
|y_acceleration||Float8||||||y axis acceleration (m/s<sup>2</sup>2) forward movement is + and backwards is -<br />
|-<br />
|z_acceleration||Float8||||||z axis acceleration (m/s<sup>2</sup>2) upwards movement is + downwards is -<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||Degrees<br />
|-<br />
|pressure||float8||||||Pressure sensor (pascal)<br />
|-<br />
|temperature||Float8||||||Degrees celcius<br />
|-<br />
|solar_voltage||Float8||||||V<br />
|-<br />
|battery_voltage||Float8||||||V<br />
|-<br />
|quality||text||||||Data flagged as unacceptable by user<br />
|-<br />
| “"location”"||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== UVA_ENGINEERING_DATA ==<br />
<br />
Engineering data from UvA GPS tags for older firmware<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|t_syncsts||smallint||||||0: not synced, 1: user synced, 2: Gps synced<br />
|-<br />
|t_entzt||smallint||||||0: UCT time,1: TZT time (timezone time)<br />
|-<br />
|gzp_currentrategps||int4||||||<br />
|-<br />
|gzp_currentratecom||int4||||||<br />
|-<br />
|gzp_currentratepwr||int4||||||<br />
|-<br />
|sbm_voltagesolarpanel||float8||||||<br />
|-<br />
|sbm_voltagebattery||float8||||||<br />
|-<br />
|sbm_chargemode||int2||||||<br />
|-<br />
|egzp_mainrategps||integer||||||<br />
|-<br />
|egzp_mainratecom||integer||||||<br />
|-<br />
|egzp_mainratepwr||integer||||||<br />
|-<br />
|smg_on||text||||||<br />
|-<br />
|smg_off||text||||||<br />
|-<br />
|smg_esavegpsrate||integer||||||<br />
|-<br />
|smz_on||text||||||<br />
|-<br />
|smz_off||text||||||<br />
|-<br />
|smz_esavecomrate||integer||||||<br />
|-<br />
|gpsnavigationmode||smallint||||||<br />
|-<br />
|gpsfixtimeout||smallint||||||<br />
|-<br />
|eh||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== UVA_DEVICE == <br />
<br />
To be able to track the different firmware versions for the different devices the UVA_DEVICE table was added.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|- <br />
| firmware_version || text |||| NOT NULL ||<br />
|}<br />
<br />
== UVA_COMM101 == <br />
<br />
Communication table indicates status and result of communications with ground stations. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
| device_info_serial || integer || PK || NOT NULL ||<br />
|-<br />
| date_time || timestamp || PK || NOT NULL || timestamp of start communication<br />
|-<br />
| date_time_end || timestamp |||||| timestamp of end communication <br />
|-<br />
| date_time_utc || timestamp |||||| date_time in utc (if available)<br />
|-<br />
| date_time_end_utc || timestamp |||||| date_time_end in utc (if available)<br />
|-<br />
| action || text|||||| JOINED / RESCHEDULE ??<br />
|-<br />
| bytes_communicated || integer |||||| Number of bytes communicated (total of all bytes per DATA line) <br />
|-<br />
|status || text |||||| READY, TIMEOUT, LOWPOWER, MISSING<br />
|-<br />
| network_join_time || integer||||||milliseconds<br />
|-<br />
| number_identical_lines || integer |||||| Number identical lines in data block. Gives indication <br />
|-<br />
| non_ascii_char || integer |||||| Number of non ascii characters (indicated by question-mark ?)<br />
|-<br />
| sts_time || timestamp |||||| derived from S0 hh,mi<br />
|-<br />
| timesynced || smallint|||||| TimeSynced (0=not sy:wnced, 1=user set, 2=Gps Synced)<br />
|-<br />
|devicemode || smallint||||||DeviceMode (0-99)<br />
|-<br />
| vbat || float |||||| Battery voltage in V (0-~4.200V) <br />
|-<br />
|logb || integer |||||| logged bytes, waiting for download (0-4Mbyte)<br />
|-<br />
| logp || smallint |||||| Logged percentage (units 0.1%) of memory waiting to be downloaded (0-1000)<br />
|-<br />
| gpsii || integer |||||| GpsIval, current (0-65535)<br />
|-<br />
|comii || integer|||||| ComIval, current (0-65535)<br />
|-<br />
|accii || integer|||||| AcceleroIval, current (0-65535)<br />
|-<br />
|swddd || integer|||||| User switches, current (0-65535) <br />
|-<br />
|last_gps_fix ||timestamp||||||timestamp of last fix<br />
|-<br />
|latitude||float||||||Latitude of last fix. Decimal degrees <br />
|-<br />
|longitude||float||||||Longitude of last fix. Decimal degrees<br />
|}<br />
<br />
<br />
== UVA_SETTINGS101 == <br />
<br />
Settings are either from C0-C1-C9 lines or parsed from uplink communication lines <br />
If C0-C1 is parsed its values are compared with the previous value and if the settings are the <br />
same no new records needs to be added <br />
If uplink settings are parsed wait till the last setting has been seen, (DL command or EOF) <br />
then store all the new settings in one record. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||Derive timestamp from Hh:mi fields in C0 combined with computer timestamp in JOINED line<br />
|-<br />
|timesynced || smallint ||||||<br />
|-<br />
|timezone_time || smallint ||||||<br />
|-<br />
|swddd || integer|||||| SpecialUserSwitches <br />
|-<br />
|gpsnavmode || smallint|||||| GpsNavMode 0-7<br />
|-<br />
|gpsreceivermode || smallint |||||| GpsReceiverNode 0-3<br />
|-<br />
|gpsfixtime || smallint|||||| GpsFixTime 0-255<br />
|-<br />
|gps_ivaln_on_h || smallint|||||| hours Gps IvalN on<br />
|-<br />
|gps_ivaln_on_m || smallint|||||| minutes Gps IvalN on <br />
|-<br />
|gps_ivaln || integer|||||| GpsIvalN (0-65530)<br />
|-<br />
|gps_ivale_on_h || smallint|||||| hours Gps IvalE on<br />
|-<br />
|gps_ivale_on_m || smallint|||||| minutes GpS IvalE on<br />
|-<br />
|gps_ivale || integer|||||| GpsIvalE <br />
|-<br />
|com_ivaln_on_h || smallint|||||| hours Com IvalN on<br />
|-<br />
|com_ivaln_on_m || smallint|||||| minutes Com IvalN on<br />
|-<br />
|com_ivaln || integer|||||| ComIvalN (0-65530)<br />
|-<br />
|com_ivale_on_h || smallint|||||| hours Com IvalE on<br />
|-<br />
|com_ivale_on_m || smallint|||||| minutes Com IvalE on<br />
|-<br />
|com_ivale || integer|||||| ComIvalE<br />
|-<br />
|accii || integer|||||| Accelero measurement interval <br />
|-<br />
|accbn || integer|||||| Accelero number of blocks <br />
|-<br />
|accsn || integer|||||| Accelero number of samples (0-65536)<br />
|-<br />
|f || smallint||||||Accelero sample frequency (0=20Hz, 1=10Hz, 2=5Hz, 3=1Hz)<br />
|-<br />
|pdp || smallint|||||| PdopMsk (3-250)<br />
|-<br />
|pac||smallint|||||| PaccMsk (10-100)<br />
|-<br />
|tdp ||smallint|||||| TdopMsk (3-250)<br />
|-<br />
|tac ||smallint|||||| TaccMsk (30-300)<br />
|-<br />
|ga || smallint|||||| Additional Fixes GpsIval mode (3-25) before interval fix is logged<br />
|-<br />
|aol || smallint||||||AccMemOffLev (100 - 950) units 0.1%; if Memfull above this level all Accelero activity will be overruled and switched off untill MemFull < level - 5<br />
|-<br />
|eventnum || text|||||| 12 eventnumbers (0-0xff) only printed if not zero, therfore converted to text<br />
|}<br />
<br />
<br />
== UVA_TRACKING_DATA101 ==<br />
<br />
The tracking dat for newer firmware.<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude ||float||||||Decimal degrees<br />
|-<br />
|longitude ||float||||||Decimal degrees<br />
|-<br />
|altitude ||integer||||||heigth above sealevel meters<br />
|-<br />
|pressure ||integer||||||in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature ||float||||||in celcius degrees<br />
|-<br />
|satellites_used ||smallint||||||satellites used for fix <br />
|-<br />
|gps_fixtime ||float||||||GpsFixTime in seconds <br />
|-<br />
|positiondop ||float||||||Position DOP in units<br />
|-<br />
|h_accuracy || float||||||Horizontal accuracy (units of meter)<br />
|-<br />
|v_accuracy || float||||||Vertical accuracy (units of meter)<br />
|-<br />
|x_speed ||float||||||Speed in x-axis (m/s)<br />
|-<br />
|y_speed ||float||||||Speed in y-axis (m/s)<br />
|-<br />
|z_speed ||float||||||Speed in z-axis (m/s)<br />
|-<br />
|speed_accuracy || float||||||Speed accuracy (m/s) <br />
|-<br />
|location || geometry |||||| lat/long as PostGIS geometry<br />
|}<br />
<br />
<br />
== UVA_ACCELERATION101 == <br />
<br />
Acceleration entries if accelerometer was turned on. Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|index ||smallint||PK||NOT NULL||<br />
|-<br />
|x_acceleration ||smallint||||||acceleration in X-axis (-2666 till 2666)<br />
|-<br />
|y_acceleration ||smallint||||||acceleration in Y-axis (-2666 till 2666)<br />
|-<br />
|z_acceleration ||smallint||||||acceleration in Z-axis (-2666 till 2666)<br />
|}<br />
<br />
== UVA_ENERGY101 ==<br />
<br />
Only for newer firmware.<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|timesynced ||smallint||||||TimeSynced (0=not synced, 1=user set, 2=Gps synced)<br />
|-<br />
|devicemode ||smallint||||||(0-99)<br />
|-<br />
|vsll ||float||||||Solar Voltage during charging in mV (0-~2500)<br />
|-<br />
|vbat ||float||||||Battery Voltage in V (0-~4.200)<br />
|-<br />
|ssw ||smallint|||||| Solar Cell Switches ... (0-255) fw1022 and up <br />
|-<br />
| ||||||||extended fields if special user switch is on <br />
|-<br />
|vsoo ||float|||||| Solar voltage open in V (0-~2.500)<br />
|-<br />
|vdrf ||float||||||reference voltage Dac in V (0-~2.435)<br />
|-<br />
|vchr ||float||||||charge current voltage<br />
|-<br />
|g ||smallint|||||| Gps battery threshold OK<br />
|-<br />
|c || smallint||||||Com battery threshold OK<br />
|-<br />
|m || smallint||||||Charge Mode (0,1,2 Com battery threshold OK<br />
|-<br />
|pressure || integer|||||| in pascal (1mBar = 100Pa, 1pressuremeter = ~12Pa)<br />
|-<br />
|temperature || float|||||| in celcius degrees <br />
|}<br />
<br />
<br />
== UVA_TRACKING == <br />
<br />
View to show identical fields for older and newer firmware tracking data<br />
<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|device_info_serial||int4||PK||NOT NULL ||<br />
|-<br />
|date_time||timestamp||PK||NOT NULL||<br />
|-<br />
|latitude||float||||||<br />
|-<br />
|longitude||float||||||<br />
|-<br />
|altitude||float||||||<br />
|-<br />
|pressure||integer|||||<br />
|-<br />
|temperature||float||||||<br />
|-<br />
|h_accuracy||float||||||<br />
|-<br />
|v_accuracy||float||||||<br />
|-<br />
|x_speed||float||||||meters/second<br />
|-<br />
|y_speed||float||||||meters/second<br />
|-<br />
|z_speed||float||||||meters/second<br />
|-<br />
|gps_fixtime||float||||||<br />
|-<br />
|location||geometry||||||<br />
|}<br />
<br />
== UVA_TRACKING_SPEED == <br />
<br />
Additional view that computes with the x_speed, y_speed and z_speed components the vnorth, veast and vdown speed components as well as the absolute value speed in meters/second. <br />
<br />
In addition to the fields in the UVA_TRACKING view this view adds :<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|vnorth||float||||||- vx * sin(lat) * cos(long) - vy * sin(lat) * sin (long) + vz * cos(lat)<br />
|-<br />
|veast||float|||||| - vx * sin(lon) + vy * cos(lon)<br />
|-<br />
|vdown||float|||||| - vx * cos(lat) * cos(lon) - vy * cos(lat) * sin(lon) - vz * sin(lat)<br />
|-<br />
|speed||float|||||| sqrt(vx^2 + vy^2 + vz^2)<br />
|}<br />
<br />
= UvAGPS functions =<br />
<br />
== get_uvagps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meters/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial.<br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows.<br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_uvagps_track_speed(119);<br />
<br />
select t.*, a.distance, a.interval, a.speed, a.direction from gps.get_uvagps_track_speed(119, '2008-01-01 00:00:00', '2010-01-01 00:00:00') a join gps.uva_tracking t using(device_info_serial, date_time);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. PostGIS does not calculate the heading, so therefore we don't use PostGIS.<br />
<br />
== get_uvagps_track_distance ==<br />
<br />
Compute distance (meters) for UvAGPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
select * from gps.get_uvagps_track_distance(119, 52.1897017, 6.1996606); <br />
<br />
select * from gps.get_uvagps_track_distance(119, (select location from gps.uva_tracking where device_info_serial = 119 and date_time = '2009-05-07 19:55:08')); <br />
<br />
</pre><br />
<br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Argos_Data_Model&diff=313Argos Data Model2010-01-22T10:19:23Z<p>Bart: /* get_argosgps_track_distance */</p>
<hr />
<div>== GPS Data Model == <br />
<br />
Last updated January 5, 2010 Bart Heupers - [[ UvAGPS ]] moved to special page<br />
<br />
Updated January 22, 2008 Judy Shamoun-Baranes <br />
<br />
'''FLYSAFE TRACKING DATABASE'''<br />
<br />
The tracking database will include data from several species. Some species are trapped and then monitored during the breeding season while others are trapped during the winter season. Information is collected on each tracked bird, including biometric measurements. These measurements may be collected more than once. During the breeding season information is also collected about the gull breeding colony itself, location of nests, state of breeding (number of eggs and juveniles) and then juveniles themselves are marked and measured (although not tracked).<br />
<br />
In addition, PTTs are often tested before they are actually placed on the birds. This information is also important during analysis and particularly to establish accuracy of data. This data should also be stored in the database. Therefore it is important that this information is stored properly in the database<br />
<br />
Units and descriptions should be filled in for all measurements<br />
<br />
One way of looking at this structure is considering 3 categories of tables: <br />
<br />
# '''lookup tables''' (information stored once) <br />
# '''session tables''' (stored occasionally) <br />
# '''observations''' – highest frequency of information.<br />
<br />
Primary keys are noted by bold italic text. Foreign keys are noted by italic text in the Field column.<br />
<br />
Microwave, will under no circumstances provide information about their checksum calculations. If feasible, SARA will duplicate the procedure and include a flag in the representing the microwave filtered data.<br />
<br />
'''TECHNICAL INFORMATION FROM TAGS'''<br />
<br />
<br />
== DEVICE_INFO ==<br />
<br />
Table including technical information about tag hardware. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL||serial number of PTT provided by Argos and used for communication with Argos satellite<br />
|-<br />
|serial ||int4||||NOT NULL||serial number of tag from manufacturer<br />
|-<br />
|weight ||int4||||NOT NULL||Unit = grams<br />
|-<br />
|type ||text||||NOT NULL||<br />
|-<br />
|manufacturer ||text||||||Device manufacturer<br />
|-<br />
|hexadecimal_id||text||||||Hexadecimal address, unique for each tag<br />
|-<br />
|PAN_id||Text||||||Personal area network ground based tags communicates with<br />
|-<br />
|Base_station_id||Int4||||||base station ground based tag communicates with<br />
|-<br />
|Remarks||text||||||<br />
|}<br />
<br />
== TRACK_SESSION == <br />
<br />
This table includes information about each measurement session and enables inclusion of data from new species and also from the test phase of different tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4 ||PK||NOT NULL||unique ID for each usage of a PTT so test and bird with same ptt_id are two separate IDs/indexes<br />
|-<br />
|''pttid''||int4 ||FK||NOT NULL||Link to DEVICE_INFO table<br />
|-<br />
|''ring_number''||text ||FK||||link to individual table – tests do not have a ring_number<br />
|-<br />
|start_date ||timestamptz||||||Date/time (Local) when tracking begins<br />
|-<br />
|start_latitude ||float8||||NOT NULL||latitude where tracking begins, unit = dec degress<br />
|-<br />
|start_longitude ||float8||||NOT NULL||longitude where tracking begins, unit = dec degrees<br />
|-<br />
|start_altitude||Float8||||||Unit = m, include when known, important for testing<br />
|-<br />
|end_date||timestamptz||||||End of session if known<br />
|-<br />
|time_window ||text||||||<br />
|-<br />
|time_steps ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|location ||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
== GPS_TRACKING_DATA ==<br />
<br />
Tracking data from GPS sensors on PTT/GPS tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||degrees<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|alt_status||text||||||<br />
|-<br />
|quality||text||||||Quality information from sensor<br />
|-<br />
|user_QC||text||||||Data flagged as unacceptable by user<br />
|-<br />
|parser_QC||text||||||Data flagged as unacceptable by Microwave parser<br />
|-<br />
|location||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
<br />
Note : <br />
<br />
The parser_QC value can be 1, 2,3,4, 99, or 100. If it 1 the data is OK. If it is 2 or 3 or 4 some form of error correction has been <br />
performed by the Microwave parser. And if it is 100 no error correction was possible. For reliable results it is advised only to use <br />
records with parser_QC values of 1<br />
<br />
== ARGOS_TRACKING_DATA ==<br />
<br />
Tracking data from Argos sensors<br />
<br />
{|border=1<br />
|'''Field'''||'''Type '''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4 ||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|fix ||text||||||<br />
|-<br />
|latitude1 ||float8||||||<br />
|-<br />
|longitude1 ||float8||||||<br />
|-<br />
|latitude2 ||float8||||||<br />
|-<br />
|longitude2 ||float8||||||<br />
|-<br />
|msgcount ||int4||||||<br />
|-<br />
|frequency ||float8||||||<br />
|-<br />
|average_ti ||float8||||||<br />
|-<br />
|satellite ||text||||||<br />
|-<br />
|max_str ||text||||||<br />
|-<br />
|location1 ||geometry||||||postgreSQL geometry<br />
|-<br />
|location2 ||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== PTT_ENGINEERING_DATA ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''tx_date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|'''satellite_id'''||text ||PK||NOT NULL||<br />
|-<br />
|ptt_date_time ||timestamp||||||GMT<br />
|-<br />
|activity||int4||||||<br />
|-<br />
|tx_count||int4||||||<br />
|-<br />
|temperature||float8||||||<br />
|-<br />
|battery_voltage||float8||||||<br />
|-<br />
|gps_fix_time||int4||||||<br />
|-<br />
|satellite_count||int4||||||<br />
|-<br />
|hours_reset||int4||||||<br />
|-<br />
|hours_since_gps_fix||int4||||||<br />
|-<br />
|mortality_gt||int4||||||<br />
|-<br />
|seasonal_gt||int4||||||<br />
|-<br />
|shunt||int4||||||<br />
|-<br />
|}<br />
<br />
<br />
In addition the views GPS_TRACKING_SESSION, ARGOS_TRACKING_SESSION, PTT_ENGINEERING_SESSION are which adds the correct track_session.id to the GPS_TRACKING_DATA, ARGOS_TRACKING_DATA and PTT_ENGINEERING_DATA table data.<br />
<br />
<br />
'''BIOLOGICAL INFORMATION'''<br />
<br />
== INDIVIDUAL ==<br />
<br />
Table includes information used to identify an individual<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ring_number'''||text||PK||NOT NULL||metal ring number<br />
|-<br />
|Id||int4||PK||NOT NULL ||auto-insert, unique ID for each individual organism <br />
|-<br />
|''NEST_INFO_id''||int4||FK||||link to NEST_INFO, not all specimens are linked to a nest<br />
|-<br />
|nest_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|species_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|ring_number||text||||NOT NULL||metal ring number<br />
|-<br />
|color_code||text||||||code for color ring without punctuation<br />
|-<br />
|species||text||||NOT NULL||Scientific name (at least genus)<br />
|-<br />
|sex||text||||||update if or when known<br />
|-<br />
|''FATE_CODEE_id''||textInt4||FK||||Link to FATE_CODE<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== FATE_code == <br />
<br />
{|border=1<br />
|Field ||Type||Key||Constraints||Comments<br />
|-<br />
|'''Id'''||'''Int4'''||'''PK'''||||'''auto-insert'''<br />
|-<br />
|code ||int4||PK||NOT NULL||<br />
|-<br />
|description||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== MEASUREMENT ==<br />
<br />
Metadata Provided by Sovon is needed to describe how these measurements are taken.<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4||PK||NOT NULL||auto-insert, unique ID for each observation<br />
|-<br />
|''ring_number''||text||FK||||link to individual<br />
|-<br />
|catch_datetime ||timestamp||||||Local time<br />
|-<br />
|release_datetime||timestamp||||||Local time<br />
|-<br />
|mass ||float8||||||grams<br />
|-<br />
|age ||text||||||AD = adult, JUV = juvenile<br />
|-<br />
|wing_length ||float8||||||<br />
|-<br />
|bill_length1 ||float8||||||<br />
|-<br />
|bill_length2 ||float8||||||<br />
|-<br />
|bill_height1 ||float8||||||<br />
|-<br />
|bill_height2 ||float8||||||<br />
|-<br />
|tarsus_length ||float8||||||<br />
|-<br />
|total_head||float8||||||<br />
|-<br />
|observer ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|}<br />
<br />
===Catch_datetime & release_datetime===<br />
<br />
During ringing of juveniles only the date was recorded and not the time. Birds were all released the same day. Ringing and measuring small chicks in the nest took about 2-5 minutes. Colour ringing and sampling of the larger chicks (from 4 July onwards) took about half an hour (rounding up several chicks and banding, sampling and releasing them together). To avoid leaving fields blank, a standard catch time was noted at 12:00 and a release time of 12:15 before July 4 and 12:30 from July 4 and onwards. ''''comments by Kees Oosterbeek''''<br />
<br />
== NEST_INFO ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|''id''||int4||PK ||NOT NULL||<br />
|-<br />
|Species||text||||||<br />
|-<br />
|latitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|longitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|year||Int4||||||Year of breeding season<br />
|-<br />
| "location"||geometry||||||postgreSQL geometry<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== NEST_OBSERVATION ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||''''''Comments''''''<br />
|-<br />
|''id''||''int4''||PK||NOT NULL ||Auto-insert, unique ID for each observation<br />
|-<br />
|''NEST_INFO_id''||''int4''||FK||NOT NULL ||<br />
|-<br />
|date||timestamptz ||||NOT NULL||<br />
|-<br />
|number_egg||int4||||||<br />
|-<br />
|number_young||int4||||||<br />
|-<br />
|pipping||text||||||Activity in egg (peeping or signs of hatching)<br />
|-<br />
|attended||text||||||Activity on nest<br />
|-<br />
|observer||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|}<br />
<br />
=Comments:=<br />
<br />
<br />
<br />
<br />
== Graphical Data Model == <br />
<br />
[[Image:Gps_datamodel.png ]]<br />
<br />
<br />
= Argos GPS functions = <br />
<br />
== get_argosgps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meter/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial. <br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows. <br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_argosgps_track_speed(41745);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. Because PostGIS does not calculate the heading we don't use PostGIS here.<br />
<br />
== get_argosgps_track_distance ==<br />
<br />
Compute distance (meters) for Argos GPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances from nest<br />
<br />
select * from gps.get_argosgps_track_distance(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function which uses spherical correction.</div>Barthttps://wiki.e-ecology.nl/index.php?title=Argos_Data_Model&diff=312Argos Data Model2010-01-22T10:09:44Z<p>Bart: /* get_argosgps_track_speed */</p>
<hr />
<div>== GPS Data Model == <br />
<br />
Last updated January 5, 2010 Bart Heupers - [[ UvAGPS ]] moved to special page<br />
<br />
Updated January 22, 2008 Judy Shamoun-Baranes <br />
<br />
'''FLYSAFE TRACKING DATABASE'''<br />
<br />
The tracking database will include data from several species. Some species are trapped and then monitored during the breeding season while others are trapped during the winter season. Information is collected on each tracked bird, including biometric measurements. These measurements may be collected more than once. During the breeding season information is also collected about the gull breeding colony itself, location of nests, state of breeding (number of eggs and juveniles) and then juveniles themselves are marked and measured (although not tracked).<br />
<br />
In addition, PTTs are often tested before they are actually placed on the birds. This information is also important during analysis and particularly to establish accuracy of data. This data should also be stored in the database. Therefore it is important that this information is stored properly in the database<br />
<br />
Units and descriptions should be filled in for all measurements<br />
<br />
One way of looking at this structure is considering 3 categories of tables: <br />
<br />
# '''lookup tables''' (information stored once) <br />
# '''session tables''' (stored occasionally) <br />
# '''observations''' – highest frequency of information.<br />
<br />
Primary keys are noted by bold italic text. Foreign keys are noted by italic text in the Field column.<br />
<br />
Microwave, will under no circumstances provide information about their checksum calculations. If feasible, SARA will duplicate the procedure and include a flag in the representing the microwave filtered data.<br />
<br />
'''TECHNICAL INFORMATION FROM TAGS'''<br />
<br />
<br />
== DEVICE_INFO ==<br />
<br />
Table including technical information about tag hardware. <br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL||serial number of PTT provided by Argos and used for communication with Argos satellite<br />
|-<br />
|serial ||int4||||NOT NULL||serial number of tag from manufacturer<br />
|-<br />
|weight ||int4||||NOT NULL||Unit = grams<br />
|-<br />
|type ||text||||NOT NULL||<br />
|-<br />
|manufacturer ||text||||||Device manufacturer<br />
|-<br />
|hexadecimal_id||text||||||Hexadecimal address, unique for each tag<br />
|-<br />
|PAN_id||Text||||||Personal area network ground based tags communicates with<br />
|-<br />
|Base_station_id||Int4||||||base station ground based tag communicates with<br />
|-<br />
|Remarks||text||||||<br />
|}<br />
<br />
== TRACK_SESSION == <br />
<br />
This table includes information about each measurement session and enables inclusion of data from new species and also from the test phase of different tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4 ||PK||NOT NULL||unique ID for each usage of a PTT so test and bird with same ptt_id are two separate IDs/indexes<br />
|-<br />
|''pttid''||int4 ||FK||NOT NULL||Link to DEVICE_INFO table<br />
|-<br />
|''ring_number''||text ||FK||||link to individual table – tests do not have a ring_number<br />
|-<br />
|start_date ||timestamptz||||||Date/time (Local) when tracking begins<br />
|-<br />
|start_latitude ||float8||||NOT NULL||latitude where tracking begins, unit = dec degress<br />
|-<br />
|start_longitude ||float8||||NOT NULL||longitude where tracking begins, unit = dec degrees<br />
|-<br />
|start_altitude||Float8||||||Unit = m, include when known, important for testing<br />
|-<br />
|end_date||timestamptz||||||End of session if known<br />
|-<br />
|time_window ||text||||||<br />
|-<br />
|time_steps ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|location ||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
== GPS_TRACKING_DATA ==<br />
<br />
Tracking data from GPS sensors on PTT/GPS tags<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|latitude||float8||||||Decimal degrees<br />
|-<br />
|longitude||float8||||||Decimal degrees<br />
|-<br />
|speed ||float8||||||m/s<br />
|-<br />
|course||float8||||||degrees<br />
|-<br />
|altitude ||float8||||||m<br />
|-<br />
|alt_status||text||||||<br />
|-<br />
|quality||text||||||Quality information from sensor<br />
|-<br />
|user_QC||text||||||Data flagged as unacceptable by user<br />
|-<br />
|parser_QC||text||||||Data flagged as unacceptable by Microwave parser<br />
|-<br />
|location||geometry||||||postgreSQL geometry<br />
|}<br />
<br />
<br />
Note : <br />
<br />
The parser_QC value can be 1, 2,3,4, 99, or 100. If it 1 the data is OK. If it is 2 or 3 or 4 some form of error correction has been <br />
performed by the Microwave parser. And if it is 100 no error correction was possible. For reliable results it is advised only to use <br />
records with parser_QC values of 1<br />
<br />
== ARGOS_TRACKING_DATA ==<br />
<br />
Tracking data from Argos sensors<br />
<br />
{|border=1<br />
|'''Field'''||'''Type '''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4 ||PK||NOT NULL ||<br />
|-<br />
|'''date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|fix ||text||||||<br />
|-<br />
|latitude1 ||float8||||||<br />
|-<br />
|longitude1 ||float8||||||<br />
|-<br />
|latitude2 ||float8||||||<br />
|-<br />
|longitude2 ||float8||||||<br />
|-<br />
|msgcount ||int4||||||<br />
|-<br />
|frequency ||float8||||||<br />
|-<br />
|average_ti ||float8||||||<br />
|-<br />
|satellite ||text||||||<br />
|-<br />
|max_str ||text||||||<br />
|-<br />
|location1 ||geometry||||||postgreSQL geometry<br />
|-<br />
|location2 ||geometry||||||postgreSQL geometry<br />
|-<br />
|}<br />
<br />
== PTT_ENGINEERING_DATA ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ptt_id'''||int4||PK||NOT NULL ||<br />
|-<br />
|'''tx_date_time'''||timestamp||PK||NOT NULL||GMT<br />
|-<br />
|'''satellite_id'''||text ||PK||NOT NULL||<br />
|-<br />
|ptt_date_time ||timestamp||||||GMT<br />
|-<br />
|activity||int4||||||<br />
|-<br />
|tx_count||int4||||||<br />
|-<br />
|temperature||float8||||||<br />
|-<br />
|battery_voltage||float8||||||<br />
|-<br />
|gps_fix_time||int4||||||<br />
|-<br />
|satellite_count||int4||||||<br />
|-<br />
|hours_reset||int4||||||<br />
|-<br />
|hours_since_gps_fix||int4||||||<br />
|-<br />
|mortality_gt||int4||||||<br />
|-<br />
|seasonal_gt||int4||||||<br />
|-<br />
|shunt||int4||||||<br />
|-<br />
|}<br />
<br />
<br />
In addition the views GPS_TRACKING_SESSION, ARGOS_TRACKING_SESSION, PTT_ENGINEERING_SESSION are which adds the correct track_session.id to the GPS_TRACKING_DATA, ARGOS_TRACKING_DATA and PTT_ENGINEERING_DATA table data.<br />
<br />
<br />
'''BIOLOGICAL INFORMATION'''<br />
<br />
== INDIVIDUAL ==<br />
<br />
Table includes information used to identify an individual<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''ring_number'''||text||PK||NOT NULL||metal ring number<br />
|-<br />
|Id||int4||PK||NOT NULL ||auto-insert, unique ID for each individual organism <br />
|-<br />
|''NEST_INFO_id''||int4||FK||||link to NEST_INFO, not all specimens are linked to a nest<br />
|-<br />
|nest_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|species_certainty||int4||||||1 = certain, 0 = not completely certain<br />
|-<br />
|ring_number||text||||NOT NULL||metal ring number<br />
|-<br />
|color_code||text||||||code for color ring without punctuation<br />
|-<br />
|species||text||||NOT NULL||Scientific name (at least genus)<br />
|-<br />
|sex||text||||||update if or when known<br />
|-<br />
|''FATE_CODEE_id''||textInt4||FK||||Link to FATE_CODE<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== FATE_code == <br />
<br />
{|border=1<br />
|Field ||Type||Key||Constraints||Comments<br />
|-<br />
|'''Id'''||'''Int4'''||'''PK'''||||'''auto-insert'''<br />
|-<br />
|code ||int4||PK||NOT NULL||<br />
|-<br />
|description||text||||||<br />
|-<br />
|}<br />
<br />
<br />
== MEASUREMENT ==<br />
<br />
Metadata Provided by Sovon is needed to describe how these measurements are taken.<br />
<br />
{|border=1<br />
|'''Field '''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|'''id '''||int4||PK||NOT NULL||auto-insert, unique ID for each observation<br />
|-<br />
|''ring_number''||text||FK||||link to individual<br />
|-<br />
|catch_datetime ||timestamp||||||Local time<br />
|-<br />
|release_datetime||timestamp||||||Local time<br />
|-<br />
|mass ||float8||||||grams<br />
|-<br />
|age ||text||||||AD = adult, JUV = juvenile<br />
|-<br />
|wing_length ||float8||||||<br />
|-<br />
|bill_length1 ||float8||||||<br />
|-<br />
|bill_length2 ||float8||||||<br />
|-<br />
|bill_height1 ||float8||||||<br />
|-<br />
|bill_height2 ||float8||||||<br />
|-<br />
|tarsus_length ||float8||||||<br />
|-<br />
|total_head||float8||||||<br />
|-<br />
|observer ||text||||||<br />
|-<br />
|remarks||text||||||<br />
|}<br />
<br />
===Catch_datetime & release_datetime===<br />
<br />
During ringing of juveniles only the date was recorded and not the time. Birds were all released the same day. Ringing and measuring small chicks in the nest took about 2-5 minutes. Colour ringing and sampling of the larger chicks (from 4 July onwards) took about half an hour (rounding up several chicks and banding, sampling and releasing them together). To avoid leaving fields blank, a standard catch time was noted at 12:00 and a release time of 12:15 before July 4 and 12:30 from July 4 and onwards. ''''comments by Kees Oosterbeek''''<br />
<br />
== NEST_INFO ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||'''Comments'''<br />
|-<br />
|''id''||int4||PK ||NOT NULL||<br />
|-<br />
|Species||text||||||<br />
|-<br />
|latitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|longitude||float8||||NOT NULL||Decimal degrees<br />
|-<br />
|year||Int4||||||Year of breeding season<br />
|-<br />
| "location"||geometry||||||postgreSQL geometry<br />
|-<br />
|Remarks||text||||||<br />
|-<br />
|}<br />
<br />
== NEST_OBSERVATION ==<br />
<br />
{|border=1<br />
|'''Field'''||'''Type'''||'''Key'''||'''Constraints'''||''''''Comments''''''<br />
|-<br />
|''id''||''int4''||PK||NOT NULL ||Auto-insert, unique ID for each observation<br />
|-<br />
|''NEST_INFO_id''||''int4''||FK||NOT NULL ||<br />
|-<br />
|date||timestamptz ||||NOT NULL||<br />
|-<br />
|number_egg||int4||||||<br />
|-<br />
|number_young||int4||||||<br />
|-<br />
|pipping||text||||||Activity in egg (peeping or signs of hatching)<br />
|-<br />
|attended||text||||||Activity on nest<br />
|-<br />
|observer||text||||||<br />
|-<br />
|remarks||text||||||<br />
|-<br />
|}<br />
<br />
=Comments:=<br />
<br />
<br />
<br />
<br />
== Graphical Data Model == <br />
<br />
[[Image:Gps_datamodel.png ]]<br />
<br />
<br />
= Argos GPS functions = <br />
<br />
== get_argosgps_track_speed ==<br />
<br />
Compute distance (meters), time-interval, speed (meter/second) and heading (degrees) for a series of subsequent tracking entries with specific device_info_serial. <br />
For the first entry in the sequence these values will always be missing because they are computed as the difference between subsequent rows. <br />
<br />
Usage examples :<br />
<br />
<pre><br />
select * from gps.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');<br />
<br />
select * from gps.get_argosgps_track_speed(41745);<br />
</pre><br />
<br />
Distances and heading are calculated with spherical correction with the Haversine formula as described [http://http://www.movable-type.co.uk/scripts/latlong.html here]. <br />
The heading is the initial heading. Because PostGIS does not calculate the heading we don't use PostGIS here.<br />
<br />
== get_argosgps_track_distance ==<br />
<br />
Compute distance (meters) for Argos GPS tracks to arbitrary point in lat/long or geometry location <br />
<br />
Example usage :<br />
<br />
<pre><br />
<br />
select * from gps.get_argosgps_track_distance(41745, 53.23348333,4.91656)<br />
<br />
-- Get distances from nest<br />
<br />
select * from gps.get_argosgps_track_distance(41745, (<br />
select n.location from gps.nest_info n, gps.track_session s, gps.individual i <br />
where i.nest_info_id = n.id <br />
and i.ring_number = s.ring_number <br />
and s.ptt_id = 41745 limit 1 ))<br />
</pre><br />
<br />
Here the distance is calculated with the PostGIS distance_sphere function whuch uses spherical correction.</div>Bart