Score the groundbefore you put people on it.
For defence planners, border and disaster-response agencies and logistics staff: turn a coordinate into an operability score that captures heat stress, trafficability, altitude penalty and ground stability — the four things that decide whether a site can be held, supplied and moved through.
What the API does for defence.
Surface moisture and open-water signals show where ground turns soft, so mud windows are planned for instead of discovered.
DEM elevation drives the lift, payload and sustainment derating that decides whether a site can actually be supplied.
Mid-range NDVI indicates cover that conceals without obstructing movement; heavy canopy is penalised for blocking lift.
Every read is a passive query against open Earth-observation data — candidate ground is ranked before any recce team deploys.
Coordinate to decision, step by step.
Every defence request runs through the same five stages. Nothing is cached from a neighbouring tile and nothing is invented — if a pixel is unusable, the response says so.
- 01Inputlat / lng + mode: defence
- Single HTTP POST
- Basing point, waypoint or staging centroid
- No classified input required
- 02ObserveTerrain, surface, climate, hazard
- DEM elevation, slope and relief
- Sentinel-2 NDVI / NDWI / NDMI
- Thermal and precipitation reanalysis
- Seismic catalogue within 200 km
- 03DeriveOperability signals
- Trafficability and mud-window risk
- Altitude and lift penalty
- Concealment vs obstruction
- Thermal and cold-stress envelope
- 04FuseWeighted, deterministic model
- Climate envelope weighted highest
- Terrain workability second
- Surface going and hazard as modifiers
- Hard penalties for inundation
- 05Output0–100 score + band + components
- Machine-readable JSON
- Sustainment drivers exposed separately
- Same coordinate → same answer
No random seeds. No hidden drift. If you got a 74 last Tuesday, you'll get a 74 next Tuesday — unless the ground itself has changed. That is what makes the score defensible in an underwriting memo, a planning submission, or a board pack.
Three fields in. That is the whole input.
No shapefiles. No polygons. No uploads. No GIS stack to maintain.
latnumberLatitude in decimal degrees. Use a candidate basing point, a route waypoint, or a staging-ground centroid.
lngnumberLongitude in decimal degrees.
mode"defence"Defence mode weights climate envelope and terrain workability most heavily, and rewards mid-range vegetation for concealment.
POST /v1/land-intel/assess
{
"lat": 34.0837,
"lng": 74.7973,
"mode": "defence"
}200 OK
{
"score": 71,
"classification": "SUSTAINABLE",
"band": "Operable",
"mode": "defence",
"components": {
"climate": 64,
"terrain": 70,
"surface": 79,
"georisk": 76
},
"observations": {
"elevation_m": 1585, "slope_pct": 3.1,
"ndvi": 0.34, "ndmi": 0.18,
"ndwi": -0.11, "seismic_events_5yr": 6
},
"generated_at": "2026-07-11T12:04:22Z"
}Enterprise-grade data. Open licences. Zero cost.
Every defence score is built on the same public Earth-observation feeds that power commercial GIS stacks sold for tens of lakhs to crores per annum. We expose them directly through one simple HTTP call.
10–20 m multispectral surface reflectance from ESA's Copernicus Sentinel-2 constellation, served as cloud-optimised GeoTIFFs via the AWS Earth Search STAC catalogue. Every request samples the actual pixel at your coordinate for red, green, NIR and SWIR bands.
GLO-90 digital elevation model from the Copernicus DEM programme, sampled through a five-point stencil so slope and local relief are measured, not assumed. The centre point plus four surrounding points gives a true local gradient.
Every sampled pixel is checked against the Sentinel-2 SCL. Cloud, cloud shadow, thin cirrus, saturated and no-data pixels are rejected outright — not smoothed over — so the score only sees ground truth.
Open-Meteo historical climate reanalysis provides temperature, precipitation and humidity baselines at the coordinate. The 5-year seismic catalogue supplies catalogued ground-motion frequency and peak magnitude within 200 km.
No random seeds. No hidden drift. If you got a 74 last Tuesday, you'll get a 74 next Tuesday — unless the ground itself has changed. That's what makes the score defensible in an underwriting memo, a planning submission, or a board pack.
What you get back.
A plain-English report anyone can read. No remote-sensing degree, no GIS software, no manual report.
One simple number that tells you how operable this ground is.
Heat, cold, altitude, and terrain burden that drive fuel, water, and maintenance needs.
Where vehicles can move, where water blocks movement, and where vegetation gives concealment.
A simple label like Mission Ready, Operable, or Constrained, plus a recommended action.
The result comes as clean JSON that any software can read.
The parameters behind the score.
Every response is one score plus the measured parameters that produced it. Which parameters come back depends on the vertical you query.
Whether wheeled and tracked movement is physically possible on this ground.
Vegetation density available to mask movement and positions.
Whether the ground can carry a base, helipad, airstrip or depot.
Heat, cold and altitude penalty on people and equipment.
Rivers, ponding and seasonal inundation across the area.
Ground-motion record and terrain instability.
What those outputs do in real life.
Rank candidate basing coordinates on sustainment burden remotely, so recce effort is spent only on ground that already passed the terrain and climate filter.
Score points along a corridor across the year and publish the months where the route stays trafficable for heavy vehicles.
Combine altitude penalty with ground stability to shortlist coordinates that can carry lift, stores and repeated heavy landings.
Pick staging grounds that stay usable when the surrounding terrain saturates or shakes, and re-score them as the event develops.
Pick a coordinate. See the real output.
These are live calls to the production defence engine — real Sentinel-2 imagery, real elevation, real climate and seismic records. Nothing here is mocked.
Cold desert, extreme altitude
Gradient limit for wheeled and tracked movement
Rivers and inundation that block movement
Wetter ground bogs down heavy vehicles
Vegetation available to mask movement and positions
Firm, built surface usable for basing and staging
Altitude penalty on people, lift and vehicles
Ruggedness across the approach and basing ground
Sustainment burden on personnel and equipment
Ground stability of the sector
Fused live from Sentinel-2 L2A optical imagery, Copernicus GLO-90 elevation, NASA POWER climate reanalysis and the USGS seismic catalogue — returned in a single JSON response, typically in about a second.
How this was done before — and what changes.
Every row is a task defence teams already do today. The left column is the traditional method. The right column is the same task with one API call.
Ten bands. One axis. Zero ambiguity.
The 0–100 axis is partitioned into ten calibrated bands, each mapped to a defensible defence decision — identical across every coordinate on Earth.
The operational workflows Rootfifteen replaces.
Forward-site basing screens
Rank candidate basing coordinates on sustainment burden before a recce team ever deploys.
Route & movement windows
Score points along a corridor to find the months where ground stays trafficable for heavy vehicles.
Airfield and depot siting
Combine altitude penalty and ground stability to shortlist coordinates that can carry lift and stores.
Disaster-response staging
Pick staging grounds that stay usable when the surrounding terrain saturates or shakes.
Drop the API into the systems that already run defence decisions.
Rootfifteen is one HTTP endpoint. That means it fits inside any software that already touches defence workflows — no new dashboard, no new map stack, no internal GIS team required.
Add a terrain-readiness layer to operational maps so planners rank candidate ground before committing recce assets.
Score waypoints along routes and publish the months when corridors stay trafficable for heavy vehicles.
Shortlist candidate installations on sustainment burden, altitude penalty, and ground stability.
Combine elevation, slope, and surface moisture to find coordinates that can support repeated lift and stores.
Screen remote locations for accessibility, concealment, and all-season operability.
Pick staging grounds that stay usable when surrounding terrain saturates or shakes.
Every defence call returns a 0–100 score, a calibrated band, a machine-readable classification, and the component sub-scores that explain it. Wire it into your underwriting engine, your site-screening workflow, or your command map exactly like any other REST API.
Same coordinate. Different decision.
For insurers, lenders, agri-input companies and food supply teams: replace spot-checks, satellite-tile pipelines and subjective field report…
Read the agriculture pageFor developers, real-estate underwriters, infrastructure planners and property insurers: compress terrain, hydrology and ground-motion risk …
Read the construction pageNow 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.