Updating the current EGM database v2.1
The EGM v2.1 was released in early March 2008. This was an “intermediate updating” including just some error corrections without actual updating of the themes. Previous version v2.0 (released early 2007) was a normal update of the data and first version where ArcGIS Geodatabase structure was used to save the final European wide data. Project partners used mainly softwares such as ArcGIS, Arc/Info (workstation) or MapInfo during the data production.
EGM database specifications updating
There are needs to make slight changes to current specifications (v3.1). Updating eill be done in co-operation with other EG products (ERM and EBM) and is coordinated by the PM. The coming version is called v3.2.
Final goal in EuroGeographics is to update only the ERM data (or European wide large scale data when exists) by partners and to produce EGM from ERM data via automatic/semi-automatic procedures. This is not yet possible during the next 2 years, but needs anyhow common feature catalogue (EGM shall be a generalized part of the ERM data).Some issues:
- New feature class “Land mass” for just land areasFerry lines attributingTopology rules updating (e.g. foreshore is part of water and must overlap sea area)Checking mandatory / optional rules (attributes)Defining ICC code (country code; see below)Defining SN code (symbolisation number)
- Number of population / classification for feature classes BuiltupA and BuiltupP
EGM Technical Guide for Data Collecting and Finalizing
Current Technical Guide (v1.4) is mainly still valid, but it’s platform dependent and too closely connected to Arc/Info coverage structure. The new guide will include only instructions for data collecting and finalizing (platform independent). How to save the data into geodatabase, coverages or shape files is another question. Because most partners can use GDB or shape file structure, it looks there is no need to create instructions to other formats.
Internal quality checking of the data
Quality improvement of the national data. Creating national QI-programs:
- New document “EGM_DataValidation” explains detailed quality control processes
- Completeness: missing features and feature classes and correct density of the data (scale 1:1 M). All features existing in a country and defined in the EGM database specifications as features MUST be included to the database (e.g. all the “main roads”).
- Completeness: missing attributes (empty attribute fields).
- Checking missing attribute values: Real attribute values missing; i.e. using N/A, UNK, N_P, N_A. Basic information about this is saved to each country’s EGM metadata “lineage” file. The goal is to reach level “100 % real values” with as many attribute fields as possible. National inconsistencies are reported. Improvements compared to previous EGM version are reported.
- Replacing very old ( ≥ 7 years ) EGM data with a new national data whenever possible. This concerns all themes and feature classes.
- Fixing topology errors.
- TEN routes: According the Eurostat contract all TEN network roads should be included to the data. In most countries they are. Some partners should make necessary checks. Instructions will be given to each partner.
Regular updating of the data:
Feature |
Description of the update |
POLBNDL & POLBNDA |
Administrative boundaries. Meaning changes in national administrative structures. Related tables to be updated also. If the structure is the same as before these are not updated (slight geometry improvements not saved, just remarkable changes). Note that data has to be dated according structure 1.1.2009. |
|
RAILRDL |
New railroads, possible changes in geometry and attributes (e.g. electricity) |
ROADL |
New roads, possible changes in geometry and attributes. |
FERRYL |
New ferry lines. Attribute structure is changed is the specs. |
FERRYC |
New feature class: see the specs and the Technical Guide. |
AIRFLDP |
New airports, possible changes in attributes. |
|
BUILTUPA |
Possible changes in geometry of the areas and attributes; especially the number of population. Using actual number of population is highly recommended instead of national population classifications. |
BUILTUPP |
Possible changes in attributes; especially the number of population. Using actual number of population is highly recommended instead of national population classifications. |
LANDA |
New feature class. Is created by the PM. |
THEME: HYDRO |
No regular updating; just error corrections e.g. topology and attributes according the EGM Evaluation instructions. |
THEME: ELEV |
Checking the ZV –values: according European N2000 system; when possible. If the differenries are not significant then no updating needed. |
THEME: NAME |
No regular updating |
All the documents concerning data updating and evaluation are sent to the project partners latest at the beginning of january 2009. At the same time NMAs will receive all the databases needed to start the updating.
|