Different Scale Views w/ Same Annotation

[mit81]

Any suggestions on how to have views at different scales. Yet keep the annotation through out all views? Can't be a dependent view. Scale has to be the same. Can't be a callout. The annotations do not carry through. Can't be a copy with detail. The annotations don't carry through. Any suggestions.

Thanks.

[tedg]

Any suggestions on how to have views at different scales. Yet keep the annotation through out all views? Can't be a dependent view. Scale has to be the same. Can't be a callout. The annotations do not carry through. Can't be a copy with detail. The annotations don't carry through. Any suggestions.

Thanks.
Why can't it be a "Duplicate with Detailing"? I do this all the time and the annotations carry over (copy).
New sections and other global call-outs show up too.

Yes if you add new text and dimensions, they don't carry over to another view.. if that's what you mean.

[mit81]

The changes and adding of annotations is what I am referring to.

[tedg]

The changes and adding of annotations is what I am referring to.

Yea, I'm not sure what you're asking for is possible.
The only way I have found to do this is to copy the new or revised annotation to the clipboard (ctrl+c) and then paste it ("aligned in current view") into the other view.

[mit81]

Kind of assumed it was not possible. Just curious if I was missing some trick somewhere. My plan was to do exactly what you are saying about copying to clipboard. Oh well, we will just have to stay on top of copying annotations on to the proper views. Thanks

[david_peterson]

Nope, you're only supposed to annotate things once. Why would you want it to have to change it twice?

[mit81]

That's exactly the issue. I don't want to have to change it twice. But, if you have views that need to be at different scales. You have to do it twice or more. I would just annotated what needs to be on the specific scaled views. But, its not my call. It was decided that all annotation was going on an overall. That overall is then put into area views and then that is broken down to section views. Each time a view is broken down, the scale is changing. So it fits correctly on a sheet. Annotations that are on the overall need to show up on the area and section views that have different scales.

[tedg]

Nope, you're only supposed to annotate things once. Why would you want it to have to change it twice?

Well for me, it's when the project has gone out as construction documents, and RFI's and small changes come in.
In some cases we need to capture (copy) part of a plan to become a sketch or similar, so it needs to be a copy with annotation as it exists in the CDs.

And so if small annotation changes are made, we need to make sure they show up on the sketch and the master plan(s), so "record drawings" (as-builts) can be produced later.

That's the main reason I use duplicate with detailing and sometimes copy annotation to other plans.

[david_peterson]

We just take a screen shot and paste it on a PDF after we make the change. Issue the sketch and about once a month we issue the actual CB.
1/8" drawings shouldn't be showing the exact same information as a 1/4" plan.
Things that do need to be the same are things like room and door tags. Tags update automatically.
We've gone the keynoting route. Our new standard practice is to use keynotes for basically everything. No text allowed since you'd have to change it everywhere.

[CAtDiva]

We just take a screen shot and paste it on a PDF after we make the change. Issue the sketch and about once a month we issue the actual CB.
1/8" drawings shouldn't be showing the exact same information as a 1/4" plan.
Things that do need to be the same are things like room and door tags. Tags update automatically.
We've gone the keynoting route. Our new standard practice is to use keynotes for basically everything. No text allowed since you'd have to change it everywhere.

Minor comment ... if you're using the keynoting database, you can choose to keynote text or the number (assuming your family is set up with both). But yes, using Revit's keynoting system is a great way to make sure your notes are consistent throughout the set.

[patricks]

That's exactly the issue. I don't want to have to change it twice. But, if you have views that need to be at different scales. You have to do it twice or more. I would just annotated what needs to be on the specific scaled views. But, its not my call. It was decided that all annotation was going on an overall. That overall is then put into area views and then that is broken down to section views. Each time a view is broken down, the scale is changing. So it fits correctly on a sheet. Annotations that are on the overall need to show up on the area and section views that have different scales.

That goes against pretty much every technical drawing standard there ever was (which is probably the reason why Revit doesn't do it). I don't understand why anyone would want the same info showing on different scale drawings. As drawing scale gets smaller, you run out of room real fast for all the same documentation. Likewise as it gets bigger, the space between notes would get huge.

[tedg]

That goes against pretty much every technical drawing standard there ever was (which is probably the reason why Revit doesn't do it). I don't understand why anyone would want the same info showing on different scale drawings. As drawing scale gets smaller, you run out of room real fast for all the same documentation. Likewise as it gets bigger, the space between notes would get huge.
As I mentioned,
For me anyway, we only do this for additional work being added to the project after the fact such as RFI's and sketches that need to refer to the original plan(s or other views.
Not necessarily different scale.

We would not create a drawing within the set with the same scaled plan and annotations.
Maybe a same scaled plan with different annotation for a different purpose.

[silexz]

This might work:

Use a Detail Group. It can be copied to many different views, and when you update it in any one of those views, the others will follow suit. Yes, duplicate with detailing is grand, but I have eventually found myself chasing annotations to match across views later.

Even better: Pick on model elements that are common to many views, like grids or the property line, and make a model group out of them (yes even 1 single element can be grouped). This then allows you to Attach a Detail Group to them that can be toggled on and off anywhere that elements from that group appear.

Qualm: the slight shifting that text does between scales (and the drooping leaders that happen) is still an issue, so to get around this I have sometimes created very similar Detail Groups that cater to the varying scales, whether attached to model groups or not.

Beauty: seeing all of your annotations and dimensions in the exact same place.

Hope that helps

[Revitaoist]

That goes against pretty much every technical drawing standard there ever was (which is probably the reason why Revit doesn't do it). I don't understand why anyone would want the same info showing on different scale drawings. As drawing scale gets smaller, you run out of room real fast for all the same documentation. Likewise as it gets bigger, the space between notes would get huge.

I've actually been forced by some jurisdictions to provide a site plan on 11x17 for planning AND a site plan showing the same info in the 24x36 CD set. I hacked around it by making my CD set site plan always same scale as the 11x17, duplicated as dependent, and put it on the title sheet with the abbreviations and project info.

[Alex Page]

Or, at least do all your annotations with tags (using type description and instance comments) if you havent got keynoting sorted out: then they all update.
But if you arent using any of the Revit smarts and are just using dumb text, nothing stopping you from grouping the text and placing a group instance on each view: update the group and it updates everywhere.
Don't know how you expect to control exact placement of the note at different scales: sounds horrible!

[Chuckyd67]

That's exactly the issue. I don't want to have to change it twice. But, if you have views that need to be at different scales. You have to do it twice or more. I would just annotated what needs to be on the specific scaled views. But, its not my call. It was decided that all annotation was going on an overall. That overall is then put into area views and then that is broken down to section views. Each time a view is broken down, the scale is changing. So it fits correctly on a sheet. Annotations that are on the overall need to show up on the area and section views that have different scales.

Even though it's not your call, there's a problem with the workflow. Repeating information in that manner automatically creates two huge flaws: 1) It is a complete waste of time, and 2) It is an invitation to errors. Perhaps you could capture the hours spent repeating information and present a cost-saving proposal to your authorities, they could understand.