Germany's PV Atlas

EarthPV CalibrationBronzeSilver otherwise.
Needs more leads mapped in
OpenStreetMap to localize the model.
Add local training data →
Germany PV capacity, by 0.1° cell
11 km × 11 km cells · log scale
MWp / cell
none detected
0MWp
Best estimate, the highest defensible figure
0
Training data hand-mapped in OpenStreetMap, ≥400 m²
0
Training data hand-mapped in OpenStreetMap, <400 m²
0
of 0.1° cells within the calibrated building-density range
Capacity
The same Sentinel-2-detectable total, by installation size
Capacity per size bin, rooftop and ground-mount stacked
linear scale · MWp · hover a bar for detail
rooftop
ground-mount (hatched)
rooftop, extrapolated beyond calibration
Capacity
The same total, by method
Total Capacity
roofclf's building-by-building estimate (rooftops of every size, in cells inside its calibrated density range) supplies 61% of Best; TerraMind segmentation of large arrays (27%) and installations mapped in OpenStreetMap (13%) split the rest.
Uncertainty
How sure each part of the Best estimate is
Point estimate and 90% credible interval, per component
log scale · MWp · hover a row for detail
Each row is one addend of the Best estimate; the top row is their sum. The intervals do not add up to the total's: components that share an error source were drawn together (one area-to-capacity constant for every rooftop figure, one for every ground-mount figure, one re-draw of the calibration areas for every roofclf figure), so the total's interval is narrower than the sum of the parts' intervals would suggest. A row without a whisker is a deterministic correction rather than a modelled quantity. The intervals cover measured errors only; "How confident should you be in this?" below lists what they leave out.
All component intervals
ComponentMWp90% low90% high
Context
Against official and published figures
National total
this atlas in MWp · other figures in MW as published

