---
title: NAP 2026 data facts
description: Facts from the 2026 VNBdigital publications that matter for keys, asset codes, and validation.
sidebar:
  order: 2
---

<!--
SPDX-FileCopyrightText: 2026 Jonathan Amme <https://github.com/nesnoj> © Reiner Lemoine Institut
SPDX-FileCopyrightText: 2026 Hendrik Huyskens <https://github.com/henhuy> © Reiner Lemoine Institut
SPDX-FileCopyrightText: 2026 Chenyan Ye <https://github.com/yechenyan> © Reiner Lemoine Institut

SPDX-License-Identifier: Apache-2.0
-->

Source: the 2026 publications on VNBdigital (analysed in the NAP 2026 trial).

## VNBdigital

Each DSO has three upload slots: `NETZAUSBAUPLAN` (PDF report), `NETZAUSBAUPLAN_MASSNAHMEN` (XLSX measure list) and `NETZAUSBAUPLAN_KOMPAKT` (XLSX compact sheet). `discover` reads the slots per DSO with VNBdigital's `vnb_gridExpansionDocumentsExternal` query and only registers the newest NAP PDF per DSO (newest round from `tag`, then not marked "ungültig", then `FINAL` before `DRAFT`, then latest upload), so it never picks up the XLSX slots; the 2026 XLSX files were imported by an external script (`document.source = 'local_import'`).

## Documents in nap_data

Per DSO: the XLSX measure list and compact sheet (`local_import`), the PDF report (`vnbdigital`, with VNBdigital document id and URL, as `discover` + `download` would store it; not extracted) and a Markdown conversion of the report (`local_import`, `.md`), whose tables are the `markdown` extractions. The 2026 tables were imported by external scripts: XLSX sheets as tool `xlsx`, the Markdown tables as tool `markdown` (script snapshots in `nap_data/scripts/extract/`). `download` (`record_download`) keeps one selected `vnbdigital` document per DSO and NAP round: a new report deselects only the previous one of the same round (documents without a year replace each other), so the plans of other rounds stay in their sets.

## XLSX measure lists

- The measure list is sheet `Maßnahmenplan`: 2 note rows, header in row 3 (cleaning header row), one row per measure, ~25 columns. Many sheets are formatted down to row ~15,000, so only non-empty rows count.
- DSOs rename sheets (`Tabelle1`, …): identify sheets by content keywords, not by name. Helper sheets (`Vorblatt`, `Deckblatt`, `Datenfelder Dropdown`, `Datenblatt_Berechnungen`) are not data. Some DSOs (NRM, Stromnetz Berlin, Ulm, Harz, inetz) put the compact sheet into the measure workbook.
- The compact sheet `Datenblatt vnbdigital.de` is a cross table (grid level × period T+5/T+10/Zielnetz 2045 × category; count, MVA, km, Mio €) without a single header row. In the aggregated sheets an explicit 0 means "no need", an empty cell means missing.
- Spreadsheet tables use machine number format (`0.102`) in cleaning, PDF tables German format.

## Asset codes

Column `Betriebsmittel [Zuordnungscodes]`, meaning in [Classification](/de/docs/nap-tool/classification).

- Separators are mixed: `501. 601`, `401, 801`, `501 / 701`, none at all (`501601`). Excel stores `301.401` as a float and `201.401` as 201401 with a thousands format (SH Netz). Parse as text, never as a number.
- Deviations: invalid codes (`805` badenova, `502`–`505` ENO, `803` Stromnetz Berlin); `801` misused for fibre links, earth-fault coils and emergency power; wesernetz writes free text instead of codes.

## Quirks that matter for keys and validation

- Duplicate `lfd. Nr.` within one file are valid, distinct measures (EAM 83, SH Netz 15, Netze BW 12); never key on `measure_no` alone, use the source table and row (`row_id`). Repeated `Sammler` names (Netze BW) are labels, not duplicates.
- Reduced files lack columns (Avacon, SachsenNetze, Hamburg, Stromnetz Berlin publish 8–9 of 25); the cost column exists in only 18 files.
- Netze BW has ~18k rows (about 54 % of all records), all named "NAP Maßnahme"; it dominates totals and keeps location coverage low.
- Five publishing DSOs have no XLSX measure list: Mainzer Netze, SWE Netz (Erfurt), Stadtwerke Bochum Netz, VSE Verteilnetz, energis. Mainzer Netze's measures exist only as a table in its PDF report; that table (a `markdown` extraction) has no table type, so it is not part of the 2026 set.
- The external 2026 import matched source folders to existing `dso` rows by name and skipped the rest. TWL Netze, Stadtwerke Heidelberg Netze, Stadtwerke Herne and Syna Hochspannungsnetz were added later with the same importer functions (dso row, identifiers via `sync-dso-identifiers`, XLSX documents and tables, table type, cleaning, scheme mapping); they have no Markdown conversion. A new DSO always needs its `dso` row before its documents are imported.
