Home / Spatial readiness audit
Free · three working daysBefore you build the screen, check the data can carry it.
Most spatial projects do not fail at the map. They fail because the layer behind it has no coordinate system anyone agrees on, an attribute field that means two different things in two teams, or a licence that forbids showing it to the client who paid for it. This audit finds that out in three days, in writing, before anyone opens an editor.
What you get
- A one-page verdict: ready, ready with caveats, or not ready
- Every layer checked for CRS, extent, refresh and licensing
- The three things that would block a client-facing map today
- What the interface can honestly claim, and what it must not
No charge, no obligation, yours to keep. If the answer is "your data is fine", that is what the report will say.
Six things that decide whether a map ships
Coordinate systems
Which CRS each layer is in, whether it is declared, and whether transforms are lossy. The commonest cause of a feature landing in the sea.
Attribution and meaning
Whether a field means the same thing to the team that fills it and the team that reads it. Status, condition, ownership and dates are where this bites.
Refresh and currency
How often the data changes, whether the interface can show when it last did, and what happens to a stale record.
Licensing and provenance
What may be displayed, to whom, and whether the source must be credited on the page. Derived layers inherit constraints.
Extent and gaps
Where the data stops. A viewer that silently shows nothing for half a county is worse than one that says so.
Evidence of change
Whether the data can support a claim of the form "before and after", and with what confidence.
This is a data and interface review, not a survey, an inspection or legal advice. It examines what you can share, at the level of detail needed to say whether a client-facing interface is possible.
Consultancies, surveyors and asset owners
If you have won a contract that includes spatial data and you are deciding what to build on top of it, this tells you what is safe to promise. If you are a utility or authority holding decades of layers from different suppliers, it tells you which ones can appear on a screen.
Typical engagements that start here: an asset and network dashboard, a viewer for LiDAR or Earth observation, or a monitoring page that has to show change over time with the source visible.
If you want it built
Asset and network dashboard
One operator screen: assets on a map, status, work order, history, filters, export. €5,900 fixed · four weeks.
Spatial data viewer
Survey or Earth-observation data made readable to a non-specialist, with provenance per layer. €2,900 fixed · three weeks.
Capacity inside your team
Senior front-end work in your backlog, your repository, your brand. €350 a day.
No deposit on any of them: invoiced when it works, or half on an accepted staging preview and half at handover. The code is handed over in your repository.
What people ask first
Why is it free?
Because it is the fastest way for both sides to find out whether there is anything worth doing. It also keeps me from quoting a build on data I have not seen.
What do you need from me?
Read access to the layers, or a sample export, and a sentence about who the interface is for. If licensing forbids sharing, a description and one anonymised extract is usually enough.
Do you sign an NDA?
Yes. A mutual NDA and a data-processing agreement covering UK and EU GDPR are provided before any file is transferred.
Will you tell me if it is a bad idea?
Yes. A written "do not build this yet, here is what to fix first" is a normal outcome and it costs nothing.
What the interface work looks like
Live C-ITS operator interface
Continuous V2X messages made usable for traffic operators: map, monitoring, practical workflows. Delivered in a live deployment at SWARCO.
Road-safety evidence app
Four datasets, two cities, Romanian county benchmarks, with provenance and limits visible in the interface. Open it and check the sources.
Agri platform at scale
77,490 producers, a directory, versioned agreements and a producer-facing map. Laravel and Vue.