08 Mobile Webmaps
08 Mobile Webmaps
EGE 2312
Mobile/Webmaps
• Basics
– Lecture 1: map elements
– Lecture 2: maps for reports, PowerPoint and other small publications
– Lecture 3: multidimensional maps with alternative software
• Overview + Introduction to R
• Making maps with R
• Introduction to Python
• Making maps with Python
• Web maps
– Lecture 4: maps for the web (paper-web)
– Lecture 5: maps for the web(new elements)
– Lecture 6: maps for the web(color, layout, animation)
• Map Infographics
– Lecture 7: Map infographics
– Lecture 8: Map infographics
• CATS/Review
– Lecture 9: CAT I
– Lecture 10: Review
– Lecture 11: Review
–
1/13/2020
Lecture 12: CAT II
Introduction
3
Introduction (2)
4
Introduction(3)
5
Introduction(4)
6
Webmapping : what is it?
7
Why Webmapping?
9
FOSS and its use in web mapping
• Free and Open Source software (FOSS) means that you have
the right to download and look at the source code for the
program you are using. Most people don't need to do this and
don't much care if they have this right or not, to them open
source software just means that it is free.
• Open source software is now used in mission critical solutions
by large and small businesses as well as millions of home users
systems.
10
Principles of Open Standards
• Availability - Open Standards are available for all to read and implement.
• Maximize End-User Choice Open Standards create a fair, competitive market for
implementations of the standard. They do not lock the customer in to a particular
vendor or group.
• Royalty - Open Standards are free for all to implement, with no royalty or fee.
• Discrimination - Open Standards and the organizations that administer them do
not favor one implementer over another for any reason other than the technical
standards compliance of a vendor's implementation.
• Extension or Subset Implementations of Open Standards may be extended, or
offered in subset form.
• Predatory Practices Open Standards may employ license terms that protect against
subversion of the standard by embrace-and-extend tactics.
11
Types of Web Maps
• Static web maps - Static maps, as their name implies, are essentially
the digital equivalents of paper maps. While the user may be able to
zoom in or out on the map, the content of the map is static
• Dynamically-created web maps - In contrast to static web maps,
dynamically created web maps are generated on the fly when the
user loads the associated web page e.g population figures compiled
by a census
• Distributed web maps- those compiled from distributed data
sources
• Animated web maps - Animated web maps are most often
associated with the display of snapshots of the same map variable
taken at different times.
12
Types of Web Maps(2)
13
Example: Analytic Vs. Animated
14
Historical Development – 1st
Generation
Web 2nd
What Indepe
1990 1993 ?
1995 Inter 1997
ndent 2000 Generati
face on
15
Historical Development - 2nd
Generation
Lets
Where
200 Baby 200 get 200 Diversi acceptan
2010 2020 are
4 steps 6 involve 8 fy ce
we?
d
16
System architecture for web mapping
17
System architecture for web
mapping(2)
• desktop workstations that are used • a geospatial web
by administrators and internal services server that has specialized
client applications. software and processing power for
• These machines will also be used to drawing maps, responding to
prepare data, author maps, and feature queries, and performing GIS
sometimes administer the other analysis operations.
machines. • a web server that acts as a web
• a database and/or entry point into your organization's
file server holding all of your GIS network. This is also called a proxy
data. This machine might be server. It is protected by firewalls
equipped with redundant storage that shield malicious traffic into your
mechanisms and regular backup internal network. It's also a place
scripts that prevent the loss of data. where you can put web application
• many client applications that use code (such as HTML and JavaScript
the web map. These can be apps files) for your web maps.
that run on your desktop
workstation or they could be mobile
apps.
18
Elements of a web map
19
Map elements
1/13/2020 21
Of Mice and Touch Screens
1/13/2020 22
WIMP interface
1/13/2020 23
WIMP interface
1/13/2020 24
Post-WIMP interface
1/13/2020 25
Future is post-WIMP
1/13/2020 26
NEW INTERACTIVE MAP ELEMENTS
1/13/2020 27
New Interactive Map Elements
• traditional map elements and their design are still crucial for
effective map communication.
• The main difference is that most map elements can now be
better thought of as GUIs.
• Thus, the purpose of most map elements may not have
changed, but rather their design has become very different.
• For example, many map elements for Web maps can be
designed far more compactly and subsequently present more
information once someone has decided to interact with them.
1/13/2020 28
Title/Splash Screen
1/13/2020 29
Title/Splash Screen
1/13/2020 30
Mapped Area
1/13/2020 32
Pan User Interfaces Panning
1/13/2020 34
Arrow Keys
• arrow keys are extremely different from, and far superior to,
panning arrows.
• In fact, whenever possible, I recommend incorporating arrow
keys into one’s map design when panning is required.
• However, there is a key caveat to this: make sure arrow keys
are not the only method of panning available.
1/13/2020 35
Zoom Bars
1/13/2020 36
Zoom Bars
• Considerations
– most zoom bars are vertical in nature.
– the top of the zoom bar is the maximum map scale (i.e., more detail,
less geographic area covered, less generalization).
– The bottom of the zoom bar is the minimum map scale
– It is also convention to place it to the left or right side of the map so
that it is readily available when desired but not competing with the
data on the map.
– Akin to scale bars on print maps, less is often more. The less gaudy
zoom bars look, the less distracting they are when someone is
reading the map.
1/13/2020 37
Plus and Minus Zoom Buttons
1/13/2020 38
Double Click and Tap
1/13/2020 39
Scroll Wheel and Pinch to Zoom
1/13/2020 40
Keyboard Shortcuts
1/13/2020 41
Rectangle Zoom
1/13/2020 42
Pros and Cons – Zoom tools
1/13/2020 43
Pros and Cons – Zoom tools
1/13/2020 44
Locator Maps
• Locator maps are inset maps that show where the main mapped area is located
within a broader geographical context.
• They are useful for large-scale maps (i.e., maps showing small areas) because
people often have a difficult time referencing the location of what they are
viewing based on their mental maps alone.
• Early on, most Web maps included locator maps, and they are also a good idea
to include with your large-scale maps.
• Locator maps have an added bonus - Not only do they help map users find
where they are in the world, so to speak, they also can function as an
alternative zoom tool.
• Many locator maps let the user drag a rectangle over them or pan the area
currently being viewed by directly interacting with the locator map.
• This offers map users an additional method of zooming and getting to where
they want to be as quickly and directly as possible.
1/13/2020 45
Locator Maps
1/13/2020 46
Menu Design
1/13/2020 47
Menu Design
1/13/2020 48
Menu Design
1/13/2020 49
Menu Design
1/13/2020 50
Legend
1/13/2020 51
Legend
1/13/2020 52
Legend
1/13/2020 53
Legend
1/13/2020 54
Web Cartography
Layout
1/13/2020 55
Drastic changes
1/13/2020 56
New Visual Hierarchies for Web Map
Elements
1/13/2020 57
Screen Real Estate, Resolution, and the
Pixel Problem
• Three things will inevitably affect every Web map’s layout: (1)
screen real estate, (2) screen resolution, and (3) pixels per
inch.
• Screen real estate refers to the amount of space you have to
work with on any screened device. You have a fixed amount of
space to show everything you want to show.
• there are several major hurdles to deal with as a Web
cartographer with regard to screen real estate. First, unlike
with a print map, the Web cartographer never knows how
large a screen the map user will have
1/13/2020 58
Screen Real Estate
• Before you begin any project, you want to consider all of the
different screen sizes your Web map is likely to be viewed on and
design accordingly.
• design the same map several times to facilitate functionality in
different browsers or for different size mobile devices.
• Never settle for a one-size-fits-all Web map layout.
• Whenever possible, include code in your HTML that will allow your
map to determine the resolution and screen size of the user’s
device.
• Use screen responsive interfaces such as boostrap
• One rule of thumb is always to design your map for the device with
the smallest screen you want people to use your map on.
1/13/2020 59
Screen Resolution
• It is therefore good
practice to design your
map with a resolution
that will fit nicely on a
majority of screens
without the need for
scrolling.
1/13/2020 60
Two Types of Web Map Layouts
1/13/2020 61
Fluid Map Layout
• One potential
disadvantage, however, is
that this type of map layout
can start to look very busy.
• If not designed well, it can
result in an unbalanced
map that detracts from the
information being
communicated.
1/13/2020 62
Compartmentalized Map Layout
1/13/2020 63
Compartmentalized Map Layout
1/13/2020 64
Which layout?
Compartmetnalzied Fluid
• abundant in maps designed for Web • proliferate on mobile devices on which
browsers. screen real estate is at a premium.
• These maps frequently make use of • tend to hide features under icon-based
HTML divisions (<div> tags) that are menus and submenus - have such menus
collapse as soon as someone clicks
styled with Cascading Style Sheets (CSS). outside them
• maps function well when there is ample • The arrangement of menu icons can take
screen real estate. many forms. However, one generally
• Often lack rhetorical and aesthetic flair wants to place these icons where people
focus their visual gaze the least
• People are familiar with the layout.
• map elements simply do not lend
• Creating a fragmented map layout also themselves to small-screen devices and
lends a feeling of professional, business- should be kept off a fluid map layout in
like design these circumstances e.g title
• such maps are often a bit easier to • Panning arrows—ugh—and zoom bars
design using HTML and CSS are best omitted, or at least hidden and
minimized
1/13/2020 65
How to Design an Effective Web Map
Layout
1/13/2020 66
How to Design an Effective Web Map
Layout
• Determine which elements of the visual hierarchy need to
stand out.
– Which map elements must be promoted for the map to make the
most sense?
– I recommend making a list of all of the map elements you think your
map needs. Then, go through and prioritize them. Choose the top
three or four. Those are the map elements that are needed.
Everything else is typically supplementary.
1/13/2020 67
How to Design an Effective Web Map
Layout
• Design mock layouts and user test.
– Have you exhausted all of your layout options?
– The best Web map layouts are not whipped together at the end of a
long programming session; they are well thought out and have been
compared to a litany of other potential layouts your computer, pull
out a notebook, draw a grid on the page, and start sketching every
type of layout imaginable.
– Move your map elements and legends around, paying particular
attention to the visual hierarchy you have decided on in the previous
step
1/13/2020 68
How to Design an Effective Web Map
Layout
• Finalize the map layout and user test it again.
– Are there any unforeseen issues? For example, are there certain
aspects of your ideal map layout that are impossible to implement
due to the Web service, API, or technology you are using?
– Once you have finalized your map, it is wise to user test it to make
sure it is fully functional.
1/13/2020 69
Web Cartography
Color
1/13/2020 70
Color
1/13/2020 71
Basemap colors
• White and light gray are great choices for base map colors
because they act as a neutral canvas for other map symbols to
jump out as figures.
• what if you want to include shaded relief? There are generally
two ways to do this: grayscale shaded relief or hypsometric
tinting. Hypsometric tinting shows elevation change through
the use of a color scheme
1/13/2020 72
Choosing Thematic Map Colors
1/13/2020 73
Choosing Thematic Map Colors
1/13/2020 74
Typography
1/13/2020 75
Font rules
• No More Than Two Fonts per Map - Sure, there are always exceptions to
the rule that there should be no more than two fonts per map.
• Font Styles and Properties Indicate Different Things - Differences in type
size, case, and style still have the same visual impact on the Web map user
as they do in print maps
• When Possible, Ditch Serif Fonts - There is a new cartographic convention
that has evolved with Web cartography:
– use only sans-serif fonts (Figure 6.3). The avoidance of fonts with serifs in Web
maps developed with good reason; resolution on most digital media is
mediocre.
– Serif fonts are actually more difficult to read on backlit displays (i.e., LCDs,
cathode-ray tubes [CRTs]).
• Size Does Matter
– Not all fonts are created equally.
– The best fonts for screens have generous x-heights, spacing between letters,
internal letter widths, and consistent thicknesses
1/13/2020 76
Font rules
1/13/2020 77
Interactive text
1/13/2020 78
What font type then?
1/13/2020 79
Symbology
1/13/2020 80
Symbology
1/13/2020 81
Assignment 08
Each student has been allocated a country to prepare a webmap using ArcGIS
online (see attached excel sheet). The Webmap should contain :
1. The 1st and 2nd level boundaries ( e.g Counties//subcounties in Kenya)
2. Major cities
3. Main Highways, railways and airports
4. Major natural vegetation and water bodies
5. Male/Female population (for level 2 e.g. counties of Kenya)
6. Baselayers : Satellite, terrain
Required :
1. Download data from DivaGIS or any other site
2. Upload your data to your ArcGIS online account (all of you have!)
3. Prepare the Webmap using ArGIS online tools
4. Submit the link via the classrep
Deadline: 27th January 2020 (next week)
82