Central Hub | Council Master Data View

CENTRAL HUB

Council Master Data View

A trusted, read-only view of approved Council information. The Hub is not another GIS map viewer — it explains the data behind the map, who owns it, how fresh it is, and where records disagree.

How this stands apart from MapThat

MapThat shows mapped data. Central Hub explains whether the data is connected, current, trusted and owned. The aim is not to replace the in-house GIS system. The Hub uses maps as evidence, but its main value is source ownership, record matching, freshness, confidence and correction at source.

GIS map viewerWhere is it?Shows layers, points, polygons, labels and map tools.

Central HubWhat is it?Shows the selected property, land parcel or asset and the records connected to it.

Central HubWho owns the data?Shows the responsible source owner and who must approve corrections.

Central HubCan we trust it?Shows source, refresh date, confidence, missing links and conflicts.

Central HubWhat needs fixing?Flags discrepancies and sends them back to the source-system owner.

Central HubWhy are records connected?Uses UPRN, address, title, asset ref, X/Y, geometry and service references as evidence.

Council Source Systems

Existing systems remain responsible
Illustrative demo figures — final counts subject to source-system confirmation

DMDynamic Maps1,178 spatial layers · View

LTLand Terrier2,486 ownership records · View

GFGeneral Fund / Property1,177 asset records · View

LRLand Registry2,486 title polygons · View

PLPlanning18,420 planning refs · View

FMFM / Facilities864 building records · View

HOHousing31,250 housing assets · View

HWHighways4,120 adopted assets · View

LLLLPG / Gazetteer128,600 UPRN records · View

GMGround Maintenance612 maintained sites · View

LELegal / Lease Data3,840 legal / lease links · View

GISGIS / Mapping Layers96 approved map layers · View

+Other approved systemsConnected by agreement · View

Central Data View

Connects, compares and explains

✓ Controlled, read-only access
No direct editing of source systems

MASTER PROPERTY / ASSET RECORD

Selected address, land parcel or operational asset

Record Matching UPRN · Address · Asset reference · Title number · Spatial location

SourceShows where each value came from

FreshnessLast refresh and status

ConflictsWhere systems disagree

Users and Outcomes

Role-based views and reporting

REPORTCorporate reporting and performance

MAPGIS mapping and spatial analysis

ASSETAsset management and planning

CHECKData quality and reconciliation

AUDITAudit, compliance and governance

M ManagersA AnalystsP PlannersO Operational teamsE Elected members

Key principles

Source ownershipEach service owns and corrects its source data

Read-only viewUsers cannot overwrite original records

Regular refreshEach source has an agreed refresh schedule

Visible differencesConflicting records are shown, not hidden

Controlled accessApproved data is shown according to user role

Works alongside GISThe Hub uses maps as evidence, but it does not replace MapThat or source systems

Total assets0Current records

UPRN linked0%Address match

Title linked0%LR title present

Open requests0Correction workflow

Recent correction workflow

Data quality summary

Core demo flow

1Search / select assetFind by map, address, UPRN, title, asset ref or other approved identifier.

2Open Master RecordSee the property, land parcel or operational asset at the centre.

3Compare source recordsView connected records from services such as GF, Land Terrier, LLPG, LR, Housing, FM and Legal.

4Show source and freshnessSee where the data came from, who owns it and when it was refreshed.

5Flag conflictsShow missing, different or uncertain records rather than hiding them.

6Correct at sourceSend discrepancies to the data owner, then refresh the Hub after sign-off.

Map View

Map background

Drawing tools ready

Click points for linked records. The map is used as evidence to understand location and relationships; the Master Record explains source, owner, freshness and conflicts.

This is not trying to be another MapThat. The map supports the Central Hub by showing location evidence. The real value is the connected record, source owner, refresh status and correction route.

Connected Map Evidence

Shows how source records can be connected by location, overlap, UPRN, references and map evidence. If no record is loaded yet, the button will create one demo evidence record.

Select an asset on the map to see connection evidence.

Important: Location helps connect records, but the map is evidence — not final proof. The source owner still confirms whether the connection is correct.

Capture results

Capture checks uploaded asset coordinates. It only captures points from layers that are switched on in Layer Manager.

No captured records yet.

Layer manager

Layers are grouped by service area and start closed. Click the arrow or group heading to open each group. Point clusters are enabled, so overlapping points or zoomed-out points can show a count. Each layer shows its source owner, record count, icon and colour. Use sample points to test layers that do not yet have data.

Click an asset or map marker.

Master Property / Asset Record

