Atlasly Site Analysis: Data Sources, Coverage, and Limits

Atlasly brings together site context that is otherwise spread across planning portals, public mapping services, policy documents, terrain datasets, and export workflows. The goal is to help a project team answer the first practical questions consistently:

• what constraints, designations, and physical conditions should be checked before the brief hardens;
• which issues deserve a primary-source review or specialist appointment;
• how a site compares with another site against the same evidence; and
• how to hand an early evidence pack into design, CAD, GIS, or a client conversation.

The site-analysis review sequence describes the checks to consider. It is not evidence that every source or step has completed successfully for a particular site. A useful result is not a binary "yes" or "no" on development. It is a traceable starting point for better questions.

A run starts with an address, location, or user-defined site area. Atlasly then combines location and boundary context with the relevant available data layers, such as terrain, buildings, roads, land use, planning context, heritage, ecology, flood information, transport, and policy references.

The exact sources and coverage depend on the jurisdiction and the layer. In England, for example, planning flood information should be checked against the Environment Agency's official Flood Map for Planning; nationally protected heritage assets should be checked against Historic England's National Heritage List; and environmental designations may be explored through MAGIC, the cross-government map service.

Atlasly makes these sources easier to assemble and compare. Where a project decision depends on a source, the primary publisher remains the authority to verify.

A mapped layer can be highly useful and still be incomplete, dated, generalised, or unsuitable for a particular decision. A boundary may be an address-point approximation rather than a surveyed parcel. Building height data can be estimated. A policy search can identify relevant text but cannot determine how a decision-maker will weigh it on a live application.

This distinction matters most at transitions: from feasibility to design, from design to submission, and from an early desktop review to construction information. Atlasly does not replace the appropriate measured, statutory, or professional route when the risk, cost, or decision demands it. Use it to identify the questions and organise the supporting evidence.

Flood. The Environment Agency says its planning map can help identify when a flood risk assessment may be needed, while its displayed material is provided without guarantees as to accuracy. A proposed development may still need a site-specific flood risk assessment, drainage strategy, or advice from the Environment Agency and local planning authority. Start with Atlasly or the free flood checker, then verify the current primary source and appoint the right specialist where required.

Planning. The National Planning Policy Framework is a material consideration in England, but planning decisions are made in accordance with the development plan unless material considerations indicate otherwise. Local policies, allocations, emerging documents, validation requirements, and case-specific evidence matter. Atlasly can surface relevant policy context; it does not give legal advice or guarantee permission.

Heritage and ecology. Designations are a prompt for careful work, not a conclusion about impact. Check the authoritative record, its date, the mapped geometry, and the relationship to the actual proposal. A formal assessment may require site inspection, specialist survey work, consultation, and a defined scope.

Terrain and context models help a team understand levels, slope, drainage implications, surrounding form, access, and broad massing constraints. They are not a replacement for a topographic survey, measured building survey, utility search, ground investigation, or setting-out information.

The same applies to exports. The formats available depend on the selected workflow and account. A file extension alone does not establish usable geometry, complete source coverage or an approved handover. Before relying on it for a decision or detailed drawing, verify coordinate system, unit settings, geometry, source date, and the elements that materially affect the proposal. The site-context DXF guide explains the hand-off in more detail.

Use the output in four passes:

1. Screen: identify the constraints, opportunities, data gaps, and potential showstoppers.
2. Verify: open the primary sources for the material findings and check the date, scope, location, and current status.
3. Commission: appoint a surveyor, planner, ecologist, heritage consultant, flood consultant, transport consultant, lawyer, or other specialist when the project needs that level of evidence.
4. Record: keep the source links, assumptions, boundaries, and questions alongside the option or brief they informed.

That sequence lets automation remove repetitive assembly work without confusing an early indication for a professional conclusion.