DynamoDS / Dynamo

Open Source Graphical Programming for Design
https://dynamobim.org
Other
1.74k stars 634 forks source link

Wish: New node - XYZs from placed ACs, Repeaters & CWPs #444

Closed andydandy74 closed 8 years ago

andydandy74 commented 11 years ago

It would be great to have a node that extracts placement point XYZs from:

I created a custom node called XYZs From Adaptive Components using a bit of Python which now lives in the package manager as an example of item 1 in the above list. I don't know whether the other two are actually possible with the current Revit API (I, for one, couldn't figure it out), but I think these would be really helpful tools when working with existing geometry in Dynamo.

kronz commented 11 years ago

I'm seeing a similar request from some fabrication people as well.

kronz commented 10 years ago

ACs and Repeater elements can have their locations meaningfully extracted. We should have a method that can generically extract meaningful locations from ALL revit elements. Currently we only handle loaded families, and we should be able to get similar data for system families. Currently we extract geomcurves from curve based families so we should similarly get this kind of information from floors, walls, etc. Curtain System should be able to get curves for mullions and corner points for panels

LevL commented 10 years ago

Locations need setters. Having locations with extractors only looks limiting to me.

Some Revit elements have location setter (Walls's location curve), some do not (most important donots: sketch-based, including wall elevation profiles and floors).

We need to distinguish location with shared notion between all Revit elements of Geometrical Representation. We have node for its extraction and node for its explode into geometry objects. I hope there is away to extract curtain grid from GRep of curtain wall. At least that should be doable.

Setting curtain grid from Dynamo computed locations is a very exciting possibility to me. It needs discussion and possible Revit API enhancement. I think it will be a killer feature. The alternative is to use divided surface. That workflow has gap: no room bounds are generated. Maybe it makes sense to add node to generate room bounds from face or solid.

If Dynamo provides only extractors for locations, it does look to me as source of likely user confusion (with GRep based nodes).

ikeough commented 8 years ago

I’m closing this issue because it has been inactive for a while. This probably means that it is not reproducible or it has been fixed in a newer version. If it’s an enhancement and hasn’t been taken on for so long, then it seems no one has the time to implement this.

Please reopen if you still encounter this issue with the latest stable version.

Thank you!