Removing some features (for now)

[eddiechoi00]

Hey all, the WashU team has deemed some of the following features as unnecessary at this point in time, especially for the first release of the extension. We thought it would be better to potentially add these back in as needed, but please feel free to discuss it here. Thank you!

Property Name	Type	Description
ml:creation_method	string	REQUIRED. how the label was created e.g. field walk, image-annotated, ML generated
ml:creation_method_detail	string	additional details about the creation method, including potentially a link to the algorithm
ml:boundary_type	string	REQUIRED. whether the boundary is for a field, ownership parcel, hedge, or other boundary
ml:creation_date	datetime	REQUIRED.[Auto-added] Date collection was created or published
ml:verified_until	datetime	REQUIRED. the last date for which the boundary is verified to be present on ground (e.g., through ground-truth or remote sensing image verification)
ml:quality	string	REQUIRED. the level of quality control applied to this polygon
ml:confidence	float	a value between zero and one that represents the confidence in a generated polygon (higher value = higher confidence)
ml:machine_generated	boolean	REQUIRED. Indication of machine-generated boundaries or not
ml:admin0	string	REQUIRED. [Auto-added] a unique admin0 (country) name for the administrative region that contains the field - can auto-generate from GADM boundaries
ml:crop_type	string	the type of crop e.g. maize
ml:crop_category	string	REQUIRED. high-level crop category e.g. cereal (e.g. FAO)

[m-mohr]

I think ml:admin0 is duplicate of ml:country_code, so can be removed. ml:verified_until can be removed in favor of determination_datetime. ml:creation_method and ml:machine_generated can be removed in favor of determination_method. ml:creation_date is now in the collection properties of this extension.

ml:boundary_type seems to be a good field for a separate extension.

ml:crop_type and ml:crop_category seem to be a good fit for another extension.

ml:quality and ml:confidence could also be a good extension, but may also fit in here.

The only one that's really left then is ml:creation_method_detail.