Zone: Difference between revisions
No edit summary Tag: Manual revert |
No edit summary |
||
| Line 1: | Line 1: | ||
Zones in the {{software}} are spatial areas that can restrict, and provide feedback on, [[action]]s performed by [[stakeholder]]s. Each zone is assigned to a stakeholder; that stakeholder is the ''permitter''. | Zones in the {{software}} are spatial areas that can restrict, and provide feedback on, [[action]]s performed by [[stakeholder]]s. Each zone is assigned to a stakeholder; that stakeholder is the ''permitter''. | ||
Zones can be grouped together to form a hierarchical zoning plan, each with specific requirements to which a new action must conform. If, during a [[session]], an action does not conform to the zoning plan, a [[popup]] will appear, indicating a conflict with the zoning plan. In order to resolve the conflict with the zoning plan, either: | Zones can be grouped together to form a hierarchical zoning plan, each with specific requirements to which a new action must conform. If, during a [[session]], an action does not conform to the zoning plan, a [[permission popup]] will appear, indicating a conflict with the zoning plan. In order to resolve the conflict with the zoning plan, either: | ||
* the action has to be adjusted. | * the action has to be adjusted. | ||
* the zoning plan is changed by the permitter. | * the zoning plan is changed by the permitter. | ||
| Line 10: | Line 10: | ||
* An [[excel]] file. The excel file can request TQL statements to calculate a permittance score, determining whether a certain action can be permitted or not. Additionally, it can provide information on why that action was not permitted. | * An [[excel]] file. The excel file can request TQL statements to calculate a permittance score, determining whether a certain action can be permitted or not. Additionally, it can provide information on why that action was not permitted. | ||
The project can also be configured to disable the permission popup, which will result in the following: | |||
* Actions will not be restricted by the zoning plan. | |||
* Potential conflicts with the zoning plan(s) are no longer calculated and reported to the stakeholders. | |||
However, zones can still be used in other calculated if needed, with feedback shown in custom-made [[panel]]s. | |||
An example of a Stakeholder placing a new Sports Center in a Zone that does not allow it: | |||
<gallery mode="packed"> | <gallery mode="packed"> | ||
File:zoning_conflict.png|A zone reports a conflict with the planned [[building]], because its [[Function Category]] is not allowed. | File:zoning_conflict.png|A zone reports a conflict with the planned [[building]], because its [[Function Category]] is not allowed. | ||
Revision as of 12:44, 7 October 2022
Zones in the Tygron Platform are spatial areas that can restrict, and provide feedback on, actions performed by stakeholders. Each zone is assigned to a stakeholder; that stakeholder is the permitter.
Zones can be grouped together to form a hierarchical zoning plan, each with specific requirements to which a new action must conform. If, during a session, an action does not conform to the zoning plan, a permission popup will appear, indicating a conflict with the zoning plan. In order to resolve the conflict with the zoning plan, either:
- the action has to be adjusted.
- the zoning plan is changed by the permitter.
- the action has to be reverted.
Zones can determine if an action create a conflict with the current zoning plan in two ways:
- A set of allowed Function Categories, used to verify planned Buildings.
- An excel file. The excel file can request TQL statements to calculate a permittance score, determining whether a certain action can be permitted or not. Additionally, it can provide information on why that action was not permitted.
The project can also be configured to disable the permission popup, which will result in the following:
- Actions will not be restricted by the zoning plan.
- Potential conflicts with the zoning plan(s) are no longer calculated and reported to the stakeholders.
However, zones can still be used in other calculated if needed, with feedback shown in custom-made panels.
An example of a Stakeholder placing a new Sports Center in a Zone that does not allow it:
A zone reports a conflict with the planned building, because its Function Category is not allowed.
Denying the action results in a message to revert the action.
The permitter decides to adjust the zoning plan.
The action now is in accordance with the zoning plan.
How-to's
Current Situation
- Buildings • Terrains • Administrative • Areas • Networks • Overlays • Indicators • Panels • Globals • Queries • Geo Import
- Buildings
- Function • Function Override • Traffic Units
- Terrain
- Height sector • Elevation model • Elevation GeoTIFF • Elevation Grid Overlay • Ground Price • Terrain Type • Terrain Type Override
- Administrative
- Net Cluster • Net Function • Net Line • Net Load • Net Node • Net Setting
- Editor