Working Practices

By default, database follows the SOSI feature code register, which is a standard of Norwegian Mapping Authority. If some other feature code register is to be followed, change the feature code register, using tool 'Set Feature Code Register'. See the topic 'Set Feature Code Register' for functional explanation.

Primary data is to be imported to the data using the routine 'Import'. See the topic 'Import' for function explanation. Various data formats that can be imported are explained in the topic 'Data formats'.

After the terrain data has been imported into the database, a control graphic should be drawn. The result is best checked visually on drawing file. Undesired lines can easily be seen on a plan-drawing, whereas errors in elevations are easily seen in longitudinal/cross-section profiles. Errors in terrain data must be corrected before the terrain model is used further. Plan-drawings can be generated using the routine 'Draw Map from Terrain Model' and profiles can be generated from the routines 'Draw Longitudinal Profile from Terrain Model' and 'Draw Cross-section Profile from Terrain Model'. See the respective topics for functional explanation.

The function 'View/Edit' is a graphical interface of terrain model, which enables to view and edit the data present in the database. See the topic 'View/Edit' for more details.

For calculation of soil quantities in areas of arbitrary shape, contour map generation on the basis of total station instrument measurements, or, if points are entered into the model as a “point grid”, a grid must be generated before any other calculations are carried out. For visualization of terrain including terrain cuttings, i.e. roads from Road Design, grid model must be generated for the terrain surface. Grid models can be generated using the routine 'Grid Model'. See the topic 'Grid Model' for functional explanation.

If surveyed terrain data are logged as point grid, triangle model routine can be used for profile generation, etc. There is no limit to the number of points, which may be triangulated, but the speed of calculation depends on the number of data points. Triangulation is automatically carried out several times for large models. Triangle models and contour models can be generated using the routine 'Triangle Model'. See the topic 'Triangle Model' for function explanation.

Grid model and triangle model are created from primary data. Contours can be created either from a grid model or from a triangle model. The most commonly used method is from a triangle model.

See the topic 'Edit Feature Code Register'.

Terrain data can be produced as an edited printout or on file for transfer to other software systems. Before printing, a decision must be made as to the format and feature codes to be used. The feature code conversion table is used during printing and ought to be checked in advance.

The properties of the database (group status active/passive, priority of group, level of group, type of data in the group, feature code status active/passive, etc. For more details see the topic 'Groups/Feature Code Settings'.

Details of terrain sub surfaces can be defined used the routine 'Define Sub Surface Layers'. See the topic 'Define Sub Surface Layers' for more details.

See the topics 'Database Info', Database Maintenance', 'Database Purging', and 'Database Transformations'.