Terminal edits: what GenAnywhere lets teams change
Five moves on a terminal building, a layered site around it, and a change register that keeps a long refurbishment review honest.
Terminal teams usually arrive with a list of changes rather than a request for a model. GenAnywhere supports a small, defined set of edits on a generated site: buildings can be replaced, moved, rotated, retyped and adjusted in height, and terrain, buildings and vegetation can be handled as layers. Anything that is equipment, interiors or a new structure on empty ground falls outside that set.

1 The edit set, read as a short list
1.1 Five moves on a building
Replacement swaps one footprint for another, which is how a demolished building disappears or a planned one is sketched in. Move and rotate handle alignment against a road or a quay. Retype changes what the scene calls a building, so a terminal extension stops reading as a warehouse. Height adjustment is the one teams reach for most, because a mezzanine or an extra storey changes how a building reads from the forecourt. That is the whole list, and it is worth knowing before the meeting starts.

1.2 What the scene treats as fixed
Roads, kerbs, rail tracks and pier edges come from the map and are not editable objects, so a proposed drop-off lane cannot be moved the way a building can. Equipment is not generated at all, including air bridges, baggage systems, check-in islands, signage and seating. Interiors are outside the scope. Knowing what is fixed saves a review from promising a change the platform cannot make, and it tells you which items belong on an overlay list for the next tool.
2 Where terminal teams usually start
2.1 The forecourt and the drop-off
Forecourt work is the common opening request, because access and queuing arguments are easy to have and hard to settle with a plan. The scene shows the terminal frontage, the kerb, the parking and the road beyond it, and a building edit can show a canopy or an extension changing the frontage. It will not show a queue forming. That distinction matters when the audience includes operations staff who read a picture as an operating assumption rather than a massing study. Keep the queue discussion with the people who own the timetable.
2.2 Concourse extensions and canopies
An extension is usually a massing question before it becomes a design: how far it reaches, what it blocks, whether it leaves room for a service yard. The scene answers those by showing the mass in place among the existing buildings. A canopy may not exist as a separate object at all, since footprints come from imagery and thin roofs are often missed. Sketch the canopy as an overlay and say so, rather than adjusting a building until it looks vaguely right.
3 Keeping a change register
3.1 Naming and sequencing
Long refurbishments produce a dozen versions of the same view. Number the edits, describe each in one line, and keep the screenshots with the numbering, so a reviewer can trace why option three had a lower roof than option two. A register of half a page is enough. Date each entry as well, since a review that runs across a quarter will otherwise assume every image came from the same week. Without one, the meeting spends its opening ten minutes working out which image is current, and the answer is usually a guess.
3.2 Comparing two options honestly
Compare from a fixed camera position, with the same layers on, and label both images with the option and the date. Changing the viewpoint between options flatters whichever one got the better angle, and most audiences notice even if they cannot say why. If the argument is about height, a single eye-level view from the road settles more than four aerial views. Put the two images side by side rather than on consecutive slides.

4 Limits
4.1 No interiors, queues or fire modelling
The scene does not model interiors, passenger flows, queue lengths, fire strategy, evacuation or structural capacity. Those are specialist studies with their own data, and bodies such as UITP publish material on terminal operations that belongs with them. A generated terminal is a volume among volumes. If the review needs to know whether a concourse can hold a peak crowd, the answer is not in this file, and the meeting should say so early.
4.2 Imagery date and live terminals
A working terminal changes under its own roof, and imagery rarely keeps up. A new pier, a reclad facade or a demolished car park may be missing or still present. Check the imagery date for the area, note it on the slide, and ask the terminal operator what has changed in the last two years. Operated buildings also have temporary works that never appear in imagery at all, from hoardings to site cabins.
5 Running an edit review
5.1 A sequence that holds
Begin with the terminal in its city or port setting, then the frontage, then the specific building under change. The wide view answers how the terminal meets the transport network, the frontage view answers how it greets people, and the close view is where the edit is judged. That order also gives the audience a chance to see the unchanged context before the proposal appears. Keep the wide view as the closing slide, so the discussion ends where it started.
5.2 Handover
Export the GLB once the edit set is agreed, not after every change. The file carries the site and the edits as they stood at the moment of preview, so a late change means a new export. Note which edits were applied, in the same numbering as the register, and send the register with the file. A receiving team that can read the edit history will not repeat questions the review has already answered.
Open the GenAnywhere app and frame a terminal frontage
6 Before you export
6.1 Close the edit set
Agree which edits belong in the export before you generate it. An export made halfway through a discussion carries a version nobody agreed to, and it will circulate. Close the set, number it, and state the closing date in the note. If the review reopens the argument next month, export again rather than amending the old file by hand, because the manual amendments are the ones that go missing. Keep the previous export until the new one has been opened and checked.
6.2 List what stays outside
List the air bridges, kiosks, signage, seating, baggage systems, service vehicles and canopies that the scene does not contain. That list is the boundary between context and design, and it is the part most likely to be misread in a polished image. Keep one line per group, with the file that will supply it. If a group has no owner, that is worth discovering before the review rather than during it.
6.3 Name the next step
Say who takes the scene and what they will do with it: a design team starting a refurbishment, an operator preparing a consultation, or a planner comparing access options. Each will want a different extent and a different level of edit. Naming the next step also decides how much of the edit register needs to travel with the file. A short answer here prevents a long argument later. Write it on the opening page of the note, above the file list, because that is the part people read.
7 FAQ
FAQ-1 What can be changed after generation?
Buildings can be replaced, moved, rotated, retyped and adjusted in height, and terrain, buildings and vegetation can be managed as layers during preview. That covers most massing questions a terminal review raises. It does not cover new structures on empty ground, roads, equipment or interiors. If a requested change is not on that list, plan for an overlay in the downstream tool instead of an edit in the scene.
FAQ-2 Can I change the number of floors?
You can change a building's height, which is what the scene stores. Floor counts are not part of the generated data, so a taller mass will not show additional floors, cores or stairs. For a review about storeys, use the height change to test how the building reads and keep the floor argument in a drawing. Say which of the two the audience is looking at, because a taller block reads as extra floors to most people.
FAQ-3 Do the edits carry into the export?
Yes, the GLB carries the site as it stands when you preview it, including the edits you made. That is why the export should follow the agreed edit set rather than precede it. Keep the scene file as well, since a later change means a new export rather than a patch to the old one. Note the edit numbers in the handover so the receiving team can match images to decisions.
FAQ-4 Can two teams edit the same scene?
Treat the exported scene as a copy rather than a shared workspace. Two teams editing their own exports is workable; two teams expecting one live file is not. Agree who holds the master scene, and pass changes back as notes rather than as edits made in separate copies. When the copies diverge, the register is the record that tells you which one the meeting actually saw.
See how a terminal scene moves into a design 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-13.