Project: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
← Older edit
Frank@tygron.nl (talk | contribs)
Tygron, Tygron_admin, Bureaucrats, Interface administrators, Administrators
46,429 edits
mNo edit summary
No edit summary
 
(31 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{learned|what a Project is|how to best regard Project data in the {{software}}}}
{{stub}}
A project in general terms is an undertaking or collection of processes and activities intended to complete some predetermined goal. In computing, "project" is additionally often used to refer to a type of collection(s) of data, brought together to perform actions such as the creation of new data, or the analysis and correlation of existing data.
==Tygron projects==
In the {{software}}, a Project refers to the collection of data relevant to a specific area and use-case. Each project consists of data such as:
In the {{software}}, a Project refers to the collection of data relevant to a specific area and use-case. Each project consists of data such as:
* [[Geographical location]]
* [[Geographical location]]
* Spatial features, such as the [[terrain height]], the [[Terrain|Terrain type]]s, and present [[Construction]]s.
* Spatial features, such as an [[elevation model]], [[Terrain Type]]s, and [[Building]]s.
* Relevant [[stakeholder]]s, and their available [[Action]]s.
* Relevant [[stakeholder]]s, and their available [[Action]]s.
* Calculation models such as [[Indicator]]s, as well as [[Overlay]]s, calculated or otherwise
* Calculation models such as [[Indicator]]s, as well as [[Overlay]]s, calculated or otherwise
In most Projects, this data would mirror a real-world situation, and as such would represent the conditions and constraints of all simulations and interactions which a user may perform.


==Inert Project data and live Sessions==
==Interacting with a Project==
All Projects are stored by the {{software}} as static data. As a user, it is possible to interact with a Project through a Session. When a Session of any kind is started, the {{software}} reads the Project data and uses it to create a live environment, accessible to the user. In a Session, the user can interact with the data. When the Session is closed, all the data in the Session is discarded. If the data has not explicitly been saved, the original Project is unaffected, and again starting a Session based on the same Project will yield the same initial data as the previous Session started with.
All Projects are stored by the {{software}} as static data. As a user, it is possible to interact with a Project by starting a [[Session]]. When a [[Session#Session types|Session of any kind]] is started, the {{software}} reads the Project data and uses it to create a live session, accessible to the user and [[Project#Accessibility|optionally other users within his/her domain]]. In a Session, the user can interact with the data. When the Session is closed, all the data in the Session is discarded. If changes are not saved, the original Project remains unaffected; restarting a session restores the original data.
 
==Accessibility==
Access and adjustment rights to a project can be configured as followed:
* '''Project owner''': The user who created the project and has full control over its settings and accessibility.
* '''Domain users''': Whether users within your domain are allowed to access your project.
* '''{{software}} Support''': whether you allow {{software}} support employees access your project to provide support or identify issues encountered in your project.
These rights allow you to either start a new session or join an existing live session.
There are three options for adjustment:
* '''Write''': Write access to the project. These users are allowed to start and save during a project session.
* '''Read''': Read access to the project. Users with this accessibility option are not allowed to save the project. They can adjust the project when in a live session that the owner started with write access. When the owner saves the project data, the adjustments made by read-access users will also be included in the project.
* '''None''': No access to the project. Note that a project owner always has access to a project.
 
Only one session can edit a project at a time. To have multiple editing sessions, save the project under a new name to create a separate entity.
 
==Template Project==
Projects can be designated as "Template". [[Template Project|Templates]] can be used as a blueprint to create new Projects. This is done by creating a copy of the Template Project, removing all geographical data from it, and allowing the user to select a new location for the new Project.
 
{{article end
|seealso=
*[[New Project Wizard]]
*[[Template Project]]
|howtos=
*[[How to create a new Project]]
*[[How to start the editor with an Empty Project]]
*[[How to create a Template Project]]
*[[How to archive a Project]]
*[[How to open the Project Sources table]]
|api=*[[Api session event editor]]
}}
 
{{User rights nav}}

Latest revision as of 07:08, 10 July 2026

In the Tygron Platform, a Project refers to the collection of data relevant to a specific area and use-case. Each project consists of data such as:

Interacting with a Project

All Projects are stored by the Tygron Platform as static data. As a user, it is possible to interact with a Project by starting a Session. When a Session of any kind is started, the Tygron Platform reads the Project data and uses it to create a live session, accessible to the user and optionally other users within his/her domain. In a Session, the user can interact with the data. When the Session is closed, all the data in the Session is discarded. If changes are not saved, the original Project remains unaffected; restarting a session restores the original data.

Accessibility

Access and adjustment rights to a project can be configured as followed:

  • Project owner: The user who created the project and has full control over its settings and accessibility.
  • Domain users: Whether users within your domain are allowed to access your project.
  • Tygron Platform Support: whether you allow Tygron Platform support employees access your project to provide support or identify issues encountered in your project.

These rights allow you to either start a new session or join an existing live session. There are three options for adjustment:

  • Write: Write access to the project. These users are allowed to start and save during a project session.
  • Read: Read access to the project. Users with this accessibility option are not allowed to save the project. They can adjust the project when in a live session that the owner started with write access. When the owner saves the project data, the adjustments made by read-access users will also be included in the project.
  • None: No access to the project. Note that a project owner always has access to a project.

Only one session can edit a project at a time. To have multiple editing sessions, save the project under a new name to create a separate entity.

Template Project

Projects can be designated as "Template". Templates can be used as a blueprint to create new Projects. This is done by creating a copy of the Template Project, removing all geographical data from it, and allowing the user to select a new location for the new Project.

How-to's

See also

API Endpoints

Account management
User Account types
Join Only • Host Session • Editor • Domain Admin
Other
Domain • GeoShare • Project • User • Version Control • Platform security


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