UvAGPS - Revision history

Andera: /* UvA-BiTS Data Model */

2014-07-31T07:12:49Z

‎UvA-BiTS Data Model

Stacy shinneman: /* = uva_trackingfile_messages (Table) & uva_trackingfile_parsing (Table) */

2013-01-30T16:09:15Z

‎= uva_trackingfile_messages (Table) & uva_trackingfile_parsing (Table)

Stacy shinneman: /* uva_access_device (Table) & uva_access_individual (Table) */

2013-01-30T16:08:49Z

‎uva_access_device (Table) & uva_access_individual (Table)

Stacy shinneman: /* uva_access_device (Table) or uva_access_individual (Table) */

2013-01-30T16:04:49Z

‎uva_access_device (Table) or uva_access_individual (Table)

Stacy shinneman: /* UVA_WARNING102 (Table) or UVA_WARNING_LIMITED (View) */

2013-01-30T16:04:20Z

‎UVA_WARNING102 (Table) or UVA_WARNING_LIMITED (View)

Stacy shinneman: /* UVA_DEVICE or UVA_DEVICE_LIMITED (Table and View) */

2013-01-30T16:01:58Z

‎UVA_DEVICE or UVA_DEVICE_LIMITED (Table and View)

Stacy shinneman: /* UVA_TRACK_SESSION or UVA_TRACK_SESSION_LIMITED (Table and View) */

2013-01-30T15:59:00Z

‎UVA_TRACK_SESSION or UVA_TRACK_SESSION_LIMITED (Table and View)

Stacy shinneman: /* UVA_TRACK_SESSION or UVA_TRACK_SESSION_LIMITED (Table and View) */

2013-01-30T15:46:25Z

‎UVA_TRACK_SESSION or UVA_TRACK_SESSION_LIMITED (Table and View)

Stacy shinneman: /* UvA-BiTS Data Model */

2013-01-30T15:27:33Z

‎UvA-BiTS Data Model

Stacy shinneman: /* UvA-BiTS Data Model */

2013-01-09T11:54:04Z

‎UvA-BiTS Data Model

@@ Line 3: / Line 3: @@
 All tables, views and functions related to UvA-BiTS are in the GPS schema in the flysafe database and begin with the '''prefix "uva_"'''.  The tables/views that do not begin with "uva_" are related to a different project.
-Not everybody has access to all data.  Most users will only be granted access to tables/views with the '''postfix "_limited"''' that show data collected with devices specific to their project(s).
+Not everybody has access to all data.  Most users will only be granted access to views with the '''suffix "_limited"''' that show data collected with devices specific to their project(s).
-'''The difference between a Table and a View:''' The difference is actually quite small. The same data can be queried and viewed in the same way in both tables and views. However, the data stored in a table can also be updated, deleted and changed by people with administrative privileges. The purpose of a view is to allow users who only want to view and/or query the data to do so without any possibility of altering the data. For this reason, we recommend that most users access the data through the Views. In addition, views often contain valuable additional data calculated from the raw tracking data.
+'''The difference between a Table and a View:''' The difference is actually quite small from the user perspective. The same data can be queried and viewed in the same way in both tables and views. However, the data stored in a table can also be updated, deleted and changed by people with administrative privileges. The purpose of a view is to allow users who only want to view and/or query the data to do so without any possibility of altering the data. For this reason, we recommend that most users access the data through the Views. In addition, views often contain valuable additional data calculated from the raw tracking data.
 '''Where to find the basic tracking data:'''  Depending on the version of UvA-BiTS firmware installed in the GPS device, different database tables/views are used to store tracking data:
@@ Line 12: / Line 12: @@
 * UVA_TRACKING_DATA101 table: Introduced to the database to store the data collected with the newest firmware (versions 1.0.1.4 till 1.0.2.4) because the new version is able to collect so much more information.
-The tables/views in the UvA-BiTS database are described individually in detail below. Each table/view has been placed into one of three sections depending on the type of data they contain:
+The tables/views in the UvA-BiTS database are described in detail in the sections below. Each table/view has been placed into one of three sections depending on the type of data they contain:
 * ''Tracking Data:'' Primary tracking data that is of most interest to most users (i.e. device numbers, lat/long, x/y/z acceleration, altitude, etc.).
 * ''Bird Data:'' Data about the birds on which the devices are mounted (species, sex, etc.).

@@ Line 579: / Line 579: @@
 To regulate the access to bird trackers and individuals, access is granted through these tables. These tables grant the rights to see tracking devices and birds, respectively. Only individuals with administrative privileges are allowed to work with these tables. The data entered into these tables produces the "_limited" tables and views.
-=== uva_trackingfile_messages (Table) & uva_trackingfile_parsing (Table) ==
+=== uva_trackingfile_messages (Table) & uva_trackingfile_parsing (Table) ===
 These two tables are produced as the raw data is parsed and stored in the database. Only individuals with administrative privileges are allowed to view or work with these tables.

← Older revision		Revision as of 16:08, 30 January 2013
Line 578:		Line 578:

	To regulate the access to bird trackers and individuals, access is granted through these tables. These tables grant the rights to see tracking devices and birds, respectively. Only individuals with administrative privileges are allowed to work with these tables. The data entered into these tables produces the "_limited" tables and views.		To regulate the access to bird trackers and individuals, access is granted through these tables. These tables grant the rights to see tracking devices and birds, respectively. Only individuals with administrative privileges are allowed to work with these tables. The data entered into these tables produces the "_limited" tables and views.
		+
		+	=== uva_trackingfile_messages (Table) & uva_trackingfile_parsing (Table) ==
		+
		+	These two tables are produced as the raw data is parsed and stored in the database. Only individuals with administrative privileges are allowed to view or work with these tables.

	= UvAGPS functions =		= UvAGPS functions =

@@ Line 575: / Line 575: @@
 |}
-=== uva_access_device (Table) or uva_access_individual (Table) ===
+=== uva_access_device (Table) & uva_access_individual (Table) ===
 To regulate the access to bird trackers and individuals, access is granted through these tables. These tables grant the rights to see tracking devices and birds, respectively. Only individuals with administrative privileges are allowed to work with these tables. The data entered into these tables produces the "_limited" tables and views.

@@ Line 574: / Line 574: @@
 |line||text||||||The actual line in the file
 |}
 = UvAGPS functions =

@@ Line 281: / Line 281: @@
 === UVA_DEVICE or UVA_DEVICE_LIMITED (Table and View) ===
-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 the section below called [[UvAGPS|Accelerometer calibration]].
+Different GPS tags have been used over the years. The UVA_DEVICE table was created to be able to track the different firmware versions and specific properties for the different devices. This table also includes essential information needed to calibrate the accelerometers. For more information see the section below called [[UvAGPS|Accelerometer calibration]]. For more information about the different tags, see the section below called [[UvAGPS|Information about GPS receivers]].
 {|border=1

@@ Line 22: / Line 22: @@
 === UVA_TRACK_SESSION or UVA_TRACK_SESSION_LIMITED (Table and View)===
-This is essential metadata about GPS tag deployment that is provided by the project manager when the tag is first mounted on a bird. 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. To avoid analyzing data that was collected during testing, you should always use this table/view in your query as a way to select date that coincides with the start_date of a particular track session.
+This is essential metadata about GPS tag deployment that is provided by the project manager when the tag is first mounted on a bird. 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. To avoid analyzing data that was collected during testing, you should always include this table/view in your query as a way to select data that was measured after the start_date of a particular track session.
 {|border=1

@@ Line 5: / Line 5: @@
 Not everybody has access to all data.  Most users will only be granted access to tables/views with the '''postfix "_limited"''' that show data collected with devices specific to their project(s).
-'''The difference between a Table and a View:''' The difference is actually quite small. The same data can be queried and viewed in the same way in both Tables and Views. However, the data stored in a table can also be updated, deleted and changed by people with administrative privileges. The purpose of a view is to allow users who only want to view and/or query the data to do so without any possibility of altering the data. For this reason, we recommend that most users access the data through the Views. In addition, views often contain additional data calculated from the raw tracking data.
+'''The difference between a Table and a View:''' The difference is actually quite small. The same data can be queried and viewed in the same way in both Tables and Views. However, the data stored in a table can also be updated, deleted and changed by people with administrative privileges. The purpose of a view is to allow users who only want to view and/or query the data to do so without any possibility of altering the data. For this reason, we recommend that most users access the data through the Views. In addition, views often contain valuable additional data calculated from the raw tracking data.
 '''Where to find the basic tracking data:'''  Depending on the version of UvA-BiTS firmware installed in the GPS device, different database tables/views are used to store tracking data: