How and where it can be used?
The everyday construction jobs the score is used for.
Fifteen everyday construction decisions this score is used for.
Shortlisting a plot to build on
Compare candidate sites in minutes and drop the ones with bad slope or wet ground before paying for a survey.
Pre-feasibility for a housing project
Know the earthworks and drainage story before the layout and budget are locked.
Planning a road, rail or pipeline route
Score points along the whole corridor and reroute early around unstable or flood-prone ground.
Siting a factory or warehouse
Confirm the ground is flat and firm enough for heavy floors and machinery before committing capital.
What's new?
The legacy pre-construction workflow, and what Rootfifteen actually replaces.
How traditional land surveys still work today.
A four-phase, ground-heavy process that burns weeks before a single design decision is made.
- 11–3 weeks
Phase 1: Manual Record Collection
Surveyors manually retrieve paper cadastral and revenue maps from local government offices. Early dispute or encumbrance identification is slow and fragmented.
Pain point: Records are often outdated, physically degraded, or held across different offices.
- 23–8 weeks
Phase 2: Ground-First Field Deployment
Engineering crews carry Total Stations and DGPS receivers to establish benchmarks, measure elevations, and mark boundaries on-site.
Pain point: Labour-intensive, expensive, weather-dependent, and physically slow across vast or harsh terrain.
- 31–2 weeks
Phase 3: Topographical Mapping & Processing
Raw field data, drone orthophotos and point-cloud data are imported into legacy GIS software by technicians to build contours and slope profiles.
Pain point: High human overhead, error-prone manual vectorisation, and data locked inside expert teams.
- 4Manual review
Phase 4: Risk & Constraint Analysis
Project managers cross-reference spatial maps against environmental zones, flood basins and legal boundaries to check Right-of-Way feasibility.
Pain point: Major risks are often discovered after large sums have already been spent on preliminary engineering.
70–80% of pre-construction due diligence.
We do not eliminate surveyors — we eliminate the manual, expensive guesswork that happens before heavy equipment arrives.
We replace 70% to 80% of the friction in pre-construction due diligence. Traditionally, an EPC firm has to send field teams with DGPS receivers and Total Stations to scout vast tracts of land for weeks just to answer basic feasibility questions: Is this route viable? What is the terrain risk? Are there environmental or parcel conflicts? Rootfifteen shifts that entire preliminary phase into an automated software workflow. Our V2 engine ingests heavy remote-sensing and vector data to deliver instant risk scoring, terrain analysis and land intelligence right at the pre-bidding stage. We do not replace the final physical pegging or soil testing on the ground — we replace the weeks of manual, expensive guesswork that EPC firms currently endure before they lay a single foundation.
How this was done before — and what changes.
A live read while you are still in the meeting.
No site visit, no imagery contract.
Every score breaks down into measured values.
How it works?
You send a coordinate. We read live satellite and climate data. You get one score back.
Five steps, every request.
- 01Inputlat / lng + mode: construction
- 02ObserveTerrain, surface and hazard sampling
- 03DeriveBuildability signals
- 04FuseWeighted, deterministic model
- 05Output0–100 score + band + components
Built on open Sentinel-2, Copernicus DEM, NASA POWER and USGS data — read live at your coordinate, never copied from a nearby area.
Four open data streams, one score.
10–20 m multispectral imagery for surface state, water and built-up fraction.
~90 m global elevation for slope, relief and terrain stability.
Rainfall, temperature and solar regime used for drainage and workability signals.
Recorded seismic events within 200 km over the last five years.
Three fields in. That is the whole input.
latnumberLatitude in decimal degrees. Use the plot centroid, a proposed foundation point, or an interval along a corridor.
lngnumberLongitude in decimal degrees.
mode"construction"Construction mode weights terrain and georisk most heavily and treats dense vegetation as clearance cost rather than a positive.
POST /api/public/v1/land-intel/assess
{
"latitude": 19.0760,
"longitude": 72.8777,
"mode": "construction"
}200 OK
{
"status": "ok",
"engine": "land-intel.v1",
"mode": "construction",
"rootfifteenScore": 68.4,
"classification": "Margin caution",
"components": {
"terrain": 61,
"georisk": 72,
"surface": 74,
"climate": 80
},
"observations": {
"elevationM": 14, "slopePercent": 6.4,
"localReliefM": 22, "ndwi": 0.09,
"ndbi": 0.12, "seismicEvents5yr": 3
},
"verticalMetrics": [
{ "key": "foundation stability",
"label": "Foundation stability",
"value": 61, "display": "61 / 100",
"band": "Standard footings" }
],
"generatedAt": "2026-07-11T12:04:22Z"
}What you get back.
Exactly what the live demo report shows for a coordinate:
- 1The Rootfifteen score, 0–100, for the exact coordinate.
- 2The classification band that goes with it, from Stable to Critical hazard.
- 3Four component sub-scores: terrain, georisk, surface and climate.
- 4Construction indicators: foundation stability, earthwork burden, flood and drainage exposure, substrate wetness, seismic design demand, site clearance load, existing built context and weather workability window.
- 5Every raw measured value behind those indicators, exactly as the API returns it.
- 6A written summary of what the numbers mean for the site.
- 7A PDF of the whole report.
What the number means.
Every response carries a classification alongside the score. The score ranges from 0 to 100; these are the exact bands the API returns for construction.
Now try it in your own stack.
Tell us what you are building and we will send you endpoint docs, a key, and limits that fit your use case.