How to copy and paste to coordinates and rotation list

[jobin.e]

Hi,

Using the same procedure of pasting a coordinate (X,Y) list into the command line, can we add rotation angle of each instance also into each line so that each block will have a unique rotation value as per the list. 

Regards

Jo

[jobin.e]

1. How many PAVA blocks do you plan to insert? 700+
2. What are the rotation values for the speakers in the list shown in your image named STEP 1.  
   PA-SPKR-015   94
   PA-SPKR-014   94
   PA-SPKR-013   94
   PA-SPKR-012   94
   PA-SPKR-011   94
   PA-SPKR-010   94
   PA-SPKR-009   94
   PA-SPKR-006   274
   PA-SPKR-005   274
   
   In this area its facing each other so mostly its either of these two. but in other areas the rotation changes more.

[ChicagoLooper]

---

@jobin.e wrote:

<<A static data import to a label will not suffice unfortunately.>>

<<If it does that then great.>>

Why won’t it suffice? Can you explain what you are trying to accomplish with the datalink? 

Are you saying there’s only one ‘great’ way to do this and all other ways are not so great?

How many times will the datalinks be updated? The number of times you plan to update a datalink is helpful when deciding whether such a link will be useful. 

[jobin.e]

@ChicagoLooper 

I'm sorry, I don't mean to contradict your methods. Personally, I agree that if we can import data directly from a spreadsheet with no direct input it should be fine. But this wasn't accepted on the clients side. These files will be handed over and worked on in later phases. So they insist elements with direct linked labels that any party can easily update/modify directly without any master spreadsheet workflow. 

Please don't think I'm saying that this is the "right way". These are constraints that I have to comply with. If a direct static data import was sufficient I wouldn't have posted this as a query. For now I can work with this work around. But in case someone can provide any way to do any of the below, it will massively help my workflow. 

1. A way to directly label using property sets for non civil 3d elements such as blocks. (this will drastically improve my current workflow) (fields don't recognize property set data as input source)
2. Copy already existing set of items with individual coordinates and rotation input.

[ВeekeeCZ · Accepted solution]

 

[jobin.e]

Wow that looks really promising. Is it reading data from block attributes or property sets?

Never mind i looked through the lsp file and it looks like its reading the block attributes. Eager to try this out tomorrow. 

[ChicagoLooper · Accepted solution]

I would take an OBJECT DATA approach. You are taking a graphical approach with 'extended data.' I honestly can't see any value from extended data. Object Data can only be created and understood in Civil3D/Map3D. I don't know why you wish to work in vanilla AutoCad. 

Image-1

Image-1. Even though the block's attribute are hidden, they still have object data (OD). The object data resides on the blocks so you can consider the blocks to be smart blocks. (Think smart phones vs. dumb phones.) The OD enables you to undertake analytical scenarios: How many speakers do you have? How many are rotated at this angle? How many blocks are located over here and how many over there? (Each block has coordinates in your city so analyzing location will not be a problem.)

If you add cost to the OD, you can analyze how many blocks cost this much? How many blocks cost that much?

You can print reports with whatever OD you have and which ever OD you wish to report.

Image-2

Image-2. Each individual speaker block contains Object Data (OD). Depending on how you create your block, the OD can be used to populate the block attributes. In the above example, ASSETID, ABS_CODE and ROTATION has been 'captured' and used to fill in the block attributes. (You can also add more attributes to the block if needed.) The attributes ASSETID and ROTATION were also made invisible so only ABS_CODE is displayed as a label.  When the block are inserted (they are inserted simultaneously not individually), they can be rotated properly. The insertion point and the rotation are taken from the object data or from the coordinates and the rotation angle captured in the object data.

[jobin.e]

I am a bit ashamed to admit that I never explored object data.

I agree, it looks much better than extended data. I have just scratched the surface with some videos about object data. But yes I think this will be a better approach since handling the object data is much more flexible. 

I will definitely check it out.

Thankyou @ChicagoLooper 

[jobin.e]

@ВeekeeCZ 

I tried this lsp out and i must say, it will be a very handy tool for me to label from block attributes whenever i need to. 

And at first i thought you will be giving static mtexts and multileaders that read from the attributes but have no field links. But i was wrong! you did manage to link with the fields!! 

I will be dissecting this lsp with my limited knowledge to see how you did it. but I cant thank you enough for solving my current problem.