Changes for 2018

Data products

PSII

need equations to compute traits

Texture

• region of interest
• needs to work on raw images + scale to plot (like other image analyses)

Multispectral NDVI/PRI

aggregate points and compute plot level means

RGB stereotop

clip plot fragments and combine

https://github.com/terraref/computing-pipeline/issues/356

Environmental Logger

https://github.com/terraref/reference-data/issues/179

Geostreams

• exclude wavelength from geostreams dataset
• improve irrigation (perhaps per-plot)

Laser Scanner

• georeferenced or referenced to gantry xyz ply product
• leaf angle high priority
• height distribution: add skewness and kurtosis

netcdf

• we may not need to keep variables in both geostreams and netcdf. netcdf can be used specifically for solar informtion
• redundant variables: raw_ and sensor_ values (e.g. of par, co2, etc) are redundant with variables that have names like 'Atmospheric_CO2_concentration'.
  • Remove variables beginning in raw_ from the environmental logger netcdf files
  • variables beginning in sensor_ have no data
  • use consistent standard names

to subset out just the spectral radiometer and other values needed for the hyperspectral workflow, something like

ncks -v time -v flx_dwn -v flx_sns -v flx_spc_dwn -v wvl_lgr -v wvl_dlt \
          Level_1/EnvironmentLogger/2017-08-12/EnvironmentLogger_lv1_2017-08-12_uamac.nc  #outfile.nc?

?? what variables are needed for hyperspectral workflow?

Lemnatec Metadata

https://github.com/terraref/reference-data/issues/176

• use controlled vocabularies, e.g. as described in https://github.com/terraref/sensor-metadata/blob/master/README.md
  • provide dictionary for metadata fields
• add url link to managements from experiment_metadata field (??) similar to select * from managements where treatment_id in (select id from treatments join traits join sites join experiments where experiments.name = ....)

Protocols

Submitting an extractor

• write protocol that includes:
  • Pull requests
  • Tests
  • Protocol
  • quality statement

Revising existing extractors

• need to make sure we have done code reviews, have tests, protocols, quality statements for extractors above

Field methods

• how to use / store in BETYdb
• how to archive / assign doi, share etc

Gantry

• data reviews / qa/qc
• process to handle scan programs https://github.com/terraref/computing-pipeline/issues/362