Working with the Geodatabase

Transcription

1 Working with the Geodatabase

2 Agenda What is the geodatabase? Benefits of the geodatabase Inside the geodatabase Geodatabase rules Demos Additional resources and training Q & A

3 The Geodatabase is the foundation of ArcGIS Organizing & Managing Geospatial Data Comprehensive Information Model (Any Type of Data) Any DBMS Files ArcGIS 3D Objects Networks Attributes Geodatabase Terrain Topology Vectors Cartography Schematics Surveys Scalable Storage Environments Cadastral Annotation Dimensions Addresses Images... Essential for Leveraging the Full Capabilities of ArcGIS

4 The geodatabase is Storage container for spatial information Business rules data integrity for comprehensive GIS mapping and analysis workflows

5 Inside the Geodatabase Table Raster dataset Feature dataset Raster catalog Feature class Schematic dataset Polygon Line Annotation Dimension Survey dataset Point Route Project folder Project Relationship class Toolbox Topology Tool Model Script Geometric network Network dataset Terrain Behavior Attribute domains Attribute defaults Split/merge policy Relationship rules Connectivity rules Topology rules

6 Geodatabase benefits There are many! Let s explore the geodatabase through the many benefits it provides for your GIS workflows

7 The geodatabase stores spatial data A table with a Shape/Geometry column Feature classes Shape types Points Lines Polygons Multipatch Additional benefits Not just X and Y Z s and M s True curves Multipart features High precision Feature with many parts one row in table.

8 Storing geometry is fundamental to the geodatabase Knowing the area and length of features you maintain is critical Fundamental to GIS problem solving tasks you do every day The geodatabase manages and maintains: Area Perimeter Object ID (System managed ID) Spatial reference (Projection) measuring is a fundamental GIS task.

9 Raster data can be stored in the geodatabase Beyond vector Raster dataset Raster catalog (a collection of datasets) Raster attributes

10 The geodatabase rules The power of the geodatabase Modeling the real world: Parcels cannot overlap Roads are connected and traversable Districts might overlap in some cases Trees are only a certain type A green widget is different than a red widget Data creation Data Usage & Analysis Data "clean up"

11 Domains Describe the legal values of a field type Used to ensure attribute integrity Types of domains: Range A tree can have a height between 0 and 300 feet Coded Value A tree can be of type oak, redwood, or palm Pole <<subtype>> Steel domain Steel Height Default = 50 SplitPolicy = default MinValue = 30 Merge Policy = sum MaxValue = 75 Wood Height A Wood <<subtype>> domain Default = 30 MinValue = 25 MaxValue = 40 SplitPolicy = default Merge Policy = sum

12 Subtypes Partition the objects in a feature class into like groups, i.e. Type, Code, Class attributes Benefits of using subtypes: Rules (e.g. domains) for other attributes can be based on subtypes Provides an opportunity to manage data in one location (i.e. one table) instead of separating out into multiple tables or feature classes ArcMap knows about subtypes when adding data Descriptions Codes

13 Relationships between tables Relational database concept But we often perform this at the layer or map document level An association between two sets of records IN the database A table may participate in multiple relationship classes ArcEditor/ArcInfo to create; ArcView will read-only Simple relationships and Composite relationships Can trigger an action (cascade delete, move to follow, custom, etc.) ParcelToBuilding

14 Spatial relationships Pipes Streams A special category of spatial data rules Fundamental for spatial data storage i.e. Good data Fundamental for real-world decision making i.e. Good decisions Connectivity Land parcels Soil Coastline Country boundary Bus route Roads Adjacency Proximity

15 Geodatabase topology Manages feature classes that share geometry Coincident geometry Data integrity rules Topological relationship queries (for example, navigating feature adjacency or connectivity) Sophisticated editing tools Geodatabase Topology Rules

16 Migrating data into the geodatabase is workflow driven Straightforward tools make it possible e.g. Copy/Paste or Right-click export Import/Export CAD, Shapefile, Coverage, other formats ArcCatalog & ArcToolbox provide the end user framework But, there are other pathways if your workflow requires more flexibility Capturing workflows in Geoprocessing models and scripts ArcCatalog Simple Data Loader ArcMap Object Data Loader XML

17 Demo recap: Feature datasets A container object for feature classes and objects Same spatial reference Container for networks and topologies Must use feature dataset Design considerations Start Editing operations Not a folder ArcScripts Subdivision ParcelCorner Parcel ParcelAnno LotLines Parcel_Topo LotDimensions BoundryLines

18 Demo recap: Object Loader vs. Simple Data Loader 1. ArcCatalog feature class context menu: Simple Data Loader ArcCatalog/No edit session Object Loader Loads data in an ArcMap edit session Undo/Redo supported Snapping environment supported Simple data loader 2. ArcMap Customize dialog: Use Object Loader for: Geometric networks, feature classes in a relationship with messaging, or feature classes that have feature-linked annotation Geodatabase rules Object Loader

19 Demo recap: Topology workflow Designing Choose feature classes Choose tolerances Choose rules Creating ArcCatalog or Geoprocessing framework Validating Find errors using chosen tolerances, rules, and input features Editing ArcMap advanced Editing tools (ArcEditor/ArcInfo required) Error fixing tools Revalidating Topological querying Find adjacent; find connected ArcObjects developer samples

