Know your land before you buy or build

Look up one of three seeded ULPIN records through the D1-backed lookup, with a city-reference map and explicit provenance.

Select or enter a seeded ULPIN, request its indicative D1 record, center the reference map on its sample city coordinates, and preserve the returned state, district, area, land use, source, and evidence status in the local project context. This is not an official registry lookup.

Click the map to capture latitude and longitude, attempt an OpenStreetMap Nominatim reverse geocode, and save a location-only project context. Parcel boundary, ownership, area, and official land attributes remain unknown.

Enter decimal coordinates such as 12.9716 and 77.5946, or degrees-minutes-seconds values such as 12°58′18″N and 77°35′41″E. Ferrum validates latitude within ±90 and longitude within ±180, centers the reference map, and saves a coordinate-only context. It does not infer a parcel boundary, ownership, area, zoning, or official land record.

Search a place name through OpenStreetMap Nominatim, review returned candidates, and select one to establish a geocoded location-only context. Search results are addresses, not verified parcels or authority records.

Request browser geolocation permission and use the returned coordinates only within the local session. Denial leaves project context unchanged; parcel attributes, boundary, and official zoning remain unknown.

Move area and land-use controls to model built-up potential against a disclosed sample Karnataka FAR ruleset.

View the selected lookup result or chosen coordinates on an OpenStreetMap reference map. It does not assert an official parcel boundary.

Once a location with coordinates is set, the Environment tab shows month-by-month rainfall and maximum temperature from NASA POWER's 20-year climatology, with source, averaging period and licence. These are modelled long-term averages, not station readings or a forecast, and no design recommendation is drawn from them. INDICATIVE only; if the service is unreachable the panel says UNAVAILABLE.

Once a location is set, LandIntel shows cited reference setback and coverage tables - the NBC 2016 national baseline and the Model Building Bye-Laws 2016, plus UDCPR 2020 for Maharashtra - each with its source. They are reference baselines, not this parcel's rules: the parcel's permitted use and applicable FAR, and state tables not yet recorded (for example Karnataka), are shown as GAP, and the layer decision stays UNKNOWN. INDICATIVE only.

Once a location with coordinates is set, LandIntel reads open elevation data (AWS Terrain Tiles, a composite of SRTM and other open DEMs, roughly 30 m) and shows elevation, mean slope, slope class and aspect with source and licence. It is a terrain model, not a survey: values are INDICATIVE, the slope bands are Ferrum working bands rather than a code, and the layer never decides a hard exclusion (decision UNKNOWN).

Once a location with coordinates is set, LandIntel shows open NASA POWER rainfall climatology for the point (annual average, wettest month, intensity context) with source and licence. River flood exposure and nearby drainage paths or water bodies are shown as GAP: no licensed source is connected, so flood risk is never asserted and the layer decision stays UNKNOWN. INDICATIVE only.

Once a location with coordinates is set, LandIntel requests open ISRIC SoilGrids modelled topsoil values (clay, sand, pH, organic carbon, roughly 250 m resolution) with source and licence. These are INDICATIVE screening values, not a site investigation: bearing capacity and soil classification are shown as GAP, and if the SoilGrids service is down the layer says UNAVAILABLE instead of guessing.

Enter project metadata — title, purpose, CRS/EPSG, active-layer sources and observation dates, author, issue date, revision — and LandIntel derives an 11-check readiness score live from that metadata plus the loaded parcel context, never from typed text alone. Export stays BLOCKED until purpose, a verified boundary, geometry-derived scale, north, CRS, sources, legend, a required locator inset, collision-checked labels, disclosed confidence, and INDICATIVE qualification all genuinely pass. No PDF, GIS, CAD or image export is generated yet — only the quality gate is live.

Use a specific title that states what is being analysed and why the map exists. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

Use a traceable project or parcel boundary; a screenshot outline cannot substitute for verified geometry. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

Generate scale intervals and units from the mapped geometry and output size, never from decorative AI text. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

Derive north from the map reference system and rotation, with a clear symbol and no redundant label. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

State the coordinate reference system and EPSG identifier used for the exported map. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

List the source and observation date for every decision-relevant dataset, plus map issue date and revision. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

Generate the legend from actual visible layers and classifications so labels cannot drift from the map. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

Add a locator inset when the main frame does not establish the site’s regional context. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

Check label placement, leader lines, contrast and hierarchy; suppress noise instead of obscuring geometry. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

Show uncertainty, conflicts and missing evidence explicitly and never fill gaps with plausible-looking text. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

Mark sample or unverified maps INDICATIVE and prevent them from being presented as approval or decision-grade evidence. This check is validated live in LandIntel's Map Composer against real metadata and parcel-context evidence; it fails closed rather than passing on typed text alone.

State-specific survey, khasra, and plot-number lookup requires an authority adapter and is not currently connected. The control explains this gap without fabricating a result.

Official, authority-verified development permission and zoning interpretation are not yet connected.

Site-specific ground conditions (bore logs, bearing capacity, groundwater) and flood or seismic hazard data are not yet connected. Modelled open-data topsoil screening is shown separately in the Soil & geotechnical conditions layer.

A consolidated, shareable due-diligence report is not yet built.

Land-value and return forecasting are not yet built in LandIntel.

Combine parcel and statutory boundaries, setbacks and zoning, topography and slope, drainage and flood exposure, soil and geotechnical conditions, ecology and protected areas, utilities and access, and development cost and constructability. Each layer must retain source, date, confidence and status. The engine must distinguish hard exclusions, weighted preferences, data conflicts, UNKNOWN areas and suitable development zones, then explain every ranking from traceable evidence. This is roadmap work; no suitability zone is currently asserted.

Establish the parcel extent, survey identity, easements, reservations, and statutory overlays before any ranking begins. Decision role: Hard exclusion foundation. Required evidence: Authority parcel geometry, survey record, statutory boundary layers. This layer is visible in LandIntel but remains ROADMAP until a dated source and confidence status are connected.

Screen protected areas, sensitive habitats, vegetation, buffers, and environmental constraints with dated sources. Decision role: Hard exclusion + weighted preference. Required evidence: Notified protected-area, ecology, vegetation and environmental layers. This layer is visible in LandIntel but remains ROADMAP until a dated source and confidence status are connected.

Assess lawful access and the proximity, capacity, and crossing constraints of essential infrastructure services. Decision role: Weighted preference + conflict check. Required evidence: Verified road access, right-of-way and utility network records. This layer is visible in LandIntel but remains ROADMAP until a dated source and confidence status are connected.

Compare enabling works, access, terrain, ground risk, servicing, and other cost drivers after physical constraints are known. Decision role: Weighted preference. Required evidence: Constraint-linked quantities, verified rates, logistics and construction assumptions. This layer is visible in LandIntel but remains ROADMAP until a dated source and confidence status are connected.

Connect classified point clouds, bare-earth DTM and surface DSM data to project boundaries, design levels and traceable decisions. Every terrain dataset must expose capture date, provider, resolution or point density, classification, horizontal CRS, vertical datum, horizontal and vertical accuracy, and coverage gaps. Derived results remain INDICATIVE until validated against a project survey. Terrain evidence does not establish soil capacity, buried services, foundation suitability or legal boundaries. The specification is visible; ingestion, processing, 3D visualization and engineering calculations are not yet connected.

Separate classified ground from buildings, vegetation and other surface returns. Required evidence: Classified point cloud or authority terrain model with documented derivation. This terrain analysis is visible in LandIntel but remains ROADMAP until a qualified source is connected and validated.

Screen gradients, elevation ranges and abrupt terrain changes inside the project boundary. Required evidence: Terrain elevations with horizontal and vertical reference systems and stated accuracy. This terrain analysis is visible in LandIntel but remains ROADMAP until a qualified source is connected and validated.

Identify preliminary flow paths, sinks and low areas for drainage review. Required evidence: Hydrologically conditioned terrain model plus rainfall and drainage context. This terrain analysis is visible in LandIntel but remains ROADMAP until a qualified source is connected and validated.

Compare preliminary road or ramp alignments against target gradients. Required evidence: Terrain surface, proposed alignment, design criteria and verified tie-in levels. This terrain analysis is visible in LandIntel but remains ROADMAP until a qualified source is connected and validated.

Compare existing terrain with a proposed formation surface to estimate earthwork. Required evidence: Surveyed existing surface, design surface, boundary, method and tolerances. This terrain analysis is visible in LandIntel but remains ROADMAP until a qualified source is connected and validated.

Expose above-ground obstructions and canopy that may affect access or development. Required evidence: Classified above-ground returns with acquisition date and completeness statement. This terrain analysis is visible in LandIntel but remains ROADMAP until a qualified source is connected and validated.

Inspect the terrain profile along a proposed building, road or user-defined line. Required evidence: Georeferenced terrain plus the current design alignment or footprint revision. This terrain analysis is visible in LandIntel but remains ROADMAP until a qualified source is connected and validated.

Measure deviations between terrain evidence, project survey and design levels. Required evidence: Versioned survey and design surfaces in compatible horizontal and vertical datums. This terrain analysis is visible in LandIntel but remains ROADMAP until a qualified source is connected and validated.