🛠️
Wazimap technical handbook
  • Introduction
  • System Architecture
    • Database Models
    • IndicatorData
    • Geography Hierarchies
    • Choropleth Maps
    • Determine which instance to use
  • Development
    • Code Deployment
    • Component Architecture
    • Development Process
    • Pull Request Template Explanation
    • Code Review Process
    • Pull Request Template (FE)
    • Webflow Integration
    • Merging webflow exports
    • Rules for Webflow exports
    • Webflow exports & changelog
      • June 2023
      • March 2023
      • February 2023
      • December 2022
      • November 2022
      • October 2022
      • May 2022
      • April 2022
      • March 2022
      • January 2022
      • December 2021
      • November 2021
      • October 2021
    • Translation
    • Map components
  • Testing
    • Testing guidelines
    • Critical Paths
    • GUI Tests
    • Heroku Review Apps
  • Design
    • Iconography
  • Change Proposals
  • NGPx - Template
  • NGP1 - Changing the data model (Implemented)
  • NGP2 - Presenting Geographical Hierarchies to users
  • NGP3 - Change Geography Hierarchies
  • NGP4 - Format configuration
  • NGP5 - Multiple count columns
  • NGP6 - Profile-specific open graph metadata
  • NGP7 - Wazimap profile domain management
  • NGP8 - Replacing Webflow as frontend framework
  • Tutorials
    • Creating a new profile
    • Loading new geographies
    • Loading Data
    • Creating a new admin user
    • Creating a non-admin user for a private profile
    • Changing the Geography level name
    • Deployment to Dokku
  • Configuration
  • Profile Configuration
  • Profile Indicator Configuration
  • Profile Collection Configuration
  • Geographies, hierarchies and versions
  • API
    • General API Information
    • Upload API
    • Task Status
    • Point data API
Powered by GitBook
On this page
  • Context
  • Approach 1
  • Approach 2

Was this helpful?

Export as PDF

NGP2 - Presenting Geographical Hierarchies to users

PreviousNGP1 - Changing the data model (Implemented)NextNGP3 - Change Geography Hierarchies

Last updated 4 years ago

Was this helpful?

NG Proposal 2

Representing geographical hierarchies to the user.

Proposed by: Adi Eyal

Date: 2020-09-02

Status: Work in progress

Context

Read about Geography Hierarchies .

The non-linear structure of Geography Hierarchies poses a challenge to presenting information on a map. When in the context of a Municipality, the user will either want to see Wards or Mainplaces. These cannot be shown simultaneously as they overlap with each other. A graphical toggle would be required to change between these two levels.

Forks can occur at any part of the hierarchy and are dependent on the current geographical hierarchy in use. For the purpose of illustration, here is a more extensive hierarchy:

In this document we discuss the most appropriate user interface to navigate this hierarchy.

At the time of writing, this is how Wazimap depicts the Wards in the Cape Town metro.

Cape Town Metro with Wards displayed

Cape Town Metro with Mainplaces displayed

A typical user requirement would be to switch between Wards and Mainplaces.

Approach 1

The first approach to address this is to use a contextual toggle. The select box on the right is populated with the child levels available at the current geography. When the current geography changes, the options change with it.

This approach requires minor UI changes and can be implemented relatively quickly. Users may however may not necessarily understand the geographical hierarchy and contextual changes may be hard to follow. For example, it may not be obvious that Subplaces are not available below Wards.

Approach 2

here