European Environment Agency

European Topic Centre on Biological Diversity

Work Programme 2005

Work Package 1.4.2: Maintaining and quality assuring EEA priority data flows

Common Data Base on Designated Areas

At National Level

Report on the analysis process for National Data Base of Latvia

Lauri Klein and Tiina Dislis

EEIC

(Estonia)

February 2006

  1. Main aims and tasks

Since 2001 annual validation procedures have been performed for updated national datasets of CDDA as given in table below:

Procedure / Reason
Checking completeness of data in all tables / Many gaps are affecting data analysis and annual indicator production
Checking if there exist any change in field properties of all tables / If field properties are changed it may affect data merging as well as it refers to possibility that dataset prepared has not been used for updating
Search for changes in designation type / designation name in designations table / In case of type it should be also marked in to be deleted field or it can just be possible error
Search for new designations added into designations table / To keep record for statistical purpose
Checking difference in total area of sites per designation as taken from designations and sites tables / There should not exist difference, if there is it is error
Search for designations marked to be deleted in designations table / To keep record for statistical purpose and to delete them from master base
Search for designations deleted without marking them to be deleted in designations table / Designations should not be deleted before marking them to be deleted, that is error
Search for designations with duplicated designation code in designations table / Designation code should be unique and any duplication is error
Search for records with deleted site code, but not marked for deletion in sites table / Records should not be deleted before marking them to be deleted as they have unique site code
Search for sites with duplicated site code in sites table / Site code should be unique and any duplication is error
Search for newly entered sites without site code in sites table / Those records need site code to be added by CDDA administrators
Search for sites with missing national site code in sites table / As site code and national site code are key fields for sites table it is very important that there exists national site code for all records
Search for sites with duplicated national site code in sites table / National site code as key field should be unique and any duplication is error
Search for any change in national site code in sites table / All changes in key field may affect master base in merging, so they should be recorded
Search for records with missing ISO code in sites table / Simply question of completeness of both ISO3 and Parent ISO fields
Search for records with incorrect ISO code in sites table / Quality assurance for further analysis
Search for changes in site designation in sites table / If site designation has changed it is recorded in database as new site and also establishment year should be changed, also for recheck by country if the change is real and not error
Search for sites with missing designation in sites table / All sites should have a designation, if it is missing it is an error
Search for changes in site name in sites table / Just recording for statistics, but also if national site code is missing site name is next possible unique field for setting relations for analysis
Search for sites with duplicated name in sites table / Look previous, also feedback to country for rechecking if double names are real or mistake
Search for sites with missing name in sites table / If national site code is missing site name is next possible unique field for setting relations for analysis, also usually any site has name so it is for country to re-check if there is an error
Search for changes in site size in sites table / If site size is changed it refers to change in boundaries that should be checked accordingly
Search for sites with missing size in sites table / Any site if it exists should have a size, if it is missing it is an error (completeness of data)
Search for sites with missing NUTS code in sites table / Administrative NUTS code is important for EUROSTAT
Search for changes in IUCN category in sites table / If IUCN category is changed it may refer to change in designation and if it is not a case it may be error
Search for sites with missing IUCN category in sites table / IUCN category is very needed for statistical purposes (completeness of data)
Search for change in site year in sites table / Reason for changing establishment year may only be change in designation or mistake in previous database version
Search for sites with missing year in sites table / Checking the reason of missing data for establishment year, that is needed for statistical purposes (completeness of data)
Search for sites with missing altitude in sites table / Completeness of data and need for indicating habitat related information
Search for changes in coordinates in sites table / Change in coordinates may refer to change in site boundary and/or size, to be checked accordingly
Search sites with duplicated coordinates in sites table / Duplication, if is not error only refers to overlapping or coinciding, to be checked accordingly
Search for sites with missing coordinates in sites table / When boundary data is not available coordinates are only ones giving possibility to locate the site
Search for sites marked to be deleted in sites table / To keep record for statistical purpose and to delete them from master base
Search for records that have site codes from column SITECODE in table site relations with no reference to SITECODE column in table sites / Any result of that search refers to deletion of site from sites table, but leaving it still into site relations table, that is an error
Search for neighboring sites in site relations table / To be checked in accordance with boundary data
Search for sites containing other sites in site relations table / To be checked in accordance with boundary data
Search for sites overlapped by other sites in site relations table / To be checked in accordance with boundary data
Search for records from site habitats table having no reference in sites table / Any result of that search refers to deletion of site from sites table or just error
Search for records from sites table having no reference in site habitats table / Find out gaps in habitat data
Search for records from site habitats table with no reference in EUNIS habitats table / All habitat codes should come from EUNIS habitats table any other code is error
Search for sites from site habitats table with habitats coverage not 100% / Habitat coverage should always be 100% otherwise it is an error or a gap
Express number of habitats indicated per sites in site habitats table and total area of those sites / Statistics to show habitat diversity of sites given per size
  • The aim of digital boundaries database checking was to determine are the delivered files from different countries comparable and whether the data can be merged into a consistent database (to create seamless pan-European boundary files). For that purpose, data were checked for map projections because merging different spatial databases into one spatial database needs information in which coordinate system data are stored. The data has also been checked for main geometrical errors (are polygons closed etc)
  • Secondly boundary files were compared with CDDA database to find out whether all designated sites in CDDA database have reference features in boundary files. For the purpose of connecting digital boundary files with CDDA database, it was checked if the CDDA SITE_CODE or relevant field for CDDA is present in the boundary file attribute table.
  • Preliminary comparison of main statistics (number and total area of sites) for designated areas present in the CDDA database and those present in the digital boundaries files delivered by countries was done. For that purpose areas were calculated for boundary files using ArcInfo software. Simple MS-Access and ArcInfo queries were used to create necessary statistics. Unique CDDA site code or, in case it was missing in boundary files, national site code was used for the relation between CDDA and boundary file tables. Only in case both unique codes were missing, name was used.
  • Delivered GIS data (boundary files) were also checked on the basis of EEA’s Guide to geographical data and maps to find out whether and to what extent files are in accordance with this guide.
  1. Conclusions and recommendations
  • Database is very well compiled both in content and also technically. I propose it to get highest rank on technical point of view.

