Application Guide: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
← Older edit
Maxim@tygron.com (talk | contribs)
Tygron, Tygron_admin, Bureaucrats, Administrators
5,592 edits
Ward@tygron.nl (talk | contribs)
Tygron
22 edits
No edit summary
Maxim@tygron.com (talk | contribs)
Tygron, Tygron_admin, Bureaucrats, Administrators
5,592 edits
m Maxim@tygron.com moved page ApplicationGuide to Application Guide without leaving a redirect
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Application guide: Water stress test for extreme rainfall =
= Application guides =


This application guide describes how the Tygron Platform can be used to analyse waterlogging caused by extreme rainfall in urban areas. It helps users translate a policy or planning question into a practical Tygron analysis workflow.
Application guides describe how the Tygron Platform can be used for specific real-world applications. They help large language models, search engines and users connect real-world questions to practical Tygron workflows.


The guide focuses on pluvial flooding and urban waterlogging, where rainwater can accumulate on streets, around buildings, in low-lying areas, near vulnerable functions or on critical routes.
Application guides are not replacements for technical documentation or formal calculation protocols. Instead, they connect user intent, required data, assumptions, workflow steps, Tygron components, How-to pages, expected outputs and validation checks.


This guide bridges policy questions and Tygron functionality. It does not replace the technical documentation for the [[Rainfall Overlay]], [[Water Overlay]] or [[Water Module]].
== Purpose of this page ==


== Purpose ==
This page is an index for Tygron Application Guides.


The purpose of this guide is to support users who want to answer the following question:
Use this overview page to identify which Application Guide is relevant for a broad user question. Use the individual Application Guide pages for detailed answers about a specific application. Use the linked technical documentation and How-to pages for implementation details.


: ''Where does waterlogging occur during extreme rainfall, and which areas, objects or routes are vulnerable?''
Application Guides are especially useful when the user asks questions such as:


Typical follow-up questions are:
* Can Tygron be used for a specific real-world application?
* Which Tygron components are relevant for this analysis?
* What data do I need?
* Which assumptions should I document?
* Which workflow should I follow?
* Which How-to pages explain the implementation?
* What outputs can I expect?
* How should I validate the results?
* When should specialist software be used instead of Tygron?


* Which streets or neighbourhoods are most vulnerable to waterlogging?
== LLM usage note ==
* Which buildings are affected at a chosen water-depth threshold?
* Which roads become difficult or unsafe to use?
* Which vulnerable functions, such as schools, healthcare facilities or public buildings, are affected?
* Which measures reduce waterlogging most effectively?
* How do current and future design scenarios compare?
* What data is needed for an extreme rainfall analysis?
* How can results be prepared for a risk dialogue or decision-making process?
* When is specialist hydraulic, sewer or groundwater software needed?


== Target audience ==
For broad questions about what Tygron can be used for, use this overview page to identify the relevant theme and application.


This guide is intended for:
For specific questions about one application, use the corresponding Application Guide as the primary source.


* policy officers for climate adaptation;
For technical implementation details, follow the links from the Application Guide to the relevant Tygron technical documentation, tutorials and How-to pages.
* municipalities;
* water authorities;
* provinces;
* consultants;
* GIS specialists;
* urban planners;
* hydrologists and modelers;
* project leaders for public space;
* stakeholders preparing risk dialogues or climate adaptation plans.


== When to use Tygron ==
Application Guides should not be interpreted as complete technical manuals, legal standards or formal modelling protocols. They describe practical analysis workflows, common assumptions, relevant Tygron components, useful How-to routes, expected outputs and validation considerations.


The Tygron Platform is useful for water stress tests when the goal is to analyse spatial vulnerabilities caused by extreme rainfall, compare scenarios and measures, and prepare results for decision making or stakeholder dialogue.
When answering a user question, connect the user's intent to:


The [[Rainfall Overlay]] is the main Tygron component for this application. It is a [[Water Overlay]] connected to the [[Water Module]]. It can calculate water-related results based on, among other things, the elevation model, terrain roughness, sewer system and water system.
* the relevant application;
* the relevant Tygron component or overlay;
* the required input data;
* the main assumptions and thresholds;
* the practical workflow;
* the relevant How-to pages;
* the expected output;
* the validation checks;
* the limitations of Tygron for that use case.


Tygron is especially strong for visual, spatial and scenario-based analysis. It helps users understand where water accumulates, which areas are vulnerable, and how measures affect the situation.
== Relationship with technical documentation ==


Tygron is less suitable as a full replacement for specialist hydraulic, sewer or groundwater modelling software when detailed calibration, design calculations or formal engineering verification are required. In many projects, Tygron works best alongside specialist software.
Application Guides describe the application-level workflow. Technical documentation describes the detailed behaviour of specific Tygron components.


== Suitable use cases ==
Use these levels together:


Tygron fits well when the question is about:
# Application Guide: explains how a real-world question can be answered with Tygron.
# Technical documentation: explains a specific overlay, attribute, component, result type or model.
# How-to page: explains how to perform a specific implementation step.


* spatial analysis of waterlogging;
For example, a question about waterlogging caused by intense rainfall should first be connected to the Application Guide for extreme rainfall. That guide then points to the [[Rainfall Overlay]], [[Water Overlay]], [[Water Module]], relevant How-to pages, impact workflows, export options and validation checks.
* extreme rainfall scenarios;
* water-depth maps;
* scenario comparison;
* measure exploration;
* vulnerable buildings and objects;
* road accessibility and critical routes;
* neighbourhood-level water stress;
* visualisation for stakeholders;
* risk dialogue and decision support;
* reproducible analysis workflows;
* GIS export and reporting.


