Add *.3dm (rhino) file importing

[normanrichardson]

I've been working on a project that converts rhino geometry to shapely geometry using rhino3dm. Its gone fairly well (I think) and its at a place where it could be distributed (I think).

Is there any interest in adding this functionality? Specifically for #66 (any comments @connorferster, @Czarified, @Agent6-6-6). It would be similar to what is being worked on for dxf files. A comparable example is here.

I am happy to add this functionality to #66, following what is in dxf.py.

[connorferster]

I think thats a great idea. Perhaps do a fork of the repo and create a new branch. Add the new functionality as a separate module (like dxf.py, except rhino.py? Or 3dm.py?) and then write some pytest-style tests for it in a new module in the tests directory. I have been teaching a Python course for the last several weeks. Hope to jump back on to sectionproperties in the first couple of weeks in August.

…

On Jul 13, 2021, at 14:04, normanrichardson ***@***.***> wrote:  I've been working on a project that converts rhino geometry to shapely geometry using rhino3dm. Its gone fairly well (I think) and its at a place where it could be distributed (I think). Is there any interest in adding this functionality? Specifically for #66 (any comments @connorferster, @Czarified, @Agent6-6-6). It would be similar to what is being worked on for dxf files. A comparable example is here. I am happy to add this functionality to #66, following what is in dxf.py. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[normanrichardson]

Ok great I'll work on this. Should have it done in the week of the 25-30.

I browsed a little more and I found that the implementation for dxf is here and here inside section.py.

To clarify, if we want to put the functionality under Geometry (as something like Geometry.load_3dm(...)) then making it a separate module (say rhino.py) may not work as we'll get a circular import (as rhino.py will try import Geometry to use the Geometry and CompoundGeometry classes). Does this make sense? Or is there something I'm missing?

[connorferster]

The idea would be to write the “rhino.py” module as a series of pure functions that takes a file path as input and returns a shapely geometry. Then from pre.pre.sections, I can import rhino.py and write a small class method that takes a file path argument and returns a Geometry, using the returned Shapley polygon as the input polygon for the Geometry class. Let me know if that makes sense.

…

Sent from my iPhone

On Jul 16, 2021, at 14:39, normanrichardson ***@***.***> wrote:  Ok great I'll work on this. Should have it done in the week of the 25-30. I browsed a little more and I found that the implementation for dxf is here and here inside section.py. To clarify, if we want to put the functionality under Geometry (as something like Geometry.load_3dm(...)) then making it a separate module (say rhino.py) may not work as we'll get a circular import (as rhino.py will try import Geometry to use the Geometry and CompoundGeometry classes). Does this make sense? Or is there something I'm missing? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[normanrichardson]

Great, this makes sense: the functions in rhino.py will return shapely geometry and not sectionproperties geometry. I will begin implementing this today or tomorrow, and I will let you know if I need further clarification.

[robbievanleeuwen]

+1 to this idea!