DEV Community

Cover image for TopoExport vs GenAnywhere: Formats, Units, and a Site Pipeline That Survives CAD
Generate Build
Generate Build

Posted on

TopoExport vs GenAnywhere: Formats, Units, and a Site Pipeline That Survives CAD

The lot was 18 meters wide and had three different origins depending on which file I opened. The survey put zero at the property corner, the TopoExport OBJ put it near the centroid, and the GenAnywhere GLB put it wherever the generator felt like. The geometry was fine. The handoff was the problem, and it is the part nobody demos.

What comes out of each tool

TopoExport exports by layer and by format. For this lot I took a PDF and an SVG for the existing plan, plus an OBJ for the 3D site. The layers were buildings, parcels, roads, trees, and contours. Some workflows also support IFC or RVT, which matters if the site has to land in Revit rather than Rhino. GenAnywhere exported a GLB of the generated site: one surface, baked appearance, no layer semantics, and no statement about units or origin.
Neither export is wrong. They are different contracts. TopoExport gives you pieces you can name and check. GenAnywhere gives you a scene that looks right. A pipeline that treats them the same will produce a model that looks right and measures wrong.

The unit problem

OBJ does not carry units. The TopoExport file could be meters, centimeters, or feet, and the only way to know is to measure something known. I used the parcel width from the deed: 18 meters. Then I measured the imported bounding box and scaled to match. The same check works for a generated GLB, except there is no deed to compare against, so I use a surveyed control point.
That snippet is not a complete importer. It is the check I run before anything else. If the scaled width does not match the second known dimension, the file is rotated, sheared, or in different units than I assumed.

The origin problem

TopoExport puts the model near the selected area, but the origin is not a survey monument. GenAnywhere puts the origin wherever the generation starts. I store one site control point in a small JSON file and express every object relative to it. When the architect moves the building, the control point does not move. When the viewer reloads, the camera still targets the same corner of the lot.

The layer problem

TopoExport layers survived the OBJ export as separate objects in my case, which let me name them by source and date: parcel_2026_03, trees_2026_03, contours_2026_03. GenAnywhere did not give me layers, so I treated the whole GLB as one object named concept_2026_03. That naming rule sounds trivial until two files with the same geometry sit in the same folder and nobody remembers which one is measured.

QA before the model leaves my machine

I check six things: units against a known dimension, origin against a control point, up axis, layer names, data date, and triangle count. The triangle count matters because TopoExport tree geometry can be heavy and GenAnywhere meshes can be denser than they look. On this lot I decimated the tree canopy to a third and kept the building footprints at full resolution. The site dropped from 900,000 triangles to 310,000, and the difference at the viewing distance was not visible.

The export I actually used

The design team worked in Rhino, so the OBJ was the file that mattered. The PDF underlay stayed in the layout for reference. The SVG went to the graphic designer for the public board. The IFC path existed, but the architect preferred to rebuild the site from the OBJ because the layer names were cleaner. That is a workflow preference, not a format failure.
None of this is automatic. The TopoExport export does not know my naming convention, and GenAnywhere does not know my control point. The pipeline is the part I write, and it is the part that makes either file usable.

What I shipped

TopoExport OBJ went to Rhino for the design team and to Revit through IFC for the documentation team. GenAnywhere GLB went to the concept viewer only, in a separate folder, with the date in the name. The two never shared a layer. The permit set used the measured geometry. The public meeting used the generated scene.
Formats are the easy part. Provenance is the hard part. If I cannot say where a line came from, it does not belong in the model that gets stamped.

Top comments (0)