wAnHabit: Habitats analysis

wAnHabit is a MiraMon module that allows analyzing layers of habitats in a biogeographic region and determines the representation level (in percentage) of a selection of those habitats on a set of interest areas differentiated by a code (interest areas). It is an application developed to ease the completion of the reports that Govern de Catalunya develops periodically for the Spanish Government and the European Commission, but it has been programmed on a flexible way for, through a configuration file (AnHabConfig.ini), develop a similar analysis in other places in Europe or worldwide.

Input data and module configuration

In the configuration directory of the module, the file AnHabConfig.ini must appear.
This is an INI type file that allows, through the definition of sections and keys, configuring each of the parameters the program needs to function and that are described in this document. The reference of each element will be done by its section and key: "[SECCIO]Clau". Remember that, on an INI file, the order of the sections is irrelevant and also the order of the keys inside a section. Remember too that the lines started with a semicolon (;) are comments that the program ignores. An example appears in brackets to ease the comprehension of the help applying it to a concrete case.

The final result of the analysis is generated in two tables:

• [RESULTATS]Fitxer1 (h_atr.dbf): It contains the surface (in ha) of the habitat/s that want/s to be analyzed on the specified biogeographic region.
• [RESULTATS]Fitxer2 (e_h_atr.dbf): It contains the surface (in ha) and the representation level of the habitat/s in the region by a unique code, and thus per 100, of the layer to analyze.

All the "layer" files which are referenced in this document are "polygon" type and can be expressed either in MiraMon structured files (POL) or in REL files that target to layers of an Oracle SDO server (to which it is accessed via ODBC drivers installed on Windows) of polygon type or polygon groups (named multi-polygons in SDO). The names of the files are relative to a reference directory (or working space) that can be chosen from a window of the program.

The parameters that can be chosen in the interface are:

• Overwrite output tables: This option allows, either overwriting the existing result tables or adding the results of the analysis to the pre-existing tables. By default, this option is selected in order that the tables are overwritten or created if they did not exist previously.
• Erase intermediate layers and tables: This option allows, either erasing, at the end of the procedure, all the layers and tables created during the analysis (excepting the tables with the results), or keeping them. By default, this option is selected in order to erase them.
• Habitat types: Dropdown with the habitat types that wants to be analyzed, that are read from the file AnHabConfig.ini, where they appear following the scheme: [TIPUS_HABITATS] HAB1, HAB2,... (for example HAB1=HIC in the case of habitats of community interest, HAB2=HC in the case of habitats in Catalonia, etc). Each habitat appearing on the previous list has its own corresponding section in the file AnHabConfig.ini itself. Following the previous example, we will find the section [TIPUS_HABITATS:HIC] that describes other things that are going to be treated later in this document related to habitats of community interest, [TIPUS_HABITATS:HC] that describes other things that are going to be seen later in this document related to habitats in Catalonia, etc.
• Biogeographic region: Dropdown with the values of the biogeographic region for which an analysis has to be made, that are read from the AnHabConfig.ini file. The section [REGIO_BIOGEOGRAFICA] contains the keys Fitxer, REGIO1, REGIO2, REGIO3, ... that determine the file containing several regions (for example, alpine, mediterranean, or whole of Catalonia) that can be submitted into an analysis (that will be restricted to the desired region). Each habitat has its own section REGIO_BIOGEOGRAFICA:VALOR_REGIO] that describes other things of the region that will be seen further in this document, where VALOR_REGIOwill take the values written on the keys REGIO1, REGIO2, etc, just mentioned.
• Reference directory (working area): Directory where the layer with the biogeographic regions, the layer to analyze and the file containing the list of habitats to analyze (for example habitats.txt, name stated on the key NomFitxerSeleccio of the corresponding section to the habitats of interest typology (for example the HIC) from the file AnHabConfig.ini) are placed. It also is the directory where the tables with the results of the analysis are generated.

Provided that the procedure works correctly, it is essential that these mentioned files have the following features, some of which are configurable (so it is stated on each case):

• Biogeographic regions layer: On the section [REGIO_BIOGEOGRAFICA] the file containing the biogeographic regions of interest could be stated and as many keys as region types want to be analyzed. Each key results into a section [REGIO_BIOGEOGRAFICA:VALOR_REGIO] where its keys are, in one hand, Nom and Descripció and, in the other hand, a bundle of three keys that allow determining the desired biogeographic region:

  Nom: Key the value of which it acts as an identifier of this region. For example "Alpine".

  Descripció: Key the value where the dropdown appears allowing a more detailed description (more human if needed) or even in another language. For example, "Alpine Region".

  COND1_CAMP, COND1_OP and COND1_VALOR: Keys allowing to define the condition the region type has to fulfill. For example, if the previous triplet takes, respectively, the values CODI_REGIO, EQ, alp, the module will interpret that the alpine region is defined by those polygons that fulfill the condition that the field CODI_REGIO is the same (EQ) as “alp”.

• Layer to analyze: On the section [COBERTURA_ANALISI] the file containing the layers to analyze can be stated. Each layer has a code on which the level of representation on surface is calculated. There are three keys to fill:

  Fitxer: Name of the file containing the layers to analyze.

  Camp: Name of the file allowing to distinguish between types of areas to analyze; in this field, the areas might be a literal descriptor, a code (for example, ES5130029), etc.

  ValorAExcloure: Value of the previous field that indicates the program that that one record (polygon) will be excluded from the analysis. It is, in fact, a tag equivalent to a no-data.

• Hàbitats: The habitats are configured in the section [TIPUS_HABITATS]. The keys HAB1, HAB2, ... determine the different habitats that want to be analyzed appearing on the dropdown on the program interface. Examples: habitats in Catalonia, habitats of Community Interest,...

  For each habitat the following keys must be stated:

  Nom: Identifier given to the habitat type.

  Descripció: Textual description appearing on the dropdown of the application interface.

  Fitxer: Name of the file containing the habitats layer to analyze. Remember that, as it has been said, it could be a vector file of "polygon" type in the format of MiraMon or a REL pointing to a SDO layer.

  NomFitxerSeleccio: name of the file (related to the reference directory) that contains all the habitat codes that want to be taken into account. Each line of the file must have a code. If there are some empty lines, those are ignored. Examples of name: Arxiu HIC.txt, Arxiu HC.txt

  CampAreaOri: Numerical field containing the area calculation on which the area proportions calculations want to be done: it is useful if we want to use a calculation on special units, etc. If this key does not appear, the field "AREA" of MiraMon will be used, that uses unities of the Reference System, typically on squared meters (or squared degrees on layers in longitude/latitude).

  FactorHa: Since area results are given in hectares, this key allows us to specify the number among which the area value has to be divided to obtain the hectares. For example, if it has the area on squared meters, this factor has to be 10000.

  CampSeleccio1, CampSeleccio2, ...: Considering that on the same polygon there may be more than one habitat, with these keys the possibility of several names of fields is enabled in order that each field contains the habitat code (and its covering inside the polygon, specified below).

  CampRecobriment1, CampRecobriment2, ...: Numerical value stating the covering of the habitat in the polygon. This value has been calculated previously by the user so it is written in this field or fields of the input layer.

  IndexRecobriment: Value on which the values of CampRecobriment are expressed. For example, on one area there may be pinewood of white pine mixed with pinewood of stone pine. An observation may have determined that there is a 50% of each. In that case, it is going to be considered a 50% of covering of each species. Two fields would be filled in, with a 5 of covering in each of both, and IndexRecobriment ought to value 10. Note that is possible that IndexRecobriment would be bigger than the sum of the different values CampRecobriment if we consider that there are non-contemplated cases but they occupy the missing proportion.

  If a third habitat appeared, three fields with coverings will be filled summing a maximum of 10.

All the intermediate calculations can be consulted in some temporary files that are stated on the section [TEMPORALS]:

• Directori1: States the directory where the layers created during the analysis are saved.
• Directori2: States the intermedium directory used by MiraMon during the calculations. If the key does not exist, it would be a directory named "TEMPMM" on the reference directory.

The steps taken during the process will be registered on a file of "txt" type that can be configured in the section [PROCEDIMENT] in the key Fitxer1.

Example of module use

Suppose that an analysis of the habitats of Catalonia and habitats of Community Interest in the mediterranean and alpine biogeographic areas is wanted and, on the other hand, in all Catalonia.

In order to do that, a folder named reference directory and a SDO server are enabled. This is available:

• In the SDO server, there is a layer with the biogeographic regions and in the reference directory, there is a REL of MiraMon that points to this layer (regions_bio3_etrs89.rel). The field that determines the regions is CODI_REGIO and has the value "alp" when it is alpine and "med" when it is mediterranean. Another field CODI_REG has been enabled that determines "all Catalonia" when it values "all".
• In the SDO server, there is a layer with the habitats of community interest and in the reference directory, there is a REL of MiraMon that points to this layer (CAT_CHIC2012V2ARD.rel). The fields that determine the presence of one habitat in a region are “HICi” with a covering expressed in the field “RHICi” for i from 1 to 10. The covering is over 10. There is not a specific field for the area. MiraMon expresses the areas in square meters or in square degrees for cartographic reference systems.
• In the reference directory there is a file of text type with the list of habitats to be analyzed: Habitats_HIC.txt. The codes are the ones that appear in some of the "HICi" fields.
• In the SDO server, there is a layer of habitats in Catalonia and in the reference directory, there is a REL of MiraMon that points to this layer (CAT_CHC2012V2ATR.rel). The fields that determine the presence of one habitat in a region are "Hi" with a covering expressed in the field "REC10_Hi" for i from 1 to 3. The covering is over 10. There is not a specific field for the area.
• In the reference directory, there is a file of text type with the list of habitats to be analyzed: Habitats_HC.txt. The codes are the ones that appear in any of the "Hi" fields.
• In the SDO server, there is a layer of the interest areas on which we want to know the level of representation of each habitat and in the reference directory, there is a REL of MiraMon that points to this layer (Arees_etrs89.rel). The field with the region code is CODI_A, which has value ES-EXCLOS to be excluded in the analysis.

The results are placed on the same reference directory and moreover it is wanted:

• A file named "procediment.txt" with a register of all that has been done.
• The result of the area that a habitat occupies inside the biogeographic region in the file named "h_atr.dbf".
• The result of the area that the habitat occupies inside each one of the interest areas and its level of representation according to its area in the biogeographic region, in percentage and with two decimal figures (areas and level of representation).
• Place all the intermediate files in a directory named "taules_intermedies" inside the reference directory

To configure all this it is required to have all the files in the reference directory specified in the interface and the file AnHabitConfig in the folder of the reference directory.

The file AnHabitConfig.ini that reflect the specifications described until now is:

[REGIO_BIOGEOGRAFICA]
Fitxer=regions_bio3_etrs89.rel
REGIO1=ALPINE
REGIO2=MEDITERRANEAN
REGIO3=CATALONIA

[REGIO_BIOGEOGRAFICA:ALPINA]
Nom=Alpine
Descripcio=Alpine region
COND1_CAMP=CODI_REGIO
COND1_OP=EQ
COND1_VALOR=alp

[REGIO_BIOGEOGRAFICA:MEDITERRANIA]
Nom=Mediterranean
Descripcio=Mediterranean region
COND1_CAMP=CODI_REGIO
COND1_OP=EQ
COND1_VALOR=med

[REGIO_BIOGEOGRAFICA:CATALUNYA]
Nom=Catalonia
Descripcio=Region for whole Catalonia
COND1_CAMP=CODI_REG_1
COND1_OP=EQ
COND1_VALOR=all

[TIPUS_HABITATS]
HAB1=HIC
HAB2=HC

[TIPUS_HABITATS:HIC]
Nom=HIC
Descripcio=Habitats of community interest
Fitxer=CAT_CHIC2012V2ATR.rel
NomFitxerSeleccio=Habitats_HIC.txt
FactorHa=10000
CampSeleccio1=HIC1
CampSeleccio2=HIC2
CampSeleccio3=HIC3
CampSeleccio4=HIC4
CampSeleccio5=HIC5
CampSeleccio6=HIC6
CampSeleccio7=HIC7
CampSeleccio8=HIC8
CampSeleccio9=HIC9
CampSeleccio10=HIC10
IndexRecobriment=10
CampRecobriment1=RHIC1
CampRecobriment2=RHIC2
CampRecobriment3=RHIC3
CampRecobriment4=RHIC4
CampRecobriment5=RHIC5
CampRecobriment6=RHIC6
CampRecobriment7=RHIC7
CampRecobriment8=RHIC8
CampRecobriment9=RHIC9
CampRecobriment10=RHIC10

[TIPUS_HABITATS:HC]
Nom=HC
Descripcio=Habitats of Catalonia
Fitxer=CAT_CHC2012V2ATR.rel
NomFitxerSeleccio=Habitats_HC.txt
FactorHa=10000
CampSeleccio1=H1
CampSeleccio2=H2
CampSeleccio3=H3
IndexRecobriment=10
CampRecobriment1=REC10_H1
CampRecobriment2=REC10_H2
CampRecobriment3=REC10_H3

[COBERTURA_ANALISI]
Fitxer=Arees_etrs89.rel
Camp=CODI_A
ValorAExcloure=ES-EXCLOS

[PROCEDIMENT]
Fitxer1=procediment.txt

[RESULTATS]
Fitxer1=h_atr.dbf
Fitxer2=e_h_atr.dbf
DecimalsDeSortida=2

[TEMPORALS]
Directori1=taules_intermedies
Directori2=TEMPMM

Example of procedure

The level of representation of the community interest habitat in the alpine biogeographic region is wanted to be analyzed for the areas determined on the file Arees_etrs89.rel. The results tables are created from scratch. In this example, pay attention only to the habitat code 9530.

The code conducts a series of processes, that can be seen in the final image and that, in short, they consist of:

• Generate a polygon file with the chosen biogeographic region (bluish color with horizontal slices partially covered).
• Generate a polygon file that contains the polygons that have some representation of the habitat 9530 (polygons on white and without slices and polygons in orange/red tones with vertical and diagonal slices, respectively).
• Develop the geometrical intersection of the biogeographic region with the polygons of the habitat, only conserving the part they match with two features (polygons of orange/red tones with vertical and diagonal slices respectively).
• Check if the habitat is present on the biogeographic region. If not, it is added to the table h_atr.dbf one record for this habitat with value -1 for SUP_H (surface of the habitat on the biogeographic region) and the analysis is over. It is not the case.
• Add to the intersection layer the field SUP_H where the surface of the habitat in the biogeographic region will be calculated, and the field HIC to obtain the habitat code hic.
• Calculate the added fields SUP_H and HC/HIC and add a record to the resulting table h_art.dbf.
• Carry out the geometrical intersection of the layer to analyze (Arees:etrs89.rel) with the vector of the habitat in the region, only conserving the part where they coincide with two features (red polygons with diagonal slices)
• Check if the habitat of the biogeographic region is also present in the layer to analyze.
• If the habitat is not present, stop the analysis of the layer to analyze: add to the table h_atr.dbf the records of the table with the results of the analysis by the habitat. e_h_art.dbf does not receive any record by this habitat. Exit from the procedure by this habitat.
• If the habitat is present on the layer to analyze, create and calculate the field AREA_H with the surface of each polygon to the resulting layer of the intersection.
• Recalculate the field SUP_H according to the part of the occupied area compared to the previous (polygons colored in orange of vertical slices).
• Erase from the resulting table the records with area code ‘ES-EXCLOS’ (for the case of XarxaNatura 2000).
• Create and calculate the representation level on the resulting table (area on red/area on orange+red)*100.
• Add to the table e_h_atr.dbf the records of the tables with the results of the analysis by habitat for each code.
• Erase the layers and tables generated during the process if the user has stated it.

Considerations:

To differentiate the case of one habitat present in the biogeographic region with zero covering in all its locations and the case of a habitat that does not even appear on the region, the first case receives, as a surface on the table h_atr.dbf, a zero value, while the last case receives a value -1. This way while making the analysis the procedure returns a result besides it does not appear in the region.

Otherwise, if one habitat present in the biogeographic region does not appear on the layer to analyze, this habitat will not appear in the table e_h_art.dbf.