Troubleshooting validation errors

Validation code

Explanation

Resolution

NoServicingExtent

No servicing extent polygon is present in the project. Service AI requires this to be defined.

Add a valid servicing extent polygon to define the area for servicing design.

ServicingExtentNotInSurface

The servicing extent is not fully within the existing surface.

Adjust the servicing extent polygon so it is completely within the surface extent, or increase the size of the existing surface.

OlfpTooCloseToBuilding

The OLFP, or Overland Flow Path, is too close to a building.

Move the OLFP away from building footprints to maintain the required separation.

UnsupportedBaselineType

The corridor baseline is not a valid alignment or feature line, or it is missing or corrupted. Common causes: The baseline alignment was deleted or renamed, or the data shortcut or reference broke. Unsupported geometry is being used in a location that requires an alignment-based workflow, especially around intersections.

1. In Corridor Properties > Baselines, confirm the baseline object is a real alignment, or a valid feature line where applicable, and still exists. 2. If it is missing or broken, reselect the correct alignment or recreate it, then re-add it as a baseline. 3. Recheck the quick checklist, including profiles, regions, and design vertical baselines, then rebuild the corridor. 4. Run Validate Corridor to confirm the corridor meets requirements.

CorridorRegionOverlap

Corridor regions overlap spatially. This often causes bad surfaces, incorrect quantities, and unstable rebuilds. Common causes include overlapping region station ranges after editing or splitting, centerline alignments extending through intersections or beyond cul-de-sac ends, and unused corridor or assembly data remaining in the drawing after objects have been deleted.

1. Locate the review point to identify the overlapping regions. In Corridor Properties > Parameters > Regions, review each region’s Start and End stations, then remove overlaps by adjusting extents or splitting regions cleanly. 2. Confirm centerline alignments are trimmed correctly at dead ends and intersections, with no overrun.

3. If no visible overlap remains but warnings are still being flagged, save a backup copy and run the PURGE command. Review the listed items carefully and remove only unused definitions you recognize; do not purge everything without reviewing it.

4. Rebuild the corridor, then run Validate Corridor.

MissingRegionTarget

A required target, such as an alignment, profile, or feature line, is not assigned for a region. Common causes: Targets were not mapped after a region or assembly was added or changed. Cul-de-sac, knuckle, or intersection targets are not set to the intended centerlines.

1. Open Target Mapping for the corridor or region and assign the missing targets, such as alignments or profiles, as required. 2. If this is an intersection or curb return context, make sure you are following the supported approach. Use offset alignments or curb return alignments; feature lines are not supported for defining curb returns. 3. Rebuild the corridor and validate.

InvalidRegionSubassemblyInsertionPoint

The region’s subassembly insertion point does not match the supported workflow. Common causes: Intersection or curb return assemblies were created with the wrong insertion point. Knuckle or curb type setup is inconsistent, such as mixing Back of Curb and Gutter Edge workflows.

1. Inspect the assembly and confirm the insertion point matches the supported workflow for that feature. 2. For manually created intersections, Allsite.ai recommends using the Civil 3D default “Gutter Edge” insertion point for curb return subassemblies. 3. Rebuild the corridor and validate.

InvalidRegionAssembly

The assigned assembly is invalid for the region because it is unsupported, missing, or not appropriate for that region type. Common causes: A custom combined subassembly is being used. This is not currently supported. The assembly was deleted or renamed, or it contains parts not suitable for that region type.

1. Replace the region’s assembly with a standard, supported assembly. Avoid custom combined subassemblies. 2. Confirm the assembly exists and is assigned to the correct regions.

3. If no visible error remains but warnings are still being flagged, save a backup copy and run the PURGE command. Review the listed items carefully and remove only unused definitions you recognize; do not purge everything without reviewing it.

4. Rebuild the corridor and validate.

InvalidRegionSubassembly

A required subassembly is missing or invalid inside the assembly. Common causes: Curb return assemblies are missing required components, such as a lane subassembly. Subassembly settings or targets were not set after edits.

1. Edit the assembly and confirm all required subassemblies exist and are configured correctly. 2. For curb returns, Allsite.ai requires a lane subassembly. The lane subassembly is used to extend mesh lines toward the target alignment. 3. Rebuild the corridor and validate.

InvalidCulDeSac

The road is marked as a cul-de-sac but does not meet the required geometry or target setup. Common causes: The main road alignment does not start or end at the cul-de-sac center. The cul-de-sac alignment is not set up with the expected station, region, and target relationships. The main road alignment is being used as the cul-de-sac baseline, which is not supported. The alignment type is not centerline alignment.

1. Confirm the cul-de-sac is at a road end and that the main road alignment ties to the center as required. 2. Confirm the cul-de-sac region setup follows the required baseline, region association, and target rules. 3. Make sure the cul-de-sac target is set to the Main Road Alignment and curved to the center. 4. Make sure the alignment is a centerline alignment and not a Curb Return alignment. 5. Rebuild the corridor and validate.

InvalidGeometry

Region geometry is invalid because it contains self-intersections, zero-length geometry, broken links, or other geometry issues. Common causes: Alignment overrun or poor trimming at ends or intersections. Intersections were created before prerequisites were met, such as design profiles and vertical baselines, causing unstable profile or curb-return link behavior. Secondary road profile rules or locked PVIs may be interfering with automated updates.

1. Fix obvious geometry problems first. Trim alignments, remove tiny or zero-length regions, and correct overlaps. 2. Reapply the prerequisites, including EG and Design profiles, regions, and design vertical baselines. Recreate affected intersections if needed. 3. Disable unsupported profile rules and unlock ruled or locked PVIs where applicable. 4. Rebuild the corridor and validate.

UnsupportedTarget

The assigned target type is not supported for this region or subassembly, or the target object is incompatible or broken. Civil 3D and Allsite.ai cannot resolve it reliably. Common causes: The target is the wrong type for Allsite.ai requirements. The target object was deleted or renamed, is an unresolved data shortcut, or is out of date. The issue is in an intersection or curb return context where the workflow expects offset alignments or curb return alignments, not a different geometry type.

1. Open Corridor Properties > Parameters > Targets, or the region target mapping, and identify which target is flagged. 2. Replace it with a supported target for that subassembly. Horizontal targets should use an alignment, typically the correct one for that region, including offset alignments or curb return alignments where applicable. Vertical targets should use the required profile, including EG and Design profiles, and the region should use the intended design setup. 3. If this is near an intersection, cul-de-sac, or knuckle, confirm the setup matches the supported workflow. Trim alignments correctly, use regions, and set design vertical baselines before creating intersections. 4. Rebuild the corridor, then run Allsite > Validate Corridor to confirm the issue is resolved.

NoRoadsInPackage

Level AI Prepare was run, but no corridors or simple roads were detected in the model. In some cases, this can happen because road corridor data could not be extracted from the DWG.

Make sure either road corridors have been created correctly or simple road corridors have been created using Layout Assist.

AlignmentOverrun

The side-road alignment continues past the junction and crosses the mainline at the T-intersection.

Edit the side-road geometry so its end PI meets the mainline, then rebuild the corridors.

MultipleCurbRegions

The curb return alignment has multiple regions. Only one region is supported.

Set the curb return to a single region. Add intersection stations using Region Frequency if needed.

NoCorridorsFound

No corridors or Allsite.ai simple roads were detected in the project. You can run a project without roads, such as a commercial site, if that is intentional.

Follow the project setup steps. There are three supported methods for creating roads.

NoCoordinateSystem

No coordinate system was defined in the DWG. This is required for Allsite.ai to geolocate the project.

Add a coordinate system using MAPCSASSIGN.

NonZeroCenteredSubAssembly

The central subassembly is offset from the assembly origin. This is not supported and may cause minor discrepancies in the resulting levels.

Move the central subassemblies so they are snapped to the assembly origin.

CorridorRegionGap

A gap in the road corridors has been detected. This will affect corridor generation. Ignore this warning if you are using simple road centerlines instead of Civil 3D intersections or knuckles.

Close the gap between regions.

If no visible gap remains but several warnings are still being loaded, save a backup copy and run the PURGE command. Review the listed items carefully and remove only unused definitions you recognize; do not purge everything without reviewing it.

CurbNotAdjacentToLane

A curb subassembly is not adjacent to a lane subassembly. Allsite.ai requires lane subassemblies for data extraction, so this may affect corridor data integrity.

Change to a lane subassembly.

LaneNotAdjacentToCurbGutter

A lane is not adjacent to a curb gutter. Allsite.ai only allows lane subassemblies to be used for vehicle lanes. Lanes are used for data extraction, so this may affect corridor data integrity.

Change any sidewalk subassemblies to appropriate alternatives.

NoLayersCustomSubAssembly

A custom subassembly is in use with geometry that cannot be read.

Replace it with a standard Civil 3D subassembly.

ConditionalSubAssemNotSupported

A conditional subassembly was detected. Conditional subassemblies are not supported in Level AI.

Remove the subassembly.

CurbSubAssemblyNotCentered

A curb subassembly is not centered at its origin. This can cause slight discrepancies in Level AI levels.

Adjust the subassembly so it is centered at its origin.

CustomSubAssembly

A custom subassembly can cause issues with data extraction.

Replace it with a standard Civil 3D subassembly. If custom subassemblies are required, make sure the custom subassembly name includes “Lane” for custom lane subassemblies, “Curb” for custom curb subassemblies, or “Sidewalk” for custom sidewalk subassemblies.

NoCurbSubAssemblyInLibrary

Level AI does not know the curb profile so will default to a basic curb.

If you want a specific curb profile in your model, add the assembly containing the desired sub assembly curb profile. Then run "Fix Schema" and select the Road Modifier polyline and configure the "Type".

​

​

DaylightingNotRequired

A daylighting subassembly was detected. These are not required and are ignored in Level AI runs.

Remove the subassembly.

RdAlignmentHasLoops

The road alignment loops back on itself. This causes issues when using the Civil 3D intersection tool.

Remove any self-intersections or loops from the road alignment geometry.

NoSubassemblyType

Layout Assist has been run, but no subassembly has been assigned to the generated curb modifiers.

Follow the guide here. If an assembly is not already in the model, add one. Then refresh the property data set schema using the “UpdateAllsiteSchema” command. You can then select all curbs using Property Data Select with the “Is outside modifier” attribute set to false.

SurfaceLocationMismatch

The surface data is located far from the expected project location, indicating the coordinate system, or EPSG code, is likely incorrect.

Verify the coordinate system using the MAPCSASSIGN command and confirm it matches your site location using a geolocation basemap.

InvalidSurface

The selected surface is missing, has no triangles, is too dense, or is incorrectly referenced and cannot be processed.

Rebuild the surface in Civil 3D by right-clicking it and selecting Rebuild. Make sure it is correctly selected in project settings and contains valid triangle data.

NoPipesInPackage

No stormwater or wastewater pipe networks were found in the project, which are required to run Service AI.

Make sure pipe networks are created and visible in Civil 3D before running Service AI.

LotGradeNoType

A parcel has a min or max grade specified but no "Parcel Category" assigned. Without a category, LevelAi may grade the parcel incorrectly.

Add a category to the parcel, such as "SINGLE FAMILY".

OlfpNotTouchingRdCenterline

The OLFP does not touch a road centerline and does not touch an impervious polygon.

Make sure the OLFP crosses or touches a road centerline to inform the system of the low point.

RoadCenterpointTooCloseToRetainingWall

The road centerpoint, which is the end of the road corridor region or simple centerline, is within 3 feet of a retaining wall. This can affect the design.

Pull the road region or centerline back from the wall, or shift the wall.

RoadCenterpointTooCloseToBuilding

The road centerpoint, which is the end of the road corridor region or simple centerline, is within 3 feet of a building.

Add a building tie-in, or pull the road region or centerline back from the building.

RdRegionNotInEWExtent

The road region is not within the earthworks extent. This can cause parts of the profile to have zero elevation after a Level AI run.

Adjust the road region geometry so it fits entirely within the earthworks extent.

RdAlignCenterlineNotSnapped

The road alignment centerline is not snapped to another road alignment centerline.

Snap the endpoints of the road alignment centerline to connect with other centerlines as required.

BuildingTooSmall

A building polygon has an area smaller than the minimum threshold of 10 m², or approximately 108 ft², suggesting it is not a valid building footprint.

Remove the building or redraw it with the correct extents.

BuildingOverlap

Two or more building polygons overlap each other, which will cause conflicts in design processing.

Adjust the building footprints so they do not overlap.

BuildingNearEarthworksExtent

A building is within 1 m, or approximately 3 ft, of an earthworks extent boundary, which may cause grading conflicts.

Move the building farther from the earthworks extent boundary, with at least 1 m or 3 ft of clearance.

BuildingOverlapsRoad

A building polygon overlaps a road extent, which is an invalid configuration that will cause design failures.

Move or reshape the building or road extent to eliminate the overlap.

BuildingNearRoadExtent

A building is within 1 m, or approximately 3 ft, of a road extent boundary, which may cause grading conflicts.

Move the building farther from the road extent boundary, with at least 1 m or 3 ft of clearance.

BuildingOverlapsRoadParcel

The building polygon overlaps a road parcel, such as PUBLIC ROAD, JOAL, COAL, or CARPARK.

Adjust the building or parcel geometry to remove the overlap.

BuildingNotWithinParcel

A building is not located within any parcel, meaning it cannot be assigned to a lot for servicing and design.

Make sure the building is placed within a valid parcel boundary, or add or adjust parcels to cover the building.

BuildingTooManyPoints

A building polygon has an unusually high number of vertices relative to its area, where area/point_count < 4 and point_count > 16. This may indicate bad geometry conversion from a DWG or another CAD format.

Simplify the building geometry to reduce the vertex count while maintaining the correct shape. Remove or simplify curved building lines.

TieInNotTouching

The building tie-in does not touch the building boundary or road centerline.

Make sure the tie-in line connects to both the building boundary and the road centerline.

RdCenterlineHasLoops

The processed road centerline has loops in its geometry. This can cause issues for Level AI.

Remove any self-intersections or loops from the simple road centerline geometry at intersections.

RdCenterlineNotInRoadExtent

The road cenRdCenterlineGapterline is not within the associated road extent.

Adjust the centerline geometry so it is contained within the road extent polygon.

RdCenterlineNotSnapped

The road centerline is not snapped to another centerline or required feature.

Snap the centerline endpoints to the appropriate features.

MultipleRdCenterlinesOverNormalLot

Two or more separate road centrelines each run a substantial distance (more than 10 m / 32.8 ft) through the same NORMAL parcel. A lot carrying several roads usually means a road layout from a different design has been overlaid on the parcels. This is fatal and blocks the run.

Check for a duplicate or superseded road layout and remove it. Otherwise adjust the centrelines or the parcel boundary so at most one road crosses the lot, or retype the parcel as a road parcel.

RdCenterlineThroughMultipleNormalLots

One road centreline runs a substantial distance (more than 10 m / 32.8 ft) through three or more NORMAL parcels. A road slicing through a run of residential lots means the alignment does not match the parcel layout. This is fatal and blocks the run; every crossed lot is flagged.

Move the road centreline into its road reserve, or correct the parcel boundaries it crosses. If the road genuinely replaces those lots, retype them as road parcels.

ShortCenterline

A road centreline is shorter than the minimum supported length. A very short centreline carries too little chainage to hold a meaningful profile, and is usually a fragment left by a split.

Delete the fragment, or merge it into the adjoining centreline so the road is described by one continuous line.

RoadCenterlineGap

Two road centrelines that should join are separated by more than the gap tolerance. The road network is broken at that point, so levels do not carry across the junction.

Snap the centreline endpoints together so they meet exactly, then run again.

BadEdge

A polygon edge has a sharp angle, which can cause issues with a Level AI run. Features analyzed for bad edges include the Earthworks Extent and Corridor Extent, which is a processed polygon from a Civil 3D corridor.

Remove any vertices causing sharp angles in the geometry.

CenterlineCrossesMultipleRdExtents

A road centreline passes through more than one road extent. The centreline carries one profile, so it cannot drive two separately graded extents.

Split the centreline at the extent boundaries so each part drives one extent, or merge the extents into one.

AngleOnPublicRoad

A road centreline turns through a very sharp angle. A deflection under about 15 degrees is not drivable, and any sharp angle on a public road should be an arc rather than a kink.

Replace the angular corner with a curve of an appropriate radius. If the sharp angle is real, check the corridor was drawn correctly at that point.

CenterlineOverlap

Road centerlines overlap each other.

Adjust the geometries to remove overlaps.

ParallelCenterline

Road centerlines are too close together and nearly parallel.

Increase the separation between parallel centerlines.

ParcelOverlap

Lots or parcels overlap each other. This can happen when parcels from an old layout are still present in the project.

Adjust lot boundaries to eliminate overlaps, or delete old parcels from a previous design.

NormalLotOverRdExtent

A NORMAL category lot overlaps the road corridor by a significant amount. This can cause undesired behavior.

Reduce the size of the road corridor or shift the parcel boundaries. If the parcel is not meant to be a NORMAL category lot, change it to another category, such as DRIVEWAY or ROAD.

NoParcelCategory

The parcel does not have a category assigned. This can lead to undesired Level AI grading. This is a fatal warning if less than 10% of the lots are NORMAL category lots.

Add a category to the parcel, such as "NORMAL" or "PUBLIC DRAINAGE". For NORMAL category lots you can set the sub type to SINGLE FAMILY typology (e.g. TYPE A).

NormalLotSubTypeSize

A NORMAL lot with a “Normal lot sub type” is very large. This can cause issues because it may add extra drainage lines. This setting is intended for residential lots only.

Remove the normal lot subtype by setting it to “None,” or change the lot to a different category, such as public drainage or public park.

Road parcel (singlepart geometry)

Road parcel geometry is multipart but must be singlepart.

Split multipart geometries into singlepart features.

Building (singlepart geometry)

Building geometry is multipart but must be singlepart.

Split multipart geometries into singlepart features.

OLFP (singlepart geometry)

OLFP geometry is multipart but must be singlepart.

Split multipart geometries into singlepart features.

Retaining Wall (singlepart geometry)

Retaining wall geometry is multipart but must be singlepart.

Split multipart geometries into singlepart features.

RWNotInEWExtent

The retaining wall is not within the earthworks extent.

Adjust the retaining wall geometry to fit within the earthworks extent.

RetainingWallOverlap

Two retaining walls overlap. Each wall sets its own height offsets, so along the overlap the ground has two competing retained levels.

Trim one wall so they abut end to end rather than overlapping, or delete the duplicate if both describe the same wall.

RWUnderBuilding

Retaining wall overlaps a building. It is OK for a wall to run exactly along a wall, but not under it.

Ensure the wall is exactly snapped to the building edge.

NotSnappingEwEx

The retaining wall is not snapped to the earthworks extent.

Snap the wall endpoints to the earthworks extent boundary.

WallAngleVeryAcute

The retaining wall has angles that are too sharp and may result in bad triangulation

Adjust the wall geometry to smooth out sharp angles.

WallTooClose

Two retaining wall segments sit on top of each other, below the minimum separation. Their retained levels overlap, so neither wall gets the height it was designed for.

Move the segments apart beyond the minimum distance in the message, or delete the duplicate segment.

WallMaxHeightStep

Two connected retaining walls have significantly different maximum design heights. Because Level AI blends design heights across the shared join, the lower wall can end up taller than its declared max height near the interface.

Confirm the maximum heights are correct, then lower the height difference or move the join.

NoRoadExtents

No road extents were detected in the processed data. This usually means road data extraction from the Civil 3D model was unsuccessful or had issues.

If you are using corridors, corridor extraction may have failed. Check corridor review points for gaps or overlaps. If you are using simple roads, check the modifiers, confirm Layout Assist ran successfully, and confirm all modifiers have extended data assigned to them. If you are using manually drawn modifiers in intersections, make sure “Outside road edge” is set to true.

RoadExtentOverlap

The road extent overlaps another road extent.

Adjust road extent polygons to remove overlaps.

RoadExtentTooSmall

The road extent area is too small.

Increase the area of the road extent polygon.

PondInvertTooLowOrHigh

The pond invert is not within 65 ft of the existing ground.

Adjust the pond invert so it is closer to the existing ground level.

PondRoadClose

The pond is close to a road corridor or road parcel. If the pond is large, this can cause grading issues because the pond lip must be flat.

Provide space between the pond and road, or add a grade break between the pond and road.

PondRoadOverlap

The pond overlaps a road corridor or road parcel.

Adjust the pond lip so there is enough gap for grading between the road and the pond edge.

NoPondOutlet

No Civil 3D storm structure with a TYPE of OUTLET is defined on the same subnet as the pond.

The default subnet (out) for ponds is subnet “1.” There must be a storm structure with TYPE = OUTLET for the pond, with subnet (in) set to “2.”

RoadWidth

The road extent width does not meet minimum requirements.

Adjust the road extent geometry to meet width requirements.

RdExtentOutEwExtent

A road extent falls outside the earthworks extent. Grading only happens inside the earthworks extent, so the part of the road outside it is never designed.

Extend the earthworks extent to cover the road, or pull the road extent back inside it.

LongRdExtentCloseBuilding

A road extent is very close to a building. This can cause model viability issues.

Add a building tie-in along the edge of the building and snap the corridor or centerline to it.

Building (overlapping shapes)

A building overlaps another building.

Adjust building polygons to remove overlaps.

Building (too small)

The building area is too small.

Increase the area of the building polygon.

Lot (too small)

The lot area is too small.

Increase the area of the lot polygon.

Lot (singlepart geometry)

Lot geometry is multipart but must be singlepart.

Split multipart geometries into singlepart features.

Earthworks (overlapping shapes)

Earthworks extents overlap each other.

Adjust earthworks polygons to remove overlaps.

Earthworks (sliver)

The earthworks extent has slivers or holes.

Clean up the geometry to remove slivers and fill holes.

Earthworks (bad edges)

The earthworks extent has bad edges or sharp angles.

Smooth or adjust the geometry to remove bad edges.

Earthworks (fields)

The earthworks extent is missing required attribute fields.

Add or correct the required fields in the attribute table.

RelationshipEndPointsTooClose

Relationship endpoints are too close to each other.

Increase the separation between relationship endpoints.

RelationshipLoops

There are loops in the relationship network.

Remove or correct the relationships to eliminate loops.

LinkDownstreamElevation

A pipe link’s downstream invert level is not within the threshold of the TIN surface elevation at the downstream node. When this happens, the link is ignored from analysis.

Update the downstream invert level so it is within the threshold of the TIN surface elevation at the downstream node.

LinkUpstreamElevation

The pipe does not have an upstream elevation set within approximately 60 ft, or 20 m, of the existing surface. If servicing is enabled, this can create constraints on the Level AI model.

Update the lid level.

StructureLidLevel

The structure does not have a lid or invert level set within approximately 60 ft, or 20 m, of the existing surface. If servicing is enabled, this can create constraints on the Level AI model.

If it is a headwall, update the level on the pipe end connected to it. If it is a manhole, go to Structure Properties, and change the manhole's level.

StructureInvertLevel

The structure does not have a lid or invert level set within approximately 60 ft, or 20 m, of the existing surface. If servicing is enabled, this can create constraints on the Level AI model.

Update the lid or invert level.

InvertAtOrAboveLid

A structure's invert is at or above its lid level. The structure has zero or negative depth, which cannot be built, so it is left out of the analysis.

Correct the invert or the lid so the invert sits below the lid by at least the structure's minimum depth. Check the two levels have not been swapped.

InvertLessThanMinCover

A structure's invert is above the deepest invert that still leaves minimum cover over the pipes entering it. The connections would run too shallow, so the structure is left out of the analysis.

Lower the structure's invert below the maximum invert stated in the message, or reduce the minimum cover requirement if your standards allow it.

InvertAboveGround

The structure sump is not below the ground level.

Adjust the sump level.

NoOLFPInProject

No OLFP exists in a large project area. For large projects, this is considered fatal and is likely an omission from the design. For small projects, it is a low-level warning.

Add an OLFP feature to a road in the project. It should cross a road centerline and the earthworks extent or another road centerline.

OLFPDitchConnectivity

Overland flow path ditches must cross the earthworks extent to activate.

Extend the OLFP ditch.

OLFPConnectivity

Overland flow paths only activate when they cross a road centerline or impervious polygon and cross at least one of the following: another road centerline, when the OLFP connects two roads; the earthworks extent boundary of the site; or another OLFP.

Extend the OLFP.

NearEwBoundaryNoOlfp

The end of a road or cul-de-sac is not connected to a building tie-in and has no OLFP. Ignore this warning if the location is not intended to be a low point.

Add an OLFP feature to a road in the project. It should cross a road centerline and the earthworks extent or another road centerline.

LinkUpstreamMinCover

Triggers when a link's upstream elevation is too close to (or above) the ground surface at that point.

The distance threshold comes from the project's Services settings. The link needs its upstream invert lowered to at least the smaller of the two configured covers, below the surface.

SaiPipeFamilyTooFewSizes

The pipe family selected for a Service AI network does not contain enough pipe sizes for the design. Service AI chooses a diameter for each pipe run from the sizes available in the selected family's parts list, so it needs a reasonable range. Storm networks require at least 7 sizes; sanitary networks require at least 4.

1. Open Service AI settings and check the selected pipe family for the storm and/or sanitary network (or use the Set Storm/Sanitary Network Families link in the run confirmation popup). 2. In Civil 3D, open the parts list assigned to that network and add more sizes to the selected pipe family (Storm: at least 7, Sanitary: at least 4). 3. Re-open the Service AI Prepare or Run popup to confirm the sizes list correctly, then re-run.

SaiPipeFamilySmallestSizeTooLarge

The smallest available size in the selected pipe family is larger than recommended, so Service AI cannot place small-diameter pipes where the design needs them. The selected family should include a size of 9 in (approximately 229 mm) or smaller for storm, and 6 in (approximately 152 mm) or smaller for sanitary.

1. In Civil 3D, open the parts list assigned to the storm or sanitary network and find the selected pipe family. 2. Add a smaller pipe size (Storm: 9 in / 229 mm or smaller; Sanitary: 6 in / 152 mm or smaller). 3. Re-open the Service AI popup to confirm the smallest size is now within range, then re-run.

SaiPartCreateFailed

Service AI could not create one or more pipes or structures in the Civil 3D pipe network when loading results. Civil 3D builds each part from the selected family in the network's parts list, so the most common cause is a corrupt or unavailable pipe-network part library / parts list (the part size/family can't be resolved), or a missing part catalog.

1. Confirm the storm/sanitary network has a valid parts list assigned that contains the pipe and structure families used.

2. Verify the Civil 3D part catalog is installed and not corrupt — re-point or repair/reinstall it if parts won't resolve.

3. Verify you can manually create a pipe/structure in the DWG.

4. Reload the parts list into the drawing, then re-run Service AI results.

5. Check the event log for the specific failed part IDs.

RoadProcessingError

The road/corridor processing step could not complete. This usually has one of two root causes: (a) corridor geometry that doesn't meet Allsite's requirements (baselines/alignments not connecting cleanly, region gaps or overlaps, unresolved targets, or incorrectly built intersections); or (b) missing property datasets or an outdated Allsite schema on the road objects — common when the drawing was made with an older plugin version, objects were copied in from another drawing, or the schema was never fully applied.

a. In the Allsite ribbon panel, click Fix Schema to repair and update the Allsite schema definitions and property datasets in the current drawing, then re-run. This resolves the error when the cause is a missing or outdated schema.

b. If the error persists, the corridor geometry does not meet requirements. Review your corridor against the relevant guide: Creating Roading Network (full corridors) (https://support.allsite.ai/en/articles/12495402-creating-roading-network-full-corridors) or Creating Roading Network (basic corridors, no intersections) (https://support.allsite.ai/en/articles/13746970-creating-roading-network-basic-corridors-no-intersections).

c. Confirm baselines connect correctly, regions have no gaps or overlaps, targets resolve, and (for full corridors) intersections are built per the guide.

d. Correct any issues and re-run.

WallSlightNotSnapping

A grade break is not snapped, this will be auto-snapped.

Nothing required, but confirm that this is the desired behaviour. if you desire a gap, separate grade break ends by at least 4 ft.

WallNotSnapping

A grade break is not snapped, this will NOT be auto corrected

If the gap is not intended, redraw with the walls snapped.

WallAngleAcute

A grade break has a relatively steep angle and may triangulate poorly and/or be difficult to construct.

Smooth the angles by adding extra vertices.

AlignmentLoop

An alignment crosses or doubles back on itself. A self-intersecting alignment has two stations at the same point, so stationing is ambiguous and anything measured along it — regions, offsets, profiles — becomes undefined.

Open the alignment in the Geometry Editor and find the crossing. It is usually a curve radius too large for the tangents either side, or a PI dragged past its neighbour. Reduce the radius or move the PI so the alignment runs monotonically, then rebuild the corridor.

AssemblyValidationError

The assembly checks could not be run. The check itself failed rather than finding a problem, so the assemblies are unverified — the run does not know whether they are valid or not.

Read the reason in the message. Run AUDIT on the drawing and rebuild the corridors, which clears most cases. If it persists, send the Allsite log for the run to support — an unverified assembly is not the same as a valid one.

CorridorExtractionFailed

A corridor opened, but reading its contents threw an error. The object itself is not damaged — the failure happened while walking its baselines and regions — so rebuilding is not the fix. The reason is carried in the message text.

Read the reason in the message and address that. If it names a specific baseline or region, check that part of the corridor first.

CorridorNotExtracted

A corridor in the drawing could not be opened, so nothing was extracted from it. The object failed to open for reading — usually because it is erased or damaged. It is present in the drawing but absent from the uploaded package, which would otherwise be smaller with no indication why.

Rebuild the corridor, or delete and recreate it if rebuilding fails. If it is no longer needed, remove it from the drawing so the package and the drawing agree.

CorridorValidationError

The corridor checks could not be run. The check itself failed rather than finding a problem, so the corridors are unverified.

Read the reason in the message. Rebuild the corridors and run AUDIT on the drawing, then try again. If it persists, send the Allsite log for the run to support.

LaneSubAssemblyRequired

A corridor region's assembly contains no lane subassembly. The lane defines the carriageway — its width, crossfall and pavement edge. Without one, Allsite cannot determine where the road surface is, so the region produces no usable road.

Open the assembly (Corridor Properties > Parameters shows which assembly the region uses), add a lane subassembly such as LaneOutsideSuper or LaneSuperelevationAOR to each side, then rebuild the corridor.

NetworksError

Pipe network processing failed. The run stopped while reading or building the networks. The message carries the underlying reason.

Read the reason in the message. Check the networks open cleanly in Civil 3D — an AUDIT on the drawing, then a rebuild of the networks, clears most cases. If it persists, send the Allsite log for the run to support.

NoDataExtracted

Extraction produced no data at all. Nothing in the drawing was recognised as Allsite data. Usually the drawing was never converted — Civil 3D objects have to be tagged as Allsite features before they are visible to a run.

Select the roads, lots, extents and surfaces and run Convert from the Allsite ribbon so they carry Allsite property data, then run Prepare again. If the drawing was converted previously, run Resync Project — the link may have been lost.

NoEarthworksExtentInPackage

The extracted package contains no earthworks extent. The earthworks extent is the boundary the design grades within. Without it the run has no scope and cannot tell where earthworks should stop.

Draw a closed polyline around the area to be graded and convert it to the Allsite earthworks extent, then run Prepare again. It must be a single closed loop with no self-intersections, and should sit inside the existing surface by at least a couple of cell widths.

NoParcelsFound

The drawing contains no parcels. The lots have not been created as Civil 3D parcels, so there is no lot topology to read — boundaries, areas and frontages all come from it.

Select the closed lot boundaries and create parcels from them (Home > Parcel > Create Parcel from Objects), then convert them to Allsite parcels and run again.

NoParcelsInPackage

The extracted package contains no parcels. Parcels are how the design knows what it is servicing and grading to. None reached the package, either because none are tagged as Allsite parcels or because they fall outside the earthworks extent and were clipped out.

Check the lots are converted to Allsite parcels and that the earthworks extent encloses them, then run Prepare again.

NoReferencedSubAssembly

A subassembly has no shape layers — the custom subassembly it refers to is not available here. A custom subassembly (.pkt or a subassembly composer part) carries its shapes with it. Opened on a machine without that part imported, the subassembly resolves to nothing and the corridor builds an empty cross-section at that point.

Import the custom subassembly into this drawing (Insert > Import Subassemblies, select the .pkt), or replace it with the equivalent stock Civil 3D subassembly, then rebuild the corridor.

NoRoadAlignmentsInPackage

The extracted package contains no road alignments. Roads are extracted against their baseline alignments. With none in the package there is no centreline to hang stationing, profiles or widths off.

Check the corridor baselines use alignments (not feature lines) and that those alignments are converted as Allsite road alignments, then run Prepare again.

NoSitesFound

The drawing contains no sites. Civil 3D groups parcels and alignments into sites. With no site defined, the parcel topology Allsite reads does not exist.

Create a site in Toolspace > Prospector > Sites and move the parcels into it, then run again. Parcels created from closed polylines land in a site automatically, so this usually means the lots are still plain polylines.

NoSurfacesFound

The drawing contains no surfaces. The design needs an existing ground surface to grade from — it is the datum for cut and fill.

Create or data-reference the existing ground TIN surface into this drawing (Home > Surfaces > Create Surface, or attach the survey data shortcut), assign it as the existing surface in the Allsite project settings, then run again.

ProposedSurfaceMatchesExisting

The proposed surface is the same as the existing surface. The design would be grading to the ground it started from, so every cut and fill volume would be zero and the result meaningless. Almost always the same surface has been selected twice in the project settings.

Open the Allsite project settings and select the correct proposed (design) surface, distinct from the existing ground surface. If a proposed surface does not exist yet, create one before running.

SaiInvalidPartsList

The network's parts list is missing, empty, or has no usable part families. Every pipe and structure Service AI creates comes from the network's parts list. Without a usable one nothing can be built.

Open Toolspace > Settings > Pipe Network > Parts Lists and check the list assigned to the network has part families under both Pipes and Structures. Assign a populated parts list to the network (Pipe Network Properties > Parts List) and run again.

SaiMissingSchema

A feature class Service AI needs has no schema definition in this drawing. Allsite stores its data against a schema attached to the drawing. A missing one usually means the drawing was never initialised as an Allsite project, or was created against an older schema.

Run Initialise Project on the drawing to attach the current schema. If the drawing is already linked, use Resync Project to refresh it.

SaiNetworkNotFound

The pipe network named in the project settings is not in this drawing. The selection is stored by name. Renaming, deleting, or opening a different drawing from the one the project was set up in all leave the setting pointing at nothing.

Re-select the network on the Service AI ribbon panel. If you renamed it, either rename it back or pick it again under its new name so the setting is rewritten.

SaiNoNetworkSelected

Service AI was started without a pipe network selected. Service AI designs into an existing Civil 3D pipe network — it needs to know which one before it can place anything.

Select the Storm and Sanitary networks on the Service AI ribbon panel, then start the run again. If the drawing has no pipe networks yet, create one (Home > Pipe Network > Pipe Network Creation Tools) with the parts list you intend to use.

SaiPipeFamilyNotUsable

The selected pipe family cannot be used for this design. The family is present but unusable — commonly no sizes are enabled in this parts list, or the shape/material combination has no valid size records.

In the parts list, open the pipe family and confirm at least one size is enabled with valid dimensions. If it is a specialist part, select a standard circular pipe family for the network instead.

SaiStructureFamilyNotUsable

The selected structure family cannot be used for this design. The family is present but unusable — commonly it has no sizes enabled in this parts list, or it is a domain that does not accept the connections the design needs.

In the parts list, open the structure family and confirm at least one size is enabled and its dimensions are valid. If the family is a specialist part (an inlet with no through-connection, for example), select a standard manhole family for the network instead.

SaiStructurePartFamilyMissing

Structures of a type could not be created because the network's parts list contains no part family for that type. Service AI designs a structure for every node it places, then asks Civil 3D to build it from the network's parts list. The pre-pass resolves each stored TYPE to candidate part families; a type that resolves to none cannot be built at all, so every structure of that type is absent from the drawing — and pipes and catchments that referenced them lose their links too.

Open the network's parts list (Civil 3D: Toolspace > Settings > Pipe Network > Parts Lists), add a part family for the reported type under Structures, then run Service AI Results again. If the family exists under a different name, map the type to it in the network's structure settings instead.

SaiStructurePartSizeMissing

A part family matched the structure type, but no size within it fits the dimensions the design asked for. The family was found, so this is not a missing-family problem. Every size in that family was checked against the requested dimensions and none was usable, so nothing of that type was created.

In the parts list, open the reported part family and add a size covering the dimensions in the message, or widen an existing size's range to include them. Then run Service AI Results again.

SaiStructuresNotCreated

No structures at all were created for one or more types, and no more specific cause was identified. Every structure of the listed types failed. A whole type failing is the signature of a parts-list gap rather than a problem with individual nodes, but the import could not narrow it to a missing family or a missing size.

Check that the network's parts list has both a part family and a matching size for each type listed. Confirm the parts list is the one the network is actually using, then run Service AI Results again.

SchemaFixRequired

Property data on one or more objects does not match the current schema. Allsite stores its attributes in Civil 3D property sets defined by a schema. Objects converted under an older schema can carry fields that no longer exist, or be missing ones now required, and extraction cannot read them reliably.

Run the schema fix offered with this message, or Resync Project to bring the drawing onto the current schema, then run again. Re-converting the affected objects also works if the fix does not clear it.

UnexpectedError

A run failed without producing any specific review items. The catch-all for a crash that happened before the validations could report anything of their own. The message carries whatever detail was available at the point of failure.

Read the message for the underlying error. If it recurs, send the Allsite log for the run to support — this code means the failure was not one the plugin recognised, so the log is the only record of it.

CenterlineProfileNotStatic

The centreline is driven by a dynamic profile where a design profile is required. A dynamic profile follows something else — a surface, or another profile. The centreline is the design intent Allsite is asked to honour and then adjust, so it must be a profile you own, not one that moves when its source does.

Create a layout (design) profile for the centreline in Profile View (Profile > Profile Creation Tools), assign it as the corridor baseline profile in Corridor Properties > Parameters, then rebuild.

CorridorOutOfDate

A corridor's definition has changed since it was last rebuilt, so its regions no longer match the drawing. Civil 3D marks a corridor out of date when an assembly, profile or target it depends on is edited without a rebuild. The checks and the extracted package both read the corridor as it currently stands, so a stale corridor produces a package describing roads the drawing no longer has, with nothing to distinguish it from a correct one.

Rebuild the corridor in Civil 3D (right-click the corridor > Rebuild), then re-run. Rebuilding is not done automatically because it is slow and modifies the drawing during what is meant to be a read-only check.

CurbReturnProfileNotDynamic

A curb return profile is static where a dynamic profile is required. Curb return levels are derived from the two roads they join. A static profile keeps its original levels, so once either road's profile moves the return no longer meets them.

Delete the static profile and recreate it with Create Curb Return Profile so it stays tied to both intersecting roads, then rebuild the corridor.

InvalidBoulevardAssembly

A boulevard assembly is not built the way Allsite expects. A boulevard carries a verge or median whose levels Allsite has to derive from the lane and kerb either side. An unexpected arrangement means it cannot work out which part is carriageway and which is verge.

Rebuild the assembly in the expected order — lane, curb/gutter, then the boulevard/verge subassembly outside it — or split the road into separate regions where the treatment changes. Then rebuild the corridor.

ObjectsNotReadable

One or more objects in the drawing could not be opened and were skipped. Raised by read-only checks, where a skipped object makes the report incomplete but nothing is being written. Most of model space is not Allsite data, so an unreadable object is not automatically a problem.

Check whether the listed objects matter to the design. If they do, rebuild or recreate them; if they are unrelated drawing content, this can be ignored.

OffsetProfileNotDynamic

An offset profile is static where a dynamic profile is required. Offset profiles are meant to follow the centreline as it changes. A static one holds its levels, so when Allsite adjusts the centreline the offset no longer relates to it and the crossfall is wrong.

Delete the static offset profile and recreate it with Create Offset Profile (Profile > Create Offset Profile) so it stays linked to the centreline, then rebuild the corridor.

ProposedSurfaceLooksExisting

The proposed surface closely resembles the existing surface. Not identical, but near enough that it looks like existing ground rather than a design — commonly a copy of the existing surface that was never graded, or the wrong surface selected.

Confirm the proposed surface selected in the project settings is the design surface. If it is correct and the site genuinely needs little earthworks, this can be accepted as-is.

SaiCatchmentNotLinked

Catchments were imported but could not be linked to their downstream node. The node a catchment drains to is missing from the drawing — almost always because it is one of the structures that failed to import for the same network. The catchment geometry is correct; only the link is missing.

Resolve the structure import errors for the same network first, then re-import. The links are restored automatically once the nodes exist; they do not need to be reconnected by hand.

SaiImportReported

A problem was reported during the import that has no more specific code. This names the channel the message arrived on, not what went wrong: it is applied to text raised through Civil 3D's Panorama that did not come through the structured import result. It therefore cannot carry resolution steps, and a problem appearing under it is a sign the raising code should be giving it a real code instead.

Read the message text itself — it is passed through unchanged from whatever raised it. If this code appears often for the same underlying problem, that problem needs its own code adding to ValidationCode and this catalogue.

SaiNoExistingNodes

The selected network contains no existing structures to design from. Service AI extends and connects to what is already there. An empty network gives it no outfall, no connection point and no existing levels to honour.

Add the existing structures — at minimum the outfall or connection point to the public system — to the network before running. If the network really is greenfield, confirm the servicing extent and connection point are set so the design has somewhere to drain to.

SaiStructureFamilyLargestSizeTooSmall

The largest available structure is smaller than the design needs. A structure has to be wide enough for the pipes entering it. Where the largest size in the family is too small, those structures cannot be built correctly.

Add larger sizes to the structure family in the parts list, or select a family that includes them. Check the largest size against the biggest pipe diameter in the design plus the wall thickness and connection clearances your standards require.

SaiStructureFamilyTooFewSizes

The selected structure family offers too few sizes for the design to choose sensibly. Structure size follows the pipes entering it and the depth. A family with one size forces every structure to it, whether or not the connecting pipes fit.

In the parts list, add the range of structure sizes your standards allow to the selected family (Parts List > Structures > Edit Parts List). Make sure the range covers the largest pipe diameter you expect to connect.

SaiStructurePartFamilySubstituted

Structures were created from a different part family than the one configured, because none of the configured families were usable. When the configured families cannot be used, the import falls back to the first available structure family in the parts list rather than dropping the structures. They exist and are connected, but they are the wrong part.

Check the network's part family setting for the reported type. Either correct it to a family that exists in the parts list, or add the configured family to the parts list, then re-import to replace the substituted structures.

VaryingAssemblyVerticalOffset

A road's corridor regions use assemblies with differing vertical (PGL) offsets. The offset is a property of the assembly — how far its centerline subassembly sits above or below the baseline marker. A profile is a single curve, so it can only be shifted by one value; where regions disagree, shifting by one region's offset leaves the others off their design elevation.

Make the regions agree — set the same vertical offset on the assemblies used along the road. Do not simply remove the offset: a uniform non-zero offset is compensated automatically and needs no action.

RegionOverlap

A corridor region overlaps another region's geometry. Two road surfaces occupy the same ground, so levels and widths at that location are ambiguous and the extracted road is unreliable.

Open Corridor Properties > Parameters and adjust the station ranges of the overlapping regions so they abut. Where two roads meet, model the junction with a curb return region rather than overlapping straight-road regions.

NoSolidServicingExtent

Every servicing extent in the project is marked as a hole. Holes subtract area from a solid extent, so with no solid extent to subtract from there is no servicing area at all.

Clear the hole flag on the extent that defines the serviced area, or draw a solid servicing extent enclosing the holes, then run again.

ServicingHoleOutsideExtent

A servicing extent marked as a hole does not sit fully inside a solid servicing extent. The part hanging outside subtracts from nothing, so the resulting servicing area is not what the hole was drawn to describe.

Move or reshape the hole so it lies entirely within a solid servicing extent, or extend the solid extent to cover it.

NoEwExtents

No earthworks extents were found in the project. The earthworks extent is the boundary the design grades within; without it the run has no scope.

Draw a closed polyline around the area to be graded and convert it to the Allsite earthworks extent, then run again. It should sit inside the existing surface by at least a couple of cell widths.

NoSolidEwExtent

Every earthworks extent in the project is marked as a hole. Holes subtract from a solid extent, so with no solid extent there is no area to grade.

Clear the hole flag on the extent that defines the graded area, or draw a solid earthworks extent enclosing the holes, then run again.

EwHoleOutsideExtent

An earthworks extent marked as a hole does not sit fully inside a solid earthworks extent. The part outside subtracts from nothing, so the graded area is not what the hole was drawn to describe.

Move or reshape the hole so it lies entirely within a solid earthworks extent, or extend the solid extent to cover it.

EwExtentOverlap

Two earthworks extents overlap. The overlap belongs to both, so the design has two competing definitions of what should be graded there and the boundary is ambiguous.

Edit the extents so they abut rather than overlap, or merge them into a single polygon. Use holes rather than overlapping solids where an area should be excluded.

EwExtentOutsideSurfaceWithTol

The earthworks extent extends beyond the existing ground surface (TIN). Cut and fill are measured against the surface, so any part of the extent outside it has no datum to grade from.

Extend the existing surface to cover the extent, or pull the extent back inside the surface boundary by at least a couple of cell widths, then run again.

EwExGap

A gap or slither of less than 10 square metres was found between two earthworks extents. It is too small to be intentional and would leave an ungraded sliver, so it is closed automatically during processing.

No action needed - the gap is auto-corrected. Snap the extents together if you want the drawing to match the processed result exactly.

EWStageContiguity

The earthworks stage numbers are not contiguous - a stage in the sequence has no extent assigned to it. Staging is processed in order, so a missing stage breaks the sequence and the later stages cannot be tied to the earlier ones.

Check the stage attribute on every earthworks extent and renumber them so the stages run consecutively from 1 with no gaps, then run again.

OlfpNearOlfp

Two overland flow path ditches run too close together. Their graded sections would overlap, so neither ditch ends up with the cross-section it was designed to have.

Move one OLFP so the separation exceeds the tolerance in the message, or delete the redundant one if both are draining the same area.

OlfpBoundaryZOverrideBothEnds

An overland flow path has a boundary Z override set at both ends. The override fixes the level where the OLFP crosses the earthworks boundary; setting it at both ends fixes the grade along the whole path and leaves the design nothing to solve.

Keep the override on the end where the tie-in level is known - usually the outfall - and clear it on the other end so the design can grade to it.

OlfpBoundaryZOverrideNoExtentConnection

An overland flow path has a boundary Z override but does not connect to the earthworks extent boundary. The override only applies where the path crosses the boundary, so with no crossing it has no effect.

Extend the OLFP so it crosses the earthworks extent boundary, or clear the boundary Z override if the path is not meant to discharge there.

OlfpStartZOverrideValue

The START_Z_OVRIDE attribute on an overland flow path holds a value that is not a finite number. It cannot be used as a level, so the override is ignored and the path is graded from existing ground instead.

Open the OLFP's attributes and set START_Z_OVRIDE to a valid elevation, or clear the field entirely if no override is intended.

OlfpStartZOverrideBoundary

An overland flow path has a start Z override at a location where a boundary override applies instead. The two overrides describe the same tie-in level in different ways and only one is used.

Use the boundary Z override where the path crosses the earthworks extent, and clear START_Z_OVRIDE, so the tie-in level is described once.

OlfpBoundaryZOverrideConflict

Two or more overland flow paths crossing the earthworks boundary at the same point specify different boundary Z override levels. Only one level can exist at that point, so the design cannot honour them all.

Set the same override level on every OLFP at the shared crossing, or clear the override on all but one of them.

OlfpStartZOverrideSurfaceDelta

An overland flow path's START_Z_OVRIDE differs from existing ground by more than the allowed delta. The override is still honoured, but a large difference usually means it was entered in the wrong datum or against the wrong surface.

Check the override elevation against existing ground at that point. Correct it if it was entered in error; if the difference is deliberate, no action is needed - the value is used as given.

OLFPDistAlongRd

An overland flow path runs along a road centreline for more than the permitted distance. An OLFP is meant to cross a road to define its low point, not run down it - a long overlap means the road profile and the flow path are competing to set the same levels.

Reroute the OLFP so it crosses the road rather than running along it, or shorten the overlapping section below the distance in the message.

RdCenterlineCrossesBuilding

A road centreline passes through a building footprint. The road and the building cannot both occupy that ground, and the road profile would be graded straight through the platform.

Move the road centreline clear of the building, or move or delete the building. Check the building was not placed over an old centreline alignment.

BuildingInvalidSlabThickness

A building's slab thickness attribute is negative. Slab thickness is subtracted from the platform level, so a negative value raises the platform instead of lowering it.

Open the building's attributes and set SLAB_THICK to a positive value in metres, or clear it to use the project default.

BuildingInvalidSubbaseThickness

A building's subbase thickness attribute is negative. The subbase is subtracted below the slab, so a negative value moves the formation level the wrong way.

Open the building's attributes and set SUBBASE_THICK to a positive value in metres, or clear it to use the project default.

BuildingInvalidGroundOffset

A building's ground offset attribute is negative. The offset raises the finished floor above surrounding ground, so a negative value sinks the building below it.

Open the building's attributes and set LAI_GNDOFFSET to a positive value in metres, or clear it to use the project default.

BuildingLargeSlabThickness

A building's slab thickness is far larger than a normal slab. The value is used as given, but a figure this large is usually a unit error - millimetres entered where metres were expected.

Check the value is in metres and correct it if it was entered in millimetres. If the thick slab is intentional, no action is needed.

BuildingLargeSubbaseThickness

A building's subbase thickness is far larger than a normal subbase. The value is used as given, but a figure this large is usually a unit error.

Check the value is in metres and correct it if it was entered in millimetres. If the thick subbase is intentional, no action is needed.

BuildingLargeGroundOffset

A building's ground offset is far larger than a normal finished-floor rise above ground. The value is used as given, but a figure this large is usually a unit error.

Check the value is in metres and correct it if it was entered in millimetres. If the high offset is intentional, no action is needed.

Unsupported tie-in type

A building tie-in has a type other than GARAGE. Only the garage tie-in is supported; any other type is not interpreted, so the building is not tied to the road.

Open the tie-in's attributes and set TYPE to GARAGE, or delete the tie-in if the building does not need a road connection.

CloseRdExtents

Two road extents are close enough that their buffered edges nearly meet, leaving a narrow strip between them. The strip is too thin to grade sensibly and can produce a sliver of steep ground.

Add a grade break between the two extents so the strip is graded deliberately, or move the extents apart or together so no thin strip remains.

RdExtentCloseEwExtent

A road extent runs close to the earthworks extent boundary with no general ground area or retaining wall between them. There is not enough room for the road batter to tie out to existing ground.

Add a general ground area or a retaining wall along the boundary, move the road away from the extent edge, or extend the earthworks extent to give the batter room.

RdExtentNoCenterline

A road extent has no centreline. The centreline carries the profile, stationing and crossfall, so an extent without one has no levels to grade to.

Draw a road centreline through the extent and convert it as an Allsite road centreline, or delete the extent if it is not a road.

EmptyRdExtentSegment

A road extent segment contains no geometry. It is an empty record, so nothing can be graded from it and anything referring to it loses its link.

Delete the empty segment and redraw it if the road needs one there. Re-run layout assist if the segment was generated rather than drawn.

TooManyRoadExtents

A road centreline has more than one road extent. Each centreline grades exactly one extent, so multiple extents leave it ambiguous which one carries the profile.

Merge the extents into a single polygon for that centreline, or split the centreline so each part has its own extent.

RegionsDisconnected

Two corridor regions on the same road are separated by more than the connection tolerance. The gap breaks the chain the crossfall is carried along, so the crossfall either side of it can come out wrong.

Close the gap between the regions in Corridor Properties > Parameters so they meet, then rebuild the corridor and run Prepare again.

TooManyPoints

A road centreline has more vertices than the supported limit. Dense vertex strings are usually a curve that has been drawn as many short chords, which makes the profile noisy and slows processing.

Redraw the centreline using arcs instead of chorded segments, or generalise the line to remove intermediate vertices along straight runs.

MultipleParts

A road centreline is a multi-part geometry - one record holding several separate lines. Stationing runs along a single continuous line, so a multi-part centreline has no single chainage and cannot carry a profile.

Explode the multi-part centreline into separate single-part centrelines (run multipart to singlepart), then re-convert them as Allsite road centrelines.

CentrelineCross

Two road centrelines cross each other away from a valid junction. Each carries its own profile, so at the crossing the design has two different levels for the same point.

Split the centrelines at the crossing and place a centrepoint or road extent there so it is treated as a junction, or move one centreline so they no longer cross.

InvalidCenterlineJunction

Several road centrelines meet at a point with no centrepoint, road extent, or centreline midpoint to define the junction. Nothing tells the design what happens where they meet, so the levels at the junction are undefined.

Add a centrepoint at the junction, or extend a road extent to cover it, so the meeting point is explicitly defined.

UnconnectedStartEndpoint

A road centreline's start endpoint has no valid connection. Levels propagate through the network from a valid source; an unconnected end has nothing upstream to take its level from.

Snap the start of the centreline to the adjoining centreline, a centrepoint, or the earthworks boundary so it connects to the network.

UnconnectedEndEndpoint

A road centreline's end endpoint has no valid connection. Levels propagate through the network from a valid source; an unconnected end has nothing to tie into.

Snap the end of the centreline to the adjoining centreline, a centrepoint, or the earthworks boundary so it connects to the network.

CenterlineLoop

A road centreline forms a loop with no connection to a valid level source. Every road in the loop takes its level from the next one around, so nothing fixes the levels and the loop cannot be solved.

Connect the loop to the wider road network, or set a level source on one road in it - a start or end Z override, or a connection to the earthworks boundary.

CenterlineLoopAtCenterpoint

A road centreline loop closes back on itself at a centrepoint with no external level source. The centrepoint takes its level from the roads meeting there, and those roads take theirs from the centrepoint, so nothing anchors the levels.

Connect one of the roads in the loop to the wider network, or set a start or end Z override on one of them to anchor the levels.

BadCenterpointPlacement

Extending a road centreline from a centrepoint hits another centreline, or a second road extent, before it reaches its own road extent. The centrepoint cannot be resolved to a single road end.

Split the road extents so the centrepoint's road terminates in its own extent, or remove the centrepoint if the junction does not need one.

KerbOverlap

A kerb overlaps a road centreline. The kerb should sit at the edge of the carriageway, so one crossing the centreline means the offsets are wrong or the kerb belongs to a different road.

Check the kerb's offset and the road it belongs to. Move it back to the carriageway edge or reassign it to the correct centreline.

HighMinGrade

A road centreline's minimum grade exceeds the 2 per cent maximum supported. The minimum grade is a floor the design must not go below, so setting it this high forces every length of road to be steep.

Open the centreline's attributes and reduce MIN_GRADE to 2 per cent or less. Use the maximum grade, not the minimum, to control how steep the road may become.

HighCrossfall

A road centreline's crossfall exceeds the 50 per cent maximum supported. A value this large is almost always a unit error - a percentage entered where a ratio was expected, or vice versa.

Open the centreline's attributes and set the crossfall to the intended value, checking whether the field expects a percentage or a decimal ratio.

VLowMaxGrade

A road centreline's maximum grade is below the 5 per cent minimum supported. Constraining the road this tightly leaves the design almost no vertical freedom and usually produces a worse result than a realistic limit.

Raise MAX_GRADE to at least 5 per cent, or to whatever your standards allow for this road category.

LowMaxGrade

A road centreline's maximum grade is under 8 per cent. This is permitted, but it constrains the vertical design and may stop Level AI finding a good balance of cut and fill.

If the limit is a real standard, no action is needed. If it was set conservatively, raise it to the maximum your standards allow and re-run to compare results.

UnusualRoadCategory

An unusual road category has been selected for a centreline. The category drives default widths, grades and kerb treatment, so an unexpected one usually means it was picked from the list in error.

Check the road category on the centreline matches the road you intend, and correct it if not.

RoadAlignmentStartTangent

A road alignment has a start elevation override but no start tangent. The override fixes the level at the start; without a tangent the design chooses the departing grade itself, which can produce a steep connection where the override differs from existing ground.

Set the start tangent alongside the override so the departing grade is controlled, or clear the elevation override and let the design tie into existing ground.

RoadAlignmentEndTangent

A road alignment has an end elevation override but no end tangent. The override fixes the level at the end; without a tangent the arriving grade is chosen by the design and can be steep.

Set the end tangent alongside the override so the arriving grade is controlled, or clear the elevation override and let the design tie into existing ground.

RoadAlignmentStartZ

A road alignment's start Z override is not within tolerance of the existing ground surface at that point. The road would start well above or below the ground it connects to.

Check the override elevation against existing ground at the start of the alignment. Correct it if it is wrong, or clear it so the design ties into the surface.

RoadAlignmentEndZ

A road alignment's end Z override is not within tolerance of the existing ground surface at that point. The road would end well above or below the ground it connects to.

Check the override elevation against existing ground at the end of the alignment. Correct it if it is wrong, or clear it so the design ties into the surface.

ParcelTypeOutlier

A parcel's size matches typical NORMAL single-family lots, but its TYPE or LAI_TYPE says otherwise. Lot type drives how the lot is graded and serviced, so a mismatch usually means the type was set in error.

Review the parcel's TYPE and LAI_TYPE and correct them if the lot is a normal single-family lot. If the type is right and the size is coincidental, this can be ignored.

NormalLotOverRdCenterline

A single-family lot overlaps a road centreline by more than the tolerance. A lot straddling the carriageway is not a residential lot, so Level AI will reclassify it as a road parcel.

If the lot is genuinely a road parcel, no action is needed. If not, correct the lot boundary so it stops at the road reserve.

LotTooSmall

A lot's area is below the minimum supported. It is too small to be a real lot and is usually a sliver created where two boundaries did not meet exactly.

Delete the sliver, or merge it into the adjoining lot.

LotBoundingBoxArea

A lot's bounding box is far larger than the lot itself. This is the signature of a long thin or L-shaped polygon, or of a lot with a stray vertex far from the rest of the boundary.

Check the lot boundary for a vertex in the wrong place and remove it. If the lot is genuinely an awkward shape, confirm its category suits it.

LotMinGradePresent

A lot has an explicit minimum grade set. Fixing a floor on the lot grade constrains the design more than it usually needs; leaving it unset generally produces a better result.

Clear the lot's minimum grade unless a standard requires it, then re-run to compare the result.

LotMinHigherMaxGrade

A lot's minimum grade is higher than its maximum grade. No grade can satisfy both, so the constraint pair is impossible and the lot cannot be graded to it.

Correct the values so the minimum is below the maximum, or clear one of them.

MinFallLotToVCHigherMaxGrade

The minimum fall from the lot to the vehicle crossing is larger than the maximum fall allowed. No driveway grade satisfies both, so the crossing cannot be designed to the constraints given.

Reduce the minimum fall, or raise the maximum fall, so the two leave a workable range for the driveway.

SmallPond

A pond's area is below the minimum supported. It is too small to grade a batter and floor within, so the pond shape cannot be resolved.

Enlarge the pond to at least the area in the message, or delete it if it is not required.

SteepPond

A pond's side slope exceeds the 100 per cent maximum supported. A batter steeper than 1 in 1 will not stand, and a value this high is often a ratio entered where a percentage was expected.

Check the pond's grade attributes and set them to the intended slope, confirming whether the field expects a percentage or a ratio. Flatten the batter to 100 per cent or less.

PondOverlap

Two ponds overlap. The overlapping area belongs to both, so its floor level and batter are ambiguous.

Edit the pond boundaries so they abut or separate, or merge them into a single pond if they are meant to be one basin.

PondEw

A pond sits within tolerance of the earthworks extent boundary. There is not enough room between the pond batter and the boundary for it to tie out to existing ground.

Move the pond inward, or extend the earthworks extent so the batter has room to tie out.

PondOnNormalLot

A pond overlaps a normal residential lot. A lot containing a pond is a drainage reserve rather than a building lot, so Level AI will reclassify it as a drainage lot.

If the lot is genuinely a drainage reserve, no action is needed. If not, move the pond off the lot or correct the lot boundary.

WallInsideRdExtent

A retaining wall falls inside a road extent. Roads are graded as a continuous surface, so a wall within one cannot be built and it is omitted from the Level AI model.

Move the wall outside the road extent, or narrow the road extent so the wall sits at its edge. If the wall is not needed, delete it.

WallOpposingOffset

Two retaining walls meet end to end but retain to the same side, so their height offsets oppose each other. Each wall expects the ground on its left to be the retained side, and at the join those expectations conflict.

Reverse the direction of one of the walls so their retained sides agree at the join, then run again.

WallOffsetStep

The left height offset steps abruptly between adjoining retaining wall segments. A step in the offset produces a vertical discontinuity in the retained face at that point.

Even out the height offsets between the adjoining segments, or add an intermediate segment so the change is gradual.

MinMaxHeightGap

A retaining wall's maximum height is less than the required clearance above its left offset magnitude. The wall could not reach the offset it is asked to retain to, so the maximum height is increased automatically.

No action needed - the maximum height is raised for you. Set a maximum height above the offset magnitude in the drawing if you want to control the value yourself.

DitchInvalidSideGrade

A ditch's side slope grade is zero or negative. The side slope is what forms the ditch batter, so a non-positive value gives it no shape.

Open the ditch's attributes and set the side slope grade to a positive value.

DitchSteepSideGrade

A ditch's side slope grade is very steep. The value is used as given, but a batter this steep will not stand in most materials and is often a unit or ratio error.

Check the side slope grade is the value you intend and the units the field expects. Flatten it if it was entered wrongly.

DitchInvalidMinGrade

A ditch's minimum grade is zero or negative. A ditch needs a positive fall to drain, so a non-positive minimum grade leaves it flat or falling backwards.

Open the ditch's attributes and set the minimum grade to a positive value.

DitchSteepMinGrade

A ditch's minimum grade is very steep. The value is used as given, but a minimum this high forces the whole ditch to fall steeply and is usually a unit error.

Check the minimum grade is the value you intend and the units the field expects. Reduce it if it was entered wrongly.

DitchInvalidDepth

A ditch's depth is negative. Depth is measured downward from the surrounding ground, so a negative value raises the ditch invert above it.

Open the ditch's attributes and set the depth to a positive value.

DitchLargeDepth

A ditch's depth is very large. The value is used as given, but a depth this great is usually a unit error - millimetres entered where metres were expected.

Check the depth is in the project's units and correct it if not. If the deep ditch is intentional, no action is needed.

DitchInvalidBaseWidth

A ditch's base width is negative. The base is the flat floor of the ditch, so a negative width leaves it undefined.

Open the ditch's attributes and set the base width to zero (for a V ditch) or a positive value.

DitchLargeBaseWidth

A ditch's base width is very large. The value is used as given, but a width this great is usually a unit error, or a swale that has been entered as a ditch.

Check the base width is in the project's units and correct it if not. If the wide base is intentional, no action is needed.

DitchOutsideEwExtent

A ditch's graded footprint extends beyond the earthworks extent. The ditch is too wide for the space available, so part of its batter falls outside the area being graded.

Narrow the ditch - reduce its depth, base width, or side slope - or extend the earthworks extent to give the batter room.

DitchOverlapBuilding

A ditch's graded footprint overlaps a building. The ditch would be cut into the building platform, undermining it.

Move the ditch away from the building, or narrow it so its footprint clears the footprint of the building.

DitchOverlapPond

A ditch's graded footprint overlaps a pond. Both are cut features with their own floor levels, so the overlap has two competing inverts.

Move the ditch so it stops at the pond edge, or shorten it so it discharges into the pond rather than crossing it.

DitchOverlapRetainingWall

A ditch's graded footprint overlaps a retaining wall. The ditch would be cut through the wall, so neither the retained level nor the ditch invert can be built.

Move the ditch clear of the wall, or move the wall. If the ditch runs at the toe of the wall, offset it so the footprints do not overlap.

DitchOverlapRoadExtent

A ditch's graded footprint overlaps a road extent. The road is graded as a continuous surface, so the ditch feature lines inside it are removed automatically during processing.

No action needed - the overlap is auto-corrected and the ditch stops at the road edge. Move the ditch clear of the road if you want the drawing to match the processed result.

LinkNoUpstreamElevation

A pipe has no upstream invert level. Without it the pipe's grade cannot be worked out, so it is left out of the analysis.

Set the upstream invert on the pipe, or let the design set it by leaving the structure to be designed rather than treating the pipe as existing.

LinkNoDownstreamElevation

A pipe has no downstream invert level. Without it the pipe's grade cannot be worked out, so it is left out of the analysis.

Set the downstream invert on the pipe, or let the design set it by leaving the structure to be designed rather than treating the pipe as existing.

LinkDownstreamMinCover

A pipe's downstream invert is above the deepest invert that still leaves minimum cover. The pipe would run too shallow to be protected, so it is left out of the analysis.

Lower the downstream invert so it sits below the maximum invert stated in the message, or reduce the minimum cover requirement if your standards allow it.

StructureNoLidLevel

A structure has no lid level. The lid is the surface level of the structure, so without it the structure's depth is unknown and it is left out of the analysis.

Set the structure's lid level, or let the design set it by leaving the structure to be designed rather than treating it as existing.

StructureNoInvertLevel

A structure has no invert level. The invert is what the pipes connect to, so without it the structure cannot be used in the analysis.

Set the structure's invert level, or let the design set it by leaving the structure to be designed rather than treating it as existing.

PipeOverlap

Two pipes overlap in plan. Overlapping pipes cannot both be laid on the same line, and the overlap usually means one of them is a duplicate or is connected to the wrong structures.

Delete the duplicate pipe, or reroute one of them so they run on separate lines between their structures.

LockoutNeedsProposedSurface

A locked general ground-control area has no proposed surface to preserve. A lockout holds the existing design in place, so with no proposed surface selected there is nothing for it to hold.

Open the Allsite project settings and select the proposed surface the locked area should preserve, then run again. Remove the lockout if there is no design to hold.

LockoutOutsideProposedSurface

A locked general ground-control area is not fully covered by the proposed surface. The part outside has no design levels to preserve, so the lockout cannot be honoured across the whole area.

Shrink the locked area so it sits within the proposed surface, or extend the proposed surface to cover it, then run again.

LockoutDesignArea

A locked general ground-control area will preserve the current proposed design surface. This confirms the lockout is active and the ground inside it will not be regraded.

No action needed - this is a confirmation of intent. Remove the lockout if you want the area regraded.

Small_Ground

A general ground area is smaller than the minimum. It is too small to grade a meaningful surface within and is usually a sliver left where boundaries did not meet.

Delete the sliver, or merge it into the adjoining general ground area.

ImperviousSlither

An impervious polygon has been reduced to a slither - a shape too thin to carry area. It contributes essentially no runoff and is usually a fragment left by a clip or overlay.

Delete the slither, or widen it to the area it is meant to represent.

ImperviousOverlap

Two impervious polygons overlap. The overlapping area is counted twice in the runoff calculation, so the catchment's impervious fraction comes out too high.

Edit the polygons so they abut rather than overlap, or merge them into one.

ResidualSlither

A slither polygon remains between shapes after they were snapped together. The snap closed the main gap but left a thin residual sliver, which contributes no meaningful area.

No action usually needed. If the sliver matters, snap the source polygons together in the drawing so no residual remains.

NoCurbType

A road modifier has no curb type set. The curb type drives kerb height and the back-of-kerb offset, so without it the modifier does not describe a kerb treatment.

Open the modifier's attributes and set the curb type, or delete the modifier if no kerb change is intended there.

Invalid carriageway width left

The left carriageway width is zero or negative. The carriageway is the trafficked width from the centreline to the back of kerb, so a non-positive value leaves the left side of the road with no surface.

Open the road's attributes and set CARR_WID_L to a positive value, or clear it so it is derived from the corridor.

Carriageway width left exceeds ROW

The left carriageway width is greater than the left right-of-way width. The carriageway would extend beyond the road reserve, which cannot be built.

Reduce CARR_WID_L below ROW_WID_L, or widen the right of way if the road reserve is genuinely wider than recorded.

Invalid carriageway width right

The right carriageway width is zero or negative. The carriageway is the trafficked width from the centreline to the back of kerb, so a non-positive value leaves the right side of the road with no surface.

Open the road's attributes and set CARR_WID_R to a positive value, or clear it so it is derived from the corridor.

Carriageway width right exceeds ROW

The right carriageway width is greater than the right right-of-way width. The carriageway would extend beyond the road reserve, which cannot be built.

Reduce CARR_WID_R below ROW_WID_R, or widen the right of way if the road reserve is genuinely wider than recorded.

RelationshipCycle

The feature relationships form a cycle - a chain of features each taking its level from the next, closing back on the first. Nothing in the cycle has an independent level, so it cannot be solved.

Break the cycle by pointing one relationship at a feature with a fixed level, or by removing one of the relationships in the chain.

RelOffsetNotCloseToBuilding

A building relationship offset is not close to any building. The relationship ties a level to a building edge, so with no building near it there is nothing to tie to.

Move the relationship offset onto the building it belongs to, or delete it if the building it referred to has been removed.

RelEndTooCloseToBuilding

A relationship end point sits too close to a building edge. At that distance the relationship and the building platform are setting the same level in two different ways.

Move the relationship end away from the building edge beyond the tolerance in the message, or use a building tie-in instead of a relationship here.

RelOffsetTooClose

Two or more relationship end points sit too close together. Each sets a level at its end point, so ends this close specify competing levels at effectively the same place.

Move the relationship ends apart beyond the tolerance in the message, or delete the redundant relationship.

RelOffsetOutsideTinExtent

A relationship offset falls outside the existing ground surface (TIN). Its level is sampled from the surface, so an offset outside it has no ground level to work from.

Move the relationship offset inside the surface boundary, or extend the existing surface to cover it.

ShapeOutsideTin

A feature falls outside the existing ground surface (TIN). Levels are sampled from the surface, so any part of the feature outside it has no ground to design against.

Extend the existing surface to cover the feature, or move the feature inside the surface boundary.

ShapeOverlap

Two features of the same type overlap. The overlapping area belongs to both, so whatever the feature type controls - levels, grading, or classification - is ambiguous there.

Edit the features so they abut rather than overlap, or merge them into a single shape.

MultiPart

A feature is a multi-part geometry - one record holding several separate shapes. Each Allsite feature must be a single shape, since attributes such as levels and grades apply to one geometry.

Run multipart to singlepart on the feature so each shape becomes its own record, then re-convert them as Allsite features.

NotSnapped

A feature is not snapped to the shape it should connect to. The two do not actually meet, so nothing carries across the join.

Snap the feature to the target shape so they share a point or an edge, then run again.

NotTouching

A feature does not touch the shape it is required to touch. The connection the design relies on is missing.

Extend or snap the feature so it touches the required shape, then run again.

Touching

A feature touches a shape it is required to stay clear of. The two are in contact where the design expects a separation between them.

Move the feature away from the shape so they no longer touch, then run again.

Overlapping

A feature overlaps another it is required to stay clear of. The two occupy the same ground where the design expects them to be separate.

Edit the geometry so the features abut or separate rather than overlap.

TooSmall

A feature's area is below the minimum supported. It is too small to be processed meaningfully and is usually a sliver left by a clip or an edit.

Delete the sliver, or enlarge the feature to the area it is meant to cover.

ParallelCenterlinesTooClose

Two parallel road centrelines are within the minimum separation. Their graded widths overlap, so neither road ends up with the crossfall it was designed to have.

Move the centrelines apart beyond the separation in the message, or model the two carriageways as a single road with a median.

LotNotServiceableStorm

A lot cannot drain in a straight line to any valid part of the stormwater network. Every candidate node's invert is too high, once cover, pipe size and grade over the run are allowed for, to take a connection from this lot.

Lower the invert of the nearest node, or add a node closer to the lot. The message gives the best available node and the lot level it would need - use it to decide which end to change.

LotNotServiceableSanitary

A lot cannot drain in a straight line to any valid part of the sanitary network. Every candidate node's invert is too high, once cover, pipe size and grade over the run are allowed for, to take a connection from this lot.

Lower the invert of the nearest node, or add a node closer to the lot. The message gives the best available node and the lot level it would need - use it to decide which end to change.

PondSizing

A pond could not be sized. Either INTERNAL_LOWPOINT is set to N and there is no stormwater outlet to size against, or the inputs the sizing needs are missing. A default depth is applied instead of a designed one.

Set INTERNAL_LOWPOINT to Y if the pond drains to its own low point, or connect it to the stormwater network so there is an outlet to size against. Then re-run so the pond is sized properly rather than defaulted.

CentrelineOverlap

Two road centrelines run over the top of each other. The overlapping length is described twice, so the design has two competing profiles along it.

Delete the duplicate centreline, or trim the overlapping section so each length of road is described by one centreline only.

AlignmentOverlap

Two road alignments follow the same line for most of the shorter one's length, so the same road is described twice.

They are indistinguishable on screen, but each carries its own road data — widths, radii, road category — and Layout Assist has no way to tell which one describes the road, so it may build the modifiers from the wrong alignment's data.

Usually an alignment copied, or a simple road drawn along an alignment that was already tagged.

Check the alignment property data set on both before deleting either. The one reported as redundant is only the more-covered of the pair — not necessarily the one with the wrong attributes.

Keep the alignment whose ROAD_CATEGORY, widths and radius are correct. Delete the other, then re-run Layout Assist.

AlignmentNearMiss

A road alignment stops short of another instead of meeting it, by a gap too small to see at plan zoom.

An intersection is only found where alignments actually touch, so no junction is detected there and no curb return modifier is generated.

The opposite failure to AlignmentOverlap: geometry that is disconnected rather than duplicated.

Extend or trim the ending alignment so its endpoint lies on the other one, or join them. Re-run so the intersection and its modifier curb return generate.

If the two roads genuinely do not connect, the finding can be ignored.

NoAllsiteAlignments

No alignment in the drawing carries an Allsite road schema, so a run sees no roads whatever the drawing contains.

Raised before extraction, so it names the cause of the empty-package errors that would otherwise be the first sign of it.

Convert the road centrelines to Allsite simple roads — the ribbon convert.

Polylines are promoted to alignments and the originals erased, so the handles you passed no longer exist afterwards.

If the drawing has no centrelines at all, they have to be drawn first.

UntaggedAlignments

Some centreline alignments carry no Allsite road schema and are invisible to a run, while others are tagged — so the run succeeds and silently omits those roads.

Offset and curb-return alignments are excluded from the count: they are Civil 3D's own derived geometry and are not meant to be tagged.

The message names the untagged alignments and their handles.

Convert the ones that should be roads to lai_rd_centre_simple.