#CityEngine
A Quarry Reuse Pipeline: MicroStation, TopoExport, Meshy, GenAnywhere, CityEngine
A 240-acre quarry reuse plan built with a DGN survey base, TopoExport terrain, Meshy photo-to-mesh assets, GenAnywhere generated context, and CityEngine scenarios. The hard parts were coordinate checks, layer discipline, and not mistaking generated geometry for survey data. ## The deliverable and the site Harlow Quarry is a former limestone quarry and cement plant in upstate New York. The county asked for a planning-level package: existing conditions, a terrain surface, a context model, and three housing scenarios for the east bench. The site is 240 acres, with 22 acres of water. The plant stopped in 2001 and the county bought the land in 2023. The only new survey data was a boundary file and 12 spot elevations. Everything else came from existing records or had to be labeled as an estimate. ## MicroStation: the survey base The county supplied a DGN in EPSG:2260 with the boundary, deeds, and check points. I kept the survey as the only writable file and attached everything else as references: 1998 orthoimagery, plant record drawings, and parcel polygons. I traced the rim, rail spur, and building footprints onto separate levels. The level names were plain: SURVEY, RIM, RAIL, BLDG_EXIST, BLDG_INTERP, CTX_GENERATED. Units were set to feet at the start. This file became the coordinate authority for every later import. ## TopoExport: terrain mesh and checks I outlined the property boundary in TopoExport and enabled contours, waterways, and cadastral parcels. The export gave me an OBJ mesh, a DXF of vectors, and an SVG for a quick exhibit. The mesh arrived in its own local frame. I scaled and georeferenced it against two survey control points, then compared it with the 12 spot elevations. Most benches were within a foot. The highwall was not. A height field cannot represent a vertical face, so the rock wall read as a steep slope. I clipped the terrain at the rim and kept the surveyed rim line for safety setbacks. The mesh worked for drainage and trail grading, but not for the rim condition visitors will stand next to. ## Meshy: photo-to-mesh, with a label The crusher house was demolished in 2009. I had 14 archival photographs and no measured drawings. Meshy converted the photographs into a textured GLB mesh. I imported it, scaled it to a known door height, and placed it on BLDG_INTERP. The result was plausible, not accurate. The roof pitch and conveyor connection were wrong. It worked for an exhibit and a context view, and it did not go into any area or cost calculation. Photo-to-mesh assets are useful for communication, never for dimensions. ## GenAnywhere: generated context The northeast 18 acres had no survey. In GenAnywhere I boxed that corner on the map, and the AI filled it with ground and buildings. The result came back as a separate context model. I placed it on CTX_GENERATED and used it only for view renders: no quantities, no parcel counts, no grading. The output was fast and coherent, but it invented a few driveways. That is fine for context, not for design; the layer name is part of the deliverable. ## CityEngine: rules and scenarios I wrote a CGA rule file for the east bench: lot width, front setback, height, street width, and a simple roof rule. Three scenario attributes produced 160 large lots, 210 small lots, and a 180-unit cluster. CityEngine rebuilt the masses and street network on each change. I tracked road length, lot count, tree canopy removed, and walk distance to the trailhead. The 210-lot case had the shortest road and the worst tree loss; the cluster kept a central green. The rule file mattered more than any render. It let the planning office rerun the scenarios without rebuilding geometry by hand. ## Handoff notes that mattered • Keep one master DGN and never edit a reference file. • Record the EPSG code in the file name and in the document. • Put generated geometry on its own level and explain it in the legend. • Check terrain against at least a dozen surveyed spot elevations. • Export the scenario rule file with the model, not just the geometry. ## What broke TopoExport's mesh at the vertical wall, Meshy's roof, GenAnywhere's invented driveways, and CityEngine's tendency to produce tidy lots on ground that is not tidy. None of these were fatal, because each output had a label and a job. The pipeline worked when I stopped expecting one tool to be authoritative everywhere. Survey, terrain, context, assets, and scenarios are five different kinds of data. Treating them as one thing is how a planning model turns into a very confident mistake.
dev.to
October 23, 2026 at 8:19 AM
Susannah Cox & Bruno Wu: Designing a VR Environment to Study How We Navigate Differently

Custom assets (3d models and textures) added to ESRI’s CityEngine

#NACIS2026
October 22, 2026 at 4:30 PM
@theodoraward when I studied gamedev in Uni, in the last year there was a course on "procedural content generation" but the first third-or-so was GIS and making digital twins of cities in CityEngine, I still don't know why that was there but I chose Lyon, France for the assignment because my […]
Original post on qaf.men
qaf.men
October 18, 2026 at 8:07 PM
@theodoraward like ok I guess making geometry out of abstract data is "procedural content generation" but we really wouldn't know joy until midpoint displacement and L-systems came up

