ASEMARS - Europa...ASEMARS LOT I Task 2b: Development of GIS interface CGMS-SGDBE Task 3b:...

ASEMARS

LOT I

Task 2b: Development of GIS interface CGMS-SGDBE Task 3b: Development of GIS interface for CGMS-CORINE

advanced visualization

User manual

DRAFT

December 2008

Charkovská 7 101 00 Praha 10 Czech Republic

Tel./Fax: 271741935 E-mail: [email protected]

www.gisat.cz

- 2 -

User manual Draft © 2008 GISAT

CONTENT

1 INTRODUCTION........................................................................................................................................ 3

2 DATA ......................................................................................................................................................... 3

2.1 Vector data ........................................................................................................................................... 4

2.2 Attributes data ..................................................................................................................................... 4

3 RUNNING THE GIS INTERFACE ............................................................................................................. 5

4 CHECKING DATA CONNECTION ............................................................................................................ 6

5 GEOGRAPHICAL AREA SELECTION ..................................................................................................... 9

6 THEMATIC MAPS ................................................................................................................................... 13

6.1 Soil suitability maps .......................................................................................................................... 13

6.2 Dominant STU maps.......................................................................................................................... 17

6.3 Crop calendar ..................................................................................................................................... 22

6.4 Weather Indicator Maps .................................................................................................................... 24

6.5 Crop Indicator Maps .......................................................................................................................... 28

6.6 CLC & Soil Suitability Maps .............................................................................................................. 31

- 3 -


1 INTRODUCTION The main objective of the GIS INTERFACE is to enable users with a basic knowledge of GIS to create thematic maps, which will help them to analyse and evaluate the results of the Crop Growth Monitoring System (CGMS) integrated with the Soil Geographical Database of Europe (SGDBE) and CORINE/Global Land Cover (CLC/GLC) data. The GIS INTERFACE is implemented under the ESRI® ArcMap

TM 9.x

environment. The GIS INTERFACE is programmed in Visual Basic for Application (VBA) using ArcObjects libraries. All commands and tools of ArcMap remain accessible. GIS INTERFACE is designed to work with the CGMS_07 database.

REQUIREMENTS OF THE GIS INTERFACE Basic requirements of the GIS INTERFACE are based on the Tender specifications Lot I – Task 2b: Development of GIS interface CGMS-SGDBE

The GIS interface should enable to produce the advanced thematic maps on user requirements based on data from integration of CGMS and SGDBE (Lot I – Task 2 Improvement of the soil model in CGMS)

Lot I – Task 3b: GIS interface for CGMS-CORINE advanced visualisation

The GIS interface should enable to produce the advanced thematic maps based on integration of CGMS output (level 1 and 2) with CLC classes (Lot I – Task 3 CORINE Land Cover implementation)

GIS INTERFACE modules and tools are accessible through the GIS INTERFACE toolbox.

Figure 1 GIS INTERFACE toolbox

2 DATA

- 4 -


The GIS INTERFACE manages the connection between the cartographical databases (represented by vector layers) and attributes data stored in the CGMS and SGDBE databases.

2.1 VECTOR DATA All vector data are administrated using the INSPIRE LAEA-ETRS89 co-ordinate system. The following vector layers are essential for the GIS INTERFACE:

NUTS0 / NUTS2 NUTS0 / NUTS2 are layers of topological polygons, which represent administrative boundaries. NUTS0 / NUTS2 are used for selection of geographical area and for visualization of results aggregated at the required administrative level.

GRID50 This topological polygon layer contains grid cells, each covering a rectangular area of 50 x 50km. Grids are used for selection of the geographical area and for visualisation of results aggregated within the grid.

SOIL MAP This topological polygon layer is the cartographical representation of the soil database. Each polygon of the soil map belongs to one Soil Mapping Unit (SMU). One SMU can consist of one or more polygons. An SMU is the base unit in the CGMS and SGDBE databases. SOIL vector is used for geographical representation of CGMS and SGDBE attributes, which are related to a SMU or a STU.

EMUPLUS This topological polygon layer is formed by the intersection of the SOIL, GRID50 and NUTS2 vector layers. EMUplus represents the smallest modelling unit in the CGMS database.

CLC/GLCMASK These polygon layers are derived from Corine Land Cover 2000 and Global Land Cover 2000 classes. GLC2000 is used for countries where CLC data doesn’t exist. Three kinds of masks are generated for arable land, two for pastures and one for rice. Masks are used to generate maps under the CLC & Soil Suitability module.

2.2 ATTRIBUTES DATA Data from the Crop Growth Monitoring System (CGMS) and the Soil Geographical Database of Europe (SGDBE) represent source attributes data for the GIS INTERFACE.

CGMS CGMS contains data from weather monitoring, crop monitoring and yield forecasting including yield and area statistics and the final synthesis. Data are stored in the ORACLE database.

SGDBE SGDBE data used in the GIS INTERFACE contain soil information for all Europe. In the SGDBE the smallest unit with soil nature information is a Soil Typological Unit (STU). The smallest cartographic unit is a Soil

- 5 -


