Most of the predictable problems can be combated by 
establishing BUILDER’s RULES, BUILDER's, which is 
of substantial benefit for the user. 
Problems, which BUILDER is unable to resolve on its 
own, are correspondingly marked and dealt with in a 
subsequent "correction phase" (INCOME EDITOR). 
The disadvantage of a system which tolerates errors 
is obvious. If data acquisition is too "careless", 
the number of errors, which have to be corrected 
interactively can become overwhelming. Thus the 
time gained when working with COLLECTOR is more 
than  outweighed by the additional (generally 
considerably greater) time needed vith EDITOR. 
By far the better solution is to avoid 
"predictable" conflicts in advance by fully 
exploiting the facilities provided in COLLECTOR for 
increasing data acquisition accuracy (e.g. SNAP). 
In this respect, it would be wrong to look upon 
BUILDER as a remedy for all ills, which offers just 
the right strategy in every conceivably confused 
situation. 
+ Bartelme N. und Spaeni, B.: "Spatial Access 
to Thematic and Thopological Structures in 
GIS", presented paper at the 16th  ISPRS 
Congress, Kyoto, 1988. 
+ Frank  A.: "Requirements for Database 
Management System for GIS", PERS, Vol LIV, Nr 
11, November 1988 
+ INFOCAM Product-Information, Version 5, Leica 
Heerbrugg PMU, 1991. 
14