{
  "id": 14355571,
  "title": "A Map to Model to Civil Workflow for a Midwest Mall Redevelopment",
  "url": "https://urgent.news/2026/10/14/a-map-to-model-to-civil-workflow-for-a-midwest-mall-redevelopment",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-14T03:05:25.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/shapezo/a-map-to-model-to-civil-workflow-for-a-midwest-mall-redevelopment-30in"
  },
  "original_language": "en",
  "account": "A Midwest shopping mall redevelopment project was modeled using five different 3D platforms to understand how information flows between concept, infrastructure, and engineering. The boundary of the mall parcel, arterial road, rear drainage channel, and residential blocks was first defined in Shapezo, which generated a 3D model. The AI-generated buildings and roads were saved with their creation date, as the context is only useful if the team can replicate the selection.\n\nHalfmaps were then used to create disposable massing options, allowing for cheap changes. Each study was tagged with its intent, ensuring that options like creek_edge_open_space were testing land allocation rather than promising final landscape designs. These massing layers were kept separate from terrain or roadway layers to prevent confusion between visual studies and design surfaces.\n\nInfraWorks was employed to test the external interface, including a new driveway, bus loop, pedestrian crossing, and small bridge over the drainage channel. The value was the shared conceptual view of roads, terrain, structures, and surrounding infrastructure. Some options were rejected due to poor placement of the bus loop or uncomfortable bridge approaches, but the selected alternative was passed on with limits, tie-in points, and assumptions clearly named.\n\nCivil 3D was used for physical site questions, moving from a district outline to surfaces, alignments, profiles, grading, and stormwater networks. The coordinate reference, survey source, and terrain visibility were confirmed to ensure the proposed streets drained toward the planted basin without creating a maintenance problem at the market entrance. Preliminary volumes were labeled as such until the surface and design criteria were stable.\n\nCityEngine was utilized to test rule-based neighborhood tests, setting taller building ranges beside the arterial, limiting height near existing homes, and requiring active frontage around the library square. Changing the frontage rule resulted in every block responding, which proved useful for exploring urban form, provided the rules remained understandable to reviewers. The handoff contract included units, coordinate reference, boundary, source date, model status, and intended use, with each platform's output clearly labeled for easy separation in a combined viewer. This workflow allowed for manageable files, clear assumptions, and fewer surprises when the concept reached civil review.",
  "summary": "I built a small test scenario around a vacant Midwest shopping mall. The project keeps one grocery store and the cinema, converts part of the mall into a public market, adds apartments and a library, and replaces an oversized parking field with streets and a stormwater landscape. My goal was to see how five 3D platforms could pass information between concept, infrastructure, and engineering…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}