GenAnywhere Generate Now

Select a map area. Generate a 3D city model with AI.

No drone survey required. Turn map data into editable 3D buildings, terrain, water and vegetation for BIM, GIS and 3D workflows.

Generate now

Oblique photography for planning: how teams use GenAnywhere

A dated record of what exists, an editable base for what might, and the discipline that keeps a consultation honest.

Planning conversations move between two questions: what is there now, and what would change. A capture answers the opening question with surface evidence. A map-derived base answers the second with an arrangement that can be edited in front of a room. Teams that keep the two roles distinct tend to have shorter, calmer meetings.

Aerial view of a riverfront district with a tram line and low blocks

1 What planning needs

1.1 What does a planning conversation need?

A shared picture of the site, a clear statement of the proposal and an honest account of what the evidence does not cover. The note is what keeps the opening claim and the closing caveat from being confused.

It also needs a scale that people recognise. A plan drawing is precise and hard to read; an aerial view is readable and easy to misread.

Good packs give both, with a note that says which is which. A committee that cannot read the drawing will read the picture, and a picture without a note invites over-reading. Professional institutes such as the RTPI publish material on plan-making and consultation that is useful background when a team is deciding what to present.

1.2 Where does the capture help?

It shows the setting. The neighbour's roof line, the mature trees, the yard that the scheme would overlook: these are the features a committee will ask about. Oblique photography earns its place in that conversation because a drawing describes a place and a photograph shows it.

It shows condition. A proposal beside a tired façade or a recently refurbished one reads differently, and the capture makes the difference visible.

It shows a date. A record taken before works start is useful when a later question turns on what was there. It also shows the things a photograph is good at: the tree that will be lost, the yard that will be overlooked, the gap between buildings that a plan drawing makes look generous.

2 Build the context

2.1 Draw the area

Start wider than the site. A base that includes the next street, the riverbank or the rail line gives the room the context it needs to judge scale.

Include the awkward edges. A boundary that follows a fence rather than a straight line is part of the argument, and a base drawn carelessly smooths it away. Check the extent with someone who knows the site, because a drawn boundary can follow the map rather than the fence.

Decide the level of detail. A district review needs blocks and ground, not window frames. That decision also sets the cost, because detail is what makes a scene slow.

2.2 Test the arrangement

Place the proposal in the base and look at it from the viewpoints the decision will be argued from: the street, the opposite bank, the approach road.

Move a block, change a height, remove a storey. The point of an editable base is that the room can see a change rather than imagine it. A change that cannot be seen from the standard view is often the one that matters most to a neighbour.

Keep each option as a separate scene. A single scene edited live leaves nobody sure which version was approved. Keep the edited scene separate so the standard view stays comparable.

GenAnywhere draws the area from map and satellite data, identifies building footprints, estimates heights and infers types, then separates buildings, terrain, water and vegetation into layers. A team can place a proposal in that scene, change a height, remove a storey or move a block, and compare the result from a fixed viewpoint. The export is a general GLB for design, GIS and engine workflows, so the visual and the working model stay the same file.

Aerial view of a city wrapped around a river bend

3 Show the proposal

3.1 Existing and proposed

Keep the capture as existing and the base as proposed, and style them differently.

A proposal rendered in photographic texture will be read as a photograph of something that exists, which is the most common way these packs mislead. A pack that shows one material and one massing invites the room to argue about the material.

Label the proposed volumes, the storey counts and the areas that are illustrative. A label is cheaper than a correction later.

3.2 The street view question

Someone will ask what it looks like from the pavement. A base built from map data can answer the massing part of that question and cannot answer the material part. Saying which part is answered keeps the conversation on the drawing that can answer the rest.

Be specific about it. "The block would sit four storeys above the shopfront" is a massing statement; "the façade would be brick" needs a design drawing.

Where the answer depends on a surface, use the capture. Where it depends on arrangement, use the base. Where it depends on both, show the massing and say that the material is still open. GenAnywhere can change a height or move a block without a new drawing set, which is what keeps a consultation moving.

4 Support consultation

4.1 What do residents ask?

Whether the scheme is too tall, too close, too dense or in the wrong place. Those are arrangement questions, and the base can answer them directly.

Whether the site looks as they remember. That is a surface question, and the capture answers it, including the date.