Selected property, land parcel or operational assetSearch or import records, then compare source values, freshness, confidence and owner responsibility. Records are grouped by service/layer and start closed so the view is easier to read. Click a group heading to open it.

Need live SQL data?Use the SQL Connection page to show the safe API/middleware route into a SQL reporting view.

Upload Excel X/Y

Import spatial file

Import KML or GeoJSON directly. Imports default to Uploaded Data, not General Fund / Property. For Shapefile, upload a .zip containing the .shp, .shx, .dbf and .prj files. Shapefile import needs the online shpjs library to load.

Spatial file Import into layer Or create new layer Spatial colour Fill / marker opacity KML geometry detail

Choose a KML, GeoJSON or zipped shapefile. Popup bubbles show name, description, geometry, coordinates and available attributes. The spatial colour now applies to both polygon outline and polygon fill. Large KML files are simplified by default so browser storage is not exceeded.

Asset ID	Address	Layer	UPRN	Title	Service	Confidence	Action owner	Status

SQL Connection

LIVE DATA ROUTE This shows how the Master Property / Asset Record would connect to SQL.

The safe design is browser → approved API / middleware → SQL reporting view. This avoids putting SQL credentials in the app.

SQL Database Connection

For a live version, the browser should not connect directly to SQL Server. It should connect to an approved API or reporting view, and that service connects securely to SQL.

Not connected

Central Hub screenRead-only user view

→

Approved API / middlewareSecurity, permissions, audit

→

SQL reporting viewApproved data from source systems

Configure SQL/API connection for this prototype

API endpoint / middleware URL Database / reporting view name Primary lookup key Selected lookup value Refresh frequency Connection owner

No SQL/API connection settings saved yet.

Generated query will show here.

Important: Do not store SQL passwords or direct database credentials in this browser prototype. The proper live route is browser → approved API → SQL/reporting database, with permissions and audit logging.

Source Contacts & Updates

DATA OWNERSHIP REGISTER This page shows who owns each source system and when the information was last reviewed.

The Central Hub can show linked data, but the source owner remains responsible for correcting and approving their own records.

Source ownership and contact details

Source contacts are grouped like the Layer Manager and start closed. Open each group to update owner, email, telephone, review date and status. These details are stored in this browser for the prototype.

Why this matters

Clear responsibilityEveryone can see which team owns the source record.

Faster correctionIssues can be routed to the right officer or service area.

Trusted reportingManagement can see whether source details are current or need review.

No hidden changesThe Hub should show and explain differences, not silently overwrite source systems.

Data Accuracy & Ownership Responsibility

DATA FIRST The data is the most important thing.

The map, dashboards and reports are only as reliable as the source data behind them. Good data must be owned, checked and signed off by the correct service owner.

Key message

The map displays the data. The data owner confirms whether the data is correct.

What the data owner is responsible for

AccuracyConfirming whether the record is correct, current and complete.

MeaningExplaining what the record actually represents: land, building, flat, garage, lease, title or service responsibility.

Ownership / responsibilityConfirming who owns, manages or is responsible for the asset or record.

Sign-offApproving changes before they are published or refreshed into the Hub.

What the GIS / mapping team is responsible for

Publishing approved dataDisplaying the data supplied or approved by the source owner.

Map location and projectionMaking sure coordinates, layers and map display work correctly.

Presentation with owner agreementShowing layers, labels, popups, colours and visibility in a usable way, with the data owner agreeing how the data should be displayed.

Colour and symbol sign-offMap colours and symbols can change the meaning of the data. For example, blue may suggest water and green may suggest land or open space, so styling should be agreed and signed off by the data owner.

Flagging possible issuesRaising suspected problems back to the data owner for review.

LINKING WITHOUT A UPRN

X/Y coordinates can provide spatial evidence

The Central Hub does not always need a UPRN to find a possible connection. If a source record contains X and Y coordinates, the Hub can place it on the map and check which property or land boundary it falls within.

For example, an FM record may not have a UPRN, but its coordinates may fall inside a General Fund asset polygon. The Hub can then show that the records are likely to relate to the same location.

This is recorded as a spatial match, not an automatically confirmed match. The evidence shows whether the point is inside the boundary, its distance from the boundary and the confidence of the connection. A data owner can then review and confirm it where necessary.

Especially useful for: land, garages, open spaces and other assets without a normal postal address or UPRN. UPRNs are still used where available; X/Y gives the Hub another reliable way to find possible links.

KEY PRINCIPLE Location finds the possible link. The data owner confirms it.

See how an X/Y spatial match works

