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 /wiki/spaces/SPADE3/pages/71762209 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 | 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:
- A Destination essentially contains a sequence of LocationInformation elements.
- Each LocationInformation object contains:
- A LocationType equivalent to the FacilityType we're looking at.
- A location Identifier
- A location name
- AN address. Note that CountyFIPS code is a ContextItem for us.
Cropzone use cases (in progress)
Crop | Spatial footprint | Time | Example use case |
|---|---|---|---|
| Different | Same | Same | Can correspond to a tightly intercropped pair of crops or varieties, where it is not practical to separate them geographically. |
| Different | Same | Different | Crop rotation Note that the timeframes do not have to be mutually excusive: for example, a cover crop can be sown (e.g., via an aerial applicator) before the preceding crop is harvested. it would correspond to a different crop zone because of our definition of cropzones as a spatial region where a given crop is being grown during a given time interval. |
| Different | Different | Same | Block pattern in a field grown with different horticultural crops in a single-crop (short) growing season. |
| Different | Different | Different | Block pattern in a field grown with different horticultural crops in a multiple-crop (long) growing season. |
| Same | Same | Same | Improbable use case. Could be used to represent a landlord arrangement, where different landlords are allocated different fractions of the production of the whole field. (That case can be represented differently.) |
| Same | Same | Different | Multiple horticultural crops per season in a warm climate. |
| Same | Different | Same | Different management or traceability needs (e.g., different customers) require separate record-keeping. Can reflect a setting where parts of a field have different customers, or a blocked arrangement on a citrus grove. |
| Same | Different | Different | Successive plantings of the same crop, but with different spatial footprints (e,g., due to different guidance patterns used during planting) |