GIS & Spatial Analysis
Spatial Data Foundations
Most organisations that use spatial data do not manage it. Layers accumulate on individual machines and shared drives, boundaries are edited locally and never reconciled, coordinate systems are mixed, and the version that gets used in a decision is whichever one the analyst had open. Nobody can say which boundary file is authoritative because none of them is.
The cost surfaces as irreproducible analysis and quiet disagreement between departments working from different geometry. Fixing it is unglamorous, a canonical store, coordinate discipline, topology validation, metadata and a governance model, and it is the thing that makes every subsequent piece of spatial work faster and defensible.
How the work runs
Four phases, and what comes out of each.
2 weeks
Audit what exists
We inventory the spatial layers actually in use, where they live, what they claim to represent, their coordinate system, currency and lineage, and identify where the same feature is represented differently in different places. This audit is usually uncomfortable and it is the whole basis for deciding what becomes authoritative.
Outputs
- Inventory of layers in use with lineage and currency
- Conflict register where the same feature differs across sources
- Coordinate system and topology issues catalogued
3–4 weeks
Establish the authoritative layers
For each core feature type one source becomes canonical, with a named owner and an update process. Geometry is cleaned, topology validated, coordinate systems standardised, and identifiers made stable so that a feature can be tracked across versions. Stable identifiers matter more than they appear to, without them, no history is possible.
Outputs
- Canonical layers with validated topology and stable identifiers
- Coordinate reference system standard with the reasoning documented
- Named ownership and an update process per layer
3–5 weeks
Build the store and the services
Data goes into a spatial database (PostGIS unless there is a specific reason otherwise) with versioning, and is served through open standards so any client can consume it. Open standards are the point: they are what allows you to change platform later without re-migrating everything, which is the trap most organisations are currently in.
Outputs
- Spatial database with versioning and access control
- OGC-compliant services so any client can consume the data
- Migration from existing files with validation against the source
2 weeks
Make the governance survive us
Infrastructure without governance reverts within a year, layers get copied out, edited locally and drift again. We put in the update workflow, the validation that runs on ingest, the metadata standard and the review cadence, then train the people who will run it.
Outputs
- Update workflow with automated validation on ingest
- Metadata standard and catalogue
- Governance model with named owners and a review cadence
What good looks like
The ranges we design toward.
3–9
Conflicting versions
Typical number of differing copies found for a core boundary layer during audit.
50–80%
Analysis preparation time
Reduction in effort spent finding, cleaning and reprojecting data before analysis can start.
0
Proprietary formats
Everything delivered in open formats through open standards. Changing platform later should not mean migrating again.
Deliverables
What you are left holding.
- 01Layer audit and conflict register, usually the most immediately useful artefact
- 02Canonical layers with validated topology, stable identifiers and named owners
- 03Spatial database and OGC services built on open standards, no lock-in
- 04Automated validation on ingest so quality does not decay after handover
- 05Governance model, metadata standard and trained operators
What an engagement looks like
A representative shape.
Illustrative. This is the shape of work in gis & spatial analysis, not an account of a specific client. We do not publish named results, and we would be wary of a firm that publishes them without the client in the room.
10 weeks
- 01Situation
A distribution business was assessing eight candidate locations using ten-kilometre radius catchments, and had recently opened two sites after which nearby existing sites declined without anyone having forecast it.
- 02What we did
Geocoded three years of transaction data to customer origin, built drive-time catchments calibrated against where customers demonstrably came from, and fitted a gravity model to allocate demand between competing sites.
- 03Where it landed
Modelled catchments were substantially smaller and differently shaped than the radii implied. Two candidates that had ranked highly on gross population fell sharply once cannibalisation was subtracted, and the ranking changed at the top.
Where this connects
Rarely a self-contained problem.
Questions
The ones we get asked.
We already have an Esri licence. Does this replace it?
Not necessarily, and we have no interest either way since we sell no licences. ArcGIS is a capable platform and if your team is productive in it, keep it. What we would change is the storage and interchange layer, so the authoritative data lives in an open format served over open standards, with ArcGIS as one client among several. That preserves your investment and removes the lock-in.
Which coordinate system should we standardise on?
Store in EPSG:4326 for interchange and analyse in an appropriate projected system, because area and distance calculations in geographic coordinates are wrong. For India that usually means the relevant UTM zone for local work, or a national projection for country-wide analysis. The important thing is that it is decided once, written down, and enforced on ingest rather than left to each analyst.
How long before this pays for itself?
The audit usually pays for the engagement on its own by surfacing conflicts that were producing wrong answers. Beyond that the return is in every subsequent piece of spatial work being faster and reproducible, which is real but diffuse. If you have no near-term spatial analysis planned, this is not urgent, do it alongside the first substantial project rather than as a standalone programme.
Can you work with Survey of India, Bhuvan and OpenStreetMap data?
Yes, and they have genuinely different licensing, currency and accuracy characteristics that need deciding on deliberately. OSM is excellent for road networks in urban India and uneven in rural areas; official sources are authoritative for administrative boundaries but often less current. We document which source is authoritative for which layer and why, rather than blending them silently.
Insights
Related reading.
Why a radius is not a catchment
Drawing a ten-kilometre circle takes ten seconds and is wrong in a specific, predictable direction. The lease it justifies runs a decade.
Cost-to-serve: the analysis most companies skip
Most businesses know their gross margin by customer. Rather fewer know which customers are profitable, and the two lists differ more than anyone expects.
Closely related
More on GIS & Spatial Analysis →Decision Maps
Maps that trigger a decision, in the browser, for the people doing the work, not another viewer nobody opens.
GIS & Spatial AnalysisSite Selection
Where to open, what it will draw, and what it will take from what you already have, modelled on travel time and real demand rather than a radius.
Start a conversation
Talk to us about spatial data foundations.
Most useful first conversations are thirty minutes and involve no proposal. Describe the problem you are looking at and we will tell you honestly whether it is one we can help with.
Or write directly to hello@shyenova.com
