Practical Session

Introduction to ArcMap

Lecture 4 (5 June 2021)

Dr. Asib Ahmed

Department of Environmental Science

BANGLADESH UNIVERSITY OF PROFESSIONALS
 Designing a Geodatabase

Steps of geodatabase design

1. Identify the information products that you
will create and manage with your GIS
• Your GIS database design should reflect the work of your
organization. Consider compiling and maintaining an inventory of
map products, analytic models, Web mapping applications, data
flows, database reports, key responsibilities, 3D views, and other
mission-based requirements for your organization. List the data
sources you currently use in this work. Use these to drive your
data design needs.
• Define the essential 2D and 3D digital basemaps for your
applications. Identify the set of map scales that will appear in
each basemap as you pan, zoom, and explore its contents.
2. Identify the key data themes based on your
information requirements
• Define more completely some of the key aspects of each data
theme. Determine how each dataset will be used—for editing, GIS
modeling and analysis, representing your business workflows, and
mapping and 3D display. Specify the map use, the data sources,
and the spatial representations for each specified map scale; data
accuracy and collection guidelines for each map view and 3D view;
how the theme is displayed, its symbology, text labels, and
annotation. Consider how each map layer will be displayed in an
integrated fashion with other key layers. For modeling and analysis,
consider how information will be used with other datasets (for
example, how they are combined and integrated). This will help you
to identify some key spatial relationships and data integrity rules.
Ensure that these 2D and 3D map display and analysis properties
are considered as part of your database design.
 3. Specify the scale ranges and the spatial
representations of each data theme at each scale

• Data is compiled for use at a specific range of map

scales. Associate your geographic representation for
each map scale. Geographic representation will often
change between map scales (for example, from
polygon to line or point). In many cases, you may need
to generalize the feature representations for use at
smaller scales. Rasters can be resampled using image
pyramids. In other situations, you may need to collect
alternative representations for different map scales.
4. Decompose each representation into one or
more geographic datasets

• Discrete features are modeled as feature classes of points, lines,

and polygons. You can consider advanced data types such as
topologies, networks, and terrains to model the relationships
between elements in a layer as well as across datasets.
• For raster datasets, mosaics and catalog collections are options
for managing very large collections.
• Surfaces can be modeled using features, such as contours, as
well as using rasters and terrains.
5. Define the tabular database structure and
behavior for descriptive attributes

• Identify attribute fields and column types.

Tables also might include attribute domains,
relationships, and subtypes. Define any valid values,
attribute ranges, and classifications (for use as
domains). Use subtypes to control behaviors. Identify
tabular relationships and associations for relationship
classes.
6. Define the spatial behavior, spatial relationships,
and integrity rules for your datasets

• For features, you can add spatial behavior and

capabilities and also characterize the spatial
relationships inherent in your related features for a
number of purposes using topologies, address locators,
networks, terrains, and so on. For example, use
topologies to model the spatial relationships of shared
geometry and to enforce integrity rules. Use address
locators to support geocoding. Use networks for tracing
and path finding. For rasters, you can decide if you need
a raster dataset or a raster catalog.
7.Propose a geodatabase design

• Define the set of geodatabase elements you want in your

design for each data theme. Study existing designs for
ideas and approaches that work
• Copy patterns and best practices from the ArcGIS Data
Models.
8. Design editing workflows and map display
properties.

• Define the editing procedures and integrity rules (for

example, all streets are split where they intersect other
streets and street segments connect at endpoints).
• Design editing workflows that help you to meet these
integrity rules for your data.
Define display properties for maps and 3D views.
• Determine the map display properties for each map
scale. These will be used to define map layers.
9. Assign responsibilities for building and
maintaining each data layer

• Determine who will be assigned the data maintenance

work within your organization or assigned to other
organizations. Understanding these roles is important.
You will need to design how data conversion and
transformation is used to import and export data across
various partner organizations.
10. Build a working prototype. Review and refine
your design

• Test your prototype design. Build a sample geodatabase

copy of your proposed design using a file, personal, or
ArcSDE Personal geodatabase. Build maps, run key
applications, and perform editing operations to test the
design's utility. Based on your prototype test results,
revise and refine your design. Once you have a working
schema, load a larger set of data (such as loading it into
an ArcSDE geodatabase) to check out production,
performance, scalability, and data management
workflows.
• This is an important step. Settle on your design before
you begin to populate your geodatabase.
11. Document your geodatabase design.

