Template Project: Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
No edit summary
 
(48 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{being updated}}
[[File:Api_tools_geo.png|thumb|right|400px|[[Template]] in relation to [[Source]]s and [[Geo Plugin]]s]]
{{learned|what a template in the Tygron Engine is|which data is transferred to a new project|how to create a template project|how to share your project template within your domain|how to use a template project}}
A template (project) contains a predefined generic structure that can be copied when creating a new project. This new project can have a location that differs from the template project upon which it is based. However, it will, for instance, contain the same [[Indicators]] and [[Actions]]. This can be convenient in cases of similar spatial issues at hand that occur at different locations that require different projects. Also, this functionality enables the user to develop elaborate predefined actions and custom indicators, which can then be easily applied to multiple areas/projects by simply using a template, saving the user a lot of time and effort in the long run.


==What is a template in the Tygron Engine==
==Which elements are transferred to a new project==
A template is a project that can be used to create a new project with. This new project can have a different location than the original template project, but has the same  [[Indicators]] and [[Actions]] for example, as the template project. This is very convenient in case a similar spatial issue is at hand on different locations and you want to create different projects for these locations. Also, this functionality enables the user to make elaborate predefined actions or custom indicators, which can then be easily applied with a template to another area.
In a template project, elements that are not spatial, that is, not linked to a specific location, will be transferred to a new project.
This functionality saves a lot of time and makes preparing projects faster.


==Which elements are transferred to a new project==
===Elements that ''are transferred'' to a new project===
In a template project, elements that are not spatial, thus the elements that are not linked to a location will be transferred to a new project.<br>
* [[Indicator]]s
===Examples of elements that ''are transferred'' to a new project===
* [[Stakeholder]]s
* [[Indicators]]
* [[Overlay]]s and their settings, such as the grid size
* [[Stakeholders]]
* New [[Functions]]/changes in [[function values]]
* [[Overlays]] settings, such as the grid size.
* New [[Terrain Type]]s/changes in terrain types
* New [[functions]]/changes in function values
* [[Global]]s
* [[Globals]]
* [[Action Menu]]s
* [[Actions]]
* New/changed [[Upgrade Type]]s
* New/changed [[Upgrade types]]
* [[WFS]] connections in the [[Geo Data Wizard]]
* [[WFS]] connections in the [[Geo Data Wizard]]
<br>
* [[Geo Plugin]]s


===Examples of elements that are ''not transferred'' to a new project===
===Elements that are ''not transferred'' to a new project===
* (Imported) [[Areas]]
* [[Area]]s, [[Building]]s, [[Neighborhood]]s, [[Network]]s,[[Plot]]s, [[Terrain]]s, [[Zone]]s
:The areas have a certain location in the template project. The new project is very likely on a new location and therefore the areas are not in that location and in the new project
:These type of spatial objects are bound to a specific location in the template project and are therefore not migrated to other locations/projects.
* [[Measures]]
* [[Measure]]s
:Measures are drawn on a certain location, this location is also not present in the new project anymore
:Measures which are drawn at a certain location and therefore are not applicable to other locations/projects.
* [[Cinematics]]
* [[Cinematics]]
:In a cinematic, the camera has a certain location in the 3D world, since the location is different in the new project, the cinematic will not be transferred.
:A cinematic has one or more key point locations within the project area, which will not be applicable to other locations/projects.
* [[Panel]]s
: Panels which are position or are instances of panel templates, which will not be applicable to other locations/projects due to removed content items.  


<br>
===Transferred elements that rely on spatial data===
 
* [[Overlay]]s
===Special elements that need to be ''adjusted accordingly'' after creating a new project based on a template===
: Overlays are transferred to a new project (they will be recalculated for the new project), as will the settings in the template project, such as the grid size. However, specific data that are imported and used for, for instance, the [[Rainfall Overlay]], such as water areas and weirs, are spatial data and are therefore not transferred to the new project. These datasets should therefore be imported manually into the new project. On the contrary, settings such as the length and duration of the rainfall event, ''are'' transferred from the template.
* [[Overlays]]
: Overlays are transferred to a new project (they will be recalculated for the new project) and the same settings as in the template project will be applied, such as the grid size. However, for example for the [[Rainfall_(Overlay)|rainfall overlay]]. Specific data that is imported and used for this overlay such as water level areas and weirs, is spatial data that is not transferred to the new project. These datasets should therefore be imported in the new project. Settings in the [[Rainfall_(Overlay)#Rainfall_overlay_wizard|rainfall overlay wizard]], such as the length and duration of the rainfall are transferred from the template.
* [[Panels]]
: The content of the panels is transferred to a new project, but the locations of these panels must be set again.
 
==How to create a template project==
See below for the full list of steps for creating a template project. The steps are explained in this section.
To create a template project, start with a project that you want to use as a template for other projects.


===Template settings===
===Template settings===
[[File:Template_settings_panel.png|right|500px]]
[[File:Template_settings_panel.png|right|500px]]
In the template settings screen, the data sources that should be used by default when using this template, can be set. For example AHN3 can be selected so that the AHN3 is always used when creating a project based on the template.
===Clear map===
The map needs to be cleared, so the project size will be small. This will ensure the creation of a new project based on the template will be as fast as possible.
The clear map option is a permanent setting and cannot be undone. Therefore it is recommended to create a new [[Account_Management#Change_the_version_of_your_project|version]] first, or to make a copy of your project by saving the project under a different name.


===Remove not generic elements===
{{Editor location|Template}}
When the map is cleared, remove elements that are not generic for other projects. For example, stakeholder names. The stakeholder municipality is named after the municipality in where the project area lies. If the template project is created for The Hague, the stakeholder is called ''Municipality The Hague''. If you apply the template on a project in Amsterdam, the stakeholder will use the previous name combined with the new name which will result in ''Municipality The Hague Amsterdam.'' Therefore in the template project, remove the ''The Hague'' part, so the stakeholder in the template project will be named only Municipality and in the new project in Amsterdam ''Municipality Amsterdam''.


===Domain admin rights===
In the template settings screen, the data sources that should be used by default when using this template, can be set. For example AHN3 can be selected so that the AHN3 is always used when creating a project based on that template. Changes made are stored in [[Geo Option]] items.
[[File:Template_projects.JPG|right|500px]]
Setting a project as a template can only be done by users with [[Account_management#Domain_Admin|Domain Administrator]] rights.
When a project has been made a project template, the read and write permissions will change. This is to ensure that nobody accidentally edits the project template. The permissions will be set to either none or read (project cannot be edited anymore) and only the creator can read the template by default. By default the template is not shared with other users within your domain. Please refer to the next paragraph about making templates available for the domain.


Below the list of steps for creating a project.
<br>
<br>
{{Editor steps|title=create a template project|Start with a project you want to use as a template|Create a new version of your project|Go in the Editor Ribbon to ''Tools'' --> ''Template'' --> ''Template settings''.|Set the desired data sources for new projects based on this template| Clear map. '''Warning''': this will remove the 3D world from your project and can't be undone. Therefore you have created a new version first in step 2.|When the map is cleared, remove elements that are not generic|Save the project under a new name so as to create a new project or create a new version and close the project|Log in to the main menu (make sure you have domain admin rights)|Go to ''Options'' and then select ''Projects''| Click on the Check box named "Template" to mark the project as a template}}


==Sharing your template with other users in your domain==
{{article end
[[File:Q1-2016-TemplatePermissions2.jpg|right|500px]]
|howtos=
When a project has been made a project template, the read and write permissions will change. This is to ensure that nobody accidentally edits the project template. No write permissions remain (project cannot be edited anymore) and only the creator can read the template by default. In order to change the read permissions, so that other users within the same domain can also use the template, the creator can change the permissions of the original project in the editor.
* [[How to create a Template Project]]
<br>
* [[How to share a Template Project with other users in your domain]]
<br>
* [[How to base a new Project on a Template Project]]
{{Editor steps|title=share the template with other users in your domain|Load in the editor the template project to be shared with the domain|Select "File" when in main view|Select "Permissions"| Change the entry for "Other users in domain" to "Read"|Save project}}
|videos={{video|gallery=
{{video|link=https://youtu.be/VZrazrmgYZM|description=Video tutorial on using Template Projects.}}
}}
}}


==Applying a template project on a new project==
{{editor tools nav}}
[[File:Choose_template.PNG|right|500px]]
[[Category:Project Metadata]]
For creating a new project based on a template project, follow the steps for creating a new project, but choose instead of Empty project the template project in the project wizard (see image on the right in where the user can select the Tygron Net template by clicking on the ''Use Tygron Net template button'').

Latest revision as of 14:45, 28 September 2023

Template in relation to Sources and Geo Plugins

A template (project) contains a predefined generic structure that can be copied when creating a new project. This new project can have a location that differs from the template project upon which it is based. However, it will, for instance, contain the same Indicators and Actions. This can be convenient in cases of similar spatial issues at hand that occur at different locations that require different projects. Also, this functionality enables the user to develop elaborate predefined actions and custom indicators, which can then be easily applied to multiple areas/projects by simply using a template, saving the user a lot of time and effort in the long run.

Which elements are transferred to a new project

In a template project, elements that are not spatial, that is, not linked to a specific location, will be transferred to a new project.

Elements that are transferred to a new project

Elements that are not transferred to a new project

These type of spatial objects are bound to a specific location in the template project and are therefore not migrated to other locations/projects.
Measures which are drawn at a certain location and therefore are not applicable to other locations/projects.
A cinematic has one or more key point locations within the project area, which will not be applicable to other locations/projects.
Panels which are position or are instances of panel templates, which will not be applicable to other locations/projects due to removed content items.

Transferred elements that rely on spatial data

Overlays are transferred to a new project (they will be recalculated for the new project), as will the settings in the template project, such as the grid size. However, specific data that are imported and used for, for instance, the Rainfall Overlay, such as water areas and weirs, are spatial data and are therefore not transferred to the new project. These datasets should therefore be imported manually into the new project. On the contrary, settings such as the length and duration of the rainfall event, are transferred from the template.

Template settings

Template settings panel.png
Editor → Tools (Ribbon tab) → Template (Ribbon bar)

In the template settings screen, the data sources that should be used by default when using this template, can be set. For example AHN3 can be selected so that the AHN3 is always used when creating a project based on that template. Changes made are stored in Geo Option items.


How-to's

Videos

Video tutorial on using Template Projects.
Editor ribbon icon tools.pngTools
Tools
Building style • Environment • Cinematics • Screenshot • Free Cam • Web Interface • API Overview • Triggers • Template • Geo Plugins • Debug Info
Environment
Sun angle • Solar Panels • Lighting • Weather
Cinematics
Special Effects • Particle Emitters
Screenshot
GIF animation • Video recording
Geo Plugins
Error Logs • Geo Links • Geo Options • Sources
Editor
Current Situation • Future Design • Multi Scenario • Tools • Community
Retrieved from "https://previewsupport.tygron.com/w/index.php?title=Template_Project&oldid=55578"