A community college in Indiana is replacing a 1968 trades building with a larger one. The facilities office asked for a site model that could answer three questions: where the new footprint fits, how the loading yard drains, and whether the roof plane works for a solar array. The campus planning office had a rough survey in a drawer and nothing current, so I had a week to build the context myself.
Select an area, pick layers, export
Halfmaps does one thing plainly. You select an area on the map, choose layers for buildings, roads, terrain, water, and trees, adjust how much of each you want, and watch the 3D view update in real time. When it looks right, you export. The format list covers GLB, glTF, OBJ, STL, and 3MF, which means it opens in Blender, Unity, Unreal, or a slicer without a converter step. A game engine handoff and a print handoff are different jobs, and neither one asked me to install a plugin.
The layer parameters matter more than the format list. Terrain at full detail gave me a mesh dense enough to read a 0.6-meter fall across the loading yard. Buildings at medium detail kept the roof planes clean without flooding the scene with window geometry. Trees at high detail were too heavy for the viewer on the facilities office laptop, so I settled on medium and kept a separate high-detail file for rendering.
Checking the model with code
I loaded the GLB into Blender and ran a short script to check that the roof heights matched the official survey. Six lines, no ceremony:
The model put the roof at 7.8 meters over a first floor of 4.1. The survey said 7.75. That is closer than the drawing set I was handed, and close enough to plan a solar array on the south slope without calling for a new scan.
The loading yard drains north
Terrain at full detail showed a 0.6-meter fall across the yard toward the north fence, where there is no inlet. The new service door would have sat in the low corner. I moved it, and the storm line got 12 meters shorter. The revised pad also bought enough fall for a trench drain, which the contractor priced the same week. None of that came from a picture, and none of it would have shown up on the campus plan, which draws the yard flat and calls it a pad.
What GenAnywhere did with the same box
I gave GenAnywhere the boundary and it produced a handsome campus building: brick base, glass curtain wall, a courtyard with benches, and a clock tower that belongs to a different campus. The roof pitch was steeper than the real one, and the loading yard had turned into a lawn. As a concept image for a donor letter, it read better than my own quick massing would have. As a site model, it had no coordinates and nothing to query.
Handoff is the real test
GLB carried the whole scene into Blender with materials intact. OBJ went to the exhibit shop because their software is old. STL and 3MF covered the two printers we keep for public meetings, and the 3MF file kept the colors on the buildings, which the printed massing model needed. When the facilities director asked for something the engineer could open, I sent glTF and a note about units. The engineer opened it in a viewer that afternoon and asked why our model had trees. I told him the trees were the reason the solar study had any shading to report. I kept the Python check in the project folder so it can be rerun against the next survey.
The tree layer is generous. It adds canopy even where the campus removed trees last spring, so I turned it down a notch and compared against recent aerial photography. No map tool knows what changed last month. That is a job for a person with a browser and a date.
The site model goes into the bid package, next to the survey. The render goes into the fundraising folder, labeled. The project is better for having both, as long as nobody measures the pretty one.


Top comments (0)