About

Who builds STREAM?

STREAM did not start as a software company's product idea. It grew out of the daily needs of an engineer doing the work it is meant for. This page explains who builds it and why it works the way it does.

Mehmet Akyüz

Surveying Engineer · Software Developer

Graduate of Geomatics (Surveying) Engineering at Cumhuriyet University. Since 2016 he has worked as a chief surveyor on mining, dam and infrastructure projects, and still holds that role at a mining company.

His day-to-day work is monthly production volumes, stockpile measurement, pit and haul-road layout, cut and fill analysis, and the reporting that goes with them. STREAM was written for exactly this work — first for his own use, then for the people doing the same job.

He holds a commercial UAV pilot licence and a MAPEG Authorized Technical Personnel certificate, and works with drone- and LiDAR-derived DEMs, orthophotos and point clouds on his own projects every week.

Education and credentials

  • Geomatics (Surveying) Engineering — Cumhuriyet University
  • UAV-1 Commercial Drone Pilot Licence
  • MAPEG Authorized Technical Personnel (YTK) Certificate

Why STREAM exists

Drone and LiDAR data kept growing every year, but the workflow in the field stayed the same: wait for the DEM, orthophoto and point cloud from your photogrammetry software to open, switch to another program for volumes, another for cross-sections, then assemble the report by hand. Every hand-off risks a shifted coordinate system and a simplified surface.

STREAM was written to close the middle of that chain. It does not replace photogrammetry software — it takes its output. Open the DEM, orthophoto and LAS/LAZ files you produced in Pix4D, Agisoft Metashape or DJI Terra and turn them into engineering deliverables: volumes, quantity tables, cross-sections, analyses, drawings and reports.

Most design decisions come from the field. Stating in the report which reference a volume was computed against, making sure the section interval does not degrade the surface resolution, keeping data off the cloud — these exist because they are real problems in this work, not to lengthen a feature list.

Contact

Write in about anything you find missing, or would like added or fixed. The roadmap is largely shaped by the feedback that comes in.