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 export: where the GenAnywhere GLB goes next

The site leaves as a GLB. The crane joins it in another tool, and the join is where most of the work sits.

When a crane scene leaves GenAnywhere, what arrives is the site: terrain, water, vegetation and building masses, plus whatever edits you made. The crane itself is not in the file and never was. It gets added in Blender, a game engine, a BIM authoring tool or a GIS viewer, depending on who needs the picture. Knowing that order makes the export a short step instead of a surprise at the far end.

Aerial view of a port construction yard with a lattice crane and steel stockpiles

1 What actually leaves the platform

1.1 Scene contents in the file

The exported GLB carries the generated ground, any water surface in the extent, the vegetation layer and the building masses with the positions you left them in. It also carries the result of your edits, so a hall you resized arrives resized. What it does not carry is a history of those edits. If a reviewer needs to know which masses were corrected, that information travels in your notes, not in the geometry. Treat the file as a snapshot, and the notes as the record of how it was made. A snapshot with no note is still useful; a snapshot with a wrong note is a liability.

Aerial view of a container terminal with ships and stacked boxes

1.2 What a crane scene does not carry

There is no crane, no jib, no counterweight, no base slab and no lifting plan in the export. There is also no road, no hardstanding and no buried service. Those are design and equipment assets, and they enter at the next stop. This is not a gap to be patched by editing the scene harder. It is the division of labour that makes the export small enough to move between tools at all. If a machine had to be generated too, the file would carry data nobody asked for and every tool would read it differently.

2 Where the file usually lands

2.1 Engines and content tools

Most crane scenes end up in Blender, Unreal Engine or Unity, where a plant model can be dropped onto the ground and lit properly for a review. The GLB format is maintained through the Khronos Group, whose glTF specification describes how a scene, its nodes and its materials should be read. Import behaviour still varies by application and version, so the specification tells you what to expect rather than guaranteeing that every tool will agree. Read the import notes for your version before you build a workflow around a format that behaves differently on a colleague's machine.

2.2 BIM and GIS contexts

The same file can be opened in a BIM authoring tool or a GIS environment, usually as context beneath a design model or a mapped base. That workflow is worth describing as a workflow and nothing stronger. A site scene placed under a design model is useful for checking position and scale; it is not a substitute for the design model, and it does not bring survey control with it. Describe it as context in any note you send out. The people receiving that context are usually the ones who will test it hardest, usually by comparing a wall against a drawing.

3 Scale and orientation on arrival

3.1 Units and origin

Check the unit convention in the receiving tool before you place anything. A scene that arrives at the wrong scale looks fine until a crane is dropped in and turns out to be the height of a shed. Compare a known building against its real dimension, such as a hall you can measure on a drawing, and write down the correction factor you used. The origin is worth a look too, since it decides where the model lands when someone types coordinates. If the scene is going into a GIS context, note whether it arrives in the right place or needs a shift, and record the shift.

3.2 Up axis and crane placement

Up axis is the other classic mismatch: what stands upright in one tool lies on its side in another. Fix the axis before you place the crane, not after, because a crane placed against a tilted world is hard to judge and easy to misread. Once the site is upright and scaled, place the machine so its base sits on the terrain rather than hovering. Zoom to the base and check the contact point from a low angle, because a gap of a few hundred millimetres is invisible from above and obvious from the side.

Container terminal with several blue cranes along the water

4 Keeping the crane layer clean

4.1 Naming and grouping

Put the crane in its own named group, with the configuration in the name, and keep the site in another. Anyone who opens the file later can then hide the machine and look at the ground, or hide the ground and look at the machine. Name the buildings that were edited too, so a corrected hall is not mistaken for a mapped one. This is housekeeping, and it is the difference between a file that gets reused and one that gets rebuilt. It takes five minutes at export and saves an afternoon later.

4.2 Materials and lighting

The generated scene arrives with simple surfaces, which is fine for massing and thin for presentation. If the review needs a realistic image, the materials work happens in the host tool, and it is worth doing it on a copy. Lighting changes the reading of height more than most people expect, especially in a scene with long sheds. Keep the camera positions you chose, and resist the urge to relight between views. A set of images lit the same way reads as one scene; images lit differently read as three separate proposals.

5 Handover discipline

5.1 Licence and reuse

Exports are licensed for permanent commercial use, which covers the internal reviews and client presentations most crane scenes are made for. The limits are worth knowing before a file leaves the organisation: no resale of the raw files, and no use for training AI models. The authorization statement sets out the terms in full. If a contractor wants to reuse the scene in its own tools, that is a conversation to have early rather than after the file has been passed around. Put the terms in the covering note, not in a message thread nobody will find again.

5.2 Versioning

Keep one folder per site and number the exports, rather than saving over the same file. A crane scene changes when the building masses change, and an old version is often the one that explains a decision. Note the extent, the imagery date and the edits in a short text file beside the export. When someone asks which version was shown in a meeting, the answer should take ten seconds to find. A date in the file name is cheap and it settles most of those questions.

Open the GenAnywhere app and export a site for a crane study

6 Testing before you present

6.1 A three-point import check

Three checks catch most import problems: scale against a known building, up axis, and ground contact under the crane base. Run them every time, even when the same file imported cleanly last week, because host tools update. If all three pass, the scene is ready for the crane and for the meeting. If one fails, fix it before adding anything else, since a misplaced machine on a good site is harder to diagnose than a bad site on its own. Run the checks in the same order every time and they become a habit rather than a task.

6.2 Fix here or fix there

Some problems are better solved by exporting again, and some by fixing locally. A missing building usually means the extent clipped it, so go back and reframe. A material that reads badly is a host-tool problem. Decide which side of the fence a fix belongs to, write it down, and avoid doing both at once. Doing both at once is how two versions of the truth appear in one project folder. One owner for the site and one for the machine keeps the fixes in the right place.

6.3 When the machine moves

Cranes move, and a scene with a crane bolted into the ground will not survive that. Keep the machine as a separate object with a clear pivot so it can be repositioned for the next option. If several positions are being compared, save them as separate objects or separate files rather than as one scene with three machines in it. A reviewer should be able to tell at a glance which position is being discussed. If the positions are close together, a small marker or a labelled camera per option helps more than a wider view.

7 FAQ

FAQ-1 Does the GLB include the crane?

No. The export contains the site: terrain, water, vegetation and building masses with your edits. The crane is added in the receiving tool from a plant or manufacturer model. That keeps the exported file small and lets one site support several machine options without being regenerated each time. It also makes the boundary between site data and plant data visible to everyone who opens the file.

FAQ-2 Which applications can open the file?

The common 3D, BIM, GIS and game engine tools, with the usual caveats about version and import settings. Blender, Unreal Engine, Unity, Revit, Rhino, SketchUp and ArcGIS Pro all appear in GenAnywhere's published workflows. Test in the exact version you plan to use, because behaviour can differ between releases of the same application. If the file is going to several teams, ask each one which version they run before promising a single export.

FAQ-3 Why is my crane the wrong size?

Almost always a unit mismatch between the site export and the crane asset, or a scale applied on import. Compare a known building against its drawing dimension, then scale the machine rather than the site. Check the crane file's own units too, since some libraries ship in millimetres and some in metres. Fixing the asset is safer than scaling the site, because the site is the part other people rely on.

FAQ-4 Can I send the file to a contractor?

Yes, as an exported scene, within the licence terms. It is not a survey and should not be presented as one, so label it as context and say which parts came from map data. The contractor can add its own plant, sequence and site setup. Read the authorization statement before the file goes outside your organisation, and keep a copy of the terms with the export. That record answers most questions before they become a dispute.

See how a GLB moves from a map into a crane study

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.