GIS products. Interactive maps and the data pipelines behind them.

Contact

See the work

Land Owl

View Case Study

HVDC World transmission intelligence platform

Client Story

"I've worked alongside Micky for over 18 months building Land Owl, and he's genuinely excellent across many dimensions of software development. He understands GIS workflows at a level most people never reach, and turns messy, inconsistent jurisdictional data into something clean, reliable, and actually usable. He thinks like an entrepreneur and is someone I trust completely."

Sean Ingram

Co-Founder, Land Owl

how I work

The pipeline and the map are one system, not two. You work directly with the person building both.

From the data to the finished map.

Visa Map, an interactive world map of entry requirements

Maps for websites

An interactive map that belongs on your website. Show locations, explore a dataset or let visitors find what matters to them. Custom styling, search, filters and detail panels.

Talk it through

Internal tooling built for the Harcourts real-estate network

Internal mapping tools

A working view of your business data. Somewhere your team can find assets, inspect locations and work through decisions, with the database integrations and permissions behind it.

Talk it through

Map-based applications

A map at the centre of a product. I build the application around it: data ingestion, map performance, accounts and subscriptions, through to the screens your customers use.

Talk it through

DC Atlas, a data-centre intelligence platform

The pipeline underneath

Most of the work is getting the data usable and keeping it that way: ingest from APIs, exports and county records, then cleaning, reconciliation and scheduled refreshes.

Talk it through

Every project follows the same path. Scope first, data second, and nothing built before both are understood.

Scope

What the map needs to do, who uses it, and the data it has to handle. We agree on it before anything is built.

Data review

I take a real sample of your data and find out what is actually in it, so the pipeline is sized to the real mess, not the brochure.

Build

Pipeline and map built together, in working increments you can open and use. Something real early, refined from there.

Handover

Deployment, documentation and a refresh schedule that runs without me. You own the product and the data.

The stack. Picked per project, for the data and the budget.

Maps

Mapbox GL
When the product wants Mapbox styles, search and services.
MapLibre GL
The open-source renderer, with no per-load bill.

Tiles

Martin
Dynamic vector tiles served straight from Postgres, for data that changes.
Cloudflare R2
Large tile sets built ahead of time and served as static files.

Data and backend

Supabase and Postgres
The spatial database, auth and APIs behind the map.
Cloudflare Workers and D1
Edge APIs and lightweight data close to the user.
DigitalOcean
Servers for the jobs that need one: tile servers, pipelines, scheduled refreshes.

Work with me

Start the conversation

Tell me what you are trying to see.
Send the data, or just the problem.

Tell me about the project

Send the scope, a link to anything built, and a sample of your data.

Look at the work first

Case studies across property, energy, healthcare and infrastructure.

Have a map in mind?

Tell me about your project