Classification
The purpose of these tasks is to connect objects and processes in the model that maintain various considerations and purposes. For example, one classification theme can be separated by drawing key, phase division, or in example classifications acc. processes and objects, in accordance with a given specification.
Find it here:
The individual class assignments in a classification can be linked to objects in the model. One can thus, for example, connect the objects belonging to the tasks of moving cables, demolishing houses, and/or adding a tarmac. Another example is, e.g., linking objects belonging to one field and the person/company responsible for this field. This way, you can connect information in the model with different classifications, depending on the purpose of the classification.
In the Insert menu, there is a button for classification that gives you the ability to insert two new task types:
Classification - Classification is a task that contains classes put into one system and a structure to satisfy a particular purpose. The classification task must contain a name and a description of the standard.
Class - A class task can not exist without a classification task. A class consists of a code and a description.
With V770 classification, you get process codes, and with the class tool, you can connect objects.
To connect classes with process tags to objects use the class tool. Here you can select specific objects or if you want as automatic as possible, use the dynamic query dialog.
Installed templates
In the international version, there are no installed templates.
Input of a classification structure from a text file
If you have your own classifications, you can read these into Novapoint. What is required is that you have a tab-delimited file with a minimum of 2 columns. One column for class code and one column for class description.
Choose the Import from a text file template. The dialog that comes up lets you open a text file, and you get a preview of what the class tasks will look like.
In the dialog, decide from which line classes are defined and you can load one delimiter; a specific character that indicates that there is a new class. Otherwise, there is an alphanumeric sorting, and it pays to have done this sort of text file before reading the file.
If it looks okay, click Finish and type a help text for this classification in the menu.
Known error: There is a limit of 255 characters in the code and description field. If you have more the program will stop reading the file.
Export of objects with classification codes
When objects in a model are connected to their respective process codes, you can use these when exporting to DWG and LandXML. For these formats, you set up combinations of classification and description, so that, e.g., DWG layer names and LandXML object name is named acc. classifications.
Export to DWG.
To produce a DWG file with process codes in the layer name, you must start the function export to DWG on the delivery menu. This functionality is only available here. The following menu bar appears:
To set up the classifications to be generated in the layer name, you must choose the Use field codes option in the drop-down list below the layer standard assignment and then press Settings (sprocket). Then you get the following dialog:
In this dialog, you must add the codes and descriptions that should be used to generate the layer name. Furthermore, it is possible to create a separate string for the layer name description. See the next dialog as an example of the setup of layer names, with a drawing key and object code in the layer name and description in the column layer description.
By pressing Add, you get access to the classifications placed in the model. And you can then select each one as part of a layer name.
In the setup for export to DWG, the layer name of the string “ FIELDCODE_1 » and layer name description of string ” FIELDCODE_2 .“ ” FIELDCODE_1 » is string created.
Once you are ready, save your setup to the task by pressing Finish to produce a DWG drawing. In the open drawing setup (shown above), have a layer structure that looks as follows; (depending on which objects you have chosen to send to DWG )
LandXML export
In the same way as for DWG export, in LandXML export you must also set up how the string to be sent to LandXML should look as to code and description.
In the export, choose LandXML as the format and then press Settings (sprocket) which provides access to a setting dialog. The following picture shows one example of how code and description are combined. This string is later sent to the object name of the object in the LandXML file.
When the string is set up as you want it to, press Save to task and then Choose a rule in the export menu. It is important that you choose the conversion rule «Roadmodelsurfaces with fieldcode name».
Press Select and then OK so the file will be added to the conversion field export menu.
Press OK in the menu for export. The LandXML file is produced. If one reads the file in another application. E.g., in Civil 3D, objects from the LandXML file come up with names such as those configured in string field codes.
See the following pictures. From import; Done uploaded;