Modelling tool user interfaces - Revision history

Julia Glenday: /* User impressions of 'ease-of-use' (modeller survey) */

2023-12-04T09:44:52Z

User impressions of 'ease-of-use' (modeller survey)

Julia Glenday: /* Formats of input and output data */

2023-12-04T09:14:09Z

Formats of input and output data

Julia Glenday at 09:11, 4 December 2023

2023-12-04T09:11:29Z

Julia Glenday at 09:10, 4 December 2023

2023-12-04T09:10:51Z

Julia Glenday at 08:32, 4 December 2023

2023-12-04T08:32:58Z

Julia Glenday: /* User ratings across tools */

2023-12-04T08:28:26Z

User ratings across tools

Julia Glenday at 08:25, 4 December 2023

2023-12-04T08:25:47Z

Julia Glenday at 15:27, 1 December 2023

2023-12-01T15:27:33Z

Julia Glenday at 13:50, 1 December 2023

2023-12-01T13:50:38Z

Julia Glenday: /* Interface comparison overview */

2023-12-01T13:46:50Z

Interface comparison overview

@@ Line 186: / Line 186: @@
 == User impressions of 'ease-of-use' (modeller survey) ==
 A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software user interface, it's documentation, and available support for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''</br>
-There was a very wide range of scores assigned for each tool across the respondents, showing that different people experience the tools differently! </br>
+There was a ''very'' wide range of different scores assigned for each tool across the respondents, with some assigning a poor score while others assign and excellent score to the same tool, showing that different people experience the tools differently! </br>
-Both the average and the range of scores assigned are presented below.
+Both the average and the range of scores assigned are presented below.</br>
-(Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]])
+(Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]])</br>
 {| class="wikitable"
-! scope="col" style="width:15em" | Survey data <big></big>
+! scope="col" style="width:15em" colspan="2"| Aspect of tool <big></big>
 ! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
 ! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
@@ Line 197: / Line 200: @@
 ! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
 |-
-| style="vertical-align: vertical-align: center;" |''Number of users answering survey''
+| style="vertical-align: vertical-align: center;" colspan="2"|'''''Number of users answering survey'''''<big></big>
 | style="background: #FFF5FA; vertical-align: center; text-align:center;" |''13''
 | style="background: #FFF7F5; vertical-align: center; text-align:center;" |''14''
@@ Line 204: / Line 207: @@
 | style="background: #F5FCFF; vertical-align: center; text-align:center;" |''8''
 |-
-| style="vertical-align: vertical-align: center;" |'''Average ease-of-use score''' </br><small> 1-poor to 5-excellent
+| rowspan="2"; style="vertical-align: top; width:10em "|'''Interface'''<big></big></br><small> 1-poor to 5-excellent
-| style="background: #FFF5FA; vertical-align: center; text-align:center;" |3.8
+| style="vertical-align: vertical-align: center;" |''Average score'' <big></big>
-| style="background: #FFF7F5; vertical-align: center; text-align:center;" |3.4
+| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''3.8
-| style="background: #F5FFF5; vertical-align: center; text-align:center;" |3.4
+| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''3.4
-| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3.9
+| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''3.4
-| style="background: #F5FCFF; vertical-align: center; text-align:center;" |3.0
+| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''3.9
 |-
-| style="vertical-align: vertical-align: center;" |'''Range of scores assigned'''</br><small> 1-poor to 5-excellent
+| style="vertical-align: vertical-align: center;" |''Range of scores''<big></big>
 | style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
 | style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
 | style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
 | style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
 | style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
 |}

@@ Line 158: / Line 158: @@
 ! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
 |-
-| style="vertical-align: top;" |'''Timeseries data'''
+| style="vertical-align: top;" |</br>'''Timeseries data'''
 | style="background: #FFF5FA; vertical-align: top; text-align: left;" |</br>'''Specially formatted text files (special file extensions)'''
-</br> Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. </br> Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
+</br><small>Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. </br> Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
 | style="background: #FFF7F5; vertical-align: top; text-align: left;" |</br>'''Specially formatted text files (.txt)'''
