01
Assembling
Six transit feeds, a walk network, a population raster, an air network — found, licence-checked, reprojected, joined.
Liveability baseline for European SUMPs
Your SUMP diagnosis baseline — already built, measured, and sourced.
A fused 250 m picture of transit, heat, green and air for European cities, delivered in your formats — with every source, licence and disagreement published alongside.
Transit accessliveUrban heatdeliveredGreendeliveredAirdeliveredPopulationdelivered
Madrid · Access index (PTAL) · AM peaklive
PTAL 0 · least servicePTAL 6b · most service
Madrid · full municipal run
6,305populated cells
Every metric lands on the same 250 m cells, for the full municipal boundary.
CoverageAny EU city with a published GTFS feed
Lead time1 business day from go-ahead
Run so farMadrid — municipal boundary, 6,305 populated cells
Pan-European inputsCopernicus · Landsat 8/9 · GHS-POP R2023A
The job it removes
Every SUMP starts with weeks of assembling the same baseline by hand.
Accessibility, equity, the LEZ picture — rebuilt from scratch each project, from the same public sources, by the same senior people who should be writing the plan.
02
Reconciling
Two publications by the same operator disagree. Someone has to decide what the baseline says.
03
Re-explaining
Every committee asks where the number came from. The answer lives in a colleague's head.
What you get
One 250 m grid. Five layers. A re-weightable liveability picture.
A finished deliverable, in the formats you already work in — not a platform to learn.
Layer 1
Transit access
Walk time to frequent service, departures per hour, reachable population, a PTAL-style index and band.
- SourcesCRTM · EMT · Renfe GTFS
- Statuslive in the Madrid demo
Layer 2
Urban heat
Land surface temperature on the same cells, so a well-served district's heat penalty is visible beside its access score.
- SourcesLandsat 8/9 · Copernicus
- Statusdelivered in the baseline
Layer 3
Green & air
Green provision and the pollutant picture from the city's own monitoring network, gridded to the same cells.
- SourcesCopernicus · municipal AQ network
- Statusdelivered in the baseline
Layer 4
Population
Residents per cell, the denominator under every equity statement in the plan.
- SourceGHS-POP R2023A · JRC
- LicenceCC BY 4.0
Delivery
In your formats
GeoPackage into QGIS, styled plates for committee papers, a metrics CSV for the report, sourced headlines and a methodology note.
- ProjectionEPSG:3035
- Files.gpkg · .qml · .csv · .md
Not included
No platform to learn
No login for your team, no dashboard to maintain, no subscription to renew before the plan is finished.
- A deliverable, and the audit trail behind it.
Fusion
Transit can look fine while heat, air and green tell another story.
A district well served by frequent service can still be punished on heat and starved of green. Only the fused view puts both facts on the same cell — and lets you re-weight which one matters for this plan.
Re-weighting · a drawingillustrative, not measured
A drawing of how re-weighting moves cells. Not measured data — the live demo shows the measured transit layer.
3.80Mresidents
The denominator under every equity statement in the plan.
13metrics per cell
Walk times, departures per hour, reachable population, a PTAL-style index and band, and service flags.
Fits your workflow
It speaks to the jobs you are already billing for.
Not a platform to learn — a deliverable that drops into your QGIS and your committee papers.
Job 01
Baseline & diagnosis
The evidence base arrives finished; your senior time goes to the diagnosis itself.
- Output.gpkg · metrics .csv
Job 02
Equity assessment
Residents per cell under every access, heat and green figure, so distribution statements carry a denominator.
- Outputpopulation-weighted metrics
Job 03
LEZ appraisal
Air and transit on the same cells as the boundary you are appraising.
- Outputstyled plates · .qml
Job 04
Committee & public visuals
Plates styled to print, with the source line already on them.
- OutputA3 plates · sourced headlines
Glass box
How you can trust every number.
Every figure is sourced, dated and licensed. Where two publications by the same operator disagree, we publish the disagreement rather than the more flattering half.
33 / 41
Comparisons against the operators' own published timetables that fall inside their published frequency band.
8unresolved
Comparisons that fall outside the published band: 5 higher, 3 lower. Published, not omitted.
11checks
Quality checks recorded for the Madrid run, with what each one returned.
Sourced
Named official sources
Copernicus and Landsat for heat and green, CRTM/EMT/Renfe feeds for service, the city's own air-quality network, JRC GHS-POP for population.
- Attributionreproduced as each publisher words it
Dated
One service day, stated
Every figure describes scheduled service on one representative service day, named in the file. One feed's calendar had lapsed 63 days earlier; that is disclosed, never silently dropped.
- Service day2026-07-29 · termtime-2026
Consistent
The same method in Málaga as in Madrid
Pan-European inputs and one pipeline, so a second city is comparable with the first rather than a fresh set of local choices.
- Code versionea9436909834 · a digest, not a label
Domingos y festivos · Desde las 6:05 · 20 Minutos
What it costs
A fixed price per city, quoted in one email.
One invoice, no subscription, no per-seat licence. Four things set the figure — send the city and the scope and you have a number the same day.
City sizePopulated cells inside the boundary you work to.
LayersHow many of the five you want, and whether green and air are in scope.
WindowsOne representative service day, or several time windows.
OutputsData only, or data plus styled plates and committee visuals.
A city without a published GTFS feed is a different job — we will say so rather than quote for it.
See it live
The Madrid transit-access layer is deployed and open.
Thirteen metrics on 6,305 populated cells: walk time to frequent service, departures per hour, reachable population, PTAL band. The other layers are delivered in the baseline, not in this demo.
Madrid · Access index (PTAL) · 13 metrics · AM peaklive
PTAL 0 · least servicePTAL 6b · most service
About
Independent, and transparent by construction.
Spatial Spine is built by a data practitioner, not a platform vendor. The pipeline records its own code version as a digest, publishes its quality checks with what each one returned, and states what it does not measure.
41operator comparisons
Each with a source URL, a verbatim quote and a retrieval date — the reference set hash-pinned so it cannot be made to pass.
What it does not measure: whether services ran on time. No realtime feed, vehicle position or arrival observation is used anywhere in the dataset.
Request your city
Tell us the city and the boundary you work to.
We come back with what the baseline would contain, which sources cover it, and what it would cost. No signup, no trial.
Request a baseline
Opens your mail client, addressed to hello@spatialspine.com, with the three things we need already in the body.
We reply with what the baseline would contain · usually within two working days.
Next step
Request a baseline for your city
Send the city and the boundary. We reply with what the baseline would contain, the sources behind it, and the price.
A 30-minute call · no deck, no signup