Skip to content

Service 05 / Understand

GIS, mapping & spatial intelligence

Make geography and project information easier to explore, compare and act on through interactive maps and spatial applications.

Independent Somerleyton Living Estate study cover using estate aerial photography
Independent working studySomerleyton Living Estate ↗

The commission / an interactive walkthrough

See the work take shape.

Explore how this service moves from your starting information through a scoped build to testable acceptance and handover.

Your starting material

Gather the evidence.

We start with the users, records, constraints and decisions that the commission must respect.

  • 01Maps, plans, GIS layers or property schedules you can share
  • 02Source provenance, revisions and unresolved geometry questions
  • 03The journeys and decisions the spatial interface must support

Share a representative example with private records removed; detailed access follows an agreed secure process.

Specific deliverables, assurance and acceptance depend on the agreed brief.

Explore our delivery process ↗

Keep the information connected to its place.

01Place
02Record
03Evidence
Scope & deliverables

Where it fits

Applications & scope.

Local authorities, development projects, natural resources, estates and visitor experiences.

What we can deliver

  • 01Geospatial databases and interactive atlases
  • 02Planning, property and asset map interfaces
  • 03Masterplan and place-based visualisation
  • 04Evidence-linked records and spatial dashboards
Explore the system

System sketch / Illustrative spatial record model

Keep the information in place.

Inside / Locate

Establish the geographic reference, scale and source quality before presenting a place as precise.

Geometry
The spatial shape or location
Scale
The appropriate level of detail
Source
Provenance and precision

Illustrative service architecture. Detailed rules and responsibilities are agreed for each commission.

A resource registry needs more than a table ↗
Acceptance, QA & handover

A useful starting point

Bring the context.

  • Maps, plans, GIS layers or property schedules you can share
  • Source provenance, revisions and unresolved geometry questions
  • The journeys and decisions the spatial interface must support

Acceptance & handover

Agree what good means.

  • Record-to-map selection and source references
  • Scale, filters, navigation and narrow-device performance
  • Clear boundaries between supplied evidence and illustrative content

HandoverStructured spatial data, source references and documented map behaviour.

From requirements to operation

A complete commission, not an isolated build.

01 / Gather & shape

Establish the foundations.

Maps, plans, GIS layers or property schedules you can share. Source provenance, revisions and unresolved geometry questions. The journeys and decisions the spatial interface must support.

Strategy & discovery ↗
02 / Build & review

Make progress inspectable.

Implement the agreed scope in reviewable increments. Check user journeys, integration boundaries and failure conditions against the requirements, with unresolved decisions kept visible.

Review the delivery stages ↗
03 / Accept & hand over

Define what is ready.

Record-to-map selection and source references. Scale, filters, navigation and narrow-device performance. Clear boundaries between supplied evidence and illustrative content.

Structured spatial data, source references and documented map behaviour.

Evidence and scope are different.

Working examples and archive captures show their stated maturity. The service scope is a commissioning capability, not a claim that every listed system has been deployed for a client.

Independent Somerleyton Living Estate study cover using estate aerial photography

A related working example

Somerleyton Living Estate

A photographic estate atlas connecting places, stories, historic layers and an interactive garden walk.

Independent working study

Explore the project ↗

Before commissioning

The questions worth asking.

Discuss your requirements ↗
Can maps combine different sources and scales?

We review coordinate systems, data licences, provenance and update responsibilities before connecting layers. Survey accuracy, planning status and ownership are not inferred from a map or a concept model.

Can you work with our existing systems?

Yes, where access and integration are authorised. We first establish ownership, documentation, dependencies and the boundaries of any replacement or connection. A commission does not require abandoning a system that already works.

How do we agree the first release?

We prioritise complete user tasks rather than an arbitrary feature count. Scope, exclusions, dependencies and acceptance scenarios are agreed before implementation, with review points for changes.

How are security and personal data handled?

We identify data owners, information categories and permitted actions during discovery. Controls, retention, specialist assurance and any data-processing responsibilities are scoped against the actual service. A studio credential does not certify your future system.

What happens after handover?

Documentation, access ownership, training and operating responsibilities are agreed before release. Maintenance, incident coverage and further development have an explicit scope; they are not assumed to be unlimited.

The standard behind the work

Designed to be used.
Built to be owned.

Delivery & acceptance ↗
01

A clear decision trail

Scope, assumptions, dependencies and changes recorded against the brief.

02

Evidence before acceptance

User journeys, permissions, failure conditions and operating requirements reviewed before release.

03

Ownership beyond launch

Source, documentation, training and recovery responsibilities agreed as part of handover.

Credentials & project assurance ↗

Start a conversation

Tell us what needs to work.

Bring the brief, the source material and the constraints. We will help define the scope and the right next step.