Sources and what each figure counts
    By province

    All province figures
    ProvinceThis atlas, BestReference Ratio
    Panel orientation
    Fitted tilt & azimuth, from Sentinel-2 glint
    Tilt (radius) × Azimuth (angle) 0 measured
    rooftop generator ground plant unreachable by this sensor's fixed overpass time
    0%
    of ≥ 1,000 m² installations get a pose in this plot at all -- the rest never produce two self-consistent spikes, so there's nothing to fit
    ≥1 spike, no fittable pose; 0%
    no glint signal at all 0%
    azimuth range observed –
    tilt IQR observed –

    What is PV glint and how is it detected?

    PV Glint is a brief, brighter-than-diffuse flash where a panel's specular reflection lines up with the sun and Sentinel-2's fixed overpass geometry on one date -- see the method page for the full derivation and an annotated image gallery. A single spike can't be checked for self-consistency -- 0% of installations glint once (or on dates that disagree on a panel geometry) and so are correctly detected as "PV is probably here" but carry no orientation information.

    Why the plot only fills part of the circle

    Sentinel-2 crosses this latitude at a fixed ~10:30 local time, so in every image of the survey window the sun's azimuth at the moment of overpass never once swings west of due south -- a panel facing southwest, west, or north cannot glint into this sensor no matter how long you wait. That's a sensor limit, not a property of rooftops here: the shaded wedge (0° wide) marks orientations this survey cannot observe at all, not orientations known to be empty. Nothing is plotted there, because nothing was measured there.

    Data: . Validated = a single (tilt, azimuth) explains ≥ 2 independent spike dates via the specular reflection condition, tolerance 3°. Point size ∝ √(installation area). Hover a point to see which installation it is; click it to open that installation in OpenStreetMap. The CSV download lists every point with its OSM id and coordinates. Full derivation of the glint signal this pose fit is built on: the method page. Annotated Sentinel-2 / high-res examples of what a validated spike actually looks like in the source imagery: the image gallery.

    Background
    How to read these numbers
    How the estimate is built the methods in plain language, what each can see, how they add up+
    How confident should you be in this? preliminary results, sampling caveats, independent corroboration+

    Best estimate: 86,010 MWp, with a 90% range of 76,182–97,943 MWp. The range covers two measured sources of uncertainty, not everything that could move this number. Below: what is inside the range, what is not, and how it compares with other sources.

    Inside the range:

    • The two area-to-power constants. Panel area on a roof converts at about 0.18 kWp per m², the rating of a typical module; the outline of a ground-mounted park converts at about 0.05 kWp per m², measured on parks whose capacity is known. Each is varied over its own range (90%: 0.15–0.21 and 0.035–0.075 kWp per m²).
    • How reliable the segmentation model's detections are. How often its detections turn out to be real, and how many mapped arrays it misses, were measured size class by size class against mapped installations. Those measurements have their own sampling error, which is drawn into the range.

    Outside the range, and not something more arithmetic can add back:

    • Getting the national total right is not evidence the geography is right. Cross-validated, this method's German national figure lands within a few percent of the register while the median municipality is out by roughly half, because over-prediction of the densest tenth of municipalities cancels under-prediction of the other ninety percent. Three different models whose municipal errors spanned 38–64% all produced nearly the same national number. What a grid model is consumed for is the geography, not the total.
    • In Germany, multiplying roof area by a constant does as well as the classifier. Against a per-municipality roof-area baseline, the classifier's median error (48.4%) is worse than the baseline's (37.8%). Where rooftop PV is close to ubiquitous, capacity is nearly proportional to roof area by construction. The classifier earns its keep where PV is rare -- in Pakistan it cuts the same error from 88.9% to 26.5% -- which is the regime it was built for and Germany is not.

    Treat this as an early estimate from an active research pipeline, not a census. What it offers is a reproducible way to estimate distributed solar from free satellite imagery and open-source models where official statistics are thin or missing. Expect the figures to move as the evidence behind them grows.

    There are no hand-mapped ground-truth areas behind this page, and for the small-panel half there do not need to be. Registration in Germany's Marktstammdatenregister is legally mandatory rather than voluntary, and it publishes totals per municipality -- which is exactly the quantity the small-panel estimator produces. The conversion from flagged roof area to kilowatts was therefore fitted against the register across 9,674 fully-covered municipalities, at 0.2793 kWp per m² of credited roof area, and applied countrywide as a genuine out-of-sample test. What a register cannot substitute for is a precision check on small installations: below 30 kWp it publishes no coordinates at all, so there is no way to ask whether a particular flagged roof really carries panels.

    A complete national register puts the Best estimate above too high. The Marktstammdatenregister records roughly 74.8 GWp of PV in Germany, below the figure this page reports, so read these tiers as geography -- where capacity sits -- rather than as a national total. The hand-mapped OpenStreetMap component was reconciled against the register in September 2026 and both placements now sit within about 10% of it; what remains unreconciled is the model's own detections and the small-panel half. Every other country in this project would need a register of this kind to make the same statement, and does not have one.

    Using the map and exporting figures layers, your own data, downloads, licences+

    Layers. "Show" picks the quantity the cells are coloured by: the Best estimate, the OSM-mapped capacity alone, the satellite detections above 400 m², rooftop PV below it, farm ground PV below it (arrays beside fields, where the farm detector has run), or the gap between the Best estimate and what is already mapped, which is where mapping effort pays off most. Each cell shows its total in MWp. The colour scale is logarithmic and is refitted to whichever quantity is shown; the legend always states its range.

    Your own data. "Layers" → "Add a layer" overlays a GeoJSON file, a CSV with latitude/longitude columns, a GeoJSON URL, an XYZ raster tile URL or a WMS (use {bbox-epsg-3857} in its GetMap URL). Files are read in your browser and are not uploaded anywhere. The live OpenStreetMap overlay queries the public Overpass API for the area in view when you zoom in, so it shows mapping done after this page was built.

    Exports. Every figure downloads as PNG (for slides), SVG (vector, for papers) and CSV (the numbers behind it); the map as PNG with its legend and attribution, and the grid as GeoJSON or CSV. Basemap imagery and tiles keep their own providers' terms: OpenStreetMap data is © OpenStreetMap contributors (ODbL), the grey canvas and the satellite imagery © Esri and its partners.

    Data
    Download the data behind this atlas
    Download the underlying data capacity parquets, calibration boundaries, pose survey, raw detections, model checkpoint+
    Live OSM PV, not this snapshot -- Overpass query
    [out:json][timeout:180]; area ["boundary"="administrative"] ["admin_level"="2"] ["ISO3166-1"="DE"] ->.searchArea; ( nwr["power"="generator"]["generator:source"="solar"](area.searchArea); nwr["power"="plant"]["plant:source"="solar"](area.searchArea); ); out geom;
    Paste into overpass-turbo.eu for an interactive map and GeoJSON export, or POST it as the data parameter to https://overpass-api.de/api/interpreter from a script. The raw-detections download above predates this page and will go stale as mappers keep editing; this query always reflects live OSM state.
    Capacity data

    The capacity per grid cell shown on the map, as CSV. One row per 0.1° cell, generated in your browser from the data this page is drawing, so it is exactly the numbers above. lon0/lat0 are the south-west corner of the cell. The GeoParquet carries the cell polygon in EPSG:4326, so it opens directly in QGIS or GeoPandas.

    Download GeoParquet
    Add a data layer

    Overlay your own data on the capacity map. A file is read in your browser and never leaves it; a URL is fetched by your browser, so the server must allow cross-origin requests.