Whether anything will be lost. Trees, views and familiar buildings are the usual concerns, and both records help when they are labelled honestly. Prepare two answers for each: what the record shows and what it does not.

Rooftop plant overlooking a city skyline at sunset

4.2 How do you answer honestly?

Show the limits. If the capture has a hole where a tree canopy sat, say so rather than letting the smooth surface speak.

Separate what the model knows from what it assumes. Heights estimated from map data are estimates, and a planning conversation should not present them as measurements. A consultation that admits a gap is more likely to be trusted than one that fills it with a plausible surface.

Record the questions you cannot answer. A consultation that promises an answer later is more credible than one that improvises. Write the promise down, with a date, so it can be kept.

5 Keep the record

5.1 What do you keep?

The capture with its date, the base with its imagery date and the version of the proposal that was shown. A record that cannot be reproduced is difficult to rely on later. The base can be reissued with a new version of the proposal without touching the capture.

The questions asked and the answers given. A consultation record is useful when the same question returns a year later. Keep the version that was shown, as well as the version that was approved.

The known gaps. A list of what the evidence did not cover protects the team that presented it.

5.2 What do you publish?

Images that show the arrangement clearly and do not imply a certainty the model lacks. Say what the images are for: a conversation about arrangement, not a promise about appearance. A scene drawn from map data can be widened when the argument moves beyond the site, and the same convention applies to the next area. That keeps the pack consistent without another flight, and it keeps the capture as the record of the day it was flown.

A note that says the visuals are illustrative and that dimensions should be read from the drawings.

Nothing that presents a map-derived model as a survey or a decision. The visual supports a conversation; it does not replace the process.

6 Set the limits

6.1 What can this evidence not do?

It cannot determine an application, establish a boundary or certify a height. Those belong to the statutory process and the survey. Say so plainly in the pack rather than leaving the room to discover it.

It cannot show condition where no capture exists. A plausible mass says nothing about the state of a façade.

It cannot promise that the model matches the site today. Map data lags, and a site that has changed will not be reflected. It cannot resolve a question about ownership, access or legal interest, which belong to other records.

6.2 When is a capture not needed?

When the question is purely about arrangement and the site is clear. A massing study can run on the base alone.

When the site is well documented and the proposal is far from the neighbours. The capture adds little where nothing is being compared. Where the proposal is small and the neighbours are far away, the capture adds cost without changing the argument.

When the decision is at a scale where surfaces disappear. A corridor study rarely needs façade texture.

6.3 When do you stop?

Stop when the room can answer the question it came with. More views do not make a settled point stronger.

Stop when the pack becomes longer than the discussion it supports. A pack that fits the time the meeting has is usually the right size.

Draw the area in the GenAnywhere app and present it beside the dated capture rather than in place of it.

7 FAQ

FAQ-1 Is a GenAnywhere model acceptable as planning evidence?

It is a visual aid for discussing arrangement, not a statutory document. Applications rely on drawings, surveys and the formal process, and the model should be presented as illustrative material that supports that process. A pack that says this at the start is easier to defend than one that leaves the status ambiguous.

FAQ-2 Can I show a proposal inside the capture?

Yes, as a reference scene, provided the proposal is styled and labelled so it cannot be mistaken for existing fabric. Keep the capture and the model as separate files for audit. Keep the proposal on its own layer so it can be switched off when the room needs to see the site as it is.

FAQ-3 How detailed should a consultation model be?

Detailed enough to answer the arrangement questions the consultation will raise, and no more. Extra detail adds cost and invites questions the visual cannot answer. A model that answers the room's three questions well is worth more than one that answers none of them. The aim is a conversation the room can follow, not a complete record of the site.

FAQ-4 What should the visual note say?

That the model is built from map and satellite data, that heights are estimates, that the capture has a stated flight date, and that dimensions should be read from the project drawings. Four sentences usually cover it.

See how a map area becomes an editable site model in the GenAnywhere workflow.

Content and technical notes

This article was prepared by the GenAnywhere team with AI-assisted drafting and human review.

Product features, formats, and availability change as the platform evolves; refer to the official GenAnywhere website for current details.

For technical questions or corrections, contact support@genanywhere.com.

Last reviewed: 2026-11-06.