|
roaming | (Part 1 here: http://talk.newagtalk.com/forums/thread-view.asp?tid=496857)
(Part 2 here: http://talk.newagtalk.com/forums/thread-view.asp?tid=496918)
The 3rd presentation of the morning was shorter, and took us up to lunch. The presenter spoke about different industry projects that are trying to bring some standardization to "big ag data". i.e. file formats (ESRI Shapefiles vs ISO XML vs proprietary formats, etc.) In other words, if we're going to recognize the true potential of "big data", we have to be able to share lots of "little data". Getting that "little data" right (i.e. valid, accurate, cleaned of errant data points, etc.) is critical. Otherwise, "big data" will just be lots and lots of bad data. This kind of aggregate data, whether at the farm level or higher, would be at the best useless, and at the worst actually harmful.
The presenter holds a leadership position in AgGateway (link below), which has a Precision Ag Council to focus on precision ag issues. In turn, the Precision Ag Council has an ongoing "SPADE" project, "Standardized Precision Ag Data Exchange". As I understood him, SPADE seeks to build on the functionality of the ISOBUS Task Controller for machinery control and data exchange between an implement and desktop software program, and to develop standards for additional levels of functionality for pre-field planning, compliance reporting, and data exchange between desktop software programs ("FMIS" in ISO parlance").
The ultimate goal of AgGateway is seamless data interchange between all pieces in the data space, from machine displays to desktop software to data service providers to researchers to regulatory agencies, etc, etc, etc. Like when I send a text message from my Verizon Droid phone to my brother's AT&T Windows phone, to my wife's Sprint iPhone, and to my sister's PC. What happens behind the scenes is invisible to the end-user, but the texts go through (usually :-)) without a hitch, though there are different manufacturers, service providers, embedded software, and hardware devices involved. A great deal of standardization is required to make this happen.
One other major effort is to standardize reference data/terminology so that there is a common vocabulary for data exchange across manufacturers. You'd think this would be a pretty fundamental concept of ISOBUS, but... This project is actually part of a larger effort to identify gaps in existing ISO 11783 functionality or standards, so that the gaps can be addressed by the appropriate ISO working groups.
Finally, standards are only part of the issue. Standards that aren't implemented, or that are implemented in a non-standard way, don't move us forward.
http://www.aggateway.org/
http://www.aggateway.org/WorkingGroups/Councils/PrecisionAgCouncil....
http://www.aggateway.org/WorkingGroups/Projects/SPADE.aspx
http://www.aef-online.org/en/aef-projects/isobus/why-isobus.html
http://www.aggateway.org/News/PressReleases/AgGatewayTestsPrecision...
(Part 4 here: http://talk.newagtalk.com/forums/thread-view.asp?tid=497226)
(Part 5 here: http://talk.newagtalk.com/forums/thread-view.asp?tid=498506)
Edited by torn 9/2/2014 18:15
| |
|