Details

Visibility: Public
Owner: Nissim Lebovits
Created: 17 Aug 2026
Last Updated: 17 Aug 2026

Analytics

28 days

Downloads

9,660

Data served

3.4 GB

Countries

28-day downloads

29 Jul 2026

25 Aug 2026

Analytics

Moldova Geodata

RO. Catalog cloud-native cu date selectate din geoportalul național geodata.gov.md. Româna este limba de referință. Textele în rusă și engleză sunt traduceri. Catalogul nu este o publicație oficială a AGCC.

RU. Облачный каталог избранных данных национального геопортала geodata.gov.md. Румынский текст является основным; русский и английский тексты — переводы. Каталог не является официальной публикацией AGCC.

EN. A cloud-native catalog of selected data from Moldova’s national geoportal, geodata.gov.md. Romanian is authoritative; Russian and English are translations. This is not an official AGCC publication.

Name: AGENTS.md
Size: 5.81 KB
Content Type: text/markdown; charset=utf-8
Last Modified: 17 Aug 2026
Source URL: https://data.source.coop/nlebovits/moldova-geodata/utilities/waterpipe/AGENTS.md
Cloud URI: s3://us-west-2.opendata.source.coop/nlebovits/moldova-geodata/utilities/waterpipe/AGENTS.md

Download

Object Preview

AGENTS.md — WaterPipe

Despre date / О данных / About the data

RO. Conductă de apă. Conține 13 493 puncte extrase din spațiul de lucru utilities al serverului geodata.gov.md prin WFS 2.0.0 la data de 2026-08-16. Coordonatele sunt păstrate în sistemul sursă MOLDREF99 / Moldova TM (EPSG:4026).

RU. Водопроводная труба. Содержит 13 493 точек, извлечённых из рабочего пространства utilities сервера geodata.gov.md через WFS 2.0.0 от 2026-08-16. Координаты сохранены в исходной системе MOLDREF99 / Moldova TM (EPSG:4026).

EN. Water pipe. Holds 13 493 points extracted from the utilities workspace of geodata.gov.md over WFS 2.0.0 on 2026-08-16. Coordinates are kept in the source system, MOLDREF99 / Moldova TM (EPSG:4026).

Overview

13,493 features extracted from utilities:WaterPipe on the geodata.gov.md GeoServer over WFS 2.0.0 on 2026-08-16, and verified against the server's own feature count.

Coordinates are MOLDREF99 / Moldova TM (EPSG:4026): projected, in metres, and the source's own system. They are not reprojected. ST_Area returns square metres directly, and a spatial predicate written against a WGS84 envelope will match nothing without raising an error.

Access

Schema

Column	Type	Notes
`pipeDiameter`	BIGINT	49 distinct values
`pressure`	VARCHAR	Empty in every row. The source publishes the column and no values
`waterType`	VARCHAR	A single value throughout: `potable`
`waterPipeType`	VARCHAR	2 distinct values
`averageVolume`	VARCHAR	Empty in every row. The source publishes the column and no values
`maxCapacity`	VARCHAR	Empty in every row. The source publishes the column and no values
`pipeCoatingType`	VARCHAR	Empty in every row. The source publishes the column and no values
`pipeMaterialType`	VARCHAR	7 distinct values

Measured distributions

waterPipeType, 2 distinct values, most common first:

Value	Rows
`None`	6,439
`LL`	5,535
`ML`	1,519

pipeMaterialType, 7 distinct values, most common first:

Value	Rows
`None`	7,320
`PE`	3,238
`steel`	1,721
`castIron`	1,108
`PVC`	52
`asbestos`	44
`compositeConcrete`	9
`concrete`	1

utilityDeliveryType, 2 distinct values, most common first:

Value	Rows
`distribution`	13,474
`transport`	19

Data quality

Feature count matches the server's resultType=hits exactly, so nothing was lost to a capped WFS response.
pressure, averageVolume, maxCapacity, pipeCoatingType are empty in every row. The source publishes the columns and no values, so treat them as absent.
waterType, pipeShapeType carry one value throughout, so they cannot discriminate.
The upstream server answers from several backends that disagree about which layers exist. See the catalog's known-issues page.

Example queries

Row count:

Distribution of waterPipeType:

Rows carrying geometry. Some layers hold null geometries, so filter before a spatial predicate:

Spatial filtering

This file is Hilbert-ordered and carries a bbox struct with GeoParquet 1.1 covering metadata. That combination makes row groups spatially coherent, so a bounding-box predicate lets the reader skip most of the file unread.

DuckDB does not apply it for you. Writing it yourself is worth 3-7x on a spatial query, measured on this catalog:

Coordinates are metres, so those bounds are a 10 km box.

cadastru_data_uat2 holds the 35 second-level administrative units and is the join target for anything aggregated by raion or municipality. Both sides are EPSG:4026, so a spatial join needs no transform. Prefilter on each raion's bounds so the expensive predicate runs on a fraction of the rows:

The catalog's own AGENTS.md covers the join keys and the quirks that apply across every collection here.

AGENTS.md — WaterPipe

Despre date / О данных / About the data

Overview

13,493 features extracted from utilities:WaterPipe on the geodata.gov.md GeoServer over WFS 2.0.0 on 2026-08-16, and verified against the server's own feature count.

Access

Schema

Column	Type	Notes
`pipeDiameter`	BIGINT	49 distinct values
`pressure`	VARCHAR	Empty in every row. The source publishes the column and no values
`waterType`	VARCHAR	A single value throughout: `potable`
`waterPipeType`	VARCHAR	2 distinct values
`averageVolume`	VARCHAR	Empty in every row. The source publishes the column and no values
`maxCapacity`	VARCHAR	Empty in every row. The source publishes the column and no values
`pipeCoatingType`	VARCHAR	Empty in every row. The source publishes the column and no values
`pipeMaterialType`	VARCHAR	7 distinct values

Measured distributions

waterPipeType, 2 distinct values, most common first:

Value	Rows
`None`	6,439
`LL`	5,535
`ML`	1,519

pipeMaterialType, 7 distinct values, most common first:

Value	Rows
`None`	7,320
`PE`	3,238
`steel`	1,721
`castIron`	1,108
`PVC`	52
`asbestos`	44
`compositeConcrete`	9
`concrete`	1

utilityDeliveryType, 2 distinct values, most common first:

Value	Rows
`distribution`	13,474
`transport`	19

Data quality

Feature count matches the server's resultType=hits exactly, so nothing was lost to a capped WFS response.
pressure, averageVolume, maxCapacity, pipeCoatingType are empty in every row. The source publishes the columns and no values, so treat them as absent.
waterType, pipeShapeType carry one value throughout, so they cannot discriminate.
The upstream server answers from several backends that disagree about which layers exist. See the catalog's known-issues page.

Example queries

Row count:

Distribution of waterPipeType:

Rows carrying geometry. Some layers hold null geometries, so filter before a spatial predicate:

Spatial filtering

DuckDB does not apply it for you. Writing it yourself is worth 3-7x on a spatial query, measured on this catalog:

Coordinates are metres, so those bounds are a 10 km box.

The catalog's own AGENTS.md covers the join keys and the quirks that apply across every collection here.

1INSTALL spatial; LOAD spatial; INSTALL httpfs; LOAD httpfs;
2
3SELECT *
4FROM read_parquet('https://data.source.coop/nlebovits/moldova-geodata/utilities/waterpipe/utilities_waterpipe.parquet')
5LIMIT 10;

1INSTALL spatial; LOAD spatial; INSTALL httpfs; LOAD httpfs;
2
3SELECT *
4FROM read_parquet('https://data.source.coop/nlebovits/moldova-geodata/utilities/waterpipe/utilities_waterpipe.parquet')
5LIMIT 10;

1SELECT count(*) FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet');

1SELECT count(*) FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet');

1SELECT "waterPipeType", count(*) AS n
2FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet')
3GROUP BY 1 ORDER BY n DESC;

1SELECT "waterPipeType", count(*) AS n
2FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet')
3GROUP BY 1 ORDER BY n DESC;

1INSTALL spatial; LOAD spatial;
2
3SELECT count(*)
4FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet')
5WHERE geometry IS NOT NULL;

1INSTALL spatial; LOAD spatial;
2
3SELECT count(*)
4FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet')
5WHERE geometry IS NOT NULL;

1INSTALL spatial; LOAD spatial;
2
3-- bbox first, then the exact test on what survives
4SELECT count(*)
5FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet')
6WHERE bbox.xmin >= 200000 AND bbox.xmax <= 210000
7  AND bbox.ymin >= 180000 AND bbox.ymax <= 190000
8  AND ST_Within(geometry, ST_MakeEnvelope(200000, 180000, 210000, 190000));

1INSTALL spatial; LOAD spatial;
2
3-- bbox first, then the exact test on what survives
4SELECT count(*)
5FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet')
6WHERE bbox.xmin >= 200000 AND bbox.xmax <= 210000
7  AND bbox.ymin >= 180000 AND bbox.ymax <= 190000
8  AND ST_Within(geometry, ST_MakeEnvelope(200000, 180000, 210000, 190000));

1INSTALL spatial; LOAD spatial;
2
3WITH units AS (
4  SELECT name, geometry,
5         ST_XMin(geometry) x0, ST_YMin(geometry) y0,
6         ST_XMax(geometry) x1, ST_YMax(geometry) y1
7  FROM read_parquet('cadastru/uat2/cadastru_data_uat2.parquet')
8)
9SELECT u.name, count(*) AS n
10FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet') x
11JOIN units u
12  ON x.bbox.xmin BETWEEN u.x0 AND u.x1
13 AND x.bbox.ymin BETWEEN u.y0 AND u.y1
14 AND ST_Within(ST_Centroid(x.geometry), u.geometry)
15GROUP BY u.name
16ORDER BY n DESC;

1INSTALL spatial; LOAD spatial;
2
3WITH units AS (
4  SELECT name, geometry,
5         ST_XMin(geometry) x0, ST_YMin(geometry) y0,
6         ST_XMax(geometry) x1, ST_YMax(geometry) y1
7  FROM read_parquet('cadastru/uat2/cadastru_data_uat2.parquet')
8)
9SELECT u.name, count(*) AS n
10FROM read_parquet('utilities/waterpipe/utilities_waterpipe.parquet') x
11JOIN units u
12  ON x.bbox.xmin BETWEEN u.x0 AND u.x1
13 AND x.bbox.ymin BETWEEN u.y0 AND u.y1
14 AND ST_Within(ST_Centroid(x.geometry), u.geometry)
15GROUP BY u.name
16ORDER BY n DESC;

Moldova Geodata

AGENTS.md — WaterPipe

Despre date / О данных / About the data

Overview

Access

Schema

Measured distributions

Data quality

Example queries

Spatial filtering

Related collections

AGENTS.md — WaterPipe

Despre date / О данных / About the data

Overview

Access

Schema

Measured distributions

Data quality

Example queries

Spatial filtering

Related collections