also I totally failed the CityEngine assignment (twice) :ablobcatcry:
October 18, 2026 at 8:09 PM
A Reproducible 3D Context Pipeline with Cityweft, Shapezo, site3d, Tripo3D, and CityEngine
Multi-tool modeling usually breaks at the handoff. One person exports a scene, another person imports it, and the team loses the answer to a basic question: what does this geometry represent? I use Cityweft, Shapezo, site3d, Tripo3D, and CityEngine as separate pipeline stages and attach a small contract to every artifact. ## Start with a compact artifact contract Before I generate anything, I record the area of interest, coordinate reference, horizontal and vertical units, source date, target format, and intended use. I also set a status: source, imported, generated, conceptual, coordinated, or verified. The status is not decoration. It defines what the next tool or reviewer may do with the model. A generated surface can support a visual check, while a verified alignment can support a controlled design decision. Both can be useful without being interchangeable. ## Use Cityweft for connected context Cityweft is my city-fabric stage. I use it to establish readable relationships between streets, blocks, buildings, public space, and movement corridors. The handoff record includes source coverage, date, visible gaps, and any simplification that affects interpretation. I do not reduce this stage to a screenshot. I keep the context package and a stable view so another person can understand what was included around the project. When the source is mixed, the record says so. ## Use Shapezo for a map-selected first model Shapezo starts with a selected map area. I draw the boundary, and its AI generates a model for that region. This is useful when the location is known but a prepared 3D context is not. For each run, I retain the selected polygon or extent, generation date, visible coverage, and run identifier when available. The output is marked generated. I use it to inspect rough adjacency, massing, and access, but I do not use inferred coordinates as controlled survey data without an independent check. ## Use site3d for terrain and site logic site3d is the site-scale branch. I keep terrain source, assumed grade, model origin, unit system, pad elevations, circulation, parking, and drainage assumptions with the export. Those details are often more important than the rendering settings. Before handing the model onward, I test a small area for scale and coordinate behavior. A site model that opens in the right place but uses the wrong vertical units can mislead a review very quickly. ## Use CityEngine for repeatable district scenarios CityEngine receives a boundary, source layers, rule files, and scenario settings. I version those inputs together. The reproducible object is inputs plus rules, not just the generated scene. When density, frontage, height, or block depth changes, I want a diffable explanation. I also state which layers are generalized or missing. Procedural consistency helps comparison, but it does not transform a scenario into authoritative planning data. ## Use Tripo3D for object-level communication Tripo3D fills gaps such as a shelter, vehicle, facade element, or street fixture. I retain the prompt or reference, normalize units, set the origin, inspect topology and normals, and remove unnecessary geometry when appropriate. The cleaned asset receives a new version rather than overwriting the source. I mark the asset as presentation-only unless a separate review changes its status. This keeps a useful object from becoming an undocumented dependency. ## Handoff checklist * Confirm coordinate reference, units, origin, and vertical convention. * Preserve source dates, selected extents, and rule versions. * Separate generated, generalized, conceptual, coordinated, and verified geometry. * Keep prompts, settings, exports, and transformations beside outputs. * Open a small test export before moving a large scene. * State the next allowed use in plain language. The tools have different jobs: Cityweft gives connected context, Shapezo gives a map-selected generated model, site3d gives site logic, CityEngine gives repeatable urban patterns, and Tripo3D gives individual communication assets. The pipeline becomes reliable when the handoff record explains what each artifact means. I keep exports intentionally small while a workflow is being tested. A clipped boundary, one representative block, or a single object is enough to catch a unit mismatch, a flipped axis, a missing material, or an unexpectedly heavy mesh. Once those checks pass, I move the larger scene. This makes failures cheap and leaves a readable trail for anyone reproducing the run later. For larger handoffs, I also keep the transformation sequence: reproject, clip, simplify, orient, and export. The sequence gives a reviewer a practical path back to the source. It also makes it easier to replace one stage, such as a generalized context layer, without rebuilding the entire scene from memory.
dev.to
September 21, 2026 at 5:43 AM
What does the future of #GIS have in store for planners? 🗺️ Topology's Stephanie Specht had the opportunity to attend the 2026 Esri User Conference in San Diego and summed up her experience in this piece for Planetizen!

#EsriUserConference #ArcGIS #ArcGISUrban #ArcGISCityEngine #digitaltwins
The future of GIS, explored
The pros and cons of ArcGIS Urban, CityEngine, AI assistants and more notes from the 2026 Esri User Conference.
www.planetizen.com
September 10, 2026 at 5:34 PM
Of course you want to do your #ArcGIS #CityEngine #procedrual coding in papyrus font....
youtu.be/nFkodnOTCrA?...
Change your font (or increase font size) in ArcGIS CityEngine
YouTube video by GD3D 3DPathFinder
youtu.be
November 17, 2024 at 12:05 PM
Create a new #ArcGIS #CityEngine Project and Change the Mouse Schema

