Dual Plan View Sheets using Plan Production

[Anonymous]

I have seen some older posts about this, but nothing for quite some time.  My issue is creating sheets using plan production that have 2 (or more) plan viewports.  We do alot of road plans where the Existing Condtion/ Removals plans are shown using a top/bottom plan view along the alignment.  Currently, when we use plan production, we end up creating a sheet for each view, then copying the views from everyother sheet to the previous sheet and deleting the extra sheets.  Still better than setting up completely manually, but a far cry from automated.

Has this been addressed now, and if so, how do I create a template and navigate the wizards to accomplish this?

Thank you!

[Anonymous]

I have seen some older posts about this, but nothing for quite some time.  My issue is creating sheets using plan production that have 2 (or more) plan viewports.  We do alot of road plans where the Existing Condtion/ Removals plans are shown using a top/bottom plan view along the alignment.  Currently, when we use plan production, we end up creating a sheet for each view, then copying the views from everyother sheet to the previous sheet and deleting the extra sheets.  Still better than setting up completely manually, but a far cry from automated.

Has this been addressed now, and if so, how do I create a template and navigate the wizards to accomplish this?

Thank you!

[Civil3DReminders_com]

Nope, nothing new. 

I think Autodesk only knows how to program tools for relatively long and straight roads. Evidently curved and short roads are too complex for Autodesk to handle with their $600 million/year R&D budget. It's a shame because this is on my list of things to rewrite, except I'm short on time. 

[Civil3DReminders_com]

Nope, nothing new. 

I think Autodesk only knows how to program tools for relatively long and straight roads. Evidently curved and short roads are too complex for Autodesk to handle with their $600 million/year R&D budget. It's a shame because this is on my list of things to rewrite, except I'm short on time. 

[Joe-Bouza]

Your sardonic yarns are most amusing and thought provoking. Have you considered an AU class that trips over all the .... " Uhh we didn't get to that part yet" parts of the program

[Joe-Bouza]

Your sardonic yarns are most amusing and thought provoking. Have you considered an AU class that trips over all the .... " Uhh we didn't get to that part yet" parts of the program

[Civil3DReminders_com]

I submitted that class for #AU2015, but it did not get accepted.

[Civil3DReminders_com]

I submitted that class for #AU2015, but it did not get accepted.

[sboon]

We've had to do this in the past.  I created a template with one viewport that is exactly twice the length that it should be, and two rectangles on a no-plot layer to mark where the two viewports should be.  When the sheets are created we copy the viewport from the top half of the sheet to the bottom and grip edit to shrink the two viewports to the correct size.

Steve
Please use the Accept as Solution or Kudo buttons when appropriate

[sboon]

We've had to do this in the past.  I created a template with one viewport that is exactly twice the length that it should be, and two rectangles on a no-plot layer to mark where the two viewports should be.  When the sheets are created we copy the viewport from the top half of the sheet to the bottom and grip edit to shrink the two viewports to the correct size.

Steve
Please use the Accept as Solution or Kudo buttons when appropriate

[Anonymous]

Thanks for the idea, Steve. Currently we end up doing similar and copy the viewport from the next sheet to the previous sheet, along with the North Arrow.  I think the issue of the North Arrow not being lined up automatically may be the only thing that keeps me from setting up a template like you described.  On a completely straight road, your template would work great.

---

@sboon wrote:

We've had to do this in the past.  I created a template with one viewport that is exactly twice the length that it should be, and two rectangles on a no-plot layer to mark where the two viewports should be.  When the sheets are created we copy the viewport from the top half of the sheet to the bottom and grip edit to shrink the two viewports to the correct size.

Steve
Please use the Accept as Solution or Kudo buttons when appropriate

---

[Anonymous]

Thanks for the idea, Steve. Currently we end up doing similar and copy the viewport from the next sheet to the previous sheet, along with the North Arrow.  I think the issue of the North Arrow not being lined up automatically may be the only thing that keeps me from setting up a template like you described.  On a completely straight road, your template would work great.

---

@sboon wrote:

We've had to do this in the past.  I created a template with one viewport that is exactly twice the length that it should be, and two rectangles on a no-plot layer to mark where the two viewports should be.  When the sheets are created we copy the viewport from the top half of the sheet to the bottom and grip edit to shrink the two viewports to the correct size.

Steve
Please use the Accept as Solution or Kudo buttons when appropriate

---

[Anonymous]

Does anybody have any tricks for manipulating the matchline annotation labels when doing a top/bottom plan sheet?  I end up exploding the labels in my base, then explode the blocks, then copy the mtext from the base to the intended drawing, pasting, and then editing to either call out the previous/next sheet, or "SEE ABOVE"/"SEE BELOW".

I've thought about creating a block I could insert at the matchlines with attributes that could be easily editted for each instance, but haven't got around to it.

[Anonymous]

Does anybody have any tricks for manipulating the matchline annotation labels when doing a top/bottom plan sheet?  I end up exploding the labels in my base, then explode the blocks, then copy the mtext from the base to the intended drawing, pasting, and then editing to either call out the previous/next sheet, or "SEE ABOVE"/"SEE BELOW".

I've thought about creating a block I could insert at the matchlines with attributes that could be easily editted for each instance, but haven't got around to it.