Skip to main content

From PDF (back) to DWG

Disclaimer: I was politely asked by Emily Donalds from Cometdocs to possibly feature a post on their PDF to AutoCAD webservice. While wary about advertisement, this is an open and free offer and useful for CAD users.
On http://www.convertpdftoautocad.com you can (obviously) convert PDF files to the AutoCAD DWG format. In a time were probably every single PDF containing CAD drawings was originally created as a digital drawing anyway, it makes sense to optimise on this kind of drawings.


You can go to the website and, without creating an account or registering, you can upload a PDF from your computer. It should not exceed 40MB and you need to be willing to enter your e-mail address, cause the conversion process will happen on their servers.

The service is free and upon testing, was reasonably fast.

The example I tried was a PDF from a elderly care centre provided during a research project and was originally drawn digitally (although I'm not aware of the exact software that was used). I only had access to 2D PDF drawings. The file was about 350 kB so it was fast to upload.

After a short while (a few minutes), I received an e-mail with a download-link. The file stays online for about 24 hours and although the link is not protected, it is including a globally unique ID (guid), so it would be statistically impossible to retrieve links for other files.

The result?

The file is quite large (almost 2 MB), which is caused by the abundance of smaller lines. All dashes and dots from linetypes and all hatch lines become separate line entities. The drawing in itself looks quite faithful considering the loss of information inherent in a vectorial PDF rendition of a CAD drawing.

I detected that it was an AutoCAD 2000 format DWG (the first six bytes in the file contain "ac1015"), which is an old release of the DWG format, making it compatible to almost any software that can read DWG files. This is a good thing.

It opened nicely in Adobe Illustrator CS4, Rhino 5 and ArchiCAD 16 (I don't have AutoCAD installed anymore), where I could detect that three layers were included: the obligatory layer 0 and two layers for all filled solid hatch entities (P) and another for linework (P).

In my first test, the text was not actual text, but a series of lines and polylines, which is less convenient, but this was already the case in the original PDF. A second test, with a PDF with actual full text entities, they stayed real text, on a separate layer (T).

Color information was apparently lost in translation.

For me, personally, it would be a good way to replace a PDF as underlay with a DWG as XRef in e.g. ArchiCAD, since PDF underlays can not be snapped to directly, although you might be able to get usable results using e.g. Illustrator.
Beware, this is NOT an OCR system, so your PDF needs to contain vectorial line drawings, as is usually the case when they are generated by CAD software.
Labels:

Comments

Post a Comment

Popular posts from this blog

Improve usage of BIM during early design phases

When I was collecting ideas for a book chapter on BIM (that seemed to never have emerged after that), I collected 10 ideas, which I believe still reflect good recommendations to improve the usage of BIM during the early design phases. These ideas are related to BIM software, but you can apply them in any flavor, as long as you can model with Building Elements, Spaces and have control over representation. Introduction This article gives an overview of several recommendations and tips, to better apply BIM applications and BIM methodologies, in the context of the early design phases. Many of these tips are applicable in any BIM application and they are based on experience gathered from teaching, researching and using BIM software. Sometimes they could help software developers to improve the workflow of their particular BIM implementation. Tip 1 : Gradually increase the amount of information In the early design phases, the architect makes assumptions and lays out the main design in...
2 comments
Read more

Getting BIM data into Unity (Part 0 - Introduction)

This post reflects on work that I carried out, elaborated during my guidance of a few Master thesis students, to better integrate BIM models into Unity. This will be a multi-part post. This makes each article a bit shorter to read, but allows more in-depth information overall. Hope you like it. Please comment with feedback and further improvements. Basic methodology Unity can import geometry from FBX and Collada (DAE) files primarily. There are a few other formats, but these are the preferred ones. When integrating CAD or BIM files into a realtime environment, you have to convert the geometry. During my Unity teaching and the writing of the book Unity for Architectural Visualization ( buy from Packt ), I’ve come up with a basic diagram explaining geometry exchange between CAD and BIM software and Unity. Throughout these posts, we’ll go more into detail. We start with ArchiCAD, but will tackle Revit in a follow-up post. Promised!
Post a Comment
Read more

PythonOCC : Open Source interactive CAD shell (and how to run it on OSX)

What is PythonOCC? PythonOCC is an Open Source (LGPL) Python-wrapper for OpenCASCADE. So what is OpenCASCADE (OCC)? This is an advanced Open Source (custom license) modeling kernel, comparable to commercial engines, such as ACIS or Parasolid, which are used in quite some commercial CAD programs. When you want to develop CAD software, you could use OCC and write programs in C++. And why using Python? With this wrapper, you can create CAD and geometry scripts in Python, which is an interpreted Object-oriented scripting language. You can write almost "on-the-fly" and seriously reduce the implementation effort, by skipping the compiling-phase. You can even interact with a running program in the Python interpreter. Want to read more about this? The OpenCASCADE official website  (currently Linux and Windows are officially supported) The PythonOCC website/blog  (beware that the core of the actions happen in the development repositories). So far so good. Now the nasty, techn...
4 comments
Read more