Waterbase

The European Environment Agency's family of state-of-environment water tables covering rivers, lakes, groundwater and emissions to water, released in bulk as CSV and SQLite files totalling tens of millions of rows across Europe.

In this catalog it appears concretely: - EEA Data and Maps - Water short_description — "Waterbase state-of-environment tables for rivers, lakes, groundwater and emissions with CSV/SQLite downloads". - tags on the EEA (catalog record) — "waterbase', 'wise". - estimated_size — "Tens of millions of rows across Waterbase themes; individual release ZIPs range from tens to hundreds of MB".

A label on a listing is not a deliverable. Teams that license on the strength of a product-name match routinely find the shipped files cover a narrower slice than they assumed, and backfilling history afterwards costs more than the license ever did.

The failure mode is concrete: a source can carry the Waterbase label while differing from what you need on exactly the dimension that matters — Waterbase state-of-environment tables for rivers, lakes, groundwater and emissions with CSV/SQLite downloads. Comparing two sources on that line usually settles the choice faster than any feature matrix.

You rarely have to take a vendor's word for it. 82.4% of the 1,744 datasets Datadory catalogs are free to access, and EEA Data and Maps - Water short_description lets you inspect the real artifact before any budget is committed.

Treat every claim of this attribute as testable:

1. Open EEA Data and Maps - Water short_description and confirm its record — "Waterbase state-of-environment tables for rivers, lakes, groundwater and emissions with CSV/SQLite downloads" — against the files you actually receive. 2. Read tags on the EEA's record on catalog record — "waterbase', 'wise" — then confirm the delivered artifact matches before you license anything. 3. Open estimated_size and confirm its record — "Tens of millions of rows across Waterbase themes; individual release ZIPs range from tens to hundreds of MB" — against the files you actually receive. 4. Pin down update cadence in writing.

Adjacent concepts worth reading next: - determinand - discodata sql access - monitoring-site level statistics - wise dashboards