Data foundation
Public-source ingestion, normalisation and spatial persistence.
Independent product and engineering lab
Independent Real-Estate Intelligence & 3D Mapping
A public-data product exploring how cadastral, company, statistical and map information can support property research through 2D/3D views and structured workflows.
Context
Property research is fragmented across records, maps and manual notes.
The independent product brings together public-safe company-register, cadastral, statistical and geographic sources to support research around properties and ownership context.
It explores 2D and 3D map interaction alongside favourites, interest lists, scheduling and market-analysis workflows. Public-source licensing and exact ownership relationships remain explicit design constraints.
Problem
The difficult part is connecting evidence without inventing certainty.
Geospatial interfaces must remain responsive while preserving the distinction between a source record, a derived relationship and a user’s own research note.
- 01
Large cadastral and geospatial queries need bounded requests and database-aware aggregation.
- 02
Ownership navigation must not infer a unit owner from a parent parcel or building.
- 03
Research, favourites, scheduling and market views need a coherent product model around the map rather than a collection of disconnected layers.
Approach and solution
Make source provenance and spatial boundaries part of the architecture.
Public data is ingested and normalised into PostgreSQL/PostGIS, exposed through Fastify and Prisma, and presented through React and TypeScript with MapLibre and Leaflet.
The delivery approach prioritises bounded 3D queries, direct navigation from an owner to explicitly linked properties, and clear separation between verified source data and application-level research state.
Role and responsibility
Nik’s role: independent product, architecture and full-stack delivery.
Nik shapes the product workflows, data model, geospatial performance strategy, backend APIs and React/TypeScript interface.
The work connects technical investigation with product decisions about evidence, usability, performance and the responsible presentation of public records.
Architecture and delivery
Public data becomes a bounded research experience.
No live map tiles or property records appear in this public schematic.
- 01
Public sources
Company register · cadastral data · NSI · OpenStreetMap
- 02
Ingestion and normalisation
Source-aware parsing · validation · relationship handling
- 03
Spatial data layer
PostgreSQL · PostGIS · Prisma
- 04
Application API
Fastify · bounded queries · product workflows
- 05
Research interface
React · TypeScript · MapLibre · Leaflet · 2D/3D
Delivery
Current product scope.
Map experience
2D and bounded 3D property exploration with source-aware relationships.
Research workflows
Favourites, interest lists, scheduling and market-analysis concepts under active development.
Result and current status
A working independent research platform under active development.
The project demonstrates a real full-stack geospatial product and a disciplined approach to larger spatial datasets, public records and evidence-aware navigation.
It is not presented as a client engagement and makes no claim about customers, adoption, valuation accuracy or commercial results.
Ways to work together
Three clear ways to move a difficult system forward.
Choose the smallest engagement that can produce a useful decision and a credible delivery path.
- 01
Operational Systems Assessment
A paid, time-boxed discovery producing a process and data map, visible risks and priorities, an architecture and delivery roadmap, and pragmatic next steps.
- 02
Build & Delivery Leadership
Senior technical direction with hands-on implementation of critical paths, aligning owners, operations, product, suppliers and engineering from decision to release.
- 03
Fractional Technical Partner
Ongoing technical leadership for roadmap, supplier and team coordination, architecture choices and continuous delivery improvement.
Next step
Working with public records, maps or evidence-heavy workflows?
We can examine the data boundaries, performance risks and product decisions before committing to a larger implementation.