Trimble Business Center

 View Only
Expand all | Collapse all

DWG/DXF - Export Error

  • 1.  DWG/DXF - Export Error

    Posted 12-19-2019 06:14
      |   view attached

    I am receiving the following error message when trying to export the linework in the attached vcl as a dwg or dxf.

     

    The linework is imported vector data from vector pdfs.

     

     

    Thank you!

    Attachment(s)

    zip
    DOt Imports.vcl.zip   3.84 MB 1 version


  • 2.  Re: DWG/DXF - Export Error

    Posted 12-19-2019 07:56

    I was able to export it with no errors

    Rackstation - Synology RackStation 



  • 3.  Re: DWG/DXF - Export Error

    Posted 12-31-2019 04:52

    I did a complete uninstall of 5.20.2 and reinstalled and I am still seeing this error message.

     

    This was using the file attached above.

     



  • 4.  Re: DWG/DXF - Export Error

    Posted 01-06-2020 14:11

    Ok, I zoomed extents and "Window Selected" everything and I was able to export a .dxf file. BUT when i use the "Select All" function i get the same error. So then I compared the total number of objects to both selections, I noticed a difference of 250 objects. In the properties window you can see that 250 CAD multi line text is selected when selecting all. Once i filtered those objects I reviewed the properties and I noticed they have a rotation, northing and easting of question mark (?). I changed the rotation to 90 deg and than exported them but now when re-imported they have a insertion point of 0,0 but they did retain the original layer and text for each object. I am also running TBC 5.20.2. 



  • 5.  Re: DWG/DXF - Export Error

    Posted 01-07-2020 07:46

    Thanks for looking into this. I just tested using your steps and that is indeed what the issue is. 

     

     

     

     

    I cannot figure out how those text items got "?" for their rotation.

     

    I tried:

    • reimport sheets
    • import vector pdfs as sheets
    • transform by points
    • move
    • project cleanup
    • convert to linestring
    • explode

     

    None of these seem to reproduce the issue.

     

    I will have to keep an eye on this but at least i know what the cause of the error in the export is now.