One address in.
The real building out.

Try it on an address you know.

geo3d is most convincing on your own house. You confirm your e-mail address once and then have three complete queries — with 3D model, site plan and location dossier.

Note for the integration: this console is the interface of the white-label widget. Licensees run it without the e-mail gate, with their own theme and their own domain.

What lies beneath the house

The terrain comes as a file, not as an image.

With every simulation we deliver the official terrain model within the radius — in the formats your programs really do read in. Not as a screenshot, not as a PDF: as a point grid for the design engineer and as a mesh for the 3D scene.

Three formats, one charge

.xyz (space-separated) for ArchiCAD — its file dialogue knows only .txt and .xyz. .csv (comma-separated) for Revit, as a point cloud for the toposolid. .glb for the 3D scene in the browser and for Rhino. .xyz and .csv carry the same content; only the separator and the extension differ. All three together are one retrieval: whoever fetches the terrain once gets every format at no further cost.

The number of points is not a matter of taste

At a 150 m radius we deliver 7,569 points on a 3.5 m grid, at 75 m 5,776 points on a 2 m grid. That is coarser than our data are — and the reason does not lie with us: Revit 2024 and 2025 reduce a point cloud, when a toposolid is created, without a warning down to 10,000 points. From version 2026 the limit is adjustable. As long as 2024 and 2025 are on the market, we deliver below it — a file with 22,801 points would look on opening as delivered and would arrive thinned out, and nobody would have noticed. The mesh does not have this limit: it goes into the browser, not into Revit's point cloud path, and at 150 m delivers a 1 m grid with 90,601 points — four times finer than the CAD file.

Where the axes lie — and why not the same everywhere

Easting and northing are local metres around the model origin in all formats. The height is in .xyz and .csv absolute in m above NHN, in the .glb relative to the model origin. Both are intended: the CAD file is often opened without an accompanying document, and there NHN is the convention of the surveying formats. The mesh ends up in a scene in which the building model already lies with a local reference — absolute heights would place the terrain 151 metres above the house. The shared origin is supplied in both cases: terrain, building and neighbouring buildings lie on top of one another without any transformation.

The terrain tab — the same terrain, just to look at

Anyone who does not want to open the files themselves sees the same terrain in the browser. In the demo and in the widget the building stands in the official terrain, the neighbouring buildings as boxes beside it, and the below-grade facade is named; the opening view shows terrain, neighbours and house together. Where the slope cuts the wall, the intersection is shown, not covered up — it is the same cut edge the below-grade wall area in the table above comes from.

What the terrain does NOT contain

The DGM1 is a terrain model: the ground surface, without buildings and without vegetation. It shows the slope on which the house stands, and the hollow behind it — not the neighbouring house and not the tree. Where no elevation is available, the point is missing; we never insert a value we do not have.

The terrain is currently available at our example addresses. For your region, ask us — the preparation is under way. The rollout carries on, address by address — tell us which region you need.

Fine point: the 3.5 m grid spans ±150.5 m instead of ±150.0 — 87 points per axis do not divide evenly at 3.5 m spacing. We keep the number of points constant, not the round radius; the number of points is the quantity Revit's limit hangs on. The 1 m mesh spans exactly ±150.0.

How the house fits into the street

Street elevation: the neighbourhood, seen in height.

The footprint says how wide the building may be. How high it may go without falling out of line is something only the elevation says: the terrain profile along the street axis, both building lines, and the houses on both sides of the street, each at its own level.

What the Street elevation sheet holds

The axis is the centre line of the address street from the official street network, joined across tile seams and cut around the building. On it lies the terrain profile from the DGM1, station by station. Added to that is the terrain on both building lines (±12 m from the axis) — the line where the ground meets the front gardens. The buildings on both sides of the street stand as LoD2 boxes with a schematic roof, each on its own ground plate, rather than all on one imagined plane.

Three extensions, one charge

.json holds the numbers: axis, stations, levels, buildings with station, front, eaves, ridge, ground. .dxf is the CAD drawing in the R12 format, which older programs open without a detour. .svg is the finished sheet — site plan, legend, and both sides of the street on one page, as pictured below. The three belong together: the terrain family counts once per simulation. Whoever fetches the terrain model and the street elevation for the same simulation pays for one retrieval; every follow-up retrieval — every further extension, every repeat — is free.

Open the sheet as SVG

What it is needed for

In the preliminary design the sheet answers the question that always comes up at the first meeting: how does the design fit into the street scene? In the building application it carries the height development of the street and the connection to the terrain — both otherwise laboriously gathered from separate figures. And because terrain, building and neighbouring buildings share one origin, the sheet fits everything else delivered for the same address, without conversion.

What the Street elevation is NOT

These limits travel with the file: they stand in the response as well as in the legend of the sheet:

• Buildings are LoD2 boxes from footprint, eaves and ridge height — no facades, no openings; roofs are drawn schematically as a gable between eaves and ridge height, the roof shape is an attribute.
• Terrain is the DGM1 (ground without buildings and vegetation), 1 m grid, bilinear interpolation — no accuracy guarantee.
• Each building stands on its LoD2 ground plate; where none is stored, on the lowest DGM1 height at its footprint corners.
• The street axis is the basemap.de centre line, joined across tile seams; it is a position line, not a surveyed kerb.
• A building counts when a footprint corner lies within 40 m of the axis; buildings whose centroid lies more than 100 m from the axis are not searched.
• The right-hand side is drawn in stationing direction, not mirrored.
• Heights in m above sea level, DHHN2016 (Germany).
• The rule for the tile seam is calibrated at one seam, not measured across the whole stock.
• Germany only. Denmark and France do not run over this route.