Mapping Unit (SMU), which is represented in SOIL MAP. An STU contains information about distinct soil type and specifies the nature and properties of the soil. It is described only by its attributes. Data are stored in a dbf table. Each SMU is composed of at least one STU. The weight of an individual STU within an SMU is given as a percentage. The sum of percentages for STU units in each SMU is 100%.

3 RUNNING THE GIS INTERFACE For the successful running of the GIS INTERFACE the following must be met:

1. The GIS INTERFACE is running from the GIS_INTERFACE_ver*.mxd file. All modules are available through the GIS INTERFACE toolbar.

2. Initialization files GIS_INTERFACE_SETUP.ini and SCHEMA.ini must be available at the same directory as the GIS_INTERFACE_ver*.mxd file.

3. Style library SSM.style must be available at the same directory as the GIS_INTERFACE_ver*.mxd file.

4. Collection of source data must be accessible. The table below gives the directory structure in which the source data must be saved. The path to the SOURCE_DATA directory is read from the GIS_INTERFACE_SETUP.ini file.

5. Connection to the ORACLE CGMS database must be set up. Connection parameters are read from the GIS_INTERFACE_SETUP.ini file.

6. the CGMS-Webserver must be running for using the Weather and Crop indicators

PERMANENT FILES

\SOURCE DATA

subdirectories files description used in module

\CGMSv81 CGMS_indic_menu.mdb

list of indicators, involved functions, parameters and symbology files

Weather Indicator, Crop Indicator

list of crops and appropriate CLC masks CLC & Soil Suitability

\CLC CLC_ARABx/PASTx/RICE.shp clc masks for arable land, pastures and rice

CLC_EUxx_ARABx/PASTx/RICE.shp

clc masks for arable land, pastures and rice prepared for EUxx group of countries

CLC & Soil Suitability

\EMU_PLUS grid50_soil_nuts_intersect.shp EMU plus vector layer Soil Suitability

\GRID50 grid50_etrs.shp GRID50 vector layer

Soil Suitability, Crop Calendar, Weather Indicator, Crop Indicator, Select Geographical Area

\LYR *.lyr symbology files

Dominant STU, Crop Calendar, Weather Indicator, Crop Indicator

\NUTS0 NUTS0.shp NUTS0 vector layer Select Geographical Area

\NUTS2 NUTS2_cgms06.shp NUTS2 vector layer Soil Suitability, Select Geographical Area

\SGDBE stu_tab.dbf SGDBE database - attribute table Dominant STU

- 6 -


\SOIL soil_etrs.shp soil map Soil Suitability, Dominant STU, CLC & Soil Suitability

\UNION CC_GRID50_EUxx.shp GRID50 vector layers prepared for EUxx

Crop Calendar, Weather Indicator, Crop Indicator

EMUplus_EUxx.shp EMU plus vector layer prepared for EUxx

EMUplus_EUxx_G50.shp EMU plus vector layer prepared for EUxx Soil Suitability

GRID_EUxx GRID50 vector layers prepared for EUxx

NUTS2_EUxx NUTS2 vector layers prepared for EUxx

SOIL_EUxx SOIL vector layers prepared for EUxx Dominant STU

UNION_EUxx UNION vector layers prepared for EUxx

Soil Suitability, Dominant STU, Crop Calendar, Weather Indic., Crop Indic., CLC & soil Suitability

UNION_EUxx_G50 UNION vector layers prepared for EUxx Soil Suitability

CGMS database ORACLE database all

TEMPORARY FILES

\WORK_DATA

FINAL MAPS

\JPG

Table 1 Data structure

Temporary and final files:

1. Temporary data are being saved in directory \WORK_DATA\. This directory is created automatically if it doesn’t exist.

2. Final maps are exported in jpeg format and are saved in \JPG\ directory. This directory is created automatically if it doesn’t exist.

3. \WORK_DATA and \JPG directories are created under directory of GIS_INTERFACE_ver*.mxd file

4 CHECKING DATA CONNECTION To check data accessibility before working with the program go to the GIS INTERFACE toolbox (Figure 1), and select the “Check Data Connection” tool. The dialog box shown in Figure 2 is displayed.

- 7 -


Figure 2 Checking Data Connection dialog box

Tools from this dialog box enable checking accessibility of vector data, connection to CGMS and SGDBE datasets, and activation of the CGMS-Webserver. Data for Weather and Crop indicators are obtained through the CGMS-Webserver. This application must be run before using the Weather or Crop Indicator modules. CGMS Webserver is the a database client which provides sending requests to Oracle CGMS database and saving the obtained datasets to the *.csv file see chapter 6.4, 6.5 and Figure 28

BASIC VECTOR LAYERS tool checks if all pivotal vector layers are connected. If all required layers are

connected, the user is informed via the message as in Figure 3 (a). If any vector layer is not available, the message shown in Figure 3 (b) indicates the missing one. It is possible to find and attach an appropriate vector layer to the project, see Figure 3 (c). In case one attaches a vector layer the mxd-file must be saved otherwise this has to be repeated during the next session.

- 8 -


(a) (b) (c)

Figure 3 Checking basic vector layers are connected

CONNECTION TO CGMS (ORACLE) tool checks the connection to ORACLE and the accessibility of all

