Open craig-willis opened 6 years ago
We can discuss when you get in. The "Datasets" streams are all driven by sensorposition extractor which we haven't been running more than 3 at once while doing the full field processing. Currently there are ~6 million messages to process there: http://rabbitmq.ncsa.illinois.edu:15672/#/queues/clowder/terra.metadata.sensorposition
I would expect a number of the RGB Geotiffs, for example, are in that queue waiting to be submitted to Geostreams.
For the upcoming DataDrivenAg hackathon, I was trying to do the following:
The hope was to use the new sensorquery API, but this is still not fully working. Instead, I tried going to Geostreams directly:
Find the Geostreams sensor associated with a given Season 4 plot -- I picked something in the middle of the field:
I couldn't find a way to get the list of available streams (i.e., TERRA sensors) available for the plot. Instead, I had to retrieve the full list of streams and parse for the name (this seems undesirable):
Now that I know the names of available streams, I can compose by combining name with Geostreams sensor_id (i.e., "RGB GeoTIFFs Datasets (1008)") :
And finally I can make the leap to get the associated datapoints:
In this case, there are only 82 datapoints covering only a handful of season 4 dates:
It seems that there is a large amount of information missing from Geostreams? I was expecting a minimum of one datapoint per day