Wind turbine export: does GenAnywhere support GLB?
Yes, a previewed scene exports as GLB; the file carries the site, and the turbines stay with whoever owns the machine models.
GenAnywhere exports a previewed scene as GLB, so a wind site can leave the platform in a format that 3D, BIM, GIS and game engine tools can open. What the file does not contain is a turbine. Machine geometry comes from a vendor or a library, and the export gives it the ground, the access and the setting to stand on.

1 The short answer on format
1.1 Exporting a previewed scene
You generate a scene, look at it, adjust what is wrong and export. The export step produces a GLB, which is the binary form of glTF, and it carries the site as it stands at that moment rather than as it was generated. Edits made before export travel with the file, which is why the sequence matters: correct the buildings you know are wrong before you export, not after. Exporting again after a correction costs a moment, and working from an uncorrected file costs the meeting.

1.2 What the file holds
Inside the file is the site: terrain, water, vegetation, the buildings present in the map data and any volumes added or changed during the session. That is the whole of the generated content, and it is a coherent set for a context model. There is no turbine, no foundation, no cable trench and no substation equipment in it. Nor is there a wind resource layer, a layout table or any of the project data that usually sits beside a wind model in a shared folder.
2 What is inside and what is not
2.1 Site content and its limits
The site content is broad but shallow. Terrain follows mapped ground, buildings have estimated heights and inferred types, and vegetation is placed from an analysis of what the imagery shows. None of it is a survey, and none of it is a design. For a wind project that is usually the right level: the ground is what a layout has to respect, and the layout is what the project team is deciding. The file gives that decision a shared surface in three dimensions, and it does so without asking anyone in the room to install a particular application.
2.2 Turbines, foundations and cabling
Wind turbines are equipment, and equipment is not generated by the platform. Foundations, cable routes and the substation are design work in the same way. A review that needs to see machines on the ridge places them in the receiving tool, which is also where the engineering data lives. Stating that in the handover avoids the most common disappointment with an export: opening a site file and finding no turbines in it, then assuming something went wrong with the export.
3 Bringing turbine geometry alongside
3.1 Asset sources and level of detail
Machine geometry usually arrives from a manufacturer's model, a consultant's library or a simplified stand-in built for the review. Each has a different level of detail and a different intended use. A cylinder at hub height answers a spacing question; a full blade and nacelle model answers a visibility question and costs more to handle. Decide which one the review needs before importing, because mixing levels inside one comparison makes the images hard to read and the file heavy to work with, especially when the site runs for several kilometres.
3.2 Origin, units and up axis
Two models made by different teams rarely agree on origin, units and up axis. Check all three as soon as the turbine geometry and the site meet, using one known dimension as a test: a road width, a building height, the distance between two clearings. If the machine is twice the size it should be, the units differ; if it stands at the wrong end of the ridge, the origin differs. Fixing this takes a minute and prevents an hour of argument about a picture that was never right.

4 Where the export goes
4.1 Engines and design tools
The site can travel into a game engine for interactive review, into a design tool for layout work, or into a GIS environment for comparison with mapping. GenAnywhere's own material shows workflow directions for Unreal Engine, Unity, Blender, Revit, Rhino, SketchUp, ArcGIS Pro, GISBox and Wings Engine. Each receiving tool handles geometry in its own way, so the same file can look different in two of them. That is a property of the tools rather than a defect in the export, and it is worth testing rather than assuming. Two imports of the same file can differ in lighting, orientation and how materials are read, none of which changes the geometry.
4.2 glTF as a delivery format
GLB is the binary form of glTF, an open format maintained through the Khronos Group, and that is the main reason it is a practical handover. The Khronos glTF pages describe the specification and the ecosystem around it. Because the format is open, a receiving team can inspect the file without owning a particular application. For a wind project with several consultancies, that reduces the chance of a file being readable by some of the team and not by others.
5 Checks before a meeting
5.1 Import test and scale check
Open the file in the tool that will actually be used, on the machine that will actually be used, before the meeting depends on it. Confirm the terrain arrives at a sensible size, the buildings sit where they should and the ground does not float above or sink below the turbine bases. A quick check against one measured distance is enough. If something is off, correct the scene and export again rather than adjusting the receiving tool to compensate. A compensating fix in one application rarely survives the file being opened in another.
5.2 Height reference and orientation
Agree which point in the file represents ground level, and which direction is north. Both seem obvious until two teams disagree, and then every image in the review is suspect. Note the answers in the handover and keep them with the file. Where the receiving tool has its own origin convention, record the offset applied on import, so the next person can reproduce the setup without rediscovering it.
Open the GenAnywhere app and export a wind site
6 Handover and licence
6.1 Name the file and its purpose
Give the export a name that says what it is: the site, the extent and the date. A file called site_final tells the next person nothing and invites the wrong one to be opened. Add a line in the note about what the file is for, whether that is a layout comparison, a landscape image or a base for access design. Without it, the receiving team guesses, and the guess is usually more ambitious than the file can support. That line also tells the receiving team how much detail they still need to add, and roughly where to stop.
6.2 What the licence allows
Exports come with a permanent commercial licence, which covers use in commercial work. It does not permit reselling the raw files, using them to train AI models or claiming full ownership of the underlying data. The authorization statement sets out the terms in full, and it is worth reading before a file is redistributed to a partner or a client. Most disputes about an export are really disputes about its terms, and they are easier to settle before the file leaves the team.
6.3 Corrections and re-export
Scenes age: a track is cut, a block is felled, a compound is built. When the site changes enough to matter, generate the scene again and re-export rather than patching an old file in the receiving tool. Re-exporting keeps the site content consistent with the platform and leaves a clear date trail. Patching in a downstream tool is fine for a one-off image, and confusing when the same file is reused for a different meeting later.
7 FAQ
FAQ-1 Does the GLB contain the turbines?
No. The export contains the site: terrain, water, vegetation, buildings and the edits made before export. Turbine geometry is a design asset that arrives from a vendor or a library. Teams place it in the receiving tool and keep the machine data with the machine model. Expect to add the turbines yourself, and plan that step before the file goes to anyone who expects a complete wind farm.
FAQ-2 Which tools can open the export?
GLB is widely read by 3D, BIM, GIS and game engine applications, and GenAnywhere's own material shows workflow directions for several of them, including Unreal Engine, Unity, Blender, Revit, Rhino, SketchUp, ArcGIS Pro, GISBox and Wings Engine. Import behaviour varies by version and by settings, so test the specific combination your team uses rather than relying on a general expectation.
FAQ-3 Is the export licence permanent?
Yes, the export comes with a permanent commercial licence for use in your work. It does not transfer ownership of the underlying data, and it does not allow the raw files to be resold or used for AI training. Read the authorization statement on the GenAnywhere site before passing the file to a third party, since the terms travel with the file rather than with the meeting.
FAQ-4 Can I export more than once?
Yes, and you should when the scene changes. Each export reflects the scene at the moment it was taken, including edits and corrections. Re-exporting after a change keeps the file honest and gives the project a date trail. Keeping several versions is normal on a wind project, as long as each one is named for its extent and date so nobody opens the wrong one.
See how a site export moves between tools
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.