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

Crane placement: where GenAnywhere sets heading and height

Nowhere in the platform. The scene fixes the ground and the buildings; crane orientation and jib height are set in the tool that holds the crane.

GenAnywhere does not set crane heading or crane height, because cranes are not part of the generated content. The scene supplies the ground a crane stands on, the sheds it works beside and the layers used to read them. Heading, height and every other part of a crane's pose are set in the downstream tool where the crane asset is placed.

Aerial view of a crawler crane lifting steel pipes at an industrial site

1 The direct answer

1.1 No crane controls in the scene

There is no heading slider, no height field and no jib angle for any piece of equipment, because no equipment is generated. The scene contains terrain, buildings, vegetation and water, and the editing controls apply to the buildings and to the layers. A team that goes looking for a crane rotation control will not find one, and the search wastes a session. Better to know that before the session starts, and to plan the placement step for whoever holds the crane model. Write the plan into the agenda, with a name against it, so the step has an owner.

Cargo ship at a berth with the port glowing at sunset

1.2 What the platform does set

The platform sets the ground: its shape, its level and its extent. It sets the buildings that surround a crane position, with heights estimated and types inferred, and it lets those buildings be replaced, moved, rotated or resized. It also sets what the viewer can hide, since terrain, buildings and vegetation are separate layers. Those are the conditions a crane works in. The crane is the object that gets placed into those conditions later, and the quality of that placement depends on how well the ground was framed.

2 Why pose belongs downstream

2.1 The asset carries its own geometry

A crane model arrives with its own origin, its own working radius and its own boom or jib geometry. Those properties live in the asset and in the software that authored it, not in a site model. Recreating them in a scene generator would duplicate work and produce a second, weaker copy. Placing the asset in a 3D, BIM or game engine environment keeps one version of the crane, which is the version the equipment team maintains. A second copy inside a scene generator would drift out of date within a month.

2.2 Placement happens in the receiving tool

Once the site is exported, the receiving tool has the ground and the buildings, and the crane can be positioned against them. Heading is a rotation around the vertical axis at that point. Height is a translation along it. Both are ordinary transforms in the receiving application, and both can be revised in seconds when an option changes. That is a better division of labour than asking a site generator to hold equipment poses it cannot verify. It also means a change of option is a transform, not a regeneration.

3 What a crane review needs

3.1 Ground, access and the buildings in between

Most crane questions start with the ground: whether the outriggers have room, whether the access road takes the delivery, whether a shed blocks the approach. The generated scene answers those at a glance, and it lets a team move a shed to test an alternative. Site level matters too, since a crane standing on a slope is a different proposition from one on a hardstanding. The scene shows the level, and the crane study decides what to do about it. Check the access route in the scene before the crane arrives on paper, because a route that pinches at a gate is easier to spot from above.

3.2 Radius and reach stay outside

Working radius, load charts, boom length and lifting capacity are engineering values, and the scene holds none of them. A crane placed on a site model is a picture of a position, not a demonstration that a lift is possible. Teams that forget this end up defending a screenshot in a meeting that asked for a calculation. Keep the radius question with the lift plan and the people qualified to produce it. If the picture shows a crane that could not reach its target, the picture is wrong, and the lift plan is the document that can say so.

Container terminal with ships berthed along a long quay

4 Limits

4.1 No lifting, clearance or clash analysis

Nothing in the scene checks lifting capacity, slew clearance, power line proximity or clashes between a jib and a building. Those need the crane data, the site rules and a study. Placing a crane asset next to a generated building shows a relationship; it does not verify it. Say that when the image is shown, especially to an audience that reads a realistic picture as a technical claim. A one line caveat on the slide does more work than a long explanation afterwards. Organisations such as ISO publish the standards that crane classification and testing rest on.

4.2 No equipment library

The platform does not ship a library of cranes, and it does not convert one into generated content. Teams bring their own assets, often from an equipment manufacturer, a plant hire company or an internal model library. Formats vary, so the placement tool has to accept what the asset pipeline produces. Plan that step before the review rather than during it, because a missing crane model stalls a session faster than a missing slide. Ask the equipment team for the asset a week ahead and confirm the format it exports.

5 Working practice

5.1 Preparing the handover for a crane study

Decide which area of ground the crane study needs and export that extent. Include the buildings around the position, since they define what the crane has to work around. Note the site level assumption in the handover, because a level taken from imagery may differ from the surveyed level on site. Keep the file name specific to the area, so the crane team can match it to its own drawings without a conversation. A grid reference in the name is enough for most site teams to locate the file.

5.2 Reviewing a crane once it is placed

When the crane appears on the scene, check three things before discussing anything else: the position relative to the ground, the heading relative to the work front, and the height relative to the nearest obstruction. Those three checks catch most of the errors that a composite invites. Then compare the picture with the lift plan, and treat any disagreement as a question for the plan rather than for the picture. Record the heading and height you used, since a later reader cannot infer them from the image alone.

6 Before you export

6.1 Scope

Frame the ground the crane works over, plus enough around it to show access and neighbouring structures. A tight frame around the crane base hides the constraints that matter. A frame that covers the whole site loses the detail near the base. Two frames, one for context and one for the working area, cover most reviews without forcing a compromise. Send both, and say in the note which frame the crane position was tested against.

6.2 Missing assets

Cranes, delivery vehicles, lifting gear and temporary works are all outside the generated set. List them with an owner, and say which tool will place each one. That list prevents the assumption that a crane will simply appear in the next version of the file. It also makes clear that the crane's heading and height are decisions made by the team placing it. That sentence alone prevents a round of questions about missing controls.

Open the GenAnywhere app and frame a crane working area

6.3 Purpose

State what the file is for: a position study, an access check, a visual for a community meeting, an environment for a simulation. Purpose decides the extent and the level of building correction. A file sent for a position study should not be read as a lift plan, and a clear purpose statement is what keeps that boundary intact once the file is forwarded. Put the statement in the file name as well as the covering note, since names travel further.

7 FAQ

FAQ-1 Can I set a crane's heading in GenAnywhere?

No. Cranes are not generated content, so the platform has no crane controls at all. Heading is a rotation applied to the crane asset in the tool where it is placed, after the site has been exported. Decide the heading there, and record it in the note that goes with the picture. A heading recorded once saves a rebuild when the question comes back a month later.

FAQ-2 Can I set crane height?

No, for the same reason. Height is a translation of the asset in the receiving tool, and it depends on the crane's own geometry and on the lift being studied. The scene gives you the ground level and the buildings around it. The height of the jib or boom belongs to the equipment model and to the person running the lift analysis.

FAQ-3 Where do cranes get placed, then?

In a 3D, BIM, GIS or game engine tool that can import the exported GLB and hold the crane asset. Placement is an ordinary transform there, and it can be revised quickly as options change. Keep the crane model in that environment rather than rebuilding it for each review. The generated scene stays the fixed reference for the ground.

FAQ-4 Does the scene check whether a lift is possible?

No. Capacity, radius, load charts and clearance are outside the scene. A crane placed against a generated building shows a relationship that someone still has to verify. Keep those checks with the lift plan and the engineers who own it. A picture that looks plausible is not evidence, and treating it as evidence is how a review approves something it should have questioned.

See how a crane working area moves into a GLB 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.