62-acre project site corridor all-as-one or multiples?

[RobertEVs]

Picking the corridor modeling expert brains here.

I'm laying out this subdivision and in addition to multiple streets there are several sidewalk pathways. I plan on creating corridor models for all streets and pathways as individual models since most of the pathways are not contiguous and the streets intersect. Since my deeper-dive corridor experience has only been over the last couple years is it better to create one single corridor model of the streets/pathways and region out each intersection or leave them as standalone corridor models? I have the CTC project suite installed so I can merge them all to one model and when finished pretty easily. What would be the pros or cons to multiple corridor models in one drawing? 

Just looking for thoughts

 

[brian.strandberg]

I haven't seen a good reason to use multiple corridors.  The only reason to use more than one in my opinion is if you want more than one resulting surface, Phase 1-2, or if you are tiling the data in the project due to size issues.

[RobertEVs]

Thank you for the input.

I can create surfaces from each corridor and paste them all into my Final FG. So far, my file size is under 7.5mb with 7 streets and 13 pathways running frequency at 10 tangents/curves which makes this drawing manageable. Can you tell me why you would prefer one single corridor? Easier to manage? I ask because either way seems to work the same from my experience.

[brian.strandberg]

I agree with you there isn't any big change in the way you manage the corridor 1 vs many.  I have typically used one, because I haven't seen a great reason to go with many.  Both should work about the same.  

[RobertEVs]

Good info Brian. BTW you create the GSV? I love that little add-on. Use it almost daily

 

[brian.strandberg]

Yes I did.  I'm glad you enjoy it.  I was reviewing a survey and it took me like 5 minutes to find the right point in street view, and decided that was stupid it should take so long.

[RobertEVs]

We had about 11 on staff in our department now down to 6. I did a presentation once I found out about this add-on, offered to install and set it up for anyone. Not a single response. I SMH to young engineers at times.

[brian.strandberg]

I added that to our menu and did a short video and many didn't know about it.  Later I sent an email with just links to a few short videos on process and got alot of positive feedback on that.

Currently we have over 30 Civil 3d videos in our company system, and over 60 total, I think its getting harder for people for people to find what they need.

[RobertEVs]

I created an excel spreadsheet with links to all my training videos and links I find pertinent to my own needs. I open Ctrl>F type some text, example intersections or targeting and away I go.

 

[BrianHailey]

I'm also in the mindset of a single corridor model. I model as much as I can with the corridor and then leave gaps where the corridor doesn't make sense and then use featureline grading in those areas.

Here's an example of a similar project (a bit smaller though) done with one corridor.

[RobertEVs]

Brian I'm gathering you are not one to bother with intersection offsets or returns?

[Joe-Bouza]

I am in the one corridor camp. unless you have to divided the work among others

[BrianHailey]

---

@RobertEVs wrote:

Brian I'm gathering you are not one to bother with intersection offsets or returns?

---

@RobertEVs it depends. At the start of the design, absolutely not. I don't bother with them at all. Once the design gets close to completion and things aren't moving around as much, then I'll do the intersection. When I do, if they are simple intersections that the intersection tool can be used for, then I will do them with a corridor. If not, then I'll do them with featureline grading. The example picture I shared was from a project that I did the design for back in the LDD days and then used that project to train myself on Civil 3D so it's not a complete design.

What makes an intersection so incredibly complex that it's not worth trying to model it using the corridor tools? A cross pan, which almost every intersection in my  area has.

[RobertEVs]

What makes an intersection so incredibly complex that it's not worth trying to model it using the corridor tools? A cross pan, which almost every intersection in my area has.

I'm with you on that. I'll do a simple intersection then set any post drain pans across streets using featurelines relative to surface. If I have to adjust the PVI at the intersection my drain pans will follow. So far, my project is going well.

 

[lim.wendy]

I also lean towards using one corridor model for similar reasons. Here’s an example from a project I worked on many years ago using a single corridor model:

I find that managing one comprehensive model ensures consistency across the project. Of course, there are always pros and cons to consider depending on the specific project needs...

[chriscowgill7373]

I'm not quite sold on a single corridor model.  I found it weird when I came to my current company and that is how some users were doing it.  Perhaps I'm just overcomplicating my corridors, but, how would a single corridor work in areas where parts of the corridor that need to tie together, but they are dependent on a part of the corridor for definition?  With a separate corridor, you can generate an autofeature line,and possibly use that as a baseline, or a target point.  You wouldnt be able to do that with a single model, because it is tied to that corridor object and it would be in an infinite loop of redefining the feature line, and then updating the portion of the corridor.   I dont believe that offset alignments and offset profiles work in every situation to define the road section.  there are some really weird things that go on when you have bumpouts for curb and such.