Choose a scenario to see the evidence and the action the Hub should take.

1

Place the recordUse its X and Y coordinates.

2

Compare boundariesCheck containment, distance and competing candidates.

3

Record the evidenceThe point falls inside one asset boundary.

HIGH-CONFIDENCE SPATIAL MATCH Show as a likely connection

The Hub proposes the link and keeps the matching method visible. The source owner reviews and confirms it where required.

Correct change process

1Issue spottedSomeone notices a possible problem or inconsistency.

→

2Owner reviewsThe responsible data owner checks the background and meaning.

→

3Owner signs offThe source owner approves the correction or confirms no change is needed.

→

4GIS publishesThe approved data is displayed or refreshed on the map.

Why this matters

Some records may look wrong, incomplete or unusual for a valid reason. Ownership history, legal records, leases, maintenance responsibility, estate boundaries and service decisions can all affect what the data means.

Changes should not be made just because something appears wrong on a map. The source owner must confirm the reason and approve any change first.

Map Display Sign-off

How the data is displayed can change how people understand it. Colours, symbols, labels and layer names should be agreed with the source data owner before publishing.

BlueCould be understood as water, drainage or river-related land.

GreenCould be understood as land, open space, parks or environmental areas.

RedCould be understood as a warning, conflict, risk or urgent issue.

Boundary styleA solid line may imply confirmed ownership, while a dashed line may imply indicative or needs review.

The GIS / mapping team should publish the agreed map display, but the data owner should sign off the meaning, colours and classification before it is treated as approved.

Simple rule

DoFlag possible issues to the data owner.

DoKeep evidence of who confirmed the change.

Do notChange ownership, classification, legal status or responsibility without source-owner sign-off.

Do notAssume an address or map position proves the business data is wrong.

Map Layers & Data Freshness

SIMPLE GIS GUIDE A map layer is not automatically live, current or correct.

This page explains the basic types of GIS layers, common file formats, and the difference between live data and snapshot data.

Simple picture guide

Map Layers and Data Freshness simple guide

1. What type of map layer is it?

Point layerOne location, such as a building, garage or asset point.

Line layerA route or boundary line, such as a road, path, pipe or red line.

Polygon layerAn area or boundary, such as land, estate, title extent or maintenance area.

Image / raster layerA background image, such as aerial photography or a scanned plan.

Table-only dataData with no map shape yet. It may need X/Y, lat/long or a boundary before it can be mapped.

2. What format is it stored in?

Shapefile / SHPA file format. It can hold points, lines or polygons.

KML / GeoJSONWeb-friendly map files.

Excel / CSV with X,YA spreadsheet that can become map points if the coordinates are reliable.

Database layerA layer coming from a live or managed database.

WMS / tile layerA display layer. It may look like data, but is often just an image service.

3. Is the data live or a snapshot?

Live dataConnected to a source system and refreshed automatically or on an agreed schedule.

Snapshot dataA copy taken on a certain date. It may have been correct when exported, but it can go out of date.

Archived dataOld data kept for history or evidence. It should not be treated as the current position.

Unknown / unmaintainedNo clear owner or update process. This is high risk.

Key message

A layer on a map is not automatically live or correct.

Before relying on it, we need to know who owns it, when it was last updated, whether it is live or a snapshot, and whether the source owner has signed it off.

How Records Connect

SIMPLE MANAGEMENT VIEW The Hub does not connect records just because the address looks the same.

It looks for stronger proof that two records are talking about the same property, land, building, garage or legal record.

The simple version

1 A source system has a record For example: General Fund, Land Terrier, LLPG, FM, Housing, Garages, Land Registry or Legal.

2 The Hub looks for proof It checks links such as UPRN, asset ref, title number, X/Y, map boundary or service reference.

3 The Hub shows the result It shows whether the record is connected, partly connected, possible, missing, conflict or needs review.

Why address is not enough

One address can mean different things

10 Example Road could mean the whole building, one flat, a garage block, a piece of land, a maintenance area, or a legal title.

So the address helps us search, but it does not prove the records are the same thing.

Better proof of connection

UPRNBest for official address/property matching.

Asset referenceBest for Council property/land records.

Title numberBest for Land Registry / legal evidence.

X/Y or map boundaryBest for checking where something is on the map.

FM / Garage / Legal refBest for linking service records back to the asset.

What management needs to know

ConnectedStrong links agree.

Partly connectedSome links exist, but not enough to be fully trusted.

Possible matchLooks likely, but needs checking.

ConflictSystems disagree or the map location does not fit.

