Inserts a catalogue in DIRA


With this command the user can insert a data table in the PDB in a simple and fast way. The data fields, in the input table, must be separated by columns of blank characters, otherwise the task can not recognize the fields. The application reads the user file, recognizes the column and identifies character or numerical fields, then update the PDB with dummy variables called V1, V2, V3 ... Vn. When the user data file includes sky coordinates these must be in a DIRA valid format (see chapter on Catalogue fields) because DB_INSTAB does not make data conversion.

The DB_INSTAB command can fail when there is not a blank column between two fields, in this case he recognizes only a single field. Moreover when there is, by mistake, a wrong alphabetic character in a numerical field the DB_INSTAB recognize entire the field as a character field. The user can fix this problems useing the PDB_MANAG command. When this task can not resolve two fields the user can modify the evaluated lenght of the first field and then, manually, insert the second field with the command "INSERT cat VAR namevar" of the PDB_MANAG task. Remember that, the sequence of the the fields written in the system file, can be different from the sequence of the fiels in the catalogue file.

INPUT FIELDS of the command:

Input File name:

The name of the input data table that the user wants to insert in the PDB.

Example : TABEL1.DAT

PDB Catalogue :

The name of the new catalogue that will be created in the Personal Data Base.

Example : TABEL1


The task starts reading the input data file, then type on the screen the fields mask found on the data set. On the field mask a column of numerical character is identified with "9", a dot between numbers is identified with "." and characters column with "X". Then the list of the field found is written.

After a DB_INSTAB session the user must run the PDB_MANAG to rename the fields (V1,V2 ... Vn) with mnemonic codes and he must define the right types for the coordinates fields and specify sort key (if it exists).

We advice to use the DB_CHECK to verify data coherence of the new catalogue.

Previous: DB_INFO
Up: Commands
Previous Page: DB_INFO
Next Page: DB_JUNKEY