...
This document will go over the proposed structure for a history object for the species selector
Object Example Simple
This object will need to be changed to match the API structure. It holds the minimum set of things that should be remembered
| Code Block |
|---|
{
"statestateId": "<state>",
"regionstateLabel": "<region>"<label>,
"goals": "<goals>",
} |
Object Example with Soil Conditions and Weather
| Code Block |
|---|
{ "state": "<state>", "region": "regionId": "<region>", "soilConditionsregionShorthand": ["<soil codition 1><shorthand>", "<soil codition 2>", ...], "floodingFrequency": ["<flooding frequency 1>", "<flooding frequency 2>", ...], "firstFrost": "<date>""concilLabel" <label>, "concilShorthand" <shorthand>, "lastFrostgoals": "<date><goals>", "averageMonthPrecipselectedCrops": ["<data>crop1", "averageAnnualPrecip": "<data>"crop2"], "frostFreeDaysconsent": "<days>"<bool>, "goalsdeclinedLogin": "<goals>"<bool>, } |
Questions
Do we want to store soil conditions and weather?
Do we want to store sidebar → my impression is no