Environmental systems scientist and geospatial analyst, working at the intersection of land, ecology, and code.
I prepare the spatial analysis behind impact assessments and planning procedures in Austria, then build the tools that work needs. What I hand over is reproducible, carries its own provenance, and opens without a server.
Practice
I work as a contractor for planning offices, consultancies and ecologists — getting the spatial data into a state the procedure can rely on. Usually a self-contained part of a larger project, with a defined scope and deliverable. German or English.
The remote-sensing baseline and field survey behind a habitat suitability assessment: forest-structure metrics per hectare, a survey project for the field, and the results worked back into the maps and figures the expert report cites.
Semi-automated revision of a municipal land-use plan — existing state balanced and cleaned, a working layer for the manual revision, then the before/after comparison. Delivered with a change atlas and an export that meets the state interface.
Condition monitoring from satellite time series, where one survey is not enough. Currently grazing pressure and heathland condition on a coastal Norwegian farm.
The deliverable
The analysis arrives as a single HTML file that opens by double-click. Switch between parameters, click a feature to see the values behind it, read the method alongside the map. No GIS, no install, no login, no server.
Everything is embedded, so it works with the network off and still opens years later.
The standard set comes with it: GeoPackage ready for analysis, CSV and XLSX tables, a QGIS project, a QField package for the survey, a PDF map atlas, an interface-conformant export where the procedure demands one, and a documented pipeline that re-runs.
Standards
Work that goes into a procedure has to survive being questioned, sometimes years later.
Reproducible — every result rebuilds from the inputs, with no undocumented manual step.
Traceable — each file carries its data reference date, code version and date of creation.
Self-contained — deliverables open without install, server or network.
Sparing with personal data — disclosed only as far as the recipient actually needs it.
Local — sensitive data is never sent to a hosted service, and no figure comes from a model.
Portable — standard formats throughout; nothing needs my code to be read.
Tools
Software I build because the work needed it and nothing on the market fit.
A collaborative outliner for small teams. One infinitely nested tree, tags that cut across it. No folders, no documents — just nodes. Runs the day-to-day of a working farm.
Photograph a shop front or a hiking guidepost, check the tags the app reads off it, upload them to OpenStreetMap. Recognition runs offline on the device.
A minimalist Android launcher and task manager. Tasks live across five time horizons, from Today to This Life, and sync between devices.
Ask your terminal a question in plain language, get the command back. Runs on local models.
A planning tool for commercial market gardens. Plan backwards from harvest dates, model capacity in bed-weeks, draw your beds on a map.
Draw a bounding box over a site, get a navigable 3-D scene from elevation and land-cover data, and watch decades of succession play out. An experiment in making land-use trade-offs arguable in a room.
Also around: distillery, self-hosted news synthesis · sentio, a load and recovery model built around farm work · odyssee, a writing companion · ideaNEXUS, a collective ideation platform [ideanexus.cloud].
About
Austrian by origin, trained in environmental systems science — my grounding is in spatial analysis, QGIS, and understanding how landscapes work. Over time that grew into Python, full-stack development, and building the kind of tools the field doesn't yet have. I run Arch Linux and carry that philosophy forward: composable parts, minimal dependencies, things you actually own and understand.
I've always thought in systems. I set the architecture and the standards the work is held to, and use AI to move faster through the execution. What stays mine is the judgement — what is correct, what holds up when a procedure is contested, and what a client can safely rely on.
The tools are mostly given away; if one has been useful, a coffee keeps me at it. Commissioned work is a separate conversation, and email is the right start for it.
Currently on the island of Lygra, Norway [on.lygra.no].
Contact