Find it here:

MOUS_ICO Menu: Noise > Calculation

In this dialog box, we create alternatives and perform calculations. Only one alternative may be calculated at a time.

An alternative may be regarded as a name of the calculation we are running. The calculation results and the input data that were current at the start of the calculations are saved together with the alternative. In Novapoint Noise, we may compare different alternatives by printing text at calculation points for multiple alternatives at the same time.

In Novapoint Noise, it is completely up to the user of the program to keep track of the different alternatives. The user himself must change input data as different alternatives are calculated.

We have the opportunity to supplement an alternative with more points. This is done by setting the calculated points passive and the new points active. After that, the calculation of the relevant alternative is restarted. In this case, as well it is the user's responsibility to make sure that input data for the two calculations are identical.

Object handling

Window handling


Calculation parameters

When Reuse of profiles is activated, all terrain profiles are saved to a file during the first calculation. For the following calculation(s), Novapoint Noise fetches the requested terrain profiles which already exist from the file. Requested profiles that do not exist in the file, are imported from the terrain model. These new terrain profiles are saved with the rest.

Terrain profiles that are saved to file, are deleted once the calculation starts if the terrain model has been accessed since the previous calculation. This is done to prevent mixing old and new terrain profiles in a Novapoint Noise calculation or using only old terrain profiles if there have been changes to the terrain model.

Changes of barriers, buildings, hard ground regions and traffic data may be made without regenerating new terrain profiles from the terrain model. This functionality reduces time use considerably.

This option can not be used if reflection is specified.

Storing terrain profiles may require a lot of disk space. The terrain profiles for one single calculation point may require approximately 50 kb per road. The exact number of bytes needed depends on the length of the road, the distance between the road and the calculation point etc.

Calculation using reflection takes more time than without. Especially using multiple order reflection the time increases exponentially with the order of reflections.

MOUS_ICO Menu: Noise > Deletion > Delete temporary data

The profiles show terrain profiles with barriers and buildings if any. If a barrier is included, reflection planes are drawn in front of and behind the barrier.

Lower, left corner

Sets the coordinates for the lower, left corner of the first profile to be drawn, if Draw profiles is on.


Calculation of alternative - Example

The following gives an example of the possibilities Novapoint Noise offers for defining alternatives. In this example, we are going to calculate noise levels for a new road (Designed in the Road model). Seven different alternatives for ten calculation points are to be calculated.

Common preparation (applies to all alternatives):

Alternative 0

Alternative 1

Alternative 2

Alternative 3

Alternative 4

Alternative 5

Alternative 6


Reports may be printed for all alternatives, including summaries and all details.

Alternatives 1-6 may be compared by printing text at calculation points for all alternatives simultaneously.

No warning will be given if for instance Alternative 3 had been calculated with the input data for alternative 2. The user is always responsible for checking that the input data are correct.

If in doubt about which input data was used for a specific alternative, look at the input data report. This report is ordered in the dialog box “Report” (see Report).

Next topic: Noise Contour Lines