GIS Programming 2011-1

(GIS 프로그래밍 )

( 아볼가셈 )
 2

Designing a GIS
database

아볼가셈 지리정보공학
 3
Lesson overview
 The database design procedure
 Needs assessment
 Conceptual and logical design
 Physical design
 Automation plan
 Pilot project
 Implementation

아볼가셈 지리정보공학
 4
The database design procedure
 Ideally a feedback loop
Needs assessment

Conceptual and
logical design
Prototyping
Physical design

Automation plan

Pilot project

Final implementation

아볼가셈 지리정보공학
 5
The database design procedure
 Needs assessment
 Determine the functions that will be supported by the GIS in this time-
consuming step
 To get the information necessary to complete this task by
 Interview potential users
 Tour operations
 Conduct inventories of data hardware, software, and personnel
 Conduct educational seminars
 Conceptual and logical design
 Determine database contents and how to logically organize the data in the
database
 The conceptual and logical design for the project in this course is based on
the concept of a shared database using ESRI data models, particularly the
geodatabase

아볼가셈 지리정보공학
 6
The database design procedure
 Physical design
 Physically structure the data so that it conforms to the ESRI
data structures
 A detailed database schema is also implemented in this phase,
along with plans for documentation and naming conventions
 Automation plan
 Establish automation procedures
 Prepare data for automation and implement the plan.
 If there are problems during this step, need to reevaluate the
design of the database

아볼가셈 지리정보공학
 7
The database design procedure
 Pilot project
 Test the functionality, performance, and flexibility of the
database design.
 At least one pilot study should be performed before full
implementation of the database
 Prototyping
 Remember to test
 Consistent feedback from users can avoid problems later

아볼가셈 지리정보공학
 8
Assessing needs
 Define objective
 What is the GIS intended to do?
 One-off project? On-going business?
 Decide what is needed to achieve it
 Ask the right people the right questions
Data

GIS
GIS Users
tasks
database

아볼가셈 지리정보공학
 9
Needs Assessment
 Perhaps no step in the database design process is as
critical and potentially time-consuming as the needs
assessment.
 The ability of the GIS to operate acceptably is directly
related to how well the necessary functions the GIS will
perform are understood.
 To gather the right information, must ask the right
people the right questions.
 This means conducting detailed interviews with end
users, data managers, supervisory personnel, and
anyone else who might be impacted by the new system

아볼가셈 지리정보공학
10
Needs Assessment –Con…

 From these interviews you should try to determine:

 What tasks are performed using spatial data?

 What tasks are performed that do not currently use

spatial data, but have a spatial component?

 What tasks are not currently performed, but are desired

 Who will be using the system and what their roles will be
아볼가셈 지리정보공학
11
Needs Assessment –cont…

 What types of products the system will need to produce

(maps, reports, etc.).

 What applications will need to be developed?

 What data will be needed to fulfill the stated tasks?

 Will the data be shared among multiple users?

 What special security measures are necessary?

아볼가셈 지리정보공학
12
Conceptual and logical design
 Identify geographic entities and attributes
 Save entities into feature classes
 Organize geographic entities into thematic layers
Real-world
entities Streets Soil types City parcels City trees

Feature class Lines Polygons Polygons Points

Name Type Land use Species

Attributes Class Permeability Zoning Age

Connectivity Soil class Open space Pruning

Behavior rules domain subtype schedule

아볼가셈 지리정보공학
13
Determining the data storage format
 Choose a format that meets your needs
 Can convert between formats if necessary
Shapefiles
 Think long-term
CAD files Coverages

Raster Geodatabase

GIS
database

아볼가셈 지리정보공학
14
Determining the data storage format
 Some issues to consider when choosing data formats are:
 Topology:
 Coverages store polygon and line topology.
 The geodatabase has multiple topology options.
 Shapefiles do not store topology.
 Vector versus raster data:
 Raster format is especially suited to data without clear store boundaries (continuous
data)
 such as temperature, pollution, and elevation.
 Vector formats discrete lines
 so they are more suited to discrete data such as streets and parcel boundaries.
 Consistency:
 The formats you choose should be standardized within your organization,
and easily converted if necessary.

아볼가셈 지리정보공학
15
Why the geodatabase?

Geodatabase
Scalability Validation

File- or Personal Spatial:

GDB (.gdb or .mdb) Geometric networks,
Topology
Attribute:
Enterprise GDB Subtypes, Domains
(ArcSDE + RDBMS) Relationship classes
Custom behaviors

아볼가셈 지리정보공학
16
Why the geodatabase?
 The geodatabase format offers many unique advantages for
geographic data storage.
 Scalability
 As user needs for security and data management grow, the geodatabase
can meet them.
 Domains and subtypes
 These properties, easily created and maintained in the geodatabase, make
data creation, editing, and maintenance much more efficient and would
require special programming to be achieved in other formats.
 Geometric Networks
 Using the geodatabase, can create geometric networks for modeling
connectivity and performing trace and path finding analysis.

아볼가셈 지리정보공학
17
Why the geodatabase?
 Topology
 Working with a geodatabase topology is much more flexible
than working with coverages
 because once the topology has been created you can stop at any point
in the process.
 During working with the Geodatabase, have the choice
between
 assigning or not assigning topology to data.
 Can also pick which topology rules in Geodatabase not at
coverage model.
 Custom features
 Because of its COM architecture, custom objects can be
programmed that represent real-world features more
accurately.
아볼가셈 지리정보공학
18
Physical design
 Detailed layout of conceptual and logical steps
 Identify sources of data
 Clarify database schema
 Tabular structure
 Relationships
 Coding schemes
 Domains and subtypes
 Determine documentation procedures
 Naming conventions
 Updating metadata
 Data dictionaries

아볼가셈 지리정보공학
19
Database schema
 Database structure or design
 Thinking through ahead of time saves effort later

아볼가셈 지리정보공학
20
Database schema
 The schema of a GIS database is its overall structure
 This part of the physical design translates the
conceptual or logical design into a detailed layout
 In addition to the data components, the schema should
also take into account the
 physical storage devices
 security issues
 user needs
 Once designed, a database schema should be difficult to
alter, but possible if truly necessary.
아볼가셈 지리정보공학
21
Choosing a projection
 Issues to consider
 Which spatial properties are most critical for the applications?
 Where is the study area?
 How large is the study area?
 Who will users share data with, and how often?

아볼가셈 지리정보공학
22
Automation plan

$
Part of the
Data purchase Data capture automation plan

Subtypes
Domain
Relationship

classes
Topology

Data conversion Data Geometric

networks
and editing aggregation
Annotation
아볼가셈 지리정보공학
23
Pilot project

 A small, focused test

 Determine if design works

 Lets evaluate the database design at a relatively low cost prior to

full-scale implementation

 The design should be tested for functionality, performance, and

flexibility

아볼가셈 지리정보공학
24
Pilot project – Con…

 To meet this objective, a pilot study should reflect the

types of tasks the GIS will be required to perform

 It should also use several different datasets to ensure

that the design is working across the board

 More than one pilot study may be required

아볼가셈 지리정보공학
25
Metadata: Documenting data
 Available for anything in ArcCatalog
 Including added file types (.txt, .ppt, etc.)
 Stored in Extensible Markup Language (XML)
 Similar to HTML but with custom tags
 Example:
<abstract>Boundary of Aquidneck
island</abstract>
 Stored with the data
 Moved/copied with the data if the data is managed by
ArcCatalog

아볼가셈 지리정보공학
26
Types of metadata
 Documentation
 Created by the user
Documentation

 Properties
 Created by ArcCatalog
 Preferences for
when to update Properties

아볼가셈 지리정보공학
27
Viewing metadata
 Style sheets define how XML data is presented
 Written using Extended Style sheet Language (XSL)

Style sheets

XML

FGDC ESRI

ISO

아볼가셈 지리정보공학
28
Editing metadata documentation
 Edit individual fields
Edit metadata

 Add enclosures
Metadata
 Embeds a copy of the file in the metadata properties

아볼가셈 지리정보공학
29
Setting metadata properties
 Select default style sheet
 Many to choose from

 Control when metadata is

created or updated
 Automatically on by default

 Select metadata editor

 FGDC, ISO, or create your own

아볼가셈 지리정보공학
30
Metadata import and export
 Uses standard formats
 Federal Geographic Data Committee (FGDC) Content
Standard for Digital Geospatial Metadata (CSDGM)
 Import
 FGDC CSDGM
 SGML, TXT, XML
Import Export
 XML
 Export
 FGDC CSDGM
 FAQ, HTML, SGML, TXT, XML
 HTML, XML

아볼가셈 지리정보공학
31

아볼가셈 지리정보공학
32
Exercise 6 overview

 6A: Given a needs assessment, create a simple, logical,

and physical design

 6B: Explore existing data from the database

 6C: Use ArcCatalog to explore and edit metadata

아볼가셈 지리정보공학
33
Lesson 6 review
 By skipping the needs assessment process, you can save time and
money with your database design. (T/F)
 If problems with the database design arise during the pilot project, it
is often most cost-effective to carry on with the final
implementation of the GIS, and resolve the design issues later. (T/F)
 Whenever data is copied or moved by ArcCatalog, any existing
metadata is copied or moved as well. (T/F)
 Metadata is written and stored in XFL. (T/F)
 Style sheets written in XSL define how metadata is presented. (T/F)

아볼가셈 지리정보공학
34
Lesson 6 review
 What are some of the advantages of using the
geodatabase to store data?
 What decisions are made at the conceptual and logical
design phases?
 In addition to data entry, what other issues should you
consider when preparing a data automation plan?
 Which of the following should be considered when
deciding on a storage format for the data:
a. Data type c. Conversion
b. Data security capabilities
c. Long-term plans d. All of the above

아볼가셈 지리정보공학
35

Go to exercise
section!
(Exercise 6-BookII:
Designing a GIS database)

아볼가셈 지리정보공학