...
Crops and tasks can’t be applied to layers (open discussion)
Layers can consist of any number of polygons (rather than only 1)
Layers may have different attributes at different depths (e.g. soil texture at 0 - 10cm vs. 50 - 100cm)
Only 1 of each type of layer can be “active” at a given time (though we should probably allow multiple different layers to be active simultaneously)
Though Layers maintain a history
...
Open questions:
Should we be able to assign a task to a layer?
Likely beneficial for the user! May be difficult to implement. Example David gave is “Take a soil sample from all organic locations on the farm”. In order to do this the system would need to be able to:
Differentiate different location / zone statuses for grouping (e.g. organic, non-organic, transitioning)
Specify a task type for teach of the grouped locations / zones
Link together in a flow each task x location pairing so that the user can provide details specific to that pairing (e.g. a lat / long within a area for the soil sample to be taken)
Easier to implement would be the ability to identify locations that fall into a specific grouping (e.g. organic locations) and then easily select those to create a task.
How should we handle layers that have a vertical component? For example, with soil texture we might want to define the soil texture attributes for different strata, e.g. 0 - 10 cm, 11 - 30 cm, 31 - 50 cm, 51 - 100 cm.
...