Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 Notes*GuidanceAllocationIds* FieldIdCropZoneIdSummaryId
AttributeTypeMultiplicityDescription
WorkItemIdIdCompoundIdentifier1
WorkRecordIdInteger1
GrowerIdInteger0..1
FarmIdIntegerLoggedNote0..1 
FieldIdInteger0..1
CropZoneIdMachineIdInteger0..1 
FarmIdTimeScopesTimeScope0..*
PersonRoleIdsInteger0..*
EquipmentConfigurationGroupEquipmentConfigurationGroup0..1 
GuidanceAllocationIdsInteger0..*
WorkItemIdsInteger0..1* 
SummaryIdInteger0..1
 NotesPersonRoleIdsNoteInteger0..n* 
OperationDataOperationData1..* 
ReleaseSpatialDataAction

DescriptionString0..1
MachineIdInteger0..1 

OperationData

  • We will break this out so we have only one OperationData object instance per load. 
AttributeTypeMultiplicityDescription
IdCompoundIdentifier1

Unique identifer

 R. Andres Ferreyra (Unlicensed): I think this needs to go; I see no reason for OperationData to need to exist independently of the LoggedData

.

 

ConnectorIdsInteger0

.

.n

A reference to the Connector objects linking MachineConfiguration and ImplementConfiguration (or two ImplementConfiguration) objects. Somewhat redundant because that info can be traced back through the ImplementConfiguration and its Connector references to machine and/or other impllements, but included here to help test / sanity check / select Connectors for processing / export.


LoadIdInteger0..1

A reference to the load. See ADAPT - Load / LoadDestination Discussion

OperationTypeOperationTypeEnum1The operation performed
PrescriptionIdInteger0..1A reference to the Prescription, if any, used during this operation. If multiple products are used they will be included as a single multi-product prescription.
ProductIdInteger0..1

The product used for the operation

ProductIdsInteger0..*
VarietyLocatorIdInteger0..1A reference to the VarietyLocator layer used during this operation, if any
WorkItemOperationIdInteger0..1A reference to the Work Item Operation that generated this work
MaxDepthInteger1Count of depth
SpatialRecordCountInteger1How many spatial records are there?
EquipmentConfigIDInteger0..1
EquipmentConfigurationIdsInteger0..*
GetSpatialRecords()IEnumerable<SpatialRecord>
 

Returns an IEnumerable of SpatialRecord
GetSections(Depth: Integer)IEnumerable<Section>  SpatialRecordCountInteger1How many spatial records are there?EquipmentConfigID
GetDeviceElementUses()(int, IEnumerable<DeviceElementuse>)

DescriptionString0..1
CoincidentOperationDataIdsInteger0..*
GetSections(Depth: Integer)IEnumerable<Section>

ConnectorIdsInteger0..
1 

...

nA reference to the Connector objects linking MachineConfiguration and ImplementConfiguration (or two ImplementConfiguration) objects. Somewhat redundant because that info can be traced back through the ImplementConfiguration and its Connector references to machine and/or other impllements, but included here to help test / sanity check / select Connectors for processing / export.


SpatialRecord

AttributeTypeMultiplicityDescription
GeometryShape1The geometry defining the location
TimestampDateTime1The timestamp of the location.
GetMeterValue(meter: Meter)RepresentationValue 
?
SetMeterValue(meter: Meter, RepresentationValue: value)   


GetAppliedLatency(meter: Meter)   

 





Section

  • Depth 0 always represents the full swath and contains DDIs and their values at that level (e.g. Elevation, Weather Information, Fuel Consumption)
  • Depths 1+ represent a segmented version of the full swath
AttributeTypeMultiplicityDescription
IdCompoundIdentifier1UniqueIdentifier
OperationDataIdInteger1A reference to the OperationData this section applies to
DepthInteger1Indicates which depth the section was recorded for
OrderInteger1An incrementing value indicating the order of the sections from left to right
SectionWidthNumericRepresentationValue1The width of the section
TotalDistanceTravelledNumericRepresentationValue0..1Total distance travelled for the operation when section status was on
TotalElapsedTimeNumericRepresentationValue0..1Total elapsed time for the operation when the section status was on
MetersMeter0..n 

Meter (analogous to a process data variable in ISO)

...

AttributeTypeMultiplicityDescription
IdCompoundIdentifier1The id of the calibration factor
MeterIdInteger1The meter to apply the calibration factor to
TimeScopeIdsInteger0...nThe time the calibration occurred. 20150903: R. Andres Ferreyra (Unlicensed) replaced datetime class with TimeScope, for consistency with other mandates.
ValueNumericRepresentationValue1The value of the calibration. 20150903:  R. Andres Ferreyra (Unlicensed) replaced Double type with NumericRepresentationValue, for consistency with other mandates.

...

 



Note: 


Code Block
languagec#
foreach (spatialRecord in operationData.GetSpatialRecords())
{
	var shape = spatialRecord.GetShape();
	var time = spatialRecord.GetTimeElapsed();
	for(depth=0; depth< operationData.GetMaxDepth();depth++)
	{
		foreach(section in operation.GetSections(depth)
		{
			var width = section.Width;
			foreach(meter in section.GetMeters())
			{
				if(meter is NumericMeter)
				{
					var value = spatialRecord.GetMeterValue(meter);   // Yo, note that there are different representations for meters...
					var appliedLatency = spatialRecord.GetAppliedLatency(meter);
				}
				else if(meter is EnumeratedMeter)
				{
					var value = spatialRecord.GetMeterValue(meter);
				}
			}
		}	
	}
}

...