RevitGeoSuite

Getting an indoor Revit model into GIS-ready, IMDF-compliant data used to mean a brittle chain of manual steps — set coordinates by hand, hunt down PLATEAU context data separately, export to DWG, clean up in another tool, hand-convert to Shapefile — with no validation and no stable IDs across re-exports.

RevitGeoSuite is a modular Revit add-in — Georeference, Import, and Export each open as a Svelte web app inside a WebView2 window, talking to the C# backend over a typed RPC bridge, with the UI shipped in English and Japanese. Georeferencing gets its own guided workflow: CRS selection from Japanese presets, map-based point picking, and PLATEAU grid-tile snapping, backed by a live validation panel that checks coordinate setup and export readiness as you work. From there it imports context from PLATEAU (folder or API) or OpenStreetMap, pulls terrain from a local DEM or Cesium Ion, and exports to 3D Tiles, CityGML, or GeoPackage/Shapefile floor plans using an IMDF-style schema — with a preview map, category/floor assignment, and a diagnostics manifest before anything gets written. It's the same indoor-mapping pipeline behind the Sta.navi Indoor Navigation project, now built as a proper modular tool instead of a one-off script.

What used to be a chain of manual, error-prone conversions is now a guided pipeline with validation built in up front — the export preview for one Shinjuku floor plan alone flagged 329 issues before a single file was written. Incremental export means re-running a job after a small model change only rewrites what changed, and bilingual (EN/JP) UI means the workflow doesn't depend on me being in the room to explain it.