As-built FKB SOSI Control¶
SOSI Control¶
Check the file in SOSI control¶
SOSI-vis with SOSI control is a program for quality control of geodata in SOSI format. SOSI control can be used to check the format (syntax) and code sets. We get help finding errors in the dataset and it makes us more aware of the quality of data files in SOSI format.
During installation we get two programs: SOSI control and SOSI-vis. SOSI-vis is a program that provides a graphical display of files in SOSI format. SOSI control is integrated into SOSI-vis, and it is recommended that we use this combination for the control. We then get a graphical identification of the objects that contain errors.
Software download
SOSI control (which is free) can be downloaded from the Norwegian Mapping Authority's website.
Using SOSI-vis/SOSI control¶
Procedure
- Start SOSI-vis
- Select File - Open files...
- Browse to the project folder and open the SOSI file
- Activate the i (information) icon on the toolbar
- Click on the icon for SOSI control
- If the file does not contain product specification, we must select controls manually
- Check the relevant options
- Click the Perform control button
- Click Exit and a new window with errors and warnings appears. Browse through the errors, which are also located on the screen
Report file
You can also create a report file (*.txt) with the same name as the SOSI file. On the first files we run SOSI control, everyone will experience getting error messages. As we become more experienced and familiar with the causes of the error messages, they become fewer and fewer.
Errors and warnings¶
Below are the most common error messages and warnings in connection with as-built road data described.
Error: No match on object type. Check standard for product¶
This message occurs if you have not entered values for OBJTYPE. Go back to Gemini Terrain and enter OBJTYPE where it is missing.
Error: HREF missing¶
We get this error when mandatory properties do not have a value. In this case, it is HREF that is missing. Go back to Gemini Terrain and enter HREF where this is missing.
Error: Illegal object type used for delineation of the surface¶
This error is due to one or more lines delimiting the surface having the wrong OBJTYPE. Go back to Gemini Terrain and enter the correct OBJTYPE for the line.
Error: Surface delineation error. Delineation object type not referenced in any surface¶
This error message is caused, for example, by a road edge line not being referenced in a surface. Typically, this will be small line segments that remain after automatic cleanup of the lines.
Error! Different height between group nn and mm¶
This message is due to having 3D lines (lines also with value for z) with different heights at the junction points. Go back to Gemini Terrain and set equal height on all lines at the junction point.
Warning! Same group information with group nn¶
Between two junction points, there should only be one line object when all other properties are the same. This is not an error, but more of a remark. By merging these line stubs, we get reduced size and complexity of the dataset.
Example where lines 1, 2, 3 can advantageously be merged since they have the same group information