Intro to Visio and UML Modeling (Visio 2003/ArcGIS 9) GISC 6383 UT-Dallas Briggs 9/26/06

Microsoftss Visio is a general purpose diagramming program. Its strength is the existence of dozens of
templates which set up the page and stencils which contain pre-drawn shapes. Although you can start
from scratch if you wish, this is seldom wise. Normally, you select an appropriate template for what
you want to do (draw a map, produce an organization chart, PERT chart, database diagram, computer
network diagram, etc.) and then drag and drop the pre-drawn shapes and arrange as desired. A stencil is
available for producing UML diagrams.
If you encounter problems accessing Visio, you might try to logon using the generic
sslab/utdallas local account with Domain set as this computer.
Begin by copying the folder p:\briggs\g6383\uml to c:\my documents
This example is based in ESRI Designing Databases Using ArcInfo
Drawing a Map with Visio
1. Open Visio and Select appropriate Template
Go to Start/All Programs/Microsoft Office and select Microsoft Visio 2003
Click Cancel button to dismiss the splash screen (if it appears).
Go to File/New/Map/directional map(US units) to select the directional maps
template
2. Stencils are shown down the left side
--the Road Shapes stencil should currently be open, displaying its road shapes
--click another stencil name (e.g Transportation) to show available shapes from that stencil
--go to File/Open/My Documents/UML/US Canada & Mexico.vss
An additional stencil is added to the list. It contains outlines of states.
You can make any additional Visio stencil (and its shapes) available this way.
3. Drag the Texas outline onto the drawing page
--use the object handles to resize the outline to be about 6x 6
--note that geographic accuracy is NOT maintained since you can change the aspect ratio!!!
--click the Road Shapes stencil to display its shapes
--drag a bridge shape and place it over the Red River
--drag a road shape (square) and have it go N/S over the bridge
--drag a second road shape (round), connect to first and angle at 45
--drag the IH marker symbol and place on 1st road
--double the IH marker and you can change its number to 35
--drag another IH marker place it on 2nd road and number it 45
--click the Landmark Shapes stencil and drag a North arrow onto the page
(dont ask me why a North Arrow is a Landmark!!!)
--go to File/Save and save the document as c:\usr\init\Texas
4. To work with several drawings simultaneously, simply open another template with
--File/New/Map/Directional map (or any other type of template)
--select the one you wish to work with using
Window pull down menu to select by name
Or ctrl/Tab to scroll through all open drawings
--close all drawings by successively selecting File/Close (no need to save any)
Drawing a UML Diagram---generic approach
5. Open Visio (if not already open). Cancel splash screen if necessary and go to:
1

File/New/Software/UML Model Diagram (US units)

There is an additional Window on left side: Model Explorer (UML Navigator in Visio 2000)
--use this to manage separate drawing pages and other components of your data model

If you close these windows, re-opened by going to UML pull down menu.
Close the Pan &Zoom window to give you more space.
6. There are a variety of stencils for use at different stages of the design process. For example, the
UML Use Case stencil is used for modeling the users needs as discussed in class. In this demo,
we will concentrate on modeling the data, so click on Static Structure stencil to open it. It should
have shapes such as Package, Class, Data Type
--the Static Structure Diagram is the main type of diagram used in UML modeling
--Static Structure diagrams are used for both Logical Modeling (in essence, E/R diagrams) and
can then be developed into Physical Models specific for ESRI GDB via ArcCatalog.
--however, Visio knows nothing of ESRI as yet, which is how it should be since we are in the
Conceptual stage of the design
7.
8. Draw Generic UML Static Structure Diagram
--from UML Static Structure stencil, drag two Class shapes onto page and arrange vertically
--what are classes?
--zoom in to about 150% (use View/Zoom/150%, or type 150 in the Zoom box on toolbar)
--double click the top class box to open its Properties dialog
In Categories box, click Class, and then for Name, enter Vehicle
place check in boxes for: IsRoot and IsAbstract (what does this mean?)
Click Attributes tab, and click New button
In Attribute column, enter SeatingCapacity, (note: no spaces in names!)
In Type column
select VB::Integer
Click OK to close dialog
--from UML Static Structures stencil, drag a Generalization onto the page
Connect triangle end to Vehicle class, and other end to the other class
click any place on the page away from the shapes
be sure that no red appears in the boxes or the line
Double click the lower class box (probably labeled Class2)
In Categories box, click Class, for Name, enter Airplane
In Categories box, click Attributes,, then click the Vehicle tab at bottom.
--the attribute SeatingCapacity is inherited from abstract Vehicle class
Click the tab at bottom labeled Airplane
--click the New button and add the attribute CrewSize as VB-Integer
Click ok to close dialog
9. Note that on the drawing page:
The box name Vehicle is in italics to indicate that this is an abstract class.
The attributes (variables) are listed for each box:
--although SeatingCapacity is an attribute of Airplane, its not listed in the Airplane box
on the diagram. This is for simplicity since we know it will be inherited from Vehicle
where its listed.
10. Note in the Model Explorer window
2

