On Thu, Jun 24, 2010 at 11:22 AM, Jelle Feringa <jelleferi...@gmail.com> wrote: > Conversion from CAD to STL, then STL to STEP and back to CAD is a strange > workflow. The STEP file generated from the STL mesh will be huge and any CAD > program will fail loading it (well, that's an assumption, didn't test). > Furthermore, the conversion from a mesh to a BRep geometry is still an open > issue. > > That is strange indeed. > > According to me, a better way is to generate the STEP and STL files from the > same CAD program. VTK does not handle STEP files and, in a sense, it can be > easily understood : the "V" of VTK stands for "Visualization", whereas STEP > is rather related to modeling. I think that both OCC and VTK should be used > in a complete modeling/visualization application. The salome development > team (http://www.salome-platform.org) recently commited a code named > 'OCC2VTK'. It's not released yet, but it could be very interesting to have > both libraries interoperable. > > Interesting. You even do not need the OCC2VTK ( though I'm excited to hear > about this! ) project. What I recommend you to look into is using pythonOCC > to load your CAD data, grab the vertex coordinates and indices, and use this > to build the mesh in VTK. This is pretty trivial in fact. Look at the MSH > framework in the /contribs directory, this will provide you with a point of > departure. > Take care, > -jelle > _______________________________________________ > Pythonocc-users mailing list > Pythonocc-users@gna.org > https://mail.gna.org/listinfo/pythonocc-users
Actually what I want is from VTK to pythonOCC to then save a STEP file and maybe use pythonOCC to other things. Thanks! _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
