Project ID

Use this tool for the following:

• Create/open/delete Novapoint projects, terrain database (Digital Terrain Model), and road model database.
• Administrate the terrain model database and the road model database.
• Save project settings file (*.NCP) - save different project specific parameters, e.g. default values in drawing functions, etc.

Run the function form the following locations:

Toolbar: Project ID

Menu: Novapoint > Project ID…

Command Line: Not available from the command line

The dialog box 'Novapoint Project Setting' will pop up.

• It is an option to show the Project Configuration dialog on Novapoint Start-up.
• It is recommended to set this to 'On', reminding the active project, the active database and, if of interest, the active road model database to the user.
• If this is not set to 'On', the dialog will pop up automatically if user starts a function that need a Novapoint project.

User doesn't need an active project to start using Novapoint. This to support users who sometimes use plain AutoCAD functions, storing to drawing files only.

When active project is set to <Not Selected> Novapoint still operates with a set of temporary databases:

• Temporary terrain model: Novapoint Terrain Model.TMG
• Temporary road model: Novapoint Road Model.GEN

If you start using Novapoint functions that needs to store in one of these databases, Novapoint will automatically store data into the temporary files.

If you exit from AutoCAD, or if you start the Project ID dialog, and select or create a new terrain or road model, you will be asked if you want to store the temporary databases first.

Novapoint keeps track of the 10 last used projects. Select active project from the drop down menu.

By clicking this icon, a dialog box pop up, listing all the users who are logged on to the same project as you are, along with a log on information such as date, time, etc.

If green, it means that no one else is logged on to the project.

If yellow, it means that there exists one or more users logged on to the active project, but you may have read access to the project.

If red, it means that there are users logged on to the active project, and you have no access to the project.

You can save changes made to Project Settings using the save icon. This option is available only to the user having access type Write Access.

This applies to Novapoint Project Settings that are saved in the project file. This file needs to be “protected” if one of the users needs to edit it. This user chooses access type Write access.

Other project users will then have 'Read only access', as the access type is disabled (note the icon for read access).

Set default start-up to Read Only: Use this if you normally should have Read Only access only to project data.

By default, Novapoint will give the 'Write access' to the first user who logs on to a project. This will be the natural choice for the single user project.

If you choose “Use active project settings” you will experience that settings you have made “disappears”. The reason behind this option is that in multi user projects the settings are setup “once and for all”, and then everyone gets access to this information in the project. To be able to do this, Novapoint allows the project users to have read access only. If everyone were to have write access simultaneously, the NCP file could easily be corrupted.

In a project, it is often desirable to divide the data between concurrent users. This is a challenge, because only one user at a time can have write access to a given data object. When someone for example imports a file to the terrain model, other users need to be kept away from the terrain model until the import function has completed.

In addition, it is desirable to be able to obtain information about the users working on the project, in order to easily co-ordinate within the project. In Novapoint this is controlled by means of Project Settings, which at runtime logs the concurrent users within the project.

It is important to be aware of the fact that the information about who and when the users have worked on the project is not permanently saved to the project file. When user exit the project, he/she is “removed” as an active user.

Use this function to establish a new project. Give the project file a name and a location.

This function creates a new terrain model and adds it to the project. The path to the terrain model will be stored relative to the path of the project (that is: The location of the NCP file).

This function makes you browse to an existing terrain model and add this to the project. It also sets the added terrain model to active.

The user may from the terrain model drop down list select another terrain model, to set this as the active terrain model. The Road model selection list will be refreshed to show the road models, if any, that are connected to the active terrain model.

This function removes the active terrain model from the project. It only removes the reference to the terrain model from the project (stored in the NCP file), and does not delete the terrain model database from the project folders. Any references to road models connected to the removed terrain model are also removed from the project. Only the references to the road models are removed, not the road model databases itself. To add the terrain model to the project again you use the Add terrain model function.

This function creates a new road model and adds it to the active project. Give the road model a name and browse to the location for storing the road model. You may select a road model template (file extension: IND) from the drop down list when creating a new road model. The road model will then be created using the default values from the template. A terrain model must be active in the project when a road model is created. If the terrain model is set to <Not Selected> the road section is disabled. The path to the road model will be stored relative to the project path (that is: The location of the NCP file). (The road models path to its terrain model is actually stored within the road model also, and then with full path.)

When creating a new road model the system as default uses a template file to establish road model default values. A standard file that comes with Novapoint installation is used as default. The name of this template is Standard. You may browse to your own templates (files of type IND), select browse in the selection list to do this. To make you own favourite templates selectable in the drop down list, store your templates here: [DRIVE]:\Documents and settings\[UserLogonName]\Application Data\ViaNova\Novapoint\16.30\Norway\Road\Config\*.IND A template can be made from the road models ìSave asÖî function. See documentation of this function in the Road Design Help file.

This function makes you browse to an existing road model and add this to the active project. If the road model has been connected to a terrain model with the same name as for the active terrain model, it will connect without any further questions. If the road model has been connected to a terrain model with a different name as for the active terrain model, a message box will appear, with information of the previous terrain models name, and a question if you want to proceed. If yes, the road model will be connected the active terrain model. This function also sets the newly added road model to active road model in the project.

You may from the road model selection list select another road model, to set this as the active road model. If the road model's reference to it's terrain model is not concurrent with the active terrain model, a message box will appear, asking if you want to redirect the road model to the active terrain model.

This function removes the active road model from the project. It only removes the reference to the road model from the project (stored in the NCP file), and does not delete the road model database from the project folder. To add the road model to the project again use the Add Road model function.

You may need to relocate the project to another server or folder, with all its subfolders. This may be done using the File Explorer or other file handling tools. Since the path to the terrain and road models are relative to the NCP file, you do not have to redirect these as long as you do not alter the original structure within the project folders.

The following file types are created and administrated from Novapoint Project Settings:

<Project Name>.NCP: The file is created when establishing a new Novapoint Project. Project Settings are saved in this file. On creation you decide where to locate the file.

Ncpinuse.ncp: When a user logs onto a Novapoint Project, data from <Project Name>.NCP is copied to this file. Path for the file location is

<Local Drive>:\Documents and Settings\[User Logon Name]\Application Data\ViaNova\Novapoint\<Novapoint Release Version>\<Installation Version>

E.g.: For Novapoint Release Version 17.00 and Norwegian Version the path for the file location is: <Local Drive>:\Documents and Settings\[User Logon Name]\Application Data\ViaNova\Novapoint\17.00\Norway

If user has access to the project settings, the content of this file will be copied to <Project Name>.NCP when:

• The user saves the project settings
• Select another project, or exit Novapoint.

The file is created when the first user logs into a Novapoint project. If other users logs into the same project, the NCP file will be updated with information about this user. The file is deleted when the last user logs off the project. The file is created in the same folder as the project file.

A list of users who are logged on to the database will be created. Every time user logs on to the database the file will be updated.