{"labelingInfo":null,"renderer":{"description":"Survey Data Locations","label":"GWRC Request for Information on Flood Forecasting Platforms","symbol":{"angle":0,"color":[255,0,0,255],"outline":{"color":[255,255,0,255],"width":1},"size":8,"style":"esriSMSCircle","type":"esriSMS","xoffset":0,"yoffset":0},"type":"simple"},"transparency":0}
HasZ: false
HasM: false
Has Attachments: false
Has Geometry Properties: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
worklocation (type: esriFieldTypeString, alias: Your work place location, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
q_1_1_1 (type: esriFieldTypeString, alias: Does the approach allow for precipitation input (observed or forecast); if so does the approach allow for redundancies in the monitoring network, allow the integration of Doppler radar data to understand QPE and other gridded precipitation sources?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_1_2 (type: esriFieldTypeString, alias: Can the approach account for snowmelt processes?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_1_3 (type: esriFieldTypeString, alias: Does the approach account for hydrological or hydraulic routing?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_1_4 (type: esriFieldTypeString, alias: Can the approach account for tidal and fluvial interaction?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_1_5 (type: esriFieldTypeString, alias: Can the approach apply data assimilation to flow forecasts using actual recorded data?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_1_6 (type: esriFieldTypeString, alias: Can the approach account for reservoir impoundment?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_2_1 (type: esriFieldTypeString, alias: Is the approach lumped and therefore able to present forecast output at fixed locations such as gauging stations or communities?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_2_2 (type: esriFieldTypeString, alias: Is the approach distributed and provide forecast output on a region-wide basis?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_3_1 (type: esriFieldTypeString, alias: What is the typical run time of the approach?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_3_2 (type: esriFieldTypeString, alias: Is the approach proven to work with flood forecasting platforms (operational flood forecasting systems) and if so, which systems is the approach being currently used?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_3_3 (type: esriFieldTypeString, alias: Are model runs able to be archived so all data used and produced in each run is saved?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_4_1 (type: esriFieldTypeString, alias: Is the solution widely used in the industry, i.e. several firms can deliver this approach or is it bespoke to your company?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_4_2 (type: esriFieldTypeString, alias: With training, are GWRC staff able to develop the calibration of the approach?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_4_3 (type: esriFieldTypeString, alias: Who currently offers support and maintenance of the solution?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_5_1 (type: esriFieldTypeString, alias: Is the approach currently in operation in Greater Wellington or New Zealand in a flood forecasting context?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_5_2 (type: esriFieldTypeString, alias: Is the approach currently in operation in another operational environment which offers similarities to the challenge in Wellington?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_5_3 (type: esriFieldTypeString, alias: What operational flood forecasting centres currently use this approach?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_6_1 (type: esriFieldTypeString, alias: Forecast approach. Used to understand the approach or combined approach to forecasting rivers, whether data-driven, conceptual and/or physical process, and its suitability for the forecasting challenge in Greater Wellington, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_6_2 (type: esriFieldTypeString, alias: Forecast output. Used to understand how the forecast will be output, i.e. can this support flood warning needs in Greater Wellington., SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_6_3 (type: esriFieldTypeString, alias: Operational considerations. Used to understand the operational requirements when supporting flood warning operation., SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_6_4 (type: esriFieldTypeString, alias: Support. Used to measure the practical nature of support and maintenance of the future solution., SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_1_6_5 (type: esriFieldTypeString, alias: Proven capability. Used to measure the proven nature of the solution and its suitability to Greater Wellington., SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_1_1 (type: esriFieldTypeString, alias: Is the platform able to integrate hydrometric data from the Hydrotel system?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_1_2 (type: esriFieldTypeString, alias: Is the platform able to integrate gridded precipitation data, and if so, can gridded data be post processed for catchment averages?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_1_3 (type: esriFieldTypeString, alias: Can the platform process ensemble gridded data?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_1_4 (type: esriFieldTypeString, alias: Can the system post process and quality control third party data?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_1_5 (type: esriFieldTypeString, alias: Does the platform have a facility to archive data?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_2_1 (type: esriFieldTypeString, alias: Can the platform be used by staff operating in a physically distributed Windows desktop environment, and what are the requirements?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_2_2 (type: esriFieldTypeString, alias: Does the platform support customisation through scripting or automation?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_2_3 (type: esriFieldTypeString, alias: What are the supported hosting environments (SaaS, Public/Private Cloud, OnPrem)?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_2_4 (type: esriFieldTypeString, alias: Is support and maintenance operated and if so, what arrangements are currently in place?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_2_5 (type: esriFieldTypeString, alias: Does future development, configuration, or extensions of the platform require vendor support, or can they be managed by GWRC and partners?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_2_6 (type: esriFieldTypeString, alias: What is the level of consideration/certification around data security, privacy, and risk, and have any third party assessments been done against the platform?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_3_1 (type: esriFieldTypeString, alias: Does the platform allow for displaying information on a map display?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_3_2 (type: esriFieldTypeString, alias: What role do users have to interact with the forecast output, i.e. is model data manipulation possible or is this more black box?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_3_3 (type: esriFieldTypeString, alias: Does the platform access observations remotely and run the model automatically?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_3_4 (type: esriFieldTypeString, alias: Can the platform support real time inundation mapping?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_3_5 (type: esriFieldTypeString, alias: What form of forecast verification or performance analysis can be performed?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_3_6 (type: esriFieldTypeString, alias: Can the platform link forecast output to other dissemination channels, e.g. social media or SMS?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_3_7 (type: esriFieldTypeString, alias: Does the platform allow multi-model ensembles or probabilistic distributions?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_4_1 (type: esriFieldTypeString, alias: What models are compatible with the platform solution? GWRC currently operates models including DHI MIKE FLOOD/OPERATIONS and Hydrol/Timestudio. GWRC has the Aquarius Forecast model software. Hydrol/Timestudio is no longer supported and Aquarius Forecast can incorporate the existing models., SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_5_1 (type: esriFieldTypeString, alias: Data integration.To assess if the platform is suitable for integrating existing hydrometric and future meteorological data, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_5_2 (type: esriFieldTypeString, alias: ICT considerations. To ensure GWRC future support and maintenance needs are taken into consideration, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_5_3 (type: esriFieldTypeString, alias: Forecast interface. To ensure the usability of the system meets GWRC's requirements, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
q_2_5_4 (type: esriFieldTypeString, alias: Model compatibility. To ensure existing and future model approaches are compatible, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)