Warning/Error Messages

We generally recommend to resolve any messages as soon as it is practical to do so to avoid the results having errors or issues that might give a wrong representation of the design for other disciplines in the project.

How to act to solve your messages 

Answer: Try to remember what changes you did to the road task that caused the messages to appear. There are probably something in that design change that caused the message. You may also try to turn different functions ON/OFF to see if the messages disappear in the Settings-function. Try to turn them all or some of them OFF and see if things improve.

If you cannot find the reason for the problems in a specific cross-section it may be because the model is using Boundaries on the left- or righthand side in the Road Surface description. Try turning OFF the boundaries found here: Design > Settings > Elements > Boundaries > **Road surface boundaries**.

The Road model calculation separate messages between:

Furthermore there are error messages that may be related to the specific step in the road model calculation, where some may be related to the cross-section calculation (step 1), and others may be related to the updating process with the Quadri model (step 2 and/or step 3).

The error/warning messages are listed in numerical order below.

(The list is not complete)

0: Fail to connect features to alignment

Answer: The alignment is missing its linksequence. Check that the line feature in the Line task is of type 'LinearElement'.

2: Unable to establish terrain profile at this chainage

Answer: The cross-section does not have terrain data. Or the cross-section has too much other data in the cross-section so that it cannot store the terrain data. Reduce the amount of data in the cross-sections, either from the calculation basis or the illustration objects.

If you need the illustration objects for visualization you can consider trimming the amount of data, or use a Cross-Section task in Quadri to show the illustratory data together with the road model.

12 or 15: Insufficient vertical alignment. Starts before or ends after terrain data.

Answer: The alignment may exist outside of the terrain data and gives error messages related to this.

116 or 118: Left/right road pavement description missing

Answer: Probably road surface thicknesses on this side is set to 'Inherit' thickness. Define a thickness in meters instead.

140: Ref. surf. for vertical alignment missing. Use median line

Answer: The road surface defined to govern the elevation of the road in relation to the alignment elevation does not exist or is with 0.000m width. Road surface defined to set the elevation is marked in the description with **bold** surfacename.\\

To switch to another surface, then right-click the surface to use > Properties > Usage > Ref.surface for vertical geometry.

220: Ditch bottom cannot be linked to road bed

Answer: By default the road bed and pavement is connected to the ditch bottom when not using Detailed Pavement description. If the model only has defined a very narrow ditch, and the side of the road with narrow ditch does not have a road surface with pavement description on it, it may be too tight to be able to establish a roadbed to the ditch.

Add some road surfaces before the ditch or use Detailed Pavement description to define the road bed.

230: Incomplete description of .... / incomplete terrain data

Answer: Model doesn't know if it has enough terrain data because surface group 4, 5, 6 or 7 has insufficient description.

Roadmodel should always have at least one defined surface in each surface group on either side (even if they are limited with boundaries):

270 or 271: Road surface table full, left/right side

Answer: Error is related to internal tables for calculation. This message is normally related to rock stripping in combination with very detailed terrain.

290 or 291: Road bed affects road pavement, left/right side 

Answer: Check the section to find issues with the road bed. The error may be related to the 'Detailed Pavement' description if some of the subsurfaces are not described correctly in these areas, f.ex. missing slope on a subsurface.

372 or 373: Sodding table is full on left/right side

Answer: Error is related to the internal tables for calculation. This message is related to the inner slope that follows terrain gets full. Probably the project has very detailed terrain data, or the fill is large.

Try turning ON 'Design > Settings > Terrain boundaries > Advanced > Simplify terrain cross-sections'.

384 or 385: Landscaping imposs. 1 surf. inside road struct., L/R side 

Answer: Landscaping probably starts by crashing into the road surface, f.ex. starting at the shoulder edge and going out with a slope steeper than the ditch/fill slope. This way the Landscaping function cannot start its design.

604: Line for this surface does not cut the section 

Answer: Alignment used as surface edge does not exist in the specified cross-section.

605: Line for this surface is on the other side of the road

Answer: The alignment as surface edge is located on the other side of the road and tries to use that. If one alignment is detected on both sides of the road this needs to be split into two alignments.

610: Line for this surface is within prev. surface

Answer: An alignment used as surface edge is located closer to the center of the road than the surface where it should be used exists.

Make sure that the alignment used as surface edge is located correctly so that there is room for the surfaces that are supposed to be placed on the inside of it, also when another surface is defined as a 'Free surface'.

626: Reference surface edge line limit not found in this stn.

Answer: Error is related to a road surface used as boundary on either left/right side does not exist in this section. Either they are not defined, the width is set to 0.000m, or they do not exist in this situation (f.ex. a ditch surface not existing in a fill situation).

650: Deep blasting cannot be created when pavement layers are undefined

Answer: The message is related to there being no pavement layers defined for the cross-section. Either all thicknesses are with '0.000' or 'Inherit' thickness, or something similar to this. Add some pavement thicknesses to remove the message.

