Hi,
I've done this in the past but I can't remember how I did it. I'm sure there is a better way now. What we need is to be able to grab the title block information from our drawings and have that information listed in an Excel file or a Word document. I remember placing a .bat in the same folder as the drawings and then choosing the run macro button (or something like that) in one open file. This would create a list of all the drawings in that folder.In other words. My engineer wants a list of the names of the drawings in an excel file. (Not the file names. But the names of each drawing. As an example: 230/69KV Control RoomSwitchgearPSC Panel They are a combination of data fields and simple text. Drawings from last century and this century. Thanks for any and all suggestions.
Jon Summers said:With MicroStation CONNECT, Item Types provide an additional possibility.
I'll take your word for it, but Item Types don't exist in my world so it's not a solution I would offer.
Is Title block data manipulation bi-directional with Item Types?
Kelly Ogle said:We need is to be able to grab the title block information from our drawings and have that information listed in an Excel file or a Word document using MicroStation CONNECT Edition
A Report of text elements might do what you want. The problem, as others have written, is filtering text to know what belongs to your title block.
Here's a step-by-step guide to writing a text report...
Regards, Jon Summers LA Solutions
Barry Lothian said:for harvesting title block data, you HAVE to use tags
With MicroStation V8, you're correct. With MicroStation CONNECT, Item Types provide an additional possibility.
However, tags remain available in MicroStation CONNECT. It's indicative of their value that ProjectWise continues to use tags for annotating title blocks.
Really, for harvesting title block data, you HAVE to use tags. Anything else and your in a world of pain; as you correctly question, how do you differentiate between annotation elements that are title block data, and others of the same type that are not?
Personally, I think the answer is: with great difficulty (it at all possible)
The other thing to keep in mind is how you would "know" what information to harvest. If it's all a text element on one specific level (not shared with anything else) that's pretty easy. If it's a combination of text and text nodes, that's something a little different. If the level has a bunch of other information on it, that's something else. Whatever you decide to do, you need to be able to visualize exactly how to locate the information.
Since you said "last century", I would assume that this isn't as neat as "all sheet models" or something as simple to run through as that, either.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2