Stichting RIONED · Publieke Dienstverlening Op de Kaart

Dutch source

Municipal sewer networks (GWSW)

The sewer management data of municipalities that share it under the Urban Water Data Dictionary (GWSW) of the RIONED foundation: pipes with material, diameter and construction year, manholes, pumps, structures, house connections and discharge points such as combined sewer overflows. On 16 October 2026 it held 1.8 million pipes, 1.45 million manholes and 14,905 discharge points from 144 municipalities (out of 342), plus one dataset from the water authorities. Via PDOK as OGC API, WFS, WMS and GeoPackage.

Housing and land Climate and environmentOpenAPIMap layerDownloadNetherlands · pipe and manhole

Up to date · updated yesterday · checked 17:23

Sewer pipes in the GWSW by material: most PVC (683,213 pipes), then concrete and PE (polyethylene)

Sewer pipes in the GWSW by material, October 2026, in pipes. Total: 1,799,360; the largest 12 of 13 categories are shown. PVC is 38% of the total. 232,889 pipes have no or another material. Only municipalities that share their sewer data through the GWSW.

Source: Stichting RIONED, GWSW Beheer stedelijk water via PDOK (WFS) · opgehaald 25 oktober 2026Open the table Single block

What can you do with it?4 ideas

Getting started

Where does the sewer overflow?

The beheerlozing collection has 14,905 discharge points: external overflows (in heavy rain sewage flows into a ditch or canal), outlets and emergency outlets. Map them next to bathing water.

Getting started

Where is asbestos cement still in the ground?

11,900 pipes are asbestos cement, 683,489 PVC and 682,052 concrete. Colour a map by material or compute the share of old materials per municipality.

Advanced

How old is the sewer?

The begindatum field gives a pipe's construction year. Build an age profile per neighbourhood and compare it with the municipality's sewer plan.

Advanced

Which municipalities share their sewer data?

The dataset field names the municipality. On 16 October 2026 there were 144; the rest of the country is missing. A map of who takes part and who doesn't is already a story.

How to process it4 steps

Overflows of one municipality
The OGC API only filters on a few fields per collection. Use a bbox around the municipality (in degrees), at most 1,000 per page, and follow the next link.
```
https://api.pdok.nl/rioned/beheer-stedelijk-watersystemen-gwsw/ogc/v1/collections/beheerlozing/items?f=json&limit=1000&bbox=5.05,52.05,5.17,52.13
```
Counting with the WFS
The WFS of the same dataset gives totals with resultType=hits. Material is a GWSW URI with a version (…/1.6/totaal/PVC): count with PropertyIsLike on */PVC.
```
https://service.pdok.nl/rioned/beheer-stedelijk-watersystemen-gwsw/wfs/v1_0?service=WFS&version=2.0.0&request=GetFeature&resultType=hits&typeNames=beheerlozing
```

One municipality via the WFS

Filter on the dataset field (the full URL with the municipality name without spaces, e.g. Utrecht, UtrechtseHeuvelrug, DenHaag) and request GeoJSON in degrees.

https://service.pdok.nl/rioned/beheer-stedelijk-watersystemen-gwsw/wfs/v1_0?service=WFS&version=2.0.0&request=GetFeature&typeNames=beheerlozing&outputFormat=application/json&srsName=EPSG:4326&count=100&FILTER=%3CFilter%3E%3CPropertyIsEqualTo%3E%3CPropertyName%3Edataset%3C/PropertyName%3E%3CLiteral%3Ehttps://apps.gwsw.nl/item_config?dataset=Utrecht%3C/Literal%3E%3C/PropertyIsEqualTo%3E%3C/Filter%3E

Everything in one file
The GeoPackage with all collections is 2.96 GB and is refreshed daily (Last-Modified 15 October 2026). The ATOM feed lists the file.
```
https://service.pdok.nl/rioned/beheer-stedelijk-watersystemen-gwsw/atom/index.xml
```

Interesting combinations

datum en coördinaten (dichtstbijzijnd station)

How often is there enough rain to trigger the overflows?

The GWSW shows where the overflows are; count with KNMI daily data how often more than 20 millimetres fell in a day. Actual overflow measurements are not in the GWSW.

Combine with KNMI daily weather data

buurtcode (ruimtelijk koppelen)

Metres of sewer per resident

Sum pipe length per neighbourhood (field lengte_leiding) and divide by the population from the CBS neighbourhood figures.

Combine with Key figures for districts and neighbourhoods

Similar sources

Water authority data (IMWA and DAMO)
The water authorities manage what comes next: sewage pumping stations, pressure mains and treatment plants (wastewater chain DAMO). The GWSW covers the municipal sewer up to that handover point.
RS
Richtlijn stedelijk afvalwater (Rijkswaterstaat) not in the index yet
National reporting to the EU on sewer systems and treatment plants, much coarser than the GWSW.
OpenStreetMap
OSM has almost no underground pipes; the GWSW is the only open source at this level of detail.

What to watch out for

Not nationwide
Only municipalities that share their management data through the GWSW. On 16 October 2026 we counted 144 municipality names in the dataset field (some with a second _Aansluitingen set) and one set from the water authorities. Amsterdam and Rotterdam are missing.
Codes as URLs with a version
Type and material are data.gwsw.nl URIs with a version number (1.4, 1.5, 1.6, 1.7). The same type therefore appears under four names: look at the last part. Some municipalities use their own abbreviations (pp for polypropylene).
Many fields empty
231,022 of the 1,799,881 pipes have no or an unusual material. Dates are sometimes an empty string instead of null.
No totals in the OGC API
The OGC API returns no numberMatched and at most 1,000 objects per page. Use the WFS (resultType=hits) for counts; a filtered count over all pipes takes 3 to 8 seconds.

APIOGC WFS 2.0.0 · read 16 Oct 2026

StandardOGC WFS 2.0.0docs

Access no key

No key. Fees: none; access constraints: https://creativecommons.org/publicdomain/zero/1.0/deed.nl. from the description

Size14,905

features in beheerstedelijkwater:BeheerLozing tested

Formats

application/gml+xml; version=3.2text/xml; subtype=gml/3.2.1text/xml; subtype=gml/3.1.1application/json; subtype=geojsonapplication/json

Base URL

https://service.pdok.nl/rioned/beheer-stedelijk-watersystemen-gwsw/wfs/v1_0

Endpoints 5

GET?request=GetCapabilitiesservice description
GET?request=DescribeFeatureTypefields of a layer (XSD)
GET?request=GetFeaturethe features themselves, with geometry
GET?request=ListStoredQueriesstored queries
GET?request=DescribeStoredQueriesstored query details

Layers and projections

Aansluitleidingbeheerstedelijkwater:AansluitingLeidingEPSG:28992, EPSG:25831, EPSG:25832, EPSG:3034, EPSG:3035, EPSG:3857, EPSG:4258, EPSG:4326
Pompbeheerstedelijkwater:BeheerPompEPSG:28992, EPSG:25831, EPSG:25832, EPSG:3034, EPSG:3035, EPSG:3857, EPSG:4258, EPSG:4326
Bouwwerkbeheerstedelijkwater:BeheerBouwwerkEPSG:28992, EPSG:25831, EPSG:25832, EPSG:3034, EPSG:3035, EPSG:3857, EPSG:4258, EPSG:4326
Putbeheerstedelijkwater:BeheerPutEPSG:28992, EPSG:25831, EPSG:25832, EPSG:3034, EPSG:3035, EPSG:3857, EPSG:4258, EPSG:4326
Aansluitpuntbeheerstedelijkwater:AansluitingPuntEPSG:28992, EPSG:25831, EPSG:25832, EPSG:3034, EPSG:3035, EPSG:3857, EPSG:4258, EPSG:4326
Leidingbeheerstedelijkwater:BeheerLeidingEPSG:28992, EPSG:25831, EPSG:25832, EPSG:3034, EPSG:3035, EPSG:3857, EPSG:4258, EPSG:4326
Lozingbeheerstedelijkwater:BeheerLozingEPSG:28992, EPSG:25831, EPSG:25832, EPSG:3034, EPSG:3035, EPSG:3857, EPSG:4258, EPSG:4326
Gebiedbeheerstedelijkwater:BeheerGebiedEPSG:28992, EPSG:25831, EPSG:25832, EPSG:3034, EPSG:3035, EPSG:3857, EPSG:4258, EPSG:4326

Filtering from the description

OGC Filter Encoding (FES 2.0)

PropertyIsEqualToPropertyIsNotEqualToPropertyIsLessThanPropertyIsGreaterThanPropertyIsLessThanOrEqualToPropertyIsGreaterThanOrEqualToPropertyIsLikePropertyIsBetweenPropertyIsNullEqualsDisjointTouchesWithinOverlapsCrossesIntersectsContainsDWithinBeyondBBOXDuring

Parameters 6

`typeNames`	which layer: beheerstedelijkwater:AansluitingLeiding, beheerstedelijkwater:BeheerPomp, beheerstedelijkwater:BeheerBouwwerk, beheerstedelijkwater:BeheerPut, beheerstedelijkwater:AansluitingPunt, beheerstedelijkwater:BeheerLeiding, beheerstedelijkwater:BeheerLozing, beheerstedelijkwater:BeheerGebied	from the description
`outputFormat`	e.g. application/json for GeoJSON	from the description
`srsName`	projection, e.g. EPSG:4326 for web maps (default EPSG:28992, RD)	from the description
`count / startIndex`	paging	from the description
`filter`	FES XML filter on fields or geometry	from the description
`bbox`	box in the chosen projection	platform

Fields 12 · beheerstedelijkwater:BeheerLozing

Name	Type	Meaning
`geom`	geometrie
`dataset`	string
`stelsel`	string
`stelseltype`	string
`naam`	string
`uri`	string
`type`	string
`begindatum`	string
`einddatum`	string
`drempelniveau`	double
`drempelbreedte`	long
`fuuid`	string

Limits and pitfalls

At most 1,000 features per request (CountDefault). from the description
Paging supported: count and startIndex (ImplementsResultPaging). from the description
A filter with many conditions (e.g. 150 PropertyIsNotEqualTo) does not fit in a URL: send the WFS request as a POST with XML. That worked on 16 October 2026. tested
Layer names are case-insensitive (beheerlozing = BeheerLozing). Field names in the WFS sometimes differ from the OGC API (materiaal_leiding is returned as materiaalLeiding). tested

Try it HTTP 200 · 274 ms · 16 Oct

https://service.pdok.nl/rioned/beheer-stedelijk-watersystemen-gwsw/wfs/v1_0?request=GetFeature&service=WFS&version=2.0.0&typeNames=beheerstedelijkwater:BeheerLozing&outputFormat=application/json&srsName=EPSG:4326&count=1&propertyName=naam,type,stelsel,dataset

{
  "type": "FeatureCollection",
  "name": "BeheerLozing",
  "crs": {
    "type": "name",
    "properties": {
      "name": "urn:ogc:def:crs:OGC:1.3:CRS84"
    }
  },
  "features": [
    {
      "type": "Feature",
      "properties": {
        "dataset": "https://apps.gwsw.nl/item_config?dataset=Meierijstad",
        "stelsel": "EB/Erp De Bolst",
        "naam": "123 OVST",
        "type": "http://data.gwsw.nl/1.6/totaal/ExterneOverstortput"
      },
      "bbox": [
        5.60296378387015,
        51.60742967926958
      ],
      "geometry": {
        "type": "MultiPoint",
        "coordinates": "…"
      }
    }
  ],
  "bbox": [
    5.60296378387015,
    51.6074296792696
  ]
}

Shortened response, saved at harvest time. Click the URL for the real, current response.

Read from GetCapabilities: layers, projections, formats, filters, limit · DescribeFeatureType: fields of beheerstedelijkwater:BeheerLozing. Labels: from the description stated in what the api itself publishes. tested from our own small call. platform applies to every api on this platform, per its documentation. experience learned while building open data index.

How to fetch it

curl "https://api.pdok.nl/rioned/beheer-stedelijk-watersystemen-gwsw/ogc/v1/collections/beheerlozing/items?f=json&limit=5"