Massachusetts Institute of Technology
Department of Urban Studies and Planning


11.188: Urban Planning and Social Science Laboratory

Lecture 2: Cartography, Coordinate Systems, Relational Databases, & Data Management

February 13, 2019,  Joe Ferreira

(including notes by Prof. Joe Ferreira, Prof. Mike Flaxman, Laura Delgado, and former Visting Prof. Zhong-Rhen Peng)


Administrative notes regarding lab exercises and schedule

Outline of Today



GIS Example:

 

 

(1) Site Selection for Low Cost Grocery Store Chain



 

Map elements and thematic mapping:
Symbology, classification, and normalization

 

Elements of the Map

Scale

Ratio Scales

            1:10,000, or 1:100,000 or 1/100,000
            No units, just one unit on the map equals a designated number of units on the ground.

Verbal Scales:

     One inch represents 2,000 feet (1:24,000 because there are 24,000 inches in 2,000 square feet).

     One centimeter represents 20 kilometers (1:2,000,000)

Printout vs. onscreen:

10 foot pixel + 72 pixels per inch onscreen

   ==> One inch represents 720 feet (1:8,600) -

But some screens have higher/lower pixel densities; not all screens have square pixels; also, screendump to printer will change scale since printer will have different dot-density than the screen

Beware! Good GIS software will try to match screen and printer properties to software settings so screen and printouts will show appropriate scale and show correct scalebars. For the scale to be meaningful, display units and hardware choices must be properly identified.

Large Scale or Small Scale

In general,

         Large scale: >= 1:24,000 (the representative fraction is large, but they are good for        *small* area representation - city block)

         Small scale: <= 1:500,000 (good for *large* area representation - metro area)

  Important concept: “Minimum Mapping Unit" (MMU)

 

Typical Scales Used

In Metric System:

1:10,000 (example: German national basemaps – individual houses shown) 1:25,000 ... 1:100,000


In American System:

1:9,600 (one inch represents 800 feet)

1:24,000 (one inch represents 2000 feet) – typical USGS “quad sheet”

1:62,500 (one inch represents slightly less than one mile)

 

Key Cartographic Principals

Maps are a medium of communication

              So…know your audience

              Or if you don’t/can’t, use the “10 foot rule”

                     Can an average citizen read & comprehend E sized plot at 10’?

                     Or a page print at 8.5x11” – font size at least 12 point

A good map should never be a “GIS Data Dump”

Selective emphasis is key

The hard part is removing data, when in doubt - delete

Divide mapped elements into “figure / ground”

Figure = Foreground elements – the essential story of the map

Ground = Background elements – provide context, but don’t overwhelm

==> Use visual symbols, colors, and shades to emphasize foreground, & minimize background clutter


Colors and Categories

Human cognitive limit / rule of thumb:

Try to limit the number of thematic colors

  • If not possible, try creating logical visual subgroups
    • example: housing in 3 shades of orange, commercial 3 shades of red, etc.
  • Hard to distinguish more than 3-4 tones within same hue
    • Even harder when your map is reproduced in grayscale…

ArcGIS color defaults are *random* saturated colors

  • Tip #1: desaturate colors, especially background colors or those covering large areas of the map
  • Tip #2: reserve bright, saturated colors either for foreground elements, or small polygons
  • Tip #3: turn *off* the outline of polygons, particularly for background polygons or small polygons

Six Principal Visual Variables

Use contrasting symbols to portray geographic differences

For qualitative differences

Use shape, texture and hue (e.g., land use types).

For quantitative differences

Use size to show variation in amount or count
(e.g., population, number of crimes),

Use graytone or hue to show differences in ratio or intensity
(e.g., proportion of household in poverty, population density).

 

Southern New England Counties

Southern New England Counties



Map Projections and Coordinate Systems

Datums, Map Projections, & Coordinate Systems

      What is the minimum information needed to precisely determine
      location on the surface of the planet?

Need *both* a known coordinate system
and a known model of the earth’s surface

If you only know one, you can be hundreds of meters off target

      -literally

An Ellipsoid or a Datum are abstractions of the surface of the earth

WG84 (the World Geodetic System of 1984) is a standard ellipsoid.

In North America, the most recent ellipsoid data it is called the North American Datum of 1983 (NAD83) (the earlier version is NAD27).

Geographic Reference System: Latitude and Longitude

Axis: the center of earth rotation.

Equator: The plane through the center of mass perpendicular to the axis.

Longitude: lines slicing the earth parallel to the axis, and perpendicular to the plane of equator.

The line going through Greenwich in London has 0 longitude.

Range from 0 to 360 degrees, or 180 degree west (-) to 180 degree east (+).


Latitude

Latitude is defined based on ellipsoid representing the shape of the earth.

See: Prof. Peter Dana's notes on projections and coordinate systems ( U. of Colorado ) http://foote.geography.uconn.edu/gcraft/notes/coordsys/coordsys_f.html

<Click the images below to enlarge...>

Latitude definition:

A line drawn through a point of interest perpendicular to the ellipsoid at that location, the angle made by this line with the plane of Equator is the latitude of that point.

Ranges from 90 degree south (-) to 90 degree north (+).

 

What do Latitude and Longitude mean?

Two points on the same longitude, separated by one degree of latitude are 1/360 of the circumference of earth apart, or about 111 km apart.

One minute latitude is 1.86 km.

One second latitude is 30 m.

For the same latitude, one minute of longitude separation corresponds to different distances depending on the latitude (111 km at equator, nothing at the poles!).

Nowadays, latitude/longitude often expressed in decimal degrees.

Distance calculation using latitude and longitude


Cartesian Coordinate System


Map Projections


For additional information, see example from Prof. Peter Dana's notes (
U. of Colorado)
http://http://foote.geography.uconn.edu/gcraft/notes/mapproj/mapproj.html

NOTE: There is no need to memorize the formulas or properties of various coordinate systems. Just understand the concepts and how to find more information about specific cases and coordinate conversion



Map Projection Classifications based on preservation properties

 

Map Projection classifications based on physical surface models

 

Unprojected projection: Plate Carrée or Cylindrical equidistance Projection

 

The Universal Transverse Mercator (UTM) Projection

 

State Plane Coordinates and other local systems

 

Converting Georeferences

More info on Coordinate systems and projections




Relational Database Modeling


Limitations of 'flat-file' data model & motivation for relational model (for attributes)

 

A Table (relation)

           Attribute name


 Tuples  
 

 

 

 


 

 


Rows: tuples that specify particular relations among values of each attribute
Columns: attributes describing a feature of interest
Domain: data types and range of values for an attribute (like integer, strings, floats, dates, city names, etc.
)

 

Relational Databases

 

Structured Query Language (SQL)

            SELECT columns

            FROM tables

            WHERE row conditions and joins are matched

            GROUP BY non-aggregated columns

            ORDER BY certain columns

e.g., join city table to state table, parcel table to owner table, or house sales table to house table

 

 



<<< lecture ends here - additional notes below are extra >>>


 






Other (abstract) Database Concepts (generally beyond scope of class)

 

Distributed databases and Federated databases

n Distributed databases refer to one database (or data replicates) that are distributed across multiple sites.

n Federated databases refer to many similar databases that are distributed across multiple sites but are more loosely coupled and additional rules may be needed to cross-reference tables meaningfully

n Federated databases are also called distributed relational database with fragmentations.

 

Relational data model (our focus)

n      Collection of interrelated tables

n       Highly structured data schemas and data types with data dictionary

n       We'll examine US Census Bureau examples in Lab #5

Relational Database as Entity-Relationship Model

n E-R model sees the world as inter-related entities (tables);

n Use MS-Access to build E-R diagram for the three city/state tables: lec5_cities.mdb.

n  Entities (or entity types like cities and states in our example) are related with each other by a relationship (linking primary and foreign keys - e.g, which city is in which state)

n  E-R model uses E-R diagrams to describe relations between entity types (generally one-to-many connections)

n E-R model describes the static state of the entity types.

 

Object-Oriented Model - one alternative to E-R for RDBMS

n Object-oriented model sees the world as inter-related objects.

n Object is dynamic and has its own lifespan. Hence OO model is used to deal with the dynamic nature of real-world object.

n Object = static state + functionality

n Object with similar behaviors are organized into types, a semantic concept.

n Object Class = data structure + methods, an implementation construct.

 


 

Other Noters about RDBMS and relational tables in ArcGIS

 

Joining and Relating Tables in ArcGIS
n          Join in ArcGIS appends the attributes of the non-spatial table to the spatial (layer) attribute table.
n          Relate in ArcGIS does not append attributes; only establishes a logical relationship so that when you select one record in one table you can see the matching records in the other table.
Don't get confused between ArcGIS 'relate' (which describes the relationship between two tables, and RDBMS terminology where 'relation' = a table)
 
When to Use Join and Relate
n       Relate is preferred if the non-spatial table is maintained and updated constantly while the spatial data is not. (e.g., Mass towns shapefile plus summary table with data for each town)
n       Use relate when the relationship is many-to-many.
n       Use relate when you have a very large non-spatial table and you don't need all the attributes in the table.
n       Columns in 'related' table cannot be thematically mapped - they must first be 'joined' in
n       In other situations, you could use either.



Last modified 12 February 2019 [jf]

Back to the 11.188 Home Page.
Back to the CRON Home Page.