And if you open the data in FME Universal Viewer? And if you instead of writing the data to ESRI File Geodatabase writes to an FFS and opens it in FME Universal Viewer - is it displayed correctly?
Try to narrow down by reading for instance only the 10 first features and see it these are displayed correctly in FFS / ESRI File Geodatabase.
Hi,
If you have ArcGIS, why not use the geodatabase writer instead of the API?
The
geodatabase writer is ArcObjects based and provides more functionalities.
Hope this helps.
What you are describing potentially sounds like either a geometry issue with one or more features (i.e. a feature with invalid geometry) in the feature class or a spatial index problem. I suspect the former.
I don't know much about the file gdb api, but I'm guessing that this doesn't implement the kind of geometry checks that the native geodatabase writer might. In any case, you may want to use the new GeometryValidator in 2013 to validate geometries before writing to the file gdb.
An alternative is to run the "Check Geometry" tool in ArcGIS to report any geometry issues on your output feature classes and then repair them with the "Repair Geometry" tool.
Thanks for the assist people. The FSS results displayed in the viewer and adding the GeometryValidator cleared up a few issues in the DWG, I couldn't use the simple converter because some dwg layers had hyphens and we all know that databases hate hyphens. Fortunately, I stumbled on the cause... I set the coordinate system on the input dwg file and on the output fGDB. The features that did not behave in ArcCatalog/ArcMAP did not have a projection associated with it in the DWG. Apparently forcing one to it in the process caused the issue. When I took out the coordinate declarations, everything ran fine. I just have to run the CoordinateSystemSetter on the results to finish.
Thanks Again.
-John