In the Top Package folder, you have:

A diagram called Static Structure-1
A class called Airplane with one attribute (Crew Size)
A class called Vehicle with one attribute (SeatingCapacity)
All these names must be unique otherwise you will get error messages
11. Go to File/Close to close this model. There is no need to save it. If you do, it will be saved as a
Visio document with an extension of .vsd
Drawing a UML Diagram---incorporating ESRI
In theory, we should develop our Conceptual Model independent of any specific database. In practice,
the database decision is often already made:
--we already have other applications developed using this database
--we have already made a decision to use ESRI software
Also, when we use ArcSDE, we can save the Geodatabase in any standard DBMS.
12. Load the ArcGIS UML Model
First, we must load the ArcGIS Visio template which contains ESRI-specific shapes
You will find the template in the gdb folder you copied to c: drive prior to step 1. Its called:
ArcInfo UML Model (Visio 2003).vst
The original for this template is located in the ArcGIS install folder, normally at
C:\arcgis\ CaseTools\Uml Models\
--never work with the original, always copy to a new location!!
In Visio, click File/Open and navigate to
C:\usr\your_initials\gdb and select the document: ArcInfo UML Model (Visio 2003).vst
(click Enable Macros if you get a Macro Virus Warning)
13. Examine the Model Explorer Windowits considerably different than before:

This is the overall folder for the ArcInfo model you

are creating. You may rename if you wish. Click on
the name and change it to MyCity UML Model
Note the Workspace folder. Its critical that all diagrams you create
are located in this folder in the Model Explorer otherwise you
cannot export them to ArcCatalog.

Note the new ESRI types entry listing ESRI data

(and other) types

14. Save under a different name so that we dont damage the template (best done now)
File/Save as, navigate to c:\my documents\uml and name it MyCityUML
3

Save as file type should be set to Drawing (.vsd)

Click Save to save the file.
(If Save as option is greyed, make the Drawing window active)
15. Name your model (if not already done so)
In Model Explorer, click on the text ArcInfo Uml Model (by the green folder) and change to
MyCity UML Model.
Think of this as the overall name for your project.
16. Using Packages for organizing pages and diagrams within the model:
Packages are, in essence, folders for organization information.
Within your UML Model you may have many different pages containing drawings, etc.
These can be organized into Packages, which in essence are folders containing different pages.
A normal way of organization is to have a master
package containing an overall big picture static
structure diagram, and then separate packages for each
of your use cases.
We will now set up the big picture package and then
packages for each use case.
17. Create Big Picture Overview package and associated static
structure diagram
First create a Package to contain the big picture pages.
Right-click on Workspace folder in the Model
Explorer window and select New/Package
In the UML Package Properties dialog window,
specify name as MyCity Overview. Click ok to Close
window
Now create a Static Structure Diagram to be used to
show all classes (tables) in your model
Right click on MyCity Overview package and
select New/Static Structure Diagram
A Static Structure-1 diagram entry appears
in Model Explorer.
Click on this name and change to MyCity Classes
Set the page size for printout via File/ Page Setup (best done before we start drawing)
Under Print Setup tab, be sure Paper Size is letter and set Orientation to Landscape
Under Page Size tab, click Same as printer paper size Click OK to close
18. Add special ESRI classes for the Big Picture representation
In Model Explorer window, double click the MyCity Classes entry to open its page (its blank)
In Model Exp., click on expansion box next to ESRI Classes package to open its contents
Drag the Object class onto the top center of the MyCity Classes Diagram page.
Drag the Feature class onto the page below the object box
Note how the Generalization is automatically added
To zoom to the area you want to work on, select View/Pan&Zoom to open the Pan&Zoom
window (if not already open). Drag the left mouse button to draw a frame surrounding the area
you want to.
19. Set up Packages for Use Cases
For each use case, we will set up a package and include a static structure diagram.
To start, we setup a master USE Case package (folder) to store the packages for each use case.
In Model Exp., right click on Workspace folder and select New/Package
Name the package MyCity Use Cases click OK to close
4

We now set up packages for each use case. To

set up each use case package and diagram:
Right click on MyCity Use Cases entry in
Model Exp. and select New/Package
Name the package Tax_Mngmnt
and click OK to close the Properties dialog
Right click on new Tax_Mngmnt entry in
Model Exp. and select New/Static Structure
In Model Exp., single click on new
Static Structure Diagram-# entry under
Tax_Mngmnt and change
its name to Owner Classes.
Go to File/ Page Setup. Under Print
Setup tab, set Paper Size to letter
Under Page Size tab, click Same
as printer paper size Click Apply then
OK
Repeat the above to set up three more use case packages
A package called Utilities with a diagram called Utility Classes
A package called Property with a diagram called Property Classes
A package called Airport with a diagram called Airport Classes
At this stage, the Model Explorer should look as above.

Packages (folders) have been set up to hold the:

--Overview of all classes
--Each Use Case
--within each Use Case we have a static structure diagram (currently blank)
20. Adding Classes and Modeling Relationships--overview
First, we add the classes to the big picture MyCity Classes diagram (but no relationships).
We then copy classes as required for a specific use case to its diagram and model the
relationships there.
The same class may appear in many use cases.
21. Add real world classes (tables) to the Overview Model
We now add real world classes to the big picture MyCity Classes diagram (and will later
copy them to relevant use case diagrams.)
In Model Exp., double click the MyCity Classes diagram entry to open its page.
21.1
Add the first class:
From UML Static Structures stencil, drag a Class & place on page below Features box.
Double click new class to open its Property Editor and name it Parcel. Click OK.
From UML Static Structures stencil, drag a Generalization & place between these boxes
Connect the Generalization arrow head to the Features class.
Connect other end to the Parcel class.
Drag the Parcel class to the left so that it is no longer directly under the Features box
--the Generalization line should move with the Parcel box
21.2 We now add a second class:
5

