US Army Corps of Engineers BUILDING STRONG ® Preparing Your Local Data: Considerations for Cleaning-up your Geodatabase in Preparation for Adaptation Development.

US Army Corps of Engineers

BUILDING STRONG®

Preparing Your Local Data: Considerations for Cleaning-up your Geodatabase

in Preparation for Adaptation Development

USACE SDSFIE Training

Prerequisites: Introducing the SDSFIE

BUILDING STRONG®

Video Sequence

2 of 25

BUILDING STRONG®

Objectives

Understanding adaptations of the SDSFIE Understanding the term model element Understanding what does and does not need to be included in

an Adaptation Understanding whether or not an element is populated Understanding the requirement to define and justify every

extended model element Understanding that you should back-up your geodatabase Understanding how to approach an initial data cleanup Understanding when to delete unneeded data elements

3 of 25

BUILDING STRONG®

WHAT IS AN SDSFIE ADAPTATION

4 of 25

BUILDING STRONG®

SDSFIE adaptation description

An SDSFIE adaptation contains feature types, feature attributes, enumerations and enumerates having the same definition as SDSFIE Gold►Does not need to contain everything in

SDSFIE Gold►Can rename elements that are in SDSFIE

Gold

5 of 25

BUILDING STRONG®

SDSFIE extensions

An SDSFIE adaptation can contain feature types, feature attributes, enumerations and enumerants that are not in SDSIFE Gold►An extension must be approved►Definition of an extension cannot conflict in

any way with SDSFIE Gold

6 of 25

BUILDING STRONG®

SDSFIE Adaptation Concept

7 of 25

Parent Adaptation

Child Adaptation

PROFILE

EXTEND

(Profiled Parent)

Remove attributes and domains

Remove entire Feature Types, and/or Tables

Add attributes and/or domains

Add entire Feature Types, and/or Tables

BUILDING STRONG®

SDSFIE adaptation approval

All adaptations must be reviewed and approved by the DISDI or a person having delegated authority► The USACE Adaptation was approved by the

DISDI► The USACE GIS Coordinator has delegated

authority from the DISDI► The USACE Data Standards PDT reviews

adaptations of the USACE adaptation

8 of 25

BUILDING STRONG®

Benefits of SDSFIE adaptations

Shared data schema Consistent data definitions Easily share data Potential for common mission schemas Provides definitions for several offices to

leverage in enterprise GIS initiatives

9 of 25

BUILDING STRONG®

WHAT IS AN SDSFIE MODEL ELEMENT?

10 of 25

BUILDING STRONG®

SDSFIE Model “Elements”

Model “elements” include any of the following model components:►Feature dataset – a set of feature classes►Feature class – a set of thematically equivalent

features►Attribute – a characteristic of the features►Domain – constraint on an attribute►Enumerant – permissible domain values within a

domain

11 of 25

BUILDING STRONG®

WHAT TO INCLUDE IN AN ADAPTATION

12 of 25

BUILDING STRONG®

Inclusion / Exclusion Criteria

Include:►core business data that you create, maintain, and

you would typically share

Don't include: ►data that would not be shared data►data that is obtained from sources external to the

District, and no value is added► data that is out of date, not maintained, not used,

or otherwise should not be used

13 of 25

BUILDING STRONG®

Is Your Element Populated?

Two primary cases to be considered:►Feature classes that contain no features.►Attributes for which none of the records in the

feature class have values.

In both cases, only include “empty” elements when you have plans to create (or acquire), store, and maintain data for the element, and would need to share that element

14 of 25

BUILDING STRONG®

DEFINITIONS AND JUSTIFICATIONS FOR EXTENDED ELEMENTS

15 of 25

BUILDING STRONG®

Extentsion Requirements

DoD and USACE rules mandate that definitions and justifications be supplied for every extended SDSFIE model element in your adaptation

This is another consideration when you are trying to determine element inclusion or exclusion

16 of 25

BUILDING STRONG®

INITIAL DATA CLEAN-UP

17 of 25

BUILDING STRONG®

First, Back-Up Your Data!

18 of 25

Clean up your data to prepare for adaptation development, using a copy of your geodatabase

Use the ArcCatalog –right mouse click– Copy/Paste function

BUILDING STRONG®

Process to Back-Up Your Data

19 of 25

Navigate to your geodatabase, and right mouse click

BUILDING STRONG®

Process to Back-Up Your Data

20 of 25

Select “Copy

BUILDING STRONG®

Process to Back-Up Your Data

21 of 25

Select “Paste

Right click in white space of Contents view, in right window

BUILDING STRONG®

Process to Back-Up Your Data

22 of 25

“* - Copy” is created

BUILDING STRONG®

Top-Down Approach To Initial Geodatabase Clean-Up

23 of 25

Take top-down approach through the geodatabase model (element) hierarchy:► feature datasets – remove when no feature classes

therein are to be retained in adaptation► feature classes – examine remainder, one-by-one► attributes – examine all in retained feature classes► domains – remove when none of the attributes

constrained by the domain are being retained

If unsure about an element, retain it for now!

BUILDING STRONG®

Review

24 of 25

Understanding what does and does not need to be included in an Adaptation

Understanding the term model element Understanding whether or not an element is populated Understanding the requirement to define and justify

every extended model element Understanding that you should use a copy of your

geodatabase for adaptation development Understanding how to approach an initial data cleanup Understanding when to delete unneeded data elements

BUILDING STRONG®

Next Steps

Video that should be seen next is:►Creating a data dictionary for your local data

Contact [email protected] with comments or additional information

25 of 25