Hi,
We have a drawing with attributes in the object data of features and willing to create layouts of A3 size at the scale of 1:250. we wish to have solutions for below 2 problems :
1. The attribute data is displaying only at 1 location ( https://knowledge.autodesk.com/support/autocad-map-3d/learn-explore/caas/CloudHelp/cloudhelp/2019/EN...) but we want to have the label in every view port/ layout wherever the feature is appearing.
2. Is it possible to print multiple layouts from the model automatically
Any suggestions will help either from the AutoCad Map3d or by creating any lisp routine.
Thanks in advance !
It can be done using annotative text and/or annotative blocka.
Using anno text and anno blocks will allow the labels to appears in multiple viewports especially where each viewport is given a different VP scale. There are different way to use object data as your label source but there are many variables that must be factored in to achieve your goal, e.g. the quantity of labels, label font height, your final sheet size, whether the labels overlap one another, number of viewports and viewport scales, number of characters in the labels, whether length of label is consistent from one label to the next, rotation of labels, etc., etc........
You will need to provide ultra super detailed information regarding your drawing and your layout tabs for a feasible step-by-step solution. Better yet, upload your dwg and associated xrefs.
Chicagolooper
Thanks for the response ! I tried enabling annotation for text and tried with view ports but the text did not come in all the view ports. please suggests.
I have attached the drawing and the layout for automatic layout generation, grid layer has the boundary which shall be used as layout boundary. Please suggest a lisp routine or way out in autocad for this. I tried to follow the lisp at link :
https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/how-to-create-automatic-layouts/td-p... but this gave error at CVPORT var setting and I could not run this.
Huh? Your drawing needs work. There is no object data residing in your drawing. Yes, you have Object Data tables but that doesn't mean you have object data 'attached' to any entities.
You have taken a single letter, the letter G and made it a block. Your G block is not attributed. Why? It's just a letter G (yaaawn). What's the point? You should've used plain ol' mtext. At least you can change the G to a Q or a V.
Your block is not annotative. This means your block's appearance, the height of your G, will vary when your viewport zooms in and out. I don't think you want the height of the G to vary, you want the height to remain constant regardless of your viewport scale. Correct?
Your drawing units are in feet but your sheet size is metric. Why? If you use VP scale 1:250 this means one foot modelspace equals 250mm? That kind of math doesn't compute, it's wrong.
You have blue lines on a layer named Proposed Center Line but the lines aren't in the middle of the street, they're touching the curb or on the sidewalk. Maybe change the layer name to Off-Centered Line?
The 4Mtr wide road is 3 meters wide and the 8Mtr wide road is 5 meters wide. I could ask why but won't. I give up.
You have a closed polyline named Area Survey Boundary. If you have a certified survey, start with that and go forward without embellishing. Use a metric template, not imperial. Draw in meters not feet.
Next, create an annotative block with at least one attribute. You may, or may not, wish to attach Object Data to the block, it's up to you.
If you want your annotative block to be 5mm tall when you print on A3 sheet, open a new drawing and create a block 0.005 meters tall (5mm=0.005meters). Save the block in your block library. If you don't have a block library, create one.
If you create your annotative block correctly, your new block, when inserted into your drawing, will magically adjust to the correct height relative to your VP scale. This means it will print 5mm tall on your A3 sheet regardless of the VP scale.
If you don't want to create an annotative block you can use use annotative mtext instead. You can create a legend that explains each letter of mtext.
If you are ambitious, create a MapBook to print your layouts. Watch this >>VIDEO<< by Jerry Bartels to see how it's done.
Chicagolooper
explaining the project would be useful to helping you.
In the attached dwg would you explain what each layer that is visible represents?
and what the goal of the project is?
Can't find what you're looking for? Ask the community or share your knowledge.