pivotal tables, which may be used within the modules for Soil Suitability, Dominant Suitability, Crop Calendar and CLC & Soil Suitability. If everything is OK, the user is informed via the message as in Figure 4. In case of any problem with accessibility, check the GIS_INTERFACE_SETUP.ini file to see if all the parameters are set-up correctly, or contact the database administrator.

Figure 4 Checking ORACLE connection and accessibility of required tables

CONNECTION TO SGDBE (dbf) tool checks accessibility of the SGDBE table. The GIS INTERFACE

assumes that table stu_tab.dbf is stored in the \SOURCE_DATA\SGDBE\ directory. If the table is found in this directory the user is informed as in Figure 5.

- 9 -


Figure 5 Checking SGDBE (stu_tab.dbf) connection

CGMS WEBSERVER tool checks if the CGMS-Webserver is running. The CGMS-Webserver prepares

datasets for the Weather and Crop Indicators maps and must be running in advance. The user is informed whether the CGMS-Webserver is active or not as in Figure 6.

Figure 6 Checking the CGM-Webserver is active

5 GEOGRAPHICAL AREA SELECTION Before creating thematic maps, the required geographical area (GA) must be selected. GA is identified by selecting features from NUTS0, NUTS2 or GRID layers. It can be selected using the “GA selection dialog box” or the ArcGIS “select features tool”.

USING DIALOG BOX The Dialog box is accessible through the GIS INTERFACE toolbox or through any thematic map dialog box., Select the “Geographical Area Selection” tool in the GIS INTERFACE toolbox (see Figure 1) or from each thematic map dialog box. The dialog box shown in Figure 7 is displayed.

- 10 -


Figure 7 Geographical Area Selection dialog box

Select by: Select by NUTS0 – layer NUTS0 (country borders) is used to define GA. The required country can be selected from the “Select Country” list box. Multiple selections can be made by pressing Shift or Ctrl. It is also possible to select a predefined group of countries EU10, EU12, EU15, EU25, EU27, EU28 (EU27+TR) or ALL countries. Select by NUTS2 – layer NUTS2 is used to select GA. Required regions can be selected from the list box. It is also possible to select groups of regions within selected countries. Select by GRID – layer GRID50 is used to select GA. Required regions can be selected from the list box.

USING ARCGIS SELECT FEATURE TOOL Alternatively GA can be selected using a combination of the “Geographical Area Selection” dialog box and the “SelectFeature” tool. After clicking on Select by NUTS0, Select by NUTS2, or Select by GRID in the dialog box (Figure 7) the appropriate layer becomes the only selectable layer and the required features can be easily selected using the SelectFeature Tool.

- 11 -


Figure 8 Selection of GA by grid using ArcGIS Select Feature tool

PREDEFINED GROUPS OF COUNTRIES Selection of a predefined group of countries is accessible from the “Geographical Area Selection” dialog box or directly from the each thematic map dialog box Figure 9.

Figure 9 Selection of GA using predefined groups of countries

- 12 -


The GIS INTERFACE toolbox contains also the following useful tools:

SAVE SELECTION SET

Enables saving the current GA selection into text file SelectionMemory.txt

RESTORE SELECTION SET

. Enables restoring the last saved selection from text file SelectionMemory.txt

ZOOM TO SELECTED FEATURES

Zoom to Selected Features – a standard ArcGIS tool

UNLOCK FIXED SCALE

Unlock fixed scale – resets the data-frame-extent property from Fixed Scale to Automatic. The tool is useful to cancel fixed scale, which is locked after each map generation. The Save Selection Set tool and Zoom tools are not accessible if the data-frame-extent property is set to Fixed Scale

SELECT FEATURES

Select Features – a standard ArcGIS tool

CLEAR SELECTION

Clear Selection – a standard ArcGIS tool

- 13 -


6 THEMATIC MAPS The GIS INTERFACE contains the following modules for generating thematic maps: - Soil Suitability - Dominant STU - Crop Calendar - Weather Indicators - Crop Indicators - CLC & Soil Suitability

6.1 SOIL SUITABILITY MAPS The purpose of the Soil Suitability map is to present which crop can be included in the crop growth simulation for a given soil unit. CGMS contains the information related to the crop group and soil suitability stored in the SMU_SUITABILITY table. Data from this table are joined to the SOIL vector layer through an SMU_NO identifier. The SMU_SUITABILITY table contains fields SMU_NO (soil mapping unit number), CROPGROUP_NO (group which crop belongs to) and PERCENTAGE (percentage of soil mapping unit suitable for crop group). Before generating a Soil Suitability Map, the required Geographical Area must be selected.

Figure 10 Soil Suitability Map dialog box

Input parameters which are set up using the Soil Suitability Map dialog box (Figure 10): CROP GROUP THRESHOLD for suitability limit – default value is 25% AGGREGATION UNITS - default is SMU Generation of maps:

A Soil Suitability Map (SSM) is automatically generated in the following steps (see Figure 11- Figure 15):

- 14 -


Attribute data

1. Selecting all records from the SMU_SUITABILITY table which meet the selected CROP GROUP and THRESHOLD. A new SMU_SUIT_x.dbf table is created. (x = CROP GROUP number)

2. If AGGREGATION UNIT = NUTS2 or GRID, the SMU_SUIT_x table is joined with the EMUplus Selection layer. Attributes from the joined table are aggregated into required aggregation units. A new NUTS2sum.dbf table / GRIDsum.dbf table is created.

Vector data

3. Union of all features in the selected GA. A UNION.shp layer is created. 4. If the AGGREGATION UNIT NUTS2 or GRID is selected, all features from the NUTS2 / GRID layer,

which intersect the UNION layer, are selected. A new layer NUTS2 Selection / GRID Selection is created. All features from the NUTS2 Selection / GRID Selection are unioned. A new UNION.shp layer is created.

5. Selecting all features from the EMUplus layer which overlay the UNION.shp. A new layer “EMUplus Selection” is created. If AGGREGATION UNIT SMU is selected a new layer “SMU Selection” is created.

Joining Vector and Attributes data

6. If AGGREGATION UNIT NUTS2 or GRID is selected, the NUTS2sumTable / GRIDsumTable is joined with the EMUplus Selection vector layer. If AGGREGATION UNIT SMU is selected, the SMU_SUIT_x table is joined with the SMU Selection vector layer.

7. Visualization of results using color-ramp style (yellow = 5% - dark brown = 100%) Example of SSM – generated for parameters: CROP GROUP = CEREALS, THRESHOLD = 50%, AGGREGATION UNIT = GRID:

Figure 11 Selection of GA (France on NUTS2 level) / Setting input parameters for Soil Suitability Map

- 15 -


Figure 12 Union of all features in selected GA / Selection of aggregation units / Selection of all features from EMUplus layer (grid50_soil_nuts_intersect), which overlay selected aggregation units

Figure 13 SSM for AGGREGATION UNIT = GRID, CROP GROUP = CEREALS, THRESHOLD = 50%,

- 16 -


Figure 14 SSM for AGGREGATION UNIT = NUTS2, CROP GROUP = FORAGE, THRESHOLD = 5%

Figure 15 SSM for AGGREGATION UNIT = SMU, CROP GROUP = CEREALS, THRESHOLD = 20%

- 17 -


Output: The extent of the map is defined by the selected GA. Map can be exported to jpeg format by clicking the “Export to JPG” button in the Soil Suitability Maps dialog box – see Figure 10.

6.2 DOMINANT STU MAPS The purpose of Dominant STU maps is to create thematic maps for CGMS and SGDB attributes that specify the nature and properties of the soil. These attributes are related to a Soil Typological Unit (STU). Because the smallest cartographical representation in the soil database is SMU, the first step is to find the dominant STU (the STU with the highest percentage representation) for each SMU unit. Each SMU is composed of one or more Soil Typological Units. The total of the percentages for STU units in an SMU is 100%. The percentage of the dominant STU must be greater than or equal to the selected PURITY threshold value. Three types of maps can be generated within this module: Dominant Suitability for CROP GROUP, Dominant STU using attributes from CGMS and Dominant STU using attributes from SGDBE. Before generating a Dominant STU Map, the required Geographical Area must be selected.

Figure 16 Dominant STU Map dialog box

Input parameters which are set up using the Dominant STU Map dialog box (Figure 16): TYPE OF MAP - default is Dominant Suitability PURITY threshold for dominant STU - default is 5% CROP GROUP – for “Dominant Suitability - Crop Group” map STU attribute for “Dominant STU - CGMS” and “Dominant STU - SGDBE” map

- 18 -


DOMINANT SUITABILITY MAP FOR CROP GROUP Generating maps: Tables SUITABILITY (cropgroup_no;stu_no) and SOIL_ASSOCIATION_COMPOSITION (smu_no;stu_no;percentage) from CGMS are used for map creation. Dominant Suitability Map (DSM) is automatically generated in the following steps (see the Example DSM below): Attributes data:

1. Selecting all records from the SOIL_ASSOCIATION_COMPOSITION table which meet the selected PURITY threshold.

2. Summarizing all selected records (SMU_NO, Maximum.PERCENTAGE). A new SumTable.dbf is created.

3. Selecting all records from the SUITABILITY table which meet the selected CROP_GROUP. A new STU_SUIT_x table is created. (x = CROPGROUP number)

4. Joining the SOIL_ASSOCIATION_COMPOSITION table, the SumTable (join field = SMU_NO), and the STU_SUIT_x table (join field = STU_NO)

5. Selecting all records where CROPGROUP = x AND SOIL_ASSOCIATION_COMPOSITION.PERCENTAGE = SumTable.Maximum_PERCENTAGE.

6. Exporting selected records to an SAC_2.dbf table Vector data:

7. Union of all features in the selected GA. A new layer UNION.shp is created. 8. Selecting all features from the soil_etrs layer which overlay the UNION layer. A new layer SOIL

Selection is created. Joining Vector and Attributes data:

9. Joining table SAC_2 with the SOIL Selection layer. (join field = SMU_NO) 10. Visualization of results using color-ramp style (yellow = 5% - brown = 100%)

Example DSM – generation of Dominant STU Map for parameters: CROP GROUP = ROOT CROPS and THRESHOLD = 50% (Figure 17 - Figure 19)

Figure 17 GA and input parameters are selected

- 19 -


Figure 18 Union of selected GA / Selection of all features from soil_etrs layer which belongs to the UNION layer / join soil layer and SAC_2.dbf table

Figure 19 DSM for ROOT CROPS, PURITY THRESHOLD = 20%

DOMINANT STU (CGMS) The GIS INTERFACE is connected to the CGMS database. Generating maps: Tables SOIL_TYPOLOGIC_UNIT [STU_NO, soil attributes] and SOIL_ASSOCIATION_COMPOSITION [SMU_NO;STU_NO; PERCENTAGE] from CGMS are used for map creation. Thematic maps for the following soil parameters can be generated: SOIL, SLOPE1, TEXT1, PHASE1, CALCULATED_ROOTING_DEPTH, SOIL_GROUP_NO, DRAINAGE, ALKALINITY, SALINITY, SOIL_WRB, SOIL_FAO90.

- 20 -


A Dominant STU CGMS Map is automatically generated in the following steps: Attributes data:

1. Selecting all records from the SOIL_ASSOCIATION_COMPOSITION table which meet the STU PURITY threshold.

2. Summarizing all selected records (SMU_NO, Maximum.PERCENTAGE, STU_NO). A new SumTable.dbf is created. If there are two or more STU_NO with the same maximum percentage (e.g. 50, 50 or 30, 30, 30) the first STU_NO (STU with the lowest STU_NO) is selected.

3. Joining this SumTable (join field = STU_NO) with the SOIL_TYPOLOGIC_UNIT (join field = STU_NO). A new CGMS_1.dbf is created

Vector data:

4. Union of all features in the selected GA. New layer UNION.shp is created. 5. Selecting all features from the soil_etrs layer which overlay the UNION layer. A new layer “SOIL

Selection” is created. Joining Vector and Attributes data:

6. Joining table CGMS_1 with the SOIL Selection layer. (join field = SMU_NO) 7. Visualization of results using the corresponding *.lyr file with predefined symbology.

Figure 20 DSM for CGMS – PHASE1, PURITY THRESHOLD=10%

DOMINANT STU (SGDBE) The GIS INTERFACE is connected to the SGDBE database. Generating maps: STU_TAB table [STU, soil attributes] from the SGDBE and the table SOIL_ASSOCIATION_COMPOSITION [SMU_NO;STU_NO;PERCENTAGE] from CGMS are used for map creation. Thematic maps for the following soil parameters can be generated:

- 21 -


WRB_FULL, FAO90_FULL, TEXT_SRF_D, TEXT_SUB_D, PAR_MAT_DO, PAR_MAT_SE, USE_DOM, AGLIM1, AGLIM2, ROO, IL, WR, WM1, SLOPE_DOM, FAO985_FULL, ZMIN, ZMAX, USE_SEC, SLOPE_SEC, TEXT_SRF_S, TEXT_SUB_S, TEXT_DEP_C, WM2, AGLIM1NNI, AGLIM2NNI, WRB_LEV1, WRB_ADJ1, WRB_ADJ2, ALKALINITY, SALINITY, DRAINAGE, ROOTING_DEPTH, SLOPE1, TEXT1. A Dominant STU SGDBE Map is automatically generated in the following steps: Attributes data:

1. Selecting all records from the SOIL_ASSOCIATION_COMPOSITION table which meet the STU PURITY threshold.

2. Summarizing all selected records (SMU_NO, Maximum.PERCENTAGE, STU_NO). A new SumTable.dbf is created. If there are two or more STU_NO with the same maximum percentage (e.g. 50, 50 or 30, 30, 30) the first STU_NO (STU with the lowest STU_NO) is selected.

3. Joining this SumTable (join field = STU_NO) with the STU_TAB (join field = STU). A new SGDBE_1.dbf table is created.

Vector data:

4. Union of all features in the selected GA. A new layer UNION.shp is created. 5. Selecting all features from the soil_etrs layer which overlay the UNION layer. A new layer “SOIL

Selection” is created. Joining Vector and Attributes data:

6. Joining the SGDBE_1 table with the SOIL Selection layer. (join field = SMU_NO) 7. Visualization of results using the corresponding *.lyr file with predefined symbology

Figure 21 DSM for SGDBE – PAR_MAT_DO, PURITY THRESHOLD=5%

- 22 -


Figure 22 DSM for SGDBE – WRB_FULL, PURITY THRESHOLD=5%

Output: The extent of the map is defined by the selected GA. Map can be exported to jpeg format by clicking the “Export to JPG” button in the Dominant STU Map dialog box – see Figure 16.

6.3 CROP CALENDAR The CGMS Crop Calendar table describes the temporal and spatial distribution of the crops and is related to the grid system. If a crop is to be simulated for a specific grid the crop information about the crop variety, sowing and harvesting days and simulation strategies are read from the Crop Calendar table. Before generating a Crop Calendar Map, the required Geographical Area must be selected.

- 23 -


Figure 23 Crop calendar dialog box Input parameters which are set up using the Crop Calendar dialog box (Figure 23): CROP YEAR TYPE OF MAP - default is Start date Generating maps: A Crop calendar map (CCM) is automatically generated in the following steps: Attribute data

1. Selecting all records from the CROP_CALENDAR table which meet the criteria for CROP and YEAR. A new CCtable.dbf is created.

Vector data

2. Union of all features in the selected GA. A UNION.shp layer is created. 3. Selection of all features from GRID50 layer which overlay the UNION.shp. A new CROP CALENDAR

vector layer is created Joining Vector and Attributes data

4. Join this CCtable with the CROP CALENDAR vector layer. 5. Visualization of the results using the corresponding *.lyr file.

- 24 -


Figure 24 CROPCALENDAR for POTATO, START DAY, YEAR 2004

Output: The extent of the map is defined by the selected GA. Map can be exported to jpeg format by clicking the “Export to JPG” button in the Crop Calendar dialog box – see Figure 23.

6.4 WEATHER INDICATOR MAPS The purpose of the Weather Indicator Maps module is to create thematic maps based on CGMS level1 attributes. Weather attributes are related to the grid system (grid cells of 50 x 50 km). Before generating Weather Indicator Maps, CGMS-Webserver must be running (Figure 25) and the required Geographical Area must be selected.

- 25 -


Figure 25 Weather Indicators dialog box, CGMS-Webserver

Input parameters which are set up using the Weather Indicator dialog box (Figure 25): INDICATOR FUNCTION TIME PERIOD AGGREGATION DIFFERENCE TYPE THRESHOLD Thematic maps for the following indicators are generated within this module: Average daily temperature Climatic water balance Global radiation Longest heat wave period Maximum daily temperature Minimum daily temperature Number of cold days Number of days with significant rain Number of heat waves Potential evapotranspiration(ET0) Precipitation Snow depth Temperature sum Vapour pressure Wind speed

- 26 -


For each selected indicator the following functions are available: Current year Long term average (LTA) Current year – LTA Weather Indicators and functions are described in detail in “D.W.G. van Kraalingen, H.L. Boogaard, C.A. van Diepen: CGMS Viewer - User Manual and Reference Documentation, Alterra, 2007”. Generating maps: After settings all parameters, a URL string for the CGMS-Webserver is created (Figure 26) by clicking on the “createURL string” button in Weather Indicators dialog box (Figure 25). The method for creating a URL string is described in detail in “D.W.G. van Kraalingen: CGMS-Webserver – URL Interface, Alterra, 2008”.

Figure 26 A URL string generated for the CGMS-Webserver

Attribute data

1. After clicking on the “Generate data from Webserver” button, the GIS INTERFACE sends user-requirements to the CGMS-Webserver (as a URL string).

2. The CGMS Webserver is connected to the ORACLE CGMS database and the requested dataset is saved to a *.csv file. A schema for acquiring of data from the CGMS database is shown in Figure 28.

Vector data

3. Union of all features in the selected GA. A UNION.shp layer is created. 4. Selecting all features from GRID50 layer which overlay the UNION.shp A new WEATHER

INDICATOR vector layer is created Joining Vector and Attributes data

5. Joining data from the *.csv file with the WEATHER INDICATOR vector layer. The joined field is GRID_NO.

6. Visualization of results using the corresponding *.lyr file

- 27 -


Figure 27 WEATHER INDICATOR MAP. Indicator = AVERAGE DAILY TEMPERATURE, function = Current year-LTA, time period = 1.5.2002-31.5.2002, aggregation = average, difference = absolute

Output: The extent of the map is defined by the selected GA. Map can be exported to jpeg format by clicking the “Export to JPG” button in the Weather Indicator Maps dialog box – see Figure 25.

- 28 -


Figure 28 Schema of acquiring datasets for Weather and Crop Indicator modules.

6.5 CROP INDICATOR MAPS The purpose of the Crop Indicator Maps module is to create thematic maps based on CGMS level2 attributes. Crop attributes are related to the grid system (grid cells of 50 x 50 km). Before generating a Crop Indicator Maps the CGMS-Webserver must be running (Figure 29) and the required Geographical Area must be selected.

- 29 -


Figure 29 Crop Indicators dialog box, CGMS-Webserver

Input parameters which are set up using a Crop Indicator dialog box (Figure 29): INDICATOR FUNCTION SIMULATED CROP TIME PERIOD AGGREGATION DIFFERENCE TYPE Thematic maps for the following indicators are generated within this module: Development stage Potential leaf area index Potential above ground biomass Potential storage organs Relative soil moisture Total water consumption Total water requirement Water limited leaf area index Water limited above ground biomass Water limited storage organs For each selected indicator the following functions are available: Current year Long term average (LTA)

- 30 -


Current year – LTA Crop Indicators and functions are described in detail in “D.W.G. van Kraalingen, H.L. Boogaard, C.A. van Diepen: CGMS Viewer - User Manual and Reference Documentation, Alterra, 2007”. Generating maps: After settings all parameters an URL string for the CGMS-Webserver is created (Figure 26) by clicking on the “createURL string” button in the Crop Indicators dialog box (Figure 29). The method for creating the URL string is described in detail in “D.W.G. van Kraalingen: CGMS-Webserver – URL Interface, Alterra, 2008”. Attribute data

1. After clicking on the “Generate data from Webserver” button the GIS INTERFACE sends user-requirements to CGMS-Webserver (as a URL string).

2. The CGMS Webserver is connected to the ORACLE CGMS database and the requested dataset is saved to a *.csv file. A schema for acquiring data from the CGMS database is shown in Figure 28.

