Location of a Geodatabase XML Schema Document?

3073
13
01-04-2012 12:53 AM
by Anonymous User
Not applicable
Original User: tomlind

Hi,

we are trying out the Sparx Enterprise Architect ArcGIS module, and are having problems to import xml-files generated by EA in ArcCatalog 10 sp3 (parsing error). We are contacting sparx support. Meanwhile we would like to validate the XML-files against a ESRI Geodatabase schema-document but cannot loacate such a schema. The xml-files generated by ArcCatalog and EA both contains

<esri:Workspace xmlns:esri="http://www.esri.com/schemas/ArcGIS/10.0"...

but no schemalocation is provided.

Does anyone know if an "official" ESRI Geodatabase schema is published, and where?

Thanks
Tomas
0 Kudos
13 Replies
BenConstable
New Contributor

The spatial reference was missing on the feature dataset
...
I had done some copying and pasting in the first iteration, reassigning polygon/polyline/point stereotypes.


Hi Stephen,

Setting the spatial reference info is a step I forget at least every second time I create an arcgis model. Fortunately, implementing an arcgis model validation routine is on Sparx's to do list, so we'll get a reminder in future...

Regarding the switch between feature class stereotypes, it's probably easier currently to create a new element of the desired stereotype and drag across whatever fields etc. you have in the old element. Otherwise there's a bit of manual tweaking of tagged values to get it right. It would be nice to have a conversion function say from the ArcGIS extension menu. Hopefully we'll see something like that in a future release.

Regards,
Ben
0 Kudos
by Anonymous User
Not applicable
Original User: doveydee

Hi all,

Like several others in this thread, I am trying to import an EA generated xml doc into ArcGIS as per the EA tutorial.  I am using EA version 9.3.932 and ArcGIS (ArcCatalog) version 10.0 buil 2414.

I followed the EA tutorial (Modelling and ArcGIS geodatabase with UML and Enterprise Architect) verbatim, and after reading this thread, I made certain that the spatial references were added.

I exported the EA xml doc following the directions in the tutorial, created a new file geodatabase and attempted to import the xml doc into my new file geodatabase using the schema only option.  Like others in this thread, I got an error:
'Import xml data failed
FDO error: -2147186428 [XML parse error: Unspecified error [Line: 285,column:23].]"

I did not find a resolution to this error in the thread postings here.

Since I am following the tutorial, is there something that I am missing?

I have attached the xml doc that I generated from EA as a result of following the tutorial.  A resolution ASAP is truly appreciated.

Thanks,

DD
0 Kudos
RodolfoMoreno1
New Contributor II
Hi All,
I have EA 9.3.935 and I have created a ArcGIS model. I exported this model and next I try to import with ArcCatalog 10.1 and I get "Import xml data failed" message. I supposse that EA 9.3.935 does not work with ArcGIS 10.1. If so which EA version should I have ?.    Thanks in advance.
0 Kudos
by Anonymous User
Not applicable
Original User: sparxesri

This is a late follow-up to Rodolfo's post, but hopefully will be of help to others in the same situation...

The current version of Enterprise Architect is 10.0.1009. This works with ArcGIS 10.2 (and should be compatible with ArcGIS 10.1 and 10.0). I'd recommend using Enterprise Architect 10.0.1009 if possible.

Likely of interest to Rodolfo and others that posted to this thread is Enterprise Architect's model validation script for ArcGIS / UML models. The script and instructions are available from:
http://www.sparxsystems.com/arcgis/model-validation.html

It performs quite a detailed analysis of the modeled schema, starting from the Workspace package down. It will find the common modeling errors and report things like missing spatial references etc.

Also, look out for the next minor release of Enterprise Architect (10.0.1010). It will include numerous enhancements for ArcGIS modeling. The model validation capability will also be included in the installer, rather than requiring a script be separately downloaded.

Regards,
Ben
0 Kudos