For visualization you can use Visualize and Open Cloud (this product specially designed for creating web/Saas application). These products work not only with different CAD file formats, but with BIM as well.
For developing BIM solutions you can use a wide range of file formats:
- Autodesk® Revit® files (rfa/rvt) – BimRv
- IFC files – IFC SDK
- Autodesk® Navisworks® files (nwd, nwc, nwf) – BimNv
You can get 2D and 3D .pdf with Publish SDK.
Yes, we have wrappers for Python2 for the vc15 platform. Wrappers generated using SWIG, that uses CPython technology.
Currently we don’t have trial archives with Python wrappers, but they are available for non-commercial members (and higher).
We have several examples of using the ODA SDK in Python: Drawing \ Swig \ Python \ Examples \ OdDemoViewerExSwigPythonTK and Drawing \ Swig \ Python \ Examples \ OdReadExSwigPython.
Download wrappers for Python here. You will need the following archives: Kernel SDK, Drawings SDK, Python SDK (Kernel.PY & Drawings.PY).
Both products are wrappers above the C++ code.
Drawings.NET Classic is a set of wrappers designed manually using the managed C++.
Drawings.NET is a set of wrappers, generated by means of a swig tool - and is a set of C# wrappers, that use pInvoke to address C++ code.
Both of these products allow to use ODA SDK functionality with managed languages, like C#, C++/CLI, VB. These products are set of wrappers for C++ native code.
.NET Classic (or Drawings .NET Classic) is an API which is identical to AutoCAD .NET API. If you have .NET plugin for AutoCAD, you'll be able to build it for ODA apps almost without changes. You can consider using .NET Classic if you are familiar with AutoCAD .NET API, or if you have existing .NET plugin for AutoCAD which you want to port to ODA based applications.
The disadvantage is that .NET Classic covers less C++ functionality than Drawings.NET. You can request to implement a .NET class from AutoCAD API if it is not implemented yet, but it requires more time than in Drawings.NET (because in .NET Classic we have to implement each class manually, while in Drawings.NET we use automatic code generation).
Drawings.NET (or .NET Swig, or .NET) provides API identical to ODA C++ interface. It provides same classes with same functions and parameters as ODA C++ SDK. On this project we use automatic code generation, so almost all ODA C++ functionality is available.
At the moment, only imports from PDF to DWG are possible with our software. The imported drawing is obtained as a copy of its presentation in PDF. All drawn elements are transferred to DWG in the form of curve sets, texts, images, etc.. The naturally imported drawing is not an absolute copy of the original drawing (which was imported into PDF) as not all data is transferred to PDF from the original drawing.
|Drawings SDK version||.dwg file version|
|2020 Update 1||AutoCAD 2018-2019 (AC1032)|
|2020||AutoCAD 2018-2019 (AC1032)|
|2019 Update 2||AutoCAD 2018 (AC1032)|
|2019 Update 1||AutoCAD 2018 (AC1032)|
|2019||AutoCAD 2018 (AC1032)|
|4.3.2||AutoCAD 2018 (AC1032)|
|4.3.1||AutoCAD 2018 (AC1032)|
|4.2.2||AutoCAD 2013-2017 (AC1027)|
|4.2.0||AutoCAD 2013-2017 (AC1027)|
|4.1.1||AutoCAD 2013-2017 (AC1027)|
|4.1.0||AutoCAD 2013-2017 (AC1027)|
|4.0.1||AutoCAD 2013-2017 (AC1027)|
|4.0.0||AutoCAD 2013-2017 (AC1027)|
|3.9.1||AutoCAD 2013-2017 (AC1027)|
|3.9.0||AutoCAD 2013-2017 (AC1027)|
|3.8.2||AutoCAD 2013-2017 (AC1027)|
|3.8.1||AutoCAD 2013-2017 (AC1027)|
|3.7.0||AutoCAD 2010 (AC1024)|
|3.6.0||AutoCAD 2010 (AC1024)|
You can use ODA archives with SWIG wrappers, which are implemented for some products: Drawings.NET, Publish.NET, Visualize.NET, Architecture.NET and Civil.NET.
Do ODA Products provide ability to parse *.dxf and *.dwg files with the support of modern CAD features (e.g. layers, multiline texts)?
ODA Drawings SDK provides native support for .dwg, .dxf, .dgn files as well as a set of exports and imports. We provide support for old and the most recent versions of .dwg.
BimNv SDK creates .nwd (Model Data), .nwc files (Geometry Cache), .nwf (BIM Data Integration) files.
BimNv SDK allows to combine and review detailed 3D design models from multiple file formats:.dgn, .dwg, .rvt/.rfa.
.dwg, dgn и BimRv (rvt/rfa) can be converted to .prc (3D pdf).
BimRv reads and renders .rvt, .rfa, and .rte files of format versions 2011-2020. File will be saved in the latest version (depending on which release do you use).
Exporting to a Collada, .pdf, .svg, .obj, raster file.
Importing Collada files.
These products are Drawings extensions for civil custom objects, architectural design and mechanical objects. Please use this link to find out more about file formats Drawings SDK works with.
|.dgn||no||yes (import .dgn to .dwg only)|
|.dwf (Drawing Web Format)||no||yes|
|.dwg, .dxf||yes (.dwg only)||yes|
|.nwd, .nwc, .nwf (NwInterop)*||no||yes|
|.pdf (3D PRC-based)||yes||no|
|.rfa, .rvt (BIM)*||no||yes|
|.rcs, .rcp (Point Cloud)||no||yes|
|.sat (ACIS, Version 7 only)||no||yes|
|.vsf (Visualize Stream File)||yes||yes|
* — BIM and NwInterop are not part of a standard ODA membership and require an additional annual licensing fee.
Drawings SDK works with different file formats including .dwg, .dgn, .dwf, .dxb, .pdf, .dae (Collada),.svg, raster formats, .stl, .hsf, Three.js, .pc3, .rcs, .rcp. Drawings SDK saves file in the latest file version.
Supported versions of .dwg, .dxf, .dxb (binary .dxf): starting from ACAD9 and ACAD10 (.dxf and .dxb only) to ACAD2018.
Supported versions of .dwf: XPS, B6, A6, C5.5, A5.5, B5.5, C4, A4, B4, 3D.
|.dgn||no||yes (import .dgn to .dwg only)|
Yes, we already support .rcp and .rcs files, we can import this data in our visualize database and visualize it.