-</br> Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
+</br><small> Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
 | style="background: #F5FFF5; vertical-align: top; text-align: left;" |</br>'''Specially formatted ASCII text files (.txt) & .DBF files'''
-</br> Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. </br> Outputs are .dbf format text files which open easily in Excel.
+</br><small> Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. </br> Outputs are .dbf format text files which open easily in Excel.
 | style="background: #FFFFF5; vertical-align: top; text-align: left;" |</br>'''Specially formatted text files (.txt) & Access database files '''
-</br> Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. </br> Outputs can also be produced in an Access database.
+</br><small> Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. </br> Outputs can also be produced in an Access database.
 | style="background: #F5FCFF; vertical-align: top; text-align: left;" |</br>'''Software-specific .dfs0 file format'''
-</br> Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
+</br><small> Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
 |-
-| style="vertical-align: top;" |'''Spatial data'''
+| style="vertical-align: top;" |</br>'''Spatial data'''
 | style="background: #FFF5FA; vertical-align: top; text-align:left;" |</br>'''N/A''' </br>(Spatial data is not ''directly'' input into the software)
-</br>''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
+</br><small>''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
 | style="background: #FFF7F5; vertical-align: top; text-align:left;" |</br>'''N/A''' </br>(Spatial data is not ''directly'' input into the software)
-</br>''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
+</br><small>''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
 | style="background: #F5FFF5; vertical-align: top; text-align:left;" |</br>'''N/A''' </br>(Spatial data is not ''directly'' input into the software)
-</br>''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
+</br><small>''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
 | style="background: #FFFFF5; vertical-align: top; text-align:left;" |</br>'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
-</br> DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). </br> Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. </br> Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
+</br><small> DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). </br> Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. </br> Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
 | style="background: #F5FCFF; vertical-align: top; text-align:left;" |</br>'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
-</br> dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. </br> Subcatchments and landcover can be input as shapefiles. </br> Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. </br>.dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
+</br><small> dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. </br> Subcatchments and landcover can be input as shapefiles. </br> Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. </br>.dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
 |}
 </br>

← Older revision		Revision as of 09:11, 4 December 2023
Line 3:		Line 3:
	What can be achieved in the time available for a modelling project is influenced by the combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, laborious, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).		What can be achieved in the time available for a modelling project is influenced by the combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, laborious, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).

−	Ease and efficiency of software use is also influenced by the documentation and support available for the tool. How accessible and user-friendly these are can determine whether or not users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly. User impressions of the ease of use of tool interfaces, documentation, and support are provided [[below]]. Links to online documentation and support resources for these tools are provided [[Modelling tool documentation\|here]]	+	Ease and efficiency of software use is also influenced by the documentation and support available for the tool. How accessible and user-friendly these are can determine whether or not users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly. User impressions of the ease of use of tool interfaces, documentation, and support are provided [[#User impressions of 'ease-of-use' (modeller survey)\|below]]. Links to online documentation and support resources for these tools are provided [[Modelling tool documentation\|here]]

@@ Line 1: / Line 1: @@
-The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration.
+The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration. (More specifics about what outputs each tool can produce is covered [[Water balance outputs across tools|here]].)
-The combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model influences what can be achieved in the time that is available for a modelling project. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).
+What can be achieved in the time available for a modelling project is influenced by the combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, laborious, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).
-Ease and efficiency of software use is also influenced by the documentation and support available for the tool - how accessible and user-friendly these are can prevent users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly.
+Ease and efficiency of software use is also influenced by the documentation and support available for the tool. How accessible and user-friendly these are can determine whether or not users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly. User impressions of the ease of use of tool interfaces, documentation, and support are provided [[below]]. Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]]
@@ Line 10: / Line 10: @@
 </br>