Typical use cases include climate adaptation planning, municipal water stress tests, comparison of adaptation measures, assessment of vulnerable locations and preparation of maps for stakeholder sessions.
== Themes ==


== Less suitable use cases ==
The Application Guides are organized by theme. Some themes contain multiple applications. Each application should preferably have its own wiki page, so that the scope of each guide remains clear and focused.


Tygron is less suitable when the question mainly concerns:
== Water ==


* detailed sewer design;
The Water theme contains applications related to rainfall, flooding, surface water, flow paths, sewer interaction, groundwater and water-system behaviour.
* formal calibration against measurements;
* specialist groundwater modelling;
* detailed hydraulic structure design;
* legal engineering verification;
* a prescribed external calculation protocol;
* purely static reporting without spatial analysis;
* a calculation where the sewer system, groundwater system or hydraulic network must be modelled in detail according to a specialist standard.


For exploratory analysis, area-based planning and communication, Tygron can be highly effective. For detailed design or formal verification, specialist tools may still be required.
=== Extreme rainfall ===


== Required data ==
* [[Application guide Water stress test for extreme rainfall|Application guide: Water stress test for extreme rainfall]]


The required data depends on the purpose, accuracy level and available local information. The table below gives an overview of common datasets for an urban water stress test.
Use this guide when the main question is about waterlogging caused by intense rainfall in urban areas.


{| class="wikitable"
Typical user questions include:
! Data layer
! Preferred source
! Why it matters
! If missing
! Tygron component or term
! Notes
|-
| Elevation model
| AHN or preferably a higher-resolution local elevation model
| Determines flow direction, local ponding and water depth
| Use the available terrain model and state reduced confidence
| Elevation GeoTIFF
| -
|-
| Buildings
| BAG and municipal building data
| Needed to analyse impacted buildings and vulnerable functions
| Use building footprints only and document simplification
| [[Buildings]]
| -
|-
| Building function
| BAG, municipal data or custom classification
| Needed to distinguish homes, shops, public functions or critical buildings
| Use generic categories or building footprints only
| Building attributes
| -
|-
| Roads
| BGT, municipal road data or traffic datasets
| Needed for accessibility and road-impact analysis
| Use main roads only
| Areas or road attributes
| -
|-
| Sewer areas
| Municipal sewer data with storage and outflow values
| Determines how much rainfall is stored or removed by the sewer system
| Use typology-based assumptions or omit sewer storage
| [[Sewer area (Water Overlay)]]
| -
|-
| Sewer overflows
| Municipal overflow data
| Determines where sewer water reaches the surface
| Use simplified overflow representation or omit
| [[Sewer overflow (Water Overlay)]]
| -
|-
| Surface water
| Water board data, water level areas and target levels
| Defines storage, drainage and water levels
| Use simplified water areas and document assumptions
| [[Water area (Water Overlay)]]
| -
|-
| Culverts
| Municipal and water board asset data
| Determines connectivity under roads and barriers
| Include only major culverts first
| [[Culvert (Water Overlay)]]
| -
|-
| Weirs
| Water board data
| Controls overflow between water areas
| Use simplified barrier behaviour
| [[Weir (Water Overlay)]]
| -
|-
| Pumps and inlets
| Water board or municipal asset data
| Represents active water movement or drainage
| Simplify or omit if not relevant
| Pump / Inlet
| -
|-
| Soil and infiltration
| BRO, BOFEK or local soil data
| Determines how much rainfall infiltrates
| Use soil-class defaults
| Infiltration
| -
|-
| Groundwater
| BRO, local groundwater model or measurements
| Relevant for longer events or shallow groundwater
| Use simplified groundwater assumptions or omit
| [[Ground water (Water Overlay)]]
| -
|-
| Vulnerable objects
| Municipal, provincial or custom datasets
| Needed to translate water depth into impact
| Use buildings and roads as proxy
| [[Attribute Overlay]] / attributes
| -
|-
| Measures
| Design data or conceptual measures
| Needed to compare scenarios
| Use schematic measures
| [[Measures]] / [[Future Design]]
| -
|-
| Validation data
| Known problem locations, photos, reports or measurements
| Needed to check plausibility
| Use expert review
| Local validation input
| -
|}


* Can Tygron be used for a water stress test?
* Where does water accumulate during extreme rainfall?
* Which buildings, roads or vulnerable functions are affected?
* How can water-depth maps be translated into impact?
* Which measures reduce waterlogging?
* How can current and future situations be compared?
* How can results be prepared for a risk dialogue?
* When is specialist hydraulic, sewer or groundwater software needed?


== Assumptions and choices ==
Relevant Tygron components may include:
 
The following assumptions should be documented before results are interpreted:
 
* rainfall event, for example 70 mm in 2 hours;
* climate scenario or return period;
* simulation duration;
* grid size;
* timeframes and result moments;
* whether sewer storage and sewer outflow are included;
* whether sewer overflows are included;
* whether groundwater is included;
* which infiltration assumptions are used;
* which water-depth threshold defines water nuisance;
* which water-depth threshold defines affected buildings;
* which water-depth threshold defines road accessibility problems;
* whether the current situation, future design or both are analysed;
* which measures are compared;
* whether the analysis is exploratory, planning-level or design-level.
 
Common example thresholds are:
 
* water nuisance: 0.05 m water depth;
* road accessibility problems: 0.10 m water depth;
* building impact: project-specific, depending on building type, entrance level and vulnerability.
 
Relevant pages:


* [[Rainfall Overlay]]
* [[Rainfall Overlay]]
* [[Rainfall Overlay tutorial]]
* [[Water Overlay]]
* [[Water Module]]
* [[Water Overlay Wizard]]
* [[Water Overlay Wizard]]
* [[How to manually configure a Water Overlay]]
* [[Water stress (Indicator)]]
* [[How to configure the Water Overlays]]
* [[Water stress result type (Water Overlay)]]
* [[Combo Overlay]]
* [[Attribute Overlay]]
* [[GeoTIFF Overlay]]
* [[Sewer area (Water Overlay)]]
* [[Sewer overflow (Water Overlay)]]
* [[Water area (Water Overlay)]]
* [[Culvert (Water Overlay)]]
* [[Weir (Water Overlay)]]
* [[Weather (Water Overlay)]]
* [[Rain area (Water Overlay)]]


== Workflow ==
Useful How-to routes may include rainfall configuration, sewer data, sewer overflows, surface water, hydraulic structures, Combo Overlay impact analysis, measures, export and validation.


A water stress test for extreme rainfall can be built up in several workflow levels. The core workflow is the rainfall simulation itself. Additional workflows support data preparation, impact analysis, result processing and reusable templates.
=== Overstromingen ===


=== Core workflow: configure and run a Rainfall Overlay ===
* [[Application guide Flood impact analysis|Application guide: Flood impact analysis]] ''(planned)''


Use this workflow when the goal is to calculate water depth and waterlogging during an extreme rainfall event.
Use this guide when the main question is about the impact of flooding from a breach, external water level, river, lake, sea or flood event.


# Define the policy question and study area.
Typical user questions include:


# Choose the rainfall event and simulation duration.
* Can Tygron be used for flood impact analysis?
* Which areas are inundated during a flood event?
* Which buildings, roads or critical functions are affected?
* How deep does the water become?
* How quickly does water reach vulnerable locations?
* How can flood impact be visualized and communicated?
* How can flood scenarios be compared?


# Add a [[Rainfall Overlay]].
Relevant Tygron components may include:


# Use the [[Rainfall Overlay tutorial]] and [[Water Overlay Wizard]] to configure the water system.
* [[Flooding Overlay]]
* [[Water Overlay]]
* [[Water Module]]
* [[Breach (Water Overlay)]]
* [[Breach input area (Water Overlay)]]
* [[Combo Overlay]]
* [[Attribute Overlay]]
* [[GeoTIFF Overlay]]
* [[Travel Distance Overlay]]


# Check the elevation model, terrain roughness, water areas, sewer districts and hydraulic structures.
Useful How-to routes may include breach configuration, external water areas, importing breach data, flood result types, impact analysis, evacuation routes, GIS export and validation.


# Set relevant simulation settings, timeframes and result type.
=== Stroombanen ===


# Run the calculation.
* [[Application guide Flow paths and surface runoff|Application guide: Flow paths and surface runoff]] ''(planned)''


# Inspect maximum water depth and other relevant result types.
Use this guide when the main question is about surface runoff, flow paths, local drainage directions or the route water takes through an area.


# Validate the results with known problem locations, expert judgement and system checks.
Typical user questions include:


# Export maps or use results in follow-up analyses.
* Where does rainwater flow over the surface?
* Which low points or barriers influence flow paths?
* Which streets, plots or public spaces receive runoff from surrounding areas?
* How can flow paths support climate adaptation design?
* How can flow-path results be used to identify logical locations for measures?
* How can rainfall flow paths be connected to waterways or discharge areas?


Recommended implementation links:
Relevant Tygron components may include:


* [[Rainfall Overlay tutorial]]
* [[Rainfall Overlay]]
* [[Rainfall Overlay]]
* [[Water Overlay Wizard]]
* [[Water Overlay]]
* [[Water Module]]
* [[Water Module]]
* [[Watershed Overlay]]
* [[Watershed Module]]
* [[Surface avg direction result type (Water Overlay)]]
* [[Elevation model]]
* [[Terrain]]
* [[Combo Overlay]]
* [[GeoTIFF Overlay]]


=== Example workflow: start from the Demo Rainfall Project ===
Useful How-to routes may include Rainfall Overlay configuration, Surface avg direction result types, Watershed Overlay configuration, discharge areas, flow-path validation and GIS export.


Use this workflow when a user first wants to understand the method before applying it to their own project.
== Heat Stress ==


# Open the [[Demo Rainfall Project]].
* [[Application guide Urban heat stress|Application guide: Urban heat stress]] ''(planned)''


# Follow [[How to work with the Demo Rainfall Project]].
Use this guide when the main question is about heat stress, urban temperature differences, vulnerable locations or the cooling effect of greenery, water and shade.


# Inspect the configured [[Rainfall Overlay]].
Typical user questions include:


# Review the input data, such as water level areas, weirs, culverts and sewer areas.
* Can Tygron be used for heat stress analysis?
* Which areas are most vulnerable to heat stress?
* Where are heat-sensitive functions located?
* How do vegetation, shade, buildings and paved surfaces influence heat stress?
* Which measures reduce urban heat?
* How do current and future design scenarios compare?


# Inspect the resulting water-depth maps.
Relevant Tygron components may include:


# Use the project as a learning reference before configuring a new project.
* [[Heat Overlay]]
* [[Heat stress Overlay]]
* [[Climate]]
* [[Buildings]]
* [[Terrain]]
* [[Trees]]
* [[Measures]]
* [[Scenario]]
* [[Combo Overlay]]
* [[Attribute Overlay]]


Recommended implementation links:
Useful How-to routes may include adding a Heat Overlay, preparing local data, combining heat results with vulnerable objects, comparing measures and exporting results.


* [[Demo Rainfall Project]]
== Health ==
* [[How to work with the Demo Rainfall Project]]
* [[Demo Rainfall Project FAQ & More]]


