The Dutch- and German-speaking Division of the United Nations Group of Experts on Geographical Names (UNGEGN) and the German Federal Agency for Cartography and Geodesy (BKG) initiated the EuroGeoNames (EGN) project in 2004.
During its EU-funded project period (Sep ’06 to Feb ’09) it established a European geographical names infrastructure by connecting the existing national data sources of the participating NMCAs. By that the geographical names data is updated in a consistent way and maintained at the source level by the responsible organisations. Hence, EGN neither affects the independence or the organization nor the responsibility of the national agencies that produce and maintain geographical names repositories.
The EuroGeoNames project targeted primarily at value added resellers (VARs) and service providers to develop specific applications for their customers and deploy value-added GIS products by using the EGN Central Service.
EGN also capitalised on the knowledge of European geographical names experts with respect to using authoritative geographical names context sensitively and appropriately. Sometimes wider political issues are related to them and almost always, linguistic issues were taken into account e.g. majority and minority languages, pronunciation etc.
Thus, a full-blown distributed multilingual geographical names data infrastructure for Europe helps to promote cultural diversity and multilingualism.
Project’s objectives
The main objectives for the EGN infrastructure and services proposal were:
Project’s solutions
The EGN consortium addressed the current deficiencies within Europe with respect to the management and exploitation of geographical names resources by the following means.


EXAMPLE: Danube as border-crossing spatial object
- Link between EGN Central Service, the EGN Local Services and the Exonyms and other variant names database (EVN-DB)
The objective of EGN

A German user wants to get the information about the Danube river and starts his/her single inquiry with “Donau”. He/she aims at getting information (all names and the geographic extent) about the complete spatial object (which may be a combination of 9 spatial objects from 9 national datasets).
EGN Local Services
Assuming that all EGN Local Services needed are running, the EGN Local Services provide the following information:

One country/NMCA may provide more than one geographical name associated to the respective spatialObject_UID.
The linkage between the “national” pieces of the whole spatial object (border-crossing spatial objects) is done within the Exonyms and other variant names database – EVN-DB.
The EGN Central Service provides the respective national pieces from the EGN Local Services together with the information stored and maintained in the EVN-DB.
Relation to the Exonyms and other variant names database – EVN-DB

The EVN_DB stores one set of exonyms and variant names [1..*] which can be associated to all (national) spatialObject_UIDs with cardinality [1..*].
As for the Danube river, 1 set of exonyms and variants are stored for 9 spatial objects – which are linked together through the EVN-DB.
The English exonym or variant name is always introduced if available.
Border-crossing spatial objects without associated exonyms are not linked within the EU-funded period.
Results provided through the EGN Central Service in combination with the EGN Reference Application (according to the EGN data model):

The compiled boundingBox will not be calculated automatically, but the national parts will be provided together with their respective boundingBoxes!