Skip to content

HydroSHEDS v2 · 30 m / FullBasin

South America

Choose a processing region or explore basins. Map outlines use a 1/400° grid; the table keeps the native 30 m statistics.

Loading native region statistics…

Loading map…

Selected outline   Native processing window

Click again or press Esc to clear. More IDs appear as you zoom in.

Select a region

Click the map or a table row to compare the region and its processing window.

Region table

Native 30 m statistics · click a row to locate it on the map.

How much memory do I need?

The four choices trade larger processing windows for fewer regions. The labels above are practical starting points for processing one region at a time. L3 has no size cap: in the current tables the Amazon window needs about 111 GiB at 11 bytes per cell, and the largest North American L3 window needs about 124 GiB. A machine with 192–256 GB leaves more working space than 128 GB.

The default estimate uses 11 bytes per native window cell, the reference array budget used in the L3 planning table. Your algorithm may allocate more or fewer arrays. Adjust the budget below; operating-system memory, caches and other overhead need additional space.

Array memory = native window rows × columns × bytes per cell ÷ 2³⁰. These controls use GiB for memory budgeting. A green result only means that this array estimate fits the chosen working budget.

Download this layer

GPKG files open directly in QGIS. Polygon geometry uses the 1/400° grid; scientific attributes remain those of the native 30 m data. Basin and bnd vectors contain only basins with native area strictly greater than 1 km². The coarse basin raster also retains smaller basins that satisfy the coarse-mask support rule.