The International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences. Vol. XXXVII. Part B4. Beijing 2008 
u 
sfi 
¡3 
S 
.2 
? 
Is 
5 
> 
Interaction 
(query/geopro- 
cessing/routing) 
Download 
’S 
ta 
Commit 
Public 
limited 
limited 
no 
no 
no 
maps + 
attribute 
Hum 
Logs 
yes 
yes 
reports 
. only 
no 
(.IS 
y es 
yes 
yes 
........yes...... 
no 
maps + 
attribute 
HQ 
Logs 
yes 
yes 
reports 
only 
no 
GIS 
yes 
yes 
yes 
yes 
ye 
s 
Table 4 - UN JLC users privileges schema 
The system is made of two Oracle database instances, one 
acting as master database and another, the slave GeoDB, 
hosting a full two-way replica for data production; that solution, 
together with adequate back-up policies, should grant data 
protection and integrity (Figure 5). 
HUMS Oracle JOg 
G«*wa? ESRJ AreSDt 
PosrfkPoiUrrcSQL. 8.2 
( .tornei n storage tXK'WKJ} 
SDOGEOMTTRY 
WKB 
WKT 
CIS clients 
tt Mi Applications 
Mtladtla anil 
Calalttgue 
(SRi AtvGIS Desktop Desktop or WEB based 
Î SRI ArcCilN Serscr* WMS WFS 
GeoNMwork 
Caapfint graduai 
K*!»tie*ed pre-dsiet 
Table 6 - System standard compliancy 
2.5 Back-up system and strategies 
Physical back-ups are performed on tape for offsite storage and 
system restore. In addition, the master instances will be 
replicated in a near real time on a back-up site configured and 
kept aligned constantly with the master site. 
A further development includes the creation of a Real 
Application Cluster based on Oracle 10 G, in order to increase 
performances by applying load balancing mechanisms. 
Figure 5 - Data distribution schema 
The back-up site is configured to behave as a stand-by node: in 
case of a major failure of the main node, application layer can 
be redirect on the slave cluster in order to grant services without 
any significant failure (Figure 7). 
Following that schema, LAN users that can connect directly to 
the master GeoDB may operate in function of their privilege 
levels on the database or on specifically created versions, to be 
reconciled or not with the parent one. 
External users that have limited or no connectivity, may work 
on replicas that, once an editing activity is terminated, system 
administrators may synchronize with the master database. 
Moreover, users that are in charge of manipulating only the 
alphanumerical content of the database may work using 
specifically developed data entry applications. 
The broader humanitarian community, made not only of UN 
officers but also of NGO’s, local administrators, affected 
population, etc. can gain access to stored territorial information 
through suitable web-based services and applications provided 
by the application layer connected to the publication GeoDB 
replica. This environment is designed to be fully a standard and 
interoperable one (Table 6). 
Figure 7 - Back-up schema 
3. GEODATABASE CONTENT 
Based on the data structure submitted and approved by WFP 
(ODAP and VAM) and UNJLC, a UML data model has been 
consolidated and implemented using an ORACLE lOg database 
as DBMS platform. 
The database schema is composed by 2 different entities: 
• Base data includes basic geographic and alphanumeric 
information, in order to produce basic geographic outputs 
and analysis (Tables 8 and 9). 
• 
According to the geographical extension of areas of interest 
considered in WFP activities, globally consistent data (very 
little scale) or data concerning at least the main WFP action 
areas, have been included in this database. Moreover, 
particular attention has been paid to identify and include 
geographic data released into the public domain; these data 
cannot be copyrighted, restricted or licensed once they are 
1100