Evaluating a Workﬂow Tool for Simplifying Scenario Planning with the Online WhatIf? Planning Support System

: In an era of smart cities and digitalisation, there has been a noticeable increase in the development and application of planning support systems (PSS). However, a signiﬁcant challenge in the broader adoption of these PSS can be attributed to the user experience, which includes the e ﬀ orts required in pre-processing data. It has been observed that typically 80% of the PSS usage time goes into pre-processing, cleaning, and loading data—a signiﬁcant barrier for new users. This research focuses on improving user experience by developing and evaluating a new workﬂow tool called EasyUAZ. This workﬂow tool directly supports the iterative data preparation needs of scenario planning with the Online WhatIf?—a widely used PSS to develop land-use suitability, demand and land-allocation scenarios. A comparative evaluation has been conducted to quantify the time taken for data preparation with ArcGIS, QGIS, and the EasyUAZ. The study found that EasyUAZ o ﬀ ers a time saving of 30%–35% when compared with other options. with GIS functions, including data management and spatial analysis, and (iii) proficiency in using ArcMap and QGIS.


Introduction
The interdependence of transportation, environment, land use, and other socioeconomic factors has made urban planning a complex, dynamic, and highly subjective process. In today's body of knowledge, many GIS-based planning support systems (PSS) exist, which can not only be used to formulate scenario-based alternatives but can be used to evaluate and validate urban plans. Russo has documented more than 100 planning support systems, some of which are open-sourced and are available as freeware [1,2]. However, these tools' adoption and application have been slow [3][4][5][6]. The investigation of the reasons behind low utilisation identifies difficulties in data preparation as a major cause [7]. When the flow from data to data-driven urban planning is explored, two significant stages of bottlenecks can be identified; (i) the challenges which hinder the effective utilisation of data in PSS tools and create the barrier of perceived complexity in new users while initiating the use of PSS and (ii) the challenges which hinder the adoption of PSS tools (see Figure 1). A group of scholars has extensively highlighted the bottlenecks affecting the widespread adaptation and usage of planning support systems and digital planning tools in the real-world planning [3,6,7]. Their work is primarily focused on stage 2 bottlenecks, where they try to explore the mismatch between what planning support tools are offering versus what is need by the planners. After the increased availability of big and complex datasets, there is a need to focus on the stage 1 bottleneck as well, so that the available information can be truly harnessed and put into meaningful action by the planning support tools. This research is focused on the stage 1 bottleneck. Hence, the overall aim of this research is to investigate if workflow tools can assist in reducing the barriers of adoption for new PSS users by simplifying data pre-processing needs.
focused on stage 2 bottlenecks, where they try to explore the mismatch between what planning support tools are offering versus what is need by the planners. After the increased availability of big and complex datasets, there is a need to focus on the stage 1 bottleneck as well, so that the available information can be truly harnessed and put into meaningful action by the planning support tools. This research is focused on the stage 1 bottleneck. Hence, the overall aim of this research is to investigate if workflow tools can assist in reducing the barriers of adoption for new PSS users by simplifying data pre-processing needs. Despite their usefulness, many of the well-documented PSS such as UrbanSim [8] Metronamica [9], SLEUTH [10], and CommunityViz [11] have been critiqued for being relatively complex. These PSS tools require high levels of training and experience to run, take a significant amount of data, and need extensive data cleaning and pre-processing [12][13][14]. It is estimated that 80% of the PSS utilisation time goes into data pre-processing and refining the data information structure [15,16]. A decade ago, while documenting their PSS, Rainis et al. also highlighted its limitation for data pre-processing and high dependency on other GIS tools [17]. The data preparation becomes more intense in the scenario planning process, which demands iterations and frequent data changes during execution [18][19][20]. Holway et al. (2012) highlighted that data acquisition, usage, and interoperability are major stumbling blocks in opening access to the scenario planning tools [5].
Online WhatIf? (OWI) is one of the most prominent open-sourced PSS tools, developed and managed by Australian Urban Research Infrastructure Network (AURIN), used in over 22 countries by more than 250 international users and academically published for suitability analysis, demand analysis and allocation analysis in spatial planning scenarios [2,7,[21][22][23][24][25][26]. Currently, the process of data preparation for Online WhatIf? requires the use of geospatial analysis using desktop GIS tools. While the researchers have extensively documented the benefits of Online WhatIf? in exploring scenarios for spatial plan making [4,21,22,[25][26][27][28][29][30][31][32], some have indicated the burden of extensive data preparation. As the use cases have increased, the demand for a data processing workflow tool has arrived [27,28]. Rainis et al. had hoped that the limitations for data pre-processing and dependency in external GIS tools would be overcome with future development in the GIS industry [17]. However, despite fast-paced growth in the PSS domain, the paucity of pre-processing tools still prevails. The next section expresses the current state of data pre-processing and workflow tools in detail. It can be witnessed that there exists a dearth of workflow tools for PSS, which is primarily due to the diversity and choice-driven inherited demand of PSSs, not always offered by generic tools.
This research reviews the state of the art of data pre-processing tools and presents a classification template. It addresses the critical question of how the time efficiency can be ensured in data preparation time for a specific PSS by employing a customised workflow tool. It highlights the importance of data preparation and workflow tools as complementary products to well established planning support systems. Considering the concepts of task-technology fit [3,[33][34][35], usefulness and added value of PSS [13], this study presents the designing, building, and testing of a data preparation Despite their usefulness, many of the well-documented PSS such as UrbanSim [8] Metronamica [9], SLEUTH [10], and CommunityViz [11] have been critiqued for being relatively complex. These PSS tools require high levels of training and experience to run, take a significant amount of data, and need extensive data cleaning and pre-processing [12][13][14]. It is estimated that 80% of the PSS utilisation time goes into data pre-processing and refining the data information structure [15,16]. A decade ago, while documenting their PSS, Rainis et al. also highlighted its limitation for data pre-processing and high dependency on other GIS tools [17]. The data preparation becomes more intense in the scenario planning process, which demands iterations and frequent data changes during execution [18][19][20]. Holway et al. (2012) highlighted that data acquisition, usage, and interoperability are major stumbling blocks in opening access to the scenario planning tools [5].
Online WhatIf? (OWI) is one of the most prominent open-sourced PSS tools, developed and managed by Australian Urban Research Infrastructure Network (AURIN), used in over 22 countries by more than 250 international users and academically published for suitability analysis, demand analysis and allocation analysis in spatial planning scenarios [2,7,[21][22][23][24][25][26]. Currently, the process of data preparation for Online WhatIf? requires the use of geospatial analysis using desktop GIS tools. While the researchers have extensively documented the benefits of Online WhatIf? in exploring scenarios for spatial plan making [4,21,22,[25][26][27][28][29][30][31][32], some have indicated the burden of extensive data preparation. As the use cases have increased, the demand for a data processing workflow tool has arrived [27,28]. Rainis et al. had hoped that the limitations for data pre-processing and dependency in external GIS tools would be overcome with future development in the GIS industry [17]. However, despite fast-paced growth in the PSS domain, the paucity of pre-processing tools still prevails. The next section expresses the current state of data pre-processing and workflow tools in detail. It can be witnessed that there exists a dearth of workflow tools for PSS, which is primarily due to the diversity and choice-driven inherited demand of PSSs, not always offered by generic tools.
This research reviews the state of the art of data pre-processing tools and presents a classification template. It addresses the critical question of how the time efficiency can be ensured in data preparation time for a specific PSS by employing a customised workflow tool. It highlights the importance of data preparation and workflow tools as complementary products to well established planning support systems. Considering the concepts of task-technology fit [3,[33][34][35], usefulness and added value of PSS [13], this study presents the designing, building, and testing of a data preparation workflow tool for the Online WhatIf? PSS. The experimental design of this research takes the form of a case study approach where the workflow tool is applied and evaluated in the context of formulating a spatial plan for the city of Faisalabad in Pakistan.

State of the Data Pre-Processing and Workflow Tools
With the recent rise of big and complex datasets [36,37], the need for workflow and pre-processing tools has become increasingly important. Furthermore, with the rapid growth of new data sources available to support urban modelling and data-driven decision-making [38][39][40], data cleaning and processing have appeared as more critical tasks requiring improved efficiency. While the concept of workflow tools has been primarily in business automation for the last many decades [41], it has been extensively adopted in the domain of GIS. However, there has been limited development of such workflow tools in the field of PSS.
Generic data pre-processing and workflow tools can assist in various processing needs ranging from simpler ETL operations (extract, transform, and load) to more complex workflow tasks spanning over heterogeneous applications. From the perspective of planning support science, we may categorise workflow tools in four categories (see Figure 2): ISPRS Int. J. Geo-Inf. 2020, 9, x FOR PEER REVIEW 3 of 22 workflow tool for the Online WhatIf? PSS. The experimental design of this research takes the form of a case study approach where the workflow tool is applied and evaluated in the context of formulating a spatial plan for the city of Faisalabad in Pakistan.

State of the Data Pre-Processing and Workflow Tools
With the recent rise of big and complex datasets [36,37], the need for workflow and preprocessing tools has become increasingly important. Furthermore, with the rapid growth of new data sources available to support urban modelling and data-driven decision-making [38][39][40], data cleaning and processing have appeared as more critical tasks requiring improved efficiency. While the concept of workflow tools has been primarily in business automation for the last many decades [41], it has been extensively adopted in the domain of GIS. However, there has been limited development of such workflow tools in the field of PSS.
Generic data pre-processing and workflow tools can assist in various processing needs ranging from simpler ETL operations (extract, transform, and load) to more complex workflow tasks spanning over heterogeneous applications. From the perspective of planning support science, we may categorise workflow tools in four categories (see Figure 2):

Tools for Pre-Processing Heterogeneous Data
This group may refer to the data processing tools (spatial and non-spatial) related to building data pipeline and wrangling data. Such tools are generally focused on accessing data from multiple heterogeneous data stores and producing outputs with the uniform format, scale, and geographic projection, etc. Examples of these tools include Google OpenRefine [42][43][44], Scatter, Clustering, 0-Networking [45], GeoKattle [46], and Talend spatial extension. Furthermore, the more common proprietary tools include Microsoft PowerBI [47] and Sisense. The critical processing requirement behind these tools is the ability to read diverse data sources and formats.

Tools for Task Automation within the Same Application
This group includes the tools that are generally offered as developer libraries, extensions, or plugins of software packages. These tools allow access to the functions and tasks available within the specific application and allow the knitting of those functions via programming and/or graphic workflow interfaces. Notable examples include ArcGIS workflow Manager [48] and ArcGIS model builder [49] in the proprietary domain while QGIS Processing Framework [50] and Google Earth Engine [51] in the open-source domain.

Tools for Pre-Processing Heterogeneous Data
This group may refer to the data processing tools (spatial and non-spatial) related to building data pipeline and wrangling data. Such tools are generally focused on accessing data from multiple heterogeneous data stores and producing outputs with the uniform format, scale, and geographic projection, etc. Examples of these tools include Google OpenRefine [42][43][44], Scatter, Clustering, 0-Networking [45], GeoKattle [46], and Talend spatial extension. Furthermore, the more common proprietary tools include Microsoft PowerBI [47] and Sisense. The critical processing requirement behind these tools is the ability to read diverse data sources and formats.

Tools for Task Automation within the Same Application
This group includes the tools that are generally offered as developer libraries, extensions, or plugins of software packages. These tools allow access to the functions and tasks available within the specific application and allow the knitting of those functions via programming and/or graphic workflow interfaces. Notable examples include ArcGIS workflow Manager [48] and ArcGIS model builder [49] in the proprietary domain while QGIS Processing Framework [50] and Google Earth Engine [51] in the open-source domain.

Tools for Task Automation among Heterogeneous Applications
In contrast to the second group, these tools offer workflow management among multiple heterogeneous applications. The most commonly used example is Feature Manipulation Engine (FME) [52], which is capable of integrating multiple applications to resolve a complex workflow. The strength of FME lies in its ability to talk to multiple software and communicate data between over 450 applications through a visual interface [53]. In contrast to the licensed tools, Hale Studio is an open-source option to migrate, integrate, or harmonise complex spatial data [54].

Pre-Processing Workflow Tools to Generate Input Datasets for PSS
This group includes the tools specifically designed to complement planning support systems by providing an assistive mechanism to generate PSS specific input datasets. The previous three tools' groups are not explicitly designed to support PSS. Instead, those are primarily meant for generic task solving. In contrast, the tools under the fourth group are very strongly linked to specific PSS nomenclature. The critical processing need for these tools is the ability to take varied user choices and iterative processes as inputs. For instance, UrbanCanvas Modeler for UrbanSim is a web-based platform to manage model data inputs and results. This proprietary tool offers workflow management for developing input data relevant to land use and future development [55,56]. On the other hand, ORCA is an open-sourced tool for data processing and orchestration to support UrbanSim, which allows the users to define dynamic data sources and explicitly connect them to processing functions. ORCA is a part of Urban Data Science Toolkit (UDST) [57].
There has been a lack of data preparation and workflow tools, even for prominent PSS, especially those in the open-sourced domain. For instance, SLEUTH accepts the input data in GIF image format, which requires transforming input layers into rasterised grids of the same extent, resolution, and geographic projection. However, data preparation has to been completed using external desktop tools [10,58,59]. In the case of UrbanSim, data can be loaded into the simulation framework using ORCA or Pandas Dataframes, which offers data connectivity modules to fetch data from multiple sources, including HDF5 files, CSV and Excel files, DBF databases, and others. However, these data preparation mechanisms do not have graphical user interfaces (GUIs) and require user familiarity with the Python programming language. To overcome this limitation, UrbanCanvas has been provided with a GUI in a browser interface which, unlike other UrbanSim components, is a subscription-based service [55,57].
Similarly, LandUse Scanner (another well-known PSS, also called Ruimtescanner) [60], which provides a framework for Land Use change modelling, uses GeoDMS as its modelling software to process, calculate with and visualise datasets. The preparatory work for the use of LandUse Scanner requires the setting up of configuration files using a declarative language. The graphical user interface of the GeoDMS allows users to configure data files [61], which can be considered as a built-in preparatory tool. On the other hand, proprietary tools such as Metronamica, Index, and CommunityViz have some form of inbuilt data preparation tools. Metronamica has pre-integrated tools to construct and amend spatial scenarios using its Overlay Tool and Map Comparison Kit [9,[62][63][64]. INDEX Planbuilder [65,66], and CommunityViz [67] are based on ESRI' ArcGIS platform, which makes the tools convenient for users while preparing data and undertake spatial pre-processing.
In the discussion of workflow automation for PSS, tools in the second and third groups are more useful. For instance, FME has been used to integrate multiple software and input-output flow [52]. However, FME is particularly useful if the inputs-outputs are clearly defined, and the process is non-iterative with lesser user inputs in choice selection [52,68,69]. Similarly, ArcGIS Model Builder has been frequently used and cited in combination with Python-based applications to streamline the processes in geospatial analysis.
By virtue of its larger user base and applications, the Online Whatif? planning support system has been studied and reviewed from various dimensions. In the last five years, researchers have evaluated the usefulness of the Online WhatIf? and have presented ways to further improvise its utility. Hussnain et al. have presented the development of a mobile-based data collection module to collect primary data on urban indicators for the Online WhatIf? [26]. Hussnain et al. have documented the process of input data preparation and subsequent processing challenges during a real-life project highlighting the iterative nature of the looping processes of geometric and spatial analysis [28]. While comparing the multi-criteria evaluation (MCE) based PSS, Russo et al. (2018) have referred to the data preparation challenges concerning PSS usability [29]. Pettit et al. have highlighted the use of ArcGIS desktop to prepare input datasets while using the Online WhatIf? in building land use and transport scenarios in Australia. While appreciating the Online WhatIf? utility for planning support, Pettit et al. registered their concern that input datasets preparation had been a time-consuming process that had to be restarted with any change in the study area. Pettit et al. have highlighted the need for automated workflow tools, which might be implemented as a module to the Online WhatIf? or as a stand-alone supporting tool [27]. The critical data pre-processing requirement gap has been filled through this study.

Data and Preparation Requirements for the Online Whatif? PSS
This study focuses on developing and evaluating the EasyUAZ; a new data preparation workflow tool for improving the useability of the Online WhatIf? (OWI) PSS [25,[70][71][72][73]. The Online WhatIf? is a widely used PSS used to support scenario planning for future urban growth of cities and regions. The Online WhatIf? comprises three key components (i) Land Suitability (iii) Land Demand, and (iii) Land Allocation [72]. A comprehensive array of datasets is required to generate future urban growth scenarios for a city. This data traditionally requires significant effort to collect, clean, and process before the three key components of the tool can be run [27].
The spatial data used by Online WhatIf? contains various geophysical and natural conditions (terrain, soil, land uses, population etc.), factorial information (proximity, services availability, growth priorities etc.), existing and proposed infrastructure and land use controls (zoning districts, planned land uses etc.) which are processed to generate a single polygonal input vector file. To summarise, the whole study area is divided into land units possessing homogeneity of all factors under consideration called Uniform Analysis Zones (UAZs). Since the basic spatial unit of analysis in Online WhatIf? is a polygon; each polygon must represent the parcel of land where each point has the same value for all attributes. In the current workflow of the Online WhatIf? the preparation of the UAZ file is an external process that may be performed using any desktop GIS application. Resultantly, the UAZ for the Online WhatIf? contains all the essential information required to execute land suitability, future demand and land use allocation analysis.

Research Design
This research follows a two-stage process to achieve the desired objectives, as shown in Figure 3. Stage 1 is the design stage, which covers the development of EasyUAZ. Stage 2 focuses on both the technical and user evaluation of the tool. In evaluating the EasyUAZ workflow tool, the evaluation method proposed by Russo et al. [4] has been adapted after contextualisation. While comparing the usability of PSS tools to complete a predefined task, Russo et al. [4] employed a group of six participants and monitored them under the lab environment during the task performance process. Furthermore, they have used the user experience (UX) questionnaire to document users' mental models and expectations [29].

Stage 1: Development of the EasyUAZ; a Preparatory Workflow Tool for Online WhatIf?
Development of the EasyUAZ has been initiated with the review of the existing standard practice workflow of the Online WhatIf? user to generate UAZ (see Figure 4). It must be noticed that data preparation workflow is not just technical but involves discussions with key stakeholders to both negotiate data access and to determine acts of geoprocessing along with determining the factors (opportunity and constraints) which underpin the scenario planning process. This process is iterative and often needs revisiting in the scenario planning process if stakeholders wish to make changes to the input assumptions, later on, i.e., the new opportunity and constraint layers often need to be modified in the workflow tool. When users engage generic GIS tools for data preparation, the focus remains more on the technical aspects of geoprocessing rather than the dialogue between stakeholders on planning factors. Task Technology Fit (TTF is defined as the fit between PSS capacities (supply-side) and planning tasks (demand side)) Framework [14,74] has been considered to see what processes can be automated so that the user may systematically interact with the factors (opportunity and constraints) which underpin the scenario planning process by focusing more on the factors and worry less about the background geo-processing. Development of the EasyUAZ has been initiated with the review of the existing standard practice workflow of the Online WhatIf? user to generate UAZ (see Figure 4). It must be noticed that data preparation workflow is not just technical but involves discussions with key stakeholders to both negotiate data access and to determine acts of geoprocessing along with determining the factors (opportunity and constraints) which underpin the scenario planning process. This process is iterative and often needs revisiting in the scenario planning process if stakeholders wish to make changes to the input assumptions, later on, i.e., the new opportunity and constraint layers often need to be modified in the workflow tool. When users engage generic GIS tools for data preparation, the focus remains more on the technical aspects of geoprocessing rather than the dialogue between stakeholders on planning factors. Task Technology Fit (TTF is defined as the fit between PSS capacities (supply-side) and planning tasks (demand side)) Framework [14,74] has been considered to see what processes can be automated so that the user may systematically interact with the factors (opportunity and constraints) which underpin the scenario planning process by focusing more on the factors and worry less about the background geo-processing.

Stage 2: Comparative Evaluation
This research uses a combination of qualitative and quantitative approaches to evaluate the user experience; (a) technical (comparative analysis between tools for time evaluation), and (b) focus group discussion with participants on the strengths and weaknesses of the workflow tool in terms of ease of use and overall experience.

User Experience (Technical)
Pettit (2017) and  have used usability frameworks to explore user experience [75,76]. For time efficiency evaluation, the EasyUAZ tool has been compared with two other commonly used generic spatial data preparation tools; (a) ArcMap with spatial analyst [77] and (b) QuantumGIS (also known as QGIS) [78]. The newly developed tool (EasyUAZ) is the first of its kind to facilitate data processing for Online WhatIf? PSS. Traditionally, the data preparation for Online WhatIf? is done either by ArcGIS or QGIS. This research compares and explains how EasyUAZ can perform compared with the two for the specific case of Online WhatIf? users. It is essential to highlight that each of the other workflow tools in group 4 (as per Figure 2 such as UrbanCanvas, ORCA, GeoDMS) is specifically built to complement its respective PSS tools only including UrbanSim, and LanduseScanner, respectively. None of them can be used for the data preparation of other PSSs. In the given mutual exclusiveness, inter-PSS comparison of workflow tools has not been possible at the current situation. Consequently, this research focuses on comparing and understanding workflow improvement within EasyUAZ, ArcGIS and QGIS.
A team of 12 graduate planners (men (n = 9) and women (n = 3), age between 25 to 40 years) from the planning community of Punjab, Pakistan, have been engaged for the study. Participants had to meet the following criteria: (i) practising professional urban planner, (ii) experienced with GIS functions, including data management and spatial analysis, and (iii) proficiency in using ArcMap and QGIS.
This study adopted the within-subject design as recommended by Russo [4] and Graziano [79], where each participant used all three options to generate the desired UAZ but in a different order by

Stage 2: Comparative Evaluation
This research uses a combination of qualitative and quantitative approaches to evaluate the user experience; (a) technical (comparative analysis between tools for time evaluation), and (b) focus group discussion with participants on the strengths and weaknesses of the workflow tool in terms of ease of use and overall experience.

User Experience (Technical)
Pettit (2017) and  have used usability frameworks to explore user experience [75,76]. For time efficiency evaluation, the EasyUAZ tool has been compared with two other commonly used generic spatial data preparation tools; (a) ArcMap with spatial analyst [77] and (b) QuantumGIS (also known as QGIS) [78]. The newly developed tool (EasyUAZ) is the first of its kind to facilitate data processing for Online WhatIf? PSS. Traditionally, the data preparation for Online WhatIf? is done either by ArcGIS or QGIS. This research compares and explains how EasyUAZ can perform compared with the two for the specific case of Online WhatIf? users. It is essential to highlight that each of the other workflow tools in group 4 (as per Figure 2 such as UrbanCanvas, ORCA, GeoDMS) is specifically built to complement its respective PSS tools only including UrbanSim, and LanduseScanner, respectively. None of them can be used for the data preparation of other PSSs. In the given mutual exclusiveness, inter-PSS comparison of workflow tools has not been possible at the current situation. Consequently, this research focuses on comparing and understanding workflow improvement within EasyUAZ, ArcGIS and QGIS.
A team of 12 graduate planners (men (n = 9) and women (n = 3), age between 25 to 40 years) from the planning community of Punjab, Pakistan, have been engaged for the study. Participants had to meet the following criteria: (i) practising professional urban planner, (ii) experienced with GIS functions, including data management and spatial analysis, and (iii) proficiency in using ArcMap and QGIS.
This study adopted the within-subject design as recommended by Russo [4] and Graziano [79], where each participant used all three options to generate the desired UAZ but in a different order by considering all permutations [29,79]. Since we had three conditions to compare, the participants have been divided into six groups, who undertook the process in the order of ABC, ACB, BAC, BCA, CAB, and CBA [80] (see Table 1). Each participant was asked to process only one workflow per day, considering the intensity of the task. Three identical workstations (screen size: 27", resolution: 1366 × 768, processor: Core i7, 7th Gen, 16GB SSD RAM with keyboard and mouse) have been used which were rotated such that three different participants in one day use each workstation, to keep uniformity in the processing power of the apparatus. The usage of workstations and participants were carefully scheduled such that each workstation could facilitate two distinct participants per day. As a result, the study was completed in three days. The processing time to prepare the UAZ was noted in minutes using the built-in stopwatch function of the workstation, which stayed hidden from the participants. The recording of the time was started from the moment of opening/running the understudy tool to its closure on a given workstation. For instance, if a user group (UG-1a) has been tasked to perform the UAZ preparation task on the workstation (ws1) using ArcMap; their time has been started from the moment they run ArcMap.exe on the ws1 and ends when they closes the project file after completing all the required task. The difference between the start and end time has been recorded in minutes. The colours in Table 1 give the visual representation to the counter-balanced order.
The participants were oriented about the Faislabad peri-urban plan and its data sets through a two-hour session. Table 1 provides the details of the datasets, its spatial type, and attribute classes. The task was to prepare a single polygonal-a UAZ file-which has the following characteristics: • is free from geometric errors and comply with the topology rules of no overlaps, must not have gaps, and must not have slivers • the factor layers need to be prepared and assigned to the main polygon file as columns containing required classes To prepare the participants, they were informed that they would have to use the following spatial operations: service area analysis, multi-ring buffer analysis, natural neighbour interpolation, and spatial joining. Participants were informed that they could also perform other spatial analysis and data processing operations as they deemed appropriate using the tools available during the exercise.

User Experience (Focused Group Discussion)
In addition to the time recording, users were asked to share their feedback in a moderated focused group discussion which occurred on day 4. The participants of the focused group discussion included the same users who tested the tools in the first place in the previous experiment. The active discussion spanned over 2 h; however, once the note-taking was complete, some additional time was spent on ensuring that the feedback has been recorded in the exact sense as perceived by the experiment participants. The discussion revolved around documenting: (a) the most relevant experiences while engaging with different tools (ArcGIS, QGIS and EasyUAZ), (b) the extent to which features and the functions in the tools under comparison have been satisfactory for UAZ preparation and (c) the key most positive and most negative aspects.

Use Case
This study uses the urban spatial plan of Faisalabad city, which is called Faisalabad Peri-Urban Structure Plan 2035 (FPUSP) to test the EasyUAZ tool. Faisalabad is the third-largest city of Pakistan, with more than 3.2 million population [81] and the built-up area of more than 260 square kilometres. The FPUSP was developed in 2015 by the City District Government under the Punjab Cities Governance Improvement Project (PCGIP) with the support of consultants, including the Urban Unit under the financial assistance of the World Bank. The Faisalabad Peri-Urban Structure Plan (FPUSP)2035 is the first and the only approved spatial plan in the country which has witnessed the documented application of a GIS-based land suitability analysis [82,83]. The final report of the plan contains most of the essential details and underlying assumptions behind the plan-making. Hence, it provides a relevant case study to evaluate and compare the results. For this research, a subset of the spatial data and plan preparation assumptions from FPUSP has been used. Table 1 presents the list of data layers taken from FPUSP along with the layer type and the key attributes that need to be processed by the EasyUAZ tool in the data preparation for further processing in the Online WhatIf? PSS. In contrast, Table 2 presents the list of factor layers and associated classes that have been used in FPUSP preparation and contains all the data going into the EasyUAZ tool. These factor layers were required to be developed from the data layers (given in Table 2) using various geoprocessing tools available in the tool kits of each software. The factor data obtained from each generated layer are then attached to each parcel polygon, and finally, a polygonal file (UAZ) is generated as an output which could qualify as an input to the Online WhatIf? PSS. In Table 3, 'Classes' refers to the number of spatial buffer rings along with a distance of each ring. For instance, '5 classes of 500 m' denotes that five buffer rings have to be prepared with 500 m width for each buffer ring. Furthermore, the 'Factor Type' refers to the classification of planning factors based on their nature, adapted from Hussnain et al. [28]. The 'proximity factors' refer to the factor layers which are based on the spatial distance or proximity to particular land use. Meanwhile, 'policy factors' refers to the factors based on the data sets derived from the policy documents.

Results and Discussion
In the current working modality, the UAZ file for the Online WhatIf? is typically created using offline desktop-based applications. The Online WhatIf? user documentation [72] has enlisted the six steps, which can be repeated by n times (where n denotes the number of layers/factors) to produce the final form of UAZ. These steps include (a) Combining GIS layers; (b) Removing multi-part Features; (c) Removing slivers; (d) Creating/correcting topology; (e) Deleting unnecessary data fields, and (f) Creating the UAZ shapefile. Generally, when the Online WhatIf? is implemented in real-world projects, the number of factor layers exceeds ten and these can be updated through several iterations as the stakeholder refine the key input for the scenario planning process. Hence the data pre-processing in preparing the UAZ process can be time-consuming, and arduous reported by Russo et. and decrease the useability of the OWI PSS [28]. The problem is exacerbated in developing countries like Pakistan, where national spatial data infrastructures (NSDIs) are yet not in place. In the absence of standardised datasets, processing of datasets to generate desired results becomes challenging.

Development of EasyUAZ
Considering the dynamics of user experience with user interface (UX-UI) and TTF, the EasyUAZ tool has been designed to offer a structured workflow process where users are guided through the procedural steps in a sequence employing a user-friendly visual interface. The Online WhatIf? expects the input UAZ file to qualify specific geometric characteristics and attributes completion checks. The EasyUAZ has been designed to ensure that those conditions are met. To support the real-life projects which require the processing of a long list of factors and data files, the EasyUAZ has been designed to guide the user for considering the factors under various possible categories, such as proximity factors, policy factors, growth control or composite factors.
The EasyUAZ workflow tool has been implemented as a QGIS plugin, considering the stability, growth in user base and worldwide adaptability of OSGeo ecosystem [84,85]. The technology stack has been presented in Figure 5. This section provides the visual and functional details on the EasyUAZ, which can be accessed using the QGIS Desktop, as it has been built as a stand-alone plugin (See Figure 6). The developed plugin demonstrates the following functional strengths: This section provides the visual and functional details on the EasyUAZ, which can be accessed using the QGIS Desktop, as it has been built as a stand-alone plugin (See Figure 6). This section provides the visual and functional details on the EasyUAZ, which can be accessed using the QGIS Desktop, as it has been built as a stand-alone plugin (See Figure 6). The developed plugin demonstrates the following functional strengths: The developed plugin demonstrates the following functional strengths:

Layer Checking Module
The layer checking module allows the user to check multiple conditions on the base parcels/polygons file. These conditions are required to be satisfied for feeding data into the Online WhatIf?. The conditions are pre-populated, and the user has the option to check or uncheck specific conditions based on the requirement. Figure 7 shows the interface of the layer checking module. A tick mark sign appears for every satisfied condition, and in case of unsatisfied conditions and cross appears with further instructions for the user-populated in the status column. The layer checking module allows the user to check multiple conditions on the base parcels/polygons file. These conditions are required to be satisfied for feeding data into the Online WhatIf?. The conditions are pre-populated, and the user has the option to check or uncheck specific conditions based on the requirement. Figure 7 shows the interface of the layer checking module. A tick mark sign appears for every satisfied condition, and in case of unsatisfied conditions and cross appears with further instructions for the user-populated in the status column.

Situational Analysis Module
Situation Analysis allows the user to perform statistical analysis on the data. The user has to select the relevant data layer based on which the attributes are available in a drop-down list so that the user can select the classification attribute. It allows the user to view area classification based on values or percentages of the values. Users can also export the pie chart in PNG format for use in other reports (see Figure 8).

Situational Analysis Module
Situation Analysis allows the user to perform statistical analysis on the data. The user has to select the relevant data layer based on which the attributes are available in a drop-down list so that the user can select the classification attribute. It allows the user to view area classification based on values or percentages of the values. Users can also export the pie chart in PNG format for use in other reports (see Figure 8).

Layer Checking Module
The layer checking module allows the user to check multiple conditions on the base parcels/polygons file. These conditions are required to be satisfied for feeding data into the Online WhatIf?. The conditions are pre-populated, and the user has the option to check or uncheck specific conditions based on the requirement. Figure 7 shows the interface of the layer checking module. A tick mark sign appears for every satisfied condition, and in case of unsatisfied conditions and cross appears with further instructions for the user-populated in the status column.

Situational Analysis Module
Situation Analysis allows the user to perform statistical analysis on the data. The user has to select the relevant data layer based on which the attributes are available in a drop-down list so that the user can select the classification attribute. It allows the user to view area classification based on values or percentages of the values. Users can also export the pie chart in PNG format for use in other reports (see Figure 8).

UAZ Preparation
UAZ Preparation module allows the user to process the parcels layer and include values for multiple factors that are to be used in the Online WhatIf? analysis. There are three categories of factors: Proximity Factors: This tab provides the user with 15 pre-populated proximity factors with the option to check, uncheck, and add new factors as per requirement. The user has to select the relevant data shapefile for every factor and enter the buffer interval value. No of Intervals refers to the buffer rings that are required for making proximity classes. The Result Field column is to be populated with the name of the field required in the output file. Once all the required values are added, and the Process button is clicked, the EasyUAZ tool now performs the spatial analysis between the base layer and factor layers to add factor attributes in the base layer and populate them with the respective values (see Figure 9). ISPRS Int. J. Geo-Inf. 2020, 9, x FOR PEER REVIEW 13 of 22

UAZ Preparation
UAZ Preparation module allows the user to process the parcels layer and include values for multiple factors that are to be used in the Online WhatIf? analysis. There are three categories of factors: Proximity Factors: This tab provides the user with 15 pre-populated proximity factors with the option to check, uncheck, and add new factors as per requirement. The user has to select the relevant data shapefile for every factor and enter the buffer interval value. No of Intervals refers to the buffer rings that are required for making proximity classes. The Result Field column is to be populated with the name of the field required in the output file. Once all the required values are added, and the Process button is clicked, the EasyUAZ tool now performs the spatial analysis between the base layer and factor layers to add factor attributes in the base layer and populate them with the respective values (see Figure 9). Policy Factors and Composite Factors: These tabs provide the user with two pre-populated factors, each with the option to check, uncheck, and add new factors as per requirement. Here, the user has to select relevant data shapefile and then the respective attribute for the Source Field column based on which the intersection operation is performed, and values are then populated in the result fields.

Technical Evaluation of the Workflow Tool
The analysis of the experiment observations reveals that users have taken 297 min on average when they prepare a UAZ with ArcGIS, which increases to 320 min when the UAZ preparation is done through QGIS. However, in the case of the EasyUAZ, the average time turned out to be 217 min, which is 30% less than the ArcGIS and 35% lesser than QGIS generic tools (see Figure 10). Policy Factors and Composite Factors: These tabs provide the user with two pre-populated factors, each with the option to check, uncheck, and add new factors as per requirement. Here, the user has to select relevant data shapefile and then the respective attribute for the Source Field column based on which the intersection operation is performed, and values are then populated in the result fields.

Technical Evaluation of the Workflow Tool
The analysis of the experiment observations reveals that users have taken 297 min on average when they prepare a UAZ with ArcGIS, which increases to 320 min when the UAZ preparation is done through QGIS. However, in the case of the EasyUAZ, the average time turned out to be 217 min, which is 30% less than the ArcGIS and 35% lesser than QGIS generic tools (see Figure 10). Table 4 represents the interquartile range of the experimental results, which are graphically represented by a box and whisker plot in Figure 11. The analysis reveals that the minimum recorded time for UAZ preparation with the EasyUAZ has been 187 min, which is considerably less than QGIS Desktop (285 min) and ArcGIS (269 min). This time efficiency is triangulated from the first quartile distribution, which is measured as 196, 299, and 285 min for the EasyUAZ, QGIS, and ArcGIS, respectively. In terms of range, the EasyUAZ reflects the most compact form of all three processes with a value of 52, followed by ArcGIS with a more significant range spread of 81. At the same time, QGIS has the most extensive range of 107, which shows that users have a higher diversity of completion time with QGIS. In the case of EasyUAZ, most of the users were able to complete the task in a closer time range.  Table 4 represents the interquartile range of the experimental results, which are graphically represented by a box and whisker plot in Figure 11. The analysis reveals that the minimum recorded time for UAZ preparation with the EasyUAZ has been 187 min, which is considerably less than QGIS Desktop (285 min) and ArcGIS (269 min). This time efficiency is triangulated from the first quartile distribution, which is measured as 196, 299, and 285 min for the EasyUAZ, QGIS, and ArcGIS, respectively. In terms of range, the EasyUAZ reflects the most compact form of all three processes with a value of 52, followed by ArcGIS with a more significant range spread of 81. At the same time, QGIS has the most extensive range of 107, which shows that users have a higher diversity of completion time with QGIS. In the case of EasyUAZ, most of the users were able to complete the task in a closer time range.    Another useful insight earned with the experiment is to explore how the differences in the time needed to complete the task with EasyUAZ vs. ArcGIS/QGIS is affected by processing time (only), which varies in ArcGIS vs. QGIS, and due to the case of possible more complex workflow in the manual approach. This is interesting to understand that the gross time differences are primarily due Another useful insight earned with the experiment is to explore how the differences in the time needed to complete the task with EasyUAZ vs. ArcGIS/QGIS is affected by processing time (only), which varies in ArcGIS vs. QGIS, and due to the case of possible more complex workflow in the manual approach. This is interesting to understand that the gross time differences are primarily due to the 'user action' rather than the 'processing time'. Some comparative studies have [86][87][88][89] compared the functionalities and geo-processing time requirement of both of the applications while an endless comparison debate can be seen on the Q&A websites such as StackOverflow and StackExchange. It has been observed that for the given geoprocessing tasks, there exists a very marginal difference between the processing time with QGIS vs. ArcGIS, which has been recorded as 175 min vs. 165 min, respectively (see Figure 12). The EasyUAZ primarily improves the 'user action time' by reducing it by 67% when compared with QGIS and 64% in the case of ArcGIS. Furthermore, a reduction of 10% time has also been noticed against QGIS.

User Experience (Focused Group Discussion)
While discussing the ease of using the workflow and the improvements in the overall experience, the participants commented on their preference for using the EasyUAZ. "Although the ArcGIS toolbox is very powerful, we need to search for the relevant commands while in case of EasyUAZ, those processes have been pre-selected, making it very handy," narrated one participant. Similarly, others shared that during the tasks' performance with the generic GIS tools (ArcGIS and QGIS), they had to spend considerable time figuring out the right flow of geo-processes. On the other hand, the EasyUAZ tool presented a customised and structured approach where the desired commands were pre-embedded in the tool, along with their sequencing, to support urban research workflow required to create the UAZ file. Another participant commented, "EasyUAZ will be particularly useful for users having lesser experience in GIS workflows including buffering, shapefile editing, spatial joins etc". One participant commented that "In the case of ArcGIS and QGIS, we remained more focused on finding the GIS commands and geoprocessing tools than thinking about the planning problem at hand. While the EasyUAZ took that burden off, we were more focused onto the placement of planning factors and their categorisation. For example, while using EasyUAZ, I did not have to worry about what GIS processes are going at the backend; rather, I enjoyed categorising opportunity and constraint layers. I realised that I had some differences in how those factors were arranged, and I was able to rearrange them as per my choice". Most of the participants appreciated that EasyUAZ has been based on open source tools and hoped that this would allow a broader audience to contribute in the future and a great uptake due to both EasyUAZ and OWI being freely available.

User Experience (Focused Group Discussion)
While discussing the ease of using the workflow and the improvements in the overall experience, the participants commented on their preference for using the EasyUAZ. "Although the ArcGIS toolbox is very powerful, we need to search for the relevant commands while in case of EasyUAZ, those processes have been pre-selected, making it very handy," narrated one participant. Similarly, others shared that during the tasks' performance with the generic GIS tools (ArcGIS and QGIS), they had to spend considerable time figuring out the right flow of geo-processes. On the other hand, the EasyUAZ tool presented a customised and structured approach where the desired commands were pre-embedded in the tool, along with their sequencing, to support urban research workflow required to create the UAZ file. Another participant commented, "EasyUAZ will be particularly useful for users having lesser experience in GIS workflows including buffering, shapefile editing, spatial joins etc". One participant commented that "In the case of ArcGIS and QGIS, we remained more focused on finding the GIS commands and geoprocessing tools than thinking about the planning problem at hand. While the EasyUAZ took that burden off, we were more focused onto the placement of planning factors and their categorisation. For example, while using EasyUAZ, I did not have to worry about what GIS processes are going at the backend; rather, I enjoyed categorising opportunity and constraint layers. I realised that I had some differences in how those factors were arranged, and I was able to rearrange them as per my choice". Most of the participants appreciated that EasyUAZ has been based on open source tools and hoped that this would allow a broader audience to contribute in the future and a great uptake due to both EasyUAZ and OWI being freely available.
On the other hand, while discussing the negative aspects, one participant noted that the EasyUAZ tool was not as stable as the generic GIS tools-"at the final stage of adding attributes to the UAZ file, the QGIS halted and was not responding for a long time. This delay crashed the EasyUAZ. It was shocking. However, I was relieved to know that the outputs of all the processes completed until that point were saved, and I did not have to redo all of the work". Another participant commented that that "although the EasyUAZ can detect topology errors, the fixing of topology has to be done outside the tool. It would be great if that can also be integrated within the workflow". The current unavailability of PyQGIS core APIs for topology checker is a barrier to incorporating this functionality in the EasyUAZ at the moment.
Another exciting dimension is exploring the extent to which the automation of the workflow, which indeed proved to increase the focus on spatial thinking rather than geo-processing, would have been affected to the black box effect, particularly for the new users. Since the inputs and output of the EasyUAZ are well known and well expected to the users; the automation does not create a sense of the usual software-related black box effect. In the traditional data preparation process for Online WhatIf?, the users have to trust the GIS tool (ArcGIS or QGIS) for the geoprocessing tasks, and that same level of the black-box syndrome would prevail for EasyUAZ as well. This tool does not alter or modify any of the geoprocessing tasks in their primary working; instead, it helps the users arrange their planning-factors data layers and run the necessary processing tasks more systematically so that the final output could match with the Online WhatIf? Input needs.

Other Use Cases
The participants were able to identify additional use cases for the EasyUAZ tool. Although the tool was initially designed to support the Online WhatIf? workflow [27], participants noted its value in assisting in data preparation for other spatial multi-criteria decision-making processes. In its current form, it can be used to calculate and add geometry fields (i.e., area) to the projected files.
Furthermore, it offers the summary calculations and charting on any attribute field, which can provide useful descriptive statistics when commencing new exploratory planning studies. The results of the factor calculations and classifications can be saved as the intermediary outputs. Those can be used for weighted overlay studies in other generic GIS tools (e.g., ArcGIS model builder) or other spatial MCE planning tools [90,91] other than the Online WhatIf?.

Conclusions
For the last ten years, there has a significant increase in the development and availability of planning support systems. However, the adoption has been slow due to various demand and supply factors. On the supply side, data hungriness and extensive data preparation requirements have been identified as a significant challenge to wider adoption [4,6,7]. The existing range of available PSS tools used in research and practice are data-intensive and require significant effort in conducting data pre-processing, cleaning, and loading, which remains a barrier to their wider adoption. Mostly the developers tend to focus more on PSS development to solve complex planning problems and give less attention to the data preparation workflow requires to support such data-intensive tools. As a result, many PSS are not well used as they require deep expertise in GIS and also there is a considerable investment in the time for configuring urban models and scenario planning tools. The development of the EasyUAZ tool presented in this paper endeavours to address these important issues to support the more rapid application of data-driven scenario planning tools to ensure they provide timely advice to planners and policy-makers [73].
This research presents a data processing workflow tool, the EasyUAZ, designed to support the Online WhatIf? planning support system. By applying the task-technology-fit (TTF) on the standard practice workflow of the Online WhatIf? to generate UAZ, requirements for the new pre-processing tool were documented, and the tool was developed as a QGIS plugin The comparative evaluation of the tool against a proprietary tool-based workflow (i.e., ArcMap) as well as an open-sourced tool based workflow (i.e., QGIS) reveals that the new tool can reduce the UAZ preparation time by 30%-35%. The other identified advantages include the ease of use, the opportunity for the user of PSS to focus more on the scenario planning approach rather than geospatial processing and file handling, and a shorter learning curve for basic GIS users. Its availability as an open-source tool will have an increased potential for future development and contribution by other users. Considering the large user base of the Online WhatIf? planning support system, the EasyUAZ tool will be beneficial to the existing and future users and will help improve the further adaptation of the PSS and ultimately other spatial MCE planning tool identified such as ENVISION [91]. Furthermore, this research has identified the need for further research and development into the simplification of complex urban models through reducing data processing time and ensure such models and planning support systems remain useable and relevant.