Example2: Analysis of the arable lands

[jachym]

In order to prepare the analysis of arable land should be downloaded e.g. a layer
with the data of the Land Classification. At the beginning, you can analyse the
available data by query. You can easily select attributes with QGIS and one of
the available tools – Geoprocessing tool- Dissolve. Thanks to this you can select
the appropriate information and create new layers. For each layer, you can
assign an appropriate display style.

[jachym]

There are two possible ways how to solve this:

1. We prepare static map of "arable" lands, based on corine land cover dataset (for example)
   https://land.copernicus.eu/pan-european/corine-land-cover/clc-2012?tab=download
   and perform manual classification, the result will be map of arable lands.
2. Dynamic web procesing service will be needed. It's standard raster reclassification (assign new values of raster map based on input data values).

Static map

1. Download the raster map of corine landcover
   Use classes 12,13,14,15,16,17,18,19,20,21, leave the rest

[jachym]

Arable lands from Corine, categories 12-21

[jachym]

Use WebProcessingService, process ras:RangeLookup with following input

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<wps:Execute service="WPS" version="1.0.0" xmlns:wps="http://www.opengis.net/wps/1.0.0" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 ../wpsExecute_request.xsd">
	<ows:Identifier>ras:RangeLookup</ows:Identifier>
	<wps:DataInputs>
		<wps:Input>
			<ows:Identifier>coverage</ows:Identifier>
            <wps:Reference xlink:href="" />
		</wps:Input>
		<wps:Input>
			<ows:Identifier>band</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>1</wps:LiteralData>
            </wps:Data>
		</wps:Input>
		<wps:Input>
			<ows:Identifier>ranges</ows:Identifier>
            <wps:Data>
                14;21
            </wps:Data>
		</wps:Input>
		<wps:Input>
			<ows:Identifier>outputPixelValues</ows:Identifier>
            <wps:Data>
                    1
            </wps:Data>
		</wps:Input>
		<wps:Input>
			<ows:Identifier>noData</ows:Identifier>
            <wps:Data>
                    0
            </wps:Data>
		</wps:Input>
	</wps:DataInputs>
</wps:Execute>

NOTE: The first input coverage is missing attribute xlink:href - Corine would have to be published as WCS layer on EOClimLab server (which does not seem to be).