Per-building measured LoD2 geometry across several German states — the full solid: every roof, wall and ground surface as a 3D polygon in its native coordinates, plus building height, the roof scalars (tilt, azimuth, area) and a representative coordinate — as Linked Data, from each state's own AdV LoD2 3D building model (CityGML). See coverage below for which states are currently served, region pages for a per-state view (served or not), and /status for live per-source mount state.
Geometry is served faithfully: each surface is a CRS-tagged GeoSPARQL
POLYGON Z (a MULTIPOLYGON Z when the source models it as several
polygons) in the source's own native CRS (UTM zone 32N/EPSG:25832 or zone
33N/EPSG:25833, depending on the state), elevation preserved, no reprojection and no
rounding. (The rooftop-PV yield calculation now lives in the consuming app, not this
wrapper.)
oid/{id}POLYGON Z) plus height and roof scalars — keyed by its LoD2 gml:id
(e.g. oid/DEBY_LOD2_…). Carries the Gemeinde AGS as a
join key. The HTML view adds a 3D viewer and a 2D map. oid/{id}.json is the
building as a bare GeoJSON Feature (footprint, id the building
#b), also JSON-LD; its licence and source are Link headers.
oid/ is the collection: it cannot be listed, it has the lookups.intersects?bbox={minLon},{minLat},{maxLon},{maxLat}sfIntersects,
tested on the surfaces, so a building crossing the edge is in). Also serves GeoJSON —
intersects.geojson?bbox=… (or Accept: application/geo+json) — a
FeatureCollection of building-centroid Points for map clients.
intersects.json?bbox=… (or Accept: application/linkset+json)
lists every building in the box as an RFC 9264 linkset of oid/{id}.json
links, with no paging.nearby?lon={lon}&lat={lat}&r={metres}r metres of a point. Also serves GeoJSON
via nearby.geojson?… (or Accept: application/geo+json), and
every one of them as a linkset via nearby.json?….vocab · indexEach endpoint negotiates content (Accept) and also offers explicit
.ttl / .nt / .rdf / .jsonld suffixes;
Turtle is the default. The spatial endpoints intersects and nearby
additionally offer .geojson (GeoJSON, also
application/geo+json) for map clients and .json, an RFC 9264
linkset of every building matched. Text answers are gzipped when
Accept-Encoding allows it.
The links are relative, so they resolve under wherever the wrapper is deployed.
Every AdV Land, whether currently served or not — each has its own region page reporting live mount status and building count when served, or its research note (portal, licence, known data shape) when not. See /status for a flat live summary of everything currently mounted.
Each building carries its own state's producer and licence attribution
(prov:wasAttributedTo, dcterms:license) — see index
for the full list of currently-served producers, or a building's own RDF for its specific
source and licence. Code: AGPL-3.0.