Difference between revisions of "UAV High-Throughput Phenotyping Database"

From Poland Lab Wiki
Jump to: navigation, search
 
(11 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
 
1. Flight metadata - Contains information about the date, time and location of each flight where image data is collected.
 
1. Flight metadata - Contains information about the date, time and location of each flight where image data is collected.
2. Image metadata - Contains inforamation about date, time and UAV position for each image collected during a flight.
+
 
 +
2. Image metadata - Contains information about date, time and UAV position for each image collected during a flight.
  
 
The current database schema for UAV HTP data is shown in the figure below:
 
The current database schema for UAV HTP data is shown in the figure below:
Line 11: Line 12:
  
 
=== Flight Images Query ===
 
=== Flight Images Query ===
The query below shows how to retrieve all images for a specific flight:
 
  
 
Select all image data records for a specific flight:
 
Select all image data records for a specific flight:
SELECT * from uas_images WHERE flight_id ='<flight_id from uas_run table ';
+
 
 +
<syntaxhighlight lang="sql">
 +
SELECT * from uas_images WHERE flight_id ='<flight_id from uas_run_new table> ';
 +
</syntaxhighlight>

Latest revision as of 13:12, 1 August 2018

The UAV High-Throughput Phenotyping Database contains information about images collected by camera-equipped aerial platforms. There are two basic classes of information that are collected:

1. Flight metadata - Contains information about the date, time and location of each flight where image data is collected.

2. Image metadata - Contains information about date, time and UAV position for each image collected during a flight.

The current database schema for UAV HTP data is shown in the figure below:

Uav htp.png

Example Queries

Flight Images Query

Select all image data records for a specific flight:

SELECT * FROM uas_images WHERE flight_id ='<flight_id from uas_run_new table> ';