text on paperspace/model space

should all text and dimensioning be put on paperspace? or is it depending on the nature of the business? what is the pros and cons on either ps/ms?

 

Do a search or just have a look around, this question has been asked and debated ad-nauseaum.

Personally, I find it easier to have all text and dims in the model, but that's just my opinion. I'm sure you'll get many a response to this one.

Good luck.

 

The "correct" solution is "whatever you (or your employer) prefer."
___

 

I prefer m/s for type of work I am doing, engineers keep want to zoom in and out of map area. If I put txt in ps, I need to keep using express tool to change text in space. and also it's easier for me to send files for international office who may be using lower technique, just working on ms only.

but my other dept. put txt on ps for their work. and we are trying to standardize drafting technique.

so I am wondering, if it is depending on the type of work?

 

This depends on the situation. IMHO, some definitely belong on one or the
other. Some times we double up our text because we need it to work in MS,
but then it falls poorly in the Layouts or is at an inconvenient scale or
rotation for the layout.

We do roadway design and traffic studies. In both there is a need to view
the same thing from different scales and rotations in the layouts. On the
other hand, so notes are particular to a layout, and would only clutter up
MS. We also have scenarios of the same drawing with minor traffic flow
difference (without development vs. with development, etc.) that are easiest
to deal with when there is a standard design for the layout with minor edits
for each of the scenarios.

Brad Yarger

on the nature of the business? what is the pros and cons on either ps/ms?

 

I like to x-ref my dimensions & grid lines into my plan sheets (structural).
So I dimension in model space.

Rick

 

<<I like to x-ref my dimensions & grid lines into my plan sheets (structural). So I dimension in model space.>>

You can XREF into paperspace as well.

 

But you can only xref data that is in MS, as you well know Old Cadaver.....so he could not xref dims in PS into another dwg.

We use the rule of thumb;
If it relates to the model it goes in MS. (i.e. dims, labels, notes with leaders)
If it relates to the drawing it goes in PS (i.e. Title block, component table, assembly instructions, BOMs.

But I agree with the other posters that it is entirely dependent on what works for your company. You are right in looking to standardise though....

 

<<But you can only xref data that is in MS, as you well know Old Cadaver.....so he could not xref dims in PS into another dwg.>>

Certainly, but following that posters comment, it seems he has a model of dims and grids already in MS. That model may be XREF'd into PS.

We have a rule of thumb as well, "all anotation in PS". The only thing in Modelspace is the model.

 

pretty much our rules here too. the biggee is; "if the same text needs to
appear on more than one sheet, it is typed once in MS." I don't want to
have to worry about revising/updating more than one occurrence.

seems like in the "civil" world, text in ms is more necessary than some
other disciplines.

 

huh ? it sounds like you *do* have annotation in MS somewhere then.

and I have no need for a "clean" model. all text is on text-specific layers
that can be frozen/thawed as needed.

with your way if i open a new viewport, i gotta do an xref just to have text
appear that would normally just be there already. no thanks.

we don't do twisted 3d views, so there are no worries there.

 

<<huh ? it sounds like you *do* have annotation in MS somewhere then. >>

True, but the annotation is the ONLY thing in that model. If we get the ability to XREF PS elements that'll change.


<<and I have no need for a "clean" model. all text is on text-specific layers that can be frozen/thawed as needed.>>

Nearly every file we produce is a candidate for use as an XREF'd background somewhere else, usually many many times. The effort spent controlling annotation in dozens of subsequent files is mitigated by moving that annotation into PS.

 

for us its quite different, we may never xref drawings across a project at
all (except titleblocks).

with the advent of faster/stronger computers, my need for xrefs has
diminished. Most jobs under 200 acres, I can manage with just one or two
files, not including profiles and details.

to have a different xref for just the text for each sheet would be a
management nightmare.

 

<<for us its quite different, we may never xref drawings across a project at all (except titleblocks).>>

We have several different disciplines utilizing the same background models, XREF is the only way to fly. (BTW, IMMHO, titlblocks are the least intelligent elements to XREF)


<< to have a different xref for just the text for each sheet would be a management nightmare. >>

Missed the point. Just the annotation that would be required to display in ALL sheets would be in the separate file to be XREF'd and XCLIPped. Individual sheet annotation, specific to that sheet would reside in PS in that sheet.