So let me circle back to my first post in this chat. The intent in being able to “denote room/space types…” was to be able to include more information as part of the display name like shown in the image
This allows the user to be in control of how they want to sort the spaces. Including the Level or Space Type as part of the display name simply acts as a sort of Prefix. This is due to Architects having a plethora of rooms that may/may not follow a naming convention.
They could have could have 50 rooms with 50 different names and perhaps 20 function as an office, 10 function as storage, and 20 function as conference rooms. Prefixing the Space Type to the name help mechanical alleviate having to select the spaces one by one in the VE to apply whatever properties the user likes.
This is a workflow I have been using for almost a year now and it is one that has saved me a lot of time when working in the VE.
The way I have been appending the Space Type at the moment is by exporting the Revit schedule, concatenating the Space Type and Space Name, and copy/pasting that into the Space Name parameter column.
I hope this is able to provide clarification with the original intent of this post.
That’s an interesting workflow. I’m not sure if I’m for or against. I do think whatever is done from a space type mapping to the VE, it needs to be coordinated with the future development intent in the VE.
I have been advocating for having a more general space type classification on ApacheRoom Data to allow for more easier changing between 90.1 versions without full reassignment of data.
Our solution for such cases, is to develop an app but because of our current limited ability to change the information in Revit that wouldn’t work.
Model Editor is going to change this, as we can easily and quickly develop automated workflows to edit the information in the Model Editor.
@crduggin, I need to learn more about this. I thought one can easily swap the Thermal Templates for rooms once they have been assigned.
It looks like we need an intermediate step during the translation to allow the user to map the Program Types or Rooms to the existing Thermal Templates in VE.
This has been already addressed by adding the Python Script Editor to the Model Editor in August last year. I mentioned it in a post, but I realized I never left a comment here.
The process does what you asked for above by renaming the Pollination rooms inside the Model Editor.
Here is how it works.
Select the property to be exported as user data. In this case, Space Type.
Use this Python code to rename the rooms based on the Space Type.
from model_editor import Editor
editor = Editor()
model = editor.model
for room in model.room_2ds:
try:
user_data = room.user_data["Space Type"]
except KeyError:
# The rooms user_data doesn't have a space type in it.
# The user has forgotten to export them as user data
continue
if not user_data:
# user_data is None
continue
room.display_name = f'{user_data} - {room.display_name}'
editor.update()
Here is a short video that shows the process.
The reason that we didn’t add it to the UI as you suggested above is that not all the incoming rooms and spaces have a program type assigned to them. This method is flexible enough that you can use it with any other room/space properties.
I’m going to mark this as resolved but feel free to unmark it if you have any other questions.
There were two challenges to implementing what you asked for directly: