I’m collecting the rooms from a linked model, then trying to get the room boundaries to find points in rooms. The Crumple Room Boundary node is able to provide the boundaries from linked models, although there seems to be an issue where if the bounding element of a room comes from a linked model then the API isn’t able to create the complete boundary and I’m left with thousands of elements. Snip below showing the output of all the boundaries from a level. I do not want to create the rooms myself as there’s thousands of rooms, and the architect has said they will get the room bounding correct so it seems a bit pointless to recreate them if they already exist which is also more of a ‘BIM’ workflow to me. This appears to be an API limitation for Revit 2024 (depending on how accurate this chatbot response this), is there a potential workaround as visually on the floor plan I can see the whole room boundary of the room element, I’m not sure how to read the API docs updates either to see if this has been fixed in newer versions. [image] [image]

The solution I ended up going with: Download the architects models Open these models Reload all of the model links Extract all the boundaries (lines) Fix up any boundaries that don’t form complete polycurves Convert them to a string and export to excel Import the excel to the MEP model Convert from string to line Fix up the boundaries that break on the conversion Transform the lines by the internal origin as the architect won’t fix the internal origin for some of the models Fix up the boundaries that break from this transform Use these complete polycurves to find the rooms where the MEP elements are in It’s a bit painful as we need to complete this process every time we get a new model but seems quite accurate.

I did try this node and for the same rooms that had issues with room bounding it wouldn’t create the solid.

Do you mean the room calculation point? The elements I’m collecting are all MEP elements, so some categories don’t have that option. I also prefer the element centroid as I find it a bit more ‘stable’ than the element.location node, what are you concerns about the centroid accuracy?

I tried this and did a comparison against the room boundaries, and the room boundaries collected more boundaries for every room than the finish boundary. Although the rooms the finish boundary collected all seem to be ‘complete’ rooms which is better for processing if the rooms are bounded entirely within the linked model, while if you look at the preview, the room boundary collection also collected as many boundaries as it could but still ignores any room bounding from a linked element. [image]

[image] RDM: what are you concerns about the centroid accuracy? The edge case of L shaped objects putting centroid in locations which don’t report a useful location is too frequent. The result of which is significant exception handling which slows things down and you still get a lot of false positives. Enabling location point and reporting rooms that way solves the issue and runs faster as there is no need to pull the geometry of the family instances to get the centroid. For the object types which can’t have a room calculation point turned on, the location is the next best solution. If the location is a curve type take the curve geometry and pull the center point; if it is a point then just take the point. From there pull the points to an elevation just above the associated level by adjusting the Z component (pntCheck = Point.ByCoordinates(pnt.X, pnt.Y, lvl.Elevation + 1); and get the room at that point using the room at point method.

I’ll update the script to use the location point, I’ve processed the line based families before so that should be fine. I have seen a few nodes that can take points and rooms, but the internal origin of the linked model is wrong so I’m not sure if these nodes automatically do the transform since I’m inputting linked elements (not rooms from the MEP model), although I guess it’ll be obvious if it doesn’t do the transform because there will be no results.

Hi, Instead of working with linked rooms, why not work directly with spaces ? (a process generally applied to MEP models) [image]

Totally agree I could use spaces, but it’s going to take 10-20 times the effort/time to maintain 10,000+ spaces on this project when the architect already has a requirement to deliver bounded rooms so they’ve done that process for me. I’m very hesitant to use any rooms or spaces as the models are already big enough, if I was to copy spaces in they’d push the file size over to where I’d need to split the models down further. As a workaround to that if I create the spaces in a dummy model then link in the MEP models to find linked elements in local rooms/spaces, it should work but that’s on the assumption that they get all created perfectly without me having to review the space bounding and then raise the spaces up to be slab to slab to capture elements in the ceiling void. Spaces in theory are the solution but why replicate something the architect already created, as this process is simply for the asset requirements (no design parameters required) so it wouldn’t even be necessary to create spaces but also use rooms as there’s more dynamo nodes for finding elements.

Do you have a sample model (not the actual ones but ones which reproduce the conditions) for people to help test on? Stuff like generating the 10,000 spaces (or even 10,000,000 spaces) to do the coordination and then removing them isn’t a big lift.

MEP-Link A.rvt (1.4 MB) I’ve recreated the scenario where the MEP model has Arch-A and Arch-B as model links where the rooms in Arch-A are bounded by Arch-B, I’ll make a simpler version of my script as well for how I had been finding the points in rooms. Arch-Link A.rvt (504 KB) Arch-Link B.rvt (588 KB)

@RDM it’s quite a long thread and I’m not exactly sure what the goal is. Seemed to start off with this [image] RDM: Where the outcome of the script is to find what room an element is in but now is more like how to create the rooms (or spaces) in the first place ?? Distilling it down, is the issue this ?: you’ve got a number of points you’ve got a number of polygons (such as rooms) you want to work out which polygon each point is in, then update the attributes of the point with the polygon attrributes- such as name or mark

Linked Room boundaries being bounded by linked elements

Revit

jacob.small October 29, 2025, 3:55pm 26

The zip file here has a sample graph to generate a playable journal which will run a Dynamo graph on a correctly named .rvt. You can look at how that is structured to generate something which meets your needs.

Topic		Replies	Views
Get room bounding elements from linked models Revit	6	3605	June 12, 2021
Getting linked room boundaries and edge references Revit	9	510	May 3, 2024
Create Rooms by Point list Revit Linked Room Revit	0	959	May 3, 2017
Wall finishes on linked model Revit python , dynamo	9	1309	September 21, 2022
Give parameter from place within bounding box Revit revit , roomboundaries	13	952	August 15, 2018

Linked Room boundaries being bounded by linked elements

Related topics