DB Tables 2015 - Revision history

Stacy shinneman: /* gps.uva_tracking_data101 */

2021-01-22T09:33:08Z

‎gps.uva_tracking_data101

Stacy shinneman: /* gps.ee_nest */

2021-01-22T09:32:00Z

‎gps.ee_nest

Stacy shinneman: /* gps.uva_tracking_data101 */

2021-01-22T09:31:41Z

‎gps.uva_tracking_data101

Stacy shinneman at 14:18, 20 February 2018

2018-02-20T14:18:11Z

Stacy shinneman at 14:17, 20 February 2018

2018-02-20T14:17:09Z

Andera: moved DB Tables 2014 to DB Tables 2015

2015-01-09T12:22:09Z

moved DB Tables 2014 to DB Tables 2015

Andera: /* gps.uva_acceleration101 */

2014-11-27T10:56:19Z

‎gps.uva_acceleration101

Andera: /* gps.uva_tracking_data101 */

2014-11-20T14:19:33Z

‎gps.uva_tracking_data101

Andera: /* gps.uva_tracking_data101 */

2014-11-20T14:18:45Z

‎gps.uva_tracking_data101

Andera: /* Relationship with projects */

2014-11-19T11:24:53Z

‎Relationship with projects

@@ Line 182: / Line 182: @@
 === ''gps.''uva_tracking_data101 ===
-Each row represents a GPS fix as it is interpreted from the data that comes via the GPS tracker.
+Each row represents a GPS fix as it is interpreted from the data that comes via the GPS tracker. See [[Reference systems for GPS coordinates and altitudes]] for further details.
 This table structure has ''not'' changed with respect to our previous database.

@@ Line 310: / Line 310: @@
 |reference_name||varchar||NO||A string with a useful reference for you. We recommend its being unique for each nest in a project, but the system does NOT enforce it.
 |-
-|latitude||numeric||YES||Latitude of the coordinates where the nest was found.
+|latitude||numeric||YES||Latitude of the coordinates where the nest was found (WGS1984 datum)
 |-
-|longitude||numeric||YES||Longitude of the coordinates where the nest was found.
+|longitude||numeric||YES||Longitude of the coordinates where the nest was found (WGS1984 datum)
 |-
 |start_date_time||timestamp||NO||When the nest was spotted.

@@ Line 196: / Line 196: @@
 |date_time||timestamp||NO||Time when the fix was taken. UTC (i.e.: no timezone). Part of the unique identifier of the GPS fix.
 |-
-|latitude||float8||YES||Latitude of the GPS fix.
+|latitude||float8||YES||Latitude of the GPS fix (WGS1984 datum)
 |-
-|longitude||float8||YES||Longitude of the GPS fix.
+|longitude||float8||YES||Longitude of the GPS fix (WGS1984 datum)
 |-
-|altitude||int4||YES||Altitude above sea level measured by GPS tag in meters
+|altitude||int4||YES||Altitude above sea level measured by GPS tag in meters (WGS1984 datum)
 |-
 |pressure||int4||YES||Pressure measured by GPS tag sensor in Pascals

← Older revision		Revision as of 14:18, 20 February 2018
Line 1:		Line 1:
−	'''Note:''' What follows is a list of tables and explanations intended for the database maintainers or otherwise people actively involved in the development of the e-Ecology system itself. ~~Users from~~ e-Ecology should ~~mainly~~ focus on the documentation ~~made available~~ on the [[UvA-BiTS_Tracking_Data\|UvA-BiTS Tracking Data page]]. This page is ~~made available to all users~~ as a reference only.	+	'''Note:''' What follows is a list of tables and explanations intended for the database maintainers or otherwise people actively involved in the development of the e-Ecology system itself. Most e-Ecology users should focus on the documentation on the [[UvA-BiTS_Tracking_Data\|UvA-BiTS Tracking Data page]]. This page is intended as a reference only.

	The database is split into two useful schemas: ''admin'' and ''gps''. The ''gps'' schema is meant for data that should be readily available for users, and that they may edit via the services (software tools) offered to that effect. The ''admin'' schema is meant to host data only accessible for e-Ecology administrators.		The database is split into two useful schemas: ''admin'' and ''gps''. The ''gps'' schema is meant for data that should be readily available for users, and that they may edit via the services (software tools) offered to that effect. The ''admin'' schema is meant to host data only accessible for e-Ecology administrators.

← Older revision		Revision as of 14:17, 20 February 2018
Line 1:		Line 1:
−	'''Note:''' What follows is a list of tables and explanations intended for the database maintainers or otherwise people actively involved in the development of the e-Ecology system itself. Users from e-Ecology should mainly focus on the documentation made available on the [[~~DB_Views_2014~~\|~~DB views 2014~~ page]]. This ~~actual [[DB_Tables_2014\|DB tables 2014~~ page]] is ~~only~~ made available to ~~every user for completion~~.	+	'''Note:''' What follows is a list of tables and explanations intended for the database maintainers or otherwise people actively involved in the development of the e-Ecology system itself. Users from e-Ecology should mainly focus on the documentation made available on the [[UvA-BiTS_Tracking_Data\|UvA-BiTS Tracking Data page]]. This page is made available to all users as a reference only.

	The database is split into two useful schemas: ''admin'' and ''gps''. The ''gps'' schema is meant for data that should be readily available for users, and that they may edit via the services (software tools) offered to that effect. The ''admin'' schema is meant to host data only accessible for e-Ecology administrators.		The database is split into two useful schemas: ''admin'' and ''gps''. The ''gps'' schema is meant for data that should be readily available for users, and that they may edit via the services (software tools) offered to that effect. The ''admin'' schema is meant to host data only accessible for e-Ecology administrators.

← Older revision	Revision as of 12:22, 9 January 2015
(No difference)

@@ Line 295: / Line 295: @@
 |-
 |z_acceleration||int2||YES||Acceleration measured on the z (or heave) axis (range between -2666 and 2666).
 |}

@@ Line 234: / Line 234: @@
 |direction||numeric||YES|| Heading in degrees; 0 is north, 90 is east
 |-
-|altitude_agl||float8||YES|| Reported GPS altitude - terrain elevation on the coordinate
+|altitude_agl||float8||YES|| Reported GPS altitude MINUS terrain elevation on the coordinate
 |}

@@ Line 227: / Line 227: @@
 |-
 |location||geometry||YES||postgreSQL geometry; to allow GIS operations
 |}

@@ Line 289: / Line 289: @@
 |}
-== Relationship with projects ==
+== Relation to projects ==
 === ''admin.''ee_membership ===