Explore the marketplace. Items labelled Example are fictional. Video reviewed means a human has reviewed the introduction, not the engineering qualifications. Sign in to contact a client about a published project. Project payments are not open.YOUR ENGINEER
Open for proposals

Turn irrigation logger exports into a clean daily dataset

Combine two logger export formats into a documented daily table for twelve irrigation zones.

Acaciafold Agritech

Nairobi, Kenya Remote

Posted

This is an example brief. Its company, dates, budget, assignment and progress illustrate a project; they do not represent available or commissioned work. Proposals cannot be submitted.

The brief

The work and the intended result

Our agronomy team currently merges flow and soil-moisture exports by hand. We want a repeatable local pipeline for two fixed CSV formats across twelve zones. It should standardise timestamps, preserve source identifiers, flag missing intervals and create daily summaries without silently filling gaps. The work includes one dry-run review using a six-week sample. Sensor configuration, irrigation recommendations, live ingestion and predictive models are not part of this package.

Duration
2 weeks
Commitment
Approx. 30 hours total
Location
Remote

What you’ll deliver

  • Two input parsers and a common timestamped output table
  • Daily flow totals and moisture summaries with explicit completeness flags
  • A reconciliation report tracing three selected days back to source rows
  • Repeatable scripts, example configuration and a short operator guide

Expertise needed

  • Experience aligning time-series exports with inconsistent timestamps
  • Ability to preserve provenance through aggregation
  • Clear handling of counter resets and missing intervals
  • Python
  • Data engineering
  • Time series
  • Data validation

A running start

What’s already in place

  • Six weeks of both logger formats for twelve named zones
  • A zone-mapping table and local time-setting notes
  • Three manually checked days and examples of known counter resets

Project milestones

To shape together
  1. 01

    Map the input formats

    Confirm zone identifiers, time conventions and how counter resets should be flagged.

  2. 02

    Build the daily transformation

    Parse both formats and produce summaries with completeness indicators and source references.

  3. 03

    Reconcile the sample period

    Match the three reference days and review how missing or reset intervals appear in the output.

To agree before starting

A shared definition of done

Confirm the deliverables, review checks and response window together so everyone knows what a successful handover looks like.

Suggested acceptance criteria

  • Every agreed deliverable is included in the handover, in the agreed file formats.
  • Assumptions, limitations and open questions are documented alongside the work.
  • The project owner reviews the work against the brief and returns one consolidated feedback list before approval.

When the scope changes

Record the requested change, its reason and its effect on deliverables, budget and timing. Both parties agree the revised scope in writing before the additional work begins.