-== Interface comparison overview  ==
+== Interface comparison ==
 {| class="wikitable"
@@ Line 185: / Line 185: @@
 == User impressions of 'ease-of-use' (modeller survey) ==
-A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software interface for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''</br>
+A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software user interface, it's documentation, and available support for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''</br>
 There was a very wide range of scores assigned for each tool across the respondents, showing that different people experience the tools differently! </br>
-Both the average and the range of scores assigned are presented below
+Both the average and the range of scores assigned are presented below.
 {| class="wikitable"
 ! scope="col" style="width:15em" | Survey data <big></big>
@@ Line 216: / Line 217: @@
 | style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
 | style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
 |}

← Older revision		Revision as of 08:32, 4 December 2023
Line 2:		Line 2:

	The combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model influences what can be achieved in the time that is available for a modelling project. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).		The combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model influences what can be achieved in the time that is available for a modelling project. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).
		+
		+	Ease and efficiency of software use is also influenced by the documentation and support available for the tool - how accessible and user-friendly these are can prevent users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly.

← Older revision		Revision as of 08:28, 4 December 2023
Line 217:		Line 217:


−	== User ratings ~~across~~ tools ==	+	== User ratings of tools' documentation & support (modeller survey) ==

	In 2021, we surveyed the South African hydrological modelling community to ask them about their modelling background and level, which tools they used, and what their perceptions about these tools were. Specifically we asked them to rate the ease-of-use of the user interface, the ease-of-use of the documentation as well as the support of each modelling tool on a scale of 1-5, 1 being poor, 3 being satisfactory, and 5 being excellent. On 31 May 2021 we had 45 responses, and we summarised results here for any modelling tools that were reviewed by more than two people (i.e. sample size greater than 2). If you are choosing a modelling tool for your project, perhaps this table, as well as those on capabilities and specific use cases, would help you make a decision on which to select.		In 2021, we surveyed the South African hydrological modelling community to ask them about their modelling background and level, which tools they used, and what their perceptions about these tools were. Specifically we asked them to rate the ease-of-use of the user interface, the ease-of-use of the documentation as well as the support of each modelling tool on a scale of 1-5, 1 being poor, 3 being satisfactory, and 5 being excellent. On 31 May 2021 we had 45 responses, and we summarised results here for any modelling tools that were reviewed by more than two people (i.e. sample size greater than 2). If you are choosing a modelling tool for your project, perhaps this table, as well as those on capabilities and specific use cases, would help you make a decision on which to select.

@@ Line 1: / Line 1: @@
 The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration.
-The combination of how long it takes to set up a model, how long it takes to run a model, how long it takes to access model outputs of interest, and how long it takes to test and refine the model all influence what can be achieved in the time that is available for a modelling projects. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, making calibration a time consuming manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model runs require a lot of computing power!).
+The combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model influences what can be achieved in the time that is available for a modelling project. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).
 == Interface comparison overview  ==
 {| class="wikitable"
-! scope="col" style="width:15em" | Interface characteristic
+! scope="col" style="width:15em" | Interface characteristic <big></big>
 ! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
 ! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
@@ Line 139: / Line 144: @@
 </br>
-== Formats for input-output data ==
+== Formats of input and output data ==
 The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. </br> For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.
 {| class="wikitable"
-! scope="col" style="width:10%" |'''Data type'''
+! scope="col" style="width:10%" |'''Data type''' <big></big>
 ! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
 ! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
@@ Line 175: / Line 180: @@
 </br> dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. </br> Subcatchments and landcover can be input as shapefiles. </br> Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. </br>.dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
 |}
-== Ease of use rating from surveyed users  ==
+== User impressions of 'ease-of-use' (modeller survey) ==

← Older revision		Revision as of 13:50, 1 December 2023
Line 175:		Line 175:
	</br> dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. </br> Subcatchments and landcover can be input as shapefiles. </br> Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. </br>.dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.		</br> dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. </br> Subcatchments and landcover can be input as shapefiles. </br> Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. </br>.dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
	\|}		\|}
		+
		+	== Ease of use rating from surveyed users ==

@@ Line 137: / Line 137: @@
 | style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
 |}
 == Formats for input-output data ==