Architecture teams keep asking the same question in different words: should we model the site ourselves, or generate it from map data? The honest answer depends on whether you are describing a place that exists or proposing one that does not yet. halfmaps is built for the first job — it converts OpenStreetMap features and terrain into styled 3D city meshes you can export. GenAnywhere is built for the second — content-first shaping of the design itself. They look similar in a screenshot and behave nothing alike in a project.
The Short Version
halfmaps produces context: buildings extruded from footprints, roads, water, and terrain, packaged for Rhino, Blender, SketchUp, or a 3D printer. GenAnywhere produces design: the massing, the street relationship, the character of the intervention, revised live as decisions land. One tool answers "what is there?" The other answers "what are we adding, and does it work?"
What halfmaps Does Well
Site context used to be a tax on every project. Someone had to trace footprints, estimate heights, and model blocks that would never appear in a rendering. halfmaps removes most of that labor. Pick an area, adjust the style of buildings, roads, water, and terrain, check the live preview, and export.
Formats that fit real pipelines — GLB, glTF, OBJ, STL, 3MF, and DXF cover visualization, CAD, and fabrication.
District-scale coherence — one dataset and one style setting produce a base model that reads consistently block to block.
Neutral base geometry — the output describes existing conditions without implying a proposal, which makes it fair ground for option studies.
Simple economics — $15 for a single area with unlimited re-exports, or $49 per month for the Creator plan, with no free tier beyond the example maps.
For feasibility studies, competition context, shadow and view tests, or a physical site model, that is a lot of value for very little ceremony.
Where the Map Ends
Map data is a record, not a design. Heights come from tags and estimates. Facades are extrusions. Interiors do not exist. Public realm is a surface, not an authored experience. Style controls change how geometry is presented; they do not give you a way to design it.
There is also no design revision model. You can restyle an area and export again, but you cannot hold approved elements fixed while changing one contested corner. Teams that try to author their proposal inside a map exporter end up fighting the tool's entire purpose.
What GenAnywhere Does Differently
GenAnywhere starts from intent rather than inventory. It is a shaping environment: you construct the place, test it against its context, and refine it in the room where decisions are made. Revisions are edits, not regenerations, so what has already been approved stays untouched while the open questions get worked.
That matters most in reviews. The typical failure mode is a meeting that ends with "come back when you've modeled that option" — a deferral caused by tooling latency, not by disagreement. When reshaping a corner or retesting a street wall takes minutes instead of a day, the review can actually conclude.
Using Both Without Losing Time
Set the frame with halfmaps. Export a trimmed context model at a neutral level of detail.
Author the proposal in GenAnywhere. Keep the intervention separate from the context so each can change independently.
Match representation levels. If the context is richly styled and the design is not — or the reverse — reviewers will confuse polish with quality.
Version the seam. Note which map export the design was tested against; open data changes over time.
Which One Should You Buy?
If your deliverable is a study of existing conditions — a site analysis, a massing envelope against real neighbors, a printable block model — halfmaps is the more direct purchase. If your deliverable is the design and it will change dozens of times, GenAnywhere is the tool that survives the process.
Most serious teams eventually need both, and the split is clean: halfmaps establishes the world, GenAnywhere shapes what you add to it. The mistake is expecting either one to do the other's job.
Top comments (0)