• Various methods can be used to describe your database design and

decisions. Use drawings, map layer examples, schema diagrams,
simple reports, and metadata documents.
• Some users like using UML (Unified Modeling Language). However,
UML is not sufficient on its own. UML cannot represent all the
geographic properties and decisions to be made. Also, UML does
not convey the key GIS design concepts such as thematic
organization, topology rules, and network connectivity. UML
provides no spatial insight into your design.
• Many users like using Visio to create a graphic representation of
their geodatabase schema such as those published with the ArcGIS
data models. ESRI provides a tool that can help you capture these
kinds of graphics of your data model elements using Visio.
Designing
Geodatabase
Importing features
and table in
Geodatabase
Creating
Feature
Dataset
Dataset Name
Define your
projection
Map Projection

A map projection is a systematic transformation of

the latitudes and longitudes of locations from the
surface of a sphere or an ellipsoid into locations on
a plane. Maps cannot be created without map
projections.
• Three common types of map projections are-

• Cylindrical Map Projections

• Conical Map Projections
• Azimuthal Map Projection
Perspective Cylindrical Projections
Azimuthal Projections
Light passing in Azimuthal Projections
Coordinate Systems
 Coordinate system

• A coordinate system defines the location of a point on a

planar or spherical surface.

• Types of coordinate system

A. Based on Nature
B. Based on Extent
 Types of coordinate system (contd…)

A. Based on Nature
1. Plane coordinate system

2. Geographic coordinate system

B. Based on Extent
1. Global coordinate system

2. Local coordinate system

• Coordinate systems provide a basis for identifying
locations on the earth's surface.
• Historically, many coordinate systems, have been
devised, with the oldest ones assuming a flat earth,
then later on a perfect sphere.
• Today's geographic coordinate systems are now
based on a cartographic spheroid (an ellipse rotated
about its axis) to more closely represent the earth's
true shape and surface.
• Additionally, map projection coordinate systems have
also been developed to determine how the curved
surface of the earth is depicted on a flat map.
• Coordinate systems are mathematical models
that describe how geometries are georeferenced
to the surface of the earth.
• A coordinate system includes information such as
the unit of measure and the earth model used.
• Depending on the type of coordinate system, it
may also include how the data was projected
from a spheroidal shape to a flat plane. A
coordinate system also defines the range of
valid X and Y properties of geometries using that
system.
• The following are the two types of coordinate
systems used in ArcGIS:
Geographic Coordinate Systems

• Defines a spheroidal or spherical model of the earth, and uses

angular units defining coordinates in terms of latitude and
longitude, which are angles calculated from the center of the
earth describing a position on its surface.

• A geographic coordinate system (GCS) uses a three-

dimensional spherical surface to define locations on the earth.
A GCS is often incorrectly called a datum, but a datum is only
one part of a GCS. A GCS includes an angular unit of measure,
a prime meridian, and a datum (based on a spheroid).
 Basic concepts
Datum
• A geodetic datum (plural datums, not data) is a reference from
which measurements are made.

• In surveying and geodesy, a datum is a set of reference points

on the Earth's surface against which position measurements are
made.
 Datum types

• Horizontal datums are used for describing a point on

the earth's surface, in latitude and longitude or another
coordinate system.

• Vertical datums are used to measure elevations or

underwater depths.
 Common Datums
•Previously, the most common spheroid was Clarke
1866; the North American Datum of 1927 (NAD27) is
based on that spheroid, and has its center in Kansas.
•A newer, satellite measured spheroid is the World
Geodetic System 1984 (WGS84) spheroid, which is
more or less identical to Geodetic Reference System
1980 (GRS80). The GPS system uses WGS84.
•NAD83 is based on these spheroids and is measured
from the center of the spheroid, rather than the
surface.
•WGS84 is considered to be a datum and a spheroid
Geodetic Datum and Projections used
in Bangladesh
• Gulshan 303
• Everest Bangladesh
• WGS 1984
 Geodetic Datum used in Bangladesh
