Quick Answer

Atlasly analyses a site by running a 17-step automated pipeline that covers geocoding, building context, topography, land use, green and blue infrastructure, street networks, heritage, ecology, physical features, planning history, policy compliance, land registry, microclimate, transport connectivity, CAD exports, PDF reports, and AI synthesis — producing a complete site intelligence package in minutes.

Step through Full timeline

Step 1 of 17

Geocoding & Boundary Detection

What data is fetched

Converts the selected address or map pin into precise geographic coordinates and establishes the site boundary polygon using cadastral and parcel data.

What you get

A verified site boundary drawn on the map with latitude, longitude, and area calculated — ready to query every subsequent data layer.

Why this matters

The geocoding step is the foundation. It resolves ambiguous addresses into exact coordinates, snaps to parcel boundaries where available, and calculates the site area that gates all downstream queries. Incorrect geocoding propagates errors through every following step, which is why Atlasly cross-references multiple geocoding providers and validates results against boundary data before proceeding.

From Practice

We built the 17-step pipeline because we lived through the alternative. On a masterplanning project in east London, I spent four days assembling site context from seven different data sources. The flood data came from the Environment Agency portal. The heritage constraints came from Historic England's mapping service. Transport data came from TfL. Terrain data required a separate GIS tool. By the time I had a complete picture, the client had already asked twice when design would start. The pipeline exists so that the next architect facing that question can answer: the site analysis is already done.

Shatakshi Patil, Architect

Frequently Asked Questions

How long does a full site analysis take with Atlasly?

A complete 17-step site intelligence pipeline typically runs in under 5 minutes. Individual steps execute in parallel where data dependencies allow. The result is a full site intelligence package with exports, report, and AI synthesis — work that would normally take days of manual research across multiple tools and data sources.

What data sources does Atlasly use for site analysis?

Atlasly aggregates data from Mapbox Terrain-RGB tiles, USGS 3D Elevation Program, Microsoft Global Buildings dataset, OpenStreetMap, Environment Agency flood data, Historic England records, Natural England ecological designations, Land Registry data, local authority planning portals, and meteorological datasets. Each step in the pipeline draws from the most authoritative source available for that data type.

How accurate is Atlasly's flood risk and planning data?

Flood risk data is sourced from the Environment Agency (England) and equivalent national agencies. Planning data comes from local authority planning portals and national planning databases. Terrain data achieves 1–5 metre vertical accuracy using Mapbox Terrain-RGB — comparable to Google Earth. All data sources are cited so practitioners can verify and cross-reference before formal submissions.

Can I export Atlasly's analysis into AutoCAD or Revit?

Yes. Atlasly exports in 14 formats including DXF and DWG (AutoCAD), SKP (SketchUp), GLB and IFC (BIM/Revit), OBJ, FBX, GeoJSON, Shapefile, SVG, CSV, and PDF. All CAD exports maintain proper coordinate systems and named layers, so files open in your software without manual cleanup or georeferencing.

What makes Atlasly different from manual site analysis?

Manual site analysis requires visiting multiple data portals, cross-referencing separate tools, and manually assembling findings into a coherent package. Atlasly runs 17 data steps automatically, producing a unified site intelligence package with exports in minutes. The key difference is not just speed — it is consistency. Every site gets the same rigorous 17-step assessment, so nothing gets missed because of time pressure or unfamiliarity with a data source.

See it run on your site

Drop a pin, draw a boundary, or paste a Google Maps URL. The 17-step pipeline starts immediately.