ADAPT - Enumerations vs EnumeratedRepresentations
- Tim Shearouse (Deactivated)
- R. Andres Ferreyra (Unlicensed)
- Jaap Van Bergeijk
- Tarak Reddy (Deactivated)
One of the short-term tasks ahead of us is to resolve what enumerations should be converted to an EnumeratedRepresentation, and which should stay as enumerations. The table below will hep guide & track the situation.
| Enumeration | Context | State, recommendation | Comments |
|---|---|---|---|
| ApplicationStrategyEnum | Documents | Enumeration in the model (ApplicationStrategyEnum) Leave as-is. | Used to describe the underlying strategy for specifying a summary Work Record or Work Order. Values are: RatePerArea, RatePerTank, TotalProduct |
| CompoundIdentifierTypeEnum | General | Enumeration in the model (CompoundIdentifierTypeEnum) Leave as-is. | Suggest a conversation regarding different identification strategies we wish to support. |
| ConnectorType | Equipment | Enumeration in the model | Empty in the model. Does not seem to be used. |
| ContactTypeEnum | Document | Enumeration Leave as is | May want to rename "Contact" class to "ContactItem". May want to add Twitter handle.This rabbit-hole may lead to switching to EnumeratedRepresentation |
| ContainerAction | Container | Enumeration Make EnumeratedRepresentation | This is an active area of development, and will likely grow and change. |
| ContainerUseType | Container | Enumeration Make EnumeratedRepresentation | This is an active area of development, and will likely grow and change. |
| DateContext | General | Enumeration | Needs some deeper discussion (May fit better as a ContextItem becuase of that system's ModelScope feature). |
| DeviceClassificationEnum | Equipment | Enumeration in the model (DeviceClassificationEnum) Leave as-is | Discuss. We would benefit from making this extensible, but extending the list would likely require creating a corresponding Configuration class. |
| DocRelationshipTypeEnum | Document | Enumeration in the model Make EnumeratedRepresentation? | Discuss. We would likely benefit from making this extensible, since asserting rich relationships among documents can deliver a lot of value (e.g., traceability). |
| FacilityType | EnumeratedRepresentation Leave as-is, review content | Review content vis à vis ongoing Container discussion. | |
| GPSSourceEnum | Shapes | Enumeration Make EnumeratedRepresentation? | Discuss. Will this be extensible in the short term? Should we use this for any shape? |
| GuidanceExtensionEnum | |||
| GuidancePatternTypeEnum | |||
| HitchTypeEnum | |||
| IdSourceTypeEnum | |||
| ImplementTypeEnum | |||
| LoadTypeEnum | |||
| LoggingLevelEnum | |||
| LoggingMethodEnum | Equipment | ISO-specific Leave as-is | Discuss. Is this likely to change with new versions of ISO? |
| MachineTypeEnum | |||
| OMCodeComponentTypeEnum | Not currently in code. Probably needs to be a ContextItem | Suggesting ContextItem because of that system's Properties feature. | |
| OperationTypeEnum | |||
| OriginAxleLocationEnum | |||
| PersonRole | Documents | EnumeratedRepresentation (dtPersonRole) | Review content |
| ProductFormEnum | Product | ||
| ProductStatusEnum | Should agree on levels for all related matters. Active / Deprecated? | ||
| PropagationDirectionEnum | |||
| ReferenceLayerTypeEnum | Definitely make an enumerated representation! | ||
| RepresentationCodeSourceEnum | |||
| ShapeTypeEnum | |||
| UnitOfMeasureDimensionEnum | |||
| WorkItemPriorityEnum | |||
| WorkStatusEnum | |||
| ImplementType | Equipment | EnumeratedRepresentation (dtImplementType) | How is this used in the context of DeviceElements? Does the list represent a consensus? |
| MachineType | Equipment | EnumeratedRepresentation (dtMachineType) | How is this used in the context of DeviceElements? Does the list represent a consensus? |
| CropNutritionIngredient | Product | EnumeratedRepresentation (dtCropNutritionIngredient) | Should it contain oxides? |
| 41 Enumerated Representations | |||
| ProjectionType | EnumeratedRepresentation (dtProjectionType) | Is this used? Should it be there? | |
| TillageType | EnumeratedRepresentation (dtTillageType) | We need to discuss tillage (and services in general), but this enumerated representation is currently not used. | |
| UnloadingAugerState | EnumeratedRepresentation (dtUnloadingAugerState) | Is this used? Should it be there? | |
| JDArmedDWS | EnumeratedRepresentation (dtJDArmedDWS) | Is this used? Should it be there? | |
| SectionControlMasterState | EnumeratedRepresentation (dtSectionControlMasterState) | Is this used? Should it be there? | |
| SprayerSystemOperatingMode | EnumeratedRepresentation (dtSprayerSystemOperatingMode) | Is this used? Should it be there? | |
| PrescriptionControlMasterState | ? | EnumeratedRepresentation (dtPrescriptionControlMasterState) | Is this used? Should it be there? |
ContextItemType (ADAPT - ContextItem Discussion)
GpsSourceType (ADAPT - FieldBoundary Discussion)
- Unknown
- Drawn
- MobileGps
- DeereRTK
- DeereRTKX
- DeereSF1
- DeereSF2
- DeereWAAS
or Reference to NMEA 2000 GNSS Method parameter:
1 = GNSS fix
2 = DGNSS fix
3 = Precise GNSS
4 = RTK Fixed Integer
5 = RTK Float
6 = Estimated (DR) mode
7 = Manual Input
8 = Simulate mode
(NMEA 2000 defines at maximum 16 tokens for GNSS Method)
Additional non- NMEA 2000 methods:
16 = Desktop generated data
17 = Other
Priority (ADAPT - WorkItem and StatusUpdate Discussion)
- Immediately
- SoonAsPossible (no due date)
- High
- Medium
- Low
Role (ADAPT - Person / PersonRole / Company Discussion)
- Grower
- Operator
- CropAdvisor
- Authorizer
- CustomApplicator
- TruckDriver
- InputSupplier
- IrrigationManager
- GovernmentAgency
- Customer
- Financier
- InsuranceAgent
THIS NEEDS MORE WORK. Is there a standard list of agricultural roles? This would conceivably be an AgGateway API-mediated reference data list, but there is potential for confusion / duplication.
ShapeType (ADAPT - Shape Discussion)
- Point
- Multipoint
- LineString
- MultiLineString
- LinearRing
- Polygon
- MultiPolygon
- RasterGrid?
ProductType
OperationType
PrescriptionType
Crop Growth Stage: Note: there will be MANY of these: phenology is crop-specific, plus there are often multiple scales per crop (e.g., Zadoks and Feekes scales for wheat). We can probably begin with Wheat, Corn, and Soybeans, which have readily-available scales.