Are you getting started with ArcGIS geodatabase design and wondering how UML can help? Have you worked with ArcGIS for years and want a better way to design and
We'll show you how to design, validate and generate a simple geodatabase from the ground up.
In this webinar you will learn how to:
Don't miss this opportunity to learn more about Enterprise Architect
A pre-release of Enterprise Architect 12.1 was used. Upon official release, this will become the recommended version of Enterprise Architect for ArcGIS modeling. You can, however, recreate and edit the example used in the presentation with earlier versions of Enterprise Architect.
Yes. You can download it from this page.
We provide the ability to import models from Visio and suggest a specific model migration process for ArcGIS geodatabase designs created in Visio. For details, please see our Visio Model Migration page.
We also have an upcoming webinar on migrating ArcGIS models from Visio to Enterprise Architect. For details, please see our webinar page.
We encourage users to submit feature requests using our feature request page. You can also access this directly from within Enterprise Architect via the menu: Help | Online Resources | Request a Feature.
Enterprise Architect provides schema design (forward and reverse engineering) capabilities, which include creating standard UML diagrams to represent the geodatabase design. There may be some aspects of the geodatabase that ArcGIS Diagrammer supported that are not yet covered by Enterprise Architect - Annotations would be one example, which we hope to address in future.
We also welcome feedback on your experiences using either tool, and any suggestions to bridge functional gaps: [email protected]
Enterprise Architect and ArcGIS Diagrammer provide two different approaches to visualizing geodatabase designs for ArcGIS. While ArcGIS Diagrammer provides a detailed representation of the geodatabase and likely covers more of the ArcGIS feature set, Enterprise Architect uses the UML standard as its modeling notation. Some advantages of using Enterprise Architect include:
Yes. Even though the example used in the presentation only contained one Feature Dataset, there is no limit on how many of these you can model in your Workspace package. To create additional datasets, simply drag the Feature Dataset item from the ArcGIS Diagram Toolbox onto your workspace diagram.
Furthermore, you can create multiple workspaces in a single model repository (Enterprise Architect project).
As noted in the presentation video at 13:50 minutes, you create a copy of the related fields in the subtype. The easiest way to do this is just drag them from the feature class in the Project Browser onto the subtype(s) in a diagram. Then you can change the field type and initial value.
See pages 26 and 27 of our ArcGIS UML Modeling Tutorial.
See the Help topic: Topology Example.
No. We hope to provide this capability in a future release of Enterprise Architect.
Until version 12.1, Enterprise Architect has not supported the ability to represent the same element multiple times on a diagram. As mentioned in the webinar, Enterprise Architect 12.1 is currently in the pre-release stage and will be made available shortly as a beta release.
As of this version, Enterprise Architect has a diagramming feature/workaround that allows you to represent the same element multiple times on diagrams. The feature is Virtualized Connector Ends. It allows you to draw lines to the same element in numerous places on the diagram.
We plan to discuss Virtualized Connector Ends further during our November webinar, as it appears that it was common practice to use numerous representations of the same element in Visio diagrams. The webinar is about migrating ArcGIS models created with Visio and CASE tools to Enterprise Architect. For more information, see our Visio migration webinar.
Not currently. This is a capability we are planning to add in future though. Currently, you can use Enterprise Architect's Baseline Compare feature to generate a list of model differences, which you can then use to manually update the geodatabase schema. This approach is discussed in more detail in a question from our previous ArcGIS webinar.
It appears that an issue was introduced with the release of Enterprise Architect 12.0.1215. Our development team confirmed the error is specific to this build of Enterprise Architect, and shouldn't occur in previous builds, nor in the upcoming version 12.1, which I used for the webinar.
Fortunately the error scenario is harmless - the system fails an attempt to replace a value associated with one of the Spatial Reference properties, but the final state of that value is correct.
The only model-level setting I'm aware of is the WorkspaceType tagged value. You'll find that on the ArcGIS Workspace package with an option specifically for remote geodatabases - esriRemoteDatabaseWorkspace.
Yes. You reverse engineer an ArcGIS geodatabase from an XML Workspace document, using the menu in Enterprise Architect: Extensions | ArcGIS | Import ArcGIS Workspace XML.
Enterprise Architect does not provide a specific ArcGIS feature to do this for you, but depending on the source and format of the external vocabulary, this might be a task for a Model Script. You could import the data via a script (or even a CSV import) and then create the corresponding Coded Value Domain elements based on the input data.
For details on Automation and Model Scripts, please see the Help topic: Enterprise Architect Object Model.
Not currently. We are considering providing model transformations from more abstract information models to an ArcGIS representation (platform specific model) for a future release.
Yes. We released a set of data dictionary templates with our recent webinars on documentation. These webinars specifically used an ArcGIS data dictionary as the example.
In future we may roll these report templates into the Enterprise Architect installer as well. For now, you can get the templates by visiting the Document Generation webinar page.