From reading previous posts. Standard practice from CTDOT mid 80's to 2000 transitioning from hand drafting to Civil2004.
Profiles ALWAYS match at CL. Side road profiles start at cross slope of main road & transition with appropriately designed vertical curves. Low points to be out of intersections when ever possible.
Catch basins/inlets ALWAYS pick up stormwater uphill of intersection unless physically impossible to do. Cost of inlet cheap compared to cost of law suit from stormwater causing accident by running across intersection!
Grading of intersections shown via Intersection Grading plans showing contours at intersections at 0.1 or 0.2 contours at 10 or 20 scale. (Days of work of hand drafting way back when.)
Way I would do now, as I haven't needed in years.
Try everything to avoid having non crowned roads intersect.
Create alignments, profiles & templates. Create separate scratch file & audit hourly as file WILL corrupt.
Import roadway 3d poly lines from roadway templates. TRIM 3dpoly lines at curb returns. On X-FAULT junk layer, snap to mid point of 2d curb return. Isolate X-FAULT junk layer & 3d template polyline gutter layer. Use Terrain 3d poly line by elevation curve function. Snap PC, Midpoint & PT of curb return. Check that grade is a MINIMUM of 1/2% , 1 % better going around curve. If not, figure out best place for inlet & grade minimum 1% to inlet along curb return. 3d poly line by elevation to complete rest of curb return.
3dpoly line curb to create curbs and shoulders along curb returns for large scale modeling. Use grading objects to intersect to existing surface around curb returns. (Depending on how tight the curb return is to existing grade, you may need to fillet poly line contours from main roads) (I have yet to figure out an advantage to contour objects. You can't do this with them & I don't do uniform cross section grading any more.)
For intersection grading contours, copy proposed tin to junk Intersection TIN. Create a series of back of curb (for margin or error) poly line boundaries. For each intersection, rebuild the proposed model using the polyline as outer boundary. Generate proposed contours at 0.2 or 0.1 intervals on special Intersection contour layers. Make sure you don't erase your large scale contours or the previous intersections. I will leave it to your staff if they want each intersection on own layer. Trim/extend the contours to match face of curb to compensate for series of chords used to approximate curve. Set up viewports for each intersection.
I have to use a similar technique for subdivisions here in the mountains. Some townships here require each lot to prove that it contains a minimum adjusted tract acreage. This is an acreage of X % of slopes above steep, another % of slopes of mildly steep all of flat portion and no wetlands, flood plains, lakes, etc. They want a reasonable guarantee a homeowner has a prayer of putting up a house on a lot. I have to create a TIN of each lot & use the slope shading functions to do. Then I need to set aside 10 minutes for each project to listen to my boss yell that the slope shadings are not perpendicular to the contour lines.
I didn't know whether to laugh or cry watching the web cast showing how Civil 3D can automate subdivisions. Around here the prime question of whether you can subdivide or not is if you have a point of existing storm water discharge. If you don't, you can subdivide.
Ann Wingert, P.E.