Simply put, yes. Several plugins will do this as will Dynamo.


Sent from my iPad using Tapatalk

at its most basic, here's the graph. i think it's just a matter of parsing down the list of panels now.

Hello Ryan,

So you're going to run into one or two problems. Namely, paring the structure of your Excel with the actual panels. But it's all solvable.

I've re-created your example in my own way as follows:



I've generated 100x shuffled Types of panel I want to match. In this case, they are also colour coded.

I want to pair each one within Revit as it appears in Excel. To do so, we need to check if the way in which the panels are sequentially built in Revit matches our system.

I bring through my excel data (Which is just text) and flatten off the listings (As the Curtain panels are a flat list).



I then simply use them as a Key when I'm pairing my panels through the List.GroupByKey method.



As my families are called the same thing as my keys, I can simply use FamilyType.ByName to pull them from the Revit document. If you'rs are different, you'll simply have to create a list of them based around your key list structure.

This gives me the following results:



However, the way the Curtain Panels have been generated doesn't quite match my colour scheme in Excel. So I need to fix my panels first.



What I want is to find out how they panels appear in the list. If I use a simple colour override and pick elements of a full line and one additional, I can see how this builds:



This is showing that my first line is running along the base, then it starts back at the same place, but one line above. You can test this by changing the designscript format.




So what we need to do, is chop up our list using List.TakeEveryNthItem, transpose said list, reverse the sub-groupings and then reverse the entire outer list... rather convoluted I know



But it does give us our result!!

Another approach to make lists match could consist in classifying the panels by their coordinates.

Totally! The problem with geometrical methods is they get heavy, and you can't use Element.GetLocation on Curtain Panels If you have to pull Element.Geometry it get's nasty the bigger the panels are.

You can still use the elements bounding boxes min points, it shouldn't be too heavy to manipulate...

this is the way i approached it, i'm sure there is some consolidation that could take place. this is also assuming that the number of panels in the x and y direction don't change.

Edit: i've also chopped it down a bit, i have 19 panels to choose from, not just the 4 shown here.
I think your Keys approach will allow me to make it much simpler