Import work plans/field operations as logs

Created on 24 September 2023, 9 months ago
Updated 20 October 2023, 8 months ago

Problem/Motivation

General JD documentation:
Work plan: https://developer.deere.com/dev-docs/work-plans
Field operation: https://developer.deere.com/dev-docs/field-operations

As a first pass lets include the generic metadata for logs (basically do not include geometry, yet). This is split between Work plans and Field operations:

Work plan:
Low owner (operator assignment)
Location (field)**
Log name (work order, use as prefix/suffix?)
Equipment (machine, implement assignment)

Field operation:
Log type (field operation type)
Log name (add operation type as prefix/suffix to work order?)
Timestamp (last updated)
Location (field)**
Season (only for harvest?)
Quantities (measurement types)

Steps to reproduce

N/A

Proposed resolution

Simple import/creation

Remaining tasks

Implement

User interface changes

Add similar field operations import table

API changes

None

Data model changes

None

πŸ“Œ Task
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States paul121 Spokane, WA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @paul121
  • @paul121 opened merge request.
  • πŸ‡ΊπŸ‡ΈUnited States paul121 Spokane, WA

    Some updates on this:

    basically do not include geometry, yet

    Turns out there is an API endpoint that makes getting the field operation boundary quite easy: https://developer.deere.com/dev-docs/boundaries#/fieldOperations/{operationId}/boundary/get

    This is split between Work plans and Field operations:

    I've realized this data *is not* split between work plans and field operations. I'm not going to query work plans for now. The documentation was confusing because the examples didn't show all of the data that is returned with field operations. Basically, field operations are only created when a JD machine does something. There is no way to create them via the UI. They need a shape file and all the operation data. Work plans can be created via the UI, they are only for specifying a set of work to do. It is possible that a field operation will reference the work plan that it is related to, but it is not required or always available (if the farmer just goes out and performs some activity in the field without prior planning).

    Equipment (machine, implement assignment)

    Sooo ironically this will not be very easy. The fieldOperationMachines API that links a field operation to the machine(s) (?) that performed it is not a public API. I've been told we can get this information from the shape file metadata. πŸ“Œ Import shape files with field operations Active

  • Status changed to Fixed 8 months ago
  • πŸ‡ΊπŸ‡ΈUnited States paul121 Spokane, WA
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024