Import shape files with field operations

Created on 19 October 2023, 8 months ago
Updated 19 February 2024, 4 months ago

Problem/Motivation

Building on from πŸ“Œ Import work plans/field operations as logs Fixed it would be nice to import the shape files that JD provides via API. This would also enable the ability to link field operation logs to machines via the metadata.json in the shape file.

Steps to reproduce

N/A

Proposed resolution

Import shapefiles to the log files

Remaining tasks

Implement

User interface changes

None

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
  • πŸ‡ΊπŸ‡ΈUnited States paul121 Spokane, WA
  • Status changed to Fixed 5 months ago
  • πŸ‡ΊπŸ‡ΈUnited States paul121 Spokane, WA

    I've implemented a first version of this: https://git.drupalcode.org/project/farm_jd/-/commit/eb3785b9c704a7625474...

    When checking for new field operations we also enqueue the field operation's shape file to be generated (this is an async operation, can take up to 30 minutes). Most of the time this file should be ready once the field operation is actually imported as a log.

    Right now it is only requesting the Point - EachSection shapefile from JD. It also uses the farmOS configured units. For more info see here: https://developer.deere.com/dev-docs/field-operations#/fieldOps/{operationId}/get

    Some ideas for future:
    - Have a dedicated page that lets you sync shape files "on demand" - this could allow specifying a specific granularity of shape file you want to sync (Point/Polygon, Section, Sensor, Hertz). It could also help remedy issues when a shape file is not able to be synced when the log is created.
    - Make auto-syncing of shapefiles entirely configurable. This could also include configuration for the type of shapefile.
    - Parse the equipment out from the shapefile. This should be possible, but looks challenging.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024