>> As you probably noticed, I meant 'the IGES file format'. And you're >> right. I changed back the string constants so that commas are no >> longer followed by spaces. Also, handling spaces the same way as >> commas and semicolons in write_freeform() is no more needed. Now, >> using g-iges and iges-g to convert models from *.g to *.igs and then >> back to *.g will result in valid BRL-CAD databases.
Excellent! Really glad to hear the problem was that simple, but it wouldn’t have been easily identified without your efforts and testing. >> Unfortunately, FreeCAD and gCAD3D still don't open the IGES file. I >> inspected the source code of FreeCAD and I found that the function >> responsible of opening IGES files is Part::ImportIgesParts()[1], which >> uses Open Cascade libraries and basically follows the procedure >> described in a tutorial on their website[2]. On that page it is also a >> list of all the entities that Open Cascade can translate into shapes >> and it turns out that entities which are frequently used by g-iges >> such as 322, 406, 168 or 150 are not supported (there actually exists >> support for identifying them[3][4][5][6] and, as I tested, >> Interface_CheckTool::CompleteCheckList()[7] successfully checks them >> against errors, but they can't be converted into TopoDS_Shape[8] >> objects, which FreeCAD processes). That’s not surprising. Even though it was implemented 20 years ago, our IGES exporter is actually rather extensive (with coinciding complexity). Our converter exports rather advanced IGES structures (implicit primitives with Boolean operations) that are sometimes not even parsed by the big commercial CAD engines. Note that you can get that converter to export geometry in different formats or you can try to pre-convert geometry to a polygonal form so it’s more easily readable. What we really want is to have an option for exporting our geometry in BREP/NURBS format, which is not currently implemented by the converter. >>> The entire 5.3 specification is available online: >>> http://www.uspro.org/documents/IGES5-3_forDownload.pdf >> >> The link you provided doesn't work for me, but I found the document in >> many other places. I really don't know how come I didn't find it by >> myself, sorry. No worries. That site might be limited to US-domains or something. We have a copy on our site somewhere too, but it was easier to link them. >> Even if the files generated by g-iges look conformable to the >> specification, I can't be sure whether they are actually correct or >> not because there doesn't seem to be many IGES viewers for Linux, thus >> further testing may be needed. Yeah, the real test is to open one of our IGES exports in one of the big five (AutoCAD, CATIA, Solidworks, NX, and Pro/E). If they all can’t read it, then it doesn’t really matter what the specification says… ;) There are a couple free viewer-only tools from several of those companies that may have IGES support. E.g., Autodesk Fusion 360, Autodesk Inventor Fusion, eDrawings [1], etc. Cheers! Sean [1] http://www.edrawingsviewer.com ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