20 Demo recap: Geodatabase validation Validation ArcMap Editor workflow process E.g. Domain > Validate Topology Validate Could be automated to tailor your specific data maintenance workflows Geoprocessing tools, scripts, models ArcMap can be extended using the customization framework (e.g. ArcObjects)

21 Geodatabase also captures specialized GIS workflows Cartographic production workflows Text on maps Standardization of symbology Business/Industry specific workflows e.g. Pipelines or water lines have specific characteristics beyond being just lines E.g. Land record parcel is not just a polygon Other applications (non-industry specific) e.g. Streets have specific characteristics beyond being just lines and are useful to many GIS professionals not just Transportation planners e.g. Street addresses and address mapping processes specialized rules and objects that make spatial data more useful

22 Annotation: Text on a map feature class composite relationship class annotation feature class Storage options: 1. Map document or 2. Geodatabase Placerville 94 Sacramento 95 Topanga Canyon Non-feature-linked geodatabase annotation Not tied to spatial feature (feature & attribute(s)) ArcView licensing Feature-linked geodatabase annotation Uses composite relationship class ArcEditor/ArcInfo license needed to create & edit Placerville Sacramento Topanga Canyon

23 Cartographic representations Advanced symbolization for map features Symbolize a feature and its geometry independently Additional set of symbology rules and effects Stored in the geodatabase Property of a feature class Rules, Overrides are attributes Requires: ArcInfo (all Geoprocessing tools) ArcEditor (Creating/Editing) ArcView (Read only/use)

24 Industry specific geodatabase rules Utility networks Collections of feature classes and tables Flow, direction, sinks/sources, and special connectivity rules Solvers: real world questions and problems specific to those rules Out of the box (ArcEditor/ArcInfo) Transportation Networks Collection of feature classes and tables Direction, restrictions, impedances, costs and special connectivity rules Solvers: real world questions and problems specific to those rules Network Analyst Extension (ArcView/ArcEditor/ArcInfo) Cadastral fabrics Survey Analyst/Cadastral Editor Land records management solution

25 The geodatabase is scalable As organizational needs and challenges change through time Your geodatabase rules can change and evolve, too Your geodatabase rules are still meaningful Your investment is paying off

26 3 Types of geodatabases Personal geodatabase Single user editing Stored in MS Access File geodatabase Single user editing Stored on disk ArcSDE geodatabase Stored in an enterprise DBMS Supports geodatabase versioning Personal Geodatabase Requires ArcEditor or ArcInfo for editing ArcGIS File Geodatabase ArcSDE Oracle SQL Server DB2 Informix PostgreSQL

27 Geodatabase types: Capacities and other considerations Personal GDB File GDB ArcSDE GDB (3 editions) Storage format Microsoft Access Folder of binary files DBMS Storage capacity 2 GB 1 TB per table Depends on edition Supported O/S platform Windows Any platform Depends on edition Number of users Single editor Multiple readers Single editor Multiple readers Multiple editors & readers Distributed GDB functionality Check out/check in and One-way replication Check out/check in and One-way replication Replication (all types) & versioning

28 Editing geodatabases ArcGIS datasets stored in the geodatabase are editable Editing in ArcGIS is based on a transactional model Edits are performed in an edit session A series of edit operations constitutes a transaction Unit of work performed against the database The transaction is either committed or rolled back Editing needs to be flexible Let users define what an edit means Built around organizational skill sets and workflows Honor and understand geodatabase rules

29 Editing geodatabases by type Personal geodatabases Single user; cubicle editing on small datasets Editing locks at geodatabase level Two editors cannot edit within the same geodatabase at same time File geodatabase Single user; workgroup editing on small to very large datasets Editing locks at the feature level Two editors cannot edit the same object/feature class at same time ArcSDE geodatabases Extend the transaction model with Versions Enterprise-wide editing Multiuser editing without locking

30 Some editing workflows require special needs Editing with long transactions Isolate work across multiple sessions Edits do not impact others Example: Parcel editing Public Analyst Model what-if scenarios Simulate situations with versions Example: Disaster event planning Public Flood Workflow management Create versions of data for project stages Example: Land development Farmland Residential

31 Geodatabase versioning Multiple, virtual private workspaces Concurrent edit work on the same features Distributed (and disconnected) editing Geodatabase replication A foundational technology for historical archiving

32 Additional management considerations Upgrades Synchronization of geodatabase and application Personal and file geodatabase ArcSDE geodatabases Workgroup/Desktop Enterprise

33 Summary The geodatabase is simply: A storage container for spatial information and business rules. The geodatabase is designed: To improve your GIS data management and quality control workflows important for trustworthy spatial decision making and problem solving challenges.

34 Additional resources ArcGIS Resource Centers Blogs, Help, White papers, Getting Started Geodatabase and ArcSDE:

35 White papers Understanding Coordinate Management in the Geodatabase: wpaper&pid=43&metaid=1301 System Design Strategies

36 ESRI Learning Center ESRI provides numerous Instructor-led options for the Geodatabase : Building Geodatabases Geodatabase Design Concepts Data Management in the Multiuser Geodatabase Managing Editing Workflows in a Multiuser Geodatabase MORE Virtual Campus Many free and pay-for self-paced courses