Yemen's PV Atlas

EarthPV CalibrationBronzeSilver otherwise.
Needs more leads mapped in
OpenStreetMap to localize the model.
Add local training data →
Yemen 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
installations mapped in OpenStreetMap supplies 44% of Best; the farm ground-PV detector (arrays beside fields, below 400 m²) (29%) and TerraMind segmentation of large arrays (26%) 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: 586 MWp, with a 90% range of 480–774 MWp. The range covers three measured sources of uncertainty, not everything that could move this number. Below: what is inside the range, what is not, and what calibration areas it rests on.

    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.
    • Which farm areas the farm ground-PV estimate was fitted on. Its ratio of mapped panel area to detected area is refitted on random re-draws of the completely mapped farm areas (bootstrap over 6 mapped farm areas in Tihama; 1 in 'Amran (fewer than 3) a stated x/÷2 judgement).

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

    • The calibration areas were chosen by hand, not drawn at random, so the range is not a statistical margin of error for the country. Re-drawing them shows how much the areas disagree with each other, not how far the places the estimate is applied to differ from all of them. Only a random sample of areas can measure that.
    • "Every panel mapped" holds as of the mapping imagery, which is older than the satellite imagery. Panels installed in between are missing from the reference: the model's detections of them count as false alarms and its misses of them go uncounted. Each of these makes this figure more likely too low than too high.
    • Small household systems on roofs are not on this page yet. One area of Yemen, Al Wehdah in Sana'a, has been mapped panel by panel, but a per-building rooftop classifier has not yet been fitted to it. Rooftop solar here is either hand-mapped in OpenStreetMap or an array the segmentation model outlined directly, which in practice means installations of roughly 400 m² and up. Small solar-irrigation arrays beside fields are estimated, but only in farm cells that resemble the mapped farm areas.
    • Imagery covers where people live, plus every mapped solar site. Map cells were imaged if they hold at least 1,000 buildings or any hand-mapped solar installation. A utility-scale park built on empty land that nobody has mapped yet falls outside both rules and is not on this page.
    • Solar parks the model outlines but nobody has mapped are not counted. The detector draws the Aden plant and smaller parks on the Red Sea coast, but they are not in OpenStreetMap, and a model outline above 100,000 m² only counts when it carries a mapped plant geometry. The same rule removes the dark rock outcrops of that size the model mistakes for panels. Mapping the parks would bring them into the verified layer.
    • OpenStreetMap coverage is uneven. Hand-mapped solar is concentrated where volunteer mappers have worked, so the verified layer says as much about mapping effort as about where panels are.

    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.

    The ground-truth areas: seven farm areas, drawn and mapped by hand, not a random sample. The farm ground-PV figure is calibrated on the test ground around Huth in 'Amran, traced panel by panel, and on six areas of a Tihama region near Zabid where every installation was checked by hand, about 460 km² in all. Most of Tihama's installations were mapped in 2023 as rectangles around the whole site rather than the panels; those count at the open-ground rate, not as panel area. The areas lie in two regions, so the range measured over them says how much the result moves between farms in those two landscapes, not across Yemen, and the estimate is only applied to map cells whose share of cropland, density of buildings and elevation resemble them (lowland plain for Tihama, highland for 'Amran). A further area, Al Wehdah in Sana'a, is mapped panel by panel for a rooftop classifier that has not been fitted yet; no figure uses it.

    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"="YE"] ->.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.