Note: The integer IDs below correspond to the ReferenceID element in CompoundIdentifiers

Note: This list supersedes, as of 20150129, the WorkItemOperation material in a previously circulated Excel.

LoggedData (implements WorkRecord)

• As of 20150129, LoggedData only has the data already contained in its parent class. We will be on the lookout for any attributes that we need to add, especially in the context of Scouting / FieldObservations. If there are none before the release of v1 of the ADAPT data model, we reserve the right to collapse LoggedData back to its parent.
• In the future we will want to consider auxiliary actors in the process of logging data (e.g. a truck and its driver, a grain cart and its driver, etc...) 
• We have not yet implemented the concept of mark/note, which would allow for space- and time-specific notes to be logged.
• 20150427: R. Andres Ferreyra (Unlicensed) reviewed the LoggedData object with PAIL team members Dan Berne (Unlicensed) and aberger@agsense.net (Unlicensed). LoggedData is very compatible with PAIL's InboundData and OffsiteData objects, but the general idea of OperationData (which, I believe is central to the SPADE interpretation of LoggedData) does not fit at all. PAIL's suggestion is to create a subclass of LoggedData called Observations, that has OperationData as optional (at best.) This may be a good home for scouting data as well, although it remains to be discussed whether scouting plans (incl. pre-arranged scouting locations) are not analogous to WorkOrders / WorkItems.

OperationData

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

SpatialRecord

Section [Not Implemented]

• 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

Meter (analogous to a process data variable in ISO) [Not Implemented]

NumericMeter (Subclass of Meter) [Not Implemented]

EnumeratedMeter (Subclass of Meter) [Not Implemented]

SectionSummary

CalibrationFactor

• This is typically entered as a result of measurement via scale tickets, etc.

Note:

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);
				}
			}
		}	
	}
}