THE NUTS & BOLTS OF GIS:

A GEO-DATABASE ARCHITECTURE

Presented by

John R. Woodard MS, GISP

A Quick IntroductionPROFESSIONAL: 15 years practical experience of applying GIS to

everyday issues. GISP (Geographic Information System

Professional)Certification EA (Enterprise Architecture) Certification GIS Coordinator for Chagrin Valley Engineering, Ltd

EDUCATION: MS in Geography/GIS from the University of Akron. ¾ finished with Masters in Digital Science at Kent State

University.

PERSONAL:Scuba Diver & Beekeeper (Yes, I deal with 100,000 bees and sell honey!)

The Geo-databaseHow do you use a geo-database?

Is it a container for all of your shapefiles converted to

feature classes?

Have you organized these feature classes by type?

Have you organized the database with feature data sets?

What are there limits to a geo-database? Repair data

Size

How can we get more from a geo-database?

Create a naming convention (rule) for your feature classes:

Feature Dataset:

1. it should relate to the type of data (Municipal)

2. it should contain year of creation(2014)

Example: M_Lyndhurst2014

Now any feature class that is imported, created, or edited should be stored in this dataset. This shows that the feature class relates to the City of Lyndhurst and was created in 2014.

Names for Feature Classes and Datasets

Geo-database Architecture (Plan or Blueprint)

Overview Sheet:Feature dataset (divided by category)

Feature classes (Information Contained)

Source (Where or how was the information obtained)

Status: (Complete, Incomplete, in-progress

Feature Class Detail Sheet:Name, Shape type, Field, Data, Definition, Source, Notes

Domain Details SheetName, Properties, and a Description for each property.

How many people have received geo-database and wished it included a data dictionary?

A ROADS

   A00 Road, major and minor categories unknownA01 Road, unseparatedA02 Road, unseparated, in tunnelA03 Road, unseparated, underpassingA04 Road, unseparated, with rail line in centerA05 Road, separatedA06 Road, separated, in tunnelA07 Road, separated, underpassingA08 Road, separated, with rail line in centerA09 not used

   A1 PRIMARY HIGHWAY WITH LIMITED ACCESSA10 Primary road with limited access, major categoryA11 Primary road with limited access or interstate hwy, unseparatedA12 Primary road with limited access or interstate hwy, unseparated in tunnelA13 Primary road with limited access or interstate hwy, unseparated underpassingA14 Primary road with limited access or interstate hwy, unseparated rail line in centerA15 Primary road with limited access or interstate hwy, separatedA16 Primary road with limited access or interstate hwy, separated in tunnelA17 Primary road with limited access or interstate hwy, separated underpassingA18 Primary road with limited access or interstate hwy, separated rail line in centerA19 not used

   

Feature Class Codes (FCC)his series of codes provides more detailed information on the classification of the line segment. This list represents all feature class codes. GDT products do not necessarily include all of the codes listed below.

Geographic Data Technology

FCODE DESCRIPTION31200 Bay/Inlet53700 Area of Complex Channels30700 Area to be Submerged31800 Bridge33600 Canal Ditch 33601 Canal Ditch: Aqueduct33603 Canal Ditch: Stormwater34300 Dam/Weir34305 Dam/Weir: Earthen34306 Dam/Weir: Nonearthen36200 Flume36400 Foreshore36900 Gate37300 Hazard Zone40300 Inudation Area40308 Inudation Area: Controlled40309 Inudation Area: Controlled, Flood Elevation40307 Inudation Area: Not Controlled 56800 Levee39800 Lock Chamber41100 Nonearthen Shore43100 Rapids43400 Reef44500 Sea/Ocean45000 Sink/Rise50300 Sounding Datum Line50301 Sounding Datum Line: Approximate50302 Sounding Datum Line: Definite45400 Special Use Zone45402 Special Use Zone: Abanoned Dump Site45401 Special Use Zone: Operational Dump Site45404 Special Use Zone: Abandoned Spoil Area45403 Special Use Zone: Operational Spoil Area53300 Special Use Zone Limit53301 Special Use Zone Limit: Definitely53302 Special Use Zone Limit: Indefinitely45500 Spillway46000 Stream/River46003 Stream/River: Intermittent46006 Stream/River: Perennial

Geo-Database Tables!!!!!!

1. Create your data dictionary in Excel (or Open

Office)

2. Break down into individual sheets

3. Use the Tool for importing tables into the geo-

database.

Now you have a data dictionary or feature class information is easily accessible, can be joined or related to feature classes, and will travel with the geo-database.

Table Examples

CONCLUSIONS:

A Geo-database can be much more than a simple container for your feature classes.

One does not have to use the “high end” tools or methods to benefit from a geo-database.

Consider the geo-database to be a data warehouse. A “warehouse” architecture will

Keep you organized Eliminate mistakes Provide quicker and more efficient analysis

Thank you for your time! Are there any questions?

John R. Woodard MS, GISP

Email: jwoodard@kent.edu or jrw.gisp@gmail.com

Linked-in:

John Woodard MS, GISP

https://www.linkedin.com/profile/preview?vpa=pub&locale=en_US