Lab Manual

Geo-database management System Lab manual
Exercise One
1. 1 Conceptual for lab exercise
1.2 Logical Design
1
2
Physical Design
You will test the main advantages of using a geodatabase by performing the following actions:
o Define the common spatial reference using feature datasets
o Organize the features with the same geometry and spatial reference in feature classes
o Define attribute constraints to eliminate edit errors using subtypes, domains, and default
values
o Define spatial and non-spatial relationships using relationship classes
o Add supplementary spatial and attribute behaviors by defining relationship rules for
relationship classes
Exercise Two
2 Creating Personal Geodatabase
it is very helpful to have some base data available for creating exercises and maps. If the data is well-
organized, you can save yourself hours of work when pulling together resources for a class or
presentation. In this short exercise, you will create a Geodatabase that will give you basic data. In the
future, you can add other feature classes to your Geodatabase that you find helpful.
2.1 Creating a new File geodatabase

A file geodatabase is suited to ArcGIS for Desktop users and is stored in a filesystem folder. The main
advantages of a file geodatabase are:
Editing of different feature classes or tables at the same time by multiple users
A maximum size of up to 1 terabyte (TB) for the individual datasets stored in a file
geodatabase
Follow these steps to create a new file geodatabase in ArcCatalog using the context menu:
1. Start ArcCatalog.
2. Select Connect To Folder from the Standard toolbar.
3. In Catalog Tree, select a folder and right-click to choose New | Folder. Rename New Folder as
My-Geodatabase.
4. Right-click the location In the ArcCatalog tree where you ward to create the new file
geodatabase. Point to New.
5. Select Personal Geodatabase. ArcCatalog creates a new personal geodatabase in the location
you selected and sets its name to edit mode.
6. Type a new Geo_database_Your name personal geodatabase.
7. Press Enter.
3
Follow these steps to create a new file geodatabase in ArcCatalog using ArcToolbox:
1. Select ArcToolbox from the Standard toolbar.
2. Go to Data Management Tools Workspace, and double-click on the Create File
GDB tool.
3. For File GDB Location, select Folder Connections, go to <drive>:\ g\Data, and
select the MyGeodatabase folder.
4. For File GDB Name, type Topo5000.
5. For File GDB Version (optional), select the CURRENT option to create a file
geodatabase compatible with ArcGIS Version 10.1, and click on OK.
2.2 Creating new items in a geodatabase
Once you have created Geodatabase, you need to populate it, meaning add items to it. Geodatabase
items Geodatabases organize geographic data into a hierarchy of data objects. These data objects are
stored in feature classes, object classes, and feature datasets.
i. A feature class- is a collection of features with the same type of geometry and the same
attributes. This are the GIS data layers
ii. A feature dataset- is a collection of feature classes that share the same spatial reference. It
is similar to a sub-directory
iii. An object class- is a table in the Geodatabase that stores non spatial data.
2.2.1 Creating feature datasets

When creating a new feature dataset, you must define its spatial reference. This includes its coordinate
system, either geographic or a specific projection, and the coordinate domainsthe minimum x-, y-,
z-, and m-values and their precision.
Steps:
1. Navigate to Geo_database_Your name folder and Right-click on Personal GDB in the
ArcCatalog tree, Point to New and Click Feature Dataset.
2. Type Infra in the name text box.
3. To define the feature datasets spatial reference, Click Next Select Projected Coordinate
SystemsUTM Northern hemisphere
Note: If your feature dataset is to contain feature classes with 2 values (such as topographic
contour) and M values (such as road measure values), you need to set their precision
4. Then Click Next and double click Vertical coordinate systems world WGS 1984.
5. Now you can set M and Z tolerances. But for this exercise leave as the default and click Finish
4
o Using feature datasets is optional depending on the purpose of the geodatabase

o The name should be formed using a concatenation of:
General Descriptor (mandatory)
Projection (mandatory
2.2.2 Creating feature classes

You create empty feature classes in ArcCatalog. When creating a feature class, you choose
whether to create one that stores simple features (points, lines, or polygons) or one that stores
annotation, network features, dimension features, or raster catalogs. You also define the fields it
will contain and the geometry fields properties such as its spatial index and geometry type.
Steps:
1. Navigate to your personal geodatabase D:\Personal GDB and Right-click on
Infra feature dataset in the ArcCatalog tree OR Catalog window New Feature Class.
2. Type Roads in both Name and alias text box.
3. Click the dropdown arrow to select type of feature that can be stored in road feature class
select line feature ( This feature class will store only ESRI line feature).
4. Check in the geometric properties of M and Z values.
5. Click Next and accept the default resolution domainclick Next
6. Click on Geometry in front of SHAPE and check the Geometry type is Line
7. . Add a new Field Name Class
8. Click in the Data Type column next to class and select Double.
9. Click the field next to Default Alias and type Class and field next to default
Value and type 0 to associate a default value with this field
10. In the Field properties click finish
Feature Class Naming Standards

a. No limit on length, however, keep in mind that
b. for data that will eventually be published to SDE, a 32 character limit exists in that
storage environment, and
c. shorter names are generally easier to work with.
5
2.2.3 Creating tables

1. Right-click the database in the ArcCatalog tree in which you want to create a new table.
2. Point to New. Click Table.
3. Type a name for the table. To create an alias for this table, type the alias. Click Next.
4. Click the next blank row in the Field Name column and type a name to add a field to the table.
5. Click in the Data Type column next to the new fields name and click its data type.
6. Click the field next to Alias and type the alias for this field.
7. Click the field next to Allow NULL values, click the dropdown arrow, then click No to prevent
nulls from being stored in this field.
8. Click Finish.
Create a table which show the registrar officers to register the parcel
ID Name Sex Position Work Experience

001 Shemisu Nuru M Chief registrar 19
002 Abebech Yilma F Senior registrar 12
003 Garuma Kumera M Junior Registrar 6
004 Hawa Ali F Junior Registrar 4
005 Rediet Belay F Senior registrar 10
006 Helen H/Mariam F Junior Registrar 5
2.2.4 Adding field to existing feature class in a database

i. Right click on the feature class
ii. Go to properties fields
Add owning type with text data type in the parcel feature
6
2.2.5 Enable editor tracking
Feature services can track who has made changes to the data and when. This information is stored in
fields directly in the dataset.
Editor tracking is a feature of ArcGIS for Desktop that can be utilized by ArcGIS Server to track edits
on feature classes and tables. Editor tracking is enabled using ArcGIS for Desktop:
1. In the Catalog tree, right-click any feature class or table and click Manage > Enable Editor
Tracking. This automatically creates fields for tracking edits (if they don't already exist) and
enables editor tracking.
2. Review the message prompt and click Yes.
3. To review your editor tracking settings, right-click your feature class or table and select
Properties.
4. Click the Editor Tracking tab.
5. Verify your editor tracking settings. You can turn off editor tracking by unchecking the Enable
editor tracking check box.
You must configure editor tracking settings on each dataset individually. You can choose to create a
feature service in which only some of the layers have editor tracking enabled.
Create editor tracking to the registrar file

Add the registrar file to arc map
Start editing the table
What changes do you observe?
7
3. Exercise Three
3 Migrating existing data into a Geodatabase
You can use the Feature Class to Feature Class and Feature Class to Geodatabase tools to import
coverage, shapefiles, and CAD files into a geodatabase. You can also import feature classes from
another geodatabase. When you import several feature classes at the same time with the Feature Class
to Geodatabase tool, each feature class imports into a separate feature class.
3.1 Importing shapefiles into your geodatabase

i. Right-click on your new feature data set and choose IMPORT- Feature Class - single or
multiple. (Single if you have only one layer to load, multiple if more than one).
ii. For the Input Features, click on the folder icon and go to the location of the shape files you
want to import
iii. Select the shape file and click on Add
iv. Give the new layer a name in the Output Feature Class box (e.g., MajorRoads no spaces!)
The output location should default to the feature data set which is what you want make sure it
is NOT specifying a shapefile!
v. You can modify field names if you like.
vi. Click OK For practice, import road layers into this feature dataset
Create a geodatabase and a feature dataset with the name SNNPR GDBMS and
SNNPR_UTM_37. Import towns and Zones of the southern region in to the database from
your Ethio-GIS files
3.2 Importing a feature class (by exporting in to the Database)

1. In the ArcCatalog tree, right click the feature class you want to import.
2. Point to Export.
3. Click To Geodatabase (single).
4. Navigate to the geodatabase or ArcSDE connection you want to import to. If you want to
import to an existing feature dataset, navigate to the feature dataset.
5. Type a name for the new feature class.
6. If you want to create a query to limit the features youre importing, open the Query Builder
dialog box and create a query.
8
7. Review the names in the New Field Name column. If you do not want to use a default, click a
name and type a new one.
8. If you do not want to import one of the fields, click TRUE in the Visible column and
change it to FALSE.
9. Click OK.
10. On the Feature Class To Feature Class tool, click OK to import the feature class.
To the former geodatabase Add only woredas of the region from ethio woreda
with only one field woreda Name
Can you list down the fields and their data type?
9
Exercise Four
4. Domains
Domains are rules applied to a field in a business table that describe the legal values of a field type,
providing a method for enforcing data integrity. Attribute domains are used to constrain the values
allowed in any particular attribute for a table or feature class.
Domains: Constraints which limit attribute values to a numerical range or a list of
possibilities. Domains are defined for the geodatabase and can be applied to multiple
feature classes, tables, or subtypes.
Example 1: Population value in a province. A province cannot have a negative
population value. If we also know that no province has a population greater than
10,000,000, we could set our domain range to 0- 10,000,000.
Attribute domains can be shared across feature classes, tables, and subtypes in a geodatabase.
Whenever a domain is associated with an attribute field, only the values within that domain are valid
for the field. In other words, the field will not accept a value that is not in that domain.
There are two types of domains you can definerange domains and coded domains. Range domains
can only be applied to numeric fields.
Can you list down the types of road in Dilla Town
Prepare a domain for road type (coded domain)
Code Full name description
CSR Coble Stone road
DWR Dry weather road
GR Gravel road
AS Asphalt
4.1 Creating a Domain

Creating an attribute domain through ArcCatalog:
1. Open the Domains tab of the Database Properties window:
2. Right-click on the File Geodatabase -> Properties
3. Choose the Domains tab in the Database Properties window.
10
Domain properties:- When creating or modifying a domain, you must edit the following properties:
4. Enter the domain name and description: Enter the domain name and give it a description in
the Domain Name and Description columns of the top part of the Domains tab. The
domain name will be used to assign the domain to a field and its description is used simply to
describe a domains purpose or use.
Name and description
When creating a new domain, you specify a name that will describe the parameter it
governs.
The characters ' and `, a single quote and an apostrophe, may not be used when naming a
domain.
After a domain is created, when you open the Properties dialog box for a feature class or
table, the domain name is displayed in the domain drop-down menu when choosing a
domain to associate with a given field. The description is a small sentence describing the
purpose of the domain.
Use (name = road type and description = types of road in Dilla town)
Field type: - The field type is the type of attribute field with which the domain can be associated.
The field type can be set to any of the following:
o ShortShort integers
o LongLong integers
o FloatSingle-precision floating point numbers
o DoubleDouble-precision floating point numbers
o Text (Coded domains only)Alphanumeric characters
o DateDate and time data
Once the field type is set, the name of the domain will appear in the domain drop-down
list for any field of that type in the Properties dialog box.
11
Here the domain is created for the type of road which is text
Domain type
When you create a domain, you must specify which type of domain you want to use.
There are two types of attribute domains:
Range domainsA range domain specifies a valid range of values for a numeric attribute.
When creating a range domain, you enter a minimum and maximum valid value. A range
domain can be applied to short-integer, long-integer, float, double, and date attribute types.
Coded domainsA coded value domain can apply to any type of attributetext, numeric,
date, and so on. Coded value domains specify a valid set of values for an attribute.
Split and merge policies

Often, when editing data, a single feature is split into two features or two separate features are
combined, or merged, into a single feature. For example, in a landbase database, a land parcel
may be split into two separate land parcels due to rezoning. Similar zoning changes may require
two adjacent parcels to be merged into a single parcel.
Split policies
An attribute for any given table, feature class, or subtype can have one of three split policies
that control the value of an attribute in the output object:
Default valueThe attributes of the two resulting features take on the default value for the
attribute of the given feature class or subtype.
DuplicateThe attribute of the two resulting features takes on a copy of the original
object's attribute value.
Geometry ratioThe attributes of resulting features are a ratio of the original feature's
value. The ratio is based on the ratio in which the original geometry is divided. If the
geometry is divided equally, each new feature's attribute gets one-half of the value of the
original object's attribute. Geometry ratio policies only apply to domains for numeric field
types.
12
Merge policies
When two features are merged into a single feature, merge policies control the value of
attributes in the new feature. An attribute for any given feature class or subtype can have one
of three merge policies:
Default valueThe attribute of the resulting feature takes on the default value for the
attribute of the given feature class or subtype. This is the only merge policy that applies to
nonnumeric fields and coded value domains.
Sum valuesThe attribute of the resulting feature takes on the sum of the values from the
original features' attributes.
Geometry weightedThe attribute of the resulting feature is the weighted average of the
values of the attributes from the original features. This average is based on the original
feature's geometry.
For this exercise select default for both policies
Coded values
The coded value section is only available for coded domains. It contains the coded values for a
domain as well as an associated description of what that value represents.
The following graphic displays a method of using abbreviated text as coded values to represent
categories of a feature. In this instance, road types categories are represented by roads made up
materials
4.2 Applying a Domain

Once a domain has been created as a geodatabase property it can then applied to fields of tables or
feature classes within the geodatabase.
Applying an attribute domain through ArcCatalog:
1. Open up the properties of a feature class or table to the Fields tab:
2. Right-click on the feature class or table -> Properties
13
3. Choose the Fields tab in the properties window.
4. 2. Select the field to add a domain to:
5. In the upper table of the Fields tab select the field to add a domain to.
6. Apply the domain to the selected field:
7. In the Field Properties box select the domain to apply from the Domain drop box.
Note: Only domains from the current geodatabase that match the field type will be
listed in the Domains drop box.
14
8. Press OK to apply the settings. OR

9. Applying an attribute domain using geoprocessing tools: Use the Assign Domain To
Field tool (located in the Domains toolset within the Data Management Tools toolbox) to
assign a domain to a field.
4.3 Adding coded values in domain created

Add SR as seasonal road as description in the domain you created for road type
Or
go to Arccatalog right click on the geodatabase properties and domain tab
select the domain name from the list of domains ( if more than one available)
go to coded values
add code and discritption
4.4 Editing with a Domain

When editing in ArcMap, a field with a coded value domain applied to it will have a drop box that will
only allow domain values to be selected.
Modifying and deleting attribute domains
15
The Domains property page can be used to delete an attribute domain from the geodatabase or modify
an existing domain. You can modify domains by selecting them on the Domains Properties dialog
box.
The domain type or field type cannot be modified. But the following properties can be modified:
Domain name
Max and min values for range domains
Codes associated with coded value domains
The Description field
Split and Merge policies
1. In the Catalog tree, right-click the geodatabase and click Properties.
2. Click the Domains tab.
3. Click the domain you want to delete by clicking the left tab in the grid.
4. Press the Delete key.
5. Click Apply to delete the domain from the geodatabase, or click OK to delete the domain and
close the dialog box.
16
Each table can have only one subtype.

All the codes have to be unique and valid integers.
All the code, description pairs have to be unique
You cannot add subtypes to an existing table. If you do, it will be ignored and the table will use
the existing subtype, if one exists.
When writing features, the subtype attribute must contain the code (which is stored as an integer
by Geodatabase).
For detailed information, please see the ESRI Geodatabase chapter in the FME Readers and
Writers manual.
17
Exercise Six
6 Working with excel data
6.1 Table Joins
Table Join A table join appends the attributes of a non-spatial table to a (spatial) layer attribute table,
creating one large table. Joins are used when there is a one-to-one relationship that means that for
each geographic feature in the layer there is one match in the non-spatial table.
If the file is/are already exist in excel form
Add table to your geodatabase
RC on the database import table(single) (select farmers list file from GDMss folder
given to this exercise Select the excel spreadsheet which contains the data
Add Ok
Otherwise do a follow
Prepare a Parcel layer which has the following attributes
Parcel_ID Soil Type Area Owning type Land Use Owner_ID Registered_By
0280/02 001/98 001
1565/10 002/99 002
0405/01 003/88 003
1047/11 003/97 004
1316/07 002/89 005
014/02 125/98 006
1238/10 435/99 003
0405/08 556/00 004
0571/05 559/01 005
1448/04 001/98 003
1299/01 001/96 006
1308/01 002/88 005
1423/03 125/97 004
1222/01 435/96 004
1015/10 002/88 005
0288/01 001/98 004
0068/04 001/96 001
18
Write the following data in excel
F_ID Name Sex Age Family Size

001/98 Hayimanot Alemu F 41 2
002/99 Daniel Setotaw M 32 1
003/88 Hawa Yassin F 60 3
003/97 Zebrga Urgesa M 28 5
002/89 Chaltu Debela F 34 4
125/98 Kedija Yimam F 45 6
435/99 Habitemariam Sitotaw M 52 2
556/00 Muhammed Ahmed M 61 1
559/01 Hagos Adgo M 66 3
001/98 Hailu Belew M 45 2
001/96 Chalachew Gizew M 35 3
002/88 Chala Adabo M 52 1
125/97 Rukiya Hassen F 25 2
435/96 Nuriya Dune F 19 1
002/88 Haron Eliyas M 22 1
For Registrar use the following Table you created under Domain Exercise
R_ID Name Sex Position Work Experience
001 Shemisu Nuru M Chief registrar 19
002 Abebech Yilma F Senior registrar 12
003 Garuma Kumera M Junior Registrar 6
004 Hawa Ali F Junior Registrar 4
005 Rediet Belay F Senior registrar 10
006 Helen H/Mariam F Junior Registrar 5
During saving the second and third files use save as type CSV (Comma Delimited)
While closing the file be positive and select ( save, yes ok options only)
Finally add all the three files together with the aerial photograph in ArcMap
Start digitizing parcels in the aerial photograph use the correct parcel ID and Owner Id listed in
the table
From table of content RC on parcel
19
Which field can serve as joining field? Why ? Fill the following table
Table Relate A table relate keeps the non-spatial and spatial tables separate but linked. This means
that if you select records in one table, records in the related table will also be selected. Relates are
used when there is a one-to-many, many-to-many, many-to-one, or one-to-one (less common)
relationship between geographic features and non-spatial data.
Which parcels are owned by Females?
How many of them are registered by Garuma Kumera?
20
Exercise Five
5. Subtypes
Subtypes are properties of feature classes or non-spatial tables. The subtypes gather the features from a
feature class or records from a non-spatial table that share the same attribute values using an attribute
field. The attribute field that groups the features must be of the data type Short or Long integer, and it
will be named the subtype field. A feature class can have only one subtype field. You can assign
different behaviors to individual subtypes from a feature class/table.
A subtype has a code and a description. After you have defined the subtypes for a subtype field, you
can change everything related to a subtype: change the value or description of code, add more codes,
and delete code. The subtypes help you in the geometry editing process and prevent errors when
editing feature attribute values. The subtypes maintain the integrity in a geodatabase.
Subtypes: Rules for categorizing distinct features in the same feature class.
Example: Roads. Normally subject to a national transportation classification system, so
only a few possible values. E.g., Trunk Road, Primary Road, Secondary Road,
Residential Street. With subtypes, we can automatically classify roads as we edit,
saving time and improving data quality.
Creating new subtypes for a feature class or table
1. In the ArcCatalog tree, create a road feature class under your database which has the following
attributes
2. Right click the feature class or table to which you want to add subtypes (in this case on Road).
3. Click Properties.
4. Click the Subtypes tab.
5. Click the dropdown arrow and click the subtype field from the list of available long integer
and short integer fields.
6. To add a new subtype, click the first empty field under Code and type an integer value that will
be the code for that subtype.
7. Press the Tab key or click the Description field and type a description for the subtype.
21
8. For each field, type a default value in the appropriate field in the table.
Add the road layer and look at the table of content. What do you observe?
Start editing the road does it save your time to digitize and add attribute value ? how?
22
Exercise Seven
7 validation
7.1 Creating a topology
Consists of a set of rules structuring the relationship between collections of features in one or
more feature classes in a feature dataset. Which
o uses to ensure data quality and to allow your geodatabase to more realistically
represent geographic features.
o framework for behavior that allows you to control the geometric relationships
between features and to maintain their geometric integrity.
o To develop a behavior enables you to more accurately model the world and Maintain
referential integrity between objects in the geodatabase.
How topologies are built
The validating process proceeds in the following sequence:
1. Cracking features
2. Clustering vertices
When a vertex of one feature in the topology is within the cluster tolerance of an edge of any
other feature in the topology,
o The topology engine creates a new vertex on the edge ( Cracking)
o to allow the features to be geometrically integrated in the clustering process
(Clustering).
To create a topology,
o specify which feature classes will participate
o All feature classes participating in a topology must be in the same feature dataset.) and
o determine rules will govern the interaction of features.
o Specify a cluster tolerance (involves snapping feature vertices together to make them
coincident,)
Vertices within the cluster tolerance may move slightly in the snapping process.
23
The default cluster tolerance is the minimum possible cluster tolerance and is
based on the precision defined for the dataset.
The cluster tolerance should be small, so only close vertices are snapped
together.
Vertices that within the cluster tolerance are defined as coincident and snapped
together.
Cluster tolerance control which feature classes are more likely to be moved in the
clustering process. (adjusted. )
if they fall within the cluster tolerance of another vertex, All vertices of any
feature in a feature class that participates in a topology can potentially be
moved.
Ranks are assigned to the feature classes in the topology to accommodate this
common situation.
The less reliable features to snap to the more reliable ones.
Vertices of lower ranking features within the cluster tolerance will be snapped
to nearby vertices of higher ranking features.
Vertices of features of equal rank that lie within the cluster tolerance will be
geometrically averaged together.
Z cluster tolerance and ranks

24
o Feature classes that model terrain or buildings three dimensionally have a z-value
representing elevation for each vertex.
o if a topology has feature classes that model elevation, you can control how coincident
vertices are snapped vertically with the z cluster tolerance and ranks.
Rule
o define for a topology control the allowable relationships of
features within a feature class,
between features in different feature classes, or
Between subtypes of features.
o The initial validation of the topology checks all the features against all the rules.
o This initial check can take some time, but subsequent checks are performed only on the
areas that have been edited the dirty areas.
Creating a topology using the Catalog window or ArcCatalog

Here is the process used to create a topology using ArcCatalog.
1. Right-click the feature dataset to which you want to add a topology, point to New, then
click Topology. Click Next.
2. Name the new topology and specify the cluster tolerance. The default value will be set to the
x,y tolerance of the feature dataset. A good default value is 0.001 meters
3. Click Next.
4. Next, choose the feature classes that will participate in the topology. You will be shown a list
of all the feature classes in your feature dataset.
5. Click Next.
6. Set the coordinate accuracy ranks for each feature class in the topology.
7. Click Next.
8. Add the series of topology rules that help you structure the spatial relationships between
features and to control and validate how features share geometry.
9. Click Next.
10. Review the summary and click Finish. You have now added the new topology to your feature
dataset. You will be asked if you would like to validate your topology in your feature dataset
now. If you have data in your feature classes, you can choose Yes.
25
Creating a topology using geo-processing

ArcToolbox contains a series of geoprocessing tools for topology. The Topology toolset is located in
the Data Management toolbox.
7.1.1 Using ArcGIS to repair topology (only for one layer)
One of the most common problems in data quality is the presence of gaps or overlaps in polygons such
as administrative boundaries.
Set up the editing environment
Open ArcMap
Import into ArcMap Parcel_Topology
Click on Yes to add feature classes that participate in topology
Set the Editing Parameters In order to perform the editing procedures, it is important to set
the editing parameters as follows:
Change map Units
Go to View > Data Frame Properties
Click on the General Tab
Change Units Display: to Meters Click Apply > Okay
Set up the parameters
If its not already there, add the Editor toolbar to your workspace by going to
View > Toolbars > Editor
On the toolbar, go to Editor > Options
Under the General Tab chose Snapping Tolerance: 50 map units
Under the General Tab choose Sticky Move Tolerance: 1000 map pixels (This
will prevent accidental moves of polygons during the editing process.)
Click OK
Start the Editing Process
Start Editing
Click on Editor > Start Editing
Select the Task: Modify Feature and the Target: Parcel
Set Snapping Parameter
Go to Editor > Snapping
For the Parcel layer, check the boxes for Vertex and Edge
If toolbar not already opened, add Topology Tools
Go to Editor > More Editing Tools > Topology (another toolbar will be added)
26
Repair Overlap Errors

Select Map Topology from toolbar > Select Parcel > Click OK
Go to Topology toolbar > Click on <Map Layers> and Select Parcel_Topology
Select all Overlap Errors using the Error Inspector tool > Show Parcel Must Not Overlap >
Click on Search Now
Select all the errors
Correct the selected Overlap Errors using the Fix Topology Error tool > Right click on the
map and choose Subtract
Verify there is no more error with the Error Inspector tool (by repeating the Search Now
command as above)
Go to Editor > Save Edits
Repair Gap Errors (limited to one polygon at a time)
Zoom to error
Using the Fix Topology Error tool (), select all the topological errors associated with one of the
polygons > Right Click > Select Create Feature
Shows the topological errors selected from Parcel_Topology in black
Select the polygon and the new polygons created using the Edit Tool () or open the attribute
table and highlight the main polygon and the newly created polygons (they will be at the
bottom of the table and have null values).
Go to Editor > Merge to merge the selected polygons. Select the main polygon as the feature
with which polygon will be merged (to keep the Attributed Table information) > Click OK.
Save Edits
Continue for all errors
Additional points
Two vertex editors (one before selection the other after selection)
Cut polygon
Reshape ( select a polygon to be reshaped
Auto complete polygon
Auto complete freehand
27
Exercise Eight
8. Topology with multiple layers
Make you data ready for topology (only for this exercise)
Practical 8.1
Create a folder on D:/Drive with a name Topology_relation exercise
Under the folder create a personal geodatabase called Electrification
Under the database create a feature dataset with the following criterias
o Name == Elect_UTM_Adindan_37
o Use the coordinate system indicated in the feature datasets name
o Import the file given to this exercise in the newly created feature dataset
Create Sub type to Pole as the following
o Add field to show material Type of which a pole is constructed from
with a field name P_Material ,
dont forget to make data type short integer
o Create Sub type as coded as below
1 = Steel
2 = Concrete
3 = Wood
o Edit the table as follow
(make Concrete as default)
the Upper Right corners of the block steel ,
All poles at the end of electric line Wood (except pole Zero)
And the rest corners and Pole Along the side of the block as concrete.
Stop editing
Create Topology
Create a topology
Name Elec_Topology
Xy tolerance 0.01
Participant features == all features in the feature dataset
Rule as follow
What rule will govern

28
o Poles
All poles should be along the electric line
o Electric line
cannot be overlap (share certain edge with other) ,
must not self overlap (over lap edge with its own),
cannot be intersect ( share vertex or boundary),
must not self intersect ,
must be single part,
o Compound and communal land
must not overlap , overlap with
must not have gap, gap with
Feature layers maintained by a topology
o the topology internally stores two additional types of feature classes:
dirty areas and
error features
o these are
Instead of storing topological information with the feature classes,
to discover the relationships when the information is requested, such as when
you are editing using the shared geometry tool.
To help you manage the process of creating and editing a logically consistent
topology,
Errors and exceptions
o Errors and exceptions are stored as features in the topology and allow you to render and
manage the places where features do not obey the topology rules you specified.
o Topologies also store error features, which record where topological errors were
discovered during validation.
o Certain errors may be acceptable, in which case the error features can be marked as
exceptions
Practical 8.3
o start editing base on the topology ( dont complete your editing, left some errors for
the next exercises )
29
Dirty areas
o Dirty areas are areas that have been edited or affected by the addition, update, or
deletion
of features.
o Dirty areas allow the topology to limit the area that must be checked for topology errors
during topology validation.
o Let the topology efficiently track the places where topology rules may have been
violated during editing.
o Allow selected parts, rather than the whole extent of the topology, to be validated after
editing.
Dirty areas are created when:
A feature is created or deleted.
A features geometry is modified.
A features subtype is changed.
Versions are reconciled.
The topology properties are modified.
Practical 8.4
o Right click on the topology in table of Content Property Symbology
Check Dirty Area
o Now start editing on the basis of the topology inspection message
o What is new? _________________
o What does it mean _________________
a report of the total number of errors and exceptions
o You can use the report of the number of error features as a measure of the data
quality of a topological dataset.
Practical 8.5
o Right click on the topology in table of Content Property error
o Generate error export to file (the error will generate in text document (.txt)
o Open the exported text document in Microsoft office word ( still the file is a
little hard to understand )
o Convert text to table ( use comma as separate text at)
o Can you open the file in Microsoft office excel
error inspector in ArcMap
30
Exercise 9
9 Relationship Classes
A relationship class contains several properties that define how objects in the origin relate to objects in
the destination. You specify these properties when you create the relationship class.
Cardinality:
Cardinality describes how many objects of one type are related to an object of another type.
Is the relationship one-to-one, one-to-many, or many-to-many?
certain types of relationships support certain cardinalities, and
You can control cardinalities for any relationship class when you define relationship rules.
Key fields
o A relationship between two objects is maintained through attribute values for key fields.
o Primary and foreign keys
Type: Simple or composite
o Simple relationships
Simple, or peer-to-peer, relationships are relationships between two or more objects in the
database that exist independently of each other.
In a relationship between object A and object B, if object A is deleted from the database,
object B continues to exist
Simple relationships can have one-to-one, one-to-many, or manyto-many cardinality.
o Composite relationships
The geodatabase also supports the notion of a composite relationship, where the lifetime of
the origin object controls the lifetime of its related objects.
Composite relationships are always one-to-many but can be constrained to be one-to-one
using relationship rules.
Origin and destination classes
Message notification direction, applicable if you want to implement custom cascade update or
delete behavior Name Forward and backward labels that display when you navigate related
records in ArcMap
31
Practice 9.1
Create relationship class Steps:
1. In the Catalog tree, right-click the geodatabase or feature dataset in which you want to create
the new relationship class and point to New > Relationship Class.
1. Name == Pole_Transformer
2. Remind the cardinality of the two feature and determine the origin - destination relation
One-to-many relationships When creating a one-to-many relationship,

whether simple or composite, the one side must be the origin class. The many
side must always be the destination class.
o Origin == pole
o Destination == Transformer
3. Select composite relation
Specify the label for the relation
1. Foreword == pole support transformer
2. Back ward == transformer load on pole
Select both for message propagation
4. Determine the cardinality ( here one to man)
5. Select no I dont want to add attribute to this relationship class
6. Determine the primary and foreign key
1. Pole ID in pole feature class is primary key and
2. Pole ID in Transformer feature class is a foreign key
Now answer the following questions

A. Is the relation exist (created)? __________________ How do you know?
______________
B. how many transformer______ , poles _____ and poles with transformer
______are there
C. Start editing and delete a pole with a pole ID 36
Is there any change in the transformers? _____
What is that __________________________________________________
why? _________________________________ _____________________
32
Relationship rules
o Relationship rules control which object subtypes from the origin class can be related to
which object subtypes in the destination class.
Practical 9.2
1. Specify the relation rule

2. Right click on the relation class properties rules
3. Specify the following rules
I. a steel pole could Support up to 3 transformer
II. A concrete pole could Support up to 1 transformer
III. A wooden pole couldnt Support transformer
Validating features and relationships in ArcMap

Validate Features checks to ensure that all the attributes and relationships are valid and
gives you the opportunity to fix any issues that violate the rules of your geodatabase.
Practical 9.3
Steps:
1. Start editor
2. Click the Edit tool on the Editor toolbar.
3. Select the features you want to validate here drag over pole. You can only validate features
from a geodatabase.
4. Click the Editor menu and click Validate Features.
If your selection contains any invalid features, a message box appears with the number of
invalid features.
Only those features that are invalid will remain selected.
5. Click OK.
6. Click one of the invalid features.
7. Validate the features again.
33
A message box appears telling you why the feature is invalid.

8. Click OK.
9. Click the Attributes button on the Editor toolbar.

Correct the invalid attribute values.
If you are validating relationships, make the necessary edits to the relationships or the
related objects to make the feature valid. This may involve
1. adding and deleting relationships or
2. altering the subtype of one or all of the features.
10. Select the features, validate, and perform edits until all features are valid.
Practice 10.1
Create relationship class Steps:
2. In the Catalog tree, right-click the geodatabase or feature dataset in which you want to create
the new relationship class and point to New > Relationship Class.
1. Name == Pole_Transformer
2. Remind the cardinality of the two feature and determine the origin - destination relation
One-to-many relationships When creating a one-to-many relationship,

whether simple or composite, the one side must be the origin class. The many
side must always be the destination class.
o Origin == pole
o Destination == Transformer
3. Select composite relation
Specify the label for the relation
1. Foreword == pole support transformer
2. Back ward == transformer load on pole
Select both for message propagation
4. Determine the cardinality ( here one to man)
5. Select no I dont want to add attribute to this relationship class
6. Determine the primary and foreign key
34
1. Pole ID in pole feature class is primary key and
Now answer the following questions

D. Is the relation exist (created)? __________________ How do you know?
______________
E. how many transformer______ , poles _____ and poles with transformer ______are
there
F. Start editing and delete a pole with a pole ID 36
Is there any change in the transformers? _____
What is that _______________________________________________________
why? _________________________________ _____________________
2. Pole ID in Transformer feature class is a foreign key
Practical 10.2
4. Specify the relation rule

5. Right click on the relation class properties rules
6. Specify the following rules
IV. a steel pole could Support up to 3 transformer
V. A concrete pole could Support up to 1 transformer
VI. A wooden pole couldnt Support transformer
Practical 10.3
Steps:
11. Start editor
12. Click the Edit tool on the Editor toolbar.
13. Select the features you want to validate here drag over pole. You can only validate features
from a geodatabase.
14. Click the Editor menu and click Validate Features.
If your selection contains any invalid features, a message box appears with the number of
invalid features.
Only those features that are invalid will remain selected.
15. Click OK.
35
16. Click one of the invalid features.

17. Validate the features again.
A message box appears telling you why the feature is invalid.
18. Click OK.
19. Click the Attributes button on the Editor toolbar.

Correct the invalid attribute values.
If you are validating relationships, make the necessary edits to the relationships or the
related objects to make the feature valid. This may involve
1. adding and deleting relationships or
2. altering the subtype of one or all of the features.
20. Select the features, validate, and perform edits until all features are valid.
36
Exercise Six
5. Raster Dataset
5.1 Importing or loading raster data
Raster data can be imported into a geodatabase in several ways:
by using Import raster datasets (geodatabase context menu),
the Copy Raster tool (geoprocessing tools), or
Load Data (ArcCatalog dataset context menu).
When working with multiple raster datasets, there are three possible storage methods
You can store each raster dataset individually,
Mosaic them all into one large raster dataset, or
Store them all inside a raster catalog container.
Storing the raster datasets individually is the best method when the datasets are not adjacent to each
other and when the datasets are rarely used on the same project. Mosaicking your inputs together to
form one large, single extent of raster data is appropriate for most applications, but a raster catalog
may be desired for one or more of the following reasons:
The extents of the raster datasets partially or fully overlap, and you want the common areas to be
preserved.
The extents of the raster datasets fully overlap and are part of a time series.
You do not need to see the entire area at one time. Raster catalogs display a wireframe at smaller
scales.
There are times when it is important to preserve each piece of metadata associated with each
raster dataset.
Steps:
1. Right-click a geodatabase and click New > Raster Catalog.

2. Optionally, choose a template raster catalog on which to base your new raster catalog.
You may want to use an existing raster catalog as a template if you have created additional
fields in it that you want to have in your new raster catalog. The new raster catalog will then
have the same fields as the template raster catalog.
3. Type a name for the new raster catalog.
37
The raster catalog name cannot have spaces. You can use underscores to separate letters.
4. Optionally, click the Coordinate System for Raster Column button to choose a coordinate
system for the raster catalog.
5. Click the Coordinate System for Geometry Column button to set a coordinate system for
the geometry column.
If your coordinate system for the geometry column is unknown, you need to set the domain.
Setting the domain for a raster catalog works the same way as it does for a feature class.
6. Optionally, you can set a configuration keyword.

7. Optionally, set a spatial grid.
Note: You do not need to specify a spatial index grid for a file geodatabase since it uses
its own optimized index.
8. Choose whether you want your raster catalog to be managed or unmanaged by the geodatabase.
9. Click OK.
5.2 Creating raster datasets in a geodatabase

When you create a raster dataset in a geodatabase, you are creating an empty location to contain a
raster dataset. You can then add a raster dataset to the empty location by copying or mosaicking one or
more raster datasets into your empty one.
Creating raster dataset
A raster dataset can be created in any type of geodatabasepersonal, file, or ArcSDE. You can create
a raster dataset using the context menu in ArcCatalog or using the Create Raster Dataset tool.
1. Before you go to create raster dataset look the number of band in the file and its extension
2. Right-click a geodatabase and click New > Raster Dataset.
38
3. Type the name of the new raster dataset.

4. Set the Cell Size of the geodatabase raster dataset.
5. Set the Pixel Type for the geodatabase raster dataset.
6. Click the Spatial Reference for Raster button to set the spatial coordinate system.
7. Type the Number of Bands that the raster dataset will contain.
8. Click OK.
Loading a raster dataset into an empty geodatabase raster dataset
1. In ArcCatalog or the Catalog window, right-click the empty geodatabase raster dataset, point
to Load, then click Load Data.
2. Click the Input Rasters browse button and navigate to the location of the Input raster
dataset you want to load, then select it.
You can add more than one.
3. Make sure that the Target Raster (output location) is correct. If not, click the browse
button and navigate to the proper location.
4. Click the Mosaic Operator drop-down arrow and choose the rule for overlapping areas if you
are loading more than one raster dataset (mosaicking).
5. Click the Mosaic Colormap Mode drop-down arrow and choose the rule for dealing with
color maps if you are loading raster datasets that have color maps.
6. Optionally, type a number for Ignore Background Value to set a background value to ignore.
7. Optionally, type a number for NoData Value to set a NoData value.
8. Optionally, check the Convert 1 bit data to 8 bit check box.
9. Optionally, set the Mosaicking Tolerance.
39
The mosaicking tolerance controls whether or not resampling of the pixels takes place. If the
difference in pixel alignment of the incoming dataset and the target dataset is less than the
tolerance, no resampling is performed (instead, a shift is performed). The unit of tolerance is
pixels, which have valid values between 0 and 1. To learn more about the mosaicking
tolerance.
10. Optionally, choose a Color Matching Method.
This allows you to choose an algorithm to color match the raster dataset being mosaicked
together.
11. Click OK.
5.3 Creating Mosaic Raster dataset

Create the mosaic dataset.
1. To create the mosaic dataset, right-click the geodatabase in the Catalog window or ArcCatalog
and selectNew > Mosaic Dataset. This will open the Create Mosaic Dataset tool. Or you can
directly access and open the Create Mosaic Dataset tool.
2. Add data to the mosaic dataset. right-click on it in the Catalog window or ArcCatalog and
clickAdd Rasters.
3. You must choose a raster type and enter the location of the input data.
4. Check Update Overviews.
5.2 Raster catalogs

A raster catalog is a collection of raster datasets defined in a table format in which each record
identifies the individual raster datasets included in the catalog. A raster catalog is most often used to
display adjacent, fully overlapping, or partially overlapping raster datasets without having to mosaic
them into one large raster dataset.
Creating raster catalogs in a geodatabase
When creating a raster catalog, the coordinate system needs to be set for the geometry column. If your
coordinate system is unknown, you need to specify the domain for the geometry column. Otherwise, if
neither of these is set, your datasets may not be visible in the display.
1. Right-click a geodatabase and click New > Raster Catalog.
40
2. Type a name for the new raster catalog (name it as DEMData). The raster catalog name cannot
have spaces. You can use underscores to separate letters.
3. Optionally, click the Coordinate System for Raster Column button to choose a
coordinate system for the raster catalog. (left other optional)
4. Choose whether you want your raster catalog to be managed or unmanaged by the geodatabase.
5. Click OK
6. Now load raster data in the catalog .
7. Load the data from the given exercise folder raster exercise select both
ASTGTM_N05E038_dem1.tif and ASTGTM_N06E038_dem1.tif
8. Look the DEMData in arcmap
9. Right click on DEMData in the table of content and open attribute
(what do you observe , any advantage, when shall we use raster catalog
41

Lab Manual

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Lab Manual

Hochgeladen von

Copyright:

Verfügbare Formate

Geo-database management System Lab manual

1.2 Logical Design

2.1 Creating a new File geodatabase

2.2.1 Creating feature datasets

o Using feature datasets is optional depending on the purpose of the geodatabase

2.2.2 Creating feature classes

Feature Class Naming Standards

2.2.3 Creating tables

ID Name Sex Position Work Experience

2.2.4 Adding field to existing feature class in a database

2.2.5 Enable editor tracking

Create editor tracking to the registrar file

3.1 Importing shapefiles into your geodatabase

3.2 Importing a feature class (by exporting in to the Database)

4.1 Creating a Domain

Split and merge policies

4.2 Applying a Domain

3. Choose the Fields tab in the properties window.

4. 2. Select the field to add a domain to:

8. Press OK to apply the settings. OR

4.3 Adding coded values in domain created

4.4 Editing with a Domain

Each table can have only one subtype.

Write the following data in excel

F_ID Name Sex Age Family Size

Z cluster tolerance and ranks

Creating a topology using the Catalog window or ArcCatalog

Creating a topology using geo-processing

Repair Overlap Errors

What rule will govern

One-to-many relationships When creating a one-to-many relationship,

Now answer the following questions

1. Specify the relation rule

Validating features and relationships in ArcMap

A message box appears telling you why the feature is invalid.

9. Click the Attributes button on the Editor toolbar.

One-to-many relationships When creating a one-to-many relationship,

1. Pole ID in pole feature class is primary key and

Now answer the following questions

2. Pole ID in Transformer feature class is a foreign key

4. Specify the relation rule

16. Click one of the invalid features.

19. Click the Attributes button on the Editor toolbar.

1. Right-click a geodatabase and click New > Raster Catalog.

3. Type a name for the new raster catalog.

6. Optionally, you can set a configuration keyword.

5.2 Creating raster datasets in a geodatabase

3. Type the name of the new raster dataset.

5.3 Creating Mosaic Raster dataset

5.2 Raster catalogs

Das könnte Ihnen auch gefallen