additional 6,254 km?). The third level (1:250,000 and 
1 : 1,000,000) is covered with only one map sheet, so the area is 
rectangular and significantly larger (55,586 km?) than other 
levels. 
Altogether, there is: 
= 22248 km? covered with the scales of 1: 5,000 or 
1:10,000, 1:25,000, and 1:250,000 (three different 
levels), 
m 5,263 km” covered with the scales of 1:25,000 and 
| : 250,000 (two different levels), 
= 62254 km? covered with the scales of 1:50,000 and 
| : 250,000 (two different levels), and 
= 21,821 km)? covered with the scale of 1 :250,000 and 
| : 1,000,000 (two different levels). 
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
Map scales of 1 : 5 000 or 1 : 10 000 
EI 
Ss Map scale of 1 : 25 000 
[777 
Le 
Map scale of 1 : 50 000 
Map scales of 1 : 250 000 and 1 : 1 000 000 
Figure 1: Areas covered by maps of various scales. 
The overlapping of different levels (see Figure 1) leads to the 
redundancy of names in the REZI database. Map annotations 
from different levels of detail should refer to the same geo- 
graphical entity. Trying to uniform different levels into a 
unique database, one is faced with troubles. These names ought 
to be the same. But there are many reasons for not being so: 
" the use of more than one name for the same geographical 
entity (allonyms), 
" the use of either full or short form of the same name, 
" the use of shortenings of the name, and last but not least, 
" the appearance of wrongly written names in the database. 
Allonyms could appear as: 
" different names in different languages on multilingual 
areas where all of them are endonyms with official status 
(eg. Koper — Capodistria in Italian), 
" different names in different languages, where some of 
them are exonyms (eg. Benetke /Venice/ = Venezia in 
Italian), 
" different names in the same language with different origin 
of the name (eg. Kriska gora = Kokovnica), 
" different names in the same language with the same origin 
of the name (eg. Dolenjska = Dolenjsko) etc. 
Allonyms could have equal status; on the multilingual area they 
could all be official. But many of alternative names could also 
arise from local or regional dialect (eg. Spodnja Idrija — Pri 
Fari). 
50 
Full and short forms of the same name appear: 
" for country names (eg. Republika Slovenija /the Republic 
of Slovenia/ — Slovenija /Slovenia/), 
= for some frequently used compound names (eg. Julijske 
Alpe /the Julian Alps/ — Julijci /the Julians/), 
" for names with appendices used for differentiation (eg. 
Breg pri Ribnici na Dolenjskem — Breg pri Ribnici — 
Breg) etc. 
Full and short forms could have equal status; for country names 
they are even standardized. But in most cases, the short forms 
are used only informally. 
Shortenings could appear as: 
=  acronyms (eg. Trg Osvobodilne fronte — Trg OF), 
= abbreviations (eg. Sveti Jurij — Sv. Jurij), or by 
= omission of letters or syllables (eg. Pri JoZetu — Pr 
Jozet’) etc. 
Shortenings are often used in cartography. The 
recommendation of experts was to avoid any kind of 
shortenings in the REZI database. Eventual shortenings are left 
to the users. 
The uniforming of the names also brings up a question, whether 
naming of geographical entities could depend on the level of 
detail (map scale). In other words, we are talking about the 
generalization of geographical names, reached by changing the 
names themselves. Unfortunately, the answer is affirmative. 
There are some groups of names that could be merged together 
into one simplified name. That could be found frequently for 
mountain peak names (eg. Veliki SneZnik + Mali Sneznik — 
SneZnik), mountain chain names, valley names, cape names etc. 
The merge of names of neighbouring geographical entities 
could be found as well (eg. Ljutomerske gorice + Ormoske 
gorice — Ljutomersko-Ormoske gorice). Of course, all these 
level of detail depended variants of the names need to be kept 
in the database. 
7. TOPONYMIC DATABASE MODEL 
The first version of the REZI database was a database of map 
annotations captured with the following attributes: 
= map inscription or name string (text up to 50 characters), 
" geographical entity type (number; entity type code), 
= map system (number; map system name code), 
= map nomenclature (text up to 10 characters), 
= text height (real number; mm on the map), 
= corner coordinates of the circumscribed rectangle (real 
numbers: x min, y min, x max, y max). 
This way all the names could be automatically used in carto- 
graphy. Typography definition was left to the map designer 
who is using the database, applying geographical entity type 
information. 
In the year 2001 a new scheme of the REZI database was 
proposed (Berk et al., 2002). The three level of detail based 
parts of the database are going to be merged into the uniform 
database. The logical database model is based on the three main 
entity types: 
= map annotation, 
= geographical name, and 
" geographical entity. 
Each get 
is a relat 
in more 
This rec 
redundai 
the thre 
dization 
ENTIT 
The new 
of two 
geograpl 
entities). 
graphica 
for the tc 
8. H 
The hart 
this yea 
expected 
(bilingue 
separate: 
with con 
be done 
not alwa 
geograpl 
the sam: 
names ir 
fifth sett 
frequent 
Ravne. , 
names e 
done ma 
There i: 
database 
changed. 
database 
Slovenia 
year in |