1501: Step not completed because of errors in the cross-sections 

Answer: Applies when the road cross-section calculation registers errors or serious errors. In these cases the 3D results are not stored/updated (in step 2). Warning is given in the Process Info. To still produce the 3D results turn on 'Ignore errors' in the road task, a checkbox between 'Preview' and 'Finish'.

1502: On average, cross sections have much data. Please check calculation basis and illustration objects

Answer: When the cross-sections for the whole model on average exceeds 1500 objects pr cross section the message will show.

1503: Performance notification: This task has a large number of cross sections (xxxxx). Please review calculation interval.

Answer: The message warns about a large number of cross-sections which may affect performance. Normallyt the reasons are:

1504: Cross section(s) incomplete as they have too much data: Please check calculation basis and illustration objects

Answer: Some data in the cross-section has been discarded because of too much data to handle. Typically this is related to very detailed triangulation of Groundsurface/Subsurface or many features in the cross-section(s). Check the cross-sections mentioned and consider reducing the data to view in the road cross-sections.

If it is necessary to see these data together with the road cross-section we recommend using a Cross-section task inside Quadri for Windows instead.

1505: Calculation not complete, too many sections (> 30000). Last section included is: XXXXX.XXX

Answer: There are more sections to be calculated than our defined limit. Consider to change the calculation interval and turn OFF calculating cross-section for every element change on alignments used as surface edge.

1508: Description has wrong chainage order

Answer: In the Road Surface description the listed road surface (f.ex. surface 1.01) has input in with wrong chainage order.

Step completed with error, code -1

Answer: Cannot connect with the Quadri database.

Step completed with error, code -5

Answer: The road task does not have access to change the result features on the task because of write-protection. This typically could happen when the task tries to delete the old data. Try to Release and Reserve the task again, or Share and Release your data to the Quadri Server, Disconnect Workset, and download a new workset from the Quadri Server. Make sure you are not using OneDrive to store your workset as it sometimes prohibits access.

Step completed with error, code -10

Answer: Cross-setions are not generated from the road model. Cannot make the 3D result model. Error may be related to the message: 'Insufficient vertical alignment. Starts before or ends after terrain data.'

Step completed with error, code -108

Answer: Conversion rules for converting and creating result features does not handle all the data from the road model. Send the log file (CTRL+SHIFT+F12) to support with steps to repeat so we can check what is the problem.

Step completed with error, code -202 

Answer: Read and/or write error to the DMI/DMR files. Check the files that they are present for the project. Try to export the XML indata parameter file from 'Design > Import/Export' on the task and read it back into a new road task to solve the problem.

VipsInterface unknown error -200 

Answer: Probably related to missing or corrupt road model files. Error may occur when the model crashes or there is slowness in the read/write-process with external file servers/Dropbox etc. This is a potential critical situation for the road task and data may get lost if not doing the correct steps. You need to retreive backup files in some way to resolve the issue.

The files you receive must be read into a new road task as the road task with the corrupted files does not work any longer.

Tip: The problem with corrupted/missing files in this way should be solved with Novaoint 2020.FP1, but will not fix already corrupted files. If you experience this issue in NP2020.FP1 or newer versions we would like to hear from you on support!

VipsInterface unknown error -210

Answer: Probably related to some read-only situation where the backup-file of DMI/DMR has problems being created.
Not related to building the roadmodel, but when working with the descriptions or trying to access the files.

200314: Attribute of type genericPropertyList has been removed. Feature (121014/T-161730)

Answer: Roadtask is created in NP2024.4 or newer and you are building the model in an older version. The reason for the message is input in the conversion rule that is not supported in older versions.

400002: Feature has too few points

Answer: The model is creating very narrow or small features in some situations with boundaries to alignments and when limiting the model to the same surface.


A road surface uses an alignment as surface edge. This alignment is also used to limit the road cross-section in 'Boundaries' in road surface description. Since the road cross-section is first building the full section before using the alignment as a limitation of the section there may exist surfaces of near 0m width. As the error message is just a notification to the user that it couldn't make the surface, and the surface is not really requested by the user, then the message can be ignored. User workaround: Limit the road cross-section to the road surface instead of the alignment in these areas.

400025: Coordinate reference system not defined

Answer:The error message can occur after share/receive with the Quadri server. Restart the project to remove the message. There is no issues in continuing working with this message.

400028: Surface edge split into two or more surfaces

Answer: Messages is from Quadri related to storing a surface to the model that had to be split into multiple surfaces before storing. The message can be ignored by the user.

Messages that has not yet been listed with a code

The alignment overlaps itself. The results might be with errors. Please split the road as multiple tasks

Answer: A warning when the roadmodel overlaps itself. In the cases of selfoverlapping cases in relation to bridges or tunnels it is recommended to use multiple roadmodels and to limit the cut/fill volumes by assigning Bridge or Tunnel in the Road Surface boundaries.

If not resolving this message then: