- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper foucus on building generalization (1:10k → 1:25k) as scene-level vector generation. Building vertices, road tokens, and a scene-scale scalar are encoded jointly. DETR-style queries predict target vertices, and a PolyWorld-style successor module links them into cycles that form exterior and interior rings, so building count and holes are predicted rather than inherited. On 35,811 OS Open Zoomstack scenes with a geographic split, the method achieves the best polygon IoU, PQ, and boundary IoU against raster, LLM, and ArcGIS baselines.
Critical strengths
Well-motivated problem formulation. Limitations are stated candidly, and the dataset could become a useful benchmark if it can be made public.
Critical weaknesses
- The representation, successor module, and loss come from PolyWorld. The additions (vector input, DETR queries, a road flag, a scale scalar, a distance prior) are modest. PolyWorld (Pix2Poly, and RoomFormer) are not compared, although they could be trained on the same rasterized masks used for the raster baselines. Such a comparison would isolate the actual contribution.
- The no-road ablations look like optimization failure. Without roads, 60.9% of outputs are empty and PQ is 0.080, while road-free raster baselines reach 0.38–0.53. The road effect may therefore reflect training dynamics rather than geographic information. Dummy-token controls and multiple seeds are needed.
- The raster baselines receive neither roads nor a fixed scale, yet Base + road (PQ 0.512) already trails the road-free RoofX-Net (0.527). ArcGIS thresholds are untuned, raster outputs lack standard post-processing, and dedicated generalization models are missing. The LLM baseline, with no training at all, is only 2.9 PQ points behind.
- No validity or cartographic checks. Rings are repaired with buffer(0), and the paper does not report self-intersection rates, orphan holes, minimum separation, or road conflicts. Full also returns empty output for 6.35% of the simplest scenes.
Questions for authors
- How do PolyWorld and RoomFormer perform on the same rasterized input with a road channel?
- Does replacing roads with dummy tokens reduce Base’s empty-output rate to a similar degree?
- Does the main ranking hold when raster baselines receive roads and a fixed resolution?
- What fraction of Full’s empty outputs stems from orientation errors?
- How was the 1:25k layer produced, and how does a tuned ArcGIS workflow perform?
- I notice that for qulitative results on Figure 6: Road-context ablation, your method shows sharp edge, what causes that?
2 comments
Thanks for the author's reply. After reading the rebuttal, I still have some concerns. (1) with roads, the raster baselines match or exceed CartoGens on overlap and instance metrics, and PolyWorld is close as well, the abstracts's claim is therefore overstated. (2) The road ablation may largely reflect escaping a degenerate solution rather than geographic information. (3) "We have improved the method to address this cause." doesn't provide details about how and to what extent. Therefore, I will keep my score.
Response to Reviewer QwQ3
We thank Reviewer QwQ3 for the comments. Point-by-point replies below.
W1 / Q1. PolyWorld and others on raster input. We trained PolyWorld from scratch on the same building + road rasters, with the official architecture and the original multi-stage schedule. Test results:
We could not train RoomFormer and Pix2Poly within the response period.
W2 / Q2. Is the no-road ablation an optimization failure; dummy tokens; seeds. Dummy-token control (same token count, road coordinates set to zero), test results:
Dummy tokens recover only 8% of the PQ gain from real roads; most of the effect comes from road geometry. An empty output is a degenerate solution of the successor objective, where every query points to itself. All results use one fixed seed.
W3 / Q3. Roads and fixed resolution for raster baselines; post-processing; gap to the LLM. Raster baselines with roads, test results:
Roads raise PQ by 0.10–0.14 for all three models, matching CartoGenS's large drop without roads (0.512 → 0.080): whatever the architecture, geographic context such as roads is necessary. With roads, RoofX-Net is ahead in PQ and polygon IoU and CartoGenS on boundaries and shape; our comparison conclusion is adjusted accordingly. We could not finish the fixed-resolution raster variants or simplification post-processing within the response period; the raster outputs here are unsimplified. As for the LLM baseline, it outputs fewer vertices than the reference (VCR 0.87) and has lower BIoU (0.566 vs. 0.661).
W4 / Q4. Validity, empty outputs and orientation. We added an analysis of the unrepaired output: the paper model has 70.4% raw validity, 10.3% self-intersections and 3.9% empty outputs. Per scene: 16.4% have a self-intersecting ring, 10.1% overlapping exterior rings, 4.4% a hole outside every exterior ring. Self-intersections have two main causes. First, Hungarian matching uses coordinates only; when two queries land on the same vertex, the label assignment is close to random, both can end up in the ring at inference, and rings with such a duplicate self-intersect 5× as often. Second, 46.6% of reference vertices are densified arc points 0.3–0.4 m apart, below the coordinate error; the order of neighbouring points is flipped on 19.4% of arc edges vs. 2.4% of other edges.
Other methods self-intersect less partly because raster polygons are traced from a mask and cannot self-intersect, and partly because they mostly do not represent arcs. Share of target arc points reproduced within 0.5 m: CartoGenS 65.7%, RoofX-Net + road 18.0% (staircase tracing, ~31× the vertices), GPT 12.6%, PolyWorld 6.8%, ArcGIS 0.5%. PolyWorld, also vertex-and-edge based, has 21.4% self-intersections.
Of the 3.86% empty outputs, 3.73% are scenes where no ring is decoded (all queries self-loop) and 0.12% are scenes where all rings are clockwise and read as holes, so orientation accounts for 3% of empties. The 6.35% empty rate on single-building scenes is the same all-self-loop failure. We have improved the method to address these causes. Minimum-separation and road-conflict checks are not added yet.
Q5. The 1:25,000 layer. It is the district building layer published in OS Open Zoomstack, produced by Ordnance Survey and used as published. ArcGIS tuned on validation (54 settings, one test run): PQ 0.493 vs. 0.616 for CartoGenS.
Q6. Sharp edges in Fig. 6. These are spikes from duplicate vertices connected in the wrong order, the first cause in W4: two queries sit on one corner, and the ring visits one, leaves, then comes back to the other. We have improved the method to address this cause.