Review warnings indicate where parts of the design may have issues for a Service AI or Level AI run. There is additional data attached to the review point (extended data property set) and panorama event log and provided in the AI assistant.
Priority can be from 1 (lowest) to 9 (highest). In general priorities < 4 are for information, priorities 4-8 are warnings (can affect Level AI / Service AI run) and 9 are errors (will affect Level AI / Service AI run and must be resolved before proceeding). By default Info review layers are left off after a Prepare run.
No. | Validation code | Explanation | Resolution |
1 | 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. |
2 | 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. |
3 | 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. |
4 | InvalidBaselineType | 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. |
5 | CorridorRegionOverlap | Corridor regions overlap spatially. This often causes bad surfaces, incorrect quantities, and unstable rebuilds. Common causes: Region station ranges overlap after edits or splitting. Alignments overshoot into intersections or past cul-de-sac ends. | 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. Rebuild the corridor, then run Validate Corridor. |
6 | 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. |
7 | 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. |
8 | InvalidAssembly | 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. Rebuild the corridor and validate. |
9 | 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. |
10 | 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. | 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. Rebuild the corridor and validate. |
11 | 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. |
12 | 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. |
13 | 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. |
14 | 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. |
15 | 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. |
16 | 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. |
17 | NoCoordinateSystem | No coordinate system was defined in the DWG. This is required for Allsite.ai to geolocate the project. | |
18 | 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. |
19 | 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. |
20 | 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. |
21 | 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. |
22 | NoLayersCustomSubAssembly | A custom subassembly is in use with geometry that cannot be read. | Replace it with a standard Civil 3D subassembly. |
23 | ConditionalSubAssemNotSupported | A conditional subassembly was detected. Conditional subassemblies are not supported in Level AI. | Remove the subassembly. |
24 | 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. |
25 | 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. |
26 | DaylightingNotRequired | A daylighting subassembly was detected. These are not required and are ignored in Level AI runs. | Remove the subassembly. |
27 | 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. |
28 | 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. |
29 | 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. |
30 | 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. |
31 | 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. |
32 | 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". |
33 | 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. |
34 | 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. |
35 | 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. |
36 | 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. |
37 | 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. |
38 | 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. |
39 | 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. |
40 | 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. |
41 | 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. |
42 | 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. |
43 | 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. |
44 | 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. |
45 | 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. |
46 | 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. |
47 | 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. |
48 | RdCenterlineNotInRoadExtent | The road centerline is not within the associated road extent. | Adjust the centerline geometry so it is contained within the road extent polygon. |
49 | RdCenterlineNotSnapped | The road centerline is not snapped to another centerline or required feature. | Snap the centerline endpoints to the appropriate features. |
50 | RdCenterlineTooShort | The road centerline is shorter than the minimum required length. | Extend the centerline to meet the minimum length requirement. |
51 | RdCenterlineGap | There is a gap between road centerlines. | Connect or extend centerlines to close the gap. |
52 | 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. |
53 | RdCenterlineCrossesMultipleRdExtents | A road centerline crosses more than one road extent. | Split the centerline or adjust the extents so each centerline is within a single extent. |
54 | RdCenterlineAngles | The road centerline has angles that are too sharp or do not meet design criteria. | Smooth or adjust the centerline geometry to meet angle requirements. |
55 | RdCenterlineOverlaps | Road centerlines overlap each other. | Adjust the geometries to remove overlaps. |
56 | RdCenterlineParallel | Road centerlines are too close together and nearly parallel. | Increase the separation between parallel centerlines. |
57 | 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. |
58 | 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. |
59 | 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 "SINGLE FAMILY". |
60 | 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. |
61 | Road parcel (singlepart geometry) | Road parcel geometry is multipart but must be singlepart. | Split multipart geometries into singlepart features. |
62 | Building (singlepart geometry) | Building geometry is multipart but must be singlepart. | Split multipart geometries into singlepart features. |
63 | OLFP (singlepart geometry) | OLFP geometry is multipart but must be singlepart. | Split multipart geometries into singlepart features. |
64 | Retaining Wall (singlepart geometry) | Retaining wall geometry is multipart but must be singlepart. | Split multipart geometries into singlepart features. |
65 | RWNotInEWExtent | The retaining wall is not within the earthworks extent. | Adjust the retaining wall geometry to fit within the earthworks extent. |
66 | RWOverlaps | The retaining wall overlaps another wall. | Adjust the wall geometries to remove overlaps. |
67 | 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. |
68 | RWNotSnapped | The retaining wall is not snapped to the earthworks extent. | Snap the wall endpoints to the earthworks extent boundary. |
69 | RWBadAngles | The retaining wall has angles that are too sharp or do not meet design criteria. | Adjust the wall geometry to smooth out sharp angles. |
70 | RWTooClose | Retaining walls are too close to each other. | Increase the separation between retaining walls. |
71 | 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. |
72 | 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. |
73 | RoadExtentOverlaps | The road extent overlaps another road extent. | Adjust road extent polygons to remove overlaps. |
74 | RoadExtentTooSmall | The road extent area is too small. | Increase the area of the road extent polygon. |
75 | 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. |
76 | 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. |
77 | 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. |
78 | 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.” |
79 | RoadExtentWidth | The road extent width does not meet minimum requirements. | Adjust the road extent geometry to meet width requirements. |
80 | RoadExtentNotInEWExtent | The road extent is not within the earthworks extent. | Adjust the road extent polygon to fit within the earthworks extent. |
81 | 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. |
82 | Building (overlapping shapes) | A building overlaps another building. | Adjust building polygons to remove overlaps. |
83 | Building (too small) | The building area is too small. | Increase the area of the building polygon. |
84 | Lot (too small) | The lot area is too small. | Increase the area of the lot polygon. |
85 | Lot (singlepart geometry) | Lot geometry is multipart but must be singlepart. | Split multipart geometries into singlepart features. |
86 | Earthworks (overlapping shapes) | Earthworks extents overlap each other. | Adjust earthworks polygons to remove overlaps. |
87 | Earthworks (sliver) | The earthworks extent has slivers or holes. | Clean up the geometry to remove slivers and fill holes. |
88 | Earthworks (bad edges) | The earthworks extent has bad edges or sharp angles. | Smooth or adjust the geometry to remove bad edges. |
89 | Earthworks (fields) | The earthworks extent is missing required attribute fields. | Add or correct the required fields in the attribute table. |
90 | RelationshipEndPointsTooClose | Relationship endpoints are too close to each other. | Increase the separation between relationship endpoints. |
91 | RelationshipLoops | There are loops in the relationship network. | Remove or correct the relationships to eliminate loops. |
92 | 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. |
93 | 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. |
94 | 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. |
95 | 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. |
96 | InvertAboveLid | The structure sump is not below the lid level. | Adjust the lid or sump level so the sump is below the lid. |
97 | LotNotServiceable | When minimum pipe grades are checked in a direct line to each structure, the parcel cannot be serviced. | Run Level AI with servicing enabled to generate a valid proposed surface, or manually edit the design. Alternatively, if the issue relates to a pump station, lower the sump elevation of the structure. |
98 | StructureInvertTooShallow | The structure sump invert is too shallow for a parcel to be serviced with minimum pipe grades and cover requirements. | Adjust the sump level. |
99 | InvertAboveGround | The structure sump is not below the ground level. | Adjust the sump level. |
100 | 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. |
101 | OLFPDitchConnectivity | Overland flow path ditches must cross the earthworks extent to activate. | Extend the OLFP ditch. |
102 | 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. |
103 | 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. |
104 | 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. |