Application Guide: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
← Older editNewer edit →
Ward@tygron.nl (talk | contribs)
Tygron
22 edits
Ward@tygron.nl (talk | contribs)
Tygron
22 edits
No edit summary
Ward@tygron.nl (talk | contribs)
Tygron
22 edits
No edit summary
Line 1: Line 1:
= Application guides =
= Application guides =


Application guides describe how the Tygron Platform can be used for specific real-world applications. They help users translate policy questions, planning questions or analysis questions into practical Tygron workflows.
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. Instead, they connect user questions, required data, assumptions, workflows, relevant Tygron components and implementation pages.
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.


Each guide should help answer:
== Purpose of this page ==


* what user question the application addresses;
This page is an index for Tygron Application Guides.
* when Tygron is suitable;
* when Tygron is less suitable;
* what data is needed;
* which assumptions must be documented;
* which Tygron components are relevant;
* which workflows and How-to pages should be used;
* what outputs can be expected;
* how results should be validated;
* which related guides or technical pages may be relevant.


== How to use these 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.


Use an Application Guide when the starting point is a real-world problem or policy question, rather than a single Tygron feature.
Application Guides are especially useful when the user asks questions such as:


For example:
* 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.


* use an Application Guide to understand how Tygron can support a water stress test, heat stress analysis or accessibility assessment;
When answering a user question, connect the user's intent to:
* use technical documentation to understand the details of a specific overlay, component, attribute or setting;
* use How-to pages when the user needs step-by-step instructions for a specific task.


The Application Guides are intended to bridge these three levels:
* 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.


# the real-world question;
== Relationship with technical documentation ==
# the Tygron analysis workflow;
 
# the relevant technical documentation and How-to pages.
Application Guides describe the application-level workflow. Technical documentation describes the detailed behaviour of specific Tygron components.
 
Use these levels together:
 
# 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.
 
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 ==
== Themes ==
Line 46: Line 69:
* [[Application guide: Water stress test for extreme rainfall]]
* [[Application guide: Water stress test for extreme rainfall]]


Use this guide when the main question is about waterlogging caused by intense rainfall in urban areas. Typical questions include:
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?
* Where does water accumulate during extreme rainfall?
* Which buildings, roads or vulnerable functions are affected?
* Which buildings, roads or vulnerable functions are affected?
* How can water-depth maps be translated into impact?
* How can water-depth maps be translated into impact?
* Which measures reduce waterlogging?
* Which measures reduce waterlogging?
* How can current and future situations be compared?
* How can results be prepared for a risk dialogue?
* How can results be prepared for a risk dialogue?
* When is specialist hydraulic, sewer or groundwater software needed?


Relevant Tygron components may include:
Relevant Tygron components may include:
Line 61: Line 89:
* [[Water Overlay Wizard]]
* [[Water Overlay Wizard]]
* [[Water stress (Indicator)]]
* [[Water stress (Indicator)]]
* [[Water stress result type (Water Overlay)]]
* [[Combo Overlay]]
* [[Combo Overlay]]
* [[Attribute Overlay]]
* [[GeoTIFF Overlay]]
* [[Sewer area (Water Overlay)]]
* [[Sewer area (Water Overlay)]]
* [[Sewer overflow (Water Overlay)]]
* [[Sewer overflow (Water Overlay)]]
* [[Water area (Water Overlay)]]
* [[Culvert (Water Overlay)]]
* [[Culvert (Water Overlay)]]
* [[Weir (Water Overlay)]]
* [[Weir (Water Overlay)]]
* [[Weather (Water Overlay)]]
* [[Rain area (Water Overlay)]]


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


* [[Application guide: Flood impact analysis]]
=== Overstromingen ===


Use this guide when the main question is about the impact of flooding from a breach, external water level or flood event. Typical questions include:
* [[Application guide: Flood impact analysis]] ''(planned)''


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 areas are inundated during a flood event?
* Which buildings, roads or critical functions are affected?
* Which buildings, roads or critical functions are affected?
Line 78: Line 117:
* How quickly does water reach vulnerable locations?
* How quickly does water reach vulnerable locations?
* How can flood impact be visualized and communicated?
* How can flood impact be visualized and communicated?
* How can flood scenarios be compared?


Relevant Tygron components may include:
Relevant Tygron components may include:
Line 89: Line 129:
* [[Attribute Overlay]]
* [[Attribute Overlay]]
* [[GeoTIFF Overlay]]
* [[GeoTIFF Overlay]]
* [[Travel Distance Overlay]]
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 ===


=== Surface runoff pathways ===
* [[Application guide: Flow paths and surface runoff]] ''(planned)''


* [[Application guide: Flow paths and surface runoff]]
Use this guide when the main question is about surface runoff, flow paths, local drainage directions or the route water takes through an area.


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 questions include:
Typical user questions include:


* Where does rainwater flow over the surface?
* Where does rainwater flow over the surface?
Line 101: Line 146:
* How can flow paths support climate adaptation design?
* How can flow paths support climate adaptation design?
* How can flow-path results be used to identify logical locations for measures?
* 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:
Relevant Tygron components may include:
Line 107: Line 153:
* [[Water Overlay]]
* [[Water Overlay]]
* [[Water Module]]
* [[Water Module]]
* [[Watershed Overlay]]
* [[Watershed Module]]
* [[Surface avg direction result type (Water Overlay)]]
* [[Elevation model]]
* [[Elevation model]]
* [[Terrain]]
* [[Terrain]]
Line 112: Line 161:
* [[GeoTIFF Overlay]]
* [[GeoTIFF Overlay]]


== Heat ==
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.
 
== Hitte ==


* [[Application guide: Urban heat stress]]
* [[Application guide: Urban heat stress]] ''(planned)''


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 questions include:
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?
* Which areas are most vulnerable to heat stress?
* Where are heat-sensitive functions located?
* Where are heat-sensitive functions located?
Line 135: Line 189:
* [[Scenario]]
* [[Scenario]]
* [[Combo Overlay]]
* [[Combo Overlay]]
* [[Attribute Overlay]]
Useful How-to routes may include adding a Heat Overlay, preparing local data, combining heat results with vulnerable objects, comparing measures and exporting results.
== Gezondheid ==


== Health ==
* [[Application guide: Health and environmental quality]] ''(planned)''


* [[Application guide: Health and environmental quality]]
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.


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


* Can Tygron support health-related spatial analysis?
* Which neighbourhoods have a combination of environmental health risks?
* Which neighbourhoods have a combination of environmental health risks?
* Where do vulnerable groups coincide with heat, noise, air quality or limited green space?
* Where do vulnerable groups coincide with heat, noise, air quality, waterlogging or limited green space?
* How can environmental quality be compared between scenarios?
* How can environmental quality be compared between scenarios?
* Which spatial measures improve health-related indicators?
* Which spatial measures improve health-related indicators?
Line 159: Line 219:
* [[Measures]]
* [[Measures]]
* [[Scenario]]
* [[Scenario]]
* [[Heat Overlay]]
* [[Rainfall Overlay]]


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


* [[Application guide: Accessibility and critical routes]]
== Bereikbaarheid ==


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 questions include:
* [[Application guide: Accessibility and critical routes]] ''(planned)''


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 roads become difficult or unsafe to use?
* Which critical routes are affected by water, heat or other conditions?
* Which critical routes are affected by water, heat or other conditions?
Line 179: Line 246:
* [[Attribute Overlay]]
* [[Attribute Overlay]]
* [[Combo Overlay]]
* [[Combo Overlay]]
* [[Travel Distance Overlay]]
* [[Distance Overlay]]
* [[Rainfall Overlay]]
* [[Rainfall Overlay]]
* [[Water stress result type (Water Overlay)]]
* [[Water stress result type (Water Overlay)]]
Line 184: Line 253:
* [[Scenario]]
* [[Scenario]]


== Structure of an Application Guide ==
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 Application Guide follows a similar structure. This helps users, search engines and large language models understand how a real-world question is connected to Tygron workflows, relevant components, How-to pages and expected outputs.
== Recommended structure for individual Application Guides ==


A typical Application Guide includes:
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.


* purpose and target audience;
A complete Application Guide should preferably include:
* suitable and less suitable use cases;
 
* required data;
* Purpose
* assumptions and choices;
* Target audience
* workflow steps;
* When to use Tygron
* practical How-to routes;
* Suitable use cases
* expected outputs;
* Less suitable use cases
* validation checks;
* Required data
* relevant Tygron components;
* Assumptions and choices
* frequently asked questions;
* Workflow
* related guides, search terms and key terms.
* 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 ==
== Guidance for AI and search engines ==


These Application Guides are intended to make it easier for users, search engines and large language models to connect real-world questions to Tygron workflows.
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:
For that reason, each guide should use clear natural-language questions, such as:
Line 213: Line 292:
* Can Tygron compare climate adaptation measures?
* Can Tygron compare climate adaptation measures?
* How do I calculate affected buildings?
* How do I calculate affected buildings?
* How do I analyse accessibility during flooding?
* How do I export results to GIS?
* How do I export results to GIS?
* When should specialist software be used instead of Tygron?
* When should specialist software be used instead of Tygron?


Each guide should also explicitly connect:
Each guide should explicitly connect:


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


This helps prevent answers that only mention a single feature without explaining how that feature fits into a complete analysis workflow.
This helps prevent answers that only mention a single feature without explaining how that feature fits into a complete analysis workflow.
Line 235: Line 317:
* [[Water Module]]
* [[Water Module]]
* [[Rainfall Overlay]]
* [[Rainfall Overlay]]
* [[Flooding Overlay]]
* [[Water Overlay]]
* [[Water Overlay]]
* [[Water Overlay Wizard]]
* [[Water Overlay Wizard]]
* [[Watershed Module]]
* [[Watershed Overlay]]
* [[Heat Overlay]]
* [[Travel Distance Overlay]]
* [[Combo Overlay]]
* [[Combo Overlay]]
* [[Attribute Overlay]]
* [[Attribute Overlay]]
Line 256: Line 343:
* Tygron water stress test
* Tygron water stress test
* Tygron extreme rainfall
* Tygron extreme rainfall
* Tygron waterlogging
* Tygron flooding
* Tygron flooding
* Tygron flood impact analysis
* Tygron flow paths
* Tygron flow paths
* Tygron surface runoff
* Tygron watershed
* Tygron heat stress
* Tygron heat stress
* Tygron health
* Tygron health
* Tygron environmental quality
* Tygron accessibility
* Tygron accessibility
* Tygron critical routes
* Tygron measures
* Tygron measures
* Tygron scenario comparison
* Tygron scenario comparison
Line 275: Line 368:
* extreme rainfall
* extreme rainfall
* waterlogging
* waterlogging
* pluvial flooding
* flooding
* flooding
* flood impact
* flow paths
* flow paths
* surface runoff
* surface runoff
* watershed
* heat stress
* heat stress
* health
* health
* environmental quality
* accessibility
* accessibility
* critical routes
* critical routes
Line 288: Line 385:
* [[Water Module]]
* [[Water Module]]
* [[Rainfall Overlay]]
* [[Rainfall Overlay]]
* [[Flooding Overlay]]
* [[Water Overlay]]
* [[Water Overlay]]
* [[Watershed Overlay]]
* [[Heat Overlay]]
* [[Travel Distance Overlay]]
* [[Combo Overlay]]
* [[Combo Overlay]]
* [[Attribute Overlay]]
* [[Attribute Overlay]]

Revision as of 15:58, 7 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.

Hitte

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.

Gezondheid

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.

Bereikbaarheid

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=89809"