DEV Community

Cover image for PlaceMaker vs GenAnywhere: Georeferencing a Fairground the Hard Way
Generate Build
Generate Build

Posted on

PlaceMaker vs GenAnywhere: Georeferencing a Fairground the Hard Way

The brief was a master plan for a county fairground: 38 acres, a dirt oval, a timber grandstand, two livestock barns, and a rail siding that dead-ends along the east fence. The county wanted one model that planning and engineering could both open. I had two days and one coordinate question that nobody had answered. My rule for county work is simple: if I cannot explain where a line came from, I do not put it in the model.

What the box actually imports

PlaceMaker works the way I wish more site tools did: find the area, drag a box, tick what you want. I took aerial imagery, terrain, buildings, roads, the rail line, water, and trees. The output arrived as separate objects with layer names, not one merged mesh, which is the first thing I check. Merged geometry is where 3D modeling goes to die.
Why I kept the layers apart
Buildings arrived as closed solids, roads as polylines with widths, water as polygons, and trees as points with a canopy radius. I kept each in its own collection and prefixed the names with the source. That sounds fussy until someone asks why the grandstand floats 20 centimeters above the terrain mesh. It floats because I moved it, and the name tells them that without a phone call.

Elevation checks I did by hand

The terrain mesh claims to follow the source DEM, so I sampled it at three known points: the grandstand foundation, the track crown, and the rail siding. Differences against the county's LiDAR spot shots were 0.2, 0.3, and 0.4 meters. Good enough for site planning, not good enough to set a finish floor without a survey. The railway layer carried its own grade, about 1.1 percent through the siding, which matched the profile I had. That 0.4-meter error at the siding is the one I would not ignore on a platform design.
Rail is not decoration

On the AI scene, the siding came back as a paved path with a tree line on it. On the real import it is a polyline with elevation and a switch. That matters because the new exhibition hall needs 7 meters of clearance from the centerline and the siding cannot move. When a layer carries geometry, you can measure against it. When it is a texture, you cannot. I measured 7.2 meters from centerline to the proposed wall, and the extra 0.2 is why I sleep.

Running the same boundary through GenAnywhere

Four minutes, and the fairground looked like a fairground: oval, barns, grandstand, gravel. It also turned the livestock barn 90 degrees, made the oval a perfect circle, straightened the creek, and produced five buildings the site has never had. For a public meeting slide, fine. For georeferencing, no. GenAnywhere does not know or care where the boundary sits on the earth. It generates a scene that resembles the prompt, and it is good at that.

Exports and where each went

The fairground site model went out three ways. OBJ to the visualization team for a Cesium viewer, GeoJSON of the rail and parcel to the county GIS, and DXF to the civil engineer for grading. Every layer name in the export carries a download date. That is data provenance, and it is the only reason anyone trusted the model six weeks later when a fence line moved. The OBJ shipped with the aerial stitched at roughly 15 centimeters per pixel, which is sharp enough to read the track surface and light enough that the browser viewer does not stall.

What broke

The one real failure was the tree layer, which clipped at the property edge and left a bald strip along the north fence. I extended it with two dozen trees placed from the orthophoto. A generated scene would have filled that strip without being asked, and it would have been wrong in a way nobody could check. That is the trade in one picture: convenience on one side, verifiable edges on the other.

What I would tell the next person

If you need a coordinate reference system that survives review, build from imported layers and check three elevations yourself. If you need a picture for the board by Friday, generate it and label it as a picture. The fairground project used both. Only one of them went into the construction set. The county planner opened the GeoJSON in QGIS without calling me for help, which is the highest praise I can give an export.

Top comments (0)