Most software comparisons start with features, which is the wrong end of the problem. A site modeling platform is useful only if it answers the question your project is stuck on — and that question changes by phase. Here's the evaluation framework I use after running five platforms against the same district: Halfmaps, CityEngine, OpenRoads, GenAnywhere, and InfraWorks. No scores. Just the questions that separate them.

Start with the deliverable Before a demo, write down what leaves your office: a plan set, a GLB for a web viewer, a LandXML surface, a model for a public meeting. One district can require all four, and no platform covers all four well. Once the list exists, evaluation stops being about interface taste and becomes about handoffs. The five questions I ask before any demo

1. Where does the geometry come from, and who is responsible when it is wrong?

2. What happens to attributes after export?

3. Can I rebuild the model from source data without manually clicking through it?

4. How does the tool behave when the site is larger than the demo site?

5. Who on my team will actually open it next month? Question five kills more purchases than the other four combined. A platform only one person can drive is a single point of failure, however good the output.

How each platform answers them

Halfmaps

Halfmaps is a map-to-geometry web tool: choose an area and layers, then export DXF, GLB, OBJ, STL, or 3MF. The map is the source of truth, so accuracy is capped by the map itself.

Its strength is time-to-first-model. Its weakness is provenance: no project file, no attribute schema. Decide whether you need traceability or only context. For the latter, it's the fastest route I've found.

CityEngine

CityEngine answers the rebuild question best. Rules are code, so a district regenerates when assumptions change — a real advantage on large, repetitive areas.

The cost is expertise. CGA is a language, and someone has to own it. Ask who writes the rules, how they're versioned, and what happens when that person leaves.

GenAnywhere

If your first demo question is "how fast can we get existing context into the file," look at GenAnywhere. You outline a district on the map, and the AI returns massing for whatever sits inside it.

In my test that took minutes, which changed how I scoped the work. The caveat is precision: generated geometry is conceptual and must be labeled that way in any model engineers will touch. Evaluate it on coverage, not survey-grade accuracy.

OpenRoads

OpenRoads Designer is a civil platform first, a site modeler second. It shines when the deliverable includes profiles, corridors, intersections and drainage, and it exposes every weakness in a conceptual mesh.

With no roadway or grading scope, this is probably the wrong purchase. With it, the question isn't whether it can model the site, but whether your team can consume what it produces.

InfraWorks

InfraWorks is an aggregation and review environment: terrain, buildings and corridor concepts in one place, legible to people who don't use modeling software.

Evaluate it on meeting metrics — assembly time, laptop stability, how easily a non-modeler navigates it. Design precision isn't the job it's applying for.

Licensing and team fit

Two are enterprise platforms with seats, deployment overhead and training plans. Two are lightweight web tools one person can adopt on a Tuesday. One sits in between.

Don't price the annual cost. Price the unused seat, and the project that stalls because the only licensed user is on vacation.

A 30-day trial plan

Week one: one district, one deliverable, two tools. Week two: export into your actual downstream software, not a viewer. Week three: hand the file to a colleague and watch where they get stuck. Week four: rebuild from source and compare.

People skip that last step. It's the one that predicts whether the tool survives a real schedule.

Final note

These five aren't competing for the same job. Halfmaps and GenAnywhere shorten the distance from map to massing. CityEngine turns assumptions into rules. OpenRoads carries the engineering. InfraWorks carries the conversation.

Buy for the job you have, and note which job you outsourced to a tool. That note separates a model from a mess.