Zone: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 28: Line 28:


{{article end
{{article end
|notes=*{{SourcedItem}}
|howtos=
|howtos=
* [[How to add and remove a Zone]]
* [[How to add and remove a Zone]]
Line 34: Line 35:
* [[Zoning permit panel]]
* [[Zoning permit panel]]
|api=*[[Api session items zones]]
|api=*[[Api session items zones]]
*[[Api session event editor zoning]]
}}
}}


{{Template:Editor current situation nav}}
{{Template:Editor current situation nav}}

Latest revision as of 12:22, 13 May 2026

Zones in comparison to Areas, Neighborhoods and Plots

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:


Notes

  • Zone is a Sourced Item, which means its records which Sources created it and which Sources changed any of its properties.

How-to's

See also

API Endpoints