|
These tables give the possibility to hold plan borders in a data bank and to generate from these plans. Because Moskito is used for listing and searching by plans then the plan management the searching speed higher than without plan management.
The tables of a plan management lie in the files
*.DBF and *.GDV
in the list GDS$DBB before. * is here the name of the plan management which <>must have been opened with plan management open <name>.
The tables ""can be filled with the unterfunctions of "plan management" or with a data bank. "Plan management CREATE *" generates that the empty data bank tables.
Structure
*.DBF
NAME
|
TEXT
|
Name of a plan
|
XUL
|
NUMBER
|
Left lower corner of the plan
|
YUL
|
NUMBER
|
"
|
XOR
|
NUMBER
|
Right upper corner of the plan
|
YOR
|
NUMBER
|
"
|
LAYER
|
NUMBER
|
Sheet type of the plan
|
*.GDV
LAYER
|
NUMBER
|
Number of the sheet type, at this number the plan management can be demanded.
|
GRADUATION
|
NUMBER
|
Plan graduation
|
RESOLUTION
|
NUMBER
|
Resolution of the co-ordinates with the memory as a DBB
|
TYPE
|
TEXT
|
Number of the sheet type as a text, on this sheet type the plan management accesses. If LAYER and TYPE should agree possibly.
|
VERSION
|
NUMBER
|
Start version of the generated plan
|
ART
|
TEXT
|
R (elativ) or A (bsolut), insignificant.
|
PUT
|
NUMBER
|
7 or 9, insignificant
|
SUBSTITUTE
|
NUMBER
|
If here one of 0 different values stands and the plan management shows such a LAYER, then the plan from this LAYER is loaded if he does not exist in the topical LAYER, does not implement.
|
PRIVILEGE
|
TEXT
|
R or W, with R the plan is loaded only reading and cannot be stored.
|
SEARCH
|
NUMBER
|
LAYER information similarly to SUBSTITUTE. However, in this case the differently named plans which lie in the same co-ordinate area are also loaded.
|
LOADER
|
TEXT
|
Name of the data format with which the plan can be put on and be protected later.
|
|