Paper UC10991

Implementing the SDSFIE Release 2.50 with Geodatabases

Paper UC1099

Paper UC10992

Presenter

The CADD/GIS Technology Centerhttps://tsc.wes.army.mil

Nancy Towne (601) 634-3181Nancy.A.Towne@erdc.usace.army.mil

Paper UC10993

8. Quality check the migration and add metadata

4. Build a filter containing the

Features (Filter Maker)

3. Create a correlation matrix between your data and SDSFIE

2. Browse the SDSFIE to identify

the Features needed (Browser)

Steps for Implementing SDSFIE

1. Identify the data to be

collected & stored in the

database

7. Populate the Geodatabase

(Migrate)

Final products (queries,

maps, etc.)

5. Determine the Spatial Reference of your data

6. Generate a SDSFIE-compliant

Geodatabase (Generator)

Paper UC10994

Once upon a time –In the land of noncompliancy –

There was a village.

The king of the village decreed that all GIS data will be SDSFIE-compliant.

This created an uproar!

A GIS Fairy Tale

Paper UC10995

The GIS royal officers took up the valiant task and discovered the key to compliancy lay in the dragon’s cave -- 3 hills, 1 mountain, and 4 rivers away.

A GIS Fairy Tale

They took up the SDSFIE library gauntlet and toolbox swords and set out on their 8 phase mission.

Paper UC10996

The first hill they conquered was identifying the GIS data to be collected & stored in the SDSFIE database.

A GIS Fairy Tale

This was a simple hill they soared over, leading them to the SDSFIE Browser river.

Paper UC10997

They discovered the SDSFIE Browser river was forked. One fork was navigable using the SDSFIE Browser tool and the other fork using the SDSFIE Browser Lite tool (for geodatabase land access).

A GIS Fairy Tale

They navigated the forks using specific navigation tools:•SDSFIE Browser Tool•SDSFIE Browser Lite Tool

Paper UC10998

Once the SDSFIE Browser river was navigated, they found themselves at the foot of the Correlation Mountain. Knowing they would need help, they gathered all of the tools laying at the base of the mountain.

A GIS Fairy Tale

• ESRI ArcGIS ArcCatalog tool• Internal field charts• Geometry Mapping pages• SDSFIE Attribute Data Types

Paper UC10999

• Use ArcCatalog to view coverages or shapefiles

• Obtain source data attributes and data types

• Metadata Tab- Attributes

Creating Correlation Matrix

Paper UC109910

ESRI Internal Fields

FID – Internal ESRI ID

Shape – Geometry

Area – If your data contains area and you want to keep it, then correlate it. Otherwise, ESRI will calculate it for you.

Perimeter - If your data contains perimeter and you want to keep it, then correlate it. Otherwise, ESRI will calculate it for you.

Paper UC109911

ESRI Internal Fields

Shapefile_Shapefile_I

Coverage#Coverage-IDFNODE#TNODE#LPOLY#RPOLY#

Shapefiles Coverages

Paper UC109912

Geometry Field Mapping

Geometry Geodatabase GeometryPoint PointPoint M Point with MeasuresPoint Z Point with ZsPolyline Line (polyline)Polyline M Line (polyline) with MeasuresPolyline Z Line (polyline) with ZsPolygon PolygonPolygon M Polygon with MeasuresPolygon Z Polygon with Zs

Multipoint M Multipoint with MeasuresMultipoint Multipoint

Multipoint Z Multipoint with Zs

Paper UC109913

Shapefile Field Mapping

Field Type Field Width Geodatabase Field TypeDate - Date

Boolean - Short IntegerNumber 1-4 (decimals = 0) Short IntegerNumber 5-9 (decimals =0) Short IntegerNumber 10-19 (decimals = 0) Short Integer

String 1-255 Text

Number 1-8 (decimals > 0) FloatFloat 14-19 DoubleFloat 1-13 Float

Number 9-19 (decimals > 0) Double

Paper UC109914

Coverage Field Mapping

B 4 Long Integer

