{
  "id": 20564945,
  "title": "GeoBIM for an Airport: Keeping BIM, GIS, and the Tunnel in One Coordinate System",
  "url": "https://urgent.news/2026/11/18/geobim-for-an-airport-keeping-bim-gis-and-the-tunnel-in-one",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-18T08:01:41.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/genanywhere/geobim-for-an-airport-keeping-bim-gis-and-the-tunnel-in-one-coordinate-system-5bb6"
  },
  "original_language": "en",
  "account": "Coordination issues on airport projects often stem from unit differences rather than geometry problems. One team might export measurements in feet, while another uses meters, leading to significant discrepancies. In HNTB's airport redevelopment project, which included terminal expansion, new boarding bridges, and a deep tunnel beneath the apron, the GeoBIM gap emerged between the BIM and GIS teams. This gap arose because BIM models start with a local origin near the building, while GIS data typically arrives in a projected coordinate system, such as a state plane zone or UTM zone. Neither system is inherently wrong; they simply represent different answers to the question of where zero is.\n\nTo address this, a project frame is established, which has a name, a number, and a keeper. Any file lacking its coordinate system is excluded from the merge. Each layer undergoes a brief manifest detailing its source, date, units, and owner, ensuring quick reference and preventing minor issues from escalating into larger conflicts.\n\nThe transformation process involves several critical details. Axis order can differ between libraries, so the convention of always using \"always_xy\" is adopted, tested with a known point. Units may vary; a State Plane system might use survey feet, while the design work is in meters. Additionally, the vertical datum plays a crucial role, as a model can be perfectly accurate in plan but off by several inches in elevation. Before merging, three Python checks are implemented: first, control points are verified against eight survey monuments, each within two centimeters; second, a bounding box sanity check ensures the terminal and fence are correctly positioned within the airport and county boundaries; and third, a vertical check against two known benchmarks. If any check fails, the merge is halted, and results are logged alongside the file name for future reference. This meticulous process caught more than just bad data; it also uncovered bad habits, such as a vendor's model that was accidentally rotated ninety degrees, which the bounding box failed to detect but the control points identified.",
  "summary": "Most coordination failures I have seen on airport work were not geometry failures. They were unit failures. One team exports feet, another exports meters, and the tunnel arrives 3.28 times too long. The model still looks convincing, which is what makes it dangerous. The project was HNTB's airport redevelopment: a terminal expansion, new boarding bridges, adjusted stand positions, and a deep…",
  "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."
}