From UML Static Structures stencil, drag another Class & place on page below Features box.
Double click new class to open its Property Editor and name it Building. Click OK.
From UML Static Structures stencil, drag a Generalization & place between these boxes
Connect the Generalization arrow head to the Features class.
Connect other end to the Building class.
Be sure there is no red showing on the diagram, or any entry in the Status Window
--these indicate errors. Fix them!!!
21.3 We now add a third class which is not spatial:
From UML Static Structures stencil, drag a Class & place on page by Object box.
Double click the box and name it Owner Click OK.
From UML Static Structures stencil, drag a Generalization and connect arrow head to Object
box, and other end to Owner class.
Since this class does not have spatial geometry it is connected to the object class and not
the feature class.
21.4 Note: the Generalization connections provide for inheritance of attributes. They are not
association or relationships in the sense that we have used these terms. To see their
effect:
double click on the Owner class to open the UML Class Properties dialog,
In Categories box, select Attributes
click the Object tab at bottom of Attributes table
note the ESRI ObjectID variable which has been inherited. Click OK.
22. Copy Classes into the Use Case Diagrams and Model Relationships
If necessary, open all the package folders under Workspace in the Model Exp.
(all expansion boxes need to have a - ; if have +, click it to open)
Note that the MyCity Overview package (folder) has 4 items: the MyCity Classes diagram plus
Building, Owner and Parcel classes.
Note that the MyCity Use Cases package contains only diagrams.
Double click the Owner Classes diagram to open its page (its blank)
From Model Exp., drag the Parcel and Owner classes under MyCity Overview onto the
empty page. Zoom in if needed by changing the red frame size in Pan&Zoom window.
Repeat for Land Mngmnt Use Cases.
Double click Property Classes diagram in Model Explorer to open its diagram
From the Model Exp., drag the Parcel, Owner & Building classes under MyCity
Overview onto the empty page. Zoom in if needed by changing the red frame size.
Note: Although we talked of copying tables from Overview to each use case, in fact these are
more like shortcuts. Its the same table. Its simply present in multiple diagrams. If we change it
in one diagram, changes are automatically reflected wherever the table appears.
(Saved as MyCityUML_A.vsd)
23. Add attributes to the class tables.
Double click Parcel class either in the Model Explorer or the MyCity Classes diagram page.
The UML Class Properties dialog opens. In Categories. box, select Attributes
Be sure Parcel is selected at the bottom of the table (like an Excel worksheet selection)
Widen the Type column (in same way as you do in Excel, by dragging its edge)
Click the New button to add a new attribute
In the Name column, enter ParcelValue
In the Type column, click the down arrow and scroll to esriFieldTypeDouble
Click the Duplicate button to add another attribute of the same type
Name this Tax
6

Click New button again to add a third variable of a different type:

Name this APN (for Assessor Parcel Number) with type esriFieldTypeInteger
Click OK to close the UML Class Properties dialog for Parcel class.
Note that the attributes you added show up in the Model Explorer and on all pages where this
class is used. For example, double click Land Mngmnt Property Classes diagram to open it and
see how these attributes are listed.
24. Set the Spatial Geometry for a feature class.
The spatial geometry is set by default to point and must be reset using tagged values for
polygon or line.
Double click Parcel class in Model Exp., or in the MyCity Classes diagram,
In Categories box select Tagged Values .
Click New to create new tagged value
For Tag enter: GeometryType
no spaces; spelling must be exact;
For Value enter: esriGeometryPolygon
must observe upper/lower case!!!
Click OK to close properties dialog
To display these properties in diagram, right click Parcel box in diagram and select Shape
Display Options. A dialog opens. Place a check in the Properties box and click OK. Make
sure that Parcel is specified as a Polygon in the
diagram. (Note: display properties need to be set for
each static structure diagram separately; they can do
not carryover from one diagram to another)