D 8 DateF 4 FloatF 8 DoubleI 1-4 Short Integer

C 1-320 Text

N 10-16 DoubleI 10-16 DoubleI 5-9 Long Integer

N 1-9 Float

Field Type Field Width Geodatabase Field Type

Paper UC109915

Database StructureSDSFIE Data Types

C - equivalent of TEXT or VARCHAR containing general character values (length must be specified) (also used for Boolean) (N BYTES)

I - signed numeric data type equivalent to INTEGER containing integer values up to 2,147,483,647 (also used for DATES/TIMES) (4 BYTES)

S - signed numeric data type equivalent to SMALLINT or SHORT INTEGER containing integer values up to 32,767 (2 BYTES)

R - signed floating point numeric data type containing almost any number with 9 significant digits and an E > 38 (4 BYTES)

D - signed numeric data type containing almost any number with 15 significant digits and an E > 300 (8 BYTES)

M – unstructured character data of nearly unlimited length (n BYTES) limited to one attribute of this type per table

Paper UC109916

Accomplishing the most arduous task of scaling Correlation Mountain, they now had in their possession a correlation matrix between their GIS data and SDSFIE.

A GIS Fairy Tale

They were relieved to see the Filter Maker river spread out before them in the valley below. A raft floating nearby proved sturdy and simple to use. (Filter Maker Tool)

Paper UC109917

Having built a filter containing the Features in record time, they crossed the drawbridge to find the small, but unknown Spatial Reference hill.

A GIS Fairy Tale

They were relieved to see such a small hill and utilized the ESRI Spatial Domain Calculator rope to pull themselves up freely.

Paper UC109918

The Spatial Reference hill proved to quite small and consisted of 3 smaller hills: the Projection hill, the Spatial Domain hill, and the Precision hill.

A GIS Fairy Tale

They were excited to see their sixth task before them – the SDSFIE Geodatabase Generator river.

Paper UC109919

The SDSFIE Geodatabase Generator river was simple to cross once they discovered the ESRI ArcGIS boat in the thrushes.

A GIS Fairy Tale

They navigated the river using specific navigation tools:•SDSFIE Geodatabase Generator Tool•ESRI ArcGIS license

Paper UC109920

Now that the geodatabase was created, the task of Populating the Geodatabase lay before them in the form of the ESRI Simple or the SDSFIE Complex Data Loader tributaries. They quickly realized the Simple path would require more work later, so they chose the Complex Path.

A GIS Fairy Tale

They used the SDSFIE Geodatabase Loader Extended Tool, along with the ESRI ArcGIS license they already had to float downriver.

Paper UC109921

A GIS Fairy Tale

The SDSFIE Geodatabase Checker Tool carried them straight to the dragon’s cave and the key to compliancy.

Now possessing a populated SDSFIE-compliant geodatabase, the GIS officers knew they must cross the Quality check river using the SDSFIE Geodatabase Checker sailboat. The metadata sails of the boat were provided by FGDC.

Paper UC109922

The GIS royal officers quickly discovered the dragon, realizing he was subdued in the face of all the knowledge and tools they possessed.

A GIS Fairy Tale

They simply asked him for the key to compliancy, which he gladly provided.

Paper UC109923

The GIS royal officers then hurried home to present the key to compliancy to the king, realizing their journey was completed and victory was theirs!

A GIS Fairy Tale

Paper UC109924

SDSFIE Compliancy!

And they all lived happily ever after.

Paper UC109925

8. Quality check the migration and add metadata

4. Build a filter containing the

Features (Filter Maker)

3. Create a correlation matrix between your data and SDSFIE

2. Browse the SDSFIE to identify

the Features needed (Browser)

Steps for Implementing SDSFIE

1. Identify the data to be

collected & stored in the

database

7. Populate the Geodatabase

(Migrate)

Final products (queries,

maps, etc.)

5. Determine the Spatial Reference of your data

6. Generate a SDSFIE-compliant

Geodatabase (Generator)

Paper UC109926

Questions