-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
821e605
commit b04c91f
Showing
1 changed file
with
25 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,28 @@ | ||
### Data Collection (Field Book, Climmob, other Phenoapps, etc) | ||
### Data Collection | ||
<!-- (Field Book, Climmob, other Phenoapps, ImageBreed, etc) --> | ||
|
||
* General use case description(s) | ||
<!-- * General use case description(s) | ||
* Specific tool examples | ||
* Alternate solutions/ why is it better with BrAPI | ||
* future related use cases, areas to improve | ||
* future related use cases, areas to improve --> | ||
|
||
#### Field Book | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
Phenotypic data collection is an essential part of the breeding process. Historically, gathering data in the field was done with pen and paper, or perhaps some version of a digital spreadsheet. The abundance and prevalence of smart phones has allowed the Field Book mobile app to enhance data collection. Field Book can create well formed digital observation records from the moment they are taken. This can improve the efficiency of data collection and reduce human error. | ||
|
||
BrAPI was able to take things a step further by automating the flow of data from the Field Book mobile app to a central database server. In this work flow, data is collected and stored completely digitally with little-to-no human involvement. | ||
|
||
#### ClimMob | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
Not all data can be collected by a single person, or even by a single organization. ClimMob is a tool to easily allow citizen scientists to assist in the data collection process. Although this data may not be as detailed as a focused scientific program, it can be very useful to collect simple data from a wide range of locations and environments. | ||
|
||
When it comes to BrAPI compatibility, ClimMob follows the same patterns established by Field Book. During a survey, all the farmer collected data is stored in a central ClimMob node. When the survey is complete, all the data is uploaded automatically via BrAPI to a central breeding database for long term storage and analysis. | ||
|
||
#### ImageBreed | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
High-throughput phenotyping has been gaining significant traction lately as a way to collect lots of data very quickly. Image collection from unmanned arial and ground vehicles (UAVs and UGVs) are a great way to collect a lot of raw data all at once, then analyze it later. ImageBreed is a image collection pipeline tool to support regular use of UAVs and UGVs. | ||
|
||
When the raw images have been processed through the standardization pipelines in ImageBreed, useful phenotypes can be extracted from the images. The BrAPI standard is used to push these phenotypes back to a central breeding database where they can be analyzed with other data. In addition to this, ImageBreed also has the option to use BrAPI to upload the raw images to the central breeding database, or any other BrAPI compatible long term storage service. The BrAPI models in the current version of the standard (V2.1) are rudimentary, but effective. The ImageBreed team has put in some work to enhance the BrAPI image data standards. |