Map data for Norway
Available now
9 national · 2 global baseline · 7 FKB layers
This country is available to order. The table shows the sources used across each map.
Sources and licences
Every layer, traced to its source
The exact datasets behind each layer in a Norway delivery, with licence and current status.
Loading the source plan…
Behind each layer
Where each dataset comes from, and what that means for the model.
- Terrain
- The 1 m national model from the 2016–2022 lidar campaign: 230,000 km² at 2–5 points per m², published openly by Kartverket.
- Buildings
- OpenStreetMap footprints, which in Norway largely descend from Kartverket's building registers through the community's national import, so coverage is close to complete. Heights are measured against the national lidar surface, never read from mapped tags.
- Roads
- Centrelines from NVDB, the road database Statens vegvesen keeps for every drivable road; the open export refreshes weekly. Widths are modelled — the source is a centreline network, not surveyed edges.
- Water
- Lake outlines from NVE's national lake database; the sea is detected against the terrain model. Water bodies are delivered as level surfaces.
- Site objects
- Walls, fences and hedges from OpenStreetMap where mapped — density follows local mapping activity.
- Parcels
- Parcel geometry from Matrikkelen, the national cadastre. Point precision follows survey history — about 4 cm where recently surveyed, 13 cm for older classes, metre-class where boundaries were digitised from the 1:5,000 economic map series — and the register records which is which.
- Surface image
- A cartographic ground texture GeoAnvil renders from OpenStreetMap data. Norwegian orthophotos (Norge i bilder) sit under Geovekst licensing, so the texture is drawn, not photographic.
- Contours
- Generated from the same lidar model as the terrain surface, at the interval you choose — contours and terrain always agree because they are one model.
- FKB Buildings
- Roof geometry stereo-plotted by operators from the national aerial programme — Takkant, Mønelinje, Taksprang. The wall line (Fasadeliv) is optional in the specification. Licensed through Geovekst.
The mapping landscape
How Norway is mapped
Norway scanned itself. The state flew the whole country with lidar and keeps roads, heights and the cadastre open, so a Norwegian delivery rests on national registers rather than global fallbacks — the table above names the register behind each layer.
Terrain grid1 mnational lidar model
FKB roof edge0.20–0.45 mstandard deviation by class: 0.20 · 0.25 · 0.45 m
Cadastral point0.04–1 mmodern survey to digitised map
- Open by default
- The lidar terrain and surface models are CC BY, the NVDB road network and Matrikkelen are open data, and the delivery leans on them wherever they beat the global baseline.
- FKB and Geovekst
- Large-scale mapping (FKB) is owned jointly through Geovekst — municipalities, Kartverket, road, energy and agriculture interests. Geometry is stereo-plotted from aerial imagery on 5–10 year national cycles and topped up from municipal building cases. Licensed, not open, so it ships as its own tier.
- Accuracy classes
- FKB is captured to area classes A–D — A city centres, B built-up areas, C rural — and the class follows the area rather than the dataset, so one national product is sharper downtown than in open country.
Georeference
Coordinates in practice
Two projection families are in daily use here, and the choice is not cosmetic: one is built for maps, the other for setting out a building.
UTMup to 40 mm400 ppm — fine in GIS, visible in setting-out
NTMunder 1.1 mmbuilt with the construction industry, 2009
- Reference frame
- Everything national sits on EUREF89, Norway's realisation of ETRS89. Frame, projection and EPSG code are stated in every file.
- UTM or NTM
- UTM zone 32, 33 or 35 is the official projection, and the zone follows county rules rather than longitude — eastern Trøndelag stays in 32. NTM narrows each zone to 1°, which is why setting-out and machine control run NTM while municipal base maps run UTM. GeoAnvil delivers both, UTM by default.
- Heights — NN2000
- Heights are NN2000, phased in 2011–2018 to replace NN1954; the shift spans −15 to +35 cm by region, mostly post-glacial land uplift. Deliveries name NN2000:2018 (EPSG 5941) rather than an ambiguous “NN2000”.
- Model origin
- The local origin is rounded to a whole 100 m in the delivery projection, so coordinates stay readable in CAD, and the exact offset ships in the delivery's georeference.
Read the specifications yourself
Every claim on this page traces to one of these documents.
- Nasjonal detaljert høydemodellKartverket
- FKB generell del 5.1 — standards and accuracy classesGeonorge
- Fotogrammetrisk registreringsinstruks, FKB-Bygning 5.0Geonorge
- EUREF89 NTM sone 5–30Kartverket
- Ta i bruk NN2000Kartverket
- Elveg 2.0 — the NVDB road network exportNVDB / Statens vegvesen
- Matrikkelen Eiendomskart Teig — product specificationGeonorge
What a delivery contains
- Layers
- Editable 3D terrain with contours, buildings, roads, water and vegetation, plus parcel boundaries where the national registry allows it.
- Formats
- IFC 4, DXF and GeoPackage, plus GeoTIFF and PDF, all open formats.
- Provenance
- Every map ships with a manifest naming each source and its version, so the data trail survives the handover.
