Introduction to the Multiuser Geodatabase
Introduction to the Multiuser Geodatabase Emily Apsey ESRI Instructor
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Defining the geodatabase • Collection of geographic datasets – Feature classes, raster data, attribute tables
• Native data structure for ArcGIS
Surveys Addresses
Networks
• Provides the ability to:
Vectors
– Leverage data relationships – Enforce data integrity – Create intelligent features
Annotation
3D Objects
Attribute
Topology Dimensions Terrain
Cadastral
Cartography
CAD Images
Advantages of geodatabase • Central location for features and attributes • Ability to create behavior – Grouping features into subtypes – Creating spatial and attribute validation rules
• Persistent relationships between records • Stored connectivity between lines and points • Many users editing database at one time – Dependant on geodatabase type
• Scaleable
Geodatabase options • Personal for Microsoft Access • File • ArcSDE technology at three levels: – Desktop – Workgroup – Enterprise
ArcGIS Server
ArcGIS Desktop Enterprise Personal Personal (Access) Access
File
File
Desktop
Workgroup
Capacity Number of users
ArcGIS Desktop geodatabases • All are single editor – Desktop (ArcSDE technology) is limited to four connections
Personal (Access)
File
Desktop (ArcSDE technology)
Functionality
Original Desktop format
Improved Desktop format
Designed for replication or project level use
Storage mechanism
Microsoft Access database (.mdb)
File folder;
Microsoft SQL Server Express
Storage limit
2 GB per geodatabase;
1 TB per object;
Effective limit ~500 MB
Configurable up to 256 TB
Platform
Windows
Any
ArcCatalog displays .gdb
4 GB per database server
Windows
ArcGIS Server licensing • Three editions of ArcGIS Server functionality Spatial Analysis & Editing Visualization & Mapping Data Management
Advanced Standard Basic
• Functionality scaled by capacity
Enterprise Workgroup
– Workgroup or enterprise
• ArcSDE technology bundled with all editions
ArcSDE geodatabase editions Supports large capacity geodatabases • Requires regular maintenance • Unlimited connections • Enterprise
Managed by ArcCatalog
• Employed Workgroup
for departmental projects • Does not require a DBA or DBA experience • 10 concurrent user connections • Replication
Desktop
and individual projects • No additional cost with ArcEditor or ArcInfo • Connections: Three viewer and one editor *Support same geodatabase functionality
A
ArcGIS Desktop licensing • Geodatabase functionality based on license –ArcView • Personal Access and File Geodatabase creation and editing • Some behavior creation (subtypes, domains)
–ArcEditor/ArcInfo (includes all from ArcView) • Desktop ArcSDE Geodatabase creation and editing • ArcGIS Server Workgroup and Enterprise editing and managing • Create additional elements (topology, networks, relationship classes) • Additional behavior creation (connectivity rules, relationship rules)
Central Maryland GIS User Group
9
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Geodatabase elements Tables Feature dataset
Raster datasets
Spatial reference
Raster catalogs
Feature classes Polygon Line Point Annotation
Route Dimension Representations
Relationship classes Geometric networks
Behavior Connectivity rules Relationship rules Topology rules
Attribute defaults Attribute domains
Toolboxes Tool
Model
Script
Topology
Additional geodatabase elements Survey datasets
Terrain datasets
Network datasets
Schematics
Network datasets
Central Maryland GIS User Group
11
Feature classes • Table that stores geographic features and attributes – One type of geometry (point, line, polygon, annotation) – Allows for XY coordinates and Z and M measures – Has associated spatial reference Geographic
coordinate system (GCS), projected coordinate system (PCS), and spatial extents – Each record represents a feature
Feature datasets • Contain feature classes – All share same spatial reference – No tables (no geometry)
• Required to model spatial relationships • Can be used for organization – Group feature classes for management – Not ideal
• Permissions given to all feature classes within dataset
Geodatabase behavior • Specific to geodatabase – Subtypes Categorize features into groups – Domains Create Create real-world real-world Attribute validation on a field feature feature behavior behavior – Topology rules in in geodatabase geodatabase Spatial validation rules – Relationship class rules Determine proper associations between records – Connectivity rules Determine proper connections between network features
Geodatabase properties and behavior • Properties stored in a relational database (DBMS) – Feature geometry and attributes stored in tables – Rules and relationships stored in system tables
• Behavior implemented by client (ArcObjects) – ArcGIS software operates according to properties – Geodatabase integrity enforced by client
ArcObjects interprets properties as behavior
Subtypes • Categorize records into groups – Manage groups of records – Within one feature class or table – Integer field required
• Property of feature class or table • Codes based on table values – Requires knowledge of data
• Use for editing and other geodatabase behavior
Advantages of subtypes • Data automation – Default attributes updated as you add new features
• Manage groups of features separately • More efficient editing – Edit directly into subtype
No No subtypes subtypes
Subtypes Subtypes
ArcMap ArcMap table table of of contents contents
Domains • Validation of values in a field • Two types: –Range –Coded values • Geodatabase property –Apply to many fields and subtypes • Allow for data standardization
Types of domains • Range – Locate errors in attribute data – Manual validation – Validate in edit session – Invalid features remain selected
• Coded values – Valid list of values for a field – Editors pick from list – Automatic validation – Reduce typos Domain Domain list list appears appears while while editing editing
Advantages of domains • Prevent and locate attribute errors • Maintain consistent coding schemes • Facilitate data entry • Available to all feature classes or tables in geodatabase
Validation Validation in in attribute attribute table table
Validation Validation in in Attributes Attributes dialog dialog box box
Relationship Classes • An association between two object classes – A class may participate in multiple relationship classes
• Simple relationships • Composite relationships – Related objects can message each other – Can trigger behavior (cascade delete, move to follow, custom, etc.)
• Associate rules with relationship classes – Each Parcel can have between 1 to 3 Buildings ParcelToBuilding
Demo • Subtypes • Relationship class
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Geodatabase Topology • Topology is used to – – – – –
Integrate feature geometry Validate features Control editing tools Define relationships between features Ensure the quality of your data
Topology Error Examples • Rules enforced to maintain topological integrity – 25+ topology rules in ArcGIS
Topological Integrity • Topology defines integrity rules for associated feature classes – Participating feature classes / subtypes – Cluster tolerance, ranks and rules • Cluster Tolerance for XY and Z
• Rules are evaluated during Validation – Define rules when creating the Topology
• Violations of these rules are expressed as error features managed in the database as a part of the topology – Error and Exceptions – Examine and Fix errors in ArcMap
Editing with a Topology • Editing creates a dirty area – Area has been edited and may contain errors – Can be symbolized
• Errors are found during validation – Errors have properties • What rule was violated • Which feature(s) created the error
• Your options: – Ignore the error – Mark as exception – Fix the error
Parcels Parcelsoverlap overlap
Networks in ArcGIS • Two network system data structures available: − Geometric networks Directed flow system applications (e.g., natural resources, utilities) Lines & points Æ Geometric network Use with Utility Network Analyst toolbar in ArcMap
– Network datasets Undirected flow system applications (e.g., transportation) Lines, points, & turns Æ Network dataset Use with ArcGIS Network Analyst extension
• Feature classes can participate in either a geometric network or a network dataset – not both A
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Raster data • Stored in geodatabase in ArcSDE raster format
Real world
– Divide space into a matrix of equally sized cells (or pixels) Each has a numeric value Store a sample of geography As raster
• Each pixel is independent – No discrete features – Pixels arranged in columns/rows
Pixel
Raster data in the geodatabase • Raster dataset – Any valid raster format that organizes data into bands – Includes mosaics
• Raster catalog – A collection of raster datasets stored in a table
• Raster data type attribute – An attribute of a feature with a raster data type
When to use raster catalogs WILSON.GISADMIN.SCANNED_MAPS OID NAME SHAPE RASTER 1 Bailey 1 1 2 Winstead 2 2 3 Lucama 3 3 4 Wilson 4 4 Files Spatial column
Raster ID
• Data properties – Need to preserve overlapping inputs – Need to maintain separate VAT, color map, renderer, etc.
• Query access – By individual raster dataset – By user-defined attribute (date, percent cloud cover, etc.)
1010-32
Mosaicking raster datasets • All images must have the same: – Number of bands – Pixel size
• Spatial reference of first image is retained in output • GP tools – Use Mosaic to add to an existing raster dataset – Create a new, mosaicked raster dataset • Mosaic to New Raster • Workspace to New Raster
1010-33
Raster attributes • Raster column data type • One raster column per table – Multiple rasters can be supported through related tables
• Rasters converted to ArcSDE raster format
Raster dataset schema overview Vector tables
Ortho
OBJECTID NAME 1 IMAGE24
SHAPE 1
RASTER 1 Supporting raster tables
• Business table – Relates to the supporting vector and raster tables
• Raster supporting tables – Store pixel data, band metadata, raster statistics, color maps
• Vector supporting tables – Vector footprint
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-side Performance
Editing in a geodatabase • Use tools to maintain data integrity while editing • Personal, file, desktop geodatabases: Single editor • Multiuser geodatabase: Many editors
Editing in a multiuser geodatabase • Non-versioned – No undo/redo functionality – Edits are visible to all geodatabase users once saved No conflict detection mechanism
• Versioned – Undo/redo capability – Edits are isolated in the edit session or version – Many users edit the same feature class at the same time* Same version or different versions Built-in mechanism to detect and resolve conflicts
Overview of non-versioned editing • Uses DBMS transaction model – Save – saves all edits, updates visible to the outside world – Exit without saving – loses all edits made since the last save
• Changes visible to geodatabase users upon refresh – Zoom, pan, map refresh
• Benefits – Non-ESRI applications can read/modify same data – Very simple to implement
Overview of versioned editing USER1 version
Original version
USER2 version
• Method of presenting and tracking changes to tables – Groups of changes accessed as self-consistent versions
• Multiple, alternate versions may coexist – Appears to users that they have their own copy of table
• Includes mechanisms for reconciling versions – Integrates changes into one version – Clients offered tools to resolve conflicts
Definition: Version • Snapshot of the geodatabase – Entire geodatabase is visible through every version
• Persistent record of changes – Disconnect/reconnect to version
• A unit of work – E.g., design alternative, work order, geometry modification
• Basis of multiuser editing of the same data
Overview of geodatabase archiving • Maintain record of edit transactions 31
• Edits are preserved in a history class – Denoted with FROM and TO dates Transaction
time is recorded May not be the time of event
16
• Built on versioning architecture 1
Geodatabase replication and versioning • Copies of data distributed among geodatabases – Users at different locations can edit the same data – Founded on versioning
• Changes can be synchronized across geodatabases Federal
USA
MI
Regional
State
CA
Napa
Fresno
Keweenaw
Huron
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Performance bottlenecks • Server hardware – Ensure storage, processor, memory can meet user demand
• Network can easily bottleneck • DBMS must be adequately tuned for geodatabase – Maintenance is essential
• Client interaction and geodatabase design ArcMap TCP/IP
User interaction
SQL
Server processing Results presented
Multiuser Multiuser geodatabase geodatabase SQL
TCP/IP ArcMap
DBMS server
Application optimization overview • Avoid full feature class display – Use the power of spatial indexing
• Employ best practices – ArcCatalog tools Thumbnails – ArcMap tools Scale dependencies Navigation tools and windows Symbology Labels vs. annotation
Maintaining performance • Your actions affect your performance! • Critical DBA or SDE manager job functions – Version management/workflow – Compress – Analyze – Index maintenance – Storage planning – DBMS tuning and configuration – Server resource monitoring
Conclusion • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Other FedUC Sessions and Activities • Technical Sessions – Managing Distributed Data with Geodatabase Replication – Multiuser Geodatabase Editing Workflows
• Hands-On Learning Lab, West Registration area – Basics of Geodatabase Model – Workflow Management with JTX – Using the GIS Data ReViewer
Thank you for attending! [email protected]
Central Maryland GIS User Group
50
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Defining the geodatabase • Collection of geographic datasets – Feature classes, raster data, attribute tables
• Native data structure for ArcGIS
Surveys Addresses
Networks
• Provides the ability to:
Vectors
– Leverage data relationships – Enforce data integrity – Create intelligent features
Annotation
3D Objects
Attribute
Topology Dimensions Terrain
Cadastral
Cartography
CAD Images
Advantages of geodatabase • Central location for features and attributes • Ability to create behavior – Grouping features into subtypes – Creating spatial and attribute validation rules
• Persistent relationships between records • Stored connectivity between lines and points • Many users editing database at one time – Dependant on geodatabase type
• Scaleable
Geodatabase options • Personal for Microsoft Access • File • ArcSDE technology at three levels: – Desktop – Workgroup – Enterprise
ArcGIS Server
ArcGIS Desktop Enterprise Personal Personal (Access) Access
File
File
Desktop
Workgroup
Capacity Number of users
ArcGIS Desktop geodatabases • All are single editor – Desktop (ArcSDE technology) is limited to four connections
Personal (Access)
File
Desktop (ArcSDE technology)
Functionality
Original Desktop format
Improved Desktop format
Designed for replication or project level use
Storage mechanism
Microsoft Access database (.mdb)
File folder;
Microsoft SQL Server Express
Storage limit
2 GB per geodatabase;
1 TB per object;
Effective limit ~500 MB
Configurable up to 256 TB
Platform
Windows
Any
ArcCatalog displays .gdb
4 GB per database server
Windows
ArcGIS Server licensing • Three editions of ArcGIS Server functionality Spatial Analysis & Editing Visualization & Mapping Data Management
Advanced Standard Basic
• Functionality scaled by capacity
Enterprise Workgroup
– Workgroup or enterprise
• ArcSDE technology bundled with all editions
ArcSDE geodatabase editions Supports large capacity geodatabases • Requires regular maintenance • Unlimited connections • Enterprise
Managed by ArcCatalog
• Employed Workgroup
for departmental projects • Does not require a DBA or DBA experience • 10 concurrent user connections • Replication
Desktop
and individual projects • No additional cost with ArcEditor or ArcInfo • Connections: Three viewer and one editor *Support same geodatabase functionality
A
ArcGIS Desktop licensing • Geodatabase functionality based on license –ArcView • Personal Access and File Geodatabase creation and editing • Some behavior creation (subtypes, domains)
–ArcEditor/ArcInfo (includes all from ArcView) • Desktop ArcSDE Geodatabase creation and editing • ArcGIS Server Workgroup and Enterprise editing and managing • Create additional elements (topology, networks, relationship classes) • Additional behavior creation (connectivity rules, relationship rules)
Central Maryland GIS User Group
9
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Geodatabase elements Tables Feature dataset
Raster datasets
Spatial reference
Raster catalogs
Feature classes Polygon Line Point Annotation
Route Dimension Representations
Relationship classes Geometric networks
Behavior Connectivity rules Relationship rules Topology rules
Attribute defaults Attribute domains
Toolboxes Tool
Model
Script
Topology
Additional geodatabase elements Survey datasets
Terrain datasets
Network datasets
Schematics
Network datasets
Central Maryland GIS User Group
11
Feature classes • Table that stores geographic features and attributes – One type of geometry (point, line, polygon, annotation) – Allows for XY coordinates and Z and M measures – Has associated spatial reference Geographic
coordinate system (GCS), projected coordinate system (PCS), and spatial extents – Each record represents a feature
Feature datasets • Contain feature classes – All share same spatial reference – No tables (no geometry)
• Required to model spatial relationships • Can be used for organization – Group feature classes for management – Not ideal
• Permissions given to all feature classes within dataset
Geodatabase behavior • Specific to geodatabase – Subtypes Categorize features into groups – Domains Create Create real-world real-world Attribute validation on a field feature feature behavior behavior – Topology rules in in geodatabase geodatabase Spatial validation rules – Relationship class rules Determine proper associations between records – Connectivity rules Determine proper connections between network features
Geodatabase properties and behavior • Properties stored in a relational database (DBMS) – Feature geometry and attributes stored in tables – Rules and relationships stored in system tables
• Behavior implemented by client (ArcObjects) – ArcGIS software operates according to properties – Geodatabase integrity enforced by client
ArcObjects interprets properties as behavior
Subtypes • Categorize records into groups – Manage groups of records – Within one feature class or table – Integer field required
• Property of feature class or table • Codes based on table values – Requires knowledge of data
• Use for editing and other geodatabase behavior
Advantages of subtypes • Data automation – Default attributes updated as you add new features
• Manage groups of features separately • More efficient editing – Edit directly into subtype
No No subtypes subtypes
Subtypes Subtypes
ArcMap ArcMap table table of of contents contents
Domains • Validation of values in a field • Two types: –Range –Coded values • Geodatabase property –Apply to many fields and subtypes • Allow for data standardization
Types of domains • Range – Locate errors in attribute data – Manual validation – Validate in edit session – Invalid features remain selected
• Coded values – Valid list of values for a field – Editors pick from list – Automatic validation – Reduce typos Domain Domain list list appears appears while while editing editing
Advantages of domains • Prevent and locate attribute errors • Maintain consistent coding schemes • Facilitate data entry • Available to all feature classes or tables in geodatabase
Validation Validation in in attribute attribute table table
Validation Validation in in Attributes Attributes dialog dialog box box
Relationship Classes • An association between two object classes – A class may participate in multiple relationship classes
• Simple relationships • Composite relationships – Related objects can message each other – Can trigger behavior (cascade delete, move to follow, custom, etc.)
• Associate rules with relationship classes – Each Parcel can have between 1 to 3 Buildings ParcelToBuilding
Demo • Subtypes • Relationship class
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Geodatabase Topology • Topology is used to – – – – –
Integrate feature geometry Validate features Control editing tools Define relationships between features Ensure the quality of your data
Topology Error Examples • Rules enforced to maintain topological integrity – 25+ topology rules in ArcGIS
Topological Integrity • Topology defines integrity rules for associated feature classes – Participating feature classes / subtypes – Cluster tolerance, ranks and rules • Cluster Tolerance for XY and Z
• Rules are evaluated during Validation – Define rules when creating the Topology
• Violations of these rules are expressed as error features managed in the database as a part of the topology – Error and Exceptions – Examine and Fix errors in ArcMap
Editing with a Topology • Editing creates a dirty area – Area has been edited and may contain errors – Can be symbolized
• Errors are found during validation – Errors have properties • What rule was violated • Which feature(s) created the error
• Your options: – Ignore the error – Mark as exception – Fix the error
Parcels Parcelsoverlap overlap
Networks in ArcGIS • Two network system data structures available: − Geometric networks Directed flow system applications (e.g., natural resources, utilities) Lines & points Æ Geometric network Use with Utility Network Analyst toolbar in ArcMap
– Network datasets Undirected flow system applications (e.g., transportation) Lines, points, & turns Æ Network dataset Use with ArcGIS Network Analyst extension
• Feature classes can participate in either a geometric network or a network dataset – not both A
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Raster data • Stored in geodatabase in ArcSDE raster format
Real world
– Divide space into a matrix of equally sized cells (or pixels) Each has a numeric value Store a sample of geography As raster
• Each pixel is independent – No discrete features – Pixels arranged in columns/rows
Pixel
Raster data in the geodatabase • Raster dataset – Any valid raster format that organizes data into bands – Includes mosaics
• Raster catalog – A collection of raster datasets stored in a table
• Raster data type attribute – An attribute of a feature with a raster data type
When to use raster catalogs WILSON.GISADMIN.SCANNED_MAPS OID NAME SHAPE RASTER 1 Bailey 1 1 2 Winstead 2 2 3 Lucama 3 3 4 Wilson 4 4 Files Spatial column
Raster ID
• Data properties – Need to preserve overlapping inputs – Need to maintain separate VAT, color map, renderer, etc.
• Query access – By individual raster dataset – By user-defined attribute (date, percent cloud cover, etc.)
1010-32
Mosaicking raster datasets • All images must have the same: – Number of bands – Pixel size
• Spatial reference of first image is retained in output • GP tools – Use Mosaic to add to an existing raster dataset – Create a new, mosaicked raster dataset • Mosaic to New Raster • Workspace to New Raster
1010-33
Raster attributes • Raster column data type • One raster column per table – Multiple rasters can be supported through related tables
• Rasters converted to ArcSDE raster format
Raster dataset schema overview Vector tables
Ortho
OBJECTID NAME 1 IMAGE24
SHAPE 1
RASTER 1 Supporting raster tables
• Business table – Relates to the supporting vector and raster tables
• Raster supporting tables – Store pixel data, band metadata, raster statistics, color maps
• Vector supporting tables – Vector footprint
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-side Performance
Editing in a geodatabase • Use tools to maintain data integrity while editing • Personal, file, desktop geodatabases: Single editor • Multiuser geodatabase: Many editors
Editing in a multiuser geodatabase • Non-versioned – No undo/redo functionality – Edits are visible to all geodatabase users once saved No conflict detection mechanism
• Versioned – Undo/redo capability – Edits are isolated in the edit session or version – Many users edit the same feature class at the same time* Same version or different versions Built-in mechanism to detect and resolve conflicts
Overview of non-versioned editing • Uses DBMS transaction model – Save – saves all edits, updates visible to the outside world – Exit without saving – loses all edits made since the last save
• Changes visible to geodatabase users upon refresh – Zoom, pan, map refresh
• Benefits – Non-ESRI applications can read/modify same data – Very simple to implement
Overview of versioned editing USER1 version
Original version
USER2 version
• Method of presenting and tracking changes to tables – Groups of changes accessed as self-consistent versions
• Multiple, alternate versions may coexist – Appears to users that they have their own copy of table
• Includes mechanisms for reconciling versions – Integrates changes into one version – Clients offered tools to resolve conflicts
Definition: Version • Snapshot of the geodatabase – Entire geodatabase is visible through every version
• Persistent record of changes – Disconnect/reconnect to version
• A unit of work – E.g., design alternative, work order, geometry modification
• Basis of multiuser editing of the same data
Overview of geodatabase archiving • Maintain record of edit transactions 31
• Edits are preserved in a history class – Denoted with FROM and TO dates Transaction
time is recorded May not be the time of event
16
• Built on versioning architecture 1
Geodatabase replication and versioning • Copies of data distributed among geodatabases – Users at different locations can edit the same data – Founded on versioning
• Changes can be synchronized across geodatabases Federal
USA
MI
Regional
State
CA
Napa
Fresno
Keweenaw
Huron
Session Path • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Performance bottlenecks • Server hardware – Ensure storage, processor, memory can meet user demand
• Network can easily bottleneck • DBMS must be adequately tuned for geodatabase – Maintenance is essential
• Client interaction and geodatabase design ArcMap TCP/IP
User interaction
SQL
Server processing Results presented
Multiuser Multiuser geodatabase geodatabase SQL
TCP/IP ArcMap
DBMS server
Application optimization overview • Avoid full feature class display – Use the power of spatial indexing
• Employ best practices – ArcCatalog tools Thumbnails – ArcMap tools Scale dependencies Navigation tools and windows Symbology Labels vs. annotation
Maintaining performance • Your actions affect your performance! • Critical DBA or SDE manager job functions – Version management/workflow – Compress – Analyze – Index maintenance – Storage planning – DBMS tuning and configuration – Server resource monitoring
Conclusion • The Geodatabase • Inside the Geodatabase • Advanced Behavior – Geodatabase Topology – Geometric Networks – Network Datasets
• Raster data in the Geodatabase • Editing the Geodatabase • Optimizing Client-Side Performance
Other FedUC Sessions and Activities • Technical Sessions – Managing Distributed Data with Geodatabase Replication – Multiuser Geodatabase Editing Workflows
• Hands-On Learning Lab, West Registration area – Basics of Geodatabase Model – Workflow Management with JTX – Using the GIS Data ReViewer
Thank you for attending! [email protected]
Central Maryland GIS User Group
50
