Evolution of Esri Data Formats

Rudolf De Munnik

Ross Solomons

Seminar Outline

• Introduction

• Legacy Formats

• Demonstration

• Current Formats

• BREAK (15min)

• Demonstration

• Future Formats

• Demonstration

• Questions / Discussions

Introduction

• Purpose of the seminar:

− History of formats.

− Awareness to the optimal usage of the

software and data formats.

− Purpose, advantages and disadvantages of

formats

− What the future holds…

History Timeline

1982(ArcInfo)

Coverages

1986(PC ArcInfo)

Coverages

1991(ArcInfo)

GRID 1991(ArcCAD)

CAD

1991(ArcView 1)

Shapefiles

1999(ArcView 3.2)

Models, Extensions 1994(ArcInfo)

ArcStorm 1995(ArcSDE)

RDBMS

1996

(MapObjects)

1997(ArcView IMS)

Map Services

1999(ArcIMS)

Map Services 2001(ArcGIS 8.1)

Geodatabase

2006

(ArcGIS Server 9.2)

Map Services

ArcGIS 10.1

2012

Cloud

Legacy Formats

• Organizational use:

− Projects and Departments

• Users:

− Data capturing and storage

Project Department

Legacy Formats

• ArcInfo Coverages:

Model for the

Geodatabase

Feature Dataset

Topology:

- Build command

- Clean command

ArcInfo Workstation

Legacy Formats

• ArcStorm:

− Central storage and checkout editing

− Coverage based

− Tile structure

− Pessimistic locking of Tiles

− Checked out Tiles not available to other users

− Mapped network drives

− No Relational database

− Initial concepts for SDE

• ArcSDE:

− Store Spatial data in a Relational Database

− Oracle, Informix, DB2

− Utilise Spatial Types (OGC)

− No Geodatabase functions

− No Feature Datasets

− Allow raster storage

− Rasters fast, but large.

− Raster duplication.

Legacy Formats

Legacy Formats

• Shapefile legacy:

− Simple geographic data

format

− Big Demand for simple

storage

− Open Exchange format

− Adopted as standard

− Interoperability buzzword

− Point, Line and Polygon only

Demonstration

• ArcInfo Workstation

• ArcView 3.2

Current Formats Overview

• Organization: − Projects, Departments, Enterprise

• User: − Analysis and Consume

• Shapefile limitations

• Geodatabase advantages

• Services

• Mobile

• Cloud

Organizational Use • Projects

− Shapefiles and File Geodatabase

• Departments

− Geodatabase (Oracle, SQL…)

• Enterprise

− Geodatabase (Oracle, SQL…)

− Services (ArcGIS Server)

Project Department Enterprise

Shape file Limitations

Shapefile

• No Topology

• No Attribute validation

• Size limitation (2GB)

• No complex geometry

• No multiuser editing

• No Annotation

• DBF Limitations

− Data types e.g. date/time

− Field names 10 chars

− Blobs

Not using full potential of ArcGIS

Shap

efile

To Geodatabase

Geodatabase Advantages

• What is a Geodatabase?

− Central storage and management location for

rich collection of spatial data,

− Sophisticated rules and relationships.

− Geoprocessing and symbology.

Geodatabase Advantages

• Why use a Geodatabase? − Integration with RDBMS (Oracle, SQL..)

− Multi-user editing (versions)

− Topology rules and behavior

− Attribute validation (domains)

− Greater storage capacity

− Lower storage requirements

− Optimized performance

− Scalable (File GDB, SQL Express, Enterprise)

Leverage full potential of ArcGIS!!

Geodatabase elements

Geodatabase

Additional geodatabase elements

Survey datasets Terrain datasets

GPS Datasets Schematics

Network datasets Representations

Raster datasets

Behavior Attribute defaults

Attribute domains

Split/Merge policy

Connectivity rules

Relationship rules

Topology rules

Tables

Spatial reference

Route

Dimension

Feature classes

Relationship classes

Topology

Geometric networks

Feature dataset

Raster mosaic

Polygon

Line

Point

Annotation

Toolboxes

Tool Model Script

Network datasets

Geodatabase Design

• Domains, Attachments and Aliases

− Utilize on multiple platforms

− Design for editing in Desktop

− Design for Server applications

− Design for Mobile

Validation in attribute table Validation in Attributes dialog box

Feature Dataset defined

• Logical grouping of Feature Classes that

participate in a behavioral function e.g.

Topology.

• Common coordinate system for all contained

Feature Classes.

• User permission set on Feature Dataset level.

• Feature Class name unique in Geodatabase,

not in Feature Dataset.

• Not to be used to organize data – not a

directory!

Services

• Dynamic Services − Live content from Geodatabase

− View updates

− Interrogate data

• Cached Services − Predefined Tile schema at

various scales

− Stored as images in Tile structure

• Image Services − Single or mosaic images served

Mobile

• Mobile (GPS) − High accuracy devices

− Data capture

− Ruggedized

− Purpose driven

− Workflow

− Geodatabase design

• Mobile (Smartphone) − Windows, Apple, Android

− Executive monitoring

− Planning

− Geodatabase design

Online (Cloud) content

• Online content

− Image and Street

− Desktop, Server, Mobile

− Online access control

• Subscription

− Personal

− Organization

− Upload data/proc

− Applications and

Dashboards

BREAK

• 15 Minute Break

Demonstration

• Geodatabase:

− Elements

− Topology

− Network analysis

− Domains

− Representations

− Annotation

− Attachments

− Geometric Networks

Demonstration

• Services

• Mobile

• Online content

Future Formats

• Organizational use:

− Projects, Departments, Enterprise

− Societal

• Users

− Everyone

Project Department Enterprise

Societal

Demonstration

• Social Media

• 3D Web Viewer (Braamfontein)

• 3D Web Viewer (Airport )

Questions & Discussions

Thank You !