Add property sets to multiple objects - BIM Feeder framework

Civil 3D
,
1

Hello community,
I have recently created a framework for adding property sets for AutoCAD objects. The connection between property sets definition and object is done by autocad layer.

What is the tech stack?

  • Civil 3D 2024 and newwer
  • dynamo
  • python
  • Civil 3D toolkit package
  • my own package called #yourC3DFeeder

What is the idea?
The idea is to

  • define your property sets in JSON format
  • create a corridor
  • export solids to autocad layers based on shape code
  • run script and have property sets defined in the solids

Everytime a corridor is created, changed you can simply add properties like that. You can even model some object on specific autocad layers and use the script to add properties to objects.

Everything is available on github so check it out and use it and do not forget to go through sample which helps you to understand the principle :slight_smile:

2

How do you want to use the C3D Toolkit in Civil 3D 2025 and higher?

3

Hello @Anton_Huizinga I believe that Civil 3D toolkit can be used in Civil 3D 2025. If not, I would be suprised, there is no problem to change the nodes that are responsible for adding properties from C3D toolkit to native dynamo nodes which should do it as well from 2025.1 i believe?

4

Civil 3d toolkit does not work in civil 3d 2025 or above, and i have posted this previously about this. One to be very much aware if relying on this package in civil 3d 2024, as it will have to be re-worked in the later versions

5

Thank you, I did not know that. But still there is no problem to change nodes from Civil 3D toolkit to native Civil 3D nodes that do the same functionality (adding psets, filling properties and selecting multiple elements - i think that is all I use)

and just to make it clear… my package use python only to prepare objects into lists and it also process the JSON property set definition into correct dictionaries. No API magic is done inside my nodes. All of this is done by Civil 3D toolkit

6

Having worked with a LOT of users who have struggled mightily to update graphs from 2024 to 2025, there is more difficulty than you make it out to be. That said, if all you are doing is property sets, then likely you can quite quickly convert to out of the box nodes.

However as a general guideline it’s best to author in 2025 or at least avoid the Civil3D toolkit in 2024 going forward as there is no reason to not update as the DWGs are completely backwards compatible for people who aren’t on the newer build yet (or at least that is my understanding), and we are now more than half way though the end of life period for the Civil3D toolkit (24 is down to the last ~19 months of it’s ~48 month support cycle). This will prevent advanced workflows you might author that don’t have an easy replacement from being unable to be used in the new builds.

7

Further to what Jacob has said, i would add that you should make sure it works in Cpython engine in Civil 2024 and 2025.

If it does then you will likely have no issues, but if you use ironpython then you may have issues in 2025 when you will likely have to switch to cpython or pythonnet3 in civil 2025 or above.

8

Thank you guys. In the matter of python language I have no doughts. CPYTHON is used in the script. Once we are allowed to use newer version of C3D in our company, I will check and update nodes for newer versions. In the meantime community through github can verify that :slightly_smiling_face: