+ All Categories
Home > Software > Data Processing Workflow for the National Geographic World Atlas Mobile App

Data Processing Workflow for the National Geographic World Atlas Mobile App

Date post: 16-Apr-2017
Category:
Upload: mousebird
View: 478 times
Download: 0 times
Share this document with a friend
34
Data Processing Workflow for the National Geographic World Atlas Mobile App Rosemary Wardley Steve Gifford
Transcript

Data Processing Workflow for the

National Geographic World Atlas Mobile App

Rosemary Wardley

Steve Gifford

Introduction

World Atlas App

Previous versions & Problems

Goals for new app

Data production

Data processing

Conclusions

World Atlas App for iPhone/iPad

Digital & Interactive Atlas

Political basemaps

Flags & Facts

Search Index

Statistical Overlays

Distance Calculator

How  it  was  done  before

How  it  was  done  before

How  it  was  done  before

How  it  was  done  before

How  it  was  done  before

App  Design/UX  Flaws

App  Design/UX  Flaws

App  Design/UX  Flaws

Goals  for  World  Atlas  v.4

Tighter  control  over  the  data  for  editorial  purposes  Leverage  more  of  our  databases  

Reduce  the  amount  of  custom  processing  Fit  into  evolving  Editorial/Production  workflow  App  data  that  is  easier  to  update  &  replicate  Maintain  NG  brand  identity    

Add  flexibility  &  reduce  size  of  the  App  Hybrid  Raster  &  Vector  process

Full  Workflow

Data  Production

Inputs:  Standard  Carto  Datasets

75  Million  Zooms  0-­‐2

40  Million  Zooms  2-­‐4

20  Million  Zooms  5-­‐6

10  Million  Zooms  7-­‐8

Editorial  &  Production  Steps

GFID  match

Flags  &  Facts

Search  Index  Creation

GIS  Database  Steps

Final  Product

Raster  &  Vector  Outputs

Background  Raster

Full  PDF

Symbol  Shapefiles

Boundary  Shapefiles

Data  Processing

Why Vectors?Image Artifacts

Blurry text & symbols

Tile edge discontinuities

Size

Images are big

Vectors are small

Selection Data

Tapping logic simpler

Vector ProcessingSymbols

Points from GIS database

Both visual and selection

Text

Extracted from PDF

Purely visual

Boundaries

Areals from GIS database

Invisible, just for selection

Background Raster

Including

Roads, Rivers

Fills, stipples

Etc (lots of etc)

Excluding

Symbols

Text

Text ExtractionParse the PDF

Need for each character

Location

Rotation

Size

Font

Output to Shapefile

Uploading to MapboxImage basemaps

Low res everything

High res blanks

Vectors

Symbols

Text

Boundaries

Anatomy of a Tile

How did it go?

App is released and working

Text is Sharp

Symbols are Sharp

Data size is way down

Old app: 500MB per layer

New app:75MB per layer

Conclusions:  Data  Update  Process

Conclusions:  Software  Used

Mapbox Studio

Wrapup & Contact

Rosemary [email protected]  

nationalgeographic.com

Steve [email protected]  

mousebird.github.io/WhirlyGlobe/  


Recommended