Currently Empty: $0
Innovation
Spatial capability for land management
and master planning
The same question comes up on every land and planning programme: what can we actually do with the data we have, and what has to be true before we can do it. This section groups the catalogue by that capability rather than by product type.
- Capabilities
- 7
- Resources mapped
- 31
- Combined value
- $16,329
- Delivery
- Instant
How this is organised
Land management and master planning work runs in a rough sequence: establish the land record, capture current ground truth, analyse what the land can support, plan and model it, coordinate the infrastructure, and govern the data throughout. The seven capabilities below follow that sequence. Most programmes are strong in two or three of them and discover the gaps late.
01
Land information foundation
The base records everything else is measured against. Parcels, addresses and protected areas have to be authoritative before any plan drawn on top of them can be defended.
02
Survey & basemap capture
Getting current ground truth at the right resolution — and knowing which capture method actually answers the question before commissioning it.
03
Site analysis & suitability
Turning constraints and opportunity into a defensible allocation decision, with the weighting written down rather than argued from intuition.
04
Master planning & 3D city
Moving from a two-dimensional land use plan to a modelled, coordinated city — including the BIM handover that most programmes discover too late.
05
Infrastructure & networks
The utility, transport and subsurface networks a master plan has to coordinate with, model as networks, and hand over as assets.
06
Standards & governance
What makes a multi-consultant programme produce one coherent dataset instead of a dozen incompatible ones delivered on the same day.
07
Applied GeoAI
Where automation genuinely pays on land and planning work — change detection and feature extraction at scale — and how to evaluate it honestly before committing.
Applications
Six products on one engine
The same methods, running as software. One engine underneath all six — which is why the second product costs a fraction of the first. Each takes a LiDAR pass where one has been flown.
GeoFarm
Every field, every season, on one page.
Satellite indices are read per field block rather than per scene, so performance is comparable between blocks and between seasons. Water drawn is set against the entitlement for that block, which turns an agronomy conversation into a compliance one.
With a LiDAR pass Wetness and depth-to-water show where the water actually goes; two surveys give land-levelling volumes. An anomaly stops being a fact and becomes a cause. What that involves →
How it works — the workflow, the tools, a worked example
The workflow
Tools it runs
Raster indices Zonal summarise Change detection Attribute rules Graduated symbology ModelBuilder Reports
Worked example — One estate, three seasons
An agricultural investor holds roughly 240 irrigation blocks and suspects a handful are carrying the rest. Nobody can say which, because performance has only ever been discussed per farm.
The result: The conversation moves from an agronomy debate to a compliance list of four blocks, with three seasons of evidence behind each. The field visit is targeted rather than general.
Illustrative figures on a representative problem, not a client delivery — these products are in development, and a pilot is where the first real numbers come from.
Pilot $12,000 – $24,000 One estate, three seasons, 8 weeks, fixed scope and price
GeoSite
Proof that the work was actually done.
Field staff capture on a phone with no signal and sync later. Every photograph carries its own position, and every claim carries the evidence behind it, so a progress dispute is settled with a record rather than a meeting.
With a LiDAR pass Two flights give earthwork volumes per period, measured off the ground. A claim for 40,000 cubic metres is checked, not negotiated. What that involves →
How it works — the workflow, the tools, a worked example
The workflow
Tools it runs
Mobile packages Offline sync Domains and subtypes Attribute rules Select by location Archiving Reports
Worked example — One programme, one valuation period
A PMO receives a monthly valuation listing roughly 1,400 completed activities. Verification today is a site walk by whoever is available, covering perhaps 5% of them.
The result: The valuation meeting starts from a list of sixty-one specific exceptions with photographs attached, instead of a general disagreement about progress. The remaining claims are evidenced and pass without argument.
Illustrative figures on a representative problem, not a client delivery — these products are in development, and a pilot is where the first real numbers come from.
Pilot $9,000 – $18,000 One programme, 6 weeks, fixed scope and price
GeoGrid
See who loses service the moment an asset fails.
The network is traced rather than drawn: break any asset and the system returns what is downstream of it, which customers are affected, and which crew is closest. The same trace supports planned shutdowns, which is where most of the value sits.
With a LiDAR pass Canopy height along the line gives a clearance breach per span, ranked — a prioritised trim list instead of a blanket cycle. What that involves →
How it works — the workflow, the tools, a worked example
The workflow
Tools it runs
Network connectivity Topology rules Downstream trace Shortest path Summarize Within Linked maps OGC API Features
Worked example — One district, one failed valve
A water utility learns which customers are affected by an outage when those customers telephone. The network exists as geometry; nothing downstream can be computed from it.
The result: The affected-customer list exists before the first call arrives, and the same trace drives a planned-shutdown notice — which is where most of the value sits, because planned work happens far more often than failure.
Illustrative figures on a representative problem, not a client delivery — these products are in development, and a pilot is where the first real numbers come from.
Pilot $18,000 – $36,000 One network or district, 10–12 weeks, fixed scope and price
GeoGreen
Proof that what you planted is still alive.
Canopy is compared between two dates and reported as a survival rate per block, against the planting record and what was paid for it. The output is a replanting list and a figure a programme can report without qualifying it.
With a LiDAR pass Trees counted individually, not inferred from a pixel too coarse to see a sapling. Two dates give survival per block and growth per tree. What that involves →
How it works — the workflow, the tools, a worked example
The workflow
Tools it runs
Canopy height models Tree detection Change detection Zonal summarise Whitebox LiDAR Attribute rules Map series
Worked example — One greening programme, two seasons on
A programme planted roughly 180,000 trees across 60 blocks. Survival is currently reported as a single percentage, estimated from spot checks, and nobody can defend it.
The result: The programme reports a survival figure it can defend, holds a maintenance contractor to nine specific blocks, and has a replanting list by location rather than a budget line called replanting.
Illustrative figures on a representative problem, not a client delivery — these products are in development, and a pilot is where the first real numbers come from.
Pilot $12,000 – $24,000 One programme, two dates, 8 weeks, fixed scope and price
GeoRisk
Know which plots flood before you sell them.
Terrain and published or modelled flood extents are held against the plot register, so exposure is a property of each plot rather than a map someone has to interpret. It answers the question a buyer, a lender and an insurer all ask separately.
With a LiDAR pass A 30 m global DEM screens a scheme; a half-metre surface names the plots. Exposure in the form a lender or an insurer will accept. What that involves →
How it works — the workflow, the tools, a worked example
The workflow
Tools it runs
LAS LAZ COPC Fill and flow Wetness and depth Select by location Suitability modelling Attribute rules Map series and PDF
Worked example — One scheme, before the plots are sold
A master developer holds a scheme of roughly 2,400 plots. Flood exposure is currently assessed against a 30 m global elevation model, which is a screening tool and is being used as an answer.
The result: Exposure becomes a property of each plot, in the form a lender, an insurer and a buyer will each accept — and the two plots under offer are caught before completion rather than after.
Illustrative figures on a representative problem, not a client delivery — these products are in development, and a pilot is where the first real numbers come from.
Pilot $15,000 – $30,000 One scheme, 8–10 weeks, fixed scope and price
GeoRoute
Three routes, priced and compared, in one afternoon.
Constraints become a cost surface, and the surface produces alignments rather than opinions. Each option carries its own land take, so the engineering choice and the acquisition bill are seen together instead of a year apart.
With a LiDAR pass Slope, curvature and wetness make the cost surface honest. Each option carries its own earthworks and clearance bill, not just a length. What that involves →
How it works — the workflow, the tools, a worked example
The workflow
Tools it runs
Suitability modelling Least-cost path Viewshed Buffer clip erase Summary statistics Terrain volumes Linked maps
Worked example — One corridor, three options, one afternoon
An infrastructure programme needs a route between two fixed points roughly 42 km apart. Today the engineering choice is made first and the land acquisition bill arrives a year later.
The result: The engineering choice and the acquisition bill are seen together, in the same review, rather than a year apart — and the option that looked cheapest on length is not the one that is recommended.
Illustrative figures on a representative problem, not a client delivery — these products are in development, and a pilot is where the first real numbers come from.
Pilot $18,000 – $36,000 One corridor, 10–12 weeks, fixed scope and price
The engine
What all of this is built on
All of it runs on RustGIS — open source, written in Rust, Apache-2.0. Three reasons it matters.
It already runs in a browser
Compiled to WebAssembly: the same application runs natively and in a browser tab, nothing to install. The delivery model these products need.
It edits like a land record, not like a drawing
Snapping and templates, topology rules, domains, subtypes, attribute rules, relationships, archiving, and undo for everything. Archiving is the one that matters for tenure: superseded geometry is retained rather than overwritten, so a boundary history stays reconstructable.
It reaches the analysis without rebuilding it
Over 1,000 GeoLibre and Whitebox tools for terrain, hydrology, LiDAR and remote sensing, plus suitability modelling, shortest path, viewshed, raster change detection and pixel classification — the raw material behind GeoRoute, GeoRisk, GeoGreen and GeoFarm.
| What a product needs | What the engine already does |
|---|---|
| Your data, unmoved | GeoPackage, GeoParquet, FlatGeobuf, Shapefile, GeoJSON, DXF, OSM PBF, PMTiles and MBTiles; GeoTIFF and cloud-optimised GeoTIFF; live PostGIS, MySQL and MariaDB; DuckDB Spatial |
| Point clouds | LAS, LAZ and COPC read in place, with the Whitebox and GeoLibre LiDAR, terrain and hydrology tool sets |
| Field work | Mobile map packages and offline areas with sync — what GeoSite needs to capture with no signal and reconcile later |
| Evidence that survives | Archiving, relationships and attribute rules, so a number can be defended months later by somebody who was not there |
| Repeatability | Every action is a command with an id, scriptable from the command line, ModelBuilder or a notebook — so a method is a file, not a habit |
| Room for our own logic | Sandboxed WebAssembly plugins add commands, tools and ribbon tabs, which is where the land rules and the rest of the family live |
| Regional delivery | Sixteen interface languages, any EPSG projection, and five offline basemaps |
Licence: RustGIS is Apache-2.0 — permissive, so it can sit inside a licensed product. A copyleft foundation would oblige us to publish our own source. The GeoLibre and Whitebox collections it reaches carry their own licences, checked per tool.
Added capability
What a LiDAR pass adds to every one of them
Most clients have already bought the survey. The terrain model was used once and the point cloud went into an archive — with everything below still in it.
| From the pass | What it is | What it lets you decide |
|---|---|---|
| Ground classification | Every point separated into ground and not-ground, across aircraft, drone and tripod surveys, without a specialist retuning the parameters per site. | This is the step that makes a survey cost what it costs. Automating it is what makes everything below repeatable. |
| Bare-earth terrain | A terrain surface at the resolution you ask for, with the buildings, vegetation and plant taken off it. | Turns a plot boundary into a plot with a gradient, a buildable area and a cut-and-fill figure. |
| Surface model | The top of everything — roofs, canopy, stockpiles, plant. | Subtract the terrain and you have the height of every object on site, including the ones nobody recorded. |
| Height-normalised cloud | Every point re-expressed as its height above the ground directly beneath it. | Makes heights comparable across a sloping site, which is the precondition for counting or measuring anything on it. |
| Canopy height | Canopy surfaces by ten different methods, including pit-free and spike-resistant processing. | Vegetation stops being a green area on a map and becomes a height you can put a clearance or a biomass figure against. |
| Terrain derivatives | Slope, aspect, curvature, hillshade, topographic position, wetness index, depth to water, terrain characterisation. | The constraint layers a route, a drainage design or an erosion case is argued from — derived, not digitised. |
| Structure metrics | Canopy cover, mean and maximum height, height variability, foliage height diversity, vertical complexity, point density. | What an environmental regulator or an ESG report actually wants: habitat quality and fuel load, with numbers behind them. |
| Individual trees | Treetops detected and crowns delineated, with the points belonging to each tree extracted as its own record. | Pay per surviving tree, inspect per tree, value per tree. An inventory instead of an estimate. |
| Change between dates | Any two compatible surveys compared — terrain, surface or canopy — with a level-of-detection threshold so noise is not reported as movement. | Volumes moved, ground subsided, canopy gained or lost, each with a defensible statement of what counts as real. |
| Large areas | Buffered tiling, parallel processing and seamless merging, so a district is the same job as a site with more tiles. | The method does not change when the programme scales, so the second scheme costs a fraction of the first. |
What the licence actually buys
- The specialist comes out of the loop. Ground classification normally needs someone who knows the sensor and retunes per site. The classification here adapts to the acquisition geometry itself, across airborne, drone and tripod surveys, so an analyst on your team runs it.
- The archive becomes an asset. Point clouds you have already paid for get re-derived at whatever resolution the current question needs, without going back to the surveyor and without a new flight.
- The second date is where the money is. Volume moved, ground subsided, canopy gained or lost — each reported against a level-of-detection threshold, so what you report as change is defensible when it is challenged.
- Area stops being the constraint. Tiling, parallel processing and merging mean a district is the same job as a site. The method does not change when the programme scales, which is why the second scheme costs a fraction of the first.
Method. Runs on the same engine: LAS, LAZ and COPC read in place, with the terrain, hydrology and LiDAR tool sets. Nothing asks you to change how you commission a flight.
For mixed airborne, drone and terrestrial surveys in one fabric we assess FAST-GC (Fareed et al., 2026) as a specialist addition. AGPL-3.0, so scoped per engagement rather than embedded — stated here rather than left to discover.
No LiDAR? The products still run on satellite and photogrammetric inputs. The pass raises the resolution of the answer, not the possibility of one.
Licence programmes
One licence model, every product
A pilot builds the first version on your data. After it, every product in the family licenses on these same tiers — so adding a second product is a purchase order, not a second commercial negotiation.
Practitioner
One named user
$1,200
12 months
- All six analyses
- Your own cadastre and imagery
- Exportable schedules and reports
- Email support
Most chosen
Team
Five named users
$6,000
12 months
- Everything in Practitioner
- Configured to your rates and tolerances
- Your minimum plot sizes and heads of claim
- Priority support
Authority
One authority or developer
$20,000
12 months
- Unlimited users in the entity
- Onboarding and template setup
- Your own subscribed imagery
- Quarterly review with our team
Single Scheme
One corridor or plan area
$4,500
90 days
- Three users for one scheme
- Fits a project budget line
- Configured to that scheme
- Credited against a later licence
Fixed term, not auto-renewing
A licence runs for its term from the date of payment and then stops. Nothing recurs on your card, and nothing renews without you.
Purchase orders welcome
Authorities and developers can be invoiced against a PO rather than paying by card. Ask and we will raise one.
Your data stays yours
Analysis runs as client-side WebAssembly. Files you open are processed in your browser and never reach our servers.
Pilot ranges above are indicative and scoped per client. Products are in development; a pilot is how the first version gets built, on your data, with you as the design partner.
Applying this to a live programme
These are the tools. Adapting them to your own land record, data standards and delivery programme — and identifying which of the seven capabilities is actually the constraint — is the advisory work.
Questions? Support@thegeolab.digital