Vector data

3. Union of all features in the selected GA. A UNION.shp layer is created. 4. Selecting all features from GRID50 which overlay the UNION.shp. A new CROP INDICATOR vector

layer is created Joining Vector and Attributes data

5. Joining data from the *.csv file with the CROP INDICATOR vector layer. 6. Visualization of results using the corresponding *.lyr file

Figure 30 CROP INDICATOR MAP. Indicator = RELATIVE SOIL MOISTURE, function = Current year-LTA, time period = 18/2002-26/2002, aggregation = average, difference = absolute

- 31 -


Output:

The extent of the map is defined by the selected GA. Map can be exported to jpeg format by clicking the “Export to JPG” button in the Crop Indicator Maps dialog box – see Figure 29.

6.6 CLC & SOIL SUITABILITY MAPS The purpose of the CLC & Soil Suitability maps is to present which crops can be included in the crop growth simulation for a given soil unit with integration to the CLC/GLC database. Generation of a CLC & Soil Suitability map is similar to the generation of a Soil Suitability Map – Chapter 6.1.

Figure 31 CLC & Soil Suitability dialog box

Input parameters which are set up using the CLC & Soil Suitability dialog box (Figure 31): CROP/CROP GROUP THRESHOLD for suitability – default value is 25% CLC MASK

CLC MASK The CLC mask is primarily derived from CLC 2000 classes, GLC 2000 data are used for countries where a CLC 2000 dataset doesn’t exist (e.g. TR, NO, CH, ...). The CLC mask is created by vectorizing appropriate CLC/GLC classes which were originally saved in grid format. To reduce the size of vector data, the smooth function was applied - Figure 32.

- 32 -


Figure 32 CLC mask creation

Three types of masks were created for arable land, two for pastures and one for rice. These masks are defined in Table 2.

mask name

CLC classes

GLC classes CLC_GLC_JRC

ARAB1 211 116 12/116

212 13

241 19

244 22

ARAB2 211 116 12/116

ARAB3 211 116 12/116

212 13

241 19

242 20

243 21

244 22

PAST1 231 113 18/113

244 22

321 26

PAST2 231 113 18/113

244 22

321 26

242 20

243 21

RICE 213 14

Table 2 Definition of CLC masks

CROP_NO CROP_NAME arab1 arab2 arab3 past1 past2 rice

1 WINTER WHEAT x x x - - -

2 GRAIN MAIZE x x x - - -

3 SPRING BARLEY x x x - - -

5 RICE - - - - - x

6 SUGAR BEETS x x x - - -

7 POTATO x x x - - -

8 FIELD BEANS x x x - - -

9 SOY BEAN x x x - - -

10 WINTER RAPESEED x x x - - -

11 SUNFLOWER x x x - - -

- 33 -


13 WINTER BARLEY x x x - - -

14 SPRING WHEAT x x x - - -

15 SPRING RAPESEED x x x - - -

50 FORAGE PERMANENT - - - x x -

51 FORAGE TEMPORARY - - - x x -

76 SUGAR BEETS - EU25 x x x - - -

77 POTATO - EU25 x x x - - -

71 DURUM WHEAT x x x - - -

25 OATS x x x - - -

24 RYE x x x - - -

12 FODDER MAIZE - - - x x -

Table 3 Applicability of CLC masks for particular crops

CLC masks are used to improve Soil Suitability maps based solely on SOIL MAP – chapter 2.1 and 6.1. The combination of CLC MASK with SOIL MAP enables more precise specification of regions suitable for a specific crop. The following vector layers (CLC masks) are created for the purpose of generating thematic maps under the CLC & Soil Suitability module: CLC_ARAB1 (clip of SOIL MAP with ARAB1 CLC mask) CLC_ARAB2 (clip of SOIL MAP with ARAB2 CLC mask) CLC_ARAB3 (clip of SOIL MAP with ARAB3 CLC mask) CLC_PAST1 (clip of SOIL MAP with PAST1 CLC mask) CLC_PAST2 (clip of SOIL MAP with PAST2 CLC mask) CLC_RICE (clip of SOIL MAP with RICE CLC mask) Generating of maps: A CLC & Soil Suitability Map is generated in the following steps

Attribute data

1. Selecting all records from the SMU_SUITABILITY table which meet the criteria for CROP GROUP and THRESHOLD. A new SMU_SUIT_x.dbf table is created. (x = CROP GROUP number)

Vector data

2. Union of all features in the selected GA. A UNION.shp layer is created 3. Clipping the ”selected CLCmask layer” with the UNION layer

Joining Vector and Attributes data

4. Joining this SMU_SUIT_x table to the clipped layer (join field = SMU_NO). 5. Visualization of results using color-ramp style (yellow = 5% - dark brown = 100%)

- 34 -


Figure 33 SOIL SUITABILITY & CLC MAP. Crop/Crop group = WINTER WHEAT/CEREALS, CLC mask = ARAB3, THRESHOLD = 20%

- 35 -


REFERENCES