youtu.be/Pq1e1lrvTh0?...
youtu.be
November 17, 2024 at 12:03 PM
Quick introduction into #ArcGIS #CityEngine, what is it and who is it for? #Esri
youtu.be/zXFE6j2Zhks?...
What is ArcGIS CityEngine? Who is it for? Why Do I need it?
YouTube video by GD3D 3DPathFinder
youtu.be
November 17, 2024 at 12:03 PM
Hi there! We are a #3DGIS #geospatial and #planning consultancy specialising in #ArcGIS #CityEngine #geodesign and #3D #procedural #modelling. We love #GIS #mapping and #cartography. Check out our #YouTube channel. For more interactive discussions follow @geoplanit.co.uk www.youtube.com/@GD3Duk
GD3D 3DPathFinder
Welcome to our YouTube channel! Here we will provide some short ArcGIS CityEngine tutorial/tips videos as well as some longer ones (when we get time!). If you want to see anything specific related ...
www.youtube.com
November 17, 2024 at 11:54 AM
Is that the @BioMedCentral office on this Twitter frequency map of London?! CityEngine-Twitter - ZENODO

zenodo.org/record/9795#.U…
CityEngine-Twitter
This is the first stable release of the data and methodology for CityEngine-Twitter, a real-time urban data visualisation project which uses Twitter data to grow buildings within a CityEngine simulation.
t.co
January 15, 2025 at 1:50 PM
ESRI ArcGIS Online

View 360 VR Experiences in the 360 VR web app—ArcGIS Online Help | Documentation

https://doc.arcgis.com/en/arcgis-online/reference/help-using-360-vr-app.htm
View 360 VR Experiences in the 360 VR web app—ArcGIS Online Help | Documentation
The 360 VR Experience is a file format published from CityEngine and allows the consumption of panoramic images of CityEngine scenes.
doc.arcgis.com
April 24, 2025 at 11:30 PM
ArcGIS CityEngine

Export 360 VR Experiences from CityEngine—ArcGIS CityEngine Resources | Documentation

https://doc.arcgis.com/en/cityengine/latest/help/help-export-360vr.htm
Export 360 VR Experiences from CityEngine—ArcGIS CityEngine Resources | Documentation
360 VR Experience (3VR) is a file format to publish and consume panoramic images of CityEngine scenes.
doc.arcgis.com
April 24, 2025 at 11:29 PM
ArcGIS Blog
3D Visualization & Analytics

ArcGIS CityEngine
Jun 23, 2022

360 VR: Create and View 360 VR Experiences on the Web
By Stefan Arisona and Taisha Fabricius and Avonlea Fotheringham

https://www.esri.com/arcgis-blog/products/city-engine/3d-gis/arcgis-360-vr
360 VR: Create and View 360 VR Experiences on the Web
360 VR is now available as web application on ArcGIS Online across all major XR, mobile and desktop platforms
www.esri.com
April 24, 2025 at 11:28 PM
Esri Events - "Building VR/AR Experiences with CityEngine, Unity, and Unreal." (7/4/2020) https://youtube.com/watch?v=c1wq1wy01b4&si=bf7Agj9VUM0cF1sn
February 8, 2025 at 2:34 AM
June 26, 2025 at 6:20 PM
June 26, 2025 at 6:20 PM
June 26, 2025 at 6:20 PM
ArcGIS Blog - ArcGIS CityEngine: 3D Visibility Analysis for Small Urban Wind Turbines in Brussels by Jen Johnson

https://www.esri.com/arcgis-blog/products/city-engine/3d-gis/uc-louvain-3d-visibility-analysis-for-small-urban-wind-turbines-brussels/
February 25, 2025 at 5:20 PM
In this project "only code" means no GUI modeling (e.g., no CityEngine/Blender), just data transformed through a scripted pipeline to create a beautiful 3D city model. My video is about reproducibility anyone can rerun.
November 1, 2025 at 3:17 PM
My latest blog post… “Is this the end of CityEngine as we know it? (2026.0 and the Python 3 era)”

www.geoplanit.co.uk?p=6334
Is this the end of CityEngine as we know it? (2026.0 and the Python 3 era) | GeoPlanIT
www.geoplanit.co.uk
July 27, 2026 at 8:34 PM
Latest video on my #youtube channel for all things #ArcGIS #CityEngine How to change your font in the code window… (dont judge me!) youtu.be/nFkodnOTCrA?...
Change your font (or increase font size) in ArcGIS CityEngine
YouTube video by GD3D 3DPathFinder
youtu.be
November 12, 2024 at 8:54 PM