• Gulshan 303 is a geodetic datum first defined in
1995 and is suitable for use in Bangladesh -
onshore and offshore. Gulshan 303 references the
Everest 1830 (1937 Adjustment) ellipsoid and the
Greenwich prime meridian. Gulshan 303 origin is
Gulshan garden, Dhaka. Gulshan 303 is a geodetic
datum for Geodetic survey, cadastre, topographic
mapping, engineering survey. It was defined by
information from Survey of Bangladesh via IGN
Paris and Tullow Oil. Network of more than 140
control points observed and adjusted in 1995 by
Japan International Cooperation Agency (JICA).
 Geoid and Ellipsoid
Geoid
• An imaginary surface that coincides with mean sea level in the
ocean and its extension through the continents.
• A hypothetical surface that corresponds to mean sea level and
extends at the same level under the continents.
• The geoid is used as a reference surface for the accurate
measurement of elevations on the Earth's surface.

Ellipsoid
• A geometric surface, symmetrical about the three coordinate
axes, whose plane sections are ellipsesor circles.
Geoid and Ellipsoid (Contd….)
Geoid and Ellipsoid (Contd….)
Geoid and Ellipsoid (Contd….)
Projected Coordinate Systems

• Uses linear units defining positions on the earth's surface

as projected to a flat plane. A projection is a specific
mathematical model for converting the spheroidal data to a
flat plane. A projected coordinate system is always based on
an underlying geographical coordinate system with a
projection applied to it.
 Types of coordinate systems
• A projected coordinate system such as universal
transverse Mercator (UTM), Albers Equal Area, or
Robinson, all of which (along with numerous other map
projection models) provide various mechanisms to project
maps of the earth's spherical surface onto a two-
dimensional Cartesian coordinate plane. Projected
coordinate systems are referred to as map projections.
• Coordinate systems (both geographic and projected)
provide a framework for defining real-world locations.
 Projection System for Bangladesh

• Survey of Bangladesh: BTM, Recently BUTM

• LGED : Lambert Conformal Conic
• SRDI and BARC : Everest Bangladesh
• DLRS: Everest Bangladesh
• Dhaka City Corporation: Gulshan 303 Bangladesh
A point is referenced by its longitude
and latitude values. Longitude and
latitude are angles measured from
the earth's center to a point on the
earth's surface. The angles often are
measured in degrees (or in grads).
The following illustration shows the
world as a globe with longitude and
latitude values.
False northing and false easting

False northing is a linear value applied to the origin of the y

coordinates.

False easting is a linear value applied to the origin of the x

coordinates.

False easting and northing values are usually applied to ensure

that all x and y values are positive.
Inverse Flattening

In geodesy publications, however, it is common to specify

the semi-major axis (equatorial radius) a and the
flattening f, defined as:

That is, f is the amount of flattening at each pole, relative

to the radius at the equator. This is often expressed as a
fraction 1/m; m = 1/f then being the "inverse flattening".
A great many other ellipse parameters are used in
geodesy but they can all be related to one or two of the
set a, b and f.
Name: Bangladesh Universal Transverse Mercator
(BUTM)
Projection: Transverse_Mercator
False_Easting: 500000.0
False_Northing: 0.0
Central_Meridian: 90.0
Scale_Factor: 0.9996
Latitude_Of_Origin: 0.0
Linear Unit: Meter
Datum: WGS1984
Spheroid: WGS1984
Name : Bangladesh Transverse Mercator (BTM)
Projection: Transverse_Mercator
False_Easting: 500000.000000
False_Northing: ¬2000000.000000
Central_Meridian: 90.000000
Scale_Factor: 0.999600
Latitude_Of_Origin: 0.000000
Linear Unit: Meter (1.000000)
Geographic Coordinate System: GCS_WGS_1984
Angular Unit: Degree (0.017453292519943299)
Prime Meridian: Greenwich (0.000000000000000000)
Datum: D_WGS_1984
Spheroid: WGS_1984
Semimajor Axis: 6378137.000000000000000000
Semiminor Axis: 6356752.314245179300000000
Creating New
Feature Class
Dept. of Environmental Science
FACULTY OF SCIENCE AND TECHNOLOGY
Dept. of Environmental Science
FACULTY OF SCIENCE AND TECHNOLOGY