Gisat (2005): Design Report – Development of GIS interface, ASEMARS LOT I, pp. 22. Savin. I., Boogard, H., van Diepen, C., Negre, T. (2004): CGMS version 8.0 User Manual and Technical Documentation, Ispra, Italy, pp. 128. Micale, F., Genovese, G. (2004): Methodology of the mars crop yield forecasting system, vol.1, Meteorological data collection, processing and analysis, Office for Official Publication of thr European Communities, ISBN 92-894-8180-3, pp. 100. Lazar, C., Genovese, G. (2004): Methodology of the mars crop yield forecasting system, vol.2, Agrometeorological data collection, processing and analysis, Office for Official Publication of thr European Communities, ISBN 92-894-8181-1, pp. 98. Royer, A., Genovese, G. (2004): Methodology of the mars crop yield forecasting system, vol.3, Remote sensing information, data processing and analysis, Office for Official Publication of the European Communities, ISBN 92-894-8182-X, pp. 75. Redesign Map Production Line (MPL), Alterra D.W.G. van Kraalingen, H.L. Boogaard, C.A. van Diepen: CGMS Viewer - User Manual and Reference Documentation, Alterra, 2007 D.W.G. van Kraalingen: CGMS-Webserver – URL Interface, Alterra, 2008

- 36 -


LIST OF FIGURES Figure 1 GIS INTERFACE toolbox ..................................................................................................................... 3 Figure 2 Checking Data Connection dialog box ................................................................................................. 7 Figure 3 Checking basic vector layers are connected ....................................................................................... 8 Figure 4 Checking ORACLE connection and accessibility of required tables ................................................... 8 Figure 5 Checking SGDBE (stu_tab.dbf) connection ......................................................................................... 9 Figure 6 Checking the CGM-Webserver is active .............................................................................................. 9 Figure 7 Geographical Area Selection dialog box ............................................................................................ 10 Figure 8 Selection of GA by grid using ArcGIS Select Feature tool ................................................................. 11 Figure 9 Selection of GA using predefined groups of countries ....................................................................... 11 Figure 10 Soil Suitability Map dialog box.......................................................................................................... 13 Figure 11 Selection of GA (France on NUTS2 level) / Setting input parameters for Soil Suitability Map ....... 14 Figure 12 Union of all features in selected GA / Selection of aggregation units / Selection of all features

from EMUplus layer (grid50_soil_nuts_intersect), which overlay selected aggregation units ................. 15 Figure 13 SSM for AGGREGATION UNIT = GRID, CROP GROUP = CEREALS, THRESHOLD = 50%, ..... 15 Figure 14 SSM for AGGREGATION UNIT = NUTS2, CROP GROUP = FORAGE, THRESHOLD = 5% ...... 16 Figure 15 SSM for AGGREGATION UNIT = SMU, CROP GROUP = CEREALS, THRESHOLD = 20% ..... 16 Figure 16 Dominant STU Map dialog box ....................................................................................................... 17 Figure 17 GA and input parameters are selected ........................................................................................... 18 Figure 18 Union of selected GA / Selection of all features from soil_etrs layer which belongs to the UNION

layer / join soil layer and SAC_2.dbf table ............................................................................................. 19 Figure 19 DSM for ROOT CROPS, PURITY THRESHOLD = 20% ................................................................. 19 Figure 20 DSM for CGMS – PHASE1, PURITY THRESHOLD=10% .............................................................. 20 Figure 21 DSM for SGDBE – PAR_MAT_DO, PURITY THRESHOLD=5% .................................................... 21 Figure 22 DSM for SGDBE – WRB_FULL, PURITY THRESHOLD=5% ......................................................... 22 Figure 23 Crop calendar dialog box ................................................................................................................ 23 Figure 24 CROPCALENDAR for POTATO, START DAY, YEAR 2004 ........................................................... 24 Figure 25 Weather Indicators dialog box, CGMS-Webserver .......................................................................... 25 Figure 26 A URL string generated for the CGMS-Webserver .......................................................................... 26 Figure 27 WEATHER INDICATOR MAP. Indicator = AVERAGE DAILY TEMPERATURE, function = Current

year-LTA, time period = 1.5.2002-31.5.2002, aggregation = average, difference = absolute ................. 27 Figure 28 Schema of acquiring datasets for Weather and Crop Indicator modules. ....................................... 28 Figure 29 Crop Indicators dialog box, CGMS-Webserver ................................................................................ 29 Figure 30 CROP INDICATOR MAP. Indicator = RELATIVE SOIL MOISTURE, function = Current year-LTA,

time period = 18/2002-26/2002, aggregation = average, difference = absolute ...................................... 30 Figure 31 CLC & Soil Suitability dialog box ...................................................................................................... 31 Figure 32 CLC mask creation ........................................................................................................................... 32 Figure 33 SOIL SUITABILITY & CLC MAP. Crop/Crop group = WINTER WHEAT/CEREALS, CLC mask =

ARAB3, THRESHOLD = 20% .................................................................................................................. 34

LIST OF TABLES Table 1 Data structure ........................................................................................................................................ 6 Table 2 Definition of CLC masks ...................................................................................................................... 32 Table 3 Applicability of CLC masks for particular crops ................................................................................... 33

Date post:	20-Jun-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

ASEMARS - Europa...ASEMARS LOT I Task 2b: Development of GIS interface CGMS-SGDBE Task 3b:...

Documents