Some recommendations still for next years update:

  • If you make change or correction of error into any record of both designations and sites tables that might need explanation why did you do that change, please indicate it either in Remark field of table designations or Notes field of table sites.
  • Please complete size field of sites table.
  • Please complete overlap field of siterelations table.
  • Check that habitats coverage is not different of 100% per site.
  • If you need to show siterelations or sitehabitats for those sites that do not yet have SITE_CODE, please could you contact me by e-mail () and I will deliver needed sitecodes. If you prefer to use SITE_CODE_NAT could you give them as separate table?

Results for digital boundary analysis

  • At first, thank you for deliveries! All delivered files were generally correct.
  • Boundary files were linked to CDDA database using national site code because CDDA site code was missing.
  • All designated sites in CDDA database have reference feature in boundary files.
  • Boundary files include features for category A designation types. See table Comparative analysis of designations in boundary files and in CDDA

Main gaps for digital boundaries

  • More than one boundary file have sites with same designation type. For example sites with designation type LV04 are presented in boundary files nat_mon_point_obj and nat_monum.
  • CDDA site code is missing.
  • Projection description is missing.

Mistakes or possible mistakes for digital boundaries

  • Values in field site_code are not CDDA site codes, but national site codes. This is misleading. Field site_code should be renamed site_code_nat

Suggestions for digital boundaries

  • It might be easier to analyse and work with designated areas if different designations were stored as different layers or at least it should be checked that relevant id-field for separation of different designations into different layers is present.
  • Projection description is needed to deliver with boundary files.
  • To avoid any errors in matching boundaries and CDDA data unique CDDA site code field should be present in both data-tables.
  • To make data from different countries comparable and analysable (e.g. to give result that would serve one of EEA headline indicator – total are designated per country) EEA Guide to geographical data and maps should be followed
  1. Main statistics

Table / Number of records in old set / Number of records in new set
Designations-LV / 8 / 10
Sites-LV / 633 / 656
Siterelations-LV / 435 / 432
Sitehabitats-LV / 1873 / 2421

3.1Field completeness

  • Designations-LV

Column / Records filled in old / Records filled in new / Completeness %
ISO3 / 8 / 10 / 100
DESIG_ABBR / 8 / 10 / 100
Category / 8 / 8 / 100
ODESIGNATE / 8 / 10 / 100
DESIGNATE / 8 / 10 / 100
Title – French / 3 / 5 / 50
CDDA sites / 8 / 10 / 100
Law / 8 / 8 / 100
Lawreference / 8 / 8 / 100
Agency / 8 / 8 / 100
Number / 7 / 7 / 90
Total Area / 7 / 7 / 90
Number reference / 7 / 7 / 90
Total Area reference / 7 / 7 / 90
Data Source / 7 / 8 / 100
Reference date / 7 / 8 / 100
Remark / 1 / 0 / 0
Remark source / 0 / 0 / 0
To be deleted / 8 / 10 / 100
  • Sites-LV

Column / Records filled in old / Records filled in new / Completeness %
SITE_CODE / 633 / 633 / 100
SITE_CODE_NAT / 633 / 656 / 100
PARENT_ISO / 633 / 656 / 100
ISO3 / 633 / 656 / 100
DESIG_ABBR / 633 / 656 / 100
AREANAME / 633 / 656 / 100
SIZE / 598 / 621 / 95
NUTS / 0 / 656 / 100
IUCNCAT / 633 / 656 / 100
YEAR / 633 / 656 / 100
ALTITUDE_MIN / 598 / 656 / 100
ALTITUDE_MAX / 598 / 656 / 100
LAT_NS / 633 / 656 / 100
LATDEG / 633 / 656 / 100
LATMIN / 633 / 656 / 100
LATSEC / 633 / 656 / 100
LON_EW / 633 / 656 / 100
LONDEG / 633 / 656 / 100
LONMIN / 633 / 656 / 100
LONSEC / 633 / 656 / 100
LAT / 633 / 656 / 100
LON / 633 / 656 / 100
EIONET CHNG_DATE / 633 / 656 / 100
EIONET CHNG_TYPE / 633 / 656 / 100
EIONET EDITED_BY / 633 / 656 / 100
EIONET INSTITUTE / 633 / 656 / 100
Remark / 0 / 4 / 1
To be deleted / 633 / 656 / 100
  • Siterelations-LV

Column / Records filled in old / Records filled in new / Completeness %
SITECODE / 435 / 432 / 100
RSITECODE / 435 / 432 / 100
REL_CODE / 435 / 432 / 100
OVERLAP / 370 / 424 / 98
  • Sitehabitats-LV

Column / Records filled in old / Records filled in new / Completeness %
SITE_CODE / 1873 / 2421 / 100
EUNIS Hab / 1871 / 2421 / 100
Cover / 1871 / 2421 / 100
  1. GIS data delivery

File name: nat_mon_point_obj

Format / SHP
Feature type / Point
Number of features / 35
CDDA site code / No (values in field site_code are not CDDA site codes, but national site codes)
Designation reference / No
Possibility to link with CDDA database / Linking is possible using national site code.
Projection / Projected coordinate system
Projection description, incl datum / No
Original scale / Unknown
Geometric quality
Remarks / Designation type LV04

File name: nat_monum

Format / SHP
Feature type / Polygon
Number of features / 260
CDDA site code / No (values in field site_code are not CDDA site codes, but national site codes)
Designation reference / No
Possibility to link with CDDA database / Linking is possible using national site code.
Projection / Projected coordinate system
Projection description, incl datum / No
Original scale / Unknown
Geometric quality / Polygons are closed
Remarks / Designation type LV04

File name: nat_teritories

Format / SHP
Feature type / Polygon
Number of features / 361
CDDA site code / No (values in field site_code are not CDDA site codes, but national site codes)
Designation reference / No
Possibility to link with CDDA database / Linking is possible using national site code.
Projection / Projected coordinate system
Projection description, incl datum / No
Original scale / Unknown
Geometric quality / Polygons are closed
Remarks / Designation types LV01, LV02, LV03, LV05, LV06, LV07, LV08
  1. Analysis of data

Comparative analysis of designations in boundary files (sites with reference to designation type) and in CDDA files

Designation name / Designation code / Number of sites in database / Total area of sites in database, ha / Number of sites in boundary files / Total area of sites in boundary files, ha
Strict Nature Reserve / LV01 / 4 / 24439 / 4 / 24439
National Park / LV02 / 3 / 146520 / 3 / 146520
Nature Park / LV03 / 43 / 248898 / 43 / 248967
Nature Monument / LV04 / 295 / 5191 / 295 / 5209
Nature Reserve / LV05 / 278 / 197255 / 278 / 197203
Protected Landscape Area / LV06 / 9 / 161692 / 9 / 161692
Biosphere Reserve / LV07 / 1 / 474447 / 1 / 475502
Micro-reserve / LV08 / 23 / 987 / 23 / 984
Total
/ 656 / 1259429 / 656 / 1260516

5.1Table “designations-LV”

  • Overall comments for columns:

Column / Comments
ISO3 / Filled correctly
DESIG_ABBR / Filled correctly
Category / Filled correctly
ODESIGNATE / Filled correctly
DESIGNATE / Filled correctly
Title – French / Filled correctly. Translation of 5 designation name into French should be done by administrators of CDDA.
CDDA sites / Filled correctly. 1 record have changed entry, but no explanation in Remark field, please not is it correction of error or any other reason.
Law / Filled correctly. Could you also consider adding number of article pointing to particular designations?
Lawreference / Filled correctly
Agency / Filled correctly
Number / Technically correctly filled, but these fields should be filled only when data (number and total area) that is different of current CDDA delivery has been published in between last and current CDDA data delivery. Hereby numbers are same that means there is no need to fill those fields.NB! Same comment was present already last year!
Total Area
Number reference
Total Area reference
Data Source
Reference date
Remark / Filled correctly
Remark source / Field is empty. Look comment on CDDA sites above.
To be deleted / Filled correctly
  • New designations:No such case
  • Change in designation name:No such case
  • Change in designation code:No such case
  • Change in CDDA sites:1 record

Designation code / Designation name / Old entry in CDDA sites field / New entry in CDDA sites field
LV08 / Micro-reserve / 0 / -1
  • Number and total area of sites per designation in last year and in current update:

Designation code / Designation name currently / Number last year / Number currently / Total area currently, ha / Total area last year, ha
LV01 / Strict Nature Reserve / 4 / 4 / 24439 / 24439
LV02 / National Park / 3 / 3 / 146520 / 146520
LV03 / Nature Park / 43 / 43 / 248898 / 248232
LV04 / Nature Monument / 295 / 295 / 5190,6 / 5190,6
LV05 / Nature Reserve / 278 / 278 / 197255,2 / 197255,2
LV06 / Protected Landscape Area / 9 / 9 / 161692 / 161692
LV07 / Biosphere Reserve / 1 / 1 / 474447 / 474447
LV08 / Micro-reserve / - / 23 / 986,99 / -

5.2Table “sites-LV”

  • Overall comments for columns:

Column / Comments
SITE_CODE / Filled correctly.
23new sites need sitecode to be added by CDDA administrators.
SITE_CODE_NAT / Filled correctly
PARENT_ISO / Filled correctly
ISO3 / Filled correctly
DESIG_ABBR / Filled correctly
AREANAME / Filled correctly
SIZE / 35 records without size.
1 record with changed size.
NUTS / Filled correctly
IUCNCAT / Filled correctly
YEAR / Filled correctly
ALTITUDE_MIN / Filled correctly
ALTITUDE_MAX
LAT_NS / Filled correctly
LATDEG
LATMIN
LATSEC
LON_EW
LONDEG
LONMIN
LONSEC
LAT
LON
EIONET CHNG_DATE / Filled correctly
EIONET CHNG_TYPE
EIONET EDITED_BY
EIONET INSTITUTE
NOTES / -
To be deleted / Filled correctly
  • Sites with deleted sitecode (not marked for deletion):No such site
  • Sites with duplicated sitecode:No such site
  • Newly entered sites without sitecode:23 records

National sitecode / Sitename / Designation
8046 / Dzelmes / Micro-reserve
8247 / Visikums / Micro-reserve
8261 / Vidagas meži / Micro-reserve
8263 / Gaujienas purvainie meži / Micro-reserve
8268 / Melderupītes meži / Micro-reserve
8301 / Ozoldārzs / Micro-reserve
8302 / Vecsēlpils / Micro-reserve
8303 / Silzemnieki / Micro-reserve
8304 / Dubļukrogs / Micro-reserve
8305 / Priedes / Micro-reserve
8306 / Bērzoles riests / Micro-reserve
8307 / Bērzu purvs / Micro-reserve
8308 / Bulvāra riests / Micro-reserve
8309 / Graviņas / Micro-reserve
8310 / Šepkas riests / Micro-reserve
8311 / Kalna riests / Micro-reserve
8313 / Bānužu Zelta avots / Micro-reserve
8314 / Dravenieku avoti / Micro-reserve
8315 / Elles purvs / Micro-reserve
8316 / Dzirnieku pļava / Micro-reserve
8317 / Maitiķu avoti / Micro-reserve
8318 / Mežamatveju kadiķu pļavas / Micro-reserve
8319 / Mežamatveju pļavas / Micro-reserve
  • Sites with missing national sitecode:No such site
  • Sites with duplicated national sitecode:No such site
  • Change in national sitecode:No such site
  • Sites with missing ISO code:No such site
  • Sites with incorrect ISO code:No such site
  • Change in site designation:No such site
  • Sites with missing designation:No such site
  • Change in site name:No such site
  • Sites with duplicated name:No such site
  • Sites with missing name:No such site
  • Change in site size:1 record

Sitecode / Sitename / Old size / New size
181880 / Bernāti / 2278 / 2944
  • Sites with missing size:35 records

Sitecode / Sitename / Designation
172475 / Jušulejas dižakmens / Nature Monument
172481 / Ādmiņu dižakmens / Nature Monument
172483 / Lielais Vella akmens / Nature Monument
172508 / Lielais akmens / Nature Monument
172517 / Zeltapses laukakmens / Nature Monument
172520 / Antonu akmens / Nature Monument
172523 / Grīžu Velna beņķis / Nature Monument
172525 / Krauju akmeņu saliņa / Nature Monument
172526 / Lauču dižakmens / Nature Monument
172527 / Seimaņu akmens / Nature Monument
172528 / Velna Skroderis / Nature Monument
172536 / Purmaļu akmens / Nature Monument
172590 / Kapsēdes dižakmens / Nature Monument
172601 / Jaunjurķiņu akmens / Nature Monument
172605 / Tilgaļu milzu akmens / Nature Monument
172606 / Jērcēnu akmens / Nature Monument
172677 / Nīcgales Lielais akmens / Nature Monument
172691 / Radžu akmens / Nature Monument
172692 / Rogaļu akmens / Nature Monument
172693 / Vaiķu akmens / Nature Monument
172712 / Šķērveļa akmens / Nature Monument
172721 / Ramatas lielakmens / Nature Monument
172722 / Ābeļu akmens / Nature Monument
172733 / Ķīvmeža akmens / Nature Monument
172734 / Vecumu dižakmens / Nature Monument
172740 / Zaķu akmens / Nature Monument
172742 / Lielais Krauju jūrakmens / Nature Monument
172743 / Muižuļu akmens / Nature Monument
172744 / Svētciema akmeņu saliņa / Nature Monument
172749 / Plusona dižakmens / Nature Monument
172789 / Velna acs avots / Nature Monument
172797 / Medņu dižakmens / Nature Monument
172806 / Stupeļu Lielais akmens / Nature Monument
172808 / Sudmalkalnu (Nīkrāces) akmens / Nature Monument
172820 / Akmeņkalnu Velnapēdas akmens / Nature Monument
  • Sites with missing NUTS code:No such site
  • Change in IUCN category:No such site
  • Sites with missing IUCN category:No such site
  • Change in site year (without change in designation):No such site
  • Sites with missing year:No such site
  • Sites with missing altitude:No such site
  • Change in coordinates:No such site
  • Sites with duplicated coordinates:No such site
  • Sites with missing coordinates:No such site
  • Sites to be deleted:No such site

5.3Table “siterelations-LV”