GeoBridge Pro
LichtBusGeoBridge Pro
LichtBusOfficial geospatial data into Autodesk® Revit® in minutes: orthophoto, terrain, city model and vector geometry — georeferenced, no CAD converter, no external GIS software needed.
$99.00/year
Geospatial data straight into Revit, no converter detour. GeoBridge closes the gap between site-plan research and the start of design work. Four add-ins read terrain, orthophoto, city model and vector data in a single step — properly georeferenced, polygon-clipped, no external GIS software.
Before. Convert city models through KITModelViewer to IFC, import into Revit, paint materials by hand — once exported, the colouring is frozen. Run the terrain through Dynamo, 64 GB of RAM mandatory, breaks between tiles. Synchronise the Survey Point by hand between plugins, half a metre of risk every time. Three to five hours of setup per project.
With GeoBridge. Pick a file, pick a polygon, done. CityGML in three minutes, DGM in four, DOP in two. Materials remain editable after import by class, function or storey. Existing Revit projects with their own georeferencing are adopted without a reset.
Four add-ins:
- DOPProjectBridge — orthophoto GeoTIFF as a georeferenced image instance
- DGMProjectBridge — DEM or XYZ as a Toposolid
- CityGMLtoRevit — CityGML LoD1/LoD2 as DirectShapes per Building × Semantics
- GeoShapeProjectBridge — import GeoJSON, Shapefile, KML, CSV or GeoPackage as 2D or 3D geometry; export to GeoJSON, KML, Shapefile or GeoPackage; HK addresses with address label, ALKIS parcels with numerator/denominator labelling
Three anchor variants — SW corner of the source, reference point for DWG handover, or an existing coordinate frame. Project-North rotation is supported from the very first import. Drift between imports and cross-zone sources are caught before the import; UTM zone prefix is confirmed once and silently inherited afterwards.
Geospatial data stays local. No cloud processing of your data, no telemetry. The only online connection is the Autodesk licence check at startup (App Store standard); everything else runs offline. F1 help and privacy policy integrated.
Founders License — €99/year. Subscriptions started before 31 December 2026 stay locked at €99/year for the lifetime of the subscription. The standard price rises to €149/year from 2027. Existing subscriptions are unaffected.
From the developer. GeoBridge grew out of my own work — what sits in the ribbon today used to be a stack of KITModelViewer roundtrips, Dynamo scripts and hand-mapped Survey Points. I use it daily on my own projects and keep developing it because I keep needing it.
LichtBus — tools for the BIM workflow.
Details
Operating system
Release date
Jul 21, 2026
Last updated
Jul 21, 2026
Version
1.2.4
Language
Compatible with
RVT
2025, 2026, 2027
Certifications
Digitally signed
Capabilities
BIM
Materials
Architectural design
Regional specific functionality
Frequently asked questions (FAQs)
What else should I know about this product?
Platform. Revit 2025, 2026 and 2027 — separate builds, identical feature scope.
Data formats. DOP: GeoTIFF with GeoKey tags or world file. DGM: GeoTIFF (Float32/Int16) or ASCII .xyz. CityGML 1.0/2.0/3.0 LoD1/LoD2 (LoD3/LoD4 on request). GeoShape: import from GeoJSON RFC 7946, ESRI Shapefile, KML/KMZ, CSV, GeoPackage; export to GeoJSON, KML, Shapefile, GeoPackage (CSV import only).
Coordinate systems. ETRS89/UTM (EPSG:25832, 25833) with prefix detection; other projected CRSs via EPSG. Vector data reprojects automatically via closed-form Krüger (WGS84↔UTM, UTM↔UTM); raster and city-model data require matching CRS for source and project.
Free edition:
- Single-file import for all four plugins
- Georeferencing with three anchor variants + UTM convention
- Drift detection, cross-zone protection
- Polygon clipping (CityGML / DGM / GeoShape)
- Material mapping per class (CityGML), basic style mapping (GeoShape)
- WGS84→UTM reprojection for GeoJSON (GeoShape)
- Import Event Manager (tabular browser)
- Nine languages, F1 help offline, diagnostic logs, support-ZIP export
Pro edition adds:
- Multi-file import
- DGM multi-tile with edge merge + multi-DOP composite as material
- UTM↔UTM reprojection (GeoShape)
- Material mapping per function + per storey (CityGML); style mapping with multi-ring polygons (GeoShape)
- Terrain preparation with independent axes Smoothing + Resolution
- HK addresses as 3D family instances + ALKIS parcels with numerator/denominator label (GeoShape)
- Export (GeoJSON / KML / Shapefile / GeoPackage) + GeoPackage import (GeoShape)
- Set Survey Point manually first; existing external anchors (DWG/IFC) adopted in place
- Event Manager: after-the-fact UTM convention declaration + non-destructive with-/without-prefix toggle
Roadmap. Datum transformations (DHDN, MGI, CH1903+) and additional federal-state conventions on request.
Are there any known issues with this product?
- LoD3 / LoD4 not in the standard scope — import covers LoD1 and LoD2. Higher levels of detail on request.
- Reprojection limited to vector data (GeoShape). WGS84↔UTM and UTM↔UTM zone changes are transformed automatically; datum transformations (DHDN, MGI, CH1903+) in preparation. DOP, DGM and CityGML require matching CRS.
- AdV file-naming convention covers 14 of 16 German federal states reliably; deviating schemas (Saxony, Austria, Switzerland) may limit automatic tile detection.
- Very large CityGML files (> 500 MB) extend the import — polygon clipping recommended.
- Test coverage primarily Germany. Data from other regions may deviate — please report to support@lichtbus.de.
Is there additional support information provided?
Fast support for GeoBridge.
- Ticket system: https://lichtbus.de/support
- Email: support@lichtbus.de
Typical response time within two business days.
Helpful in a request: plugin name + version (Revit Add-Ins tab), Revit year (2025 / 2026 / 2027), data origin (federal-state Geoportal, format, EPSG), step-by-step description, screenshot of the error. For crashes: attach the support ZIP from the About dialog — plain text, no personal data.
Sample tiles free on request (Thuringia, DOP/DGM/CityGML, AdV standard).
Feedback explicitly welcome. Every reported case helps to extend the suite to further federal states and data variants.
Found an issue?