Reference to the associated Field object, which can be found on the Catalog.
(Shape descendant class)
The dates for which the boundary is valid. May also contain last modified date.
Headland (a child class, really)
The temporal component (i.e., headlands changing over time) will be taken care of via the FieldBoundary object titself: leverage the timescopes of the FieldBoundary, and create a new field boundary if/when the headlands change.
The GPS correction system which was used to create the boundary – i.e., RTK, SF1, WAAS.
Documents the original spatial coordinate system of the data if it was recorded in something other than WGS84 (indicating the points have been re-projected)
The need is to be able to mark if the interior rings in each polygon are passable or not.
Each interior ring will have an (integer) ID. We will use the M attribute to store the shape id.
Here we would include a reference to a dictionary linking these IDs with:
A name for the ring (e.g., "Pond")
Whether the ring is passable or not.
Any geo-political attributes which need to be added to the boundary object. Examples may include FSA Area or related CLU's (Common Land Units) reported for crop insurance purposes.
This Id is going to correspond to the M value of the multipolygon rings of shape data. It references a specific ring in a FieldBoundary's spatial data.
Describes whether the interior boundary can be driven through, as opposed to some type of impassable obstacle in the field.