Argos Data Model - Revision history

Stacy shinneman: /* GPS Data Model */

2018-02-20T14:11:23Z

‎GPS Data Model

2018-02-20T14:09:50Z

2018-02-20T10:35:19Z

‎GPS_TRACKING_DATA

2018-02-20T10:34:52Z

‎GPS_TRACKING_DATA

2018-02-20T10:34:15Z

‎GPS Data Model

2018-02-20T10:33:10Z

‎GPS Data Model

2018-02-19T09:28:42Z

‎GPS Data Model

2014-07-29T07:12:55Z

‎get_argosgps_track_distance_direction

2014-07-29T07:12:28Z

‎get_argosgps_track_distance

2014-07-29T07:12:09Z

‎get_argosgps_track_speed

@@ Line 1: / Line 1: @@
-== GPS Data Model ==
+== Argos GPS Data Model ==
 Last updated January 5, 2010 Bart Heupers - [[ UvAGPS ]] moved to special page
@@ Line 7: / Line 7: @@
 '''NOTE:''' On July 2014 we moved all argos-related tables, views, functions and types to a new schema called '''argos'''.
-'''e-ECOLOGY TRACKING DATABASE'''
+'''e-ECOLOGY ARGOS TRACKING DATABASE'''
 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).

@@ Line 120: / Line 120: @@
 Note :
-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
+The parser_QC value can be 1, 2, 3, 4, 99, or 100. If it is 1 the data is OK. If it is 2 or 3 or 4, some form of error correction has been
 performed by the Microwave parser. And if it is 100, no error correction was possible. For reliable results it is advised only to use
 records with parser_QC values of 1.

@@ Line 120: / Line 120: @@
 Note :
-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
+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
-performed by the Microwave parser. And if it is 100 no error correction was possible. For reliable results it is advised only to use
+performed by the Microwave parser. And if it is 100, no error correction was possible. For reliable results it is advised only to use
-records with parser_QC values of 1
+records with parser_QC values of 1.
 == ARGOS_TRACKING_DATA ==

@@ Line 23: / Line 23: @@
 Primary keys are noted by bold italic text. Foreign keys are noted by italic text in the Field column.
-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.
+Microwave will under no circumstances provide information about their checksum calculations. If feasible, SARA will duplicate the procedure and include a flag representing the microwave filtered data.
 '''TECHNICAL INFORMATION FROM TAGS'''

@@ Line 7: / Line 7: @@
 '''NOTE:''' On July 2014 we moved all argos-related tables, views, functions and types to a new schema called '''argos'''.
-'''FLYSAFE TRACKING DATABASE'''
+'''e-ECOLOGY TRACKING DATABASE'''
 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).

← Older revision	Revision as of 14:09, 20 February 2018
(No difference)

@@ Line 394: / Line 394: @@
 <pre>
-select * from gps.get_argosgps_track_distance_direction(41745, 53.23348333,4.91656)
+select * from argos.get_argosgps_track_distance_direction(41745, 53.23348333,4.91656)
 -- Get distances from nest
 create temporary table nest as
-(   select  n.latitude, n.longitude from gps.nest_info n, gps.track_session s, gps.individual i
+(   select  n.latitude, n.longitude from argos.nest_info n, argos.track_session s, argos.individual i
      where i.nest_info_id = n.id
        and i.ring_number = s.ring_number
        and s.ptt_id = 41745 limit 1 );
-select * from gps.get_argosgps_track_distance_direction(41745, (select latitude from nest), (select longitude from nest));
+select * from argos.get_argosgps_track_distance_direction(41745, (select latitude from nest), (select longitude from nest));
 </pre>

@@ Line 373: / Line 373: @@
 <pre>
-select * from gps.get_argosgps_track_distance(41745, 53.23348333,4.91656)
+select * from argos.get_argosgps_track_distance(41745, 53.23348333,4.91656)
 -- Get distances from nest
-select * from gps.get_argosgps_track_distance(41745, (
+select * from argos.get_argosgps_track_distance(41745, (
-   select n.location from gps.nest_info n, gps.track_session s, gps.individual i
+   select n.location from argos.nest_info n, argos.track_session s, argos.individual i
      where i.nest_info_id = n.id
        and i.ring_number = s.ring_number

@@ Line 357: / Line 357: @@
 <pre>
-select * from gps.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');
+select * from argos.get_argosgps_track_speed(41745, '2008-01-01 00:00:00', '2010-01-01 00:00:00');
-select * from gps.get_argosgps_track_speed(41745);
+select * from argos.get_argosgps_track_speed(41745);
 </pre>