Help & Support

Common issues and their fix

"My model sits 32 million metres from the project origin"

Cause: the source file uses ETRS89/UTM coordinates with zone prefix (e.g. 32456789), and the project's UTM convention is set to "without prefix" — or vice versa.

Fix: re-import in a fresh project, in the UTM convention dialog choose the variant matching the file ("Without prefix" for standard geoportal values, "With zone prefix" if the source actually uses prefixed east values). If the project already contains data, all sources must be consistent. See Before the first import.

"Shape changed" warning on DGM import

This Revit warning may appear when building the Toposolid. It is harmless and concerns Revit's own Toposolid shape validation, not the elevation data. GeoBridge usually suppresses the warning automatically; if it still appears, it can be closed.

"Demonstrator version expired"

Dialog title: GeoBridge — demonstrator version expired.

Demonstrator bundles are time-limited and intended for advance evaluation. A demonstrator version issued by the vendor expires on the embedded date. Productive use requires the regular Free or Pro edition from the Autodesk App Store.

"BRep faces cannot be created" for a special-construction building in CityGML

Occasionally city models contain topologically defective building geometries (self-intersecting faces, invalid winding order). GeoBridge catches these cases and produces a simplified geometric replacement. A corresponding counter line appears in the post-import TaskDialog. The result is topologically sound but visually less detailed than the original might suggest.

A second import lands far from the first

Possible causes, in order:

1. UTM prefix inconsistency — the first import ran with prefix removal, the second without (or vice versa). The prefix choice must be identical for both. The Pro edition remembers the choice per project.
2. Survey Point manually moved — the Pro edition reports this as drift. In the Free edition it happens silently; workaround: manually reset the Survey Point to the original value or redo both imports.
3. Data in different CRS — automatically reprojected in Pro, refused in Free. Check: do the EPSG codes of the source files match?

Polygon filter yields no result (all data gone)

Possible causes:

1. Polygon outside the source bounding box — for "From GeoJSON file", GeoBridge shows a range-check warning before the filter ("Polygon outside the source bounding box"); for "From detail lines" the coordinates come implicitly from the Revit view and align.
2. CRS convention mis-interpreted — for a polygon with a CRS different from the import (typical: WGS84 polygon in a UTM project), the Pro edition reprojects automatically; Free refuses. The GeoJSON CRS check warns before the filter when the crs.properties.name declaration differs from the import CRS.

Fix: display the polygon visually in the site plan and check whether it lies within the expected DOP/DGM/CityGML tile area.

Crash on import — where do I find the error report?

GeoBridge writes a report on uncaught exceptions to:

%LOCALAPPDATA%\GeoBridge\errors\

The file is timestamped and contains plugin name, plugin version, and the stack trace. When raising a support request, attaching this file helps.

Import ran through but the geometry looks wrong — how do I diagnose?

In addition to the errors directory, GeoBridge writes a diagnostic file for every import containing all relevant input values (Survey Point coordinates, source EPSG, pixel size, bounding-box corners, project north angle, etc.) into:

%LOCALAPPDATA%\GeoBridge\diagnostics\

The file answers typical forensic questions like "in which convention was this interpreted?" or "where was the SP at the time of this import?". When contacting support, attaching the most recent relevant log significantly speeds up diagnosis. The diagnostic logs contain no personal data and no geometry content.

Convenience: the About dialog → "Export support ZIP" packs both directories into a single ZIP file.

"Existing DGM Toposolid in the same area" dialog

Appears during DGM import when the new tile's bounding box spatially overlaps a DGM Toposolid already in the project (real area overlap — direct adjacency along an edge does not count). Two options: "Import anyway" (auto-fallback engages if Revit rejects) or "Cancel — delete the existing Toposolid first" (safe path). Default is Cancel because Revit frequently rejects overlapping Toposolids with an opaque InternalException.

Where do I find sample data for testing?

Free sample data for Thuringia (DOP tile, DGM tile, CityGML LoD2 tile) is available on request. Email support@lichtbus.de with the subject "Test data Thuringia". The data is provided without further conditions.

Where do I find updates?

GeoBridge is delivered and updated via the Autodesk App Store. Updates appear automatically in the Autodesk Desktop App as soon as a new version is released. There is no in-plugin update function — by design, to honour the privacy commitment.

Current release notes and changelog: lichtbus.de/geobridge.

Privacy

GeoBridge does not collect any data from imported geodata or from Revit projects. There is no telemetry, no usage analytics, no version-check at runtime. Server connections only occur:

• on Pro license activation (license key + hardware fingerprint),
• on voluntary submission of a crash report (opt-in dialog).

Full privacy statement: lichtbus.de/geobridge/privacy.

Support contact

Reply usually within 1–2 business days.