1 Challenge the future INSPIRE coverages Modelling Land Use coverages for INSPIRE

2 Challenge the future Overview Land Use in INSPIRE Introduction to coverages Land use modeling Land use coverages

3 Challenge the future INSPIRE: Land Use My task: Make an information model for Land Use according to INSPIRE rules Definition of Land Use: Territory characterised according to its current and future planned functional dimension or socio–economic purpose (e.g. residential, industrial, commercial, agricultural, forestry, recreational). Ground rule of land use experts: Each piece of land has exactly one land use category! No gaps (category UNUSED) no overlap (category MULTIPLE LAND USE)  Land Use is a Coverage!

4 Challenge the future Coverages feature that acts as a function to return values from its range for any direct position within its spatial, temporal or spatiotemporal domain In modeling a coverage is defined by defining a type for its domain and range

5 Challenge the future Main characteristic of Coverage Continuous (useful interpolation in range values) Discrete (interpolation on range is useless)

6 Challenge the future Coverage implementation Different implementations Raster/Grid Topological Structure TIN Collection: Points Lines + interpolation method Polygons Choice depends on: The way the data is acquired The way the data is used Storage considerations

7 Challenge the future Raster Coverage Continuous Discrete Efficient encoding in files: -Implicit domain geometry -Range values can be compressed

8 Challenge the future Topology Coverage

9 Challenge the future TIN Coverage

10 Challenge the future Point coverage implementation ContinuousDiscrete

11 Challenge the future Line coverage implementation ContinuousDiscrete

12 Challenge the future Polygon coverage implementation ContinuousDiscrete

13 Challenge the future Categorizing land use Coverages Coverages are always discrete (no interpolation) Land use is a discrete coverage in all member states implemented as: Raster coverage Polygon coverage Point coverage (LUCAS)

copyright Eurostat 2011 LUCAS: Land cover dataset for Europe points LAND COVER classes 1 ARABLE LAND 2 PERMANENT CROPS 3 GRASSLAND 4 WOODED AREAS AND SHRUBLAND 5 BARE LAND, RARE VEGET. 6 ARTIFICIAL LAND 7 WATER First phase sample for stratification: orthophoto interpretation 2km squared grid Ground survey Parameters Land cover Land use pictures etc. Sample of around 260,000 pts Second phase sample: in-situ data collection

15 Challenge the future LUCAS (Land use/cover area frame survey

16 Challenge the future Land Use Range The classification value is a complex object  Land Use is always a discrete coverage

17 Challenge the future What does INSPIRE offer In the Proposed Changes to the Generic Conceptual Model and Encoding Guidelines one chapter about coverages Based on ISO Coverages and ISO Two coverage hierarchies: 1.Coverage-As-Polygon-Value-Pair 2.Coverage-By-Domain-And-Range

18 Challenge the future Discrete Coverage Geometry Value Pairs Model Discrete point coverage Discrete polygon coverage

19 Challenge the future Coverage by Domain and Range model Discrete coverage here

20 Challenge the future Coverage by Domain and Range Discrete point coverage Discrete surface coverage Discrete grid coverage This shared superclass I chose as base class for Land Use

21 Challenge the future Land Use Coverage as a DiscreteCoverage

22 Challenge the future Now the encoding part. The UML diagram model is automatically translated to a GML application schema.

23 Challenge the future Implementation of Coverage by Domain and Range Four options for Range: ValueArray homogeneous arrays of primitive and aggregate values. AbstractScalarValueList List of scalar values DataBlock Tuples of values are stored as a long list of Comma Separate Values. File Actual data is stored in a file outside GML Not what I want What I want but not the way I want it. Might be right for gridded data. So I went for a Coverage by Geometry Value Pairs

24 Challenge the future Implementation of Coverage by Geometry-Value-Pairs It works but…. Hi Wilko, I had a quick look and there are quite a number of issues in the XML so I would suggest not to present it as a sample template. I am also convinced that the coverage representation is not the right way, but that is a separate issue.

25 Challenge the future Conclusions / Limitations INSPIRE coverage model is unclear: Why do we have two types of coverages in the top of the hierarchy? INSPIRE coverage implementation wrong: Why do I have to provode a domain and range if I want to encode a Coverage- by-geometry-value-pair? Now I have GML but how to serve it Efficiently (WCS???) Time for a major revision of coverages in: INSPIRE, OGC and ISO/TC 211