Difference between revisions of "High-Throughput Phenotyping Database"
From Poland Lab Wiki
(→Future HTP Database) |
(→Future HTP Database) |
||
| Line 45: | Line 45: | ||
The key schema design changes are: | The key schema design changes are: | ||
| + | <ol> | ||
| + | <li> A single measurement metadata table for both sensors and cameras.</li> | ||
| − | + | <li> Separate observation tables which can support single or multi-valued measurements and different data types.</li> | |
| − | + | <li> Full support of GIS spatial columns for positions, plots and experiments.</li> | |
| − | + | <li> Introduction of a new platform state table that records the position and orientation of the data collection platform over time.</li> | |
| − | + | <li> Inclusion of orientation (roll,pitch and yaw) columns for both sensors and the data collection platform.</li> | |
| − | + | <li> Standardization of all position coordinate data to utilize WGS84 latitude/longitude positions.</li> | |
| − | + | <li> Separation of sensor offset information from measurement metadata table to a sensor offsets table that records offsets on a per run basis instead of per observation.</li> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | <li> Simplification of the HTP instruments table.</li> | ||
| + | </ol> | ||
| − | |||
The diagram below illustrates the set of future HTP database tables and their relationships. | The diagram below illustrates the set of future HTP database tables and their relationships. | ||
Revision as of 20:26, 17 May 2016
The High-Throughput Phenotyping database consists of a set of platform-specific tables for each data collection platform: pheMU, phenocart and phenocam.
Each platform has an images table, an htp table and a run table.
- The images table stores metadata about the images that were collected during each data collection run.
- The htp table stores metadata about sensor measurements (observations) that were collected during each run.
- The run table stores information about each data collection run such as date/time and geographical extent of the run.
Each set of platform-specific tables also relates to the plot_map table and the htp_instrument table.
- The plot_map table contains information about the geographical coordinates of each plot associated with an experiment (field).
- The htp_instrument table contains information about cameras and sensors used on each platform.
The diagram below illustrates the generalized set of HTP tables and their relationships.
PheMU HTP Database
The core set of tables for the PheMU database are the phemu_images table, the phemu_htp table and the phemu_run table.
- The phemu_images table stores metadata about the images that were collected during each data collection run.
- The phemu_htp table stores metadata about sensor measurements (observations) that were collected during each run.
- The phemu_run table stores information about each data collection run such as date/time and geographical extent of the run.
The core PheMU tables also relate to the plot_map table and the htp_instrument table.
- The plot_map table contains information about the geographical coordinates of each plot associated with an experiment (field).
- The htp_instrument table contains information about cameras and sensors used on each platform.
The diagram below illustrates the set of PheMU database tables and their relationships.
Future HTP Database
The future HTP database schema is designed to be data collection platform independent and will support both land-based and aerial data collection platforms.
The key schema design changes are:
- A single measurement metadata table for both sensors and cameras.
- Separate observation tables which can support single or multi-valued measurements and different data types.
- Full support of GIS spatial columns for positions, plots and experiments.
- Introduction of a new platform state table that records the position and orientation of the data collection platform over time.
- Inclusion of orientation (roll,pitch and yaw) columns for both sensors and the data collection platform.
- Standardization of all position coordinate data to utilize WGS84 latitude/longitude positions.
- Separation of sensor offset information from measurement metadata table to a sensor offsets table that records offsets on a per run basis instead of per observation.
- Simplification of the HTP instruments table.
The diagram below illustrates the set of future HTP database tables and their relationships.
