Skip to content

Version 2: UI Design

Jump to bottom Edit New page
Mhairi O'Hara edited this page Apr 20, 2017 · 1 revision

UI Survey

A survey was conducted to gain insight into the usability of the current HOT Export Tool. The questions presented were aimed at finding out more about the users, their overall experience using the tool, how applicable the functions are and suggestions for future enhancements. The results of the survey have been summarise below and have been used as guidance for the design of the new Export Tool UI.

Results

Frequency of Use

  • Most users have utilised the tool a few times as opposed to on a regular basis.

Note: The aim of the UI redesign will try to make it easier for users to export so that they use it on a regular basis. A comment from survey said that they prefered to use other OSM export tools as they found them easier and more intuitive to use.

Purpose of Use

  • Most users have used the tool for mapping purposes with half of them creating exports in support of an Activation.

Note: This was good to hear, as it is the main purpose of the tool. However we would like to make it usable by anyone looking to export OSM data as well as increase the user experience of those supporting activations.

Experience of Use

Very Difficult | Moderately Difficult | Average | Moderately Easy | Very Easy | Did Not Use

Overall Experience:

  • Most users found this average.

Create Export:

  • Most users found it moderately easy to select an area and preset file when creating an export.
  • Most users found it moderately difficult or did not use the SQL Transform, Translation, Upload Configuration File and Visual Tag Chooser feature at all.

Re-Run Export:

  • Most users found it moderately easy to find and re-run an existing export.

Feature Applicability:

  • Most users found no need to use the Tag Transform feature.
  • Most users found no need to use the Language Translation feature.
  • Most users found no need to use the Upload Configuration File feature.
  • The re-run feature has been used by most users at least a couple of times.

Note: It is apparent and verifies assumptions we had regarding the usability of the tool. Most users found it easy enough to select an area and preset file when creating an export, but do not really use the SQL Transform, Translation, Upload Configuration or Visual Tag Chooser. In part this is due to not requiring them, but in some cases it is because the user did not know how to use them as they are confusing with a lack of help documentation

Feature Enhancement

Tag Selection:

  • Most users agreed with the use of a tree structure to select specific feature tags for export most effective.
  • Most users felt that the Visual Tag Chooser should be retired if all of its functions are embedded into the tree structure method for select feature tags.
  • Most users agreed that having the following options would be effective:
  1. Save the selection as a preset file and add it to the global store (can be accessed by everyone).
  2. Save the selection as a preset file and add it to their personal store (only accessed by themselves).
  3. If the user selects no to both options, than the tag selections will not be saved and are only used during that export session.
  4. A naming convention that will allow filtering of the presets:

Area [ENTER TEXT] | Date [GENERATED AUTOMATICALLY] | Features [GENERATED AUTOMATICALLY] | Event [ENTER TEXT] | Description [ENTER TEXT] *Optional

Note: As the Visual Tag Chooser was also listed as a function that was not really utilised, with one comment stating that they had been using the export tool for quite some time before they even realised it existed. One of the aims in the UI redesign is to provide the functionality of the Visual Tag Chooser built in as a step when creating a new export. Feature tags can be selected from the tree structure, but there will also be the option to load a preset or use an existing saved one.

Function Requests

  • Select the export area based on free-hand polygons or an uploaded geospatial file.
  • Switch between presets saved and stored personally and those publicly.
  • Provide OSM styling files for export formats (Basic, MapQuest and Humanitarian).
  • Better help documentation.

Overview

The redesign of the HOT Export Tool UI is aimed at making it much easier for users to navigate the available functions, through a fluid and instinctive process, with the guidance of better help documentation.

The style, colour scheme and layout takes its inspiration from that of the HOT Tasking Manager and HOT website to maintain continuity between the three platforms as well as provide familiarity for users making it easier for them to use.

A previous redesign of the UI was done at State of the Map last year, which can be found on the Export Tool Version 1 GitHub repository as issue #68. This was also taken into account and factored into the design.

UI Mockup

The UI mock-upis split into three main sections:

  1. Creating a New Export
  2. Stored Existing Exports
  3. Stored Configuration Files

Note: This is still a rough design with some of the details not yet included, such as complete help documentation and pop-up information boxes.

Creating a New Export

  • To create a new export the user must login/register. Once logged in the user will be directed to the homepage to create an export.

  • The new layout works as a sort of wizard, taking the user through a number of tabs they must complete in order to be able to create an export:

  1. Describe Export: Enter the name, description and event of the export you wish to create, and select the area on the map (right section) and click 'Next'.

  2. Export Formats: Select one or more File Format for your export and click 'Next'.

  3. Export Features: Select OSM/HDM tags from a tree structure (which will have visual icons) to export specific features and click 'Next'.

  4. Configuration File: Upload a configuration file to use for the export by entering name, choosing a file and selecting the type (Presets, SQL Transforms or Translations). Click ‘Next’.

  5. Export Summary: This section is an overview of your export features and saving options, which once confirmed the user can click on 'Create Export' which runs the job.

  • The user will then be redirected to a status page that lists the details of the export and the history of its runs.

Stored Existing Exports

  • A user does not need to have an account or be logged in to access existing HOT exports, which can be viewed and searched from the ‘Exports’ page.

  • There is several options to filter the exports:

  1. Search Box: Enter text to filter the Name, Event or Description.

  2. Start Date/End Date: Select dates to filter based on when it was created.

  3. Interactive Map: The map on the right side highlights the filtered exports with bounding boxes, which works both ways, allowing the user to select a bounding box area to filter the exports.

  • The 'My Exports' tab at the bottom of the page lets the user view their own exports if they are logged in.

  • The ‘Next Page’ button allows the user to move on to the next results of exports.

Stored Configuration Files

  • A user does not need to have an account or be logged in to access configuration files, which can be viewed and searched from the ‘Store’ page.

  • There is several options to filter the available configuration files:

  1. Search Box: Enter text to filter the Name or Description.

  2. Start Date/End Date: Select dates to filter based on when it was created.

  3. File Type: This drop down option lets the user select either a Preset, SQL Transform or Language Translation file.

  • The 'My Configuration Files' tab at the bottom of the page lets the user view their own files if they are logged in.

  • The ‘Next Page’ button allows the user to move on to the next results of configuration files.

Add a custom footer
Add a custom sidebar
Clone this wiki locally