Needs reviewSend back to the source owner to fix or confirm.

The key message

The Central Hub is not guessing. It shows the evidence for each connection and highlights where Council source data needs to be confirmed, corrected or improved.

Record Matching & Data Conflicts

MASTER LINK INDEX The controlled cross-reference layer that explains how records connect.

It checks UPRN, address, title, asset reference, X/Y, lat-long, geometry overlap and service references such as FM, Housing, Garage and Legal refs.

Why an address is not enough

An address is a good starting point, but it does not always prove two records are the same asset.

Different Council systems may use the same address to mean different things. The Central Hub should show this clearly instead of joining records together just because the wording looks similar.

Simple example

10 Example Road

System AWhole building

System BOne flat

System CLand behind the building

System DMaintenance area

These records may all show the same address, but they are not necessarily the same asset.

Better linksUPRN, asset reference, title number, garage reference, FM reference, legal/lease reference, X/Y coordinate and map boundary.

What the Hub doesIt checks how strong the connection is before showing records as linked.

When links are missingIt does not guess. It marks the record as missing, partly connected, possible match, conflict or needs review.

Connection Readiness / Unlinked Sources

Some source systems cannot be fully connected until they contain a reliable common key. This helps management see where source data needs improving.

Source system	Link status	Missing or weak key	Plain English explanation	Possible fix	Owner
FM database	Partly connected	No UPRN / weak address link	FM may know the building, but not the exact Council asset record.	Match by building ref, address, UPRN or X/Y.	FM / Facilities
Legal leases	Partly connected	No UPRN or map boundary	Legal may hold a lease or title reference but not a clean map link.	Link by title number, lease ref, address and polygon.	Legal / Property
Legacy plans	Not linked yet	No coordinates	A scanned plan may show land, but the Hub cannot place it on the map until it is digitised.	Georeference plan and create polygon.	John Roberts
Garages	Partly connected	Missing UPRN / mixed addresses	A garage site may not have a normal property address.	Link by garage ref, asset ref, site address or geometry.	John Roberts
Housing records	Possible match	Different address wording	Housing may describe flats, blocks or estates differently to LLPG/SNN.	Check parent/child property relationship and UPRN.	Housing / SNN
Old asset spreadsheets	Needs review	No unique ID	A spreadsheet may have a useful description but no reliable key to prove the match.	Create asset reference and match manually.	Source owner

Master Link Index flow

Council Source Systems LLPG/SNN · Land Terrier · General Fund · Land Registry · FM · Housing · Garages · Legal · GIS

→

Master Link Index Cross-reference checks, match confidence and conflict flags

→

Master Property / Asset Record One selected record with source, owner, freshness and evidence

Connection checks

Connection method	Status	Evidence	Owner

Conflict summary

How references can connect through source systems

FM RefFM Ref → FM database → building ref / address / UPRN / X,Y → Master Link Index

UPRNUPRN → LLPG/SNN → official address / BLPU / parent-child relationship

Title numberTitle → Land Registry → registered extent / tenure / legal evidence

Asset RefAsset Ref → General Fund / Land Terrier / Dynamic Maps → asset geometry and ownership interest

X/Y and Lat-longBritish National Grid X/Y → WGS84 lat-long → map display and geometry overlap check

Garage RefGarage Ref → garages layer → site address / asset ref / geometry / operational status

Lease / legal refLease ref → Legal → title, rights, access, responsibility and restrictions

Connection Path Explorer

PLAIN ENGLISH CONNECTION VIEW Show the route a record uses to connect back to a source database.

This page explains why a record is connected, what key was used, and where the link may be weak or missing.

Connection route

Path used to connect

Why this connection is used

What could be wrong

Common connection routes

UPRNBest address/property key when present. Links LLPG, SNN, Housing and some FM records.

X/Y coordinateUseful when there is no clean ID. Checks where the record sits on the map.

Lat/longUsed by the web map. Usually converted from British National Grid X/Y.

AddressUseful for searching, but not strong enough by itself to prove records are the same asset.

Title numberConnects to Land Registry and legal ownership evidence.

FM / Garage / Legal refsConnect to service databases, then return stronger keys such as UPRN, X/Y, address or asset reference.

Data Flow & Transformation Map

TECHNICAL VIEW How source records are transformed, matched and checked before they appear in the Central Hub.

This is a simplified FME-style view. It shows the main routes into the Master Link Index, where data may be transformed, and where missing or conflicting values are flagged.

Connection flow

Source systems

LLPG / SNNUPRN · official address · parent/child

Land TerrierAsset ref · ownership · land geometry

