ADAPT - Grower / Farm / Field / Cropzone / ContactInfo / Location / Facility / FacilityTypeEnum Discussion
Grower
Attribute | Type | Multiplicity | Description |
|---|---|---|---|
Id | CompoundIdentifier | 1 | |
Name | String | 1 | |
ContactInfo | ContactInfo | 0..1 | Links to Contact Information object |
ContextItems | ContextItem | 0..* |
Farm
Attribute | Type | Multiplicity | Description |
|---|---|---|---|
Id | CompoundIdentifier | 1 | |
Description | String | 1 | |
GrowerId | Integer | 0..1 | |
ContactInfo | ContactInfo | 0..1 | 20150810: Added for ISOXML compatibility |
TimeScopes | TimeScope | 0..* | |
ContextItems | ContextItem | 0..* |
Field
Field | Type | Multiplicity | Description |
|---|---|---|---|
Id | CompoundIdentifier | 1 | |
Description | String | 1 | |
GrowerId | Integer | 0..1 | |
FarmId | Integer | 0..1 | |
Area | NumericRepresentationValue | 0..1 | User-set area. |
ActiveBoundaryId | Integer | 0..1 | Currently-active boundary |
ContextItems | ContextItem | 0..* | |
Slope | NumericRepresentationValue | 0..1 | Useful for erosion calculation |
Aspect | NumericRepresentationValue | 0..1 | Useful for understanding causes of yield variability, etc. |
SlopeLength | NumericRepresentationValue | 0..1 | Useful for erosion calculations |
GuidanceGroupIds | Integer | 0..* | The guidance group, potentially including multiple guidance lines |
TimeScopeIds | TimeScope | 0..* |
CropZone
Attribute | Type | Multiplicity | Description |
|---|---|---|---|
Id | CompoundIdentifier | 1 | |
TimeScopes | TimeScope | 0..1 | |
Description | string | 1 | |
FieldID | Integer | 1 | |
CropID | Integer | 0..1 | |
Area | NumericRepresentationValue | 1 | |
BoundingRegion | MultiPolygon | 0..1 | |
BoundarySource | GpsSource | 1 | |
Notes | Note | 0..* | |
GuidanceGroupIds | Integer | 0..* | |
ContextItems | ContextItem | 0..* |
ContactInfo
Attribute | Type | Multiplicity | Description |
|---|---|---|---|
Id | CompoundIdentifier | 1 | |
AddressLine1 | String | 0..1 | |
AddressLine2 | String | 0..1 | |
PoBoxNumber | String | 0..1 | |
PostalCode | String | 0..1 | |
City | String | 0..1 | |
StateOrProvince | String | 0..1 | 20150820: Do state & province need to be separate? What do we do with a country like Colombia that has "departments", or a country like Japan that has "prefectures"? Maybe we need to move back to a single country subdivision attribute? @Tim Shearouse (Deactivated): agroXML includes both "State" and "Province". ISO combines them. I did some digging ... international registration systems I have built in the past (outside the ag world) always combined them into a single field. Japanese "prefectures" replaced an older system of "provinces", and are typically entered in the state/province field. I do not know about Colombian addresses. |
Country | String | 0..1 | Free-form text |
CountryCode | String | 0..1 | 2-character country code from ISO 3166-2 See ISO 3166-2 Country Codes (2-letter and 3-letter) for the codes. |
Contacts | Contact | 0..* | |
Location | Location | 0..1 | 20150903: Switched to using the Location class instead of point. This provides At some recent point we added GLN to location. This makes having a separate GLN in ContactInfo a moot point. 20150909: Removed GLN from Location, switching it to a ContextItem instead. |
ContextItems | ContextItem | 0..* | 20150909: Added for flexibility and to simplify use of GLNs. |
Contact
Attribute | Type | Multiplicity | Description |
|---|---|---|---|
Number | String | 1 | |
Type | ContactTypeEnum | 1 | Phone, Mobile, Fax, Email |
Location
Attribute | Type | Multiplicity | Description |
|---|---|---|---|
Position | Point | 0..1 | |
ContextItems | ContextItem | 0..* | 20150909: Agreed to add this and collapse GLN into ContextItems |
GpsSource | GpsSource | 0..1 | |
ParentFacilityId | Integer | 0..1 |
Facility
Attribute | Type | Multiplicity | Description |
|---|---|---|---|
Id | CompoundIdentifier | 1 | Reference ID |
CompanyId | Integer | 0..1 | ID of Company the Facility belongs to |
Description | String | 0..1 | Name of the facility ("Big Grain Bin") |
ContactInfo | ContactInfo | 0..1 | Note that ContactInfo contains a Location, which in turn contains a GLN |
FacilityType | FacilityTypeEnum | 0..1 | 20150909: Driven by a use case presented by @Joe Tevis. We need to develop this list; |
FacilityType | EnumeratedValue | 0..1 | |
ContextItems | ContextItem | 0..* | 20150909: Added as agreed upon by group. (Deals flexibly with GLN and other regulatory info.) |
ParentFacilityId | Integer | 0..1 |
FacilityTypeEnum [Not Implemented]
Item | Description | Comment |
|---|---|---|
Office | 20150910 Simply an example | |
Grain bin | 20150910 Simply an example | |
Facility | From AgXML's LocationType. For discussion | |
Farm | From AgXML's LocationType. For discussion | |
Field | From AgXML's LocationType. For discussion | |
Storage Location | From AgXML's LocationType. For discussion | |
Tank | From AgXML's LocationType. For discussion |
Note how Destination is handled in AgXML: