These zips contain various simulated data. The 2 examples are identical except in the choice of ReferenceIDs, to illustrate the new flexibility for defining these.
The following questions arose out of the simulation exercise:
Do we need an enumeration to define the specific product variation within ADAPT to define which attributes collection to read? E.g., "CropProtectionProduct" in addition to setting the Product Type to "Herbicide" and filling the CropProtectionAttributes.
Cardinality issues needing discussion
Does any element with an id also require a name?
Product Status Code (Active/Inactive) current is required.
Variety Product.VarietyIsGeneticallyEnhanced currently is required
Do we need to standardize the naming/organization of GeoParquet/GeoTiff files alongside the GeoJson?
Do we need to standardize on the name for the "root.json?"
These zips contain various simulated data. The 2 examples are identical except in the choice of ReferenceIDs, to illustrate the new flexibility for defining these.
The following questions arose out of the simulation exercise:
Do we need an enumeration to define the specific product variation within ADAPT to define which attributes collection to read? E.g., "CropProtectionProduct" in addition to setting the Product Type to "Herbicide" and filling the CropProtectionAttributes.
Cardinality issues needing discussion
Do we need to standardize the naming/organization of GeoParquet/GeoTiff files alongside the GeoJson?
Do we need to standardize on the name for the "root.json?"
Integers.zip UUIDs.zip