<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Corridors for Everything</title>
	<atom:link href="http://www.civil3d.com/2006/10/corridors-for-everything/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.civil3d.com/2006/10/corridors-for-everything/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 03:48:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Dana Breig Probert, EIT</title>
		<link>http://www.civil3d.com/2006/10/corridors-for-everything/#comment-391</link>
		<dc:creator>Dana Breig Probert, EIT</dc:creator>
		<pubDate>Fri, 20 Oct 2006 03:15:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.civil3d.com/index.php/2006/10/corridors-for-everything/#comment-391</guid>
		<description>The Corridor for the rendered/horseshoe parking lot is amazingly simple. It is three baselines with one region each. EOP Left, EOP Right, CL. That's it.

I ran it a few ways- sometimes I did the EOPs as transitions, sometimes I didn't. It really depends on your design intent- the model can reflect whatever constraints you have.

As far as how long does it take to do this.... the first one you try will take you a long time. Probably longer than many people have the patience for if they don't see the value.

Since this is what I do for work and for fun, I stuck with it and figured it out.

The horsehoe took me about 3 hours to fully model (being as I was figuring out my technique at the same time) I would say that if I had a similar site, once I figured out my design constraints, it would take me about 1 hour to model. The design, however, would take as long as it takes to optimize my site.

Accuracy- this is as accurate as it gets. I put in addtional PIs and PVIs as I would need spot elevations if I was doing by hand.

The larger parking lot- I will report when I am finished with it.

Edits- I would estimate edits would be similar to when I have my large 52 baseline corridors for subdivisions. Major edits go quickly if I build my corridor empty. Just split my VP and work through my plan and profile watching the labels update. Every so often,rebuild the corridor and have a look at the surface.

remember- MODELING does not equal DESIGN

these sites take a long time to get the model properly built.

Once built, you iterate your design as much as you need to- and you will get your contours and labels changing with you.</description>
		<content:encoded><![CDATA[<p>The Corridor for the rendered/horseshoe parking lot is amazingly simple. It is three baselines with one region each. EOP Left, EOP Right, CL. That&#8217;s it.</p>
<p>I ran it a few ways- sometimes I did the EOPs as transitions, sometimes I didn&#8217;t. It really depends on your design intent- the model can reflect whatever constraints you have.</p>
<p>As far as how long does it take to do this&#8230;. the first one you try will take you a long time. Probably longer than many people have the patience for if they don&#8217;t see the value.</p>
<p>Since this is what I do for work and for fun, I stuck with it and figured it out.</p>
<p>The horsehoe took me about 3 hours to fully model (being as I was figuring out my technique at the same time) I would say that if I had a similar site, once I figured out my design constraints, it would take me about 1 hour to model. The design, however, would take as long as it takes to optimize my site.</p>
<p>Accuracy- this is as accurate as it gets. I put in addtional PIs and PVIs as I would need spot elevations if I was doing by hand.</p>
<p>The larger parking lot- I will report when I am finished with it.</p>
<p>Edits- I would estimate edits would be similar to when I have my large 52 baseline corridors for subdivisions. Major edits go quickly if I build my corridor empty. Just split my VP and work through my plan and profile watching the labels update. Every so often,rebuild the corridor and have a look at the surface.</p>
<p>remember- MODELING does not equal DESIGN</p>
<p>these sites take a long time to get the model properly built.</p>
<p>Once built, you iterate your design as much as you need to- and you will get your contours and labels changing with you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: omegared1978</title>
		<link>http://www.civil3d.com/2006/10/corridors-for-everything/#comment-365</link>
		<dc:creator>omegared1978</dc:creator>
		<pubDate>Thu, 19 Oct 2006 18:42:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.civil3d.com/index.php/2006/10/corridors-for-everything/#comment-365</guid>
		<description>Dana,

What a great concept. I will definitely be waiting for your post on this parking lot project. My only request is that you keep a record on how long it took you to corridor the parking on your first attempt. In addition, how long it takes you to do it with ease and accuracy.</description>
		<content:encoded><![CDATA[<p>Dana,</p>
<p>What a great concept. I will definitely be waiting for your post on this parking lot project. My only request is that you keep a record on how long it took you to corridor the parking on your first attempt. In addition, how long it takes you to do it with ease and accuracy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MAnderson</title>
		<link>http://www.civil3d.com/2006/10/corridors-for-everything/#comment-364</link>
		<dc:creator>MAnderson</dc:creator>
		<pubDate>Thu, 19 Oct 2006 16:29:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.civil3d.com/index.php/2006/10/corridors-for-everything/#comment-364</guid>
		<description>Dana -

You have my attention.  It is a very interesting concept.  As I have worked with feature lines and grading objects and CER reports to Autodesk for production, I have wondered if there was a better way.

I might have to spend some good quality C3d time instead of sleeping.

Matt Anderson</description>
		<content:encoded><![CDATA[<p>Dana -</p>
<p>You have my attention.  It is a very interesting concept.  As I have worked with feature lines and grading objects and CER reports to Autodesk for production, I have wondered if there was a better way.</p>
<p>I might have to spend some good quality C3d time instead of sleeping.</p>
<p>Matt Anderson</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pesto</title>
		<link>http://www.civil3d.com/2006/10/corridors-for-everything/#comment-363</link>
		<dc:creator>Pesto</dc:creator>
		<pubDate>Thu, 19 Oct 2006 14:12:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.civil3d.com/index.php/2006/10/corridors-for-everything/#comment-363</guid>
		<description>Dana,

That looks great and would make labeling, earthworks, etc. easy.  I do have concerns though.  How many profiles and alignments did you use to create this?  How easy would it be to make changes to this site?  I do recognize that once the changes to the profiles are corrected everything else follows.

It looks great!

David J. Pesavento
Morton &#38; Pitalo, Inc.</description>
		<content:encoded><![CDATA[<p>Dana,</p>
<p>That looks great and would make labeling, earthworks, etc. easy.  I do have concerns though.  How many profiles and alignments did you use to create this?  How easy would it be to make changes to this site?  I do recognize that once the changes to the profiles are corrected everything else follows.</p>
<p>It looks great!</p>
<p>David J. Pesavento<br />
Morton &amp; Pitalo, Inc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
