Pull request changes

Author: Chris-Schnaufer

sensors/06-list-datasets-by-plot.Rmd

@@ -2,8 +2,9 @@
 
 ## Pre-requisites: 
 
-* if you have not already done so, you will need to 1) sign up for the [beta user program](terraref.org/beta) and 2) sign up and be approved for access to the the [sensor data portal](terraref.ncsa.illinois.edu/clowder) in order to get the API key that will be used in this tutorial
-described in this tutorial. 
+* if you have not already done so, you will need to 1) sign up for the [beta user program](terraref.org/beta) and 2) 
+sign up and be approved for access to the the [sensor data portal](terraref.ncsa.illinois.edu/clowder) in order to get 
+the API key that will be used in this tutorial. 
 
 The terrautils python package has a new `products` module that aids in connecting
 plot boundaries stored within betydb with the file-based data products available
@@ -40,9 +41,13 @@ Names will now contain a list of sensor names available in the Clowder
 geostreams API. The list of returned sensor names could be something like the 
 following:
 
+* flirIrCamera Datasets
 * IR Surface Temperature
+* RGB GeoTIFFs Datasets
+* stereoTop Datasets
+* scanner3DTop Datasets
 * Thermal IR GeoTIFFs Datasets
-* flirIrCamera Datasets
+* ...
 
 ## Getting a list of files
 
@@ -88,9 +93,10 @@ to retrieve its data.
 
 ## A Word of Caution
 
-The names of variables in this section don't necessarily match the ones in the section 
-above. This is unintentinoal and is due to the legacy behind each of these approaches. The
-names are meaningful and consistent in their respective domains, but not between each other.
+The names and meanings of variables in this section don't necessarily match the ones in the section 
+above and it may be easy to get them confused. The API queries the database directly and thereby reflects 
+the database structure. This is the main reason for the naming differences between the API and the terraref
+client.
 
 For example, the Clowder API's use of the term *SENSOR_NAME* is equivalent to *site_name* above.