• Presenter Names

Presentation Title

Billie Leff, Esri Professional Services

Joetta Kreck, US Army Geospatial Center

21st Century Organizational Mapping Trends

Evolution of Map Products

Print Maps

Mobile, Web and

Vector Tile MapsPDFs on the Web, Data Visualizations

and Dashboards

Content Portrayal

Mapping Trend Context

Vector Portrayal

Standards Prototyping

Cartographic Review &

Standards Prototyping

21st Century Organizational Mapping Trends

Print Maps

Content Portrayal

1. From print to digital

2. From rules and requirements to best practices

3. From custom and COTS to cross-platform

Mobile, Web and

Vector Tile MapsPDFs on the Web, Data Visualizations

and Dashboards

Mapping Evolution 1: Print to Digital

Driven by…

• Evolution of technology

Mapping Evolution 1: Print to Digital

Driven by…

• Evolution of technology

• Need for disconnected field use

Easy to interpret multi-scale, vector topographic

maps for day, dusk and night

Multi-scale, vector topographic maps with

extractable component contours and land

use/cover

Mapping Evolution 1: Print to Digital

Driven by…

• Evolution of technology

• Need for disconnected field use

• Need for crisper and performant graphics

Mapping Evolution 1: Print to Digital

What comes along with it…

• Vector tiles rather than raster cache

• Multi-scale rather than single-scale maps

• Lots of data rather than single authoritative source

• Efficient cartographic data models

• Performant and simple rather than detailed products

TLM Print SpecMixed Forest

Digital TM ConceptMixed Forest

• Don’t stop at publishing existing print products

• Not all at once

• Focus on business use cases

• Prioritize

• Use what you got and make what matters

How Do Organizations “Handle” Print to Digital?

Business

TechnologyAgile

Mapping Evolution 2: Rules/Requirements to Best Practices

Driven by…

• Map use is pervasive

Mapping Evolution 2: Rules/Requirements to Best Practices

Driven by…

• Map use is pervasive

• Everyone is a “Cartographer”

• Maps are defined by users and use cases

AIR BLO END LIN OTH

DIV

Mapping Evolution 2: Rules/Requirements to Best Practices

What comes along with it…

• Use cases rather than requirements

Existing

As the wilderness fire Communications

Specialist, I need to easily identify the

infrastructure I am responsible for maintaining.

As the Army Guidance Support Specialist, I

need to prioritize airplane landing sites at a

predefined location around the world.

Mapping Evolution 2: Rules/Requirements to Best Practices

What comes along with it…

• Use cases rather than requirements

• Intuitive rather than production manual

• Using semiology and dual encoding

rather than single symbol for everything

Proposed

As the wilderness fire Communications

Specialist, I need to easily identify the

infrastructure I am responsible for maintaining.

As the Army Guidance Support Specialist, I

need to prioritize airplane landing sites at a

predefined location around the world.

What helps organizations abandon rules for best practices?

• Understand and always use business use cases

• Use iterative workflows

What helps organizations abandon rules for best practices?

• Understand and always use business use cases

• Use iterative workflows

• Prioritize and balance

• Have internal support

Business

TechnologyAgile Diversity

Mapping Evolution 3: Data to Portrayal Driven

Driven by…

• Need for interoperability

• Need for consistent look and feel

• Need for quick interpretation

GGDM

NGA

Open Source

MGCP

Commercial

Mapping Evolution 3: Data to Portrayal Driven

F_CODE = 'AP030' AND

PCF IN (2,-999999) AND

ZI016_WTC IN (1,4, -999999) AND

ZI016_ROC IN (7,8,9,10,11,12,-999999) AND

(THR IN (1001) OR

RTY IN (1,2) OR

LTN >=4 OR

SEP IN (1001) OR

MES IN (1001))

Hardsurface

Loosesurface

Not intactFair weather

Existing

Mapping Evolution 3: Data to Portrayal Driven

Feature = Road AND

Importance = Primary AND

Condition = Hard surface

Hardsurface

Loosesurface

Not intact

Proposed

Mapping Evolution 3: Data to Portrayal Driven

Mapping Evolution 3: Data to Portrayal Driven

What comes along with it…

• Taxonomy which can grow rather than predefined symbology

Dual encoding at

small scale

Feature labeling at

larger scale

No labeling or dual encoding at

largest scale

Mapping Evolution 3: Data to Portrayal Driven

What comes along with it…

• Taxonomy which can grow rather than predefined symbology

• New workflows which allow you to go from any data to a predefined portrayal

Source data

e.g. GGDM composite

Carto DB

Portrayal

DB

Multi-scale and multi-format

digital vector portrayal

Data generalization,

conflation and other tools

Mapping Evolution 3: Data to Portrayal Driven

What comes along with it…

• Taxonomy which can grow rather than predefined symbology

• New workflows which allow you to go from any data to a predefined portrayal

• Cartographic data models optimized for symbology and labeling

• Portrayal database rather than production procedures

What Helps Move from Data to Portrayal in Map Operations?

• Use cases and iterative workflows

• Line your ducks in a row but be flexible and plan for interoperability

• Know your organization and its change tolerance

• Recognize what you are not changing

Business

TechnologyAgile Diversity

21st Century Organizational Mapping Trends

Print

Rules and Requirements

Technology-based

Digital

Best Practices

Cross Platform

1. Re-evaluate business use cases from scratch

2. Use Agile portrayal development methods

3. Create flexible cross-platform portrayal systems