events.json schema + event generation script for california design points

[dlebauer]

MVP for events based on #3551

use case the primary goal is having an events.json that we can use to start building out write.events.SIPNET and doing runs for the CCMMF project. Closes ccmmf/organization#143

Includes two files:

• Script builds MVP JSON file from site attributes.
• MVP JSON schema for events

It generates fixed values for each site (planting, harvest, pruning, tillage, irrigation) according to the PEcAn events schema.

Output: events.json file.

• There is one on geo.bu.edu: /projectnb2/dietzelab/ccmmf/data/events/events.json
• attached here
  events.json.gz
• and a three site version as a gist.

This script uses dummy data and fixed values in order to support development of downstream pipeline. There is much work to do.

• Currently running for design points
• Later will need to generate event summaries in a matrix that can be used as inputs to site selection and downscaling.

Discussion ?s:

• should these go in a new package focused on agronomic data?
• These quickly get very large - with 10 sites

TODO

• add optional fraction_area_0to1 to specification
• make crop required for planting and harvest
• populate provenance / source information [not for MVP, but should be done when these are created)
• Add examples with ground cover added to orchards
• Find a home for JSON schema (inst/extdata? utils?)

[infotroph]

How carefully considered is the decision to represent geometry as a uri rather than an object? Might there be cases where geometry wants to be embedded directly like the provenance is?

[infotroph]

Check failure is saying to move the json schema out of data/ -- I'd be fine with dropping it into inst/ instead, optionally in an events/ subdir.

[infotroph]

Merging dlebauer#9 should fix the CI failure