25. Set tagged values for attribute fields (optionaldo #26 first)
Tagged Values can also be used to set properties for attributes, such as the maximum length
(number of digits) for a string variable.
Double click the Parcel class in Model Exp., In Categories. box, select Attributes
Click the CityName row to select it, then click the Properties button (lower right)
Select Tagged Values tab, then click New button
For Tag enter:
Length
For value enter:
25
and click OK, OK, to close dialogs
26. Adding more Attributes and Spatial Geometry Definitions (optional)
There are more attributes we could add (as in Step #23), and more spatial geometries we need
to define (as in step #24). These are listed below. To save time, we will not do this in class now;
instead, we will later read in a model which includes them.
Add attributes as in Step23
To Owner Class
OwnerName as esriFieldTypeString
OwnerID as esriFieldTypeInteger
To Building Class
Stories as esriFieldTypeInteger
7

Height as esriFieldTypeDouble
BuildingValue as esriFieldTypeDouble
APN (for Assessor Parcel Number) as esriFieldTypeInteger
To Parcel class
CityName, with type esriFieldTypeString
Define Spatial Geometry as in Step 24:
For Building class as esriGeometryPolygon
Saved as MyCityUML_B.vsd (with additional attributes included.)
27. Modeling Relationships: Creating a Relationship Class for 1 to Many Relationship
We will now model the relationship between Parcel and Building.
Double click the Property Classes diagram in the LandMngmnt Use Case to open it.
Zoom in if necessary
From the Static Structure stencil, drag a Composition shape onto the diagram
Connect the diamond end to Parcel and the other end to Building
Double click the line and the UML Associations Properties dialog opens
Name the relationship APNRel (Assesor parcel number relationship)
Under End Name, enter APNRel:Parcel (for the parcel end)
Set its Multiplicty to 1
APNRel:Bldg (for the building end)
Set its Multiplicty to * (for many) Click OK
To have the Relationship name show on the diagram, right click the line and select
Shape Display Options, Place check in Name box.
We now use tagged values to specify the key fields
Double click the APNRel line in the diagram--UML Assoc. Properties dialog opens:
In Categories. box, select Tagged Values
Click the New button
For Tag name enter: OriginPrimaryKey
For Value enter:
APN
Click OK
Click New button again to enter a second tagged value
For Tag name enter: OriginForeignKey
For Value enter:
APN
Click OK
Click New button again to enter a third tagged
value
For Tag name enter: Notification
For Value enter: esriRelNotificationBoth Click OK
Click New button again
For Tag name enter: OriginClass
For Value enter: Parcel
Click OK
Properties dialog should look like this.
Check all spellings, spaces and cases!!!
Click OK to close Properties dialog.
You have created a relationship named APNRel
Its a composite type (implemented via Notification) in which Parcel controls the life
of building. If parcel deleted, building is automatically deleted. (Perhaps not a good idea
since could have parcel consolidation with building remaining!)
Its cardinality is one (Parcel) to many (Buildings).
APN is the key field in the entity classes
(Saved as MyCityUML_C.vsd)
8

28. Modeling Relationships: Creating an Attributed Relationship Class for Many to Many
Relationship.
(only do this in class if time permits)
A Relationship class can have its own attributes (in a table) to describe the nature of the
relationship between the entity objects. These are normally used to model many to many
relationships.
28.1 Add association.
Double click the Owner Classes diagram in the TaxMngmnt Use Case to open it.
Zoom in if necessary
From the Static Structure stencil, drag a Binary Association shape onto the diagram
Connect one end to Parcel and the other end to Owner
Double click the line and the UML Associations Properties dialog opens
Name the relationship OwnsRel (Owners relationship)
Under End Name, enter OwnsRel:Parcel (for the parcel end)
Set its Multiplicty to * (for many)
OwnsRel:Owner (for the Owner end)
Set its Multiplicty to * (for many) Click OK to close.
To have the names show on the diagram, right click the line and select Shape Display
Options, Place check in Names box.
28.2 Add association class
For many to many relationships, an intermediate key table is needed. This stores the key
values needed to match objects between classes, and may also have additional attributes
describing the relationship.
From the Static Structure stencil, drag another Class shape onto the diagram and
position it below the relationship line. Double click the new class to open its properties.
For name enter: OwnsRel
Under Stereotype, choose RelationshipClass (scroll down to find this)
Click OK to close the properties dialog.
(note: the name of the key class table must be same as relationship name)
28.3 Add attributes to key table
Double click the OwnsRel class box and add the following attributes and specify their type
APN--- esriFieldTypeInteger
OwnerID ---esriFieldTypeInteger
PercentOwns---esriFieldTypeDouble
BuyDate---esriFieldTypeDate
SellDate---esriFieldTypeDate
Click Ok to Close Properties Box
28.4 Establish Key fields
Note: this is done with the relationship line, not the key class.
Again, tagged values specify the key fields
Double click the OwnsRel line in the diagram
UML Assoc. Properties dialog opens: In Categories box, select Tagged Values
Click the New button
For Tag name enter: OriginPrimaryKey
For Value enter:
APN
Click OK
9

Repeat this process to add the following tag names and values
OriginForeignKey ---APN
DestinationPrimaryKey ---- OwnerID
DestinationForeignKey ---- OwnerID
Notification ---esriRelNotificationBoth
IsAttributed ---True
OriginClass ---Parcel
Note: OriginClass is necessary when trying to transform the
model into XMI format.
Properties box should look like this when finished. Check all spellings and cases!!! Click OK to
close.
28.5 To Summarize
You modeled a many to many relationship.
Relationship attributes are stored in a key table with same name as the relationship.
The key class table must contain the same key fields as in the origin and destination tables.
The key fields are identified using tags on the relationship (association line) linking the origin
and destination tables.
(Saved as MyCityUML_X.vsd)
29. Modelling Other Geodatabase Capabilities
It is also possible to include other geodatabase capabilities in your UML modeling including:
Feature Datasets
Subtypes
Domains (both range and coded value)
Networks; Connectivity Rules, Edge-Edge Rules, Edge-Junction Rules

30. Exporting Model to XMI and Loading into a Geodatabase via ArcCatalogOverview of Process
Our next steps are to:
(i) export our model to XMI.
(ii) check the model for errors
(iii) Use ArcCatalog to create the Geodatabase schema from XMI
XMI is the industry standard for object repositories. If you are using Visio 2000, you can also
export to MS Object Repository. However, XMI is much faster and preferred to MS Repository
because it is an open standard.
There are three preparatory things you may need to do:
(1) load the model MyCityUML_X.vsi before proceeding. This should not have any errors and thus
will load correctly! It is in the uml folder which you downloaded from P: to C:\My documents\uml
(2) Be sure the file uml.dtd is in the folder where your XMI file will be saved (this can be the same
folder where your Visio files are saved).
This file can be found in C:\Program Files\arcgis\CaseTools\Utilities\ It was already placed in
the uml folder on the P:/ drive, so if you copied this folder to c:\My Documents\uml and are
now saving your files there you should be OK.
(3) If you are not in the computer lab, you will need to install the XMI Export facility on your
computer. Go to http://support.esri.com, search on XMI Export, and follow the instructions in
HowTo: Visio 2003 Professional UML to XMI Export Facility Installation (Article ID 26105)
10

31.

Export our model to XMIdoing it!

(This may not work in the lab.)
Be sure that you have loaded the model Mycity_X.uml
Go to Tools/Add-Ons/ESRI XMI Export---the Save as dialog opens
-- navigate to c:\MyDocuments\uml , and name the xml file MyCityRes.xml, click Save
A status bar tracks the export process.
--When finished, a small window appears showing Export succeeded!; click OK.
32. Use ESRI Semantic Checker to check model before importing into ArcCatalog.
(This checker may not work in the lab.)
Before attempting to import into ArcCatalog, its best to check the exported model.
Go to Tools/Macros/ESRI/SemanticsChecker
--in ESRI Semantics Checker window, select Model stored in XMI button
--Navigate to the XMI file you just created (c:\My Documents\uml\MyCityRes.xml)
Then click Check button.
You will receive either an Error Report or a no errors message.
Close the ESRI Semantics Checker dialog
If you had an error, you will need to go back to Visio, fix the error, and then export the model to
XMI again. Read the error report carefully to get a clue as to the problem. You need to have a
clean model before going to the next step. There is an example error report in
\uml\MyCityRes_Error.rtf. The associated XMI file is MyCityRes_bad.xml and Visio
diagram MyCityUML_bad.vsd You can run a Check on MyCityRes_bad.xml if desired.
33. In ArcCatalog, add the CASE Tool to the ArcCatalog Interface
(May already be there. This only needs to be done the first time you use case tools.)
Start ArcCatalog and go to Tools/Customize and click the Commands tab
In the Categories window, click CaseTools
Drag the Schema Wizard
in the Commands window onto any suitable toolbar
34. Use ArcCatalog to Create a new Geodatabase for your model
Right click on c:\My Documents\um\ in ArcCatalog Table of Contents tree and select
New/Personal Geodatabase
Rename to MyCity
35. Generate the Schema (tables, etc) using your UML Model
In ArcCatalog Display Window (right side), click on the MyCity gdb so that its highlighted.
35.1 Click the Case Schema Creation (Schema Wizard) icon
Click Next to cancel the opening screen
Select Model stored in XMI file button
Browse to the XMI file where you saved your UML Model
C:\My Documents\uml\MyCityRes.xml
Click Next
All the components should be listed in a Schema Wizard window
35.2 Set the spatial Properties of all spatial components.
(some of these properties cannot be changed once schema is created)
11

--to illustrate, we will set properties for Buildings

--doubleclick Buildings in the Schema Wizard window (or Parcel)
Its Properties box opens.
Under General tab, click
on Spatial Reference line.
Under Coordinate System tab, click Import button and select
c:\My documents\uml\dalareacnty.shp
(do not use Select to set the spatial reference system)
We are importing (copying) the spatial reference system from a shapefile
covering counties in the dallas area. The coordinate system can be
changed later but X/Y domain cannot. The X/Y domain establishes the
geographic area covered by the schema. If the domain is not set
correctly now, you will not be able to load data later.
Click OK to close the Spatial Reference Properties window, then OK
again to close the Building Properties window.
35.3 (optional for demo). We should also set properties for Parcels. We do this below, at the
same time illustrating additional concepts regarding Spatial Reference systems. We will
discuss these concepts in more detail next week when we explore creating schema in
ArcCatalog.
Double click Parcels, click

on Spatial Reference line, and Import spatial reference from:

c:\My documents\uml\dalareacnty.shp
(the same data set is also in p:\data\p6382\datasets\coverages\dalareacount)
Before closing the Spatial Reference Properties window, click the X/Y Domain tab
The domain establishes both the geographic extent of the data and the precision (or
resolution) with which values are recorded. Precision affects data accuracy.
Note that Precision is 976:

each foot divisible into 976 units

each inch into 81 units (976/12)
--approx. one hundreth of an inch (.01)
Click Import button again and add \uscounties from p:\data\p6382\datasets\coverages\
Select X/Y domain tab. Note that Precision is 15: each foot divisible into 15 units
Can only record to the closest inch
You can also load Txcnty and see that its precision is 122.
For more information on these concepts, click the About Setting the X/Y Domain button
Should also set M/Z values since these cant be changed later either.
35.4 Final step--Create the actual database schema:
In Schema Wizard window, be sure Workspace is highlighted. Click Next
Summary Screen lists all the tables and relationships to be created. Click Finish
Do you want to see the log file? NO (causes problem with other software!)
36. Use ArcCatalog to Explore the Schema
Double click the MyCity
geodatabase in the
ArcCatalog display window.
Should be:
12

37. Load Data

The schema contains only empty tables. The final step is to load data.
Simple Data Loader (ArcCatalog). We will do this in the next exercise.
Object Loader Wizard (ArcMap)
38. Reapplying Models to Existing Schema
The UML model can also be re-applied to an existing geodatabase schema, including
geodatabases already populated with data in order to update it.
This capability is important for keeping the model up-to-date.
39. ESRI provides sample data models for many areas at:
http://support.esri.com/datamodels
An example for water utilities is at p:\data\briggs\g6383\MyCity
WaterUtilityModel.gif --provides a conceptual overview of the model
WaterUtilityModel.vsd --same as .gif but in Visio format (load into Visio if desired)
WaterUMLv2002.vsd --this is the actual UML model
--open it in Visio
--go to Water Distribution Network folder
--open water distribution network static structure diagram
40. The following documents (originally obtained form the ESRI web) site may be useful
a. How to Create a Geodatabase from a Microsoft or XMI Repository
http://charlotte.utdallas.edu/mgis/classfiles/gisc6383/RepositoryToGeodatabase.pdf
b. How to set the Spatial Reference
http://charlotte.utdallas.edu/mgis/classfiles/gisc6383/SpatialReferenceGeodatabase.pdf

13