CAD Module is a new optional add-on utility which can be used with Apryse SDK 7.0 or later to convert CAD documents to PDF while preserving layers without any external dependencies. Supported CAD formats include DWG, DWF, DXF, and DGN can be directly converted to PDF using the PDF.Convert.FromCAD
method with this module. Beta support for RVT format is also available on Windows.
You can find more details about how to install CAD Module.
File Format | Supported Versions |
---|---|
DGN | V7, V8 |
DXF, DWF, DWG | AutoCAD R12 and newer |
RVT * | All ✓ |
To use the CAD Module, you must use the PDFNet.AddResourceSearchPath
method with the path to the module's Lib/
folder to include the module files.
Requires the CAD module add-on
If the module has been successfully added, you can use the Convert.FromCAD
method. This method requires that you pass in a PDFDoc
object that will append converted pages to the specified PDF document.
You can also optionally provide a CADConvertOptions
as an argument to change the PageHeight
and PageWidth
attributes for the conversion of the CAD document. If your document is of the RVT format, you can also set the RasterDPI
and Sheets
attributes to control the rasterization resolution and list of sheets to be converted (RVT beta support currently only available on Windows). You must call the AddSheets
method multiple times depending on the number of sheets you would like to add.
By default, layers present in the original CAD drawing will be preserved as Optional Content Groups (OCGs) in the PDF. OCGs can be extracted, edited, manipulated, and removed with Apryse SDK. They can also be rendered into a viewer where users can interact with them.
The CAD Module ships with the CAD2PDFTest sample which can be used to test the conversion functionality using provided test files or your own documents. The sample first initializes PDFNet, which is required for all Apryse SDK functionality, then uses PDFNet.AddResourceSearchPath
to include the CAD Module. The same lines of code can be used to integrate the module in your application or project. Code sample is available in C++, C#, Java, Python, Go, PHP, Ruby & VB.
The CAD2PDFTest sample also shows how to check if a file is of RVT file format and uses CADConvertOptions to convert to PDF (currently only supported on Windows).
For best results, the CAD Module requires access to the fonts (SHX, RSC and TTF) used in the drawing. If the requisite fonts are not embedded in the drawing and not installed on your server, the CAD Module will use its own bundled fonts (located in the in fonts/
folder within the CAD module package) as substitutes for the originals. The specifics of the substitution mappings are defined in a file called substitution.json
(which is also located in the fonts/
folder). If necessary, this file can be customized to define different font mappings or add new mappings. The JSON has following entries:
An alternative way of performing direct substitutions for a font is to provide a font file and name it as "<target_font_name>_fallback
.[ttf | ttc |otf]". For example, if you want to map iso8.shx
to a TTF font, then name your TTF file to iso8_fallback.ttf
and place it in the location discoverable by the CAD Module (you can use PDFNet.AddResourceSearchPath()
to specify the location of the font). Note that the fallback font name must be in lowercase. This method takes priority over the JSON file method.
There are times when a DGN CAD file uses fonts that are packaged in a resource files (.rsc) but these files are not available where the DGN file is loaded from. Without the .rsc files present alongside the .dgn there is no way to get the equivalent font data for the fonts used in the DGN file which are specified using font ID numbers. Font ID numbers may be different from the known standard ones which can be mapped internally to known font names. In this case the DGN may in some cases have font names provided as hints. We can map these names to TrueType font file names.
For example, to map the names Arial, Arial Narrow and Arial Bold, you can add to the substitutions.json the following lines in the fontFileMappings section:
"arial.shx": [ "arial.ttf" ],
"Arial Narrow.shx": [ "arialn.ttf" ],
"Arial Bold.shx": [ "arialb.ttf" ]
You then copy or make available the corresponding files (e.g. arialn.ttf
, arialb.ttf
and arial.ttf
) under the fonts
folder which is in the module binary’s folder, in the same location where the .DGN file is located, or you can use PDFNet.AddResourceSearchPath()
to specify the location of the files.
On Linux CADModule uses OpenGL API for rendering 3D objects. In a headless server environment (i.e., without monitors/graphical drivers) implementation of OpenGL specification needs to be provided. One such implementation is Mesa. On headless Linux you may need to install libgl1-mesa-dev
, libx11-dev
and libglu1-mesa-dev
.
The CAD module has support for optionally applying some style changes that can be when converting a CAD file to PDF.
This section describes the format for the the Plot-styles
JSON object which can be provided by the user to specify custom plot styles when converting a CAD drawing to PDF.
To provide plot style changes/override, a Plot-styles
JSON object can be authored and saved in a .json file. The CAD module tries to load the settings for plot styles from the following locations.
The name of the plot style settings JSON file would be cadstyledwg.json
for DWG files, cadstyledgn.json
for DGN files, or cadstyle.json
if neither of the above was found.
Following is a sample Plot-styles object, the explanatory comments follow the // (although these would not be included in the .json file.)
"Plot-styles": {
// The plot styles object. If missing, no plot styles will be applied
---- "Named-styles": {
// We can have either the Named-styles object or Direct-overrides object (see below) priority is for Direct-overrides if both are present
---- ---- "Input-stb-file": "C:/Temp/test.stb",
// Pathname of an .stb file (AutoCAD styles table.) If present will try to load and apply styles from this file. It takes priority over the Styles object below.
---- ---- "Styles": {
// List of named styles. Named styles can be used together with Layer-to-style-map below to assign a style by name to layers.
---- ---- ---- "Normal": {
// A style name
---- ---- ---- ---- "ColorRGBVal": "00FF2702",
// a Hex color value “AARRGGBB” - can be also be “RRGGBB”
---- ---- ---- ---- "LineWeightIndex": 0
// an index into the Lineweights table (see below.) The index value can range between 0 and 23 even if the Lineweights table below does not override all 24 entries
---- ---- ---- },
---- ---- ---- "New Level Style": {
// another named style
---- ---- ---- ---- "ColorRGBVal": "00FFFF00",
---- ---- ---- ---- "LineWeightIndex": 23,
---- ---- ---- ---- "LineType": "dashed",
// see list of accepted line types below
---- ---- ---- ---- "LineEndType": "bevel",
// see list of accepted line end types below
---- ---- ---- ---- "LineJoinType": "miter",
see list of accepted line join types below
---- ---- ---- ---- "FillType": "solid",
// see list of accepted fill types below
---- ---- ---- },
---- ---- ---- "New Level-1 Style": {
// another named style
---- ---- ---- ---- "ColorRGBVal": "00FF00FF",
---- ---- ---- ---- "LineWeightIndex": 3,
---- ---- ---- ---- "LineType": "iso-dash",
---- ---- ---- ---- "LineEndType": "bevel",
---- ---- ---- ---- "LineJoinType": "miter"
---- ---- ---- },
---- ---- ---- "New Level-2 Style": {
---- ---- ---- }
---- ---- },
---- ---- "Lineweights": {
// default line weights override table
---- ---- ---- "0": { "mm": 1.5 },
// override default value at index 0 with 1.5 millimeters
---- ---- ---- "3": { "in": 0.05 },
// override default value at index 3 with 0.05 inches
---- ---- ---- "23": { "mm": 12.0 }
---- ---- },
---- ---- "Layer-to-style-map": {
// Map of layer names to style names to set on layers
---- ---- ---- "0": "Normal",
// sets the style called Normal on the layer named 0
---- ---- ---- "Default": "Normal",
// sets the style called Normal on the layer named Default
---- ---- ---- "New Level": "New Level Style"
, // sets the style called New Level Style on the layer named New Level
---- ---- ---- "New Level-1": "New Level-2 Style"
---- ---- }
---- },
// end of Named-styles object
---- "Direct-overrides": {
// Direct-overrides object, when present, takes priority over the Named-styles section (see above.) This approach works differently from the styles approach above. Here we specify attributes that correspond to the standard indices for line weight tables and color tables and change the default values for those indices. We then iterate all the layers and objects in a CAD drawing and for each layer or object that has for its line weight or color index one of the indices we
---- ---- "Lineweights": {
// overridable line weight indices for DWG range from 0 to 23
---- ---- ---- "0": { "mm": 1.5 },
---- ---- ---- "3": { "mm": 0.5 },
---- ---- ---- "23": { "mm": 2.0 }
---- ---- },
---- ---- "Colors": {
// overridable color indices for DWG range from 1 to 255
---- ---- ---- "2": "FFFF00",
---- ---- ---- "5": "270200",
---- ---- ---- "7": "2702FF"
---- ---- },
---- ---- "fordgn": {
// the same as above but these apply to DGN CAD files
---- ---- ---- "Lineweights": {
// overridable line weight indices for DGN range from 0 to 31
---- ---- ---- ---- "1": { "mm": 2.5 },
---- ---- ---- ---- "31": { "in": 0.01 },
---- ---- ---- ---- "0": 2.0
// no unit specified means value is mm
---- ---- ---- },
---- ---- ---- "Colors": {
// overridable color indices for DGN range from 0 to 255
---- ---- ---- ---- "1": "FF2702",
---- ---- ---- ---- "3": "00FF00",
---- ---- ---- ---- "0": "FF00FF"
---- ---- ---- }
---- ---- }
---- }
// end of Direct-overrides object}
// end of Plot-styles object
Line types accepted values:
"solid", "dashed", "dotted", "dash-dot", "short-dash", "medium-dash", "long-dash", "short-dash-x2", "medium-dash-x2", "long-dash-x2", "medium-long-dash", "medium-dash-short-dash-short-dash", "long-dash-short-dash", "long-dash-dot-dot", "long-dash-dot", "medium-dash-short-dash-dot", "sparse-dot", "iso-dash", "iso-dash-space", "iso-long-dash-dot", "iso-long-dash-double-dot", "iso-long-dash-triple-dot", "iso-dot", "iso-long-dash-short-dash", "iso-long-dash-double-short-dash", "iso-dash-dot", "iso-double-dash-dot", "iso-dash-double-dot", "iso-double-dash-double-dot", "iso-dash-triple-dot", "iso-double-dash-triple-dot"
Line end types accepted values:
"butt", "square", "round", "diamond"
Line join types accepted values:
"miter", "bevel", "round", "diamond"
Fill types accepted values:
"solid", "checkerboard", "crosshatch", "diamonds", "horizontal-bars", "slant-left", "slant-right", "square-dots", "vertical-bars
Did you find this helpful?
Trial setup questions?
Ask experts on DiscordNeed other help?
Contact SupportPricing or product questions?
Contact Sales