1. 1 Producing “broad-brush” water resource balances at the EEA level under the SEEAW methodology. Towards regular production of water resource account Philippe Crouzet BSS2 /Spatial group

2. 2 Place of the accounts in the process Immediate term: 2008 water resource report, provisional data flows Report output, issues analysis Fuelling water resource accounts with best available data From now, for the next 4 years: implementing water resource accounts Assessing data gaps and data inconsistencies, harmonising data sources vs. nomenclatures Capacity building for the regular WA production Testing SEEAW on a large area (only limited experiments for the time being) Fuelling the indicators from optimal data

3. 3 What are natural assets resource accounts? SEEA 2003, is a satellite system of the System of National Accounts. It comprises: Flow accounts for pollution, energy and materials. Environmental protection and resource management expenditure accounts Natural resource asset accounts. These accounts record stocks and changes in stocks of natural resources such as land, fish, forest, water and minerals Valuation of non-market flow and environmentally adjusted aggregates The water sub-system (SEEAW) is a conceptual framework for the organization of physical and economic information related to water, consistent to those of the SEEA.

4. 4 Accounting conceptual model applied to water assets accounts Do gains compensate for losses? Can gain substitute to losses? Loss of stock e.g. by usage Gain in stock e.g. by storage Has the quality of the stock been maintained?

5. 5 Accounting rationales The accounting algebra depends on the specificities of the asset: water assets account is a compromise between stocks and flows, with predominance of flows (e.g. rivers) or stocks (e.g. Glaciers, groundwater), Where flow dominated, availability is immediate, only storage spares for the future, limiting time compensation If physical transfer device does not exist (aqueduct, river, etc.), defining space compensation Processing resolution and aggregation rules must take these constraints into consideration

6. 6 Relationship resource / demand Same averages may result from opposed issues Both yearly average are WRI=0.31, vs. averages of monthly WRI being respectively 0.33 (left) and 0.71 Annual time step of accounting is relevant (even resource, even demand) Annual time step does not show the water shortage (odd resource, seasonal demand)

7. 7 Reporting accounts results Nomenclature is standard and refers to SEEAW and economic accounts nomenclatures Report is input-output table for time and space unit: Natural assets Inter-agents exchanges Example refers to test case on whole France (software check of the aggregate)

8. 8 Aims of the “broad –brush” exercise Obtain comparable results at the ‘Region basin’ (and sub-basin) and ‘RBD’ (and sub-unit) levels  “ERC2” river GIS Implement calculation processes (Nopolu) in view of regular production, Test data quality and consistency, improve data flows, improve SEEAW methodology Deliver results to link with economic data and fuel EEA SoE and other assessments

9. 9 GIS river organisation Water flows following hydrological features, the only ones that can yield consistent I/O tables, whereas WFD systems are blend of administrative and hydrological features: analytical levels and reporting levels are connected thanks to conceptual model: RBDs CCM Strahler O2 catchments

10. 10 Analytical resolution and data issues Region basins and sub-basin driven by geography plus WFD constraints, however: Hydrological aggregation area < ~50,000 km 2 for large homogeneous watersheds, WFD aggregation driven by RBD and sub- units, but RBD can be disjoined, very large, overlapping sea areas -> functional RBDs and functional sub-units Data disaggregation at the adequate analytical level is a complex issue, to solve by a feed-back process Rhone/CH : >=2 FSU Po / CH : >= 4FSU

11. 11 From CCM2 to ERC: huge preparation CCM2 “basins” (source for “Region basins”): 91,912 -11332 spurious= 80,580 At least 30,000 inconsistent, because of area <0.1 km2 ~15,000 only > 10km2 Poor information on sub-units jeopardises GIS building

12. 12 Data sources and issues Rainfall: ATEAM (ready) / MARS (signed provisional agreement) / ECMWF (underway) Run-off: On the basis of 500 -1000 analytical (unitary catchments), 500 to 4000 gauging stations monthly data required, process underway with ETC/W Usage data should follow the rule “accuracy results from precision in large components”, and is under progress Urban areas and % of urban pop. vs. RBD limits

13. 13 Ways data shall be processed and included: Rainfall Raw: from data, control vs. recent sources and homogenisation, Evaporation: likely to be modelled with temperature and vapour pressure (Turc or likely Penman formula, since vapour pressure is available (albeit wind is not) and vegetation cover known from CLC or taken from only recent data sets

14. 14 Ways data shall be processed and included: run-off From gauging stations, monthly data, extrapolated between stations or nodes, taking abstractions and returns into account Storage: only large lakes and reservoirs considered (data source Eldred2 and lakes layers). Where local storage changes are known, they are considered, especially where refilling is one over N years.

15. 15 Ways data shall be processed and included: groundwater Only major aquifer systems to be delineated (no EU GW GIS available), supported by inputs from EGS, Data from WaterBase / data collection at the RBD. Groundwater inflow / outflow if a weak point of the hydrosystems functioning knowledge for the time being

16. 16 Ways data shall be processed and included: abstractions and return flows (domestic and industry) From individual data for large sources, where available. Larges sources (threshold to define) are processed individually, even though no individual data exist (volume, origin of water, seasonalisation) Smaller sources processed statistically, by difference within a statistical data provision unit EPR data set mobilised to find industrial data Sewage outputs considered when potentially changing water balance (watershed transfer) and contributes to GW -> SW balance

17. 17 Ways data shall be processed and included: seasonal demands Tourism data poorly known, although making the largest seasonal changes in location of demand and returns (irrigation being only time depending) Origin of movements (minus demand) lesser known that target of movements (larger demand)

18. 18 Ways data shall be processed and included: irrigation Data sources to refine, with the EEA specialists and agricultural experts from another framework contract Potential impact as dry-out of small water bodies not addressed in the broad-brush assessment.

19. 19 Thanks for your attention