Using ArcGIS Desktop

Here is an example description of a data theme for ownership parcels in a cadastral

application.
   
 
 

 

%   
 
   



+,"#
!  "#
%'
  
 "#
%
 && 
%
 
%
 
%
- 
%
- 
#
- 
%
%' .& '
#
%' .- 
#
 
&   

%  

   

   
$ 
$ 
$ 
$ 
$ 
$ 
$ 
$ 
$ 
$ 
$ 

 


   


*/
01
01
01
01

 '2

/

/
/
/

/
/

&

)/

  

%    


&      
  
     ' 
#   







     
   
(
)
*


&
 


   

   

   

3 ' 
  
  


   
  

 

   
 

 
  




 

 
 

    

     


 

   

   



   
 
 




   





+,"#
!  "#
 "#
%
 
%
     &   
 '3
%

 
     


$ 
$ 
$ 
$ 

0/
0/
/
*/

Create the specications for individual data themes

Once you have identied and described the thematic layers in your design, the next step is
to develop specications, or schema, for representing the contents of each thematic layer in
the physical database. The description of each thematic layer will result in a specication

of geodatabase datasets, such as feature classes, tables, relationship classes, raster datasets,
subtypes, topologies, domains, and so on.

These then become the individual geodatabase datasets you create in ArcCatalog (or that
you copy from a data model and modify). Then you import the actual data into each feature

class, or create new data by digitizing or scanning features in the feature class.
Here are the characteristics of each data theme that youll want to dene:

The coordinate systemthis may be predetermined by local or regional standards,

or by data that youre already using. You may use different coordinate systems for
different applications (and geodatabases).

How the data themes will be represented geographicallysome may be simple feature
classes (wells represented as point features); some may require special datasets (an
elevation surface represented as a terrain, or utilities as a geometric network). The map

82

2 Geographic Data Management

scale is also an issue for the geographic representation of features. You might want to
represent buildings as point features when zoomed out, and as polygons (the building
footprint) when zoomed in. In this case youll need to create two feature classes for the

data theme.

The attributes of each data themethe elds (column names), the data type for each
(whether numeric or character, the eld length, and so on), and the valid values or
value ranges. Youll also want to dene the table structure for each data theme
whether all the attributes are held in the themes attribute table, or whether there are
related tables and, if so, which elds will be used as the common keys for building

relationships.
The relationships with other features. Consider how each map layer will be displayed
in an integrated fashion with other layers. For modeling and analysis, consider how

information will be used with other datasets (that is, how they are combined and

integrated). This will help you to identify key spatial relationships and data integrity

rules, to be implemented as feature datasets and topologies.

Heres a simple example for a parcels geodatabase.
Feature Class

Representation

Notes

Street centerlines

Line

Soil types

Polygon

Parcels

Polygon

Parcel boundaries

Line

Parcel corners

Point

Parcel annotation

Annotation

Building footprints

Polygon

Street segments split at each intersection.

Usually contain address ranges and network
properties.
Usually have many descriptive attributes in
related tables.
Topologically integrated with parcel boundaries
and corners.
Has coordinate geometry and dimension
attributes. Participates in a topology with parcels
and corners.
Surveyed corners of parcels. Participates in a
topology with parcel polygons and boundaries.
Provides text labels for lot dimensions, taxation,
and legal description information.
Contains outlines of building and structures.

Specify editing workows and map display properties

If your GIS work will involve data editing or updating data on an ongoing basis, its
useful to dene up front the editing procedures and integrity rulesfor example, youd

specify that all streets are split where they intersect other streets, street segments connect at
endpoints, and so on. You can ensure that these rules are implemented in the geodatabase.
Its also useful to dene display properties for maps and 3D views, such as symbology,
standard map scales, and text fonts. These will be used to dene map layers.

Build and test a prototype design

If youre building a large, multiuser database, youll want to test your prototype design.
Build a sample geodatabase copy of your proposed design using a le geodatabase or a

personal geodatabase. Load a subset of data and build maps, run key applications, and

perform editing operations to test the designs utility. You can then make changes to the

design before loading all the data.

83