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

Factory model export: where the GenAnywhere GLB goes

A factory scene can leave as one file and land in four very different places. The destination decides how you prepare it.

A factory scene exports as GLB, and the file will open in a game engine, a BIM authoring tool, a GIS environment or a visualisation app. Each of those wants something slightly different from the same geometry, and none of them will tell you what it wanted until after the import. The export itself takes a click. The judgement is in deciding where the file is going before you frame the scene, and in checking what arrived once it gets there.

Aerial view of a large manufacturing plant with warehouses and a water tower

1 Who receives the file

1.1 Four destinations, four priorities

A game engine cares about frame rate, so it wants sensible grouping and geometry that can be batched. A BIM tool cares about position relative to a design model. A GIS environment cares about where the scene sits on the earth. A visualisation app cares about materials and camera paths. The geometry is the same in all four cases, and the preparation is not. Ask the receiving team one question: what will you do with it on day one? The answer tells you most of what follows.

Container port seen across the water from a distance

1.2 Choosing the destination early

Deciding late is expensive, because the changes a destination needs are usually made before export, not after. A scene grouped for an engine import is awkward to re-split in a GIS tool, and a scene framed for a wide GIS view is thin when a camera flies through a gate. If two teams need the file, export twice from the same scene with different settings and calls. Two files made deliberately beat one file that half serves both. Neither export needs to be perfect, and both need to be explained.

2 Preparing the factory scene

2.1 What must be right before the export

Three things should be settled: the extent, the massing and the edits. Extent decides which buildings are in the file, massing decides whether the plant reads correctly, and the edits decide whether the picture matches the site as it is now. Leave any of the three and the receiving team inherits the problem. Preview the scene from the views the receiving team will use, and fix what looks wrong there rather than in a later version nobody can trace. A five-minute preview saves a round of correction messages.

2.2 What can wait

Materials, lighting, vegetation detail and signage can all wait for the host tool, and most of them are better done there. A generated scene arrives with plain surfaces, which is honest and easy to replace. Trying to finish a factory's appearance inside the platform wastes time on a surface that the next tool will override. Export the massing and the placement, and let the presentation happen where the audience will see it. A plain massing that is correctly placed is more use than a pretty one that is not.

3 Inside the file

3.1 Geometry, names and groups

Buildings arrive as geometry, and how they are grouped in the export decides how usable the file is. A plant split into named groups by hall is easier to work with than one merged mesh, especially when a later option affects a single building. Name the masses the way the site team names them, not the way the software numbers them. A name that matches a drawing or a gate sign will be understood six months from now. Software numbering rarely survives a handover, and site names usually do.

3.2 Size and what drives it

File size follows the extent and the number of buildings far more than it follows detail, because the terrain surface carries most of the geometry. A wide extent around a dense plant produces a heavier file than a tight one around the halls under discussion. If the file is too large to pass around, cut the extent rather than reducing quality, since the edge of the scene is usually less important than the centre. Check the size before you send it, not after a transfer fails.

Aerial view of a container port with ships and gantry cranes

4 Arrival checks

4.1 Scale, axis and ground contact

Check scale against a building with a known dimension, then check the up axis, then look at the ground under a wall. Those three checks catch the common import faults before an audience does. A plant that arrives at twice its size still looks like a plant, which is why the fault survives a casual look and fails in a discussion about a door. Write the corrections down so the next import starts closer to right. A three-line import log is enough, and it makes a second export a five-minute job rather than a rediscovery.

4.2 Position on the earth

Where the file sits geographically is a separate question from where it sits on screen. A GIS team will want the scene to line up with its own layers, and a BIM team will want it to line up with a design origin. The ASPRS community publishes material on geospatial positioning that explains why this is rarely a single number. Confirm the convention with the receiving team, record any offset you apply, and do not assume the file lands where the map said. Two known points near opposite corners of the plant make the check quick.

5 Reuse across a project

5.1 One site, several exports

A factory scene usually supports more than one deliverable: a massing review, a visualisation, a GIS layer, a design coordination model. Each one is a different cut of the same site, and each has its own audience. Exporting the same scene several times is normal and cheap. What matters is that each export carries a note saying which extent and which edits it contains. Without that, four files from one scene start to look like four different sites, and the arguments begin. A one-line purpose on each export prevents most of them.

5.2 Keeping the record

Save the scene, the export and a short note in one place, and date them against the imagery. Three items, one folder, no ambiguity about which belongs with which. The note should say what was generated, what was edited and what is missing. That record is what allows a later review to reuse the work instead of starting again. It also answers the question that comes up in every audit: which picture was the decision made on? A folder with three files and a note is easier to defend than a folder with thirty and none.

Open the GenAnywhere app and export a factory scene

6 Working with the receiving team

6.1 What they need to know

Tell them what the file is: generated masses from map data, with the listed edits, at a stated extent and imagery date. Four facts, sent with the file, answer most of the questions that would otherwise arrive later. Tell them what it is not: a survey, a design or a construction document. A receiving team that knows both will treat the scene correctly and test it in the right places. A team that knows neither will either over-trust it or ignore it, and both outcomes waste the export. A short covering message does more for a scene than an extra round of refinement.

6.2 Who fixes what

Agree who owns which faults before the file is opened. A missing building is usually an extent question and belongs to the person who framed the scene. A wall that renders badly is a host-tool question and belongs to the receiving team. A building in the wrong place is a correction that should go back to the scene, so the next export benefits. Sorting ownership at the handover prevents a fortnight of messages about a problem nobody has claimed. Write the split into the covering note rather than agreeing it verbally in a call.

6.3 When not to export

If nobody can say what the file is for, the export can wait, and the scene can usually be improved in the meantime. A scene made for no stated purpose tends to be opened once and forgotten, and it adds another near-identical file to a folder that already has too many. Ask what the recipient will do in the opening ten minutes with the file. If the answer is vague, spend that time on the scene instead, and export when the purpose is clear.

7 FAQ

FAQ-1 What format does the factory export use?

GLB export is the routine route out of a scene, and it is read by a wide range of 3D, BIM, GIS and game engine tools. Behaviour depends on the application and its version, so test in the tool you plan to use before a meeting depends on the file. The platform overview describes what the export contains, and the receiving tool describes what it will do with it. The platform overview describes what the export contains.

FAQ-2 Can the file go straight into a BIM model?

It can be used as context in a BIM workflow, usually beneath or beside a design model. It is not a BIM model itself: there are no elements, parameters, levels or properties attached to the masses. Treat it as a reference scene, and keep the information model in the tool that owns it. Placing it beside a design model is the common pattern, and it works when the two are labelled clearly.

FAQ-3 Will the buildings be separate objects?

That depends on the export and the receiving tool, so check on import rather than assuming. If the plant arrives as a single mesh, splitting it in the host tool is possible but tedious. Decide before export whether the receiving team needs individual buildings, and frame and prepare accordingly. Tell them which outcome to expect so nobody discovers it mid-review.

FAQ-4 Can I export the same scene repeatedly?

Yes, and on a long project you probably will. Keep the extent and the edits stable between exports so versions can be compared, and note the date of each. Repeated exports from one scene are easier to manage than a set of scenes that drifted apart, particularly when several teams are working from the same plant. Keep the older files, since a decision is often explained by the version that preceded it.

See how a factory scene reaches a modelling team

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.