Case StudyEnvironmental Monitoring / Data Engineering

HydroScope: Automated
Environmental Data
Acquisition & Visualization.

Project preview

We engineered a bespoke, standalone desktop tool to automate the tedious extraction and translation of historical IMGW (Institute of Meteorology and Water Management) data. The application replaces manual archive parsing with a streamlined, single-screen interface that downloads, decodes, and visualizes raw environmental telemetry instantly. The tool has since been extended with a second data source — agricultural telemetry from eDWIN — reusing the same table and chart components behind a simple source switcher. Ready to see the workflow? Let's jump in.

IndustryEnvironmental Monitoring / Data Engineering
StatusDelivered / Actively Extended
MarketPoland
01_Objective

The client was wasting countless hours manually hunting for station codes, unzipping IMGW archives, and mapping raw phenomenon codes to readable formats in Excel. The goal was to build a local, lightning-fast desktop executable that automates this entire pipeline, delivering clean CSV exports and instant visual trend analysis without relying on external servers.

02_

The Challenge.

01

Fragmented Raw Data

IMGW historical archives are notoriously hostile to quick analysis-hidden behind cryptic database codes, nested ZIP files, and scattered parameters.

02

Human-Readable Translation

Automating the mapping of raw phenomenon IDs (e.g., rainfall, temperature) and numerical station codes into plain-text names without requiring a complex backend infrastructure.

03

Immediate Visual Feedback

The client needed to verify data trends instantly before exporting to Excel, requiring a lightweight, built-in charting engine within a standalone, single-screen desktop environment.

04

Preserving Investment While Expanding Scope

Adding a second, structurally different data source risked forcing a rebuild of the already-paid-for table and chart components, or spinning up a separate, redundant application entirely.

05

Divergent API Contracts

The new source's API returned multi-parameter payloads in a different shape than IMGW, paginated in 90-day windows instead of monthly blocks — incompatible with the existing chunking logic and parameter dictionary out of the box.

03_

The Solution.

01

Serverless Desktop Engine

We built a standalone desktop application tailored for local execution. Users simply select dates and search for stations by name (e.g., "Szczecin" instead of cryptic IDs), and the software handles the extraction, parsing, and data mapping entirely locally.

Station selection interface
02

Automated CSV Pipeline

The core engine automatically translates raw IMGW codes into human-readable labels, outputting structured, analysis-ready CSV files. This eliminated manual Excel formatting, turning a multi-hour chore into a one-click process.

CSV export and download screen
03

Instant Trend Visualization

We integrated a native charting module directly into the single-screen interface. Once data is fetched, the app instantly plots the parameter's trajectory (e.g., annual rainfall or water levels), allowing the operator to validate trends visually before generating the final export.

Built-in trend chart visualization
04

Multi-Source Adapter (eDWIN)

We added a source switcher that reloads the station list on toggle and normalizes eDWIN's multi-parameter agricultural payloads into the same shape our table and chart components already expect — extending the tool to ~534 agrometeorological stations without touching the existing IMGW pipeline.

IMGW / eDWIN data source switcher
04_

Technology Used.

[01]
ElectronDesktop Runtime
[02]
ReactUI
[03]
RechartsData Visualization
[04]
eDWIN AdapterMulti-Source Data Normalization

Ready to centralize your field operations?

Transition from fragmented data silos into a single source of truth. Schedule a deep-dive session to map out a scalable, hardware-agnostic architecture for your infrastructure.