Skip to main content
Solved

Missing object data tables


When using the FME Quick Translator to convert CAD from Autodesk AutoCAD Map 3D Object Data to Esri Geodatabase (File Geodb ArcObjects) as raw relational static schema conversion, tables with "_od_table" are created.

When using FME Workbench using the exact same settings, the "_od_table" are not created.

How can I replicate the production of these tables using FME Workbench?

Best answer by fmelizard

Hi @aoakes

Can you confirm that when you are creating the FME workspace that you are using the 'Generate' option. As I understand it the Quick Translator and the 'Generate' wizard should create a workspace which, when run should be producing the same results.

 

 

If so then we would love to see the workspace to see what might be missing.

 

 

Thanks in advance :)

** EDIT: It looks like in some cases (including this one) that the generated mapping file (.fme) form the Quick Translator and the Generated Workspace file (.fmw) from FME Workbench can give slightly different results. In the case of this translation it looks like generating the .fmw produces a more general output with respect to geometry types. For example, both autocad_ellipses and autocad_hatches will go into the same 'polygon' feature type in the Generate the workspace case whereas the Quick Translator keeps these as separate feature types. **

View original
Did this help you find an answer to your question?

2 replies

fmelizard
Contributor
Forum|alt.badge.img+17
  • Contributor
  • Best Answer
  • August 10, 2017

Hi @aoakes

Can you confirm that when you are creating the FME workspace that you are using the 'Generate' option. As I understand it the Quick Translator and the 'Generate' wizard should create a workspace which, when run should be producing the same results.

 

 

If so then we would love to see the workspace to see what might be missing.

 

 

Thanks in advance :)

** EDIT: It looks like in some cases (including this one) that the generated mapping file (.fme) form the Quick Translator and the Generated Workspace file (.fmw) from FME Workbench can give slightly different results. In the case of this translation it looks like generating the .fmw produces a more general output with respect to geometry types. For example, both autocad_ellipses and autocad_hatches will go into the same 'polygon' feature type in the Generate the workspace case whereas the Quick Translator keeps these as separate feature types. **


  • Author
  • August 10, 2017
fmelizard wrote:

Hi @aoakes

Can you confirm that when you are creating the FME workspace that you are using the 'Generate' option. As I understand it the Quick Translator and the 'Generate' wizard should create a workspace which, when run should be producing the same results.

 

 

If so then we would love to see the workspace to see what might be missing.

 

 

Thanks in advance :)

** EDIT: It looks like in some cases (including this one) that the generated mapping file (.fme) form the Quick Translator and the Generated Workspace file (.fmw) from FME Workbench can give slightly different results. In the case of this translation it looks like generating the .fmw produces a more general output with respect to geometry types. For example, both autocad_ellipses and autocad_hatches will go into the same 'polygon' feature type in the Generate the workspace case whereas the Quick Translator keeps these as separate feature types. **

Hi @MattAtSafe,

I am using the "Generate" option. This is why I was confused when I didn't get the same results in the output file geodatabase. I have tried using the "Esri Geodatabase (File Geodb ArcObjects)" and the "Esri Geodatabase (File Geodb API)" with the same results.

The workspace has no modifications or transformers added after generating the workspace.

The workpace can be accessed downloaded from the following link:

https://drive.google.com/file/d/0B-z9kw6vB57UQmZuek5qN3luYnc/view?usp=sharing

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings