Skip to main content
Question

Data created in AutoCAD 3d using snapping is no longer coincident when imported into geodatabase. How can I maintain this coincidence exporting to a file geodatabase?

  • November 9, 2017
  • 3 replies
  • 21 views
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

  • Author
  • November 9, 2017
To clarify, this would be 3d CAD data importing into 3d GIS file geodatabase.

 

 


danilo_fme
Celebrity
Forum|alt.badge.img+52
  • Celebrity
  • November 10, 2017

Hi @jaxelrod,

Could you share us the screen your Workspace?

Thanks,

Danilo


fmelizard
Safer
Forum|alt.badge.img+21
  • Safer
  • November 11, 2017
If you could attach a sample AutoCAD 3d file and workspace that exhibit the problem that would be helpful. It must be that the inputs are not actually coincident but are being drawn that way. Examining the input file in the FME Data Inspector and looking at the exact floating point values of the X/Y in question should provide that.

 

 

If that ends up being true, then using a Snapper transformer with a very very tiny tolerance should bring those points together numerically.