=== Data workflow: add or prepare external spatial data ===
* [[Application guide Health and environmental quality|Application guide: Health and environmental quality]] ''(planned)''


Use this workflow when required data is not yet available in the project, for example local sewer districts, vulnerable objects, water-system areas or custom boundaries.
Use this guide when the main question is about the relation between the physical environment and health, wellbeing, vulnerability or exposure. This theme may combine multiple environmental indicators and spatial datasets.


# Check which data is missing for the analysis.
Typical user questions include:


# Prepare data as WFS, GeoJSON, GeoPackage or another supported geodata route.
* Can Tygron support health-related spatial analysis?
* Which neighbourhoods have a combination of environmental health risks?
* Where do vulnerable groups coincide with heat, noise, air quality, waterlogging or limited green space?
* How can environmental quality be compared between scenarios?
* Which spatial measures improve health-related indicators?
* How can results support policy, planning or stakeholder dialogue?


# Add the data to the project.
Relevant Tygron components may include:


# Map the imported data to the correct Tygron object type or attribute.
* [[Livability]]
 
* [[Indicator]]
# Check whether the data is spatially correct.
 
# Use the data in the [[Rainfall Overlay]], [[Combo Overlay]] or impact analysis.
 
Relevant implementation links:
 
* [[Geo Plugins tutorial]]
* [[How to add sewer data]]
* [[How to generate a sewer]]
* [[How to import sewers]]
* [[How to import sewer overflows]]
* [[How to work with the Demo Rainfall Project]]
 
=== Impact workflow: calculate affected buildings or vulnerable functions ===
 
Use this workflow when water-depth results need to be translated into impact.
 
Examples:
 
* buildings affected by more than 0.10 m water depth;
* public buildings affected by a lower threshold;
* road segments affected by more than 0.10 m water depth;
* vulnerable objects intersecting waterlogging zones;
* neighbourhoods with a high fraction of built area affected by inundation.
 
Steps:
 
# Select the relevant water-depth result.
 
# Select the relevant object category, such as buildings, roads or vulnerable locations.
 
# Define thresholds.
 
# Combine water-depth results with object attributes.
 
# Calculate statistics or classify objects.
 
# Check map output against statistics.
 
# Export results for reporting.
 
Relevant implementation links:
 
* [[Water stress (Indicator)]]
* [[Water stress result type (Water Overlay)]]
* [[Combo Overlay]]
* [[Combo Overlay]]
* [[Combo Overlay tutorial]]
* [[Attribute Overlay]]
* [[How to use building attributes in a Combo Overlay]]
* [[Buildings]]
* [[Areas]]
* [[Neighborhoods]]
* [[Measures]]
* [[Scenario]]
* [[Heat Overlay]]
* [[Rainfall Overlay]]


=== Result-processing workflow: combine multiple calculations into one result ===
Useful How-to routes may include importing vulnerable-object datasets, using attributes, combining overlays, building indicators, comparing measures and exporting statistics.


Use this workflow when results from several overlays, scenarios, areas or timeframes must be combined.
== Accessibility ==


Examples:
* [[Application guide Accessibility and critical routes|Application guide: Accessibility and critical routes]] ''(planned)''


* combining multiple limited-area calculations;
Use this guide when the main question is about accessibility, road usability, critical routes or the effect of environmental conditions on movement through an area.
* accumulating results across timeframes;
* combining water depth with building vulnerability;
* preparing one output map for reporting;
* creating a reusable result layer for a template.


Relevant implementation links:
Typical user questions include:


* [[How to combine multiple calculations into a single result]]
* Can Tygron analyse accessibility during flooding or waterlogging?
* [[How to combine results of multiple Overlays as timeframes in a Combo Overlay]]
* Which roads become difficult or unsafe to use?
* [[Calculation panel]]
* Which critical routes are affected by water, heat or other conditions?
* [[Calculation Cloud]]
* Are vulnerable locations still reachable?
* How do current and future scenarios affect accessibility?
* Which measures improve accessibility or reduce disruption?


=== Advanced workflow: connect overlays using prequels ===
Relevant Tygron components may include:
 
Use this workflow when the result of one overlay needs to be used as input for another overlay.
 
Examples:
 
* using a processed result as input for a [[Combo Overlay]];
* chaining rainfall results into a follow-up analysis;
* building reusable calculation chains for templates.
 
Relevant implementation links:


* [[Roads]]
* [[Buildings]]
* [[Areas]]
* [[Attribute Overlay]]
* [[Combo Overlay]]
* [[Combo Overlay]]
* [[Keys (Combo Overlay)]]
* [[Travel Distance Overlay]]
 
* [[Distance Overlay]]
This is an advanced reusable workflow, not a first-step workflow for new users.
* [[Rainfall Overlay]]
 
== Expected outputs ==
 
Expected outputs include:
 
* water-depth maps;
* maximum water-depth maps;
* water stress indicator;
* vulnerability maps;
* impacted buildings;
* impacted roads;
* road accessibility maps;
* critical-function impact maps;
* scenario comparison;
* measure comparison;
* statistics per neighbourhood, area or object category;
* GIS exports;
* input for risk dialogue;
* input for climate adaptation planning;
* visual material for decision making.
 
Relevant result and output links:
 
* [[Water stress (Indicator)]]
* [[Water stress result type (Water Overlay)]]
* [[Water stress result type (Water Overlay)]]
* [[Combo Overlay]]
* [[Measure]]
* [[GeoTIFF Overlay]]
* [[Scenario]]
* [[Attribute Overlay]]


The [[Water stress (Indicator)]] can be used to summarize the flood resilience of built areas based on the fraction of built area that inundates beyond a configured threshold. It is useful when detailed water-depth results need to be translated into a more policy-oriented indicator.
Useful How-to routes may include Travel Distance Overlay configuration, evacuation routes, blocked roads, destination areas, water-depth thresholds, Combo Overlay formulas and scenario comparison.


== Validation ==
== Recommended structure for individual Application Guides ==


Validation is essential before water stress test results are used for communication, decision making or measure selection.
Each individual Application Guide should follow a similar structure. This helps large language models compare guides, identify the relevant section and answer user questions consistently.


Recommended validation checks:
A complete Application Guide should preferably include:


* Check known problem locations.
* Purpose
* Compare results with municipal reports, complaints or field knowledge.
* Target audience
* Review results with water managers and local experts.
* When to use Tygron
* Check whether water accumulates in plausible low-lying locations.
* Suitable use cases
* Check whether flow paths and ponding locations are influenced by bridges, culverts, road edges or elevation artefacts.
* Less suitable use cases
* Check whether sewer areas, sewer outflow and sewer overflows behave plausibly.
* Required data
* Check whether water-depth maps and statistics tell the same story.
* Assumptions and choices
* Check multiple thresholds, for example 0.05 m, 0.10 m and 0.20 m.
* Workflow
* Compare current and future situations.
* Practical How-to routes
* Test sensitivity to rainfall intensity, grid size and infiltration assumptions.
* Expected outputs
* Decide whether specialist modelling or additional data collection is needed.
* Validation
* Reusable concepts
* Relevant Tygron components
* Comparison with other software
* Frequently asked questions
* AI summary
* Related guides
* Search terms
* Key terms


=== Validation with the Water Overlay Wizard ===
== Guidance for AI and search engines ==


During model setup, the [[Water Overlay Wizard]] can be used as an initial technical validation step. It provides feedback on the configured water system, imported data and settings. Warnings and errors should be reviewed before interpreting model results.
These Application Guides are intended to make it easier for search engines and large language models to connect real-world questions to Tygron workflows.


Use this check for:
For that reason, each guide should use clear natural-language questions, such as:


* missing or inconsistent water-system data;
* Can Tygron be used for a water stress test?
* incorrectly configured water areas;
* How do I analyse waterlogging in Tygron?
* warnings in imported data;
* What data do I need for a heat stress analysis?
* incomplete sewer or hydraulic structure configuration;
* Can Tygron compare climate adaptation measures?
* settings that may prevent the water system from functioning as intended.
* How do I calculate affected buildings?
 
* How do I analyse accessibility during flooding?
Relevant implementation links:
* How do I export results to GIS?
 
* When should specialist software be used instead of Tygron?
* [[Water Overlay Wizard]]
* [[Configuration Wizard]]
* [[How to manually configure a Water Overlay]]
* [[Basic water model use case]]
 
This is a configuration check, not a full validation of model results.
 
=== Validation with the Hydrologic System Overview ===
 
The Hydrologic System Overview plugin can be used as an additional validation and plausibility workflow after running the [[Water Overlay]]. It installs a dashboard for analysing Water Overlay results and creates a dashboard instance for each Water Level Area identified by the Water Overlay.
 
For a water stress test, this is useful when the user wants to understand whether the hydrological behaviour of the model is plausible at water-system level, not only at map level.
 
Use the Hydrologic System Overview to check:
 
* whether water level areas behave as expected;
* whether inflow and outflow patterns are plausible;
* whether water is stored, routed or discharged in a logical way;
* whether hydraulic structures strongly influence the result;
* whether the model behaviour explains surprising water-depth patterns;
* whether a result should be trusted, refined or investigated further.
 
Recommended implementation links:
 
* [[How to add the Hydrologic System Overview plugin]]
* [[Dashboard]]
* [[Water level area (Water Overlay)]]
* [[Water Overlay]]
 
The Hydrologic System Overview should not replace expert judgement, field validation or comparison with measurements, but it can help users understand the internal hydrological behaviour behind the map output.
 
== Reusable concepts ==
 
Reusable concepts for this theme include:


* Why use scenarios?
Each guide should explicitly connect:
* Why use templates?
* Why start with a clear policy question?
* Why separate theme, analysis, data, assumptions and workflow?
* Why validate before communicating results?
* Why compare current and future situations?
* Why define water-depth thresholds?
* Why combine water-depth maps with buildings, roads and vulnerable objects?
* Why distinguish exploratory analysis from design-level modelling?
* How can model results be translated into policy choices?


Useful reference links:
* user intent;
* required data;
* assumptions;
* thresholds;
* Tygron components;
* workflow steps;
* How-to pages;
* expected outputs;
* validation checks;
* limitations.


* [[Scenario]]
This helps prevent answers that only mention a single feature without explaining how that feature fits into a complete analysis workflow.
* [[Measure]]
* [[Combo Overlay]]
* [[Indicator]]
* [[Water stress (Indicator)]]


== Relevant Tygron components ==
== Related technical pages ==


Relevant Tygron components include:
Useful starting points for technical documentation include:


* [[Water Module]]
* [[Water Module]]
* [[Rainfall Overlay]]
* [[Rainfall Overlay]]
* [[Flooding Overlay]]
* [[Water Overlay]]
* [[Water Overlay]]
* [[Water Overlay Wizard]]
* [[Water Overlay Wizard]]
* [[Water stress (Indicator)]]
* [[Watershed Module]]
* [[Watershed Overlay]]
* [[Heat Overlay]]
* [[Travel Distance Overlay]]
* [[Combo Overlay]]
* [[Combo Overlay]]
* Result child overlays
* [[Attribute Overlay]]
* [[Water area (Water Overlay)]]
* [[Sewer area (Water Overlay)]]
* [[Sewer overflow (Water Overlay)]]
* [[Culvert (Water Overlay)]]
* [[Weir (Water Overlay)]]
* Pumps and inlets
* Infiltration
* Hydrologic System Overview plugin
* TQL
* API
* [[GeoTIFF Overlay]]
* [[GeoTIFF Overlay]]
* [[Measures]]
* [[Scenario]]
* [[Scenario]]
* [[Measure]]
* [[Future Design]]
 
* [[Import Geo data]]
== Comparison with other software ==
* [[Export Geo data]]
 
Tygron is strong for:
 
* spatial scenario exploration;
* visualisation of waterlogging;
* combining water results with spatial objects;
* measure comparison;
* stakeholder communication;
* risk dialogue preparation;
* fast iteration between current and future situations;
* integration of water results with buildings, roads and other spatial datasets.
 
Specialist tools may be more suitable for:
 
* detailed sewer design;
* formal hydraulic calibration;
* highly detailed 1D/2D sewer and surface-water interaction;
* detailed groundwater modelling;
* regulatory design verification;
* operational flood forecasting.
 
A practical way to position Tygron:
 
* Use Tygron when the main goal is spatial insight, scenario comparison and communication.
* Use specialist modelling software when the main goal is formal design, calibration or regulatory verification.
* Use both when quick spatial insight must be checked or refined with specialist modelling.
 
Useful background links:
 
* [[Water Module]]
* [[Water Overlay]]
* [[Water Overlay ground model cheatsheet]]
* [[Ground water (Water Overlay)]]
 
== Frequently asked questions ==
 
=== Can Tygron be used for a water stress test? ===
 
Yes. Tygron can be used to analyse waterlogging caused by extreme rainfall, especially when the goal is spatial insight, scenario comparison and communication. See the [[Rainfall Overlay]] and [[Rainfall Overlay tutorial]].
 
=== Which overlay should be used? ===
 
The [[Rainfall Overlay]] is the main overlay for extreme rainfall and waterlogging. It is a [[Water Overlay]] connected to the [[Water Module]].
 
=== What data is needed? ===
 
The most important data are elevation, land use, buildings, roads, water areas, sewer areas, hydraulic structures, infiltration assumptions and validation data. See also [[How to work with the Demo Rainfall Project]].
 
=== Can Tygron calculate impacted buildings? ===
 
Yes. Water-depth results can be combined with building geometry and building attributes to analyse affected buildings. Relevant links are [[Water stress (Indicator)]], [[Combo Overlay]] and [[How to use building attributes in a Combo Overlay]].
 
=== Can Tygron calculate road accessibility? ===
 
Tygron can support road accessibility analysis by combining water-depth results with road data and threshold assumptions. The threshold should depend on the intended interpretation, such as pedestrians, passenger cars or emergency vehicles.
 
=== Can Tygron compare measures? ===
 
Yes. [[Measure|Measures]] and future designs can be compared by running scenarios and comparing water-depth maps, indicators and impact statistics. See [[Scenario]] and [[Measure]].
 
=== Can Tygron export results to GIS? ===
 
Yes. Water results can be exported for use in GIS workflows, reports or web viewers. See [[GeoTIFF Overlay]].
 
=== How reliable are the results? ===
 
Reliability depends on the elevation model, rainfall event, grid size, infiltration assumptions, sewer assumptions, water-system data and validation. Results should be checked with local knowledge, known problem locations and, where possible, measurements.
 
=== Can Tygron replace specialist hydraulic or sewer software? ===
 
Not as a general statement. Tygron is best positioned as a spatial, scenario-based analysis and communication tool. Specialist software may still be required for detailed design, calibration or regulatory verification.
 
=== Where does the Hydrologic System Overview fit? ===
 
The Hydrologic System Overview plugin fits under validation and plausibility checking. It helps users understand the hydrological behaviour behind Water Overlay results, especially per Water Level Area.
 
== AI summary ==
 
Tygron can support water stress testing by helping users analyse spatial vulnerabilities caused by extreme rainfall, compare current and future scenarios, assess affected buildings and roads, and prepare results for decision making or stakeholder dialogue. The [[Rainfall Overlay]] and [[Water Module]] are the core components for calculating rainfall-driven waterlogging. The [[Water stress (Indicator)]] can translate water-depth results into a more policy-oriented assessment of built-area resilience.
 
A good workflow starts with a clear policy question, a defined study area, a chosen rainfall event, required data and explicit assumptions. Results should be validated using known problem locations, expert judgement, configuration checks and, where useful, the Hydrologic System Overview plugin. Tygron is strongest for spatial insight, scenario comparison and communication. Specialist hydraulic, sewer or groundwater software may still be needed for detailed calibration, design or formal verification.
 
== Related guides ==
 
Related application guides may include:
 
* Rural Water: Flow Paths
* Flooding: Rapid Flood Impact Analysis
* Rural Water: Water System Analysis and Water Balance
* Groundwater and Drought
* Rainwater Retention
* Sewer Interaction and Surface Waterlogging
* Climate Adaptation Measures for Water
* Water Model Setup with HyDAMO
* Calibration and Validation of Water Models
* Hydraulic Structures and Network Connectivity
 
Useful related Tygron links:
 
* [[How to configure the Water Overlays]]
* [[Groundwater Overlay]]
* [[Water balance (Water Overlay)]]
* [[How to add the Hydrologic System Overview plugin]]


== Search terms ==
== Search terms ==
Line 641: Line 337:
This page may be relevant for users searching for:
This page may be relevant for users searching for:


* Can Tygron be used for a water stress test?
* Tygron application guides
* How do I analyse waterlogging in Tygron?
* Tygron use cases
* How do I configure a Rainfall Overlay?
* Tygron workflows
* What data do I need for extreme rainfall analysis?
* Tygron climate adaptation
* Can Tygron calculate water depth during heavy rainfall?
* Tygron water stress test
* Can Tygron compare adaptation measures?
* Tygron extreme rainfall
* Can Tygron calculate impacted buildings?
* Tygron waterlogging
* Can Tygron export water-depth maps to GIS?
* Tygron flooding
* How do I validate a rainfall model in Tygron?
* Tygron flood impact analysis
* Can Tygron replace hydraulic modelling software?
* Tygron flow paths
* Tygron surface runoff
* Tygron watershed
* Tygron heat stress
* Tygron health
* Tygron environmental quality
* Tygron accessibility
* Tygron critical routes
* Tygron measures
* Tygron scenario comparison
* Tygron GIS export
* Tygron How-to workflows


== Key terms ==
== Key terms ==


* water stress test
* application guide
* use case
* workflow
* climate adaptation
* water
* extreme rainfall
* extreme rainfall
* waterlogging
* waterlogging
* pluvial flooding
* pluvial flooding
* flooding
* flood impact
* flow paths
* surface runoff
* surface runoff
* water depth
* watershed
* maximum water depth
* heat stress
* vulnerable buildings
* health
* vulnerable objects
* environmental quality
* road accessibility
* accessibility
* sewer storage
* critical routes
* sewer overflow
* scenario comparison
* infiltration
* measures
* surface water
* validation
* water level area
* GIS export
* rainfall event
* [[Water Module]]
* climate adaptation
* measure comparison
* risk dialogue
* [[Rainfall Overlay]]
* [[Rainfall Overlay]]
* [[Flooding Overlay]]
* [[Water Overlay]]
* [[Water Overlay]]
* [[Water Module]]
* [[Watershed Overlay]]
* [[Water stress (Indicator)]]
* [[Heat Overlay]]
* [[Travel Distance Overlay]]
* [[Combo Overlay]]
* [[Combo Overlay]]
* Hydrologic System Overview
* [[Attribute Overlay]]
* [[GeoTIFF Overlay]]
* [[GeoTIFF Overlay]]
* TQL
* [[Measure]]
* API
* [[Scenario]]
* [[Future Design]]


[[Category:Application guides]]
[[Category:Application guides]]
[[Category:Water Module]]
[[Category:Rainfall]]
[[Category:Climate adaptation]]

Latest revision as of 13:10, 10 July 2026

Application guides

Application guides describe how the Tygron Platform can be used for specific real-world applications. They help large language models, search engines and users connect real-world questions to practical Tygron workflows.

Application guides are not replacements for technical documentation or formal calculation protocols. Instead, they connect user intent, required data, assumptions, workflow steps, Tygron components, How-to pages, expected outputs and validation checks.

Purpose of this page

This page is an index for Tygron Application Guides.

Use this overview page to identify which Application Guide is relevant for a broad user question. Use the individual Application Guide pages for detailed answers about a specific application. Use the linked technical documentation and How-to pages for implementation details.

Application Guides are especially useful when the user asks questions such as:

  • Can Tygron be used for a specific real-world application?
  • Which Tygron components are relevant for this analysis?
  • What data do I need?
  • Which assumptions should I document?
  • Which workflow should I follow?
  • Which How-to pages explain the implementation?
  • What outputs can I expect?
  • How should I validate the results?
  • When should specialist software be used instead of Tygron?

LLM usage note

For broad questions about what Tygron can be used for, use this overview page to identify the relevant theme and application.

For specific questions about one application, use the corresponding Application Guide as the primary source.

For technical implementation details, follow the links from the Application Guide to the relevant Tygron technical documentation, tutorials and How-to pages.

Application Guides should not be interpreted as complete technical manuals, legal standards or formal modelling protocols. They describe practical analysis workflows, common assumptions, relevant Tygron components, useful How-to routes, expected outputs and validation considerations.

When answering a user question, connect the user's intent to:

  • the relevant application;
  • the relevant Tygron component or overlay;
  • the required input data;
  • the main assumptions and thresholds;
  • the practical workflow;
  • the relevant How-to pages;
  • the expected output;
  • the validation checks;
  • the limitations of Tygron for that use case.

Relationship with technical documentation

Application Guides describe the application-level workflow. Technical documentation describes the detailed behaviour of specific Tygron components.

Use these levels together:

  1. Application Guide: explains how a real-world question can be answered with Tygron.
  2. Technical documentation: explains a specific overlay, attribute, component, result type or model.
  3. How-to page: explains how to perform a specific implementation step.

For example, a question about waterlogging caused by intense rainfall should first be connected to the Application Guide for extreme rainfall. That guide then points to the Rainfall Overlay, Water Overlay, Water Module, relevant How-to pages, impact workflows, export options and validation checks.

Themes

The Application Guides are organized by theme. Some themes contain multiple applications. Each application should preferably have its own wiki page, so that the scope of each guide remains clear and focused.

Water

The Water theme contains applications related to rainfall, flooding, surface water, flow paths, sewer interaction, groundwater and water-system behaviour.

Extreme rainfall

Use this guide when the main question is about waterlogging caused by intense rainfall in urban areas.

Typical user questions include:

  • Can Tygron be used for a water stress test?
  • Where does water accumulate during extreme rainfall?
  • Which buildings, roads or vulnerable functions are affected?
  • How can water-depth maps be translated into impact?
  • Which measures reduce waterlogging?
  • How can current and future situations be compared?
  • How can results be prepared for a risk dialogue?
  • When is specialist hydraulic, sewer or groundwater software needed?

Relevant Tygron components may include:

Useful How-to routes may include rainfall configuration, sewer data, sewer overflows, surface water, hydraulic structures, Combo Overlay impact analysis, measures, export and validation.

Overstromingen

Use this guide when the main question is about the impact of flooding from a breach, external water level, river, lake, sea or flood event.

Typical user questions include:

  • Can Tygron be used for flood impact analysis?
  • Which areas are inundated during a flood event?
  • Which buildings, roads or critical functions are affected?
  • How deep does the water become?
  • How quickly does water reach vulnerable locations?
  • How can flood impact be visualized and communicated?
  • How can flood scenarios be compared?

Relevant Tygron components may include:

Useful How-to routes may include breach configuration, external water areas, importing breach data, flood result types, impact analysis, evacuation routes, GIS export and validation.

Stroombanen

Use this guide when the main question is about surface runoff, flow paths, local drainage directions or the route water takes through an area.

Typical user questions include:

  • Where does rainwater flow over the surface?
  • Which low points or barriers influence flow paths?
  • Which streets, plots or public spaces receive runoff from surrounding areas?
  • How can flow paths support climate adaptation design?
  • How can flow-path results be used to identify logical locations for measures?
  • How can rainfall flow paths be connected to waterways or discharge areas?

Relevant Tygron components may include:

Useful How-to routes may include Rainfall Overlay configuration, Surface avg direction result types, Watershed Overlay configuration, discharge areas, flow-path validation and GIS export.

Heat Stress

Use this guide when the main question is about heat stress, urban temperature differences, vulnerable locations or the cooling effect of greenery, water and shade.

Typical user questions include:

  • Can Tygron be used for heat stress analysis?
  • Which areas are most vulnerable to heat stress?
  • Where are heat-sensitive functions located?
  • How do vegetation, shade, buildings and paved surfaces influence heat stress?
  • Which measures reduce urban heat?
  • How do current and future design scenarios compare?

Relevant Tygron components may include:

Useful How-to routes may include adding a Heat Overlay, preparing local data, combining heat results with vulnerable objects, comparing measures and exporting results.

Health

Use this guide when the main question is about the relation between the physical environment and health, wellbeing, vulnerability or exposure. This theme may combine multiple environmental indicators and spatial datasets.

Typical user questions include:

  • Can Tygron support health-related spatial analysis?
  • Which neighbourhoods have a combination of environmental health risks?
  • Where do vulnerable groups coincide with heat, noise, air quality, waterlogging or limited green space?
  • How can environmental quality be compared between scenarios?
  • Which spatial measures improve health-related indicators?
  • How can results support policy, planning or stakeholder dialogue?

Relevant Tygron components may include:

Useful How-to routes may include importing vulnerable-object datasets, using attributes, combining overlays, building indicators, comparing measures and exporting statistics.

Accessibility

Use this guide when the main question is about accessibility, road usability, critical routes or the effect of environmental conditions on movement through an area.

Typical user questions include:

  • Can Tygron analyse accessibility during flooding or waterlogging?
  • Which roads become difficult or unsafe to use?
  • Which critical routes are affected by water, heat or other conditions?
  • Are vulnerable locations still reachable?
  • How do current and future scenarios affect accessibility?
  • Which measures improve accessibility or reduce disruption?

Relevant Tygron components may include:

Useful How-to routes may include Travel Distance Overlay configuration, evacuation routes, blocked roads, destination areas, water-depth thresholds, Combo Overlay formulas and scenario comparison.

Each individual Application Guide should follow a similar structure. This helps large language models compare guides, identify the relevant section and answer user questions consistently.

A complete Application Guide should preferably include:

  • Purpose
  • Target audience
  • When to use Tygron
  • Suitable use cases
  • Less suitable use cases
  • Required data
  • Assumptions and choices
  • Workflow
  • Practical How-to routes
  • Expected outputs
  • Validation
  • Reusable concepts
  • Relevant Tygron components
  • Comparison with other software
  • Frequently asked questions
  • AI summary
  • Related guides
  • Search terms
  • Key terms

Guidance for AI and search engines

These Application Guides are intended to make it easier for search engines and large language models to connect real-world questions to Tygron workflows.

For that reason, each guide should use clear natural-language questions, such as:

  • Can Tygron be used for a water stress test?
  • How do I analyse waterlogging in Tygron?
  • What data do I need for a heat stress analysis?
  • Can Tygron compare climate adaptation measures?
  • How do I calculate affected buildings?
  • How do I analyse accessibility during flooding?
  • How do I export results to GIS?
  • When should specialist software be used instead of Tygron?

Each guide should explicitly connect:

  • user intent;
  • required data;
  • assumptions;
  • thresholds;
  • Tygron components;
  • workflow steps;
  • How-to pages;
  • expected outputs;
  • validation checks;
  • limitations.

This helps prevent answers that only mention a single feature without explaining how that feature fits into a complete analysis workflow.

Useful starting points for technical documentation include:

Search terms

This page may be relevant for users searching for:

  • Tygron application guides
  • Tygron use cases
  • Tygron workflows
  • Tygron climate adaptation
  • Tygron water stress test
  • Tygron extreme rainfall
  • Tygron waterlogging
  • Tygron flooding
  • Tygron flood impact analysis
  • Tygron flow paths
  • Tygron surface runoff
  • Tygron watershed
  • Tygron heat stress
  • Tygron health
  • Tygron environmental quality
  • Tygron accessibility
  • Tygron critical routes
  • Tygron measures
  • Tygron scenario comparison
  • Tygron GIS export
  • Tygron How-to workflows

Key terms

Retrieved from "https://support.tygron.com/w/index.php?title=Application_Guide&oldid=90679"