Introductions made.

Reviewed the work we are doing on the Field Boundary Use Case Mural.

Move work forward to create a charter.

Gather insights

The Situation/Challenge:

Multiple expressions of a field boundary that represents the same physical space; how to reconcile these?

Objective(s) for Phase 1 (the first working group)

• Metadata quality metric to tag the boundary
  • Semantic s for above
• Quality of Accuracy of RTK data (RTK-driven data is precise, not necessarily accurate)
  • This could be a follow-on or parallel working group
  • Accuracy will be different for different use cases
  • Review work from SPADE 3
  • Explore other technology options (let's not pick winners)
    
    
• Definitions/Semantics of field and field boundary
  • Classification of boundary descriptions
  • What are the data that define the classifications? (e.g., bay station data vs. prescription data)
    
    
• Regulatory vs Crop Insurance: CLUs are used by FSA (maximize acreage); Insurance looking for more accuracy than CLU (define coverage) 
  Farmers are using a manual process today
  Some countries in Europe use CLUs for prescription boundaries

Scope: Global solution (but not all edge cases)

Deliverables:

• Leverage current ISO standards
• Definitions of drivers related to field boundaries and field boundary accuracy
• Classifications of boundary uses
• Definitions of field obstacles (Enumerated list)

Timeline: 3 months from start.

Likely/Desired Members:

• Equipment manufacturers
• Hexagon (NovaTel)
• Chinese companies? 
  • OEM Subgroup of ISO Strategic Advisory Group on Smart Farming 

Jeremy W Wilson and Dan Berne (Unlicensed) to draft a charter