ArcGIS Export Workspace issues

[Thorsten Reitz]

Hi all,

I started evaluating the ArcGIS extension for EA a few days ago and so far I am quite happy. I have noticed a few issues, though:

When exporting the workspace to an ArcGIS XML workspace, in some cases Field and Index elements are placed in the wrong locations in the xml document. Specifically, the field and index definitions are not put under Fields/FieldArray respectively Indexes/IndexArray, but rather directly under DataElement.

Furthermore, if one changes the geometry stereotype of a feature class later on, the shape geometry attribute type is not updated.

I can't really say what triggers the structural errors, but in my model it affected all those Feature Classes with Mutipatch as a geometry type. Any hints are welcome, right now I manually edit the exported workspace xml documents...

Kind regards,
Thorsten

[sxie]

When exporting the workspace to an ArcGIS XML workspace, in some cases Field and Index elements are placed in the wrong locations in the xml document. Specifically, the field and index definitions are not put under Fields/FieldArray respectively Indexes/IndexArray, but rather directly under DataElement.

It sounds like an issue for EA ArcGIS in Build 921. This issue has been fixed after that Build, so I suggest you download the latest EA Build and have a try.

if one changes the geometry stereotype of a feature class later on, the shape geometry attribute type is not updated.

 Currently, the shape geometry does not change automatically if you just simply change the stereotype of a feature class.

"..affected all those Feature Classes with Mutipatch as a geometry type..."

I am guessing the root cause comes from the GeometryDef memo tag for MultiPatch. If you go to «MultiPatch» feature class, locate yourself to "Shape" attribute, then find a tagged value called "GeometryDef". Open this memo tag, inside you will see some settings, make sure one of them should be "GeometryType=esriGeometryMultiPatch;". The "p" should be upper case. This issue has also been fixed in latest EA Build.

Hope this help.