Working with Kerb Returns
Posted by Greg Cattarin, Last modified by Selwyn Pendergast on 10 March 2020 03:05 PM
How to avoid Potential Errors when Creating Kerb Returns
If you have difficulties in creating kerb returns with errors being displayed or not located correctly, go through these items correct any issues to see whether it may solve your problem.
- Check that the both Alignments are flowing and continuous - that is, there are NO kinks and Curves are TANGENTIAL to Straights or the next curve and NO gaps;
- Check the Point Connection Code settings in Active Drawing Settings (2nd tab);
- Check that the Codes exist at the required intersection (not removed by a variation);
- Check that the Side road alignment is long enough;
- Check that the Main road alignment is extended far enough beyond the
- At a 'T' intersection make sure that the Side road 'touches' the Main road (not cross it);
- Make sure there is NOT an IP on the Main road alignment for both 'T' & '+' intersections and an IP on the Side road alignment for a '+' intersection;
- Is there a profile control on the main road or the
side road affecting the EB strings, so that changing the VC of the main/side
WILL NOT change the kerb levels?
- Do the Road Cross Sections look OK?
- Do the Kerb Cross Sections look OK?
- Do the VC's list OK for the kerbs and the roads?
- Check the sections on the template and make sure that
the codes are as expected and also check
that the selected template exists.
- For a road that is being matched to existing lip-line,
then make sure that the matching alignment touches the lip alignment, NOT the
actual road alignment;
- Kerb Returns will be formed parallel to the road alignment not the connection code (by default EB), so if the connection code does not run parrallel to the centreline, consider extending the KR to a point where it is parrallel and using the Specify tab on the Kerb Return form.