The Global Archicad Community

Stay informed. Get help. Share your knowledge.

Plan, Section, Elevation, Schedule, Layouting...

Moderators: ejrolon, Barry Kelly, Karl Ottenstein, LaszloNagy, Gordana Radonic, nbalogh, gkmethy, mnguyen

What is your opinion about this Wish?

No votes
Not Important
Not Needed
I've written many posts over the years regarding Keynotes, and I continue to send my wishlists to Graphisoft. I have experimented with both Properties and Classifications as a source for Keynote descriptions, and I've found that either would work. Currently, my template uses Properties, but they use an Expression to automatically number the Keynote based on the Masterformat (USA) division, which is an available Classification. Though it's in there, it's unworkable. Neither of these is the problem.

The real issue is the limited Criteria parameters for the Schedules. Extracting the Keynote Legend is problematic because:
1. I only want to create a separate Legend for each Layout (or could be by Drawing or View) showing those items that are visible and noted. There is no way to filter Schedules to do this automatically. This is possible using old AutoCAD's Database Extraction tool, for heaven's sake!
2. Keynote information resides in the element being noted, not the Label. There is no way to Schedule Labels; they are not available. If there was a logical indicator as to whether an element was labeled, it would work. So, there is no way to automatically know if an Element's Keynote Label actually exists or not. You may be scheduling elements that have no note, which is wrong.
3. Schedules are unaware of what Layout, View, or Drawing an element appears in. A filter criteria similar to Changes, which ARE Layout-aware, would be needed to identify where the element is. Otherwise, you can only create a legend of all of the Keynotes in the whole project; not very practical or helpful.
4. A Property could be used (with an Options List) to manually choose which Drawing/Layout the Keynote appears on. However, there is no way to connect that to the visibility or the Label, which would generally be identified by Layer. It's too easy for a User to show a Label on the Ceiling Plan, but the Keynote shows up on the Floor Plan Legend. There needs to be more connection between Properties and Label visibility.
5. None of this accounts for Keynotes that are informational, and do not point to one specific Element. A Keynote like, "Connect wall to foundation at this condition in this way", would need to arbitrarily be in either the Wall or the Foundation, and then that element could not have it's own identifying Keynote. Ability to Schedule independent Labels would be helpful, or we could create "dummy" Objects.
6. Keynoting Sections and Elevations is a further conundrum. For instance, elements from the East and West Elevations show up in my North Elevation, in profile. I only want Keynotes shown on the North face of my building to be Scheduled. They should only be noted in the appropriate View where they are labeled, which is subjective. To make matters worse, 2D Objects placed in a Section/Elevation are not schedulable at all.
7. If there is a desire to use a consistent numbering system throughout the Project, so that no two Keynotes have the same number, a sequential number register or other such system would be needed to cross-check. The expressions would need to read/write (PUSH/GET) from a central database, which might be available in GDL, but not Property Expressions.
8. None of these scenarios provides a simple way to create a master list of standard/starter Keynotes for an office. Favorites can be embedded with Keynotes, but this may not account for variations.

I've used MasterScript's Total Keynote system, but it's tricky to use correctly, and most of my staff can't figure it out; plus, it's outdated. CADImage/Central Innovation has a Keynote tool, but it's very pricey for many users.

At one time, a local US company called Undecillion create and AutoKeyNote system, using a separate Object, tied to the old Calculate menu Listing functions (Property Objects, Keys, and Descriptors). They stayed coordinated through TXT files placed in the Library. It was way too complex, and stopped working due to some change in later ArchiCAD versions. There is some vestige of that left, but I don't think Graphisoft is still supporting that database structure. That's unfortunate, since the next step in BIM evolution is complex database interaction. Perhaps JSON and Python APIs, or Grasshopper, can be used to produce something better?
As i understand keynotes, they are alphanumerical codes that refer to a specification list. These codes can be standard or created adhoc by any office. If two different objects share the same specification, they can have the same keynote. One can do an automate a lot with the tools Archicad already has, but sometimes you just want to anotate and specify your drawings manually.

So, a tool that works like an excel spreadsheet, where you write or import you clasifications systems, coding/specifications and make it as hierarchical as you want.
A tool/label that reads from this aforementioned table and lets you select the item you want (as a pull down menu maybe) manually yes, but with full control of it. The tool lets you display just the id, an abreviated name or the full specification based on the scale of the plan or the user needs.
The tool/label can be read so the software knows when it is on a view that appears on a layout and thus generates a table only with the items you used instead of the whole list, but you can also display the whole list if you want. No workarounds, no nothing, just the user and his list and all the errors this can create and let the chips fall where they may.

How difficult can it be to implement something like this?
Tomek Piatek wrote: Thu Jul 16, 2020 12:33 am If anyone from GS is reading this, this feature would be really easy to implement. I know that everyone wants their requests to be implemented above other people's, but this one seems both easy to implement and really useful to the wider audience. Please consider it.
I agree with this! Annotation coordination and consistency in architecture is vital, I can't believe that such an expensive program like Archicad doesn't have this functionality!
Reviving this topic since I need to change my position and agree with Tomek Piatek that Classifications can be used as a Keynote System and that adding the description will make it easier for users. Also we can use it in 24 without the description with a small workaround.
As part of recent projects I have kept working on this and Tomek's way using Classifications is only one click vs mine (Properties) which involves 2 clicks. So one less click to make a mistake.
Basically it is easy to go from this:
Screen Shot 2021-03-21 at 12.27.09 PM.png
Screen Shot 2021-03-21 at 12.27.09 PM.png (55.53 KiB) Viewed 411 times
To this:
Screen Shot 2021-03-21 at 12.09.53 PM.png
Screen Shot 2021-03-21 at 12.09.53 PM.png (140.03 KiB) Viewed 411 times
By just ignoring the Description field.
Top Label reading the info from Classifications and bottom one from Properties.
Apologies, T
To get it to work in Details then the data has to be in the ID and/or in BMat instead of Classifications. That means that as long as Details are not live the info will have to be coordinated in different places.
A work around is to use Worksheets instead of Details since they will "explode" the label. This has other issues.
Another work around is to only use Details as linked markers and use Layers or Renovation Settings to define views which at a different scale.
Thank you for your response ejrolon. May I ask for further clarification on how to use the ID or BMat to create a master list for classification or annotations that would work somehow in the same way as Revit keynotes? I fail to understand why Archicad choses to explode the objects when using a Detail Tool. In my opinion, I find the Revit approach better.
Agree that AC shouldn't explode the labels not the model and it should stay live or at a minimum the created Fill should inherit Classifications and Properties. The reason for IDs and/or BMats is that when AC explodes the model into fills the only data those can have is either in the ID or on the BMat. So you will need to coordinate those between the original object and the exploded fill.
Screen Shot 2021-06-23 at 11.02.48 AM.png
Screen Shot 2021-06-23 at 11.02.48 AM.png (196.55 KiB) Viewed 103 times