Selected work / Product engineering · GIS · Data systems

Baruna — Spatial & Environmental Intelligence

A product-led workflow for turning a project boundary into traceable environmental and spatial evidence that teams can review, interpret, and carry into a professional decision process.

RoleProduct direction + engineering
FocusAOI workflow, evidence, review
StatusActive proof of work
01 / Context

The useful unit is a project area, not another map viewer.

Many environmental and spatial tools make datasets visible without turning them into a repeatable review workflow. Baruna is being shaped around a simpler question: given a real project area, what evidence should a team inspect before it goes deeper?

02 / System approach

Boundary → evidence → context → review.

The product direction separates input, evidence generation, interpretation context, and review output. That keeps the workflow understandable while leaving room for more datasets and analysis methods later.

01 / InputProject AOI

Boundary supplied as the starting context.

02 / EvidenceSpatial signals

Relevant datasets are summarized against the same area.

03 / ContextInterpretation

Time period, provenance, and limitations stay visible.

04 / OutputReview-ready result

A result that supports discussion instead of ending at visualization.

03 / Engineering challenges

The hard part is making evidence usable without overstating it.

Project-area first

The workflow needs to work with real project AOIs, not force every question into administrative boundaries.

Evidence before conclusion

Environmental signals need provenance, time context, and explicit limitations so the product does not overclaim what remote data proves.

From map to workflow

The product must help a reviewer move from an area to evidence and interpretation, rather than stop at a passive layer viewer.

04 / What this demonstrates

Product thinking carried through technical delivery.

Baruna is useful portfolio proof because it combines product direction, spatial/data workflows, backend and web delivery, and the discipline to define what the system can and cannot claim. The case study intentionally separates verified capability, current limitation, and planned exploration.