General FundAsset ref · finance status

Land RegistryTitle number · title extent

FM / FacilitiesFM ref · building ref · address · X/Y

GaragesGarage ref · address · geometry

Housing / LegalHousing ref · lease ref · responsibility

Extract and transform

Extract keysUPRN · address · title · asset ref · FM ref

Clean address textNormalise aliases, flats, buildings and postcodes

Coordinate conversionBritish National Grid X/Y → WGS84 lat/long

Geometry checkPoint-in-polygon · overlap · nearest feature

Source freshnessRefresh date · record count · failed records

Master Link Index

Controlled cross-reference layerStores how records connect, why they connect, and how strong each match is.

UPRNAddressTitleAsset RefFM RefGarage RefX/YLat/LongGeometry

Outputs

Master Property / Asset RecordJoined view with owner, source and freshness

Map ViewPoints, polygons, basemaps and linked bubbles

Conflict flagValues disagree or sit outside expected geometry

Needs reviewMissing, uncertain or low-confidence match

Key transformation routes

FM Ref routeFM Ref → FM database → building/address/UPRN/X,Y → Master Link IndexUseful where the FM record has a local building reference but no asset reference.

Address routeAddress → address normalisation → LLPG/SNN → UPRN and parent/child checkUseful where records use different flat/building wording.

Coordinate routeX/Y → coordinate conversion → lat/long → map view and spatial checksUseful where records have coordinates but no strong identifier.

Geometry routePolygon/point → overlap/containment check → likely parcel/title/assetUseful where title or asset reference is missing.

Title routeTitle number → Land Registry → registered extent → ownership/legal evidenceUseful where Council ownership needs evidence.

Where the flow can fail

ConflictUPRN matches but address text differs between systems.

Spatial conflictX/Y point falls outside the expected asset or title polygon.

Missing linkFM/Housing/Garage reference is not present in the selected record.

Low confidenceAddress is similar but not exact, or geometry overlap is partial.

ConfirmedUPRN, address, geometry and source references agree.

Manager-friendly message

The Hub does not just join records because they have the same address. It checks stronger links first, shows where the link is weak, and routes missing or conflicting information back to the source owner.

Simple rule example

1. Strong matchUPRN + address + coordinate all agreeStatus: Confirmed

2. Spatial supportX/Y falls inside Land Terrier or title polygonStatus: Likely / Confirmed

3. Weak matchOnly address text is similarStatus: Needs review

4. ConflictSource systems disagree or geometry does not alignStatus: Conflict

Discrepancies and Data Quality Checks

The Hub should not invent one final answer.It should show disagreement between systems and route the issue back to the responsible source-system owner.

Source ownership matrix

Data item	Source of truth	Owner

Issue owner / action routing

Issue	Action owner	Action

Report discrepancy / correction form

Asset IDIssue typePriorityRoute to ownerDescriptionEvidence / notes

Open correction requests

Before: manual checking

Check Dynamic Maps / GIS layer.
Search Land Terrier / GF records.
Check LLPG / SNN for UPRN/address.
Check Land Registry separately.
Ask FM, Housing or Legal for extra records.
Manually decide whether records match.

After: Data Views

Click one asset or map point.
Index checks Asset ID, UPRN, address and title.
Linked records display together.
Confidence, source of truth and action owner shown.
Issue routed to correct data owner.
Audit trail records changes.

Live system warning: this prototype runs in-browser. A live version needs approved infrastructure, security and data owner sign-off.

Database

SQL Server / Azure SQL
Spatial geometry support
Master Asset Index
Audit/refresh tables

Data feeds

Read-only source views
FME / SQL jobs / APIs
Approved field lists
Refresh schedules

Security

Role-based access
Restricted legal/housing fields
Internal hosting
Audit logging

GIS

Real polygons
Coordinate points
Layer manager
MapThat/OpenLayers/Leaflet

Help / Guidance

SUPPORTING EXPLANATIONS The main demo stays focused on the Master Property / Asset Record.

These pages are useful for explaining the background, but they sit behind the main workflow so the app does not feel like a training manual.

Supporting pages

Main demo message

One selected asset. Connected source records. Visible owner, source, freshness and conflicts. The map supports the evidence, but corrections go back to the responsible source owner.

Settings / Import

Import JSON backup

This prototype stores records in localStorage. Use backup/import to move test data between browsers.

Excel X/Y upload format
Upload .xlsx, .xls or .csv. You choose the coordinate system during upload. Use EPSG:27700 for Easting/Northing, or WGS84 for Longitude/Latitude.