- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper introduces CityCode, a representation that unifies metric geometry, urban topology, visual semantics, and 3D assets through persistent entity identities. It also presents Air2Code, a pipeline that combines visual structure extraction with adapted metric depth estimation to construct this agent-operable representation from sparse aerial observations. Experiments on CitySample-Aerial and UrbanScene3D show more accurate metric structure recovery and better visual fidelity to the target cities than the evaluated baselines.
Critical strengths
(1) The paper introduces CityCode, an agent-operable representation that links metric urban structure, observational evidence, visual semantics, and 3D assets through persistent entity identities.
(2) Air2Code provides a complete pipeline for constructing this representation, combining visual structure extraction with adapted metric depth estimation.
(3) Experiments on both synthetic and real-world-derived scenes show improved metric geometry and leading visual quality among the evaluated baselines on CS-Aerial and UrbanScene3D.
Critical weaknesses
(1) The paper would benefit from further revision and polishing. For example, the introduction does not include an explicit list of contributions, and the conclusion is brief.
(2) The main contribution appears to be a system pipeline that combines processing steps from existing work, including image completion and 3D generation. The individual components are largely drawn from prior methods.
(3) The pipeline relies mainly on existing models as its core generators: TRELLIS.2 for buildings, Pixal3D for backgrounds, and GPT-image-2 for appearance completion.
(4) Aerial RGB images provide rich appearance and geometric cues about the target city, so strong results from such input are somewhat expected.
(5) The paper also does not justify its choice of GPT-image-2, TRELLIS.2, and Pixal3D, or compare them with alternatives. This makes it unclear whether the gains come from the proposed design or from these pre-trained and proprietary models.
Questions for authors
(1) How does performance degrade with pose or intrinsic noise?
(2) What are the end-to-end runtime and API cost for the ~22.58 km² CS-Aerial area?
4 comments
Response to Reviewer 46u5 (2/2)
Question (1): pose and intrinsic noise.
At realistic levels it does not degrade noticeably. Our test cameras already vary per patch (tilt 2–4° from nadir in any direction, flying height 260–320 m). On top of this, we add errors to each patch's known camera and re-run the whole structure stage (App. G.10):
- Three error levels from UAV sensor specifications and calibration studies (Applanix APX-15; DJI Phantom 4 RTK; Zhou et al., 2020; Tomsett & Leyland, 2021; Pérez et al., 2011; Abeho et al., 2024): survey-grade (manufacturer specifications), field-flight (errors reported in real flights) and stress (RTK loss and poor calibration).
- Six camera parameters (position, roll, pitch, heading, focal length, principal point), perturbed one at a time ("each"; ranges are over parameters) and all jointly at the field-flight level.
At survey-grade and field-flight error levels, building F1 is unchanged and geometry changes by at most 0.31 m.
| Error level (position; roll/pitch, heading; focal; principal point) | [email protected] ↑ | IoU ↑ | XY error (m) ↓ | Height MAE (m) ↓ | DSM RMSE (m) ↓ |
|---|---|---|---|---|---|
| None | 83.4 % | 0.812 | 2.03 | 3.60 | 14.37 |
| Survey-grade (2–3 cm; 0.025°, 0.08°; 0.05 %; 1 px), each | 83.4–83.7 % | 0.810–0.812 | 2.04–2.07 | 3.57–3.67 | 14.37–14.38 |
| Field-flight (5 cm; 0.1°, 0.3°; 0.5 %; 3 px), each | 83.1–84.0 % | 0.804–0.811 | 2.03–2.17 | 3.58–3.72 | 14.37–14.45 |
| Field-flight, all jointly | 84.1 % | 0.789 | 2.34 | 3.76 | 14.60 |
| Stress (20 cm; 0.5°, 1°; 1 %; 10 px), each | 79.6–83.6 % | 0.746–0.811 | 2.05–2.87 | 3.63–4.19 | 14.37–15.18 |
Two properties keep the errors small:
- ground-anchored scale calibration absorbs about 87 % of a focal-length error;
- each building is recovered from a single patch, so errors do not accumulate across patches.
Only stress-level attitude errors cause metre-level shifts, as expected for a viewing distance of about 300 m. Under realistic camera errors, the recovered metric structure therefore stays stable.
Question (2): runtime and cost.
As detailed in General Response E, we first clarify that 22.58 km² is the BigCity area used only to train the depth model, which needs no API calls; the evaluated city covers 2.79 km² (79 regions; Sec. 4.1, revised). End to end, one 400 m region takes 32 min and USD 1.00 (0.27 GPU-h), and regions are independent, so they run in parallel. The whole evaluated city takes 801 API calls, USD 79.1 and 6.7 GPU-h.
We would be grateful to know whether these responses address your concerns, and are happy to clarify further.
Dear Reviewer 46u5, we would like to kindly follow up on our response. We would appreciate any feedback on concerns that remain and would be happy to discuss them further. Thank you for your time!
I thank the authors for their detailed response and the effort they put into the rebuttal.
However, after carefully reading the response, my main concerns remain. Despite the authors’ extensive explanations, I still find that the paper lacks novelty. Beyond combining several existing components into a single pipeline, I am unable to identify a clear technical contribution.
Several of my questions also remain unaddressed. For example, the authors argue that RGB input is not information-rich because other methods perform worse with the same input. This reasoning is flawed: it only shows that a larger combined system performs better, not that RGB provides insufficient information. The gains may stem from increased model capacity rather than the proposed design.
Overall, the authors’ response does not adequately address most of the concerns raised in my review, so I will keep my original score.
Response to Reviewer 46u5 (1/2)
Please read your individual response first: shared points are summarized here, with references to the General Response for details.
Thank you for the review, and for recognizing our entity-linked representation, complete pipeline and improved metric geometry. Your specific questions on pose and intrinsic noise are answered in full below. The revised paper and supplement mark all changes in blue. We start with where the gains come from.
Weaknesses (3) and (5): the core models are adapted, compared with alternatives, and not tied to proprietary models.
We respectfully clarify that the core models are not used off the shelf, and that the paper already compares them with their base versions (General Response B2, Table 4):
Each model fills one role and was the strongest available at submission. Pixal3D generates only the non-building background and is conditioned on the recovered ground and elevated height fields.
Weakness (2): CityCode is not a simple combination of existing methods.
As explained in General Response A and above, our contribution comprises a new setting, a pipeline (Air2Code) with models adapted with structural priors and new mechanisms, and, to our knowledge, the first exploration of long-horizon tasks (querying, editing, planning and restoring earlier states) in an observed city. Removing the adapted models or mechanisms degrades results (General Response B2). These components can also benefit city generation beyond our pipeline: structure-and-observation-guided generation (structure-guided appearance completion followed by the structure-aware building generator) yields buildings that match both the observed appearance and the recovered footprint and height, and CityCode-Depth recovers metric depth from low-altitude aerial views.
Weakness (4): informative input.
As shown in General Response B3, the input is in fact sparse: one aerial view per region, so metric scale is not directly visible and most facades are unseen. Given exactly the same RGB and cameras, Sat3DGen and Sat2Density++ reach DSM RMSE 37.03 / 33.99 m vs. 14.37 m for CityCode, and UrbanWorld2.0, given even more input (GT heights and layouts), still trails on every visual metric. Strong results thus come from our method, not from the input alone.
Weakness (1): writing.
We agree; as listed in General Response F, Sec. 1 now has an explicit contribution list and Sec. 5 an expanded conclusion with limitations.