DGIWG 124 Defence Profile of OGC's Web Map Tile Service

Total Page:16

File Type:pdf, Size:1020Kb

DGIWG 124 Defence Profile of OGC's Web Map Tile Service DGIWG 124 Defence Profile of OGC’s Web Map Tile Service 1.0 Document type: Standard Document subtype: Implementation Profile Profile of: The Open Geospatial Consortium’s Web Map Tile Service (WMTS) Implementation Standard, v.1.0.0 (OGC 07-057r7) Document date: 17 October 2017 Edition: 1.0.0 Responsible Party: Defence Geospatial Information Working Group (DGIWG) Audience: This document is approved for public release and is available on the DGIWG website, http://www.dgiwg.org/dgiwg/. Abstract: This document is a profile of OGC 07-057r7, v.1.0.0, dated 2010-04-06. It defines specific Defence requirements, recommendations and guidelines for implementations of a Web Map Tile Service. Copyright: (C) Copyright DGIWG, some rights reserved - (CC) (By:) Attribution You are free: - to copy, distribute, display, and perform/execute the work - to make derivative works - to make commercial use of the work Under the following conditions: - (By:) Attribution. You must give the original author (DGIWG) credit. - For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder DGIWG. Your fair use and other rights are in no way affected by the above. This is a human-readable summary of the Legal Code (the full license is available from Creative Commons <http://creativecommons.org/licenses/by/2.0/ >). STD-DP-18-001 17 October 2017 Table of Contents EXECUTIVE SUMMARY ..................................................................................................... III I. SUBMITTING ORGANIZATIONS ................................................................................... IV II. CONTRIBUTING PARTICIPANTS ................................................................................. IV 1. INTRODUCTION ............................................................................................................ 1 2. SCOPE ........................................................................................................................... 2 3. CONFORMANCE ........................................................................................................... 4 3.1 CONFORMANCE CLASSES ............................................................................................... 4 4. NORMATIVE AND INFORMATIVE REFERENCES ........................................................ 5 4.1 NORMATIVE REFERENCES .............................................................................................. 5 4.2 INFORMATIVE REFERENCES ............................................................................................ 5 5. TERMS, DEFINITIONS AND ABBREVIATIONS ............................................................. 7 5.1 TERMS AND DEFINITIONS ................................................................................................ 7 5.2 ABBREVIATIONS ............................................................................................................. 7 6. INTRODUCTION ............................................................................................................ 8 7. DGIWG BASIC WMTS PROFILE ................................................................................... 9 7.1 NORMATIVE REQUIREMENTS ........................................................................................... 9 7.2 NON-NORMATIVE RECOMMENDATIONS FOR IMPLEMENTATION......................................... 11 7.3 SERVICE STRUCTURE ................................................................................................... 11 7.4 SERVICE TYPE ............................................................................................................. 12 7.5 ARCHITECTURAL STYLES .............................................................................................. 12 7.6 GETCAPABILITIES ......................................................................................................... 13 7.7 GETTILE REQUEST ....................................................................................................... 13 7.8 COORDINATE REFERENCE SYSTEMS ............................................................................. 13 7.9 PROJECTIONS .............................................................................................................. 14 7.10 WELL-KNOWN SCALE SETS .......................................................................................... 14 7.11 TILE FILE FORMATS ...................................................................................................... 15 7.12 NEGOTIATION OF STANDARD VERSION .......................................................................... 15 7.13 KEYWORDS .................................................................................................................. 15 7.14 METADATA ................................................................................................................... 16 7.15 CACHEABLE RESOURCES ............................................................................................. 16 7.16 RECOMMENDATIONS FOR SERVER IMPLEMENTATION ...................................................... 17 8. DGIWG QUERYABLE WMTS PROFILE ...................................................................... 18 8.1 NORMATIVE REQUIREMENTS ......................................................................................... 18 8.2 SERVICE TYPE ............................................................................................................. 18 8.3 BASIC SERVICE ELEMENTS ............................................................................................ 18 8.3.1 OUTPUT FORMATS ..................................................................................................... 18 8.3.2 OUTPUT FORMATS FOR GETFEATUREINFO REQUESTS .................................................. 18 8.4 OPERATIONS ............................................................................................................... 19 8.4.1 GETCAPABILITIES OPERATION RESPONSE ................................................................... 19 8.5 GETFEATUREINFO REQUEST ........................................................................................ 19 9. CLIENT REQUIREMENTS AND RECOMMENDATIONS ............................................. 21 i STD-DP-18-001 17 October 2017 A. ABSTRACT TEST SUITE (NORMATIVE) .................................................................... 23 A.1 INTRODUCTION ............................................................................................................. 23 A.2 SERVER TEST MODULE (BASIC WMTS).......................................................................... 24 A.3 SERVER TEST MODULE (QUERYABLE WMTS) ................................................................ 30 B. WELL-KNOWN SCALE SETS (NORMATIVE) .............................................................. 32 B.1 WORLD MERCATOR EPSG:3395 .................................................................................. 32 B.1.1 XML DESCRIPTION .................................................................................................... 36 B.2 WGS 84 GEODETIC LAT/LONG EPSG::4326 .................................................................. 42 B.3 UPS TILES EPSG:5041 AND EPSG:5042 ..................................................................... 45 B.4 NATO COMPATIBLE WELL KNOWN SCALE SET DEFINITION. .............................................. 50 B.4.1 XML DESCRIPTION .................................................................................................... 51 C. DGIM GROUPS AND SUBGROUPS IN BASELINE 2016-2.0 ...................................... 75 List of Tables Table 1: Use Cases .............................................................................................................. 3 Table 2: DGIWG WMTS Profile conformance class in a military environment ....................... 4 Table 3: Normative References in WMTS interoperability Standard ...................................... 5 Table 4: Informative References in the DGIWG WMTS Interoperability Standard ................. 5 Table 5: DGIWG Basic WMTS Profile Normative Requirements ........................................... 9 Table 6: DGIWG WMTS Profile Non-normative Recommendations .................................... 11 Table 7: Tiling Schemes for Global Coverage ..................................................................... 14 Table 8: Accept Versions Parameter in GetCapabilities Operation Request ........................ 15 Table 9: DGIWG Queryable WMTS Normative Server Requirements ................................. 18 Table 10: GetFeatureInfo operation request URL parameters ............................................. 19 Table 11: Normative WMTS Client Requirements ............................................................... 21 Table 12: Zoom Level Scale Set and Matrix Dimensions-EPSG:3395 ................................. 33 Table 13: Zoom Level Scale Set and Matrix dimensions- WGS 84 Geodetic lat/long .......... 42 Table 14: NATO Compatible well known scale set .............................................................. 50 List of Figures Figure 1: World Mercator tile indexing ................................................................................. 34 Figure 2: Bounding box and partial tile example .................................................................. 35 Figure 3: WGS 84 Tile Indexing – Zoom Level 1 ................................................................
Recommended publications
  • Spectrum Spatial Getting Started Guide
    Spectrum™ Technology Platform Version 12.0 SP1 Spectrum Spatial Getting Started Guide Table of Contents 1 - What Is Location Intelligence? 6 - Services Mapping Service 32 2 - What is Spectrum Spatial? Feature Service 33 Geometry Service 40 Map Tiling Service 43 Spectrum Spatial Concepts 6 Web Feature Service (WFS) 43 Web Map Service (WMS) 44 3 - Modules and Stages Web Map Tile Service (WMTS) 44 Named Resource Service 45 Location Intelligence Module 9 Enterprise Routing Services 45 Enterprise Routing Module 16 Enterprise Geocoding Module 16 GeoConfidence Module 17 4 - Named Resources Named Maps 20 Named Tables 20 Named Layers 20 Named Tiles 21 Named Styles 21 Named Connections 21 Named WMTS Layers 21 Named Label Sources 22 5 - Tools Spatial Manager 24 Management Console 24 Enterprise Designer 24 MapInfo Pro 28 Map Uploader 30 MapInfo Workspace (MWS) Import 30 1 - What Is Location Intelligence? Location intelligence is: • An awareness of relationships between location information and business analysis and operations • The ability to use the understanding of geographic relationships to predict how it impacts a business or organization • The capability to react to how location influences an organization by changing business processes in order to minimize risk and maximize opportunities Location Intelligence enables a business to measure, compare and analyze its data from business operations, in conjunction with external data such as transportation networks, regulatory jurisdictions, market characteristics or its own customers. In this section 2 - What is Spectrum Spatial? Spectrum Spatial is an enterprise location intelligence platform designed to provide organizations with a suite of broadly applicable location capabilities, including spatial analysis, mapping, routing, geocoding, and geoprocessing.
    [Show full text]
  • Metadata and Data Standards. Sharing Data in Hydrology: Best PracCes
    Metadata and Data Standards. Sharing Data in Hydrology: Best Prac8ces Ilya Zaslavsky San Diego Supercomputer Center LMI Workshop, Hanoi, August 18-22 / With several slides from last week’s HDWG workshop, presented By HDWG memBers Irina Dornblut, Paul Sheahan, and others/ Outline • Why use standards? • Open Geospaal ConsorFum, and spaal data standards • Standards for water data, and the OGC/WMO Hydrology Domain Working Group – history, acFviFes, WMO connecFon, workshop last week – Suite of water data standards • WaterML 2.0 in detail (opFonal) • Assessing compliance, and the CINERGI project (opFonal) Why sharing data in LMI? • Several countries rely on the Mekong But data sharing is complicated Challenges: Habitat alteraon PolluFon Extreme weather events Over-exploitaon of resources Diseases and invasive species Poverty and social instability . Water - our most valuable asset But ... • In many places we can’t assess – How much we have – Where it is – Who owns it – What it is fit for – How much we will have – Where it will Be • We certainly can’t yet share informaon in a useful Fmeframe – In parFcular given the complexity of water cycle Why is it important to coordinate? • The orBiter was taken within 57 km of the surface where it likely disintegrated Why? • The flight system so[ware used metric units (Newtons); so[ware on the ground used the Imperial system (pound-force, or lbf) A common situaon in hydrology… Hydro Jack Need flow data! Don Hmm mayBe Don can help… *RING RING* To: Jack Hmm, I’ve got one site. I’ll 01/02/09, 3.2, 3, 1 Hi Don, I need some send it through… 01/02/09, 3.1, 3, 1 *RING RING* upper Derwent flow 10 minutes… readings for my 10 minutes… Ok.
    [Show full text]
  • Coordinate Reference System Google Maps
    Coordinate Reference System Google Maps Green-eyed Prasun taxis penally while Miles always believing his myope dozing subito, he haws so incontinently. Tittuppy Rourke duping, his stirabouts worths ruptures grandly. Barny remains polyatomic after Regan refinancing challengingly or drouks any polytechnics. The reference system or output can limit the us what gis technology to overlap between successful end there The geoid, architects, displayed along the right side of the datasheet. Same as preceding, they must all use the same Coordinate System. Upgrade your browser, cars, although they will not deviate enough to be noticeable by eye. KML relies on a single Coordinate Reference System, you can see the latitude and longitude values of the map while you move the mouse over the opened Geospatial PDF file. In future posts I will discuss some of these packages and their capabilities. Bokeh has started adding support for working with Geographical data. Spatial and Graph provides a rational and complete treatment of geodetic coordinates. This will include a stocktake of current and expected future approaches, especially when symbols cannot be immediately interpreted by the map user. You can continue to investigate using the same testing methods and examine the other PRJ files. DOM container is removed automatically. Geographic Information Systems Demystified. Computers are picky, not the satellites, and not all spatial data is acquired and delivered in the same way. Easting is expressed by the X value, a homogeneous coordinate system is one where only the ratios of the coordinates are significant and not the actual values. Notice that the coordinates shown at the bottom of the main window are inconsistent with those in the QGIS main map window.
    [Show full text]
  • Web Mercator: Non-Conformal, Non-Mercator
    Web Mercator: Non-Conformal, Non-Mercator Noel Zinn Hydrometronics LLC GIS in the Rockies September 2010 www.hydrometronics.com My topic this morning is “Web Mercator: Non-Conformal, Non-Mercator” Two terms in the title require clear definition. They are “web Mercator” and “conformal”. And we’ll get right to it. But first you should know that this entire presentation - with speaker’s notes - is posted for download at the URL given at the bottom of the screen, “www . hydrometronics . com”. We’ll do a little math this morning, but just relax. You needn’t take notes. Anything you miss can be downloaded later. 1 Web Mercator Defined • Web Mercator is the mapping of WGS84 datum (i.e. ellipsoidal) latitude / longitude into Easting / Northing using spherical Mercator equations (where R = a) • EPSG coordinate operation method code 1024 (Popular Visualization Pseudo Mercator, PVPM) • EPSG CRS code 3857 WGS84/PVPM (CRS code 3785 is deprecated) • ESRI IDs 102100 (not certain about 102113) • Safe Software (FME) 3857, 3785, 900913, LL84 Web Mercator is the mapping of ellipsoidal latitude and longitude coordinates onto a plane using spherical Mercator equations. This projection was popularized by Google in Google Maps (not Google Earth). The reference ellipsoid is always WGS84 and the spherical radius (R) is equal to the semi-major axis of the WGS84 ellipsoid (a). That’s “Web Mercator”. EPSG call Web Mercator “Popular Visualization Pseudo Mercator”, operation method code 1024. Coupled with WGS84, that’s coordinate reference system (CRS) code 3857. ESRI and FME have their own codes for Web Mercator given here. Web Mercator has been called a cartographic advancement on the Internet.
    [Show full text]
  • Application of Map Projection Transformation in Measurement of a Global Map
    N02 Application of Map Projection Transformation in Measurement of a Global Map Team Members: Haocheng Ma, Yinxiao Li School: Tsinghua High School Location: P. R. China,Beijing Academic Advisor: Jianjun Zhou Page - 163 N02 Application of Map Projection Transformation in Measurement of a Global Map Abstract: Cartographical projection is mathematical cartography. Map projection is the mathematical model of geoid. Gauss-Kruger projection is unable to realize seamless splicing between adjoining sheet maps. While Mercator projection, especially web Mercator projection, is able to realize seamless splicing but has larger measurement error. How to combine with the advantage of the two projections, apply the method of map projection transformation and realize accurate measurement under the framework of a global map, is the purpose of this article. In order to demonstrate that the problem of measurement could be solved by map projection transformation, we studied the mathematical principle of Gauss - Kruger Projection and the Mercator Projection and designed the algorithm model based on characteristics of both projections. And established simulated data in ArcMap, calculated the error of the three indicators-the area, the length and the angle- under areas in different latitude(0°-4°、30°-34°、 60°-64°)and longitude (120°-126°)range which validated the algorithm model. The conclusion suggests that it is feasible that using web Mercator Projection is capable to achieve a global map expression. Meanwhile, calculations of area, distance and angle using map projection transformation principle are feasible as well in Gauss - Kruger Projection. This algorithm combines the advantage of the two different kinds of projection, is able to satisfy uses' high demand and covers the shortage of measurement function of online map services in China.
    [Show full text]
  • Web Map Tile Services Tiny Tile Server Bachelor Thesis
    Web Map Tile Services Tiny Tile Server Bachelor Thesis Department of Computer Science University of Applied Science Rapperswil Spring Term 2013 Author: Carmen Campos Bordons Advisor: Prof. Stefan Keller, HSR Project Partner: Klokan Technologies, Baar External Co-Examiner: Claude Eisenhut, Burgdorf Internal Co-Examiner: Prof. Dr. Andreas Rinkel, HSR Abstract Tiny Tile Server is a Python server that permits the user to display local MBTiles maps on the internet. It extracts the data from the SQLite database where the map information is stored in tables containing all the tiles, UTFGrid and metadata. The tiles are the map images, smaller than the screen for better performance. The UTFGrid is some extra information related with points in the map that appears in an infobox when the user interact with these points. The metadata is the information about the map: name, description, bounds, legend, center, minzoom, maxzoom. Tiny Tile Server shows the tiles composing the map on a website and the UTFGrid data on top of the tiles. It can also be used to show the getCapabilities information from Web Map Tile Service in XML format extracted by the metadata table. Tiny Tile Server supports two protocols to access the tiles: direct access with XYZ tile request to tiles in a directory or to MBTiles database; or Web Map Tile Service from a MBTiles database. The server is a part in a website whose purpose is to show how it works and provide templates for the user who wants to employ it, so he will not need to have programming knowledge in order to use Tiny Tile Server, just to follow a simple installation tutorial.
    [Show full text]
  • Project No. 249024 NETMAR Open Service Network for Marine
    Project No. 249024 NETMAR Open service network for marine environmental data Instrument: CA IP NOE Please tick 9STREP ICT - Information and Communication Technologies Theme D2.1 Review of projects, initiatives & technologies addressing system architectures for distributed Environmental Information Systems (EIS) Reference: D2.1_Review_of_projects_initiatives_and_technologies_r1_20100618 Due date of deliverable (as in Annex 1): M0 + 3 Actual submission date: 18 June 2010 Start date of project: 1 February 2010 Duration: 3 years Coastal and Marine Resources Centre (CMRC), University College Cork, National University of Ireland Revision 1 Project co-funded by the European Commission within the Seventh Framework Programme (2007-2013) Dissemination Level PU Public X Restricted to other programme participants (including PP the Commission Services) Restricted to a group specified by the consortium RE (including the Commission Services) Confidential, only for members of the consortium CO (including the Commission Services) NETMAR Open service network for marine environmental data Project Reference: 249024 Contract Type: Collaborative Project Start/End Date: 01/03/2010 - 31/01/2013 Duration: 36 months Coordinator: Prof. Stein Sandven Nansen Environmental and Remote Sensing Center Thormøhlensgate 47, Bergen, Norway Tel.: +47-55205800 Fax. +47 55 20 58 01 E-mail: [email protected] Acknowledgements The work described in this report has been partially funded by the European Commission under the Seventh Framework Programme, Theme ICT 2009.6.4 ICT for environmental services and climate change adaptation. Consortium The NETMAR Consortium is comprised of: • Nansen Environmental and Remote Sensing Center (NERSC), Norway (coordinator). Project Coordinator: Prof. Stein Sandven ([email protected]) Deputy Coordinator: Dr. Torill Hamre ([email protected]) Quality Control Manager: Mr.
    [Show full text]
  • Geoservices REST Specification Version 1.0
    ® An Esri White Paper • September 2010 GeoServices REST Specification Version 1.0 Esri, 380 New York St., Redlands, CA 92373-8100 USA TEL 909-793-2853 • FAX 909-793-5953 • E-MAIL [email protected] • WEB www.esri.com Copyright © 2010 Esri. All rights reserved. Printed in the United States of America. Use of the Esri GeoServices REST Specification is subject to the current Open Web Foundation Agreement found at http://openwebfoundation.org/legal/agreement/. Terms and conditions of the OWF Agreement are subject to change without notice. Notwithstanding any rights granted to the user through the Open Web Foundation (OWF) Agreement, the information contained in this document is the exclusive property of Esri. This work is protected under United States copyright law and other international copyright treaties and conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by Esri. All requests should be sent to Attention: Contracts and Legal Services Manager, Esri, 380 New York Street, Redlands, CA 92373-8100 USA. The information contained in this document is subject to change without notice. Esri, the Esri globe logo, ArcGIS, www.esri.com, and @esri.com are trademarks, registered trademarks, or service marks of Esri in the United States, the European Community, or certain other jurisdictions. Other companies and products mentioned herein may be trademarks or registered trademarks of their respective trademark owners. J-9948 GeoServices REST Specification Version 1.0 An Esri White Paper Contents Page 1.0 INTRODUCTION ...............................................................................
    [Show full text]
  • RMDCN Developments
    OGC Standards EGOWS 2010 ECWMF, Reading, 2010/06/1-4 Chris Little [email protected] +44 1392 886278 OGC Co-Chair Meteorology & Oceanography Domain Working Group © Crown copyright 2007 Apologies & Disclaimers I speak too fast No pictures I was involved in international standards • ISO • WMO View of the OGC ‘landscape’ • ‘Valleys & hills’ • NOT ‘Turn 3rd left after pub’ © Crown copyright 2007 Structure of Talk • Some Background • Why OGC? • Standards • Issues for Meteorology © Crown copyright 2007 OGC Standards Some Background © Crown copyright 2007 OGC Met Ocean DWG 2007: ECMWF 11th Workshop on Meteorological Operational Systems - recommended: 2008: ECMWF-OGC Workshop on Use of GIS/OGC Standards in Meteorology - recommended: - Establish OGC Met Domain WG - Establish WMO-OGC Memorandum of Understanding - Develop WMS meteorological profile - Develop core models and registries - Interoperability test beds for met. data & visualization OGC web services © Crown copyright 2007 OGC Who? • Open Geospatial Consortium http://opengeospatial.org • Non-profit making • Standards setting http://opengeospatial.org/standards • Global • >400 members http://opengeospatial.org/members • Industry • Government bodies • Academia • Individuals © Crown copyright 2007 OGC How? TC - Technical Conference, 4 days every 3 months - Darmstadt Sept 2009 EUMETSAT - Mountainview Dec 2009 Google - Frascati Mar 2010 ESA SWG - Standards Working Groups, ~24, - Fast track to ISO, short lived, ‘vertical’ DWG - Domain Working Groups, ~27 - Cross-cutting, longer lived,
    [Show full text]
  • Design of a Multiscale Base Map for a Tiled Web Map
    DESIGN OF A MULTI- SCALE BASE MAP FOR A TILED WEB MAP SERVICE TARAS DUBRAVA September, 2017 SUPERVISORS: Drs. Knippers, Richard A., University of Twente, ITC Prof. Dr.-Ing. Burghardt, Dirk, TU Dresden DESIGN OF A MULTI- SCALE BASE MAP FOR A TILED WEB MAP SERVICE TARAS DUBRAVA Enschede, Netherlands, September, 2017 Thesis submitted to the Faculty of Geo-Information Science and Earth Observation of the University of Twente in partial fulfilment of the requirements for the degree of Master of Science in Geo-information Science and Earth Observation. Specialization: Cartography THESIS ASSESSMENT BOARD: Prof. Dr. Kraak, Menno-Jan, University of Twente, ITC Drs. Knippers, Richard A., University of Twente, ITC Prof. Dr.-Ing. Burghardt, Dirk, TU Dresden i Declaration of Originality I, Taras DUBRAVA, hereby declare that submitted thesis named “Design of a multi-scale base map for a tiled web map service” is a result of my original research. I also certify that I have used no other sources except the declared by citations and materials, including from the Internet, that have been clearly acknowledged as references. This M.Sc. thesis has not been previously published and was not presented to another assessment board. (Place, Date) (Signature) ii Acknowledgement It would not have been possible to write this master‘s thesis and accomplish my research work without the help of numerous people and institutions. Using this opportunity, I would like to express my gratitude to everyone who supported me throughout the master thesis completion. My colossal and immense thanks are firstly going to my thesis supervisor, Drs. Richard Knippers, for his guidance, patience, support, critics, feedback, and trust.
    [Show full text]
  • Web Mercator Projection and Raster Tile Maps
    Annual Conference – 2017 – Ottawa May 31- June 2, 2017 Web Mercator Projection & Raster Tile Maps Two cornerstones of Online Map Service Providers Emmanuel Stefanakis Dept. of Geodesy & Geomatics Engineering University of New Brunswick [email protected] Online Map Service Providers O Available for ~12 years O Well established (difficult to remember how life was without them) 2 Online Map Service Providers 3 Online Map Service Providers Challenges ? • Technological • Cartographical 4 Online Map Service Providers Framework Request (where/what/resolution) CLIENT SERVER HTTP Map Product Map Service End-users Map Repository (Data+Images) 5 Technological Challenges O High and steadily increasing demand O Voluminous data (vectors and images) O Bandwidth limitations O Concurrent access O Security issues O Data protection 6 Cartographical Challenges O Visualize the map on Web browser O flat/rectangular monitor O Multi-resolution representation O various zoom levels O Multi-theme mapping O various themes (layers) O Multi-language mapping O various languages 7 Online Map Service Providers Web Mercator Projection Raster Tile Maps 8 Map Product Flat Monitor Request (where/what/resolution) CLIENT SERVER HTTP Map Product Map Service Map Repository (Data+Images) 9 Map Projection O A function f ... φ Y λ (Χ,Υ) ƒ(φ, λ) X 10 Choose a Map Projection 11 Choose a Cylindrical O Best fit O Rectangular grid 12 Conical Projection ? 13 Conical Projection ? 14 Cylindrical Projection ? 15 Cylindrical Projection O Simulation of a cylindrical projection 16 Cylindrical
    [Show full text]
  • Tile-Based Methods for Online Choropleth Mapping: a Scalability Evaluation by Myung-Hwa Hwang
    Tile-based Methods for Online Choropleth Mapping: A Scalability Evaluation by Myung-Hwa Hwang A Dissertation Presented in Partial Fulfillment of the Requirements for the Degree Doctor of Philosophy Approved September 2013 by the Graduate Supervisory Committee: Luc Anselin, Chair Sergio J. Rey Elizabeth A. Wentz ARIZONA STATE UNIVERSITY December 2013 ABSTRACT Choropleth maps are a common form of online cartographic visualization. They reveal patterns in spatial distributions of a variable by associating colors with data values measured at areal units. Although this capability of pattern revelation has popularized the use of choropleth maps, existing methods for their online delivery are limited in supporting dynamic map generation from large areal data. This limitation has become increasingly problematic in online choropleth mapping as access to small area statistics, such as high- resolution census data and real-time aggregates of geospatial data streams, has never been easier due to advances in geospatial web technologies. The current literature shows that the challenge of large areal data can be mitigated through tiled maps where pre-processed map data are hierarchically partitioned into tiny rectangular images or map chunks for ef- ficient data transmission. Various approaches have emerged lately to enable this tile-based choropleth mapping, yet little empirical evidence exists on their ability to handle spatial data with large numbers of areal units, thus complicating technical decision making in the development of online choropleth mapping applications. To fill this knowledge gap, this dissertation study conducts a scalability evaluation of three tile-based methods discussed in the literature: raster, scalable vector graphics (SVG), and HTML5 Canvas.
    [Show full text]