https://support.tygron.com/w/api.php?action=feedcontributions&user=Vincent%40tygron.nl&feedformat=atomTygron Support wiki - User contributions [en]2024-03-28T12:58:29ZUser contributionsMediaWiki 1.38.2https://support.tygron.com/w/index.php?title=Tygron_learning&diff=60274Tygron learning2024-03-20T12:47:54Z<p>Vincent@tygron.nl: Redirected page to Category:Tutorials</p>
<hr />
<div>#REDIRECT [[Category:Tutorials]]</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Category:Tutorials&diff=60273Category:Tutorials2024-03-20T12:46:11Z<p>Vincent@tygron.nl: </p>
<hr />
<div>{{tygron}} offers a number of online tutorials to learn specific basic and advanced skills through a series of steps and excercises.</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Category:Tutorials&diff=60272Category:Tutorials2024-03-20T12:43:13Z<p>Vincent@tygron.nl: </p>
<hr />
<div>{{tygron}} offers a number of online tutorials to learn specific basic and advanced skills through a series of steps and excercises.<br />
<br />
See also: [[Tygron learning]]</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=How_to_configure_a_default_legend_for_GeoTIFFs_on_the_Geoshare_(linux)&diff=59258How to configure a default legend for GeoTIFFs on the Geoshare (linux)2024-02-14T08:35:32Z<p>Vincent@tygron.nl: </p>
<hr />
<div>{{stub|todo=<br />
* Must be english<br />
* Link to windows howto as well<br />
* Link to geotiffs<br />
* Formatting<br />
}}<br />
<br />
Here are a few steps with which you can create your own GeoTIFF legend: - Create your own JSON legend in the Tygron Editor by creating any Overlay and then clicking on legend tab on the right side of editor on copy in the menu near the copy-paste icon. - The JSON legend is then in your clipboard, CTRL-V in a text editor to view it.<br />
<br />
Example: { "color" : { "argb" : -3402732 }, "entryName" : "Low", "id" : 1, "value" : 0.0 }, { "color" : { "argb" : -15414180 }, "entryName" : "High", "id" : 5, "value" : 1.0} ]<br />
<br />
This is a very simple legend with two entries "Low" (green with value 0.0) and "High" (red with value 1.0). - Then download the ExifTool: https://exiftool.org/ (We tested Linux version, but there is also a Windows version). - With this tool you can read the tags of a Tiff (or other image) outside of Tygron.<br />
<br />
Example: exiftool -D -G -a -u -U -f -s test.tiff You will then get all the tags information of the file. Including the current ImageDescription. - Now use the tool to change the ImageDescription tag to the new JSON legend.<br />
<br />
Example: exiftool -ImageDescription='[ { "color" : { "argb" : -3402732 }, "entryName" : "Low", "id" : 1, "value" : 0.0 }, { "color" : { "argb" : -15414180 }, "entryName" : "High", "id" : 5, "value" : 1.0} ]' test.tiff<br />
<br />
Make sure you use single-quotes (') at the beginning and end, if you don't do that it will cause issues with the double-quotes (") in JSON.</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=How_to_configure_a_default_legend_for_GeoTIFFs_on_the_Geoshare_(linux)&diff=59241How to configure a default legend for GeoTIFFs on the Geoshare (linux)2024-02-08T09:01:09Z<p>Vincent@tygron.nl: Created page with "Bij deze een aantal stappen waarmee je nu al zelf een GeoTIFF legenda kan maken: - Maak je JSON legenda in de Tygron Editor door een willekeurige Overlay aan te maken en dan op legend tabje rechts in editor op copy te klikken in het menu bij het copy-paste icon. - De JSON legenda zit dan in je clipboard, CTRL-V in een text editor om het te bekijken. Voorbeeld: [ { "color" : { "argb" : -3402732 }, "entryName" : "Low", "id" : 1, "value" : 0.0 }, { "color" : {..."</p>
<hr />
<div>Bij deze een aantal stappen waarmee je nu al zelf een GeoTIFF legenda kan maken:<br />
- Maak je JSON legenda in de Tygron Editor door een willekeurige Overlay aan te maken en dan op legend tabje rechts in editor op copy te klikken in het menu bij het copy-paste icon. <br />
- De JSON legenda zit dan in je clipboard, CTRL-V in een text editor om het te bekijken.<br />
<br />
Voorbeeld: [ { "color" : { "argb" : -3402732 }, "entryName" : "Low", "id" : 1, "value" : 0.0 }, { "color" : { "argb" : -15414180 }, "entryName" : "High", "id" : 5, "value" : 1.0} ]<br />
Dit is een hele simpele legenda met twee entries "Low" (groen met waarde 0.0) en "High" (rood met waarde 1.0) erin.<br />
- Download vervolgens de ExifTool: https://exiftool.org/ (ik heb Linux versie getest, maar er is ook een Windows versie). <br />
- Met deze tool kun je buiten Tygron om de tags van een Tiff (of ander plaatje) uitlezen.<br />
<br />
Voorbeeld: exiftool -D -G -a -u -U -f -s test.tiff <br />
Je krijgt dan alle tags informatie van het bestand. Waaronder de huidige ImageDescription.<br />
- Gebruik nu de tool om de ImageDescription tag aan te passen naar de nieuwe JSON legenda.<br />
<br />
Voorbeeld: exiftool -ImageDescription='[ { "color" : { "argb" : -3402732 }, "entryName" : "Low", "id" : 1, "value" : 0.0 }, { "color" : { "argb" : -15414180 }, "entryName" : "High", "id" : 5, "value" : 1.0} ]' test.tiff<br />
Let op dat je single-quotes (') gebruikt aan begin en einde, als je dat niet doet gaat het mis met de dubbel-quotes (") in JSON.<br />
- Tot slot upload je de aangepast test.tiff naar de GeoShare, gooi hem in een viewer en als alle stappen goed zijn doorlopen heeft hij een nieuwe legenda.</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=File:Add_areas1.JPG&diff=55158File:Add areas1.JPG2023-09-07T14:48:25Z<p>Vincent@tygron.nl: </p>
<hr />
<div></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=File:View_area3.JPG&diff=55157File:View area3.JPG2023-09-07T14:48:03Z<p>Vincent@tygron.nl: </p>
<hr />
<div></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geo_Data_tutorial&diff=55156Geo Data tutorial2023-09-07T14:47:10Z<p>Vincent@tygron.nl: /* Create an overlay */</p>
<hr />
<div>{{tutorial prerequisites<br />
| tutorial=This tutorial relies on base knowledge about the editor interface.<br />
| project=This tutorial will include the creation of a new project.<br />
<br />
| Download and unpack the content of this zip-file on your desktop for the necessary files: [//downloads.support.tygron.com/tutorials/tutorial_GeoData.zip tutorial_GeoData.zip]<br />
| Create a [[New Project Wizard#Videos|new project]] of Delft. For the exact location of the project, see the image below or use the ''project_location.geojson'' file (in the above zip-file) to define the project location. See [https://community.tygron.com/forum/discussion/219/new-feature-for-easier-selecting-a-new-project-area#latest this tip] on our forum for more information on how to use the GeoJSON file for selecting the location.<br />
}}<br />
<br />
==Getting Started==<br />
In this tutorial you will learn the different ways to import different types of data in your project:<br />
* data from Web services <br />
* vector data<br />
* 3D models<br />
* raster data<br />
<!--For this tutorial you will have to create a new project of the city of Delft in the Netherlands.--><br />
<br />
==Import data from Web services==<br />
In this section we are going to import data from a:<br />
* WFS (Web Feature Service) <br />
* WMS (Web Map Service)<br />
* CSW (Catalogue Service)<br />
<br />
===WFS===<br />
In this assignment you will create an Archeological Terrains Map. <br />
[[File:Archeological_map.JPG|600px|center]]<br />
<br />
# First read what exactly a [[WFS|Web Feature Service]] is. <br />
# Now we need to find data that is published as a WFS. For the Netherlands, a website to find open data is: [http://nationaalgeoregister.nl Nationaal Georegister]. Go to the Nationaal Georegister and search for the''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' dataset. Take a moment to read what this dataset is about. Then copy the WFS URL: this is the URL that contains WFS in the URL link.<br />
[[File:Search_ngr.JPG|500px|center]]<br />
<br><br />
<br><br />
[[File:Copy_wfs_url.JPG|500px|center]]<br />
<br />
# Start the Geo Data Wizard by clicking in the Editor on ''Geo import''. {{Editor location|Geo Import}}<br />
# Choose the correct type for importing the data. Since we are going to create a map which is equivalent to an overlay, choose as type: Areas. Read the [[Geo_Data_Wizard|Geo Data Wizard]] for more information about the differences between the import types.<br />
[[File:Import_areas.JPG|600px|center]]<br />
# In step 1 of the wizard, choose for ''Import a Web Feature Service''. <br />
# Click on ''add a new Feature Service'' and provide a custom name, Service Type (WFS_JSON) and URL of the WFS. After you have entered this data, click on ''add'' and then ''next''. <br />
[[File:Paste_wfs2.JPG|600px|center]]<br />
# In step 1.2 all the datasets that are published through this URL are shown (these are called layers). Choose from the drop down menu the layer: ''RCE_RIJKSMONUMENTEN_VLAK''. If this dataset is not in your project, an error message is given. What could be a reason that the data is not in your project? <br />
# In step 2 the location of the objects in your project area is shown. Click ''next''. <br />
# In step 3 we can filter the features and in step 4 adding as new areas or updating areas. Click 2 times on ''next''.<br />
# In step 5 we name the features. Click on: ''Based on specific Attribute'' and choose for the attribute for example ''subcategorie''. Now the features will be named after their sub category.<br />
[[File:Naming2.JPG|600px|center]]<br />
# In step 6 the attributes that will be imported are selected. Only numerical attributes are imported in the {{software}}. These are by default checked. Why is the list of attributes shorter than the list was in step 5? Click on ''next''. <br />
# In step 7 click on ''Finish''. Now the Geo data wizard is finished and the data is imported.<br />
<br />
====Create an overlay====<br />
# In the Editor, go to Areas and notice that the areas you have imported are listed on the left side. Select one and notice that in the [[3D Visualization]] the corresponding area is highlighted. In the tab ''Attributes'' on the right side of the screen, notice that the attributes are imported as well. <br />
{{Editor location|areas}}<br />
[[File:View_area3.JPG|600px|center]]<br />
# Since we don't want to go by these areas one by one to see the archeological value areas, we are going to create a map so we can see them in one view.<br />
Click therefore in the editor on overlays.<br />
{{Editor location|overlays}}<br />
# Add a new overlay by clicking in the bottom left corner on ''Add Areas''.<br />
# Notice a new overlay, named: ''Speciaal gebied'' is added. <br />
# Select this overlay and notice the new menu on the right side.<br />
[[File:View_area2.JPG|600px|center]]<br />
# Give the new overlay a fitting name and check the areas belonging to the archeological value map. If there are a lot of areas, you can also click on the button in the bottom right corner on ''Add Areas with Attribute''. Here you can select a common attribute of these areas. Select the common attribute, for example ''RIJKSMONUMENT_NUMMER'' and click on Add.<br />
[[File:Add_areas1.JPG|600px|center]]<br />
<br />
===WMS===<br />
In this assignment we will also create an Archeological Terrains map. <br />
# Read first on the Wiki what a [[WMS|WMS]] exactly is.<br />
# Add an Image overlay by hovering over the overlays button and choose the add Image overlay.<br />
{{Editor location|Overlays}}<br />
# Notice that a new overlay (named Beeldlaag) is added. Change on the right side the name and then open the Configuration Wizard. <br />
# Select the second option: import from a Web Image Service<br />
# Select ''Add a new Image Service'' and provide a custom name, Service Type (WMS_IMAGE) and URL of the WMS. If the data is filled in correctly, click on add and then ''Next''. As WMS URL you can use the WMS url of the ''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' of the Nationaal Georegister from the previous assignment. The WMS url is the url with WMS in the link.<br />
# Choose in the drop down menu the layer ''Terreinen van archeologische waarde - provincie'' and click ''Next''.<br />
# In the following steps, proceed with ''Next'' and then ''Finish''. <br />
# After you have finished the wizard and given the overlay a proper name, can you tell the difference between the WFS and the WMS data? If not, click on the colored areas in both maps (WFS and WMS). Do you see a difference in the information in the hover panel?<br />
<br />
[[File:Archeological_map_wms.JPG|600px|center]]<br />
<br />
===Catalogue Service===<br />
In this step we are going to create a map (overlay) of all the monumental buildings in Delft. <br />
[[File:Monumental_buildings.JPG|600px|center]]<br />
# Start by reading what a [[CSW|CSW]] exactly is.<br />
# Open the Geo Data wizard and choose for type ''AREAS''. <br />
# In step 1 of the wizard, choose for: ''Search for data in a Catalog Service''. <br />
# Click on ''Select Catalog Service'' and choose ''ArcGIS online''.<br />
[[File:Catalog_service.JPG|600px|center]]<br />
# In the next screen you can type a keyword of the dataset you want to find. We are going to create a map of the monumental buildings in Delft. Think of a correct keyword to type and click on ''Search''. Remember the project owner of the data should match the location of your project. Why is that?<br />
[[File:Monument_csw.JPG|600px|center]]<br />
# Complete the wizard. Don't forget in step 5 to choose the correct attribute to base the name on.<br />
# Follow the previous steps for creating an Overlay.<br />
# Now your map of Monumental Buildings is finished.<br />
<br />
==Import vector data==<br />
In this section we are going to import [[Geo_Data|vector]] data from a file.<br />
To import data in the {{software}}, the file must be of the GeoJSON format. <br />
<br />
In the next assignment we are going to import two fictional datasets as objects in the 3D model.<br />
One dataset contains a [[spatial_plan|spatial plan]] with a road, an office, parking space and a park. The other dataset contains trees.<br />
<br />
====Office plan====<br />
* Read this [[GeoJSON#What_is_GeoJSON|section]] on the Wiki of what exactly a GeoJSON file is. <br />
* Mostly data is not available as a GeoJSON but for example as a Shapefile. We can create a GeoJSON file ourselves with a GIS. <br />
# In the zip folder you downloaded at the start of this tutorial are two .shp files. These are Shapefiles. Follow the [[GeoJSON#How_to_create_a_GeoJSON_file|steps]] to create a GeoJSON file in you preferred GIS. You can skip the part of modifying the attributes. <br />
# After you have created the two GeoJSON files, open the Geo Data Wizard. <br />
# Select as type ''Buildings''.<br />
[[File:Type_buildings.JPG|600px|center]]<br />
# Select in step 1 ''Import a GeoJSON file'' and choose the file: ''Office'' in the next step. <br />
# Click on Next in the following steps, choosing consequently the first option. In step 5 choose the correct column for the naming of the objects.<br />
#In step 7 we see a new step that we did not come across when choosing to import data as ''AREAS''. In this step you decide what kind of 3D object the data will be. Click on ''One Function'' if your dataset only consists of data of one type, for example a dataset with only buildings or only roads. If you have a file like we do with an office, road, parking space and building, choose ''Function Mapping''. <br />
# Choose first the default function by clicking on ''Select''. For this tutorial we choose as default function a function in the category Offices.<br />
# Then make sure the drop down menu is on ''Name'' and click on ''Add''. Choose for the Function fFlter 1 the Type column. Now check the other function box and click on ''Values''. Based on the data in the column Type, you can select a function. Select for example Park, click on ''Ok'' (the screen closes) en click on the button ''Select''. Choose from the Function list a park function. <br />
# Repeat the previous steps for the attributes ''Parkeerplaats'' and ''Weg''. We are now creating rules to base the mapping on. We do not have to create rules for every attribute, since we have set a default function. Think of what would happen if we had another feature in our dataset with for example Type:School.<br />
[[File:Function_mapping.JPG|600px|center]]<br />
# Click on Next. In step 8 we can also create a mapping for the Stakeholders. For example, we can assign the roads, park and parking space to the municipality and the office to the company stakeholder. The mapping is done in the same way as step 7. Create a mapping with at least two stakeholders.<br />
[[File:Stakeholders.JPG|600px|center]]<br />
# Finish the wizard. <br />
# Notice the new buildings are now in the 3D model<br />
[[File:Location_plan.JPG|400px|center]]<br />
[[File:New_plan_2.JPG|400px|center]]<br />
<br />
====Tree dataset====<br />
# Import the other dataset ''trees'' by repeating the previous steps for importing a GeoJSON file. <br />
# In step 2 of the wizard, notice that there are 10 points in the datset and no lines or polygons. In the {{software}} it is only possible to import polygons. Therefore, we can buffer the points to create (round polygons) for the trees. Set the buffer size on 1, so as not to create very large trunks and follow the rest of the wizard.<br />
[[File:Point_data_buffer.JPG|600px|center]]<br />
# How would you do the mapping in step 7? As ''One Function'' or a ''Function Mapping''?<br />
# After finishing the wizard, notice the new trees in the office location area.<br />
[[File:Trees.JPG|400px|center]]<br />
<br />
==Importing a 3D model==<br />
In the following steps we will replace the previous imported office building with a simple 3D model of a fictional office building. <br />
# There are a lot of formats for 3D models. In the {{software}} we use the I3S format for importing 3D models. Read [[I3S|here]] more about this format.<br />
# Open the Geo Data wizard and choose Buildings.<br />
# Choose in step 1 the option import an I3S SLPK file and choose in the next step the ''office_building.slpk'' file. The originally 3D CAD building model (in DWG file format) was transformed to a SLPK file. For more information, read [[How_to_create_a_SLPK_file|here]] the steps on how to create a SLPK file from different 3D file formats. <br />
[[File:I3s_step.PNG|600px|center]]<br />
4. Proceed with Next until step 4. In step 4, choose the first option to Update the 3D model of existing buildings. Now only the model will be updated, but the building will have the same function and attributes. <br />
[[File:Update_3D_model.PNG|600px|center]]<br />
5. Finish the wizard and notice the updated office building. <br />
<gallery mode="packed"><br />
File:Test_building.PNG|3D CAD building<br />
File:Office_building_demo.PNG|Building imported in the {{software}}<br />
</gallery><br />
See also the [[Demo_San_Francisco_Project|Demo San Francisco project]] for a project of San Francisco generated from, among others, [[I3S|I3S Scene Layer data]].<br />
<br />
==Importing raster data==<br />
For this part of the tutorial we use the ready prepared GeoTIFF Kd_Delft.tif. This file contains a selection of the layer ''doorlatendheid_laag 1'' from the [http://data.nhi.nu/National Hydrological Instrument]. They layer represents classes of hydraulic conductivity of the freatic groundwater layer; the ability of the layer to transport groundwater, in m<sup>2</sup>/day:<br />
<br />
{| class="wikitable"<br />
! class in GeoTIFF<br />
! kd [m<sup>2</sup>/day]<br />
|-<br />
|2<br />
|5-10<br />
|-<br />
|3<br />
|10-20<br />
|-<br />
|4<br />
|20-30<br />
|-<br />
|5<br />
|30-40<br />
|-<br />
|6<br />
|40-60<br />
|-<br />
|7<br />
|60-80<br />
|-<br />
|8<br />
|80-100<br />
|-<br />
|}<br />
<br />
If you finish the tutorial, the result should be as the picture below:<br />
<br />
[[File:GD_tuto_KD_Overlay.PNG|800px|center]]<br />
<br />
===Creating a GeoTIFF Overlay===<br />
Go to:<br />
{{Editor location|overlays}}<br />
and select Add Geo Tiff.<br />
<br />
Add the GeoTIFF ''Kd_Delft.tif'' in the following steps:<br />
# In the general-tab press ''Select GeoTIFF''<br />
# In the GeoTIFF Import Wizard, press ''Import new Geo Tiffs''in the bottom-right<br />
# Locate ''Kd_Delft.tif'' and press ''Open''<br />
# Make sure your newly imported GeoTIFF is selcted and press ''Apply''<br />
<br />
In the general-tab ''GeoTIFF:'' should refer to ''Kd_Delft.tif''. Now add a legend:<br />
# go to the legend tab<br />
# create a legend with the 7 classes as above, by:<br />
#* checking ''Has Custom Legend''<br />
#* adding 7 records (or removing if you have to many)<br />
#* adding values, descriptions and colors starting from the lowest record<br />
# if finished, go to the general-tab and press ''refresh grid''<br />
<br />
You should arrive at the overlay as shown in the picture above. Please check the following:<br />
* open ''Kd_Delft.tif'' in a GIS-editor (e.g. QGIS); review the presence of a NoData value and projection. If these are not present, the file will not be imported(!!)<br />
* open the GeoTIFF Import Wizard and notice the option ''overwrite CRS''. If your GeoTIFF does not contain projection info, you can use this option to specify a CRS (Coordinate Reference System). If the {{software}} has trouble projecting your projected GeoTIFF on the map, you can also use this option to overwrite the existing CRS.<br />
<br />
===Changing a DEM===<br />
For the purpose of this exercise, we will change the DEM with the ''Kd_delft.tiff'', previously imported. Note, it doesn't make sense to do so, but it is just for the purpose of the exercise.<br />
<br />
Note, if you change your DEM, you will loose the original DTM. Go To: <br />
{{Editor location|overlays}}<br />
<br />
And the Heightmap Overlay. Then:<br />
* change the grid-cell size to 1m<br />
* select DTM (where you will not see the elevation of houses)<br />
* export the DTM as a GeoTIFF<br />
<br />
Now we will import a different DEM. Go to:<br />
<br />
{{Editor location|import elevation}}<br />
<br />
And do the following:<br />
* Select ''Select elevation GeoTIFF''<br />
* Select ''kd_delft.tiff''<br />
* Press ''apply''<br />
<br />
The DTM should look as below:<br />
<br />
[[File:GD_tuto_KD_as_elevation.PNG|800px|center]]<br />
<br />
Now: <br />
* revert the DTM to the elevation model to its original state by re-importing the DEM you previously exported<br />
* make a GeoTIFF in QGIS covering a part of the project area, import it via ''Select elevation GeoTIFF'' and see how it mergens with the DTM</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=File:View_area2.JPG&diff=55154File:View area2.JPG2023-09-07T14:02:07Z<p>Vincent@tygron.nl: </p>
<hr />
<div></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geo_Data_tutorial&diff=55153Geo Data tutorial2023-09-07T14:01:39Z<p>Vincent@tygron.nl: /* Create an overlay */</p>
<hr />
<div>{{tutorial prerequisites<br />
| tutorial=This tutorial relies on base knowledge about the editor interface.<br />
| project=This tutorial will include the creation of a new project.<br />
<br />
| Download and unpack the content of this zip-file on your desktop for the necessary files: [//downloads.support.tygron.com/tutorials/tutorial_GeoData.zip tutorial_GeoData.zip]<br />
| Create a [[New Project Wizard#Videos|new project]] of Delft. For the exact location of the project, see the image below or use the ''project_location.geojson'' file (in the above zip-file) to define the project location. See [https://community.tygron.com/forum/discussion/219/new-feature-for-easier-selecting-a-new-project-area#latest this tip] on our forum for more information on how to use the GeoJSON file for selecting the location.<br />
}}<br />
<br />
==Getting Started==<br />
In this tutorial you will learn the different ways to import different types of data in your project:<br />
* data from Web services <br />
* vector data<br />
* 3D models<br />
* raster data<br />
<!--For this tutorial you will have to create a new project of the city of Delft in the Netherlands.--><br />
<br />
==Import data from Web services==<br />
In this section we are going to import data from a:<br />
* WFS (Web Feature Service) <br />
* WMS (Web Map Service)<br />
* CSW (Catalogue Service)<br />
<br />
===WFS===<br />
In this assignment you will create an Archeological Terrains Map. <br />
[[File:Archeological_map.JPG|600px|center]]<br />
<br />
# First read what exactly a [[WFS|Web Feature Service]] is. <br />
# Now we need to find data that is published as a WFS. For the Netherlands, a website to find open data is: [http://nationaalgeoregister.nl Nationaal Georegister]. Go to the Nationaal Georegister and search for the''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' dataset. Take a moment to read what this dataset is about. Then copy the WFS URL: this is the URL that contains WFS in the URL link.<br />
[[File:Search_ngr.JPG|500px|center]]<br />
<br><br />
<br><br />
[[File:Copy_wfs_url.JPG|500px|center]]<br />
<br />
# Start the Geo Data Wizard by clicking in the Editor on ''Geo import''. {{Editor location|Geo Import}}<br />
# Choose the correct type for importing the data. Since we are going to create a map which is equivalent to an overlay, choose as type: Areas. Read the [[Geo_Data_Wizard|Geo Data Wizard]] for more information about the differences between the import types.<br />
[[File:Import_areas.JPG|600px|center]]<br />
# In step 1 of the wizard, choose for ''Import a Web Feature Service''. <br />
# Click on ''add a new Feature Service'' and provide a custom name, Service Type (WFS_JSON) and URL of the WFS. After you have entered this data, click on ''add'' and then ''next''. <br />
[[File:Paste_wfs2.JPG|600px|center]]<br />
# In step 1.2 all the datasets that are published through this URL are shown (these are called layers). Choose from the drop down menu the layer: ''RCE_RIJKSMONUMENTEN_VLAK''. If this dataset is not in your project, an error message is given. What could be a reason that the data is not in your project? <br />
# In step 2 the location of the objects in your project area is shown. Click ''next''. <br />
# In step 3 we can filter the features and in step 4 adding as new areas or updating areas. Click 2 times on ''next''.<br />
# In step 5 we name the features. Click on: ''Based on specific Attribute'' and choose for the attribute for example ''subcategorie''. Now the features will be named after their sub category.<br />
[[File:Naming2.JPG|600px|center]]<br />
# In step 6 the attributes that will be imported are selected. Only numerical attributes are imported in the {{software}}. These are by default checked. Why is the list of attributes shorter than the list was in step 5? Click on ''next''. <br />
# In step 7 click on ''Finish''. Now the Geo data wizard is finished and the data is imported.<br />
<br />
====Create an overlay====<br />
# In the Editor, go to Areas and notice that the areas you have imported are listed on the left side. Select one and notice that in the [[3D Visualization]] the corresponding area is highlighted. In the tab ''Attributes'' on the right side of the screen, notice that the attributes are imported as well. <br />
{{Editor location|areas}}<br />
[[File:View_area2.JPG|600px|center]]<br />
# Since we don't want to go by these areas one by one to see the archeological value areas, we are going to create a map so we can see them in one view.<br />
Click therefore in the editor on overlays.<br />
{{Editor location|overlays}}<br />
# Add a new overlay by clicking in the bottom left corner on ''Add Areas''.<br />
# Notice a new overlay, named: ''Speciaal gebied'' is added. <br />
# Select this overlay and notice the new menu on the right side.<br />
[[File:Overlays_areas.JPG|600px|center]]<br />
# Give the new overlay a fitting name and check the areas belonging to the archeological value map. If there are a lot of areas, you can also click on the button in the bottom right corner on ''Add Areas with Attribute''. Here you can select a common attribute of these areas. Select the common attribute, for example ''MONUMENTNR'' and click on Add.<br />
[[File:Add_areas.JPG|600px|center]]<br />
<br />
===WMS===<br />
In this assignment we will also create an Archeological Terrains map. <br />
# Read first on the Wiki what a [[WMS|WMS]] exactly is.<br />
# Add an Image overlay by hovering over the overlays button and choose the add Image overlay.<br />
{{Editor location|Overlays}}<br />
# Notice that a new overlay (named Beeldlaag) is added. Change on the right side the name and then open the Configuration Wizard. <br />
# Select the second option: import from a Web Image Service<br />
# Select ''Add a new Image Service'' and provide a custom name, Service Type (WMS_IMAGE) and URL of the WMS. If the data is filled in correctly, click on add and then ''Next''. As WMS URL you can use the WMS url of the ''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' of the Nationaal Georegister from the previous assignment. The WMS url is the url with WMS in the link.<br />
# Choose in the drop down menu the layer ''Terreinen van archeologische waarde - provincie'' and click ''Next''.<br />
# In the following steps, proceed with ''Next'' and then ''Finish''. <br />
# After you have finished the wizard and given the overlay a proper name, can you tell the difference between the WFS and the WMS data? If not, click on the colored areas in both maps (WFS and WMS). Do you see a difference in the information in the hover panel?<br />
<br />
[[File:Archeological_map_wms.JPG|600px|center]]<br />
<br />
===Catalogue Service===<br />
In this step we are going to create a map (overlay) of all the monumental buildings in Delft. <br />
[[File:Monumental_buildings.JPG|600px|center]]<br />
# Start by reading what a [[CSW|CSW]] exactly is.<br />
# Open the Geo Data wizard and choose for type ''AREAS''. <br />
# In step 1 of the wizard, choose for: ''Search for data in a Catalog Service''. <br />
# Click on ''Select Catalog Service'' and choose ''ArcGIS online''.<br />
[[File:Catalog_service.JPG|600px|center]]<br />
# In the next screen you can type a keyword of the dataset you want to find. We are going to create a map of the monumental buildings in Delft. Think of a correct keyword to type and click on ''Search''. Remember the project owner of the data should match the location of your project. Why is that?<br />
[[File:Monument_csw.JPG|600px|center]]<br />
# Complete the wizard. Don't forget in step 5 to choose the correct attribute to base the name on.<br />
# Follow the previous steps for creating an Overlay.<br />
# Now your map of Monumental Buildings is finished.<br />
<br />
==Import vector data==<br />
In this section we are going to import [[Geo_Data|vector]] data from a file.<br />
To import data in the {{software}}, the file must be of the GeoJSON format. <br />
<br />
In the next assignment we are going to import two fictional datasets as objects in the 3D model.<br />
One dataset contains a [[spatial_plan|spatial plan]] with a road, an office, parking space and a park. The other dataset contains trees.<br />
<br />
====Office plan====<br />
* Read this [[GeoJSON#What_is_GeoJSON|section]] on the Wiki of what exactly a GeoJSON file is. <br />
* Mostly data is not available as a GeoJSON but for example as a Shapefile. We can create a GeoJSON file ourselves with a GIS. <br />
# In the zip folder you downloaded at the start of this tutorial are two .shp files. These are Shapefiles. Follow the [[GeoJSON#How_to_create_a_GeoJSON_file|steps]] to create a GeoJSON file in you preferred GIS. You can skip the part of modifying the attributes. <br />
# After you have created the two GeoJSON files, open the Geo Data Wizard. <br />
# Select as type ''Buildings''.<br />
[[File:Type_buildings.JPG|600px|center]]<br />
# Select in step 1 ''Import a GeoJSON file'' and choose the file: ''Office'' in the next step. <br />
# Click on Next in the following steps, choosing consequently the first option. In step 5 choose the correct column for the naming of the objects.<br />
#In step 7 we see a new step that we did not come across when choosing to import data as ''AREAS''. In this step you decide what kind of 3D object the data will be. Click on ''One Function'' if your dataset only consists of data of one type, for example a dataset with only buildings or only roads. If you have a file like we do with an office, road, parking space and building, choose ''Function Mapping''. <br />
# Choose first the default function by clicking on ''Select''. For this tutorial we choose as default function a function in the category Offices.<br />
# Then make sure the drop down menu is on ''Name'' and click on ''Add''. Choose for the Function fFlter 1 the Type column. Now check the other function box and click on ''Values''. Based on the data in the column Type, you can select a function. Select for example Park, click on ''Ok'' (the screen closes) en click on the button ''Select''. Choose from the Function list a park function. <br />
# Repeat the previous steps for the attributes ''Parkeerplaats'' and ''Weg''. We are now creating rules to base the mapping on. We do not have to create rules for every attribute, since we have set a default function. Think of what would happen if we had another feature in our dataset with for example Type:School.<br />
[[File:Function_mapping.JPG|600px|center]]<br />
# Click on Next. In step 8 we can also create a mapping for the Stakeholders. For example, we can assign the roads, park and parking space to the municipality and the office to the company stakeholder. The mapping is done in the same way as step 7. Create a mapping with at least two stakeholders.<br />
[[File:Stakeholders.JPG|600px|center]]<br />
# Finish the wizard. <br />
# Notice the new buildings are now in the 3D model<br />
[[File:Location_plan.JPG|400px|center]]<br />
[[File:New_plan_2.JPG|400px|center]]<br />
<br />
====Tree dataset====<br />
# Import the other dataset ''trees'' by repeating the previous steps for importing a GeoJSON file. <br />
# In step 2 of the wizard, notice that there are 10 points in the datset and no lines or polygons. In the {{software}} it is only possible to import polygons. Therefore, we can buffer the points to create (round polygons) for the trees. Set the buffer size on 1, so as not to create very large trunks and follow the rest of the wizard.<br />
[[File:Point_data_buffer.JPG|600px|center]]<br />
# How would you do the mapping in step 7? As ''One Function'' or a ''Function Mapping''?<br />
# After finishing the wizard, notice the new trees in the office location area.<br />
[[File:Trees.JPG|400px|center]]<br />
<br />
==Importing a 3D model==<br />
In the following steps we will replace the previous imported office building with a simple 3D model of a fictional office building. <br />
# There are a lot of formats for 3D models. In the {{software}} we use the I3S format for importing 3D models. Read [[I3S|here]] more about this format.<br />
# Open the Geo Data wizard and choose Buildings.<br />
# Choose in step 1 the option import an I3S SLPK file and choose in the next step the ''office_building.slpk'' file. The originally 3D CAD building model (in DWG file format) was transformed to a SLPK file. For more information, read [[How_to_create_a_SLPK_file|here]] the steps on how to create a SLPK file from different 3D file formats. <br />
[[File:I3s_step.PNG|600px|center]]<br />
4. Proceed with Next until step 4. In step 4, choose the first option to Update the 3D model of existing buildings. Now only the model will be updated, but the building will have the same function and attributes. <br />
[[File:Update_3D_model.PNG|600px|center]]<br />
5. Finish the wizard and notice the updated office building. <br />
<gallery mode="packed"><br />
File:Test_building.PNG|3D CAD building<br />
File:Office_building_demo.PNG|Building imported in the {{software}}<br />
</gallery><br />
See also the [[Demo_San_Francisco_Project|Demo San Francisco project]] for a project of San Francisco generated from, among others, [[I3S|I3S Scene Layer data]].<br />
<br />
==Importing raster data==<br />
For this part of the tutorial we use the ready prepared GeoTIFF Kd_Delft.tif. This file contains a selection of the layer ''doorlatendheid_laag 1'' from the [http://data.nhi.nu/National Hydrological Instrument]. They layer represents classes of hydraulic conductivity of the freatic groundwater layer; the ability of the layer to transport groundwater, in m<sup>2</sup>/day:<br />
<br />
{| class="wikitable"<br />
! class in GeoTIFF<br />
! kd [m<sup>2</sup>/day]<br />
|-<br />
|2<br />
|5-10<br />
|-<br />
|3<br />
|10-20<br />
|-<br />
|4<br />
|20-30<br />
|-<br />
|5<br />
|30-40<br />
|-<br />
|6<br />
|40-60<br />
|-<br />
|7<br />
|60-80<br />
|-<br />
|8<br />
|80-100<br />
|-<br />
|}<br />
<br />
If you finish the tutorial, the result should be as the picture below:<br />
<br />
[[File:GD_tuto_KD_Overlay.PNG|800px|center]]<br />
<br />
===Creating a GeoTIFF Overlay===<br />
Go to:<br />
{{Editor location|overlays}}<br />
and select Add Geo Tiff.<br />
<br />
Add the GeoTIFF ''Kd_Delft.tif'' in the following steps:<br />
# In the general-tab press ''Select GeoTIFF''<br />
# In the GeoTIFF Import Wizard, press ''Import new Geo Tiffs''in the bottom-right<br />
# Locate ''Kd_Delft.tif'' and press ''Open''<br />
# Make sure your newly imported GeoTIFF is selcted and press ''Apply''<br />
<br />
In the general-tab ''GeoTIFF:'' should refer to ''Kd_Delft.tif''. Now add a legend:<br />
# go to the legend tab<br />
# create a legend with the 7 classes as above, by:<br />
#* checking ''Has Custom Legend''<br />
#* adding 7 records (or removing if you have to many)<br />
#* adding values, descriptions and colors starting from the lowest record<br />
# if finished, go to the general-tab and press ''refresh grid''<br />
<br />
You should arrive at the overlay as shown in the picture above. Please check the following:<br />
* open ''Kd_Delft.tif'' in a GIS-editor (e.g. QGIS); review the presence of a NoData value and projection. If these are not present, the file will not be imported(!!)<br />
* open the GeoTIFF Import Wizard and notice the option ''overwrite CRS''. If your GeoTIFF does not contain projection info, you can use this option to specify a CRS (Coordinate Reference System). If the {{software}} has trouble projecting your projected GeoTIFF on the map, you can also use this option to overwrite the existing CRS.<br />
<br />
===Changing a DEM===<br />
For the purpose of this exercise, we will change the DEM with the ''Kd_delft.tiff'', previously imported. Note, it doesn't make sense to do so, but it is just for the purpose of the exercise.<br />
<br />
Note, if you change your DEM, you will loose the original DTM. Go To: <br />
{{Editor location|overlays}}<br />
<br />
And the Heightmap Overlay. Then:<br />
* change the grid-cell size to 1m<br />
* select DTM (where you will not see the elevation of houses)<br />
* export the DTM as a GeoTIFF<br />
<br />
Now we will import a different DEM. Go to:<br />
<br />
{{Editor location|import elevation}}<br />
<br />
And do the following:<br />
* Select ''Select elevation GeoTIFF''<br />
* Select ''kd_delft.tiff''<br />
* Press ''apply''<br />
<br />
The DTM should look as below:<br />
<br />
[[File:GD_tuto_KD_as_elevation.PNG|800px|center]]<br />
<br />
Now: <br />
* revert the DTM to the elevation model to its original state by re-importing the DEM you previously exported<br />
* make a GeoTIFF in QGIS covering a part of the project area, import it via ''Select elevation GeoTIFF'' and see how it mergens with the DTM</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=File:View_area1.JPG&diff=55152File:View area1.JPG2023-09-07T13:59:27Z<p>Vincent@tygron.nl: </p>
<hr />
<div></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geo_Data_tutorial&diff=55151Geo Data tutorial2023-09-07T13:59:14Z<p>Vincent@tygron.nl: /* Create an overlay */</p>
<hr />
<div>{{tutorial prerequisites<br />
| tutorial=This tutorial relies on base knowledge about the editor interface.<br />
| project=This tutorial will include the creation of a new project.<br />
<br />
| Download and unpack the content of this zip-file on your desktop for the necessary files: [//downloads.support.tygron.com/tutorials/tutorial_GeoData.zip tutorial_GeoData.zip]<br />
| Create a [[New Project Wizard#Videos|new project]] of Delft. For the exact location of the project, see the image below or use the ''project_location.geojson'' file (in the above zip-file) to define the project location. See [https://community.tygron.com/forum/discussion/219/new-feature-for-easier-selecting-a-new-project-area#latest this tip] on our forum for more information on how to use the GeoJSON file for selecting the location.<br />
}}<br />
<br />
==Getting Started==<br />
In this tutorial you will learn the different ways to import different types of data in your project:<br />
* data from Web services <br />
* vector data<br />
* 3D models<br />
* raster data<br />
<!--For this tutorial you will have to create a new project of the city of Delft in the Netherlands.--><br />
<br />
==Import data from Web services==<br />
In this section we are going to import data from a:<br />
* WFS (Web Feature Service) <br />
* WMS (Web Map Service)<br />
* CSW (Catalogue Service)<br />
<br />
===WFS===<br />
In this assignment you will create an Archeological Terrains Map. <br />
[[File:Archeological_map.JPG|600px|center]]<br />
<br />
# First read what exactly a [[WFS|Web Feature Service]] is. <br />
# Now we need to find data that is published as a WFS. For the Netherlands, a website to find open data is: [http://nationaalgeoregister.nl Nationaal Georegister]. Go to the Nationaal Georegister and search for the''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' dataset. Take a moment to read what this dataset is about. Then copy the WFS URL: this is the URL that contains WFS in the URL link.<br />
[[File:Search_ngr.JPG|500px|center]]<br />
<br><br />
<br><br />
[[File:Copy_wfs_url.JPG|500px|center]]<br />
<br />
# Start the Geo Data Wizard by clicking in the Editor on ''Geo import''. {{Editor location|Geo Import}}<br />
# Choose the correct type for importing the data. Since we are going to create a map which is equivalent to an overlay, choose as type: Areas. Read the [[Geo_Data_Wizard|Geo Data Wizard]] for more information about the differences between the import types.<br />
[[File:Import_areas.JPG|600px|center]]<br />
# In step 1 of the wizard, choose for ''Import a Web Feature Service''. <br />
# Click on ''add a new Feature Service'' and provide a custom name, Service Type (WFS_JSON) and URL of the WFS. After you have entered this data, click on ''add'' and then ''next''. <br />
[[File:Paste_wfs2.JPG|600px|center]]<br />
# In step 1.2 all the datasets that are published through this URL are shown (these are called layers). Choose from the drop down menu the layer: ''RCE_RIJKSMONUMENTEN_VLAK''. If this dataset is not in your project, an error message is given. What could be a reason that the data is not in your project? <br />
# In step 2 the location of the objects in your project area is shown. Click ''next''. <br />
# In step 3 we can filter the features and in step 4 adding as new areas or updating areas. Click 2 times on ''next''.<br />
# In step 5 we name the features. Click on: ''Based on specific Attribute'' and choose for the attribute for example ''subcategorie''. Now the features will be named after their sub category.<br />
[[File:Naming2.JPG|600px|center]]<br />
# In step 6 the attributes that will be imported are selected. Only numerical attributes are imported in the {{software}}. These are by default checked. Why is the list of attributes shorter than the list was in step 5? Click on ''next''. <br />
# In step 7 click on ''Finish''. Now the Geo data wizard is finished and the data is imported.<br />
<br />
====Create an overlay====<br />
# In the Editor, go to Areas and notice that the areas you have imported are listed on the left side. Select one and notice that in the [[3D Visualization]] the corresponding area is highlighted. In the tab ''Attributes'' on the right side of the screen, notice that the attributes are imported as well. <br />
{{Editor location|areas}}<br />
[[File:View_area1.JPG|600px|center]]<br />
# Since we don't want to go by these areas one by one to see the archeological value areas, we are going to create a map so we can see them in one view.<br />
Click therefore in the editor on overlays.<br />
{{Editor location|overlays}}<br />
# Add a new overlay by clicking in the bottom left corner on ''Add Areas''.<br />
# Notice a new overlay, named: ''Speciaal gebied'' is added. <br />
# Select this overlay and notice the new menu on the right side.<br />
[[File:Overlays_areas.JPG|600px|center]]<br />
# Give the new overlay a fitting name and check the areas belonging to the archeological value map. If there are a lot of areas, you can also click on the button in the bottom right corner on ''Add Areas with Attribute''. Here you can select a common attribute of these areas. Select the common attribute, for example ''MONUMENTNR'' and click on Add.<br />
[[File:Add_areas.JPG|600px|center]]<br />
<br />
===WMS===<br />
In this assignment we will also create an Archeological Terrains map. <br />
# Read first on the Wiki what a [[WMS|WMS]] exactly is.<br />
# Add an Image overlay by hovering over the overlays button and choose the add Image overlay.<br />
{{Editor location|Overlays}}<br />
# Notice that a new overlay (named Beeldlaag) is added. Change on the right side the name and then open the Configuration Wizard. <br />
# Select the second option: import from a Web Image Service<br />
# Select ''Add a new Image Service'' and provide a custom name, Service Type (WMS_IMAGE) and URL of the WMS. If the data is filled in correctly, click on add and then ''Next''. As WMS URL you can use the WMS url of the ''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' of the Nationaal Georegister from the previous assignment. The WMS url is the url with WMS in the link.<br />
# Choose in the drop down menu the layer ''Terreinen van archeologische waarde - provincie'' and click ''Next''.<br />
# In the following steps, proceed with ''Next'' and then ''Finish''. <br />
# After you have finished the wizard and given the overlay a proper name, can you tell the difference between the WFS and the WMS data? If not, click on the colored areas in both maps (WFS and WMS). Do you see a difference in the information in the hover panel?<br />
<br />
[[File:Archeological_map_wms.JPG|600px|center]]<br />
<br />
===Catalogue Service===<br />
In this step we are going to create a map (overlay) of all the monumental buildings in Delft. <br />
[[File:Monumental_buildings.JPG|600px|center]]<br />
# Start by reading what a [[CSW|CSW]] exactly is.<br />
# Open the Geo Data wizard and choose for type ''AREAS''. <br />
# In step 1 of the wizard, choose for: ''Search for data in a Catalog Service''. <br />
# Click on ''Select Catalog Service'' and choose ''ArcGIS online''.<br />
[[File:Catalog_service.JPG|600px|center]]<br />
# In the next screen you can type a keyword of the dataset you want to find. We are going to create a map of the monumental buildings in Delft. Think of a correct keyword to type and click on ''Search''. Remember the project owner of the data should match the location of your project. Why is that?<br />
[[File:Monument_csw.JPG|600px|center]]<br />
# Complete the wizard. Don't forget in step 5 to choose the correct attribute to base the name on.<br />
# Follow the previous steps for creating an Overlay.<br />
# Now your map of Monumental Buildings is finished.<br />
<br />
==Import vector data==<br />
In this section we are going to import [[Geo_Data|vector]] data from a file.<br />
To import data in the {{software}}, the file must be of the GeoJSON format. <br />
<br />
In the next assignment we are going to import two fictional datasets as objects in the 3D model.<br />
One dataset contains a [[spatial_plan|spatial plan]] with a road, an office, parking space and a park. The other dataset contains trees.<br />
<br />
====Office plan====<br />
* Read this [[GeoJSON#What_is_GeoJSON|section]] on the Wiki of what exactly a GeoJSON file is. <br />
* Mostly data is not available as a GeoJSON but for example as a Shapefile. We can create a GeoJSON file ourselves with a GIS. <br />
# In the zip folder you downloaded at the start of this tutorial are two .shp files. These are Shapefiles. Follow the [[GeoJSON#How_to_create_a_GeoJSON_file|steps]] to create a GeoJSON file in you preferred GIS. You can skip the part of modifying the attributes. <br />
# After you have created the two GeoJSON files, open the Geo Data Wizard. <br />
# Select as type ''Buildings''.<br />
[[File:Type_buildings.JPG|600px|center]]<br />
# Select in step 1 ''Import a GeoJSON file'' and choose the file: ''Office'' in the next step. <br />
# Click on Next in the following steps, choosing consequently the first option. In step 5 choose the correct column for the naming of the objects.<br />
#In step 7 we see a new step that we did not come across when choosing to import data as ''AREAS''. In this step you decide what kind of 3D object the data will be. Click on ''One Function'' if your dataset only consists of data of one type, for example a dataset with only buildings or only roads. If you have a file like we do with an office, road, parking space and building, choose ''Function Mapping''. <br />
# Choose first the default function by clicking on ''Select''. For this tutorial we choose as default function a function in the category Offices.<br />
# Then make sure the drop down menu is on ''Name'' and click on ''Add''. Choose for the Function fFlter 1 the Type column. Now check the other function box and click on ''Values''. Based on the data in the column Type, you can select a function. Select for example Park, click on ''Ok'' (the screen closes) en click on the button ''Select''. Choose from the Function list a park function. <br />
# Repeat the previous steps for the attributes ''Parkeerplaats'' and ''Weg''. We are now creating rules to base the mapping on. We do not have to create rules for every attribute, since we have set a default function. Think of what would happen if we had another feature in our dataset with for example Type:School.<br />
[[File:Function_mapping.JPG|600px|center]]<br />
# Click on Next. In step 8 we can also create a mapping for the Stakeholders. For example, we can assign the roads, park and parking space to the municipality and the office to the company stakeholder. The mapping is done in the same way as step 7. Create a mapping with at least two stakeholders.<br />
[[File:Stakeholders.JPG|600px|center]]<br />
# Finish the wizard. <br />
# Notice the new buildings are now in the 3D model<br />
[[File:Location_plan.JPG|400px|center]]<br />
[[File:New_plan_2.JPG|400px|center]]<br />
<br />
====Tree dataset====<br />
# Import the other dataset ''trees'' by repeating the previous steps for importing a GeoJSON file. <br />
# In step 2 of the wizard, notice that there are 10 points in the datset and no lines or polygons. In the {{software}} it is only possible to import polygons. Therefore, we can buffer the points to create (round polygons) for the trees. Set the buffer size on 1, so as not to create very large trunks and follow the rest of the wizard.<br />
[[File:Point_data_buffer.JPG|600px|center]]<br />
# How would you do the mapping in step 7? As ''One Function'' or a ''Function Mapping''?<br />
# After finishing the wizard, notice the new trees in the office location area.<br />
[[File:Trees.JPG|400px|center]]<br />
<br />
==Importing a 3D model==<br />
In the following steps we will replace the previous imported office building with a simple 3D model of a fictional office building. <br />
# There are a lot of formats for 3D models. In the {{software}} we use the I3S format for importing 3D models. Read [[I3S|here]] more about this format.<br />
# Open the Geo Data wizard and choose Buildings.<br />
# Choose in step 1 the option import an I3S SLPK file and choose in the next step the ''office_building.slpk'' file. The originally 3D CAD building model (in DWG file format) was transformed to a SLPK file. For more information, read [[How_to_create_a_SLPK_file|here]] the steps on how to create a SLPK file from different 3D file formats. <br />
[[File:I3s_step.PNG|600px|center]]<br />
4. Proceed with Next until step 4. In step 4, choose the first option to Update the 3D model of existing buildings. Now only the model will be updated, but the building will have the same function and attributes. <br />
[[File:Update_3D_model.PNG|600px|center]]<br />
5. Finish the wizard and notice the updated office building. <br />
<gallery mode="packed"><br />
File:Test_building.PNG|3D CAD building<br />
File:Office_building_demo.PNG|Building imported in the {{software}}<br />
</gallery><br />
See also the [[Demo_San_Francisco_Project|Demo San Francisco project]] for a project of San Francisco generated from, among others, [[I3S|I3S Scene Layer data]].<br />
<br />
==Importing raster data==<br />
For this part of the tutorial we use the ready prepared GeoTIFF Kd_Delft.tif. This file contains a selection of the layer ''doorlatendheid_laag 1'' from the [http://data.nhi.nu/National Hydrological Instrument]. They layer represents classes of hydraulic conductivity of the freatic groundwater layer; the ability of the layer to transport groundwater, in m<sup>2</sup>/day:<br />
<br />
{| class="wikitable"<br />
! class in GeoTIFF<br />
! kd [m<sup>2</sup>/day]<br />
|-<br />
|2<br />
|5-10<br />
|-<br />
|3<br />
|10-20<br />
|-<br />
|4<br />
|20-30<br />
|-<br />
|5<br />
|30-40<br />
|-<br />
|6<br />
|40-60<br />
|-<br />
|7<br />
|60-80<br />
|-<br />
|8<br />
|80-100<br />
|-<br />
|}<br />
<br />
If you finish the tutorial, the result should be as the picture below:<br />
<br />
[[File:GD_tuto_KD_Overlay.PNG|800px|center]]<br />
<br />
===Creating a GeoTIFF Overlay===<br />
Go to:<br />
{{Editor location|overlays}}<br />
and select Add Geo Tiff.<br />
<br />
Add the GeoTIFF ''Kd_Delft.tif'' in the following steps:<br />
# In the general-tab press ''Select GeoTIFF''<br />
# In the GeoTIFF Import Wizard, press ''Import new Geo Tiffs''in the bottom-right<br />
# Locate ''Kd_Delft.tif'' and press ''Open''<br />
# Make sure your newly imported GeoTIFF is selcted and press ''Apply''<br />
<br />
In the general-tab ''GeoTIFF:'' should refer to ''Kd_Delft.tif''. Now add a legend:<br />
# go to the legend tab<br />
# create a legend with the 7 classes as above, by:<br />
#* checking ''Has Custom Legend''<br />
#* adding 7 records (or removing if you have to many)<br />
#* adding values, descriptions and colors starting from the lowest record<br />
# if finished, go to the general-tab and press ''refresh grid''<br />
<br />
You should arrive at the overlay as shown in the picture above. Please check the following:<br />
* open ''Kd_Delft.tif'' in a GIS-editor (e.g. QGIS); review the presence of a NoData value and projection. If these are not present, the file will not be imported(!!)<br />
* open the GeoTIFF Import Wizard and notice the option ''overwrite CRS''. If your GeoTIFF does not contain projection info, you can use this option to specify a CRS (Coordinate Reference System). If the {{software}} has trouble projecting your projected GeoTIFF on the map, you can also use this option to overwrite the existing CRS.<br />
<br />
===Changing a DEM===<br />
For the purpose of this exercise, we will change the DEM with the ''Kd_delft.tiff'', previously imported. Note, it doesn't make sense to do so, but it is just for the purpose of the exercise.<br />
<br />
Note, if you change your DEM, you will loose the original DTM. Go To: <br />
{{Editor location|overlays}}<br />
<br />
And the Heightmap Overlay. Then:<br />
* change the grid-cell size to 1m<br />
* select DTM (where you will not see the elevation of houses)<br />
* export the DTM as a GeoTIFF<br />
<br />
Now we will import a different DEM. Go to:<br />
<br />
{{Editor location|import elevation}}<br />
<br />
And do the following:<br />
* Select ''Select elevation GeoTIFF''<br />
* Select ''kd_delft.tiff''<br />
* Press ''apply''<br />
<br />
The DTM should look as below:<br />
<br />
[[File:GD_tuto_KD_as_elevation.PNG|800px|center]]<br />
<br />
Now: <br />
* revert the DTM to the elevation model to its original state by re-importing the DEM you previously exported<br />
* make a GeoTIFF in QGIS covering a part of the project area, import it via ''Select elevation GeoTIFF'' and see how it mergens with the DTM</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geo_Data_tutorial&diff=55150Geo Data tutorial2023-09-07T13:53:22Z<p>Vincent@tygron.nl: /* WFS */</p>
<hr />
<div>{{tutorial prerequisites<br />
| tutorial=This tutorial relies on base knowledge about the editor interface.<br />
| project=This tutorial will include the creation of a new project.<br />
<br />
| Download and unpack the content of this zip-file on your desktop for the necessary files: [//downloads.support.tygron.com/tutorials/tutorial_GeoData.zip tutorial_GeoData.zip]<br />
| Create a [[New Project Wizard#Videos|new project]] of Delft. For the exact location of the project, see the image below or use the ''project_location.geojson'' file (in the above zip-file) to define the project location. See [https://community.tygron.com/forum/discussion/219/new-feature-for-easier-selecting-a-new-project-area#latest this tip] on our forum for more information on how to use the GeoJSON file for selecting the location.<br />
}}<br />
<br />
==Getting Started==<br />
In this tutorial you will learn the different ways to import different types of data in your project:<br />
* data from Web services <br />
* vector data<br />
* 3D models<br />
* raster data<br />
<!--For this tutorial you will have to create a new project of the city of Delft in the Netherlands.--><br />
<br />
==Import data from Web services==<br />
In this section we are going to import data from a:<br />
* WFS (Web Feature Service) <br />
* WMS (Web Map Service)<br />
* CSW (Catalogue Service)<br />
<br />
===WFS===<br />
In this assignment you will create an Archeological Terrains Map. <br />
[[File:Archeological_map.JPG|600px|center]]<br />
<br />
# First read what exactly a [[WFS|Web Feature Service]] is. <br />
# Now we need to find data that is published as a WFS. For the Netherlands, a website to find open data is: [http://nationaalgeoregister.nl Nationaal Georegister]. Go to the Nationaal Georegister and search for the''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' dataset. Take a moment to read what this dataset is about. Then copy the WFS URL: this is the URL that contains WFS in the URL link.<br />
[[File:Search_ngr.JPG|500px|center]]<br />
<br><br />
<br><br />
[[File:Copy_wfs_url.JPG|500px|center]]<br />
<br />
# Start the Geo Data Wizard by clicking in the Editor on ''Geo import''. {{Editor location|Geo Import}}<br />
# Choose the correct type for importing the data. Since we are going to create a map which is equivalent to an overlay, choose as type: Areas. Read the [[Geo_Data_Wizard|Geo Data Wizard]] for more information about the differences between the import types.<br />
[[File:Import_areas.JPG|600px|center]]<br />
# In step 1 of the wizard, choose for ''Import a Web Feature Service''. <br />
# Click on ''add a new Feature Service'' and provide a custom name, Service Type (WFS_JSON) and URL of the WFS. After you have entered this data, click on ''add'' and then ''next''. <br />
[[File:Paste_wfs2.JPG|600px|center]]<br />
# In step 1.2 all the datasets that are published through this URL are shown (these are called layers). Choose from the drop down menu the layer: ''RCE_RIJKSMONUMENTEN_VLAK''. If this dataset is not in your project, an error message is given. What could be a reason that the data is not in your project? <br />
# In step 2 the location of the objects in your project area is shown. Click ''next''. <br />
# In step 3 we can filter the features and in step 4 adding as new areas or updating areas. Click 2 times on ''next''.<br />
# In step 5 we name the features. Click on: ''Based on specific Attribute'' and choose for the attribute for example ''subcategorie''. Now the features will be named after their sub category.<br />
[[File:Naming2.JPG|600px|center]]<br />
# In step 6 the attributes that will be imported are selected. Only numerical attributes are imported in the {{software}}. These are by default checked. Why is the list of attributes shorter than the list was in step 5? Click on ''next''. <br />
# In step 7 click on ''Finish''. Now the Geo data wizard is finished and the data is imported.<br />
<br />
====Create an overlay====<br />
# In the Editor, go to Areas and notice that the areas you have imported are listed on the left side. Select one and notice that in the [[3D Visualization]] the corresponding area is highlighted. In the tab ''Attributes'' on the right side of the screen, notice that the attributes are imported as well. <br />
{{Editor location|areas}}<br />
[[File:View_area.JPG|600px|center]]<br />
# Since we don't want to go by these areas one by one to see the archeological value areas, we are going to create a map so we can see them in one view.<br />
Click therefore in the editor on overlays.<br />
{{Editor location|overlays}}<br />
# Add a new overlay by clicking in the bottom left corner on ''Add Areas''.<br />
# Notice a new overlay, named: ''Speciaal gebied'' is added. <br />
# Select this overlay and notice the new menu on the right side.<br />
[[File:Overlays_areas.JPG|600px|center]]<br />
# Give the new overlay a fitting name and check the areas belonging to the archeological value map. If there are a lot of areas, you can also click on the button in the bottom right corner on ''Add Areas with Attribute''. Here you can select a common attribute of these areas. Select the common attribute, for example ''MONUMENTNR'' and click on Add.<br />
[[File:Add_areas.JPG|600px|center]]<br />
<br />
===WMS===<br />
In this assignment we will also create an Archeological Terrains map. <br />
# Read first on the Wiki what a [[WMS|WMS]] exactly is.<br />
# Add an Image overlay by hovering over the overlays button and choose the add Image overlay.<br />
{{Editor location|Overlays}}<br />
# Notice that a new overlay (named Beeldlaag) is added. Change on the right side the name and then open the Configuration Wizard. <br />
# Select the second option: import from a Web Image Service<br />
# Select ''Add a new Image Service'' and provide a custom name, Service Type (WMS_IMAGE) and URL of the WMS. If the data is filled in correctly, click on add and then ''Next''. As WMS URL you can use the WMS url of the ''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' of the Nationaal Georegister from the previous assignment. The WMS url is the url with WMS in the link.<br />
# Choose in the drop down menu the layer ''Terreinen van archeologische waarde - provincie'' and click ''Next''.<br />
# In the following steps, proceed with ''Next'' and then ''Finish''. <br />
# After you have finished the wizard and given the overlay a proper name, can you tell the difference between the WFS and the WMS data? If not, click on the colored areas in both maps (WFS and WMS). Do you see a difference in the information in the hover panel?<br />
<br />
[[File:Archeological_map_wms.JPG|600px|center]]<br />
<br />
===Catalogue Service===<br />
In this step we are going to create a map (overlay) of all the monumental buildings in Delft. <br />
[[File:Monumental_buildings.JPG|600px|center]]<br />
# Start by reading what a [[CSW|CSW]] exactly is.<br />
# Open the Geo Data wizard and choose for type ''AREAS''. <br />
# In step 1 of the wizard, choose for: ''Search for data in a Catalog Service''. <br />
# Click on ''Select Catalog Service'' and choose ''ArcGIS online''.<br />
[[File:Catalog_service.JPG|600px|center]]<br />
# In the next screen you can type a keyword of the dataset you want to find. We are going to create a map of the monumental buildings in Delft. Think of a correct keyword to type and click on ''Search''. Remember the project owner of the data should match the location of your project. Why is that?<br />
[[File:Monument_csw.JPG|600px|center]]<br />
# Complete the wizard. Don't forget in step 5 to choose the correct attribute to base the name on.<br />
# Follow the previous steps for creating an Overlay.<br />
# Now your map of Monumental Buildings is finished.<br />
<br />
==Import vector data==<br />
In this section we are going to import [[Geo_Data|vector]] data from a file.<br />
To import data in the {{software}}, the file must be of the GeoJSON format. <br />
<br />
In the next assignment we are going to import two fictional datasets as objects in the 3D model.<br />
One dataset contains a [[spatial_plan|spatial plan]] with a road, an office, parking space and a park. The other dataset contains trees.<br />
<br />
====Office plan====<br />
* Read this [[GeoJSON#What_is_GeoJSON|section]] on the Wiki of what exactly a GeoJSON file is. <br />
* Mostly data is not available as a GeoJSON but for example as a Shapefile. We can create a GeoJSON file ourselves with a GIS. <br />
# In the zip folder you downloaded at the start of this tutorial are two .shp files. These are Shapefiles. Follow the [[GeoJSON#How_to_create_a_GeoJSON_file|steps]] to create a GeoJSON file in you preferred GIS. You can skip the part of modifying the attributes. <br />
# After you have created the two GeoJSON files, open the Geo Data Wizard. <br />
# Select as type ''Buildings''.<br />
[[File:Type_buildings.JPG|600px|center]]<br />
# Select in step 1 ''Import a GeoJSON file'' and choose the file: ''Office'' in the next step. <br />
# Click on Next in the following steps, choosing consequently the first option. In step 5 choose the correct column for the naming of the objects.<br />
#In step 7 we see a new step that we did not come across when choosing to import data as ''AREAS''. In this step you decide what kind of 3D object the data will be. Click on ''One Function'' if your dataset only consists of data of one type, for example a dataset with only buildings or only roads. If you have a file like we do with an office, road, parking space and building, choose ''Function Mapping''. <br />
# Choose first the default function by clicking on ''Select''. For this tutorial we choose as default function a function in the category Offices.<br />
# Then make sure the drop down menu is on ''Name'' and click on ''Add''. Choose for the Function fFlter 1 the Type column. Now check the other function box and click on ''Values''. Based on the data in the column Type, you can select a function. Select for example Park, click on ''Ok'' (the screen closes) en click on the button ''Select''. Choose from the Function list a park function. <br />
# Repeat the previous steps for the attributes ''Parkeerplaats'' and ''Weg''. We are now creating rules to base the mapping on. We do not have to create rules for every attribute, since we have set a default function. Think of what would happen if we had another feature in our dataset with for example Type:School.<br />
[[File:Function_mapping.JPG|600px|center]]<br />
# Click on Next. In step 8 we can also create a mapping for the Stakeholders. For example, we can assign the roads, park and parking space to the municipality and the office to the company stakeholder. The mapping is done in the same way as step 7. Create a mapping with at least two stakeholders.<br />
[[File:Stakeholders.JPG|600px|center]]<br />
# Finish the wizard. <br />
# Notice the new buildings are now in the 3D model<br />
[[File:Location_plan.JPG|400px|center]]<br />
[[File:New_plan_2.JPG|400px|center]]<br />
<br />
====Tree dataset====<br />
# Import the other dataset ''trees'' by repeating the previous steps for importing a GeoJSON file. <br />
# In step 2 of the wizard, notice that there are 10 points in the datset and no lines or polygons. In the {{software}} it is only possible to import polygons. Therefore, we can buffer the points to create (round polygons) for the trees. Set the buffer size on 1, so as not to create very large trunks and follow the rest of the wizard.<br />
[[File:Point_data_buffer.JPG|600px|center]]<br />
# How would you do the mapping in step 7? As ''One Function'' or a ''Function Mapping''?<br />
# After finishing the wizard, notice the new trees in the office location area.<br />
[[File:Trees.JPG|400px|center]]<br />
<br />
==Importing a 3D model==<br />
In the following steps we will replace the previous imported office building with a simple 3D model of a fictional office building. <br />
# There are a lot of formats for 3D models. In the {{software}} we use the I3S format for importing 3D models. Read [[I3S|here]] more about this format.<br />
# Open the Geo Data wizard and choose Buildings.<br />
# Choose in step 1 the option import an I3S SLPK file and choose in the next step the ''office_building.slpk'' file. The originally 3D CAD building model (in DWG file format) was transformed to a SLPK file. For more information, read [[How_to_create_a_SLPK_file|here]] the steps on how to create a SLPK file from different 3D file formats. <br />
[[File:I3s_step.PNG|600px|center]]<br />
4. Proceed with Next until step 4. In step 4, choose the first option to Update the 3D model of existing buildings. Now only the model will be updated, but the building will have the same function and attributes. <br />
[[File:Update_3D_model.PNG|600px|center]]<br />
5. Finish the wizard and notice the updated office building. <br />
<gallery mode="packed"><br />
File:Test_building.PNG|3D CAD building<br />
File:Office_building_demo.PNG|Building imported in the {{software}}<br />
</gallery><br />
See also the [[Demo_San_Francisco_Project|Demo San Francisco project]] for a project of San Francisco generated from, among others, [[I3S|I3S Scene Layer data]].<br />
<br />
==Importing raster data==<br />
For this part of the tutorial we use the ready prepared GeoTIFF Kd_Delft.tif. This file contains a selection of the layer ''doorlatendheid_laag 1'' from the [http://data.nhi.nu/National Hydrological Instrument]. They layer represents classes of hydraulic conductivity of the freatic groundwater layer; the ability of the layer to transport groundwater, in m<sup>2</sup>/day:<br />
<br />
{| class="wikitable"<br />
! class in GeoTIFF<br />
! kd [m<sup>2</sup>/day]<br />
|-<br />
|2<br />
|5-10<br />
|-<br />
|3<br />
|10-20<br />
|-<br />
|4<br />
|20-30<br />
|-<br />
|5<br />
|30-40<br />
|-<br />
|6<br />
|40-60<br />
|-<br />
|7<br />
|60-80<br />
|-<br />
|8<br />
|80-100<br />
|-<br />
|}<br />
<br />
If you finish the tutorial, the result should be as the picture below:<br />
<br />
[[File:GD_tuto_KD_Overlay.PNG|800px|center]]<br />
<br />
===Creating a GeoTIFF Overlay===<br />
Go to:<br />
{{Editor location|overlays}}<br />
and select Add Geo Tiff.<br />
<br />
Add the GeoTIFF ''Kd_Delft.tif'' in the following steps:<br />
# In the general-tab press ''Select GeoTIFF''<br />
# In the GeoTIFF Import Wizard, press ''Import new Geo Tiffs''in the bottom-right<br />
# Locate ''Kd_Delft.tif'' and press ''Open''<br />
# Make sure your newly imported GeoTIFF is selcted and press ''Apply''<br />
<br />
In the general-tab ''GeoTIFF:'' should refer to ''Kd_Delft.tif''. Now add a legend:<br />
# go to the legend tab<br />
# create a legend with the 7 classes as above, by:<br />
#* checking ''Has Custom Legend''<br />
#* adding 7 records (or removing if you have to many)<br />
#* adding values, descriptions and colors starting from the lowest record<br />
# if finished, go to the general-tab and press ''refresh grid''<br />
<br />
You should arrive at the overlay as shown in the picture above. Please check the following:<br />
* open ''Kd_Delft.tif'' in a GIS-editor (e.g. QGIS); review the presence of a NoData value and projection. If these are not present, the file will not be imported(!!)<br />
* open the GeoTIFF Import Wizard and notice the option ''overwrite CRS''. If your GeoTIFF does not contain projection info, you can use this option to specify a CRS (Coordinate Reference System). If the {{software}} has trouble projecting your projected GeoTIFF on the map, you can also use this option to overwrite the existing CRS.<br />
<br />
===Changing a DEM===<br />
For the purpose of this exercise, we will change the DEM with the ''Kd_delft.tiff'', previously imported. Note, it doesn't make sense to do so, but it is just for the purpose of the exercise.<br />
<br />
Note, if you change your DEM, you will loose the original DTM. Go To: <br />
{{Editor location|overlays}}<br />
<br />
And the Heightmap Overlay. Then:<br />
* change the grid-cell size to 1m<br />
* select DTM (where you will not see the elevation of houses)<br />
* export the DTM as a GeoTIFF<br />
<br />
Now we will import a different DEM. Go to:<br />
<br />
{{Editor location|import elevation}}<br />
<br />
And do the following:<br />
* Select ''Select elevation GeoTIFF''<br />
* Select ''kd_delft.tiff''<br />
* Press ''apply''<br />
<br />
The DTM should look as below:<br />
<br />
[[File:GD_tuto_KD_as_elevation.PNG|800px|center]]<br />
<br />
Now: <br />
* revert the DTM to the elevation model to its original state by re-importing the DEM you previously exported<br />
* make a GeoTIFF in QGIS covering a part of the project area, import it via ''Select elevation GeoTIFF'' and see how it mergens with the DTM</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=File:Naming2.JPG&diff=55149File:Naming2.JPG2023-09-07T13:53:00Z<p>Vincent@tygron.nl: </p>
<hr />
<div></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geo_Data_tutorial&diff=55148Geo Data tutorial2023-09-07T13:52:40Z<p>Vincent@tygron.nl: </p>
<hr />
<div>{{tutorial prerequisites<br />
| tutorial=This tutorial relies on base knowledge about the editor interface.<br />
| project=This tutorial will include the creation of a new project.<br />
<br />
| Download and unpack the content of this zip-file on your desktop for the necessary files: [//downloads.support.tygron.com/tutorials/tutorial_GeoData.zip tutorial_GeoData.zip]<br />
| Create a [[New Project Wizard#Videos|new project]] of Delft. For the exact location of the project, see the image below or use the ''project_location.geojson'' file (in the above zip-file) to define the project location. See [https://community.tygron.com/forum/discussion/219/new-feature-for-easier-selecting-a-new-project-area#latest this tip] on our forum for more information on how to use the GeoJSON file for selecting the location.<br />
}}<br />
<br />
==Getting Started==<br />
In this tutorial you will learn the different ways to import different types of data in your project:<br />
* data from Web services <br />
* vector data<br />
* 3D models<br />
* raster data<br />
<!--For this tutorial you will have to create a new project of the city of Delft in the Netherlands.--><br />
<br />
==Import data from Web services==<br />
In this section we are going to import data from a:<br />
* WFS (Web Feature Service) <br />
* WMS (Web Map Service)<br />
* CSW (Catalogue Service)<br />
<br />
===WFS===<br />
In this assignment you will create an Archeological Terrains Map. <br />
[[File:Archeological_map.JPG|600px|center]]<br />
<br />
# First read what exactly a [[WFS|Web Feature Service]] is. <br />
# Now we need to find data that is published as a WFS. For the Netherlands, a website to find open data is: [http://nationaalgeoregister.nl Nationaal Georegister]. Go to the Nationaal Georegister and search for the''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' dataset. Take a moment to read what this dataset is about. Then copy the WFS URL: this is the URL that contains WFS in the URL link.<br />
[[File:Search_ngr.JPG|500px|center]]<br />
<br><br />
<br><br />
[[File:Copy_wfs_url.JPG|500px|center]]<br />
<br />
# Start the Geo Data Wizard by clicking in the Editor on ''Geo import''. {{Editor location|Geo Import}}<br />
# Choose the correct type for importing the data. Since we are going to create a map which is equivalent to an overlay, choose as type: Areas. Read the [[Geo_Data_Wizard|Geo Data Wizard]] for more information about the differences between the import types.<br />
[[File:Import_areas.JPG|600px|center]]<br />
# In step 1 of the wizard, choose for ''Import a Web Feature Service''. <br />
# Click on ''add a new Feature Service'' and provide a custom name, Service Type (WFS_JSON) and URL of the WFS. After you have entered this data, click on ''add'' and then ''next''. <br />
[[File:Paste_wfs2.JPG|600px|center]]<br />
# In step 1.2 all the datasets that are published through this URL are shown (these are called layers). Choose from the drop down menu the layer: ''RCE_RIJKSMONUMENTEN_VLAK''. If this dataset is not in your project, an error message is given. What could be a reason that the data is not in your project? <br />
# In step 2 the location of the objects in your project area is shown. Click ''next''. <br />
# In step 3 we can filter the features and in step 4 adding as new areas or updating areas. Click 2 times on ''next''.<br />
# In step 5 we name the features. Click on: ''Based on specific Attribute'' and choose for the attribute for example''subcategorie''. Now the features will be named after their sub category.<br />
[[File:Naming2.JPG|600px|center]]<br />
# In step 6 the attributes that will be imported are selected. Only numerical attributes are imported in the {{software}}. These are by default checked. Why is the list of attributes shorter than the list was in step 5? Click on ''next''. <br />
# In step 7 click on ''Finish''. Now the Geo data wizard is finished and the data is imported.<br />
<br />
====Create an overlay====<br />
# In the Editor, go to Areas and notice that the areas you have imported are listed on the left side. Select one and notice that in the [[3D Visualization]] the corresponding area is highlighted. In the tab ''Attributes'' on the right side of the screen, notice that the attributes are imported as well. <br />
{{Editor location|areas}}<br />
[[File:View_area.JPG|600px|center]]<br />
# Since we don't want to go by these areas one by one to see the archeological value areas, we are going to create a map so we can see them in one view.<br />
Click therefore in the editor on overlays.<br />
{{Editor location|overlays}}<br />
# Add a new overlay by clicking in the bottom left corner on ''Add Areas''.<br />
# Notice a new overlay, named: ''Speciaal gebied'' is added. <br />
# Select this overlay and notice the new menu on the right side.<br />
[[File:Overlays_areas.JPG|600px|center]]<br />
# Give the new overlay a fitting name and check the areas belonging to the archeological value map. If there are a lot of areas, you can also click on the button in the bottom right corner on ''Add Areas with Attribute''. Here you can select a common attribute of these areas. Select the common attribute, for example ''MONUMENTNR'' and click on Add.<br />
[[File:Add_areas.JPG|600px|center]]<br />
<br />
===WMS===<br />
In this assignment we will also create an Archeological Terrains map. <br />
# Read first on the Wiki what a [[WMS|WMS]] exactly is.<br />
# Add an Image overlay by hovering over the overlays button and choose the add Image overlay.<br />
{{Editor location|Overlays}}<br />
# Notice that a new overlay (named Beeldlaag) is added. Change on the right side the name and then open the Configuration Wizard. <br />
# Select the second option: import from a Web Image Service<br />
# Select ''Add a new Image Service'' and provide a custom name, Service Type (WMS_IMAGE) and URL of the WMS. If the data is filled in correctly, click on add and then ''Next''. As WMS URL you can use the WMS url of the ''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' of the Nationaal Georegister from the previous assignment. The WMS url is the url with WMS in the link.<br />
# Choose in the drop down menu the layer ''Terreinen van archeologische waarde - provincie'' and click ''Next''.<br />
# In the following steps, proceed with ''Next'' and then ''Finish''. <br />
# After you have finished the wizard and given the overlay a proper name, can you tell the difference between the WFS and the WMS data? If not, click on the colored areas in both maps (WFS and WMS). Do you see a difference in the information in the hover panel?<br />
<br />
[[File:Archeological_map_wms.JPG|600px|center]]<br />
<br />
===Catalogue Service===<br />
In this step we are going to create a map (overlay) of all the monumental buildings in Delft. <br />
[[File:Monumental_buildings.JPG|600px|center]]<br />
# Start by reading what a [[CSW|CSW]] exactly is.<br />
# Open the Geo Data wizard and choose for type ''AREAS''. <br />
# In step 1 of the wizard, choose for: ''Search for data in a Catalog Service''. <br />
# Click on ''Select Catalog Service'' and choose ''ArcGIS online''.<br />
[[File:Catalog_service.JPG|600px|center]]<br />
# In the next screen you can type a keyword of the dataset you want to find. We are going to create a map of the monumental buildings in Delft. Think of a correct keyword to type and click on ''Search''. Remember the project owner of the data should match the location of your project. Why is that?<br />
[[File:Monument_csw.JPG|600px|center]]<br />
# Complete the wizard. Don't forget in step 5 to choose the correct attribute to base the name on.<br />
# Follow the previous steps for creating an Overlay.<br />
# Now your map of Monumental Buildings is finished.<br />
<br />
==Import vector data==<br />
In this section we are going to import [[Geo_Data|vector]] data from a file.<br />
To import data in the {{software}}, the file must be of the GeoJSON format. <br />
<br />
In the next assignment we are going to import two fictional datasets as objects in the 3D model.<br />
One dataset contains a [[spatial_plan|spatial plan]] with a road, an office, parking space and a park. The other dataset contains trees.<br />
<br />
====Office plan====<br />
* Read this [[GeoJSON#What_is_GeoJSON|section]] on the Wiki of what exactly a GeoJSON file is. <br />
* Mostly data is not available as a GeoJSON but for example as a Shapefile. We can create a GeoJSON file ourselves with a GIS. <br />
# In the zip folder you downloaded at the start of this tutorial are two .shp files. These are Shapefiles. Follow the [[GeoJSON#How_to_create_a_GeoJSON_file|steps]] to create a GeoJSON file in you preferred GIS. You can skip the part of modifying the attributes. <br />
# After you have created the two GeoJSON files, open the Geo Data Wizard. <br />
# Select as type ''Buildings''.<br />
[[File:Type_buildings.JPG|600px|center]]<br />
# Select in step 1 ''Import a GeoJSON file'' and choose the file: ''Office'' in the next step. <br />
# Click on Next in the following steps, choosing consequently the first option. In step 5 choose the correct column for the naming of the objects.<br />
#In step 7 we see a new step that we did not come across when choosing to import data as ''AREAS''. In this step you decide what kind of 3D object the data will be. Click on ''One Function'' if your dataset only consists of data of one type, for example a dataset with only buildings or only roads. If you have a file like we do with an office, road, parking space and building, choose ''Function Mapping''. <br />
# Choose first the default function by clicking on ''Select''. For this tutorial we choose as default function a function in the category Offices.<br />
# Then make sure the drop down menu is on ''Name'' and click on ''Add''. Choose for the Function fFlter 1 the Type column. Now check the other function box and click on ''Values''. Based on the data in the column Type, you can select a function. Select for example Park, click on ''Ok'' (the screen closes) en click on the button ''Select''. Choose from the Function list a park function. <br />
# Repeat the previous steps for the attributes ''Parkeerplaats'' and ''Weg''. We are now creating rules to base the mapping on. We do not have to create rules for every attribute, since we have set a default function. Think of what would happen if we had another feature in our dataset with for example Type:School.<br />
[[File:Function_mapping.JPG|600px|center]]<br />
# Click on Next. In step 8 we can also create a mapping for the Stakeholders. For example, we can assign the roads, park and parking space to the municipality and the office to the company stakeholder. The mapping is done in the same way as step 7. Create a mapping with at least two stakeholders.<br />
[[File:Stakeholders.JPG|600px|center]]<br />
# Finish the wizard. <br />
# Notice the new buildings are now in the 3D model<br />
[[File:Location_plan.JPG|400px|center]]<br />
[[File:New_plan_2.JPG|400px|center]]<br />
<br />
====Tree dataset====<br />
# Import the other dataset ''trees'' by repeating the previous steps for importing a GeoJSON file. <br />
# In step 2 of the wizard, notice that there are 10 points in the datset and no lines or polygons. In the {{software}} it is only possible to import polygons. Therefore, we can buffer the points to create (round polygons) for the trees. Set the buffer size on 1, so as not to create very large trunks and follow the rest of the wizard.<br />
[[File:Point_data_buffer.JPG|600px|center]]<br />
# How would you do the mapping in step 7? As ''One Function'' or a ''Function Mapping''?<br />
# After finishing the wizard, notice the new trees in the office location area.<br />
[[File:Trees.JPG|400px|center]]<br />
<br />
==Importing a 3D model==<br />
In the following steps we will replace the previous imported office building with a simple 3D model of a fictional office building. <br />
# There are a lot of formats for 3D models. In the {{software}} we use the I3S format for importing 3D models. Read [[I3S|here]] more about this format.<br />
# Open the Geo Data wizard and choose Buildings.<br />
# Choose in step 1 the option import an I3S SLPK file and choose in the next step the ''office_building.slpk'' file. The originally 3D CAD building model (in DWG file format) was transformed to a SLPK file. For more information, read [[How_to_create_a_SLPK_file|here]] the steps on how to create a SLPK file from different 3D file formats. <br />
[[File:I3s_step.PNG|600px|center]]<br />
4. Proceed with Next until step 4. In step 4, choose the first option to Update the 3D model of existing buildings. Now only the model will be updated, but the building will have the same function and attributes. <br />
[[File:Update_3D_model.PNG|600px|center]]<br />
5. Finish the wizard and notice the updated office building. <br />
<gallery mode="packed"><br />
File:Test_building.PNG|3D CAD building<br />
File:Office_building_demo.PNG|Building imported in the {{software}}<br />
</gallery><br />
See also the [[Demo_San_Francisco_Project|Demo San Francisco project]] for a project of San Francisco generated from, among others, [[I3S|I3S Scene Layer data]].<br />
<br />
==Importing raster data==<br />
For this part of the tutorial we use the ready prepared GeoTIFF Kd_Delft.tif. This file contains a selection of the layer ''doorlatendheid_laag 1'' from the [http://data.nhi.nu/National Hydrological Instrument]. They layer represents classes of hydraulic conductivity of the freatic groundwater layer; the ability of the layer to transport groundwater, in m<sup>2</sup>/day:<br />
<br />
{| class="wikitable"<br />
! class in GeoTIFF<br />
! kd [m<sup>2</sup>/day]<br />
|-<br />
|2<br />
|5-10<br />
|-<br />
|3<br />
|10-20<br />
|-<br />
|4<br />
|20-30<br />
|-<br />
|5<br />
|30-40<br />
|-<br />
|6<br />
|40-60<br />
|-<br />
|7<br />
|60-80<br />
|-<br />
|8<br />
|80-100<br />
|-<br />
|}<br />
<br />
If you finish the tutorial, the result should be as the picture below:<br />
<br />
[[File:GD_tuto_KD_Overlay.PNG|800px|center]]<br />
<br />
===Creating a GeoTIFF Overlay===<br />
Go to:<br />
{{Editor location|overlays}}<br />
and select Add Geo Tiff.<br />
<br />
Add the GeoTIFF ''Kd_Delft.tif'' in the following steps:<br />
# In the general-tab press ''Select GeoTIFF''<br />
# In the GeoTIFF Import Wizard, press ''Import new Geo Tiffs''in the bottom-right<br />
# Locate ''Kd_Delft.tif'' and press ''Open''<br />
# Make sure your newly imported GeoTIFF is selcted and press ''Apply''<br />
<br />
In the general-tab ''GeoTIFF:'' should refer to ''Kd_Delft.tif''. Now add a legend:<br />
# go to the legend tab<br />
# create a legend with the 7 classes as above, by:<br />
#* checking ''Has Custom Legend''<br />
#* adding 7 records (or removing if you have to many)<br />
#* adding values, descriptions and colors starting from the lowest record<br />
# if finished, go to the general-tab and press ''refresh grid''<br />
<br />
You should arrive at the overlay as shown in the picture above. Please check the following:<br />
* open ''Kd_Delft.tif'' in a GIS-editor (e.g. QGIS); review the presence of a NoData value and projection. If these are not present, the file will not be imported(!!)<br />
* open the GeoTIFF Import Wizard and notice the option ''overwrite CRS''. If your GeoTIFF does not contain projection info, you can use this option to specify a CRS (Coordinate Reference System). If the {{software}} has trouble projecting your projected GeoTIFF on the map, you can also use this option to overwrite the existing CRS.<br />
<br />
===Changing a DEM===<br />
For the purpose of this exercise, we will change the DEM with the ''Kd_delft.tiff'', previously imported. Note, it doesn't make sense to do so, but it is just for the purpose of the exercise.<br />
<br />
Note, if you change your DEM, you will loose the original DTM. Go To: <br />
{{Editor location|overlays}}<br />
<br />
And the Heightmap Overlay. Then:<br />
* change the grid-cell size to 1m<br />
* select DTM (where you will not see the elevation of houses)<br />
* export the DTM as a GeoTIFF<br />
<br />
Now we will import a different DEM. Go to:<br />
<br />
{{Editor location|import elevation}}<br />
<br />
And do the following:<br />
* Select ''Select elevation GeoTIFF''<br />
* Select ''kd_delft.tiff''<br />
* Press ''apply''<br />
<br />
The DTM should look as below:<br />
<br />
[[File:GD_tuto_KD_as_elevation.PNG|800px|center]]<br />
<br />
Now: <br />
* revert the DTM to the elevation model to its original state by re-importing the DEM you previously exported<br />
* make a GeoTIFF in QGIS covering a part of the project area, import it via ''Select elevation GeoTIFF'' and see how it mergens with the DTM</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geo_Data_tutorial&diff=55147Geo Data tutorial2023-09-07T13:48:06Z<p>Vincent@tygron.nl: /* WFS */</p>
<hr />
<div>{{tutorial prerequisites<br />
| tutorial=This tutorial relies on base knowledge about the editor interface.<br />
| project=This tutorial will include the creation of a new project.<br />
<br />
| Download and unpack the content of this zip-file on your desktop for the necessary files: [//downloads.support.tygron.com/tutorials/tutorial_GeoData.zip tutorial_GeoData.zip]<br />
| Create a [[New Project Wizard#Videos|new project]] of Delft. For the exact location of the project, see the image below or use the ''project_location.geojson'' file (in the above zip-file) to define the project location. See [https://community.tygron.com/forum/discussion/219/new-feature-for-easier-selecting-a-new-project-area#latest this tip] on our forum for more information on how to use the GeoJSON file for selecting the location.<br />
}}<br />
<br />
==Getting Started==<br />
In this tutorial you will learn the different ways to import different types of data in your project:<br />
* data from Web services <br />
* vector data<br />
* 3D models<br />
* raster data<br />
<!--For this tutorial you will have to create a new project of the city of Delft in the Netherlands.--><br />
<br />
==Import data from Web services==<br />
In this section we are going to import data from a:<br />
* WFS (Web Feature Service) <br />
* WMS (Web Map Service)<br />
* CSW (Catalogue Service)<br />
<br />
===WFS===<br />
In this assignment you will create an Archeological Terrains Map. <br />
[[File:Archeological_map.JPG|600px|center]]<br />
<br />
# First read what exactly a [[WFS|Web Feature Service]] is. <br />
# Now we need to find data that is published as a WFS. For the Netherlands, a website to find open data is: [http://nationaalgeoregister.nl Nationaal Georegister]. Go to the Nationaal Georegister and search for the''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' dataset. Take a moment to read what this dataset is about. Then copy the WFS URL: this is the URL that contains WFS in the URL link.<br />
[[File:Search_ngr.JPG|500px|center]]<br />
<br><br />
<br><br />
[[File:Copy_wfs_url.JPG|500px|center]]<br />
<br />
# Start the Geo Data Wizard by clicking in the Editor on ''Geo import''. {{Editor location|Geo Import}}<br />
# Choose the correct type for importing the data. Since we are going to create a map which is equivalent to an overlay, choose as type: Areas. Read the [[Geo_Data_Wizard|Geo Data Wizard]] for more information about the differences between the import types.<br />
[[File:Import_areas.JPG|600px|center]]<br />
# In step 1 of the wizard, choose for ''Import a Web Feature Service''. <br />
# Click on ''add a new Feature Service'' and provide a custom name, Service Type (WFS_JSON) and URL of the WFS. After you have entered this data, click on ''add'' and then ''next''. <br />
[[File:Paste_wfs2.JPG|600px|center]]<br />
# In step 1.2 all the datasets that are published through this URL are shown (these are called layers). Choose from the drop down menu the layer: ''RCE_RIJKSMONUMENTEN_VLAK''. If this dataset is not in your project, an error message is given. What could be a reason that the data is not in your project? <br />
# In step 2 the location of the objects in your project area is shown. Click ''next''. <br />
# In step 3 we can filter the features and in step 4 adding as new areas or updating areas. Click 2 times on ''next''.<br />
# In step 5 we name the features. Click on: ''Based on specific Attribute'' and choose for the attribute ''TOPONIEM''. Now the features will be named after their geographic entity.<br />
[[File:Naming2.JPG|600px|center]]<br />
# In step 6 the attributes that will be imported are selected. Only numerical attributes are imported in the {{software}}. These are by default checked. Why is the list of attributes shorter than the list was in step 5? Click on ''next''. <br />
# In step 7 click on ''Finish''. Now the Geo data wizard is finished and the data is imported.<br />
<br />
====Create an overlay====<br />
# In the Editor, go to Areas and notice that the areas you have imported are listed on the left side. Select one and notice that in the [[3D Visualization]] the corresponding area is highlighted. In the tab ''Attributes'' on the right side of the screen, notice that the attributes are imported as well. <br />
{{Editor location|areas}}<br />
[[File:View_area.JPG|600px|center]]<br />
# Since we don't want to go by these areas one by one to see the archeological value areas, we are going to create a map so we can see them in one view.<br />
Click therefore in the editor on overlays.<br />
{{Editor location|overlays}}<br />
# Add a new overlay by clicking in the bottom left corner on ''Add Areas''.<br />
# Notice a new overlay, named: ''Speciaal gebied'' is added. <br />
# Select this overlay and notice the new menu on the right side.<br />
[[File:Overlays_areas.JPG|600px|center]]<br />
# Give the new overlay a fitting name and check the areas belonging to the archeological value map. If there are a lot of areas, you can also click on the button in the bottom right corner on ''Add Areas with Attribute''. Here you can select a common attribute of these areas. Select the common attribute, for example ''MONUMENTNR'' and click on Add.<br />
[[File:Add_areas.JPG|600px|center]]<br />
<br />
===WMS===<br />
In this assignment we will also create an Archeological Terrains map. <br />
# Read first on the Wiki what a [[WMS|WMS]] exactly is.<br />
# Add an Image overlay by hovering over the overlays button and choose the add Image overlay.<br />
{{Editor location|Overlays}}<br />
# Notice that a new overlay (named Beeldlaag) is added. Change on the right side the name and then open the Configuration Wizard. <br />
# Select the second option: import from a Web Image Service<br />
# Select ''Add a new Image Service'' and provide a custom name, Service Type (WMS_IMAGE) and URL of the WMS. If the data is filled in correctly, click on add and then ''Next''. As WMS URL you can use the WMS url of the ''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' of the Nationaal Georegister from the previous assignment. The WMS url is the url with WMS in the link.<br />
# Choose in the drop down menu the layer ''Terreinen van archeologische waarde - provincie'' and click ''Next''.<br />
# In the following steps, proceed with ''Next'' and then ''Finish''. <br />
# After you have finished the wizard and given the overlay a proper name, can you tell the difference between the WFS and the WMS data? If not, click on the colored areas in both maps (WFS and WMS). Do you see a difference in the information in the hover panel?<br />
<br />
[[File:Archeological_map_wms.JPG|600px|center]]<br />
<br />
===Catalogue Service===<br />
In this step we are going to create a map (overlay) of all the monumental buildings in Delft. <br />
[[File:Monumental_buildings.JPG|600px|center]]<br />
# Start by reading what a [[CSW|CSW]] exactly is.<br />
# Open the Geo Data wizard and choose for type ''AREAS''. <br />
# In step 1 of the wizard, choose for: ''Search for data in a Catalog Service''. <br />
# Click on ''Select Catalog Service'' and choose ''ArcGIS online''.<br />
[[File:Catalog_service.JPG|600px|center]]<br />
# In the next screen you can type a keyword of the dataset you want to find. We are going to create a map of the monumental buildings in Delft. Think of a correct keyword to type and click on ''Search''. Remember the project owner of the data should match the location of your project. Why is that?<br />
[[File:Monument_csw.JPG|600px|center]]<br />
# Complete the wizard. Don't forget in step 5 to choose the correct attribute to base the name on.<br />
# Follow the previous steps for creating an Overlay.<br />
# Now your map of Monumental Buildings is finished.<br />
<br />
==Import vector data==<br />
In this section we are going to import [[Geo_Data|vector]] data from a file.<br />
To import data in the {{software}}, the file must be of the GeoJSON format. <br />
<br />
In the next assignment we are going to import two fictional datasets as objects in the 3D model.<br />
One dataset contains a [[spatial_plan|spatial plan]] with a road, an office, parking space and a park. The other dataset contains trees.<br />
<br />
====Office plan====<br />
* Read this [[GeoJSON#What_is_GeoJSON|section]] on the Wiki of what exactly a GeoJSON file is. <br />
* Mostly data is not available as a GeoJSON but for example as a Shapefile. We can create a GeoJSON file ourselves with a GIS. <br />
# In the zip folder you downloaded at the start of this tutorial are two .shp files. These are Shapefiles. Follow the [[GeoJSON#How_to_create_a_GeoJSON_file|steps]] to create a GeoJSON file in you preferred GIS. You can skip the part of modifying the attributes. <br />
# After you have created the two GeoJSON files, open the Geo Data Wizard. <br />
# Select as type ''Buildings''.<br />
[[File:Type_buildings.JPG|600px|center]]<br />
# Select in step 1 ''Import a GeoJSON file'' and choose the file: ''Office'' in the next step. <br />
# Click on Next in the following steps, choosing consequently the first option. In step 5 choose the correct column for the naming of the objects.<br />
#In step 7 we see a new step that we did not come across when choosing to import data as ''AREAS''. In this step you decide what kind of 3D object the data will be. Click on ''One Function'' if your dataset only consists of data of one type, for example a dataset with only buildings or only roads. If you have a file like we do with an office, road, parking space and building, choose ''Function Mapping''. <br />
# Choose first the default function by clicking on ''Select''. For this tutorial we choose as default function a function in the category Offices.<br />
# Then make sure the drop down menu is on ''Name'' and click on ''Add''. Choose for the Function fFlter 1 the Type column. Now check the other function box and click on ''Values''. Based on the data in the column Type, you can select a function. Select for example Park, click on ''Ok'' (the screen closes) en click on the button ''Select''. Choose from the Function list a park function. <br />
# Repeat the previous steps for the attributes ''Parkeerplaats'' and ''Weg''. We are now creating rules to base the mapping on. We do not have to create rules for every attribute, since we have set a default function. Think of what would happen if we had another feature in our dataset with for example Type:School.<br />
[[File:Function_mapping.JPG|600px|center]]<br />
# Click on Next. In step 8 we can also create a mapping for the Stakeholders. For example, we can assign the roads, park and parking space to the municipality and the office to the company stakeholder. The mapping is done in the same way as step 7. Create a mapping with at least two stakeholders.<br />
[[File:Stakeholders.JPG|600px|center]]<br />
# Finish the wizard. <br />
# Notice the new buildings are now in the 3D model<br />
[[File:Location_plan.JPG|400px|center]]<br />
[[File:New_plan_2.JPG|400px|center]]<br />
<br />
====Tree dataset====<br />
# Import the other dataset ''trees'' by repeating the previous steps for importing a GeoJSON file. <br />
# In step 2 of the wizard, notice that there are 10 points in the datset and no lines or polygons. In the {{software}} it is only possible to import polygons. Therefore, we can buffer the points to create (round polygons) for the trees. Set the buffer size on 1, so as not to create very large trunks and follow the rest of the wizard.<br />
[[File:Point_data_buffer.JPG|600px|center]]<br />
# How would you do the mapping in step 7? As ''One Function'' or a ''Function Mapping''?<br />
# After finishing the wizard, notice the new trees in the office location area.<br />
[[File:Trees.JPG|400px|center]]<br />
<br />
==Importing a 3D model==<br />
In the following steps we will replace the previous imported office building with a simple 3D model of a fictional office building. <br />
# There are a lot of formats for 3D models. In the {{software}} we use the I3S format for importing 3D models. Read [[I3S|here]] more about this format.<br />
# Open the Geo Data wizard and choose Buildings.<br />
# Choose in step 1 the option import an I3S SLPK file and choose in the next step the ''office_building.slpk'' file. The originally 3D CAD building model (in DWG file format) was transformed to a SLPK file. For more information, read [[How_to_create_a_SLPK_file|here]] the steps on how to create a SLPK file from different 3D file formats. <br />
[[File:I3s_step.PNG|600px|center]]<br />
4. Proceed with Next until step 4. In step 4, choose the first option to Update the 3D model of existing buildings. Now only the model will be updated, but the building will have the same function and attributes. <br />
[[File:Update_3D_model.PNG|600px|center]]<br />
5. Finish the wizard and notice the updated office building. <br />
<gallery mode="packed"><br />
File:Test_building.PNG|3D CAD building<br />
File:Office_building_demo.PNG|Building imported in the {{software}}<br />
</gallery><br />
See also the [[Demo_San_Francisco_Project|Demo San Francisco project]] for a project of San Francisco generated from, among others, [[I3S|I3S Scene Layer data]].<br />
<br />
==Importing raster data==<br />
For this part of the tutorial we use the ready prepared GeoTIFF Kd_Delft.tif. This file contains a selection of the layer ''doorlatendheid_laag 1'' from the [http://data.nhi.nu/National Hydrological Instrument]. They layer represents classes of hydraulic conductivity of the freatic groundwater layer; the ability of the layer to transport groundwater, in m<sup>2</sup>/day:<br />
<br />
{| class="wikitable"<br />
! class in GeoTIFF<br />
! kd [m<sup>2</sup>/day]<br />
|-<br />
|2<br />
|5-10<br />
|-<br />
|3<br />
|10-20<br />
|-<br />
|4<br />
|20-30<br />
|-<br />
|5<br />
|30-40<br />
|-<br />
|6<br />
|40-60<br />
|-<br />
|7<br />
|60-80<br />
|-<br />
|8<br />
|80-100<br />
|-<br />
|}<br />
<br />
If you finish the tutorial, the result should be as the picture below:<br />
<br />
[[File:GD_tuto_KD_Overlay.PNG|800px|center]]<br />
<br />
===Creating a GeoTIFF Overlay===<br />
Go to:<br />
{{Editor location|overlays}}<br />
and select Add Geo Tiff.<br />
<br />
Add the GeoTIFF ''Kd_Delft.tif'' in the following steps:<br />
# In the general-tab press ''Select GeoTIFF''<br />
# In the GeoTIFF Import Wizard, press ''Import new Geo Tiffs''in the bottom-right<br />
# Locate ''Kd_Delft.tif'' and press ''Open''<br />
# Make sure your newly imported GeoTIFF is selcted and press ''Apply''<br />
<br />
In the general-tab ''GeoTIFF:'' should refer to ''Kd_Delft.tif''. Now add a legend:<br />
# go to the legend tab<br />
# create a legend with the 7 classes as above, by:<br />
#* checking ''Has Custom Legend''<br />
#* adding 7 records (or removing if you have to many)<br />
#* adding values, descriptions and colors starting from the lowest record<br />
# if finished, go to the general-tab and press ''refresh grid''<br />
<br />
You should arrive at the overlay as shown in the picture above. Please check the following:<br />
* open ''Kd_Delft.tif'' in a GIS-editor (e.g. QGIS); review the presence of a NoData value and projection. If these are not present, the file will not be imported(!!)<br />
* open the GeoTIFF Import Wizard and notice the option ''overwrite CRS''. If your GeoTIFF does not contain projection info, you can use this option to specify a CRS (Coordinate Reference System). If the {{software}} has trouble projecting your projected GeoTIFF on the map, you can also use this option to overwrite the existing CRS.<br />
<br />
===Changing a DEM===<br />
For the purpose of this exercise, we will change the DEM with the ''Kd_delft.tiff'', previously imported. Note, it doesn't make sense to do so, but it is just for the purpose of the exercise.<br />
<br />
Note, if you change your DEM, you will loose the original DTM. Go To: <br />
{{Editor location|overlays}}<br />
<br />
And the Heightmap Overlay. Then:<br />
* change the grid-cell size to 1m<br />
* select DTM (where you will not see the elevation of houses)<br />
* export the DTM as a GeoTIFF<br />
<br />
Now we will import a different DEM. Go to:<br />
<br />
{{Editor location|import elevation}}<br />
<br />
And do the following:<br />
* Select ''Select elevation GeoTIFF''<br />
* Select ''kd_delft.tiff''<br />
* Press ''apply''<br />
<br />
The DTM should look as below:<br />
<br />
[[File:GD_tuto_KD_as_elevation.PNG|800px|center]]<br />
<br />
Now: <br />
* revert the DTM to the elevation model to its original state by re-importing the DEM you previously exported<br />
* make a GeoTIFF in QGIS covering a part of the project area, import it via ''Select elevation GeoTIFF'' and see how it mergens with the DTM</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=File:Paste_wfs2.JPG&diff=55143File:Paste wfs2.JPG2023-09-05T14:22:19Z<p>Vincent@tygron.nl: </p>
<hr />
<div></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geo_Data_tutorial&diff=55142Geo Data tutorial2023-09-05T14:22:05Z<p>Vincent@tygron.nl: /* WFS */</p>
<hr />
<div>{{tutorial prerequisites<br />
| tutorial=This tutorial relies on base knowledge about the editor interface.<br />
| project=This tutorial will include the creation of a new project.<br />
<br />
| Download and unpack the content of this zip-file on your desktop for the necessary files: [//downloads.support.tygron.com/tutorials/tutorial_GeoData.zip tutorial_GeoData.zip]<br />
| Create a [[New Project Wizard#Videos|new project]] of Delft. For the exact location of the project, see the image below or use the ''project_location.geojson'' file (in the above zip-file) to define the project location. See [https://community.tygron.com/forum/discussion/219/new-feature-for-easier-selecting-a-new-project-area#latest this tip] on our forum for more information on how to use the GeoJSON file for selecting the location.<br />
}}<br />
<br />
==Getting Started==<br />
In this tutorial you will learn the different ways to import different types of data in your project:<br />
* data from Web services <br />
* vector data<br />
* 3D models<br />
* raster data<br />
<!--For this tutorial you will have to create a new project of the city of Delft in the Netherlands.--><br />
<br />
==Import data from Web services==<br />
In this section we are going to import data from a:<br />
* WFS (Web Feature Service) <br />
* WMS (Web Map Service)<br />
* CSW (Catalogue Service)<br />
<br />
===WFS===<br />
In this assignment you will create an Archeological Terrains Map. <br />
[[File:Archeological_map.JPG|600px|center]]<br />
<br />
# First read what exactly a [[WFS|Web Feature Service]] is. <br />
# Now we need to find data that is published as a WFS. For the Netherlands, a website to find open data is: [http://nationaalgeoregister.nl Nationaal Georegister]. Go to the Nationaal Georegister and search for the''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' dataset. Take a moment to read what this dataset is about. Then copy the WFS URL: this is the URL that contains WFS in the URL link.<br />
[[File:Search_ngr.JPG|500px|center]]<br />
<br><br />
<br><br />
[[File:Copy_wfs_url.JPG|500px|center]]<br />
<br />
# Start the Geo Data Wizard by clicking in the Editor on ''Geo import''. {{Editor location|Geo Import}}<br />
# Choose the correct type for importing the data. Since we are going to create a map which is equivalent to an overlay, choose as type: Areas. Read the [[Geo_Data_Wizard|Geo Data Wizard]] for more information about the differences between the import types.<br />
[[File:Import_areas.JPG|600px|center]]<br />
# In step 1 of the wizard, choose for ''Import a Web Feature Service''. <br />
# Click on ''add a new Feature Service'' and provide a custom name, Service Type (WFS_JSON) and URL of the WFS. After you have entered this data, click on ''add'' and then ''next''. <br />
[[File:Paste_wfs2.JPG|600px|center]]<br />
# In step 1.2 all the datasets that are published through this URL are shown (these are called layers). Choose from the drop down menu the layer: ''Monumenten''. If this dataset is not in your project, an error message is given. What could be a reason that the data is not in your project? <br />
# In step 2 the location of the objects in your project area is shown. Click ''next''. <br />
# In step 3 we can filter the features and in step 4 adding as new areas or updating areas. Click 2 times on ''next''.<br />
# In step 5 we name the features. Click on: ''Based on specific Attribute'' and choose for the attribute ''TOPONIEM''. Now the features will be named after their geographic entity.<br />
[[File:Naming.JPG|600px|center]]<br />
# In step 6 the attributes that will be imported are selected. Only numerical attributes are imported in the {{software}}. These are by default checked. Why is the list of attributes shorter than the list was in step 5? Click on ''next''. <br />
# In step 7 click on ''Finish''. Now the Geo data wizard is finished and the data is imported.<br />
<br />
====Create an overlay====<br />
# In the Editor, go to Areas and notice that the areas you have imported are listed on the left side. Select one and notice that in the [[3D Visualization]] the corresponding area is highlighted. In the tab ''Attributes'' on the right side of the screen, notice that the attributes are imported as well. <br />
{{Editor location|areas}}<br />
[[File:View_area.JPG|600px|center]]<br />
# Since we don't want to go by these areas one by one to see the archeological value areas, we are going to create a map so we can see them in one view.<br />
Click therefore in the editor on overlays.<br />
{{Editor location|overlays}}<br />
# Add a new overlay by clicking in the bottom left corner on ''Add Areas''.<br />
# Notice a new overlay, named: ''Speciaal gebied'' is added. <br />
# Select this overlay and notice the new menu on the right side.<br />
[[File:Overlays_areas.JPG|600px|center]]<br />
# Give the new overlay a fitting name and check the areas belonging to the archeological value map. If there are a lot of areas, you can also click on the button in the bottom right corner on ''Add Areas with Attribute''. Here you can select a common attribute of these areas. Select the common attribute, for example ''MONUMENTNR'' and click on Add.<br />
[[File:Add_areas.JPG|600px|center]]<br />
<br />
===WMS===<br />
In this assignment we will also create an Archeological Terrains map. <br />
# Read first on the Wiki what a [[WMS|WMS]] exactly is.<br />
# Add an Image overlay by hovering over the overlays button and choose the add Image overlay.<br />
{{Editor location|Overlays}}<br />
# Notice that a new overlay (named Beeldlaag) is added. Change on the right side the name and then open the Configuration Wizard. <br />
# Select the second option: import from a Web Image Service<br />
# Select ''Add a new Image Service'' and provide a custom name, Service Type (WMS_IMAGE) and URL of the WMS. If the data is filled in correctly, click on add and then ''Next''. As WMS URL you can use the WMS url of the ''Cultuurhistorische Hoofdstructuur: Archeologische terreinen van provinciaal belang'' of the Nationaal Georegister from the previous assignment. The WMS url is the url with WMS in the link.<br />
# Choose in the drop down menu the layer ''Terreinen van archeologische waarde - provincie'' and click ''Next''.<br />
# In the following steps, proceed with ''Next'' and then ''Finish''. <br />
# After you have finished the wizard and given the overlay a proper name, can you tell the difference between the WFS and the WMS data? If not, click on the colored areas in both maps (WFS and WMS). Do you see a difference in the information in the hover panel?<br />
<br />
[[File:Archeological_map_wms.JPG|600px|center]]<br />
<br />
===Catalogue Service===<br />
In this step we are going to create a map (overlay) of all the monumental buildings in Delft. <br />
[[File:Monumental_buildings.JPG|600px|center]]<br />
# Start by reading what a [[CSW|CSW]] exactly is.<br />
# Open the Geo Data wizard and choose for type ''AREAS''. <br />
# In step 1 of the wizard, choose for: ''Search for data in a Catalog Service''. <br />
# Click on ''Select Catalog Service'' and choose ''ArcGIS online''.<br />
[[File:Catalog_service.JPG|600px|center]]<br />
# In the next screen you can type a keyword of the dataset you want to find. We are going to create a map of the monumental buildings in Delft. Think of a correct keyword to type and click on ''Search''. Remember the project owner of the data should match the location of your project. Why is that?<br />
[[File:Monument_csw.JPG|600px|center]]<br />
# Complete the wizard. Don't forget in step 5 to choose the correct attribute to base the name on.<br />
# Follow the previous steps for creating an Overlay.<br />
# Now your map of Monumental Buildings is finished.<br />
<br />
==Import vector data==<br />
In this section we are going to import [[Geo_Data|vector]] data from a file.<br />
To import data in the {{software}}, the file must be of the GeoJSON format. <br />
<br />
In the next assignment we are going to import two fictional datasets as objects in the 3D model.<br />
One dataset contains a [[spatial_plan|spatial plan]] with a road, an office, parking space and a park. The other dataset contains trees.<br />
<br />
====Office plan====<br />
* Read this [[GeoJSON#What_is_GeoJSON|section]] on the Wiki of what exactly a GeoJSON file is. <br />
* Mostly data is not available as a GeoJSON but for example as a Shapefile. We can create a GeoJSON file ourselves with a GIS. <br />
# In the zip folder you downloaded at the start of this tutorial are two .shp files. These are Shapefiles. Follow the [[GeoJSON#How_to_create_a_GeoJSON_file|steps]] to create a GeoJSON file in you preferred GIS. You can skip the part of modifying the attributes. <br />
# After you have created the two GeoJSON files, open the Geo Data Wizard. <br />
# Select as type ''Buildings''.<br />
[[File:Type_buildings.JPG|600px|center]]<br />
# Select in step 1 ''Import a GeoJSON file'' and choose the file: ''Office'' in the next step. <br />
# Click on Next in the following steps, choosing consequently the first option. In step 5 choose the correct column for the naming of the objects.<br />
#In step 7 we see a new step that we did not come across when choosing to import data as ''AREAS''. In this step you decide what kind of 3D object the data will be. Click on ''One Function'' if your dataset only consists of data of one type, for example a dataset with only buildings or only roads. If you have a file like we do with an office, road, parking space and building, choose ''Function Mapping''. <br />
# Choose first the default function by clicking on ''Select''. For this tutorial we choose as default function a function in the category Offices.<br />
# Then make sure the drop down menu is on ''Name'' and click on ''Add''. Choose for the Function fFlter 1 the Type column. Now check the other function box and click on ''Values''. Based on the data in the column Type, you can select a function. Select for example Park, click on ''Ok'' (the screen closes) en click on the button ''Select''. Choose from the Function list a park function. <br />
# Repeat the previous steps for the attributes ''Parkeerplaats'' and ''Weg''. We are now creating rules to base the mapping on. We do not have to create rules for every attribute, since we have set a default function. Think of what would happen if we had another feature in our dataset with for example Type:School.<br />
[[File:Function_mapping.JPG|600px|center]]<br />
# Click on Next. In step 8 we can also create a mapping for the Stakeholders. For example, we can assign the roads, park and parking space to the municipality and the office to the company stakeholder. The mapping is done in the same way as step 7. Create a mapping with at least two stakeholders.<br />
[[File:Stakeholders.JPG|600px|center]]<br />
# Finish the wizard. <br />
# Notice the new buildings are now in the 3D model<br />
[[File:Location_plan.JPG|400px|center]]<br />
[[File:New_plan_2.JPG|400px|center]]<br />
<br />
====Tree dataset====<br />
# Import the other dataset ''trees'' by repeating the previous steps for importing a GeoJSON file. <br />
# In step 2 of the wizard, notice that there are 10 points in the datset and no lines or polygons. In the {{software}} it is only possible to import polygons. Therefore, we can buffer the points to create (round polygons) for the trees. Set the buffer size on 1, so as not to create very large trunks and follow the rest of the wizard.<br />
[[File:Point_data_buffer.JPG|600px|center]]<br />
# How would you do the mapping in step 7? As ''One Function'' or a ''Function Mapping''?<br />
# After finishing the wizard, notice the new trees in the office location area.<br />
[[File:Trees.JPG|400px|center]]<br />
<br />
==Importing a 3D model==<br />
In the following steps we will replace the previous imported office building with a simple 3D model of a fictional office building. <br />
# There are a lot of formats for 3D models. In the {{software}} we use the I3S format for importing 3D models. Read [[I3S|here]] more about this format.<br />
# Open the Geo Data wizard and choose Buildings.<br />
# Choose in step 1 the option import an I3S SLPK file and choose in the next step the ''office_building.slpk'' file. The originally 3D CAD building model (in DWG file format) was transformed to a SLPK file. For more information, read [[How_to_create_a_SLPK_file|here]] the steps on how to create a SLPK file from different 3D file formats. <br />
[[File:I3s_step.PNG|600px|center]]<br />
4. Proceed with Next until step 4. In step 4, choose the first option to Update the 3D model of existing buildings. Now only the model will be updated, but the building will have the same function and attributes. <br />
[[File:Update_3D_model.PNG|600px|center]]<br />
5. Finish the wizard and notice the updated office building. <br />
<gallery mode="packed"><br />
File:Test_building.PNG|3D CAD building<br />
File:Office_building_demo.PNG|Building imported in the {{software}}<br />
</gallery><br />
See also the [[Demo_San_Francisco_Project|Demo San Francisco project]] for a project of San Francisco generated from, among others, [[I3S|I3S Scene Layer data]].<br />
<br />
==Importing raster data==<br />
For this part of the tutorial we use the ready prepared GeoTIFF Kd_Delft.tif. This file contains a selection of the layer ''doorlatendheid_laag 1'' from the [http://data.nhi.nu/National Hydrological Instrument]. They layer represents classes of hydraulic conductivity of the freatic groundwater layer; the ability of the layer to transport groundwater, in m<sup>2</sup>/day:<br />
<br />
{| class="wikitable"<br />
! class in GeoTIFF<br />
! kd [m<sup>2</sup>/day]<br />
|-<br />
|2<br />
|5-10<br />
|-<br />
|3<br />
|10-20<br />
|-<br />
|4<br />
|20-30<br />
|-<br />
|5<br />
|30-40<br />
|-<br />
|6<br />
|40-60<br />
|-<br />
|7<br />
|60-80<br />
|-<br />
|8<br />
|80-100<br />
|-<br />
|}<br />
<br />
If you finish the tutorial, the result should be as the picture below:<br />
<br />
[[File:GD_tuto_KD_Overlay.PNG|800px|center]]<br />
<br />
===Creating a GeoTIFF Overlay===<br />
Go to:<br />
{{Editor location|overlays}}<br />
and select Add Geo Tiff.<br />
<br />
Add the GeoTIFF ''Kd_Delft.tif'' in the following steps:<br />
# In the general-tab press ''Select GeoTIFF''<br />
# In the GeoTIFF Import Wizard, press ''Import new Geo Tiffs''in the bottom-right<br />
# Locate ''Kd_Delft.tif'' and press ''Open''<br />
# Make sure your newly imported GeoTIFF is selcted and press ''Apply''<br />
<br />
In the general-tab ''GeoTIFF:'' should refer to ''Kd_Delft.tif''. Now add a legend:<br />
# go to the legend tab<br />
# create a legend with the 7 classes as above, by:<br />
#* checking ''Has Custom Legend''<br />
#* adding 7 records (or removing if you have to many)<br />
#* adding values, descriptions and colors starting from the lowest record<br />
# if finished, go to the general-tab and press ''refresh grid''<br />
<br />
You should arrive at the overlay as shown in the picture above. Please check the following:<br />
* open ''Kd_Delft.tif'' in a GIS-editor (e.g. QGIS); review the presence of a NoData value and projection. If these are not present, the file will not be imported(!!)<br />
* open the GeoTIFF Import Wizard and notice the option ''overwrite CRS''. If your GeoTIFF does not contain projection info, you can use this option to specify a CRS (Coordinate Reference System). If the {{software}} has trouble projecting your projected GeoTIFF on the map, you can also use this option to overwrite the existing CRS.<br />
<br />
===Changing a DEM===<br />
For the purpose of this exercise, we will change the DEM with the ''Kd_delft.tiff'', previously imported. Note, it doesn't make sense to do so, but it is just for the purpose of the exercise.<br />
<br />
Note, if you change your DEM, you will loose the original DTM. Go To: <br />
{{Editor location|overlays}}<br />
<br />
And the Heightmap Overlay. Then:<br />
* change the grid-cell size to 1m<br />
* select DTM (where you will not see the elevation of houses)<br />
* export the DTM as a GeoTIFF<br />
<br />
Now we will import a different DEM. Go to:<br />
<br />
{{Editor location|import elevation}}<br />
<br />
And do the following:<br />
* Select ''Select elevation GeoTIFF''<br />
* Select ''kd_delft.tiff''<br />
* Press ''apply''<br />
<br />
The DTM should look as below:<br />
<br />
[[File:GD_tuto_KD_as_elevation.PNG|800px|center]]<br />
<br />
Now: <br />
* revert the DTM to the elevation model to its original state by re-importing the DEM you previously exported<br />
* make a GeoTIFF in QGIS covering a part of the project area, import it via ''Select elevation GeoTIFF'' and see how it mergens with the DTM</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Project_Sources&diff=54986Project Sources2023-08-10T13:41:15Z<p>Vincent@tygron.nl: /* Default sources */</p>
<hr />
<div>Project sources are the [[Geo Data]] sets that can be used by (geo) plugins to generate and build up a project in the {{software}}. Project Sources are stored as [[Source]]s in your project.<br />
Furthermore, all the additional data users import into a project are tagged with new Source as well.<br />
<br />
==Default sources==<br />
The table below contains the datasets that are automatically accessed, depending on the selected location, to create a new project. When selecting a location outside The Netherlands it is more likely that some [[Geo Data]] should be provided manually, which can done using a [[Template Project]] with one or more [[Geo Plugin]]s. <br />
<br />
{| class="wikitable"<br />
|-<br />
! (Open) Dataset<br />
! Description<br />
! Coverage<br />
! (Connection) Source<br />
! More information<br />
|-<br />
| {{anchor|BGT|BGT}}<br />
| Basisregistratie Grootschalige Topografie: Base Register containining the topography of the Netherlands. The dataset is very detailed and contains for instance roads, parks, trees, water surfaces and street objects. <br />
| Netherlands<br />
| {{anchor|PDOK<br />
| https://www.kadaster.nl/bgt; https://www.pdok.nl/introductie/-/article/basisregistratie-grootschalige-topografie-bgt-<br />
|-<br />
| {{anchor|BAG|BAG}}<br />
| Basisregistraties Adressen en Gebouwen: Base Register containing data about buildings and addresses such as function, construction year, size and the geometry of the buildings.<br />
| Netherlands.<br />
| PDOK<br />
| https://www.kadaster.nl/basisregistratie-adressen-en-gebouwen<br />
|-<br />
| {{anchor|BRO|BRO}}<br />
| Basisregistratie Ondergrond: Base Register containing detailed subsurface data. <br />
| Netherlands<br />
| PDOK<br />
| https://www.basisregistratieondergrond.nl/ <br />
|-<br />
| {{anchor|World Imagery|World Imagery}}<br />
| [[Satellite map]] used as base map for the [[height map]] in the [[3D Visualization]] and used to identify rooftop colors.<br />
| Worldwide<br />
| ESRI<br />
| https://services.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer/0 <br />
|-<br />
| {{anchor|Ocean Basemap|Ocean Basemap}}<br />
| Basemap with ocean data, including locations of water bodies and their names. Used to determine the location of water bodies worldwide. <br />
| Worldwide<br />
| ESRI<br />
| https://services.arcgisonline.com/arcgis/rest/services/Ocean_Basemap/MapServer<br />
|-<br />
| {{anchor|Terrain|Terrain}}<br />
| Digital Terrain Model (DTM): the terrain height of the bare ground without for example buildings, trees and other objects. See for more information the [[elevation model]] page. <br />
| Worldwide <br />
| ESRI <br />
| http://www.arcgis.com/home/item.html?id=58a541efc59545e6b7137f961d7de883<br />
|-<br />
| {{anchor|AHN|AHN}}<br />
| Actueel Hoogtebestand Nederland. By default AHN3 is used. We use the Digital Surface Model (DSM, the terrain height including buildings, trees and other objects) and the Digital Terrain Model (DTM, the terrain height of the bare ground) combined with the Terrain data above. For more information, see [[elevation model]]. <br />
| Netherlands<br />
| Nationaal Georegister<br />
| https://www.ahn.nl/<br />
|-<br />
| {{anchor|CBS Wijk- en Buurtkaart|CBS Wijk- en Buurtkaart}}<br />
| The CBS Wijk- en Buurtkaart (2017) contains the geometry of the division in neighborhoods and statistical data related to those neighborhoods.<br />
| Netherlands<br />
| PDOK<br />
| https://www.cbs.nl/nl-nl/dossier/nederland-regionaal/geografische%20data/wijk-en-buurtkaart-2017 <br />
|-<br />
| {{anchor|Ruimtelijke plannen|Ruimtelijke plannen}}<br />
| Ruimtelijke plannen are the offical published spatial plans/zoning plans.<br />
| Netherlands<br />
| Ruimtelijke Plannen<br />
| http://www.ruimtelijkeplannen.nl/web-roo/roo/index<br />
|-<br />
| {{anchor|Top10NL|Top10NL}}<br />
| Topographical dataset, used as an addition to the BGT data. <br />
| Netherlands<br />
| Tygron / PDOK<br />
| https://www.kadaster.nl/-/top10nl <br />
|-<br />
| {{anchor|NWB|NWB}} <br />
| The Nationaal Wegen Bestand is a dataset with the (name of) public roads in the Netherlands.<br />
| Netherlands<br />
| PDOK<br />
| https://www.pdok.nl/introductie/-/article/nationaal-wegen-bestand-nwb- <br />
|-<br />
| {{anchor|NSL|NSL}} <br />
| The NSL (Nationaal Samenwerkingsprogramma Luchtkwaliteit) contains data delivered by municipalities from their traffic models. For instance data such as road type, the tree factor, number of lanes, direction of traffic and traffic speed. <br />
| Netherlands<br />
| Rijksoverheid<br />
| https://www.cimlk.nl/documentatie/ <br>See also: [[Traffic Plugin#NSL|Traffic Plugin]]<br />
|-<br />
| {{anchor|INWEVA|INWEVA}} <br />
| The INWEVA 2020 data contains traffic intensity data for highways.<br />
| Netherlands<br />
| Rijkswaterstaat<br />
| https://data.overheid.nl/dataset/31225-intensiteit-wegvakken--inweva--2020 <br>See also: [[Traffic Plugin#INWEVA|Traffic Plugin]]<br />
|-<br />
| {{anchor|Infomil|Infomil}}<br />
| The infomil excel contains a calculation model to estimate traffic intensities for roads, based on the type of road, nearby parking and bicycle paths and urbanization degree. This excel has been converted into a lookup table in the {{software}}.<br />
| Netherlands<br />
| Rijkswaterstaat<br />
| https://www.infomil.nl/onderwerpen/lucht-water/luchtkwaliteit/slag/hulpmiddelen/inschatten/ <br>See also: [[Traffic Plugin#Infomil|Traffic Plugin]]<br />
|-<br />
| {{anchor|Infrarood|Infrarood}}<br />
| The 2016 WMS Infrarood is a layer from the aerial photography WMS from PDOK, and is used as example in the Demo Heat Stress Project.<br />
| Netherlands<br />
| PDOK<br />
| https://www.pdok.nl/introductie/-/article/luchtfoto-pdok <br> See also: [[Demo Heat Stress Project]]<br />
|-<br />
| {{anchor|BRP|BRP Gewaspercelen}} <br />
| Basisregistratie Gewaspercelen: contains the location of agricultural land and the cultivated crops. <br />
| Netherlands<br />
| Nationaal Georegister<br />
| http://www.nationaalgeoregister.nl/geonetwork/srv/dut/catalog.search#/metadata/%7B25943e6e-bb27-4b7a-b240-150ffeaa582e%7D?tab=general <br />
|-<br />
| {{anchor|BRK|BRK}} - Kadastrale Kaart<br />
| Basisregistratie Kadaster. In the {{software}} the Kadastrale kaart is used to determine the location of parcels. <br />
| Netherlands<br />
| Nationaal Georegister<br />
| http://www.nationaalgeoregister.nl/geonetwork/srv/dut/catalog.search#/metadata/40840197-0478-432b-8c76-e99c4da9203f?tab=general <br />
|-<br />
| {{anchor|Risicokaart|Risicokaart}} <br />
| This dataset shows the risks in a neighborhood, for example, by showing hazardous- and / or nuisance buildings (for example LPG station) and cables and pipes. Also contains additional information on vulnerable buildings (hotels, hospital, school, etc.).<br />
| Netherlands<br />
| Risicokaart.nl<br />
| https://www.risicokaart.nl/home<br />
|-<br />
| {{anchor|OSM|OSM}} <br />
| OpenStreetMap; this dataset contains the topography of the world and attribute information. <br />
| Worldwide<br />
| Own instance of Overpass API <br />
| https://www.openstreetmap.org/ <br />
|-<br />
| {{anchor|IMWA|Waterschapsdata}}<br />
| Several datasets from Water Authorities conforming to the Information Model Water (Informatiemodel water), including hydraulic structures and water-level areas.<br />
| Netherlands - dataset does not cover the whole of the Netherlands yet.<br />
| Copy of PDOK dataset<br />
| https://www.pdok.nl/nl/introductie/-/article/waterschapsdata<br />
|-<br />
| {{anchor|3DBAG|3D Bag}}<br />
| A dataset of 3D models covering the Netherlands, created by the 3D Geoinformation research group, Department of Urbanism at the Delft University of Technology.<br />
| Netherlands<br />
| 3D BAG<br />
| https://docs.3dbag.nl/en/<br />
|-<br />
| {{anchor|Energy labels|Energy label data}}<br />
| A dataset of most recently known energy labels per address in The Netherlands.<br />
| Netherlands<br />
| EP-online<br />
| https://www.ep-online.nl/PublicData<br />
|-<br />
| {{anchor|Timezones|Timezone data}}<br />
| A dataset of time zones which is used to determine a project's time zone.<br />
| World<br />
| <br />
|<br />
|}<br />
<br />
==More information on which sources are used==<br />
For more information on which project sources are actually used for the project, take a look at the following overviews in the editor:<br />
* the hover panel when clicking in the [[3D Visualization]] in the [[City Overlay|default view]].<br />
* the [[Source Overlay]]<br />
* the project source table (see below for more information)<br />
* the project sources menu (see below for more information)<br />
<br />
{{article end<br />
|howtos=<br />
* [[How to open the Project Sources panel]]<br />
* [[How to open the Project Sources table]]<br />
* [[How to import i3s scene layer in new project]]<br />
|seealso=<br />
*[[Source]]s<br />
*[[Template Project]]<br />
*[[Geo Plugin]]s<br />
}}<br />
<br />
{{GeoDataOverview}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Project_Sources&diff=54985Project Sources2023-08-10T12:30:22Z<p>Vincent@tygron.nl: /* Default sources */</p>
<hr />
<div>Project sources are the [[Geo Data]] sets that can be used by (geo) plugins to generate and build up a project in the {{software}}. Project Sources are stored as [[Source]]s in your project.<br />
Furthermore, all the additional data users import into a project are tagged with new Source as well.<br />
<br />
==Default sources==<br />
The table below contains the datasets that are automatically accessed, depending on the selected location, to create a new project. When selecting a location outside The Netherlands it is more likely that some [[Geo Data]] should be provided manually, which can done using a [[Template Project]] with one or more [[Geo Plugin]]s. <br />
<br />
{| class="wikitable"<br />
|-<br />
! (Open) Dataset<br />
! Description<br />
! Coverage<br />
! (Connection) Source<br />
! More information<br />
|-<br />
| {{anchor|BGT|BGT}}<br />
| Basisregistratie Grootschalige Topografie: Base Register containining the topography of the Netherlands. The dataset is very detailed and contains for instance roads, parks, trees, water surfaces and street objects. <br />
| Netherlands<br />
| {{anchor|PDOK<br />
| https://www.kadaster.nl/bgt; https://www.pdok.nl/introductie/-/article/basisregistratie-grootschalige-topografie-bgt-<br />
|-<br />
| {{anchor|BAG|BAG}}<br />
| Basisregistraties Adressen en Gebouwen: Base Register containing data about buildings and addresses such as function, construction year, size and the geometry of the buildings.<br />
| Netherlands.<br />
| PDOK<br />
| https://www.kadaster.nl/basisregistratie-adressen-en-gebouwen<br />
|-<br />
| {{anchor|BRO|BRO}}<br />
| Basisregistratie Ondergrond: Base Register containing detailed subsurface data. <br />
| Netherlands<br />
| PDOK<br />
| https://www.basisregistratieondergrond.nl/ <br />
|-<br />
| {{anchor|World Imagery|World Imagery}}<br />
| [[Satellite map]] used as base map for the [[height map]] in the [[3D Visualization]] and used to identify rooftop colors.<br />
| Worldwide<br />
| ESRI<br />
| https://services.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer/0 <br />
|-<br />
| {{anchor|Ocean Basemap|Ocean Basemap}}<br />
| Basemap with ocean data, including locations of water bodies and their names. Used to determine the location of water bodies worldwide. <br />
| Worldwide<br />
| ESRI<br />
| https://services.arcgisonline.com/arcgis/rest/services/Ocean_Basemap/MapServer<br />
|-<br />
| {{anchor|Terrain|Terrain}}<br />
| Digital Terrain Model (DTM): the terrain height of the bare ground without for example buildings, trees and other objects. See for more information the [[elevation model]] page. <br />
| Worldwide <br />
| ESRI <br />
| http://www.arcgis.com/home/item.html?id=58a541efc59545e6b7137f961d7de883<br />
|-<br />
| {{anchor|AHN|AHN}}<br />
| Actueel Hoogtebestand Nederland. By default AHN3 is used. We use the Digital Surface Model (DSM, the terrain height including buildings, trees and other objects) and the Digital Terrain Model (DTM, the terrain height of the bare ground) combined with the Terrain data above. For more information, see [[elevation model]]. <br />
| Netherlands<br />
| Nationaal Georegister<br />
| https://www.ahn.nl/<br />
|-<br />
| {{anchor|CBS Wijk- en Buurtkaart|CBS Wijk- en Buurtkaart}}<br />
| The CBS Wijk- en Buurtkaart (2017) contains the geometry of the division in neighborhoods and statistical data related to those neighborhoods.<br />
| Netherlands<br />
| PDOK<br />
| https://www.cbs.nl/nl-nl/dossier/nederland-regionaal/geografische%20data/wijk-en-buurtkaart-2017 <br />
|-<br />
| {{anchor|Ruimtelijke plannen|Ruimtelijke plannen}}<br />
| Ruimtelijke plannen are the offical published spatial plans/zoning plans.<br />
| Netherlands<br />
| Ruimtelijke Plannen<br />
| http://www.ruimtelijkeplannen.nl/web-roo/roo/index<br />
|-<br />
| {{anchor|Top10NL|Top10NL}}<br />
| Topographical dataset, used as an addition to the BGT data. <br />
| Netherlands<br />
| Tygron / PDOK<br />
| https://www.kadaster.nl/-/top10nl <br />
|-<br />
| {{anchor|NWB|NWB}} <br />
| The Nationaal Wegen Bestand is a dataset with the (name of) public roads in the Netherlands.<br />
| Netherlands<br />
| PDOK<br />
| https://www.pdok.nl/introductie/-/article/nationaal-wegen-bestand-nwb- <br />
|-<br />
| {{anchor|NSL|NSL}} <br />
| The NSL (Nationaal Samenwerkingsprogramma Luchtkwaliteit) contains data delivered by municipalities from their traffic models. For instance data such as road type, the tree factor, number of lanes, direction of traffic and traffic speed. <br />
| Netherlands<br />
| Rijksoverheid<br />
| https://www.cimlk.nl/documentatie/ <br>See also: [[Traffic Plugin#NSL|Traffic Plugin]]<br />
|-<br />
| {{anchor|INWEVA|INWEVA}} <br />
| The INWEVA 2020 data contains traffic intensity data for highways.<br />
| Netherlands<br />
| Rijkswaterstaat<br />
| https://data.overheid.nl/dataset/31225-intensiteit-wegvakken--inweva--2020 <br>See also: [[Traffic Plugin#INWEVA|Traffic Plugin]]<br />
|-<br />
| {{anchor|Infrarood|Infrarood}}<br />
| The 2016 WMS Infrarood is a layer from the airial photography WMS from PDOK, and is used as example in the Demo Heat Stress Project.<br />
| Netherlands<br />
| PDOK<br />
| https://www.pdok.nl/introductie/-/article/luchtfoto-pdok <br> See also: [[Demo Heat Stress Project]]<br />
|-<br />
| {{anchor|Infomil|Infomil}}<br />
| The infomil excel contains a calculation model to estimate traffic intensities for roads, based on the type of road, nearby parking and bicycle paths and urbanization degree. This excel has been converted into a lookup table in the {{software}}.<br />
| Netherlands<br />
| Rijkswaterstaat<br />
| https://www.infomil.nl/onderwerpen/lucht-water/luchtkwaliteit/slag/hulpmiddelen/inschatten/ <br>See also: [[Traffic Plugin#Infomil|Traffic Plugin]]<br />
|-<br />
| {{anchor|BRP|BRP Gewaspercelen}} <br />
| Basisregistratie Gewaspercelen: contains the location of agricultural land and the cultivated crops. <br />
| Netherlands<br />
| Nationaal Georegister<br />
| http://www.nationaalgeoregister.nl/geonetwork/srv/dut/catalog.search#/metadata/%7B25943e6e-bb27-4b7a-b240-150ffeaa582e%7D?tab=general <br />
|-<br />
| {{anchor|BRK|BRK}} - Kadastrale Kaart<br />
| Basisregistratie Kadaster. In the {{software}} the Kadastrale kaart is used to determine the location of parcels. <br />
| Netherlands<br />
| Nationaal Georegister<br />
| http://www.nationaalgeoregister.nl/geonetwork/srv/dut/catalog.search#/metadata/40840197-0478-432b-8c76-e99c4da9203f?tab=general <br />
|-<br />
| {{anchor|Risicokaart|Risicokaart}} <br />
| This dataset shows the risks in a neighborhood, for example, by showing hazardous- and / or nuisance buildings (for example LPG station) and cables and pipes. Also contains additional information on vulnerable buildings (hotels, hospital, school, etc.).<br />
| Netherlands<br />
| Risicokaart.nl<br />
| https://www.risicokaart.nl/home<br />
|-<br />
| {{anchor|OSM|OSM}} <br />
| OpenStreetMap; this dataset contains the topography of the world and attribute information. <br />
| Worldwide<br />
| Own instance of Overpass API <br />
| https://www.openstreetmap.org/ <br />
|-<br />
| {{anchor|IMWA|Waterschapsdata}}<br />
| Several datasets from Water Authorities conforming to the Information Model Water (Informatiemodel water), including hydraulic structures and water-level areas.<br />
| Netherlands - dataset does not cover the whole of the Netherlands yet.<br />
| Copy of PDOK dataset<br />
| https://www.pdok.nl/nl/introductie/-/article/waterschapsdata<br />
|-<br />
| {{anchor|3DBAG|3D Bag}}<br />
| A dataset of 3D models covering the Netherlands, created by the 3D Geoinformation research group, Department of Urbanism at the Delft University of Technology.<br />
| Netherlands<br />
| 3D BAG<br />
| https://docs.3dbag.nl/en/<br />
|-<br />
| {{anchor|Energy labels|Energy label data}}<br />
| A dataset of most recently known energy labels per address in The Netherlands.<br />
| Netherlands<br />
| EP-online<br />
| https://www.ep-online.nl/PublicData<br />
|-<br />
| {{anchor|Timezones|Timezone data}}<br />
| A dataset of time zones which is used to determine a project's time zone.<br />
| World<br />
| <br />
|<br />
|}<br />
<br />
==More information on which sources are used==<br />
For more information on which project sources are actually used for the project, take a look at the following overviews in the editor:<br />
* the hover panel when clicking in the [[3D Visualization]] in the [[City Overlay|default view]].<br />
* the [[Source Overlay]]<br />
* the project source table (see below for more information)<br />
* the project sources menu (see below for more information)<br />
<br />
{{article end<br />
|howtos=<br />
* [[How to open the Project Sources panel]]<br />
* [[How to open the Project Sources table]]<br />
* [[How to import i3s scene layer in new project]]<br />
|seealso=<br />
*[[Source]]s<br />
*[[Template Project]]<br />
*[[Geo Plugin]]s<br />
}}<br />
<br />
{{GeoDataOverview}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Project_Sources&diff=54984Project Sources2023-08-10T12:28:57Z<p>Vincent@tygron.nl: </p>
<hr />
<div>Project sources are the [[Geo Data]] sets that can be used by (geo) plugins to generate and build up a project in the {{software}}. Project Sources are stored as [[Source]]s in your project.<br />
Furthermore, all the additional data users import into a project are tagged with new Source as well.<br />
<br />
==Default sources==<br />
The table below contains the datasets that are automatically accessed, depending on the selected location, to create a new project. When selecting a location outside The Netherlands it is more likely that some [[Geo Data]] should be provided manually, which can done using a [[Template Project]] with one or more [[Geo Plugin]]s. <br />
<br />
{| class="wikitable"<br />
|-<br />
! (Open) Dataset<br />
! Description<br />
! Coverage<br />
! (Connection) Source<br />
! More information<br />
|-<br />
| {{anchor|BGT|BGT}}<br />
| Basisregistratie Grootschalige Topografie: Base Register containining the topography of the Netherlands. The dataset is very detailed and contains for instance roads, parks, trees, water surfaces and street objects. <br />
| Netherlands<br />
| {{anchor|PDOK<br />
| https://www.kadaster.nl/bgt; https://www.pdok.nl/introductie/-/article/basisregistratie-grootschalige-topografie-bgt-<br />
|-<br />
| {{anchor|BAG|BAG}}<br />
| Basisregistraties Adressen en Gebouwen: Base Register containing data about buildings and addresses such as function, construction year, size and the geometry of the buildings.<br />
| Netherlands.<br />
| PDOK<br />
| https://www.kadaster.nl/basisregistratie-adressen-en-gebouwen<br />
|-<br />
| {{anchor|BRO|BRO}}<br />
| Basisregistratie Ondergrond: Base Register containing detailed subsurface data. <br />
| Netherlands<br />
| PDOK<br />
| https://www.basisregistratieondergrond.nl/ <br />
|-<br />
| {{anchor|World Imagery|World Imagery}}<br />
| [[Satellite map]] used as base map for the [[height map]] in the [[3D Visualization]] and used to identify rooftop colors.<br />
| Worldwide<br />
| ESRI<br />
| https://services.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer/0 <br />
|-<br />
| {{anchor|Ocean Basemap|Ocean Basemap}}<br />
| Basemap with ocean data, including locations of water bodies and their names. Used to determine the location of water bodies worldwide. <br />
| Worldwide<br />
| ESRI<br />
| https://services.arcgisonline.com/arcgis/rest/services/Ocean_Basemap/MapServer<br />
|-<br />
| {{anchor|Terrain|Terrain}}<br />
| Digital Terrain Model (DTM): the terrain height of the bare ground without for example buildings, trees and other objects. See for more information the [[elevation model]] page. <br />
| Worldwide <br />
| ESRI <br />
| http://www.arcgis.com/home/item.html?id=58a541efc59545e6b7137f961d7de883<br />
|-<br />
| {{anchor|AHN|AHN}}<br />
| Actueel Hoogtebestand Nederland. By default AHN3 is used. We use the Digital Surface Model (DSM, the terrain height including buildings, trees and other objects) and the Digital Terrain Model (DTM, the terrain height of the bare ground) combined with the Terrain data above. For more information, see [[elevation model]]. <br />
| Netherlands<br />
| Nationaal Georegister<br />
| https://www.ahn.nl/<br />
|-<br />
| {{anchor|CBS Wijk- en Buurtkaart|CBS Wijk- en Buurtkaart}}<br />
| The CBS Wijk- en Buurtkaart (2017) contains the geometry of the division in neighborhoods and statistical data related to those neighborhoods.<br />
| Netherlands<br />
| PDOK<br />
| https://www.cbs.nl/nl-nl/dossier/nederland-regionaal/geografische%20data/wijk-en-buurtkaart-2017 <br />
|-<br />
| {{anchor|Ruimtelijke plannen|Ruimtelijke plannen}}<br />
| Ruimtelijke plannen are the offical published spatial plans/zoning plans.<br />
| Netherlands<br />
| Ruimtelijke Plannen<br />
| http://www.ruimtelijkeplannen.nl/web-roo/roo/index<br />
|-<br />
| {{anchor|Top10NL|Top10NL}}<br />
| Topographical dataset, used as an addition to the BGT data. <br />
| Netherlands<br />
| Tygron / PDOK<br />
| https://www.kadaster.nl/-/top10nl <br />
|-<br />
| {{anchor|NWB|NWB}} <br />
| The Nationaal Wegen Bestand is a dataset with the (name of) public roads in the Netherlands.<br />
| Netherlands<br />
| PDOK<br />
| https://www.pdok.nl/introductie/-/article/nationaal-wegen-bestand-nwb- <br />
|-<br />
| {{anchor|NSL|NSL}} <br />
| The NSL (Nationaal Samenwerkingsprogramma Luchtkwaliteit) contains data delivered by municipalities from their traffic models. For instance data such as road type, the tree factor, number of lanes, direction of traffic and traffic speed. <br />
| Netherlands<br />
| Rijksoverheid<br />
| https://www.cimlk.nl/documentatie/ <br>See also: [[Traffic Plugin#NSL|Traffic Plugin]]<br />
|-<br />
| {{anchor|INWEVA|INWEVA}} <br />
| The INWEVA 2020 data contains traffic intensity data for highways.<br />
| Netherlands<br />
| Rijkswaterstaat<br />
| https://data.overheid.nl/dataset/31225-intensiteit-wegvakken--inweva--2020 <br>See also: [[Traffic Plugin#INWEVA|Traffic Plugin]]<br />
|-<br />
| {{anchor|Infrarood|Infrarood}}<br />
| The 2016 WMS Infrarood is a layer from the airial photography WMS from PDOK, and is used as example in the Heat Demo Project.<br />
| Netherlands<br />
| PDOK<br />
| https://www.pdok.nl/introductie/-/article/luchtfoto-pdok <br> See also: [[Demo Heat Stress Project]]<br />
|-<br />
| {{anchor|Infomil|Infomil}}<br />
| The infomil excel contains a calculation model to estimate traffic intensities for roads, based on the type of road, nearby parking and bicycle paths and urbanization degree. This excel has been converted into a lookup table in the {{software}}.<br />
| Netherlands<br />
| Rijkswaterstaat<br />
| https://www.infomil.nl/onderwerpen/lucht-water/luchtkwaliteit/slag/hulpmiddelen/inschatten/ <br>See also: [[Traffic Plugin#Infomil|Traffic Plugin]]<br />
|-<br />
| {{anchor|BRP|BRP Gewaspercelen}} <br />
| Basisregistratie Gewaspercelen: contains the location of agricultural land and the cultivated crops. <br />
| Netherlands<br />
| Nationaal Georegister<br />
| http://www.nationaalgeoregister.nl/geonetwork/srv/dut/catalog.search#/metadata/%7B25943e6e-bb27-4b7a-b240-150ffeaa582e%7D?tab=general <br />
|-<br />
| {{anchor|BRK|BRK}} - Kadastrale Kaart<br />
| Basisregistratie Kadaster. In the {{software}} the Kadastrale kaart is used to determine the location of parcels. <br />
| Netherlands<br />
| Nationaal Georegister<br />
| http://www.nationaalgeoregister.nl/geonetwork/srv/dut/catalog.search#/metadata/40840197-0478-432b-8c76-e99c4da9203f?tab=general <br />
|-<br />
| {{anchor|Risicokaart|Risicokaart}} <br />
| This dataset shows the risks in a neighborhood, for example, by showing hazardous- and / or nuisance buildings (for example LPG station) and cables and pipes. Also contains additional information on vulnerable buildings (hotels, hospital, school, etc.).<br />
| Netherlands<br />
| Risicokaart.nl<br />
| https://www.risicokaart.nl/home<br />
|-<br />
| {{anchor|OSM|OSM}} <br />
| OpenStreetMap; this dataset contains the topography of the world and attribute information. <br />
| Worldwide<br />
| Own instance of Overpass API <br />
| https://www.openstreetmap.org/ <br />
|-<br />
| {{anchor|IMWA|Waterschapsdata}}<br />
| Several datasets from Water Authorities conforming to the Information Model Water (Informatiemodel water), including hydraulic structures and water-level areas.<br />
| Netherlands - dataset does not cover the whole of the Netherlands yet.<br />
| Copy of PDOK dataset<br />
| https://www.pdok.nl/nl/introductie/-/article/waterschapsdata<br />
|-<br />
| {{anchor|3DBAG|3D Bag}}<br />
| A dataset of 3D models covering the Netherlands, created by the 3D Geoinformation research group, Department of Urbanism at the Delft University of Technology.<br />
| Netherlands<br />
| 3D BAG<br />
| https://docs.3dbag.nl/en/<br />
|-<br />
| {{anchor|Energy labels|Energy label data}}<br />
| A dataset of most recently known energy labels per address in The Netherlands.<br />
| Netherlands<br />
| EP-online<br />
| https://www.ep-online.nl/PublicData<br />
|-<br />
| {{anchor|Timezones|Timezone data}}<br />
| A dataset of time zones which is used to determine a project's time zone.<br />
| World<br />
| <br />
|<br />
|}<br />
<br />
==More information on which sources are used==<br />
For more information on which project sources are actually used for the project, take a look at the following overviews in the editor:<br />
* the hover panel when clicking in the [[3D Visualization]] in the [[City Overlay|default view]].<br />
* the [[Source Overlay]]<br />
* the project source table (see below for more information)<br />
* the project sources menu (see below for more information)<br />
<br />
{{article end<br />
|howtos=<br />
* [[How to open the Project Sources panel]]<br />
* [[How to open the Project Sources table]]<br />
* [[How to import i3s scene layer in new project]]<br />
|seealso=<br />
*[[Source]]s<br />
*[[Template Project]]<br />
*[[Geo Plugin]]s<br />
}}<br />
<br />
{{GeoDataOverview}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=DXF&diff=54962DXF2023-07-07T12:53:10Z<p>Vincent@tygron.nl: /* Colors */</p>
<hr />
<div>DXF{{ref|DXF}} is a file format to exchange CAD data from Autodesk. It is the "open" variant of the "closed" DWG format, which is a proprietary binary format. AutoCAD can convert these formats to one another generally without loss of data. This file format can be used to import [[Spatial plan|2D spatial plans]]. <br />
<br />
==DXF file data==<br />
A DXF file is subdivided in several sections. The sections in this file that we inspect are:<br />
* HEADER: contains location and scaling information<br />
* GEODATA: contains geo-location information<br />
* TABLES: containing definitions of layers<br />
* ENTITIES: containing 2 and 3 dimensional shapes<br />
* BLOCKS: containing 2 and 3 dimension shapes, reusable using INSERTS in ENTITIES.<br />
<br />
==Layers==<br />
In the DXF file, entities are always assigned to one particular layer. In AutoCAD, layers can be turned on and off. This visibility does not influence whether or not the entities in this layer can be imported. Layers also have a visualization color, which will be set for blocks and entities belonging to that layer when they do not have a color definition themselves.<br />
<br />
==Entities== <br />
[[File:DXF_shapes.png|thumb|right|200px|A collection of shapes as possible in a DXF file.]]<br />
Currently, the following Autodesk CAD shape types are supported for entities and blocks: <br />
* '''LWPOLYLINES''': (2 dimensional line strings), including bulges.{{ref|LWPOLYLINES}}<br />
* '''LINE''': (single lines).{{ref|LINE}}<br />
* '''POLYLINE''': (3 dimensional line strings), currently only interpreted as 2 dimensional. The z-coordinate is ignored.{{ref|POLYLINE}}<br />
* '''HATCH''': (polygonal data constructed using other boundary entities).{{ref|HATCH}}<br />
* '''CIRCLE''': full and partial circles, given a center point, radius and start and end angle.{{ref|CIRCLE}}<br />
* '''ELLIPSE''': full and partial ellipses, given a center point, major and minor axis, rotation and start and end angle.{{ref|ELLIPSE}}<br />
* '''ARC''': curved lines given a center point and a radius.{{ref|ARC}}<br />
* '''VERTEX''': 2 dimensional point.{{ref|VERTEX}}<br />
* '''POINT''': Same as vertex, but 3 dimensional. Currently only interpreted as 2 dimensional. The z-coordinate is ignored.{{ref|POINT}}<br />
* '''SPLINE''': 2 dimensional Control point splines are currently supported.{{ref|SPLINE}} Fit point splines are currently not supported. Splines are converted to a POLYLINE with currently around 10 placed point per processed control point group to approximate the spline.<br />
* '''INSERT''': Predefined '''BLOCKS''' inserted at a point and with a rotation and a scale.{{ref|INSERT}}<br />
<br />
Autodesk CAD shape types that are explicitly not yet supported are:<br />
* '''REGION''': Regions are results of an operation (union, difference or intersection) using one or more input shapes.<br />
<br />
==Blocks==<br />
Blocks (BLOCKS) are parts in a CAD drawing that can be reused multiple times by inserting them at different locations with optional alternative rotations and scales. The usage of blocks in a DXF is supported.{{ref|BLOCKS}}<br />
<br />
Blocks can consist of shapes similar as to those definable in entities, including the insertion (INSERT) of other blocks. Each of these shapes can belong to a different layer. <br />
BLOCKS can also have attribute defined (ATTDEF) for them. These attributes can contain any string value.<br />
<br />
Each block is converted to one or more unique feature(s). Features within a block are kept separate when they belong to different layers. For example, a house block can consist of:<br />
<br />
* A shape for the back garden, in layer ''garden'';<br />
* A shape for the front garden, in layer ''garden'';<br />
* A shape for the garden shed, in layer ''sheds'' or ''housing'';<br />
* A shape or block of the garage, in layer ''garage'' or ''housing'';<br />
* A shape for the parking lane, in layer ''private parking'', ''parking'' or ''pavement''<br />
* An inserted block for the house itself, in layer ''housing'', where the inserted house block:<br />
** Has a rectangular shape that can be re-scaled for each insert into a parent block and also is in layer ''housing''.<br />
** Has attribute definitions describing for example:<br />
*** the floor height;<br />
*** amount of floors;<br />
*** the slanted roof height;<br />
*** the amount of units in the building, or the unit size;<br />
<gallery widths=300px heights=300px><br />
File:DXF_block_example.png<br />
File:DXF_block_platform.png|Two blocks imported into a project as a [[measure]].<br />
</gallery><br />
<br />
==Line stiching==<br />
<gallery>File:DXF_line_overlap.png</gallery><br />
Not all lines are drawn as closed lines, even though they look closed visually. For example, splines have been encountered that look closed from far away but are actually overlapping. For lines that overlap between start and end point, a line-closing-algorithm will be executed.<br />
{{clear}}<br />
<br />
==Lines to Multi-Polygons==<br />
<gallery><br />
File:DXF_linerings_in_linerings.png<br />
File:DXF_subtracting_shapes.png<br />
</gallery><br />
Shapes within a layer can be subtracted from each other, without the requirement of hatching the shape. For example, multiple line rings are drawn within each other. By subtracting these correctly, multi-polygons can be created with the expected inside and outside.<br />
{{clear}}<br />
<br />
==Colors==<br />
Colors can be defined per layer and per entity. Two types of colors are currently supported: <br />
* Indexed colors{{ref|indexcolors}}, where certain integer values represent RGB codes according to a mapping specified for AutoCAD. This color is stored in the feature under the COLOR_INDEX attribute.<br />
* True colors{{ref|truecolors}}, where an integer is used for the concatenated byte (256) numbers for the red, green and blue channel. This color is stored in the feature under the COLOR_TRUE attribute.<br />
Both colors are also converted as a {{software}} color stored under the COLOR attribute. This attribute can be remapped to a ROOF_COLOR, GEOMETRY_COLOR or any other color to be used directly in a [[Building]].<br />
<br />
{{article end<br />
| notes=<br />
* Due to the generally large number of features, it is advised to use a [[Geo Plugin]] to match [[function]]s to features in the ''Assign Function'' step of the [[Geo Data Wizard]]. This is especially useful when the DXF's layers and blocks use standardized names and attributes, such that you can reuse the GeoPlugin in multiple projects.<br />
| howtos=<br />
*[[How to import a DXF]]<br />
*[[How to export a project to DXF]]<br />
*[[How to add spatial elements to measure from a DXF file]]<br />
*[[How to import AutoCAD BLOCKS with attributes]]<br />
*[[How to edit an existing Geo Plugin]]<br />
*[[How to set the Geo-location of a DXF]]<br />
*[[How to set the unit of measurement for a DXF]]<br />
*[[How to create a Geo Plugin to import Buildings from a DXF]]<br />
*[[How to deal with a long processing DXF import]]<br />
| seealso=<br />
* [[Demo Dxf Import Project]]<br />
| references=<references><br />
{{ref|DXF<br />
|name=DXF<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://help.autodesk.com/view/ACD/2023/ENU/?guid=GUID-D4242737-58BB-47A5-9B0E-1E3DE7E7D647<br />
|lastvisit=28-11-2022<br />
}}<br />
{{ref|LWPOLYLINES<br />
|name=LWPOLYLINES<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2022/ENU/AutoCAD-Core/files/GUID-392BF13C-D9E7-47A8-8E07-435296332279-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|LINE<br />
|name=LINE<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2022/ENU/AutoCAD-Core/files/GUID-DB0FA734-8F5C-4000-92FF-89BA2D42CA21-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|POLYLINE<br />
|name=POLYLINE<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2022/ENU/AutoCAD-Core/files/GUID-392BF13C-D9E7-47A8-8E07-435296332279-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|HATCH<br />
|name=HATCH<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2023/ENU/AutoCAD-Core/files/GUID-27C104F2-B687-4025-B50B-A58E37329832-htm.html?us_oa=akn-us&us_si=8126699c-9f97-4fa3-9b23-fa556e058edb&us_st=Hatch<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|CIRCLE<br />
|name=CIRCLE<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2022/ENU/AutoCAD-Core/files/GUID-EDC69C38-6651-46DA-AFCC-56F2EB0A6AC6-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|ELLIPSE<br />
|name=ELLIPSE<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2022/ENU/AutoCAD-Core/files/GUID-2461D382-B7E5-44B3-A34C-735CE0089C8D-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|ARC<br />
|name=ARC<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2022/ENU/AutoCAD-Core/files/GUID-C78378FD-4704-4D0A-9D86-82FCBB118097-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|VERTEX<br />
|name=VERTEX<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2023/ENU/AutoCAD-Core/files/GUID-84591B48-71B9-4258-B287-CD2391C946D2-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|POINT<br />
|name=POINT<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2023/ENU/AutoCAD-Core/files/GUID-3F5861A1-9A63-42A6-8F12-3395771BAA6D-htm.html?us_oa=akn-us&us_si=cd548ae9-dde6-4a75-bb71-c74923034ef2&us_st=Point<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|SPLINE<br />
|name=SPLINE<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2023/ENU/AutoCAD-Core/files/GUID-58316136-30EB-499C-ACAD-31D0C653B2B2-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|INSERT<br />
|name=INSERT<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2023/ENU/AutoCAD-Core/files/GUID-BC0FD3C1-3BFC-4C5D-AB9A-BF480D5084BE-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|BLOCKS<br />
|name=BLOCKS<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2023/ENU/AutoCAD-Core/files/GUID-7410E7FB-3E0D-4411-B8F6-DBD59C71E87D-htm.html<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|indexcolors<br />
|name=AutoCAD Color Index (ACI) RGB equivalents<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://gohtx.com/acadcolors.php<br />
|lastvisit=26-9-2022<br />
}}<br />
{{ref|truecolors<br />
|name=AutoCAD True Color<br />
|author=<br />
|page=<br />
|source=<br />
|link=https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2023/ENU/AutoCAD-Core/files/GUID-BE316D65-8824-4114-8D7D-D02AE8BDAB70-htm.html<br />
|lastvisit=28-11-2022<br />
}}<br />
</references><br />
}}<br />
<br />
{{GeoDataOverview}}<br />
[[Category:DXF]]</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=How_to_use_the_GEOMETRY_COLOR_attribute&diff=54362How to use the GEOMETRY COLOR attribute2023-04-24T14:17:22Z<p>Vincent@tygron.nl: </p>
<hr />
<div>It is possible to change [[Geometry color (Building Attribute)]].<br />
<br />
As the operation is performed by TQL, the task can be done in the [[Editor]], with the [[Query Tool]]. More advanced users can also perform these queries through the [[API]].<br />
<br />
We will use the following example:<br><br />
<code>UPDATE_BUILDING</code><code>GEOMETRY_COLOR</code><code>WHERE</code><code>ATTRIBUTE</code><code>IS</code><code>FOO</code><br />
<br><br />
<br><br />
{{Editor steps|title=update the Geometry Color of a building|Select a building and add the attribute FOO:1.|From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).|Construct the above mentioned example, select the update color (Update to Value), and execute the query.|The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.}}<br />
<br><br />
<gallery mode="nolines"><br />
File:AddAttribute1.jpg|1. Select a building and add the attribute FOO:1.<br />
File:OpenQueryTool1.jpg|2. From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).<br />
File:ConstructQuery1.jpg|3. Construct the above mentioned example, select the update color (Update to Value), and execute the query.<br />
File:GeometryColorUpdated1.jpg|4. The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.<br />
</gallery><br />
<br />
{{article end<br />
|seealso=<br />
*[[Custom Geometries]]<br />
*[[Building]]<br />
*[[Geometry color (Building Attribute)]]<br />
}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geometry_color_(Building_Attribute)&diff=54361Geometry color (Building Attribute)2023-04-24T14:16:26Z<p>Vincent@tygron.nl: </p>
<hr />
<div>{{building attributes<br />
| <onlyinclude><br />
{{building attributes|type=row|icon=|attribute=GEOMETRY_COLOR|unit=Integer||Function value=|description=Updates [[building]] color to custom color selection.}} </onlyinclude><br />
}}<br />
<br />
The GEOMETRY_COLOR attribute enables the option to update the color of [[functions]], specified by attribute, by using a [[TQL|Tygron Query Language (TQL)]] query. It actually does not overwrite the color, so removing the attribute will restore the original color of the model.<br />
<!-- <br />
==How to use the GEOMETRY_COLOR attribute==<br />
As the operation is performed by TQL, the task can be done in the [[Editor]], with the [[Query Tool]]. More advanced users can also perform these queries through the [[API]].<br />
<br />
We will use the following example:<br><br />
<code>UPDATE_BUILDING</code><code>GEOMETRY_COLOR</code><code>WHERE</code><code>ATTRIBUTE</code><code>IS</code><code>FOO</code><br />
<br><br />
{{Editor steps|title=update the Geometry Color of a building|Select a building and add the attribute FOO:1.|From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).|Construct the above mentioned example, select the update color (Update to Value), and execute the query.|The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.}}<br />
<br><br />
<gallery mode="nolines"><br />
File:AddAttribute1.jpg|1. Select a building and add the attribute FOO:1.<br />
File:OpenQueryTool1.jpg|2. From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).<br />
File:ConstructQuery1.jpg|3. Construct the above mentioned example, select the update color (Update to Value), and execute the query.<br />
File:GeometryColorUpdated1.jpg|4. The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.<br />
</gallery><br />
--><br />
<br />
==Specific Use Cases==<br />
*Identify buildings by energy label<br />
**Give each building an energy label as attribute. <br />
**Construct a query that gives a corresponding color to each label group.<br />
*Identify trees with disease/ animal plague<br />
**Mark each infested tree with a suitable attribute. <br />
**Construct a query that gives a corresponding color to each label group.<br />
*Colorize [[Custom Geometry|3D models]] that lack textures ([[I3S]]/ 3D BAG/ [[CityGML]])<br />
**Construct a query that gives a corresponding color to each Function type.<br />
<br />
{{article end<br />
|seealso=<br />
*[[Custom Geometries]]<br />
*[[Building]]<br />
*[[How to use the GEOMETRY COLOR attribute]]<br />
}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geometry_color_(Building_Attribute)&diff=54360Geometry color (Building Attribute)2023-04-24T14:15:59Z<p>Vincent@tygron.nl: /* How to use the GEOMETRY_COLOR attribute */</p>
<hr />
<div>{{building attributes<br />
| <onlyinclude><br />
{{building attributes|type=row|icon=|attribute=GEOMETRY_COLOR|unit=Integer||Function value=|description=Updates [[building]] color to custom color selection.}} </onlyinclude><br />
}}<br />
<br />
The GEOMETRY_COLOR attribute enables the option to update the color of [[functions]], specified by attribute, by using a [[TQL|Tygron Query Language (TQL)]] query. It actually does not overwrite the color, so removing the attribute will restore the original color of the model.<br />
<br />
<!-- <br />
==How to use the GEOMETRY_COLOR attribute==<br />
As the operation is performed by TQL, the task can be done in the [[Editor]], with the [[Query Tool]]. More advanced users can also perform these queries through the [[API]].<br />
<br />
We will use the following example:<br><br />
<code>UPDATE_BUILDING</code><code>GEOMETRY_COLOR</code><code>WHERE</code><code>ATTRIBUTE</code><code>IS</code><code>FOO</code><br />
<br><br />
{{Editor steps|title=update the Geometry Color of a building|Select a building and add the attribute FOO:1.|From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).|Construct the above mentioned example, select the update color (Update to Value), and execute the query.|The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.}}<br />
<br><br />
<gallery mode="nolines"><br />
File:AddAttribute1.jpg|1. Select a building and add the attribute FOO:1.<br />
File:OpenQueryTool1.jpg|2. From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).<br />
File:ConstructQuery1.jpg|3. Construct the above mentioned example, select the update color (Update to Value), and execute the query.<br />
File:GeometryColorUpdated1.jpg|4. The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.<br />
</gallery><br />
--><br />
<br />
==Specific Use Cases==<br />
*Identify buildings by energy label<br />
**Give each building an energy label as attribute. <br />
**Construct a query that gives a corresponding color to each label group.<br />
*Identify trees with disease/ animal plague<br />
**Mark each infested tree with a suitable attribute. <br />
**Construct a query that gives a corresponding color to each label group.<br />
*Colorize [[Custom Geometry|3D models]] that lack textures ([[I3S]]/ 3D BAG/ [[CityGML]])<br />
**Construct a query that gives a corresponding color to each Function type.<br />
<br />
{{article end<br />
|seealso=<br />
*[[Custom Geometries]]<br />
*[[Building]]<br />
*[[How to use the GEOMETRY COLOR attribute]]<br />
}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Geometry_color_(Building_Attribute)&diff=54359Geometry color (Building Attribute)2023-04-24T14:15:06Z<p>Vincent@tygron.nl: /* Specific Use Cases */</p>
<hr />
<div>{{building attributes<br />
| <onlyinclude><br />
{{building attributes|type=row|icon=|attribute=GEOMETRY_COLOR|unit=Integer||Function value=|description=Updates [[building]] color to custom color selection.}} </onlyinclude><br />
}}<br />
<br />
The GEOMETRY_COLOR attribute enables the option to update the color of [[functions]], specified by attribute, by using a [[TQL|Tygron Query Language (TQL)]] query. It actually does not overwrite the color, so removing the attribute will restore the original color of the model.<br />
<br />
==How to use the GEOMETRY_COLOR attribute==<br />
As the operation is performed by TQL, the task can be done in the [[Editor]], with the [[Query Tool]]. More advanced users can also perform these queries through the [[API]].<br />
<br />
We will use the following example:<br><br />
<code>UPDATE_BUILDING</code><code>GEOMETRY_COLOR</code><code>WHERE</code><code>ATTRIBUTE</code><code>IS</code><code>FOO</code><br />
<br><br />
{{Editor steps|title=update the Geometry Color of a building|Select a building and add the attribute FOO:1.|From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).|Construct the above mentioned example, select the update color (Update to Value), and execute the query.|The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.}}<br />
<br><br />
<gallery mode="nolines"><br />
File:AddAttribute1.jpg|1. Select a building and add the attribute FOO:1.<br />
File:OpenQueryTool1.jpg|2. From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).<br />
File:ConstructQuery1.jpg|3. Construct the above mentioned example, select the update color (Update to Value), and execute the query.<br />
File:GeometryColorUpdated1.jpg|4. The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.<br />
</gallery><br />
<br />
==Specific Use Cases==<br />
*Identify buildings by energy label<br />
**Give each building an energy label as attribute. <br />
**Construct a query that gives a corresponding color to each label group.<br />
*Identify trees with disease/ animal plague<br />
**Mark each infested tree with a suitable attribute. <br />
**Construct a query that gives a corresponding color to each label group.<br />
*Colorize [[Custom Geometry|3D models]] that lack textures ([[I3S]]/ 3D BAG/ [[CityGML]])<br />
**Construct a query that gives a corresponding color to each Function type.<br />
<br />
{{article end<br />
|seealso=<br />
*[[Custom Geometries]]<br />
*[[Building]]<br />
*[[How to use the GEOMETRY COLOR attribute]]<br />
}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=How_to_use_the_GEOMETRY_COLOR_attribute&diff=54358How to use the GEOMETRY COLOR attribute2023-04-24T14:14:30Z<p>Vincent@tygron.nl: </p>
<hr />
<div>It is possible to change [[Geometry color (Building Attribute)]].<br />
<br />
As the operation is performed by TQL, the task can be done in the [[Editor]], with the [[Query Tool]]. More advanced users can also perform these queries through the [[API]].<br />
<br />
We will use the following example:<br><br />
<code>UPDATE_BUILDING</code><code>GEOMETRY_COLOR</code><code>WHERE</code><code>ATTRIBUTE</code><code>IS</code><code>FOO</code><br />
<br><br />
<br><br />
{{Editor steps|title=update the Geometry Color of a building|Select a building and add the attribute FOO:1.|From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).|Construct the above mentioned example, select the update color (Update to Value), and execute the query.|The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.}}<br />
<br><br />
<gallery mode="nolines"><br />
File:AddAttribute1.jpg|1. Select a building and add the attribute FOO:1.<br />
File:OpenQueryTool1.jpg|2. From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).<br />
File:ConstructQuery1.jpg|3. Construct the above mentioned example, select the update color (Update to Value), and execute the query.<br />
File:GeometryColorUpdated1.jpg|4. The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.<br />
</gallery></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=How_to_use_the_GEOMETRY_COLOR_attribute&diff=54357How to use the GEOMETRY COLOR attribute2023-04-24T14:14:19Z<p>Vincent@tygron.nl: Created page with "it is possible to change Geometry color (Building Attribute). As the operation is performed by TQL, the task can be done in the Editor, with the Query Tool. More advanced users can also perform these queries through the API. We will use the following example:<br> <code>UPDATE_BUILDING</code><code>GEOMETRY_COLOR</code><code>WHERE</code><code>ATTRIBUTE</code><code>IS</code><code>FOO</code> <br> <br> {{Editor steps|title=update the Geometry Color of a buil..."</p>
<hr />
<div>it is possible to change [[Geometry color (Building Attribute)]].<br />
<br />
As the operation is performed by TQL, the task can be done in the [[Editor]], with the [[Query Tool]]. More advanced users can also perform these queries through the [[API]].<br />
<br />
We will use the following example:<br><br />
<code>UPDATE_BUILDING</code><code>GEOMETRY_COLOR</code><code>WHERE</code><code>ATTRIBUTE</code><code>IS</code><code>FOO</code><br />
<br><br />
<br><br />
{{Editor steps|title=update the Geometry Color of a building|Select a building and add the attribute FOO:1.|From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).|Construct the above mentioned example, select the update color (Update to Value), and execute the query.|The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.}}<br />
<br><br />
<gallery mode="nolines"><br />
File:AddAttribute1.jpg|1. Select a building and add the attribute FOO:1.<br />
File:OpenQueryTool1.jpg|2. From the top bar, open the Query Tool (Current Situation > Queries > TQL Query Tool).<br />
File:ConstructQuery1.jpg|3. Construct the above mentioned example, select the update color (Update to Value), and execute the query.<br />
File:GeometryColorUpdated1.jpg|4. The selected building color is now updated, according to the newly added GEOMETRY_COLOR attribute.<br />
</gallery></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Measurements&diff=54067Measurements2023-03-01T14:37:54Z<p>Vincent@tygron.nl: Redirected page to Measurement</p>
<hr />
<div>#REDIRECT [[Measurement]]</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=GeoShare&diff=50276GeoShare2023-01-26T13:19:49Z<p>Vincent@tygron.nl: /* Public Share */</p>
<hr />
<div>The {{geoshare}} is a shared central repository for files and (geographical) data, hosted on the {{software}}. It is linked to an individual [[Domain]], but exists separate from active [[Session]]s. This allows for the sharing of data, either input data or results from calculations, without the overhead of a full [[Project]]'s data or a running [[Session]]. In addition to geographical data, the {{geoshare}} can also host other files which can be used as [[asset]]s in a [[Project]].<br />
<br />
The {{geoshare}} supports uploading, downloading, renaming and deleting files, as well as setting up a file structure to organize them.<br />
<br />
The {{geoshare}} can be accessed directly from the [[main menu]]. All users with [[Editor (User Account Type)|Editor rights]] can access and update all files on the {{geoshare}}.<br />
<br />
==Access==<br />
Files uploaded to the {{geoshare}} can be accessed via a url. The url allows anyone to access the file at any time. The url can be used in a webbrowser to initiate a download of the file (or provide an in-browser overview of the contents of a directory).<br />
<br />
On a per-file and per-directory basis, it is possible to set a required access token. Although to access a file or directory a url must be known in the first place, requiring an access token provides an additional secret which must be known in order to access the data.<br />
<br />
When a directory is accessed in a web browser, all direct contents of the directory are displayed, including those which actually also require an access token. However, only contents which do ''not'' require an access token can be directly accessed from that overview.<br />
<br />
==Public Share==<br />
There is also a public section on the {{geoshare}} that is accessible for all users in all domains. The public {{geoshare}} can for example be used to share publicly available default Indicators or example files. Please contact Tygron support to submit proposals for new content on the public {{geoshare}}.<br />
<br />
The public {{geoshare}} can be accessed via the toggle button in the upper right corner of the {{geoshare}} panel.<br />
<gallery> <br />
File:PublicShareToggleButton1.jpg|Toggle button to access Public Share.<br />
File:Share_public_indicators.png|Indicators section on the {{Public Share}}<br />
</gallery><br />
<br />
==Files==<br />
The {{geoshare}} is primarily intended to host geographical data, either for the purpose of standardized input for the creation of [[Project]]s, or to host the results of performed calculations in an easily accessible way without the need to keep a [[Session]] active or even a complete [[Project]]. However, other files can be hosted on the {{geoshare}} as well, with a focus on files which can be used as [[asset]]s in a [[Project]] such as [[Excel]]s.<br />
<br />
The {{geoshare}} supports the following filetypes:<br />
{|class=wikitable<br />
! Filetype<br />
! Name<br />
! Type of data<br />
! Input<br />
! Output<br />
|-<br />
| .cityjson<br />
| [[GeoJSON]]<br />
| 3D visualization data<br />
| Import as [[Custom Geometries]] for [[Building]]s<br />
| <br />
|-<br />
| .csv<br />
| [[CSV]]<br />
| Text-based list of values<br />
| <br />
| <br />
|-<br />
| .docx<br />
| <br />
| Document<br />
| <br />
| <br />
|-<br />
| .dxf<br />
| [[DXF]]<br />
| AutoCAD exchange format<br />
| Import as [[Building]]s, [[Area]]s, etc<br />
| <br />
|-<br />
| .geojson<br />
| [[GeoJSON]]<br />
| 2D Vector data<br />
| Import as [[Building]]s, [[Area]]s, etc<br />
| Export of Vector data<br />
|-<br />
| .gif<br />
| <br />
| Animated image<br />
| <br />
| Recorded [[GIF animation]]<br />
|-<br />
| .gml<br />
| <br />
| XML data<br />
| <br />
| <br />
|-<br />
| .jpeg<br />
| <br />
| Image<br />
| <br />
| <br />
|-<br />
| .jpg<br />
| <br />
| Image<br />
| <br />
| <br />
|-<br />
| .json<br />
| [[GeoJSON]]<br />
| 2D and 3D Vector data<br />
| Import as [[Building]]s, [[Area]]s, etc<br />
| <br />
|-<br />
| .pdf<br />
| <br />
| Document<br />
| <br />
| <br />
|-<br />
| .png<br />
| <br />
| Image<br />
| <br />
| [[Screenshot]]<br />
|-<br />
| .slpk<br />
| [[SLPK]]<br />
| 3D visualization data<br />
| Import as [[Custom Geometries]] for [[Building]]s<br />
| <br />
|-<br />
| .tif<br />
| [[GeoTIFF]]<br />
| Grid data<br />
| [[GeoTIFF Overlay]], [[Elevation model]], other grid data<br />
| <br />
|-<br />
| .tiff<br />
| [[GeoTIFF]]<br />
| Grid data<br />
| [[GeoTIFF Overlay]], [[Elevation model]], other grid data<br />
| Export of [[Grid Overlay]]<br />
|-<br />
| .txt<br />
| <br />
| Text<br />
| <br />
| <br />
|-<br />
| .xlsx<br />
| [[Excel]]<br />
| [[Excel]]<br />
| Assets for [[Indicator]]s, [[Panel]]s, etc<br />
| <br />
|-<br />
| .xml<br />
| <br />
| XML data<br />
| <br />
| <br />
|}<br />
<br />
==Viewers==<br />
{{main|GeoShare Viewer}}<br />
Besides the ability to serve "raw" files, it is possible to create a "viewer" on the {{geoshare}}. Viewers allow for a user-friendly way to share geographical data such as [[GeoJSON]]s and [[GeoTIFFs]]. They form a type of asset distinctly separate from conventional files and directories. Accessing a viewer in the browser shows a simple web-based interface in which the data of the viewer is visualized. The extent of the viewer is based on the extent of the data which is part of it.<br />
<br />
<br />
{{article end<br />
| notes=<br />
* The url for any file, directory, or viewer, contains the name of the file and the name of the domain in which the original file was uploaded.<br />
* To reset the access token for any file, disable and re-enable the token for the file. A new token will be generated.<br />
|seealso=<br />
* [[Geo Plugin]]: Files with geographical data can be imported directly into a [[Project]] automatically via Geo Plugins.<br />
|howtos=<br />
* [[How to create a Geo Plugin to import Areas from the Geo Share at Project creation]]<br />
|videos=<br />
{{video|link=https://www.youtube.com/watch?v=IhnEk7mp5hE|description=Integrating data using the {{geoshare}} and Geo Plugins.|language=dutch}}<br />
}}<br />
<br />
<br />
{{GeoDataOverview}}<br />
{{Editor current situation nav}}<br />
{{User rights nav}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=GeoShare&diff=50274GeoShare2023-01-26T13:19:26Z<p>Vincent@tygron.nl: /* Public Share */</p>
<hr />
<div>The {{geoshare}} is a shared central repository for files and (geographical) data, hosted on the {{software}}. It is linked to an individual [[Domain]], but exists separate from active [[Session]]s. This allows for the sharing of data, either input data or results from calculations, without the overhead of a full [[Project]]'s data or a running [[Session]]. In addition to geographical data, the {{geoshare}} can also host other files which can be used as [[asset]]s in a [[Project]].<br />
<br />
The {{geoshare}} supports uploading, downloading, renaming and deleting files, as well as setting up a file structure to organize them.<br />
<br />
The {{geoshare}} can be accessed directly from the [[main menu]]. All users with [[Editor (User Account Type)|Editor rights]] can access and update all files on the {{geoshare}}.<br />
<br />
==Access==<br />
Files uploaded to the {{geoshare}} can be accessed via a url. The url allows anyone to access the file at any time. The url can be used in a webbrowser to initiate a download of the file (or provide an in-browser overview of the contents of a directory).<br />
<br />
On a per-file and per-directory basis, it is possible to set a required access token. Although to access a file or directory a url must be known in the first place, requiring an access token provides an additional secret which must be known in order to access the data.<br />
<br />
When a directory is accessed in a web browser, all direct contents of the directory are displayed, including those which actually also require an access token. However, only contents which do ''not'' require an access token can be directly accessed from that overview.<br />
<br />
==Public Share==<br />
There is also a public section int the {{geoshare}} that is accessible for all users in all domains. The public {{geoshare}} can for example be used to share publicly available default Indicators or example files. Please contact Tygron support to submit proposals for new content on the public {{geoshare}}.<br />
<br />
The public {{geoshare}} can be accessed via the toggle button in the upper right corner of the {{geoshare}} panel.<br />
<gallery> <br />
File:PublicShareToggleButton1.jpg|Toggle button to access Public Share.<br />
File:Share_public_indicators.png|Indicators section on the {{Public Share}}<br />
</gallery><br />
<br />
==Files==<br />
The {{geoshare}} is primarily intended to host geographical data, either for the purpose of standardized input for the creation of [[Project]]s, or to host the results of performed calculations in an easily accessible way without the need to keep a [[Session]] active or even a complete [[Project]]. However, other files can be hosted on the {{geoshare}} as well, with a focus on files which can be used as [[asset]]s in a [[Project]] such as [[Excel]]s.<br />
<br />
The {{geoshare}} supports the following filetypes:<br />
{|class=wikitable<br />
! Filetype<br />
! Name<br />
! Type of data<br />
! Input<br />
! Output<br />
|-<br />
| .cityjson<br />
| [[GeoJSON]]<br />
| 3D visualization data<br />
| Import as [[Custom Geometries]] for [[Building]]s<br />
| <br />
|-<br />
| .csv<br />
| [[CSV]]<br />
| Text-based list of values<br />
| <br />
| <br />
|-<br />
| .docx<br />
| <br />
| Document<br />
| <br />
| <br />
|-<br />
| .dxf<br />
| [[DXF]]<br />
| AutoCAD exchange format<br />
| Import as [[Building]]s, [[Area]]s, etc<br />
| <br />
|-<br />
| .geojson<br />
| [[GeoJSON]]<br />
| 2D Vector data<br />
| Import as [[Building]]s, [[Area]]s, etc<br />
| Export of Vector data<br />
|-<br />
| .gif<br />
| <br />
| Animated image<br />
| <br />
| Recorded [[GIF animation]]<br />
|-<br />
| .gml<br />
| <br />
| XML data<br />
| <br />
| <br />
|-<br />
| .jpeg<br />
| <br />
| Image<br />
| <br />
| <br />
|-<br />
| .jpg<br />
| <br />
| Image<br />
| <br />
| <br />
|-<br />
| .json<br />
| [[GeoJSON]]<br />
| 2D and 3D Vector data<br />
| Import as [[Building]]s, [[Area]]s, etc<br />
| <br />
|-<br />
| .pdf<br />
| <br />
| Document<br />
| <br />
| <br />
|-<br />
| .png<br />
| <br />
| Image<br />
| <br />
| [[Screenshot]]<br />
|-<br />
| .slpk<br />
| [[SLPK]]<br />
| 3D visualization data<br />
| Import as [[Custom Geometries]] for [[Building]]s<br />
| <br />
|-<br />
| .tif<br />
| [[GeoTIFF]]<br />
| Grid data<br />
| [[GeoTIFF Overlay]], [[Elevation model]], other grid data<br />
| <br />
|-<br />
| .tiff<br />
| [[GeoTIFF]]<br />
| Grid data<br />
| [[GeoTIFF Overlay]], [[Elevation model]], other grid data<br />
| Export of [[Grid Overlay]]<br />
|-<br />
| .txt<br />
| <br />
| Text<br />
| <br />
| <br />
|-<br />
| .xlsx<br />
| [[Excel]]<br />
| [[Excel]]<br />
| Assets for [[Indicator]]s, [[Panel]]s, etc<br />
| <br />
|-<br />
| .xml<br />
| <br />
| XML data<br />
| <br />
| <br />
|}<br />
<br />
==Viewers==<br />
{{main|GeoShare Viewer}}<br />
Besides the ability to serve "raw" files, it is possible to create a "viewer" on the {{geoshare}}. Viewers allow for a user-friendly way to share geographical data such as [[GeoJSON]]s and [[GeoTIFFs]]. They form a type of asset distinctly separate from conventional files and directories. Accessing a viewer in the browser shows a simple web-based interface in which the data of the viewer is visualized. The extent of the viewer is based on the extent of the data which is part of it.<br />
<br />
<br />
{{article end<br />
| notes=<br />
* The url for any file, directory, or viewer, contains the name of the file and the name of the domain in which the original file was uploaded.<br />
* To reset the access token for any file, disable and re-enable the token for the file. A new token will be generated.<br />
|seealso=<br />
* [[Geo Plugin]]: Files with geographical data can be imported directly into a [[Project]] automatically via Geo Plugins.<br />
|howtos=<br />
* [[How to create a Geo Plugin to import Areas from the Geo Share at Project creation]]<br />
|videos=<br />
{{video|link=https://www.youtube.com/watch?v=IhnEk7mp5hE|description=Integrating data using the {{geoshare}} and Geo Plugins.|language=dutch}}<br />
}}<br />
<br />
<br />
{{GeoDataOverview}}<br />
{{Editor current situation nav}}<br />
{{User rights nav}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=File:PublicShareToggleButton1.jpg&diff=50273File:PublicShareToggleButton1.jpg2023-01-26T13:18:44Z<p>Vincent@tygron.nl: </p>
<hr />
<div></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=GeoShare&diff=50272GeoShare2023-01-26T13:18:17Z<p>Vincent@tygron.nl: /* Public Share */</p>
<hr />
<div>The {{geoshare}} is a shared central repository for files and (geographical) data, hosted on the {{software}}. It is linked to an individual [[Domain]], but exists separate from active [[Session]]s. This allows for the sharing of data, either input data or results from calculations, without the overhead of a full [[Project]]'s data or a running [[Session]]. In addition to geographical data, the {{geoshare}} can also host other files which can be used as [[asset]]s in a [[Project]].<br />
<br />
The {{geoshare}} supports uploading, downloading, renaming and deleting files, as well as setting up a file structure to organize them.<br />
<br />
The {{geoshare}} can be accessed directly from the [[main menu]]. All users with [[Editor (User Account Type)|Editor rights]] can access and update all files on the {{geoshare}}.<br />
<br />
==Access==<br />
Files uploaded to the {{geoshare}} can be accessed via a url. The url allows anyone to access the file at any time. The url can be used in a webbrowser to initiate a download of the file (or provide an in-browser overview of the contents of a directory).<br />
<br />
On a per-file and per-directory basis, it is possible to set a required access token. Although to access a file or directory a url must be known in the first place, requiring an access token provides an additional secret which must be known in order to access the data.<br />
<br />
When a directory is accessed in a web browser, all direct contents of the directory are displayed, including those which actually also require an access token. However, only contents which do ''not'' require an access token can be directly accessed from that overview.<br />
<br />
==Public Share==<br />
There is also a public section int the {{geoshare}} that is accessible for all users in all domains. The public {{geoshare}} can for example be used to share publicly available default Indicators or example files. Please contact Tygron support to submit proposals for new content on the public {{geoshare}}.<br />
<br />
The public {{geoshare}} can be accessed via the toggle button in the upper right corner of the {{geoshare}} panel.<br />
<gallery widths=300px heights=300px> <br />
File:PublicShareToggleButton1.jpg|Toggle button to access Public Share.<br />
File:Share_public_indicators.png|Indicators section on the {{Public Share}}<br />
</gallery><br />
<br />
==Files==<br />
The {{geoshare}} is primarily intended to host geographical data, either for the purpose of standardized input for the creation of [[Project]]s, or to host the results of performed calculations in an easily accessible way without the need to keep a [[Session]] active or even a complete [[Project]]. However, other files can be hosted on the {{geoshare}} as well, with a focus on files which can be used as [[asset]]s in a [[Project]] such as [[Excel]]s.<br />
<br />
The {{geoshare}} supports the following filetypes:<br />
{|class=wikitable<br />
! Filetype<br />
! Name<br />
! Type of data<br />
! Input<br />
! Output<br />
|-<br />
| .cityjson<br />
| [[GeoJSON]]<br />
| 3D visualization data<br />
| Import as [[Custom Geometries]] for [[Building]]s<br />
| <br />
|-<br />
| .csv<br />
| [[CSV]]<br />
| Text-based list of values<br />
| <br />
| <br />
|-<br />
| .docx<br />
| <br />
| Document<br />
| <br />
| <br />
|-<br />
| .dxf<br />
| [[DXF]]<br />
| AutoCAD exchange format<br />
| Import as [[Building]]s, [[Area]]s, etc<br />
| <br />
|-<br />
| .geojson<br />
| [[GeoJSON]]<br />
| 2D Vector data<br />
| Import as [[Building]]s, [[Area]]s, etc<br />
| Export of Vector data<br />
|-<br />
| .gif<br />
| <br />
| Animated image<br />
| <br />
| Recorded [[GIF animation]]<br />
|-<br />
| .gml<br />
| <br />
| XML data<br />
| <br />
| <br />
|-<br />
| .jpeg<br />
| <br />
| Image<br />
| <br />
| <br />
|-<br />
| .jpg<br />
| <br />
| Image<br />
| <br />
| <br />
|-<br />
| .json<br />
| [[GeoJSON]]<br />
| 2D and 3D Vector data<br />
| Import as [[Building]]s, [[Area]]s, etc<br />
| <br />
|-<br />
| .pdf<br />
| <br />
| Document<br />
| <br />
| <br />
|-<br />
| .png<br />
| <br />
| Image<br />
| <br />
| [[Screenshot]]<br />
|-<br />
| .slpk<br />
| [[SLPK]]<br />
| 3D visualization data<br />
| Import as [[Custom Geometries]] for [[Building]]s<br />
| <br />
|-<br />
| .tif<br />
| [[GeoTIFF]]<br />
| Grid data<br />
| [[GeoTIFF Overlay]], [[Elevation model]], other grid data<br />
| <br />
|-<br />
| .tiff<br />
| [[GeoTIFF]]<br />
| Grid data<br />
| [[GeoTIFF Overlay]], [[Elevation model]], other grid data<br />
| Export of [[Grid Overlay]]<br />
|-<br />
| .txt<br />
| <br />
| Text<br />
| <br />
| <br />
|-<br />
| .xlsx<br />
| [[Excel]]<br />
| [[Excel]]<br />
| Assets for [[Indicator]]s, [[Panel]]s, etc<br />
| <br />
|-<br />
| .xml<br />
| <br />
| XML data<br />
| <br />
| <br />
|}<br />
<br />
==Viewers==<br />
{{main|GeoShare Viewer}}<br />
Besides the ability to serve "raw" files, it is possible to create a "viewer" on the {{geoshare}}. Viewers allow for a user-friendly way to share geographical data such as [[GeoJSON]]s and [[GeoTIFFs]]. They form a type of asset distinctly separate from conventional files and directories. Accessing a viewer in the browser shows a simple web-based interface in which the data of the viewer is visualized. The extent of the viewer is based on the extent of the data which is part of it.<br />
<br />
<br />
{{article end<br />
| notes=<br />
* The url for any file, directory, or viewer, contains the name of the file and the name of the domain in which the original file was uploaded.<br />
* To reset the access token for any file, disable and re-enable the token for the file. A new token will be generated.<br />
|seealso=<br />
* [[Geo Plugin]]: Files with geographical data can be imported directly into a [[Project]] automatically via Geo Plugins.<br />
|howtos=<br />
* [[How to create a Geo Plugin to import Areas from the Geo Share at Project creation]]<br />
|videos=<br />
{{video|link=https://www.youtube.com/watch?v=IhnEk7mp5hE|description=Integrating data using the {{geoshare}} and Geo Plugins.|language=dutch}}<br />
}}<br />
<br />
<br />
{{GeoDataOverview}}<br />
{{Editor current situation nav}}<br />
{{User rights nav}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=File:MeasurementTool1.jpg&diff=50270File:MeasurementTool1.jpg2023-01-26T13:12:18Z<p>Vincent@tygron.nl: Uploaded own work with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=No description.}}<br />
|date=2023-01-26<br />
|source={{own}}<br />
|author=[[User:Vincent@tygron.nl|Vincent@tygron.nl]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{licensing|generic}}<br />
<br />
[[Category:Uploaded with UploadWizard]]</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=File:PointMeasurement1.jpg&diff=50269File:PointMeasurement1.jpg2023-01-26T13:12:18Z<p>Vincent@tygron.nl: Uploaded own work with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=No description.}}<br />
|date=2023-01-26<br />
|source={{own}}<br />
|author=[[User:Vincent@tygron.nl|Vincent@tygron.nl]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{licensing|generic}}<br />
<br />
[[Category:Uploaded with UploadWizard]]</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=How_to_inspect_object_output_attributes_of_an_overlay_using_the_measurement_tool&diff=50268How to inspect object output attributes of an overlay using the measurement tool2023-01-26T13:10:42Z<p>Vincent@tygron.nl: </p>
<hr />
<div>{{howto|title=use the measurement tool|Select a [[Water Overlay]] in the overlay menu. Notice the [[System_visualization_(Water_Overlay)|water system visualization]] is shown in the [[3D Visualization]] as well.|Select the measuring tool icon (signified by a ruler) in the overlay menu, located between the zoom buttons and the overlay icons.|Select the ''Point Measurement'' option (signified by a point) at the top of the measuring tool window.|Click on a visualized hydraulic structure of interest in the [[3D Visualization]].|The graph in the measuring tool window now displays an output attribute of the hydraulic structure at that location when it displays its name.|Click consecutively to cycle to all the output attributes for that object related to the selected overlay.}}<br />
<br />
<gallery><br />
File:MeasurementTool1.jpg|Step 2: Select the measuring tool icon (signified by a ruler) in the overlay menu, located between the zoom buttons and the overlay icons.<br />
File:PointMeasurement1.jpg|Step 3: Select the ''Point Measurement'' option (signified by a point) at the top of the measuring tool window.<br />
File:Object_measurement_wateroverlay.PNG|A weir in a Water Overlay's visualization that is being inspected with the measurement tool.<br />
</gallery><br />
<br />
{{article end<br />
|seealso=<br />
* [[Object height output (Water Overlay)]]<br />
* [[Object flow output (Water Overlay)]]<br />
* [[Object datum output a (Water Overlay)]]<br />
* [[Object datum output b (Water Overlay)]]<br />
|howtos=<br />
* [[How to export an Object output attribute as measurement]]<br />
}}<br />
<br />
[[Category:Measurement]][[Category:How-to's]]</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=How_to_inspect_object_output_attributes_of_an_overlay_using_the_measurement_tool&diff=50265How to inspect object output attributes of an overlay using the measurement tool2023-01-26T13:02:24Z<p>Vincent@tygron.nl: </p>
<hr />
<div>{{howto|use the measurement tool|Select a [[Water Overlay]] in the overlay menu. Notice the [[System_visualization_(Water_Overlay)|water system visualization]] is shown in the [[3D Visualization]] as well.|Select the measuring tool icon (signified by a ruler) in the overlay menu, located between the zoom buttons and the overlay icons.|Select the ''Point Measurement'' option (signified by a point) at the top of the measuring tool window.|Click on a visualized hydraulic structure of interest in the [[3D Visualization]].|The graph in the measuring tool window now displays an output attribute of the hydraulic structure at that location when it displays its name.|Click consecutively to cycle to all the output attributes for that object related to the selected overlay.}}<br />
<br />
[[File:Object_measurement_wateroverlay.PNG|thumb|left|400px|A weir in a Water Overlay's visualization that is being inspected with the measurement tool.]]<br />
<br />
{{article end<br />
|seealso=<br />
* [[Object height output (Water Overlay)]]<br />
* [[Object flow output (Water Overlay)]]<br />
* [[Object datum output a (Water Overlay)]]<br />
* [[Object datum output b (Water Overlay)]]<br />
|howtos=<br />
* [[How to export an Object output attribute as measurement]]<br />
}}<br />
<br />
[[Category:Measurement]][[Category:How-to's]]</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Grid_Overlay&diff=50227Grid Overlay2023-01-26T11:50:00Z<p>Vincent@tygron.nl: /* Active */</p>
<hr />
<div>A Grid Overlay is a calculated [[overlay]]. It uses a 2-dimensional grid for calculation, data storage and visualization. The calculation divides the entire [[3D world]] up into a grid of equally sized square cells, with possible size per cell ranging from 0.25m² up to 100m², depending on the size of the project area. This amounts to anywhere from thousands to millions of cells per [[Overlay |overlay]].<br />
<br />
For each cell, a calculation is performed, the specifics of which depend on the overlay being calculated. This can be as simple as displaying (possibly inherently) rasterized data, such as [[GeoTIFF Overlay]]s or the [[Heightmap Overlay|heightmap]], or as complex as multi-step [[Rainfall Overlay|rainfall calculations]].<br />
<br />
The results of a Grid Overlay can be {{inlink|Visualization|visualized}} in the [[3D world]], exported as a [[GeoTIFF]], or queried using [[TQL]].<br />
<br />
==Calculations==<br />
Depending on the exact overlay being calculated, the specifics of the calculation may differ, but the general approach is identical for each [[Overlay]].<br />
<br />
Each calculation relies on some data, which may be set as properties or attributes of the overlay, or may be based on the features present in an individual cell. This data is read from their respective locations as input for the calculation. Data from surrounding cells may also be included, in which their distance may also be factored in. If input for calculations may exist in multiple kinds of data, it depends on the exact calculation which data layer has preference. In general (for example, for attributes for an [[Average Overlay]]), the data layers are checked in the following order:<br />
# [[Building]]s<br />
# [[Terrain]]s<br />
# [[Area]]s<br />
# [[Neighborhood]]s<br />
<br />
With all the data obtained, a new values or set of values is calculated for the cell, and stored as result data for that cell. The calculation may specify this processing repeating a large number of times, for example when iterating through time steps.<br />
<br />
When the calculation is completed, a final result value is stored in the cell. The value stored in the cell itself is a unitless number. The exact meaning of the number is dependent on the overlay which defines the calculation. A calculation for [[Traffic Noise Overlay|traffic noise]] will present its result in decibels. A calculation for [[Subsidence Overlay|subsidence]] in meters.<br />
<br />
==Using grid results==<br />
The results of a grid overlay calculation can be used in multiple ways.<br />
===Visualization===<br />
The results of the overlay are displayed in the [[3D world]]. By selecting the overlay in the session interface, the world will be colored based on the calculated values. This allows the end-user to inspect the results visually and geographically.<br />
<br />
The legend displayed while the overlay is active can be configured to fit the magnitude and intent of the colors of the overlay.<br />
<br />
===TQL===<br />
The results of the calculation can be queries using [[TQL]]. Queries can either retrieve data of the grid directly, such as the average value in a given location, or use it as a filter for other queries, by specifying a value the grid should have before taking that location into account.<br />
<br />
===Export===<br />
The results can be exported as a [[GeoTIFF]] or ASCII file, allowing you to further process the results of the calculations performed in the {{software}}.<br />
See the article on [[Geo_Data#Export_raster_data|Geo data]] for more information.<br />
<br />
===Save===<br />
The results of the calculation can be saved in the form of an inactive copy of the overlay. This creates an exact duplicate of the overlay, including it's attributes, legend, and current results. The duplicate will be {{inlink|Active|inactive}}, so that when further calculations take place the duplicate still retains the results it had when it was created. The original overlay is unaffected, meaning if it was (still) active it would still be recalculated when new calculations take place. Because the duplicate is not active, saving an overlay will not affect the time it takes for the project to recalculate.<br />
<br />
==Settings==<br />
Grid overlays offer a number of settings to configure them to fit your use-case.<br />
<br />
===Shared settings===<br />
The grid overlays share a few settings, which influence the accuracy of the calculations. Depending on the calculation performed and the use-case forming the [[project]]'s context, it may be desirable to tweak the settings used for the grid overlays. For performance reasons it is not possible to set grid overlay settings to different values for different overlays in the same project.<br />
<br />
====Grid size====<br />
The 3D world is divided up into cells of the specified size. The more cells that need to be calculated, the more resources (and in the end: time) it will take to complete the calculation. Depending on the use-case and the calculation being performed, it may be desirable to change the grid size used for the grid overlays. <br />
To change the grid cell size, see {{inlink|configuring grid settings}}. <br />
<br />
The maximum amount of cells any given overlay or result type can have is {{max cells}} individual cells. For any given overlay, this includes the results of all timeframes of that overlay.<br />
Per project it is possible to have an [[Overlay]] with result types where the maximum amount of grid cells is {{max cells|group}} for the Overlay and the result types in total. You can have multiple Overlays + result type groups in your project. For example a [[Flooding Overlay]] with result types (max {{max cells|group}} grid cells) and also a [[Heat Overlay]] with result types (also max {{max cells|group}} grid cells). You can then for example add the [[Rainfall Overlay]] with result types (also max {{max cells|group}} grid cells) etc.<br />
<br />
The maximum a mount of cells in a [[Project]] in total is {{max cells|project}} individual cells. This includes all timeframes of all Grid Overlays, both active and inactive. Exceeding this amount will prevent the {{software}} from performing any further calculations of the [[Project]] until the amount of cells is reduced.<br />
<br />
''Note: if you select a grid size which does not neatly divide your project size, the south- and eastern edges of the project may not be covered by the grid, and not taken into account during a calculation.<br />
<br />
====Grid Accuracy Threshold====<br />
As the grid size decreases (and thus more cells exist in the project), calculations will take longer to complete. Under normal circumstances, when a calculation is based on geographical parameters, all contents of the cell are checked and all objects relevant to the calculation are taken into consideration based on how much of the cell is covered by it. When the grid size falls below this threshold, the method for determining these parameters changes. Instead, the exact center of the cell is checked, and if relevant data is found it is taken into consideration as if it were present in the entire cell. This is less accurate, but allows the calculation to complete faster.<br />
<br />
===Individual settings===<br />
Each individual grid overlay also has a few settings which can be set per grid overlay. These settings should be tweaked based on the actual meaning, intent, and impact, of the displayed results.<br />
<br />
====Active====<br />
Whether the grid overlay is active or not. When an overlay is inactive, the output of the overlay is not recalculated when an update or recalculation takes place. This means the results calculated by a grid overlay can be stored and inspected in a project without the computational overhead of performing the underlying calculation anew. This also means that the overlay's output may not represent the most recent evaluation of the state of the project. Instead, this option can be used to create results based on multiple scenarios, and to compare those to one another or to calculations which are updated along with changes in the project.<br />
<br />
See also: [[How_to_set_an_Overlay_to_active_or_inactive|How to set an Overlay to active or inactive]]<br />
<br />
====Legend====<br />
The visualization of the grid overlay in the [[3D world]] can be changed by providing a legend for the grid overlay. The legend of a grid overlay consists of a list of values with related captions and colors. When that specific value is output by a grid cell, that grid cell is colored in the defined color. If the value lies between two defined values, the color will lie proportionally between the colors related to the defined values.<br />
<br />
====Difference option====<br />
Depending on the [[action]]s an end-user can take during a session, the difference between two [[maptype|states]] of a calculated overlay may not be directly visible. To help gain insight into the differences in the results of grid calculations, a grid overlay may be given a difference option. This means the end-user can activate a variant of the overlay which shows the amount of change between the original values, and the values resulting from the planned actions. This is effectively a separate grid with its own values, based on the actual calculation. The difference overlay can be further configured with its own legend.<br />
<br />
==Configuring grid overlays==<br />
{{Editor location|Overlays}}<br />
<br />
===Configuring grid settings===<br />
When any grid overlay has been added to a project, it is possible to change the settings for the grid calculations. The grid settings are shared across all overlays, so adjusting the settings via one grid overlay will affect all grid overlays in the project.<br />
{{Editor steps|title=configure the Grid Overlay settings|Select any grid overlay in the editor.|On the [[right panel]], select "Change Grid".|Change the cell size to the desired size.|Change accuracy threshold to the desired threshold.|Select "Send".}}<br />
<gallery mode="nolines"><br />
File:Select_grid_overlay.jpg|Select a grid overlay<br />
File:Select_change_grid.jpg|Select Change Grid in the right panel<br />
File:Change_cell_size.jpg| Change the cell size<br />
File:Change_threshold.jpg| Change the accuracy threshold<br />
File: Select_send.jpg| Select Send<br />
</gallery><br />
<br />
{{Editor steps|title=revert the Grid Overlay settings to default values|Select any grid overlay in the editor.|On the [[right panel]], select "Change Grid".|Select "Reset to Default".|Select "Send".}}<br />
<gallery mode="nolines"><br />
File:Select_grid_overlay.jpg|Select a grid overlay<br />
File:Select_change_grid.jpg|Select Change Grid in the right panel<br />
File:Select_default.jpg| Select Reset to Default<br />
File: Select_send.jpg| Select Send<br />
</gallery><br />
<br />
===Configuring grid legend and visualization===<br />
To start defining the visualization for the grid overlay, first activate the custom overlay function for the overlay.<br />
{{Editor steps|title=activate the custom legend|Select the grid overlay you wish to configure in the editor.|On the [[right panel]], select the "Legend" tab.|Make sure "Has Custom Legend" is checked.}}<br />
<gallery mode="nolines"><br />
File:Select_grid_overlay.jpg|Select a grid overlay<br />
File:Select_legend.jpg|Select Legend in the right panel<br />
File:Select_custom.jpg| Select Has Custom Legend<br />
</gallery><br />
<br />
Next, make sure that each color or value you wish to use is defined in the list of legend items.<br />
{{Editor steps|title=add a new legend item|Select the grid overlay you wish to configure in the editor.|On the [[right panel]], select the "Legend" tab.|Select "Add" at the bottom of the [[right panel]].|The new legend item is now added with a value of 0.}}<br />
<gallery mode="nolines"><br />
File:Select_grid_overlay.jpg|Select a grid overlay<br />
File:Select_legend.jpg|Select Legend in the right panel<br />
File:Select_add1.jpg| Select Add<br />
File:New_item.jpg| This is the new Legend item<br />
</gallery><br />
<br />
{{Editor steps|title=remove legend item|Select the grid overlay you wish to configure in the editor.|On the [[right panel]], select the "Legend" tab.|Select the legend item you wish to remove.|Select "Remove" at the bottom of the [[right panel]].|The legend item is now removed.}}<br />
<gallery mode="nolines"><br />
File:Select_grid_overlay.jpg|Select a grid overlay<br />
File:Select_legend.jpg|Select Legend in the right panel<br />
File:New_item.jpg| This is the new Legend item<br />
File:Select_remove1.jpg| Select Remove<br />
</gallery><br />
<br />
{{Editor steps|title=edit a legend item|Select the grid overlay you wish to configure in the editor.|On the [[right panel]], select the "Legend" tab.|Select the legend item you wish to adjust.|Change the "value" to the value at which you want to show the color.<br><br />
Note that the legend items are automatically sorted by value.|Click on the color drop-down and select the color you wish to show.|Change the text in the top input field of the legend item to change the caption for this color in the legend.}}<br />
<gallery mode="nolines"><br />
File:Select_grid_overlay.jpg|Select a grid overlay<br />
File:Select_legend.jpg|Select Legend in the right panel<br />
File:New_item.jpg| This is the new Legend item<br />
File:Change_value.jpg| Change the value of the color<br />
File:Change_color.jpg| Change the color of the Legend item<br />
File:Change_name.jpg| Change the name of the Legend item<br />
</gallery><br />
<br />
===Configuring difference option===<br />
You can configure whether the end-user can activate a difference overlay or not on a per-overlay basis.<br />
{{Editor steps|title=activate the difference option|Select the grid overlay in the editor.|On the [[right panel]], make sure "Show Difference Option" is checked.}}<br />
<gallery mode="nolines"><br />
File:Select_grid_overlay.jpg|Select a grid overlay<br />
File:Difference_option.jpg|Check the Show Difference option<br />
</gallery><br />
<br />
{{Editor steps|title=deactivate the difference option|Select the grid overlay in the editor.|On the [[right panel]], make sure "Show Difference Option" is unchecked.}}<br />
<gallery mode="nolines"><br />
File:Select_grid_overlay.jpg|Select a grid overlay<br />
File:Unchecked_difference.jpg|Uncheck the Show Difference option<br />
</gallery><br />
<br />
==Grid recalculation==<br />
During a [[Test_Run| test run]], grids are automatically recalculated whenever a change is made to the state of the [[3D world]], including non-geographical data such as [[global]]s or [[attribute]]s. While editing, a grid is also updated when [[3D World]] data is changed and [[Calculation_panel#Auto-update_indicators|Auto-update]] is on. However, some parameters can be changed in the editor which cannot be changed during a session, such as the properties or attributes of overlays. To prevent more complex overlays slowing down editing work, a grid overlay is not always automatically recalculated when these kinds of parameters are changed. To force the grids to recalculate, the "Update Now" option can be used on any grid overlay. This will force all grids to recalculate.<br />
<br />
{{Editor steps|title=force grid overlays to recalculate|Select any grid overlay in the editor.|On the [[right panel]], select "Update Now".}}<br />
<gallery mode="nolines"><br />
File:Select_grid_overlay.jpg|Select a grid overlay<br />
File:Update_now.JPG|Select the Update Now option<br />
</gallery><br />
<br />
Some overlays could be a delaying factor in the project. For more information see the [[troubleshooting]] page.<br />
<br />
===Delayed calculation===<br />
During business hours ({{business hours}}), there is a maximum calculation time of 0.5 hour. If a calculation takes longer than that, it will time out after 1 hour. Outside of business hours, calculations will not time out. If necessary, it is possible to postpone the recalculation of overlays until after business hours.<br />
<br />
{{Editor steps|title=postpone grid overlay recalculation|Select any grid overlay in the editor.|On the [[right panel]], select "Update Later".}}<br />
<br />
{{Overlay nav}}</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Keep_alive&diff=50203Keep alive2023-01-26T09:56:49Z<p>Vincent@tygron.nl: </p>
<hr />
<div>The Keep Alive option can be found in the [[file menu]] of a [[project]] in the [[editor]] and is an option to keep a [[session]] running on the [[server]], a so called Keep Alive session, even after the [[client]] is closed. The keep alive mode delays an automatic shut-down of your project session due to a [[time-out]].<br />
<br />
There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is comonly used in the folowing use cases:<br />
<br />
* For other users to be able to join. This enables the project to be accessed by users with only join only access rights. This can be implemented in a (multi user) stakeholder [[impact session]], where an organisation has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the {{software}}.<br />
<br />
* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.<br />
<br />
* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automtically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.<br />
<br />
==How to use the Keep Alive option==<br />
{{howto|title=use the Keep Alive option|<br />
| Click on the [[File]] tab in the [[Editor]].<br />
| On the Details page, select the checkbox in the Keep Active section.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveCheckbox1.jpg|On the Details page, select the checkbox in the Keep Active section.<br />
</gallery><br />
<br />
==How to join a Keep Alive session==<br />
{{howto|title=join a Keep Alive session|<br />
| Select the Join option from the main menu.<br />
| Select the project to join from the list of available projects that are running.<br />
}}<br />
<br />
<gallery><br />
File:JoinOption1.jpg|Select the Join option from the main menu.<br />
File:SelectProjectToJoin1.jpg|Select the project to join from the list of available projects that are running.<br />
</gallery><br />
<br />
==How to end a Keep Alive session==<br />
{{howto|title=end a Keep Alive session|<br />
| Click on the File tab in the Editor.<br />
| On the Details page, deselect the checkbox in the Keep Active section.<br />
| Exit the project as usual.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveUnCheckbox1.jpg|On the Details page, deselect the checkbox in the Keep Active section.<br />
File:ExitProject1.jpg|Exit the project as usual.<br />
</gallery></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Keep_alive&diff=50198Keep alive2023-01-26T09:54:59Z<p>Vincent@tygron.nl: </p>
<hr />
<div>The Keep Alive option can be found in the [[file menu]] of a [[project]] in the [[editor]] and is an option to keep a [[session]] running on the [[server]], a so called Keep Alive session, even after the [[client]] is closed. The keep alive mode delays an automatic shut-down of your project session due to a [[time-out]].<br />
<br />
There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is comonly used in the folowing use cases:<br />
<br />
* For other users to be able to join. This enables the project to be accessed by users with only join only access rights. This can be implemented in a (multi user) stakeholder impact sessions, where an organisation has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the Tygron Platform.<br />
<br />
* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.<br />
<br />
* To finalize a long calculation. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automtically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.<br />
<br />
==How to use the Keep Alive option==<br />
{{howto|title=use the Keep Alive option|<br />
| Click on the [[File]] tab in the [[Editor]].<br />
| On the Details page, select the checkbox in the Keep Active section.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveCheckbox1.jpg|On the Details page, select the checkbox in the Keep Active section.<br />
</gallery><br />
<br />
==How to join a Keep Alive session==<br />
{{howto|title=join a Keep Alive session|<br />
| Select the Join option from the main menu.<br />
| Select the project to join from the list of available projects that are running.<br />
}}<br />
<br />
<gallery><br />
File:JoinOption1.jpg|Select the Join option from the main menu.<br />
File:SelectProjectToJoin1.jpg|Select the project to join from the list of available projects that are running.<br />
</gallery><br />
<br />
==How to end a Keep Alive session==<br />
{{howto|title=end a Keep Alive session|<br />
| Click on the File tab in the Editor.<br />
| On the Details page, deselect the checkbox in the Keep Active section.<br />
| Exit the project as usual.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveUnCheckbox1.jpg|On the Details page, deselect the checkbox in the Keep Active section.<br />
File:ExitProject1.jpg|Exit the project as usual.<br />
</gallery></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Keep_alive&diff=50196Keep alive2023-01-26T09:52:55Z<p>Vincent@tygron.nl: </p>
<hr />
<div>The Keep Alive option can be found in the file menu of a project in the editor and is an option to keep a session running on the server, a so called Keep Alive session, even after the client is closed. The keep alive mode delays an automatic shut-down of your project session due to a time-out.<br />
<br />
There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is comonly used in the folowing use cases:<br />
<br />
* For other users to be able to join. This enables the project to be accessed by users with only join only access rights. This can be implemented in a (multi user) stakeholder impact sessions, where an organisation has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the Tygron Platform.<br />
<br />
* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.<br />
<br />
* To finalize a long calculation. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automtically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.<br />
<br />
==How to use the Keep Alive option==<br />
{{howto|title=use the Keep Alive option|<br />
| Click on the [[File]] tab in the [[Editor]].<br />
| On the Details page, select the checkbox in the Keep Active section.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveCheckbox1.jpg|On the Details page, select the checkbox in the Keep Active section.<br />
</gallery><br />
<br />
==How to join a Keep Alive session==<br />
{{howto|title=join a Keep Alive session|<br />
| Select the Join option from the main menu.<br />
| Select the project to join from the list of available projects that are running.<br />
}}<br />
<br />
<gallery><br />
File:JoinOption1.jpg|Select the Join option from the main menu.<br />
File:SelectProjectToJoin1.jpg|Select the project to join from the list of available projects that are running.<br />
</gallery><br />
<br />
==How to end a Keep Alive session==<br />
{{howto|title=end a Keep Alive session|<br />
| Click on the File tab in the Editor.<br />
| On the Details page, deselect the checkbox in the Keep Active section.<br />
| Exit the project as usual.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveUnCheckbox1.jpg|On the Details page, deselect the checkbox in the Keep Active section.<br />
File:ExitProject1.jpg|Exit the project as usual.<br />
</gallery></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Keep_alive&diff=50195Keep alive2023-01-26T09:51:24Z<p>Vincent@tygron.nl: </p>
<hr />
<div>The Keep Alive option can be found in the file menu of a project in the editor and is an option to keep a session running on the server, a so called Keep Alive session, even after the client is closed. The keep alive mode delays an automatic shut-down of your project session due to a time-out.<br />
<br />
There are a couple of scenarios where keeping a session alive in the Tygron Platform is desirable. This option is comonly used in the folowing use cases:<br />
<br />
* For other users to be able to join. This enables the project to be accessed by users with only join only access rights. This can be implemented in a (multi user) stakeholder impact sessions, where an organisation has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the Tygron Platform.<br />
<br />
* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.<br />
<br />
* To finalize a long calculation. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automtically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.<br />
<br />
==How to use the Keep Alive option==<br />
{{howto|title=use the Keep Alive option|<br />
| Click on the [[File]] tab in the [[Editor]].<br />
| On the Details page, select the checkbox in the Keep Active section.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveCheckbox1.jpg|On the Details page, select the checkbox in the Keep Active section.<br />
</gallery><br />
<br />
==How to join a Keep Alive session==<br />
{{howto|title=join a Keep Alive session|<br />
| Select the Join option from the main menu.<br />
| Select the project to join from the list of available projects that are running.<br />
}}<br />
<br />
<gallery><br />
File:JoinOption1.jpg|Select the Join option from the main menu.<br />
File:SelectProjectToJoin1.jpg|Select the project to join from the list of available projects that are running.<br />
</gallery><br />
<br />
==How to end a Keep Alive session==<br />
{{howto|title=end a Keep Alive session|<br />
| Click on the File tab in the Editor.<br />
| On the Details page, deselect the checkbox in the Keep Active section.<br />
| Exit the project as usual.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveUnCheckbox1.jpg|On the Details page, deselect the checkbox in the Keep Active section.<br />
File:ExitProject1.jpg|Exit the project as usual.<br />
</gallery></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Keep_alive&diff=50194Keep alive2023-01-26T09:49:53Z<p>Vincent@tygron.nl: /* See also */</p>
<hr />
<div>The Keep Alive option can be found in the file menu of a project in the editor and is an option to keep a session running on the server, a so called Keep Alive session, even after the client is closed. The keep alive mode delays an automatic shut-down of your project session due to a time-out.<br />
<br />
There are a couple of scenarios where keeping a session alive in the Tygron Platform is desirable. This option is comonly used in the folowing use cases:<br />
<br />
* For other users to be able to join. This enables the project to be accessed by users with only join only access rights. This can be implemented in a stakeholder impact sessions, where an organisation has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the Tygron Platform.<br />
<br />
* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.<br />
<br />
* To finalize a long calculation. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automtically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.<br />
<br />
==How to use the Keep Alive option==<br />
{{howto|title=use the Keep Alive option|<br />
| Click on the [[File]] tab in the [[Editor]].<br />
| On the Details page, select the checkbox in the Keep Active section.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveCheckbox1.jpg|On the Details page, select the checkbox in the Keep Active section.<br />
</gallery><br />
<br />
==How to join a Keep Alive session==<br />
{{howto|title=join a Keep Alive session|<br />
| Select the Join option from the main menu.<br />
| Select the project to join from the list of available projects that are running.<br />
}}<br />
<br />
<gallery><br />
File:JoinOption1.jpg|Select the Join option from the main menu.<br />
File:SelectProjectToJoin1.jpg|Select the project to join from the list of available projects that are running.<br />
</gallery><br />
<br />
==How to end a Keep Alive session==<br />
{{howto|title=end a Keep Alive session|<br />
| Click on the File tab in the Editor.<br />
| On the Details page, deselect the checkbox in the Keep Active section.<br />
| Exit the project as usual.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveUnCheckbox1.jpg|On the Details page, deselect the checkbox in the Keep Active section.<br />
File:ExitProject1.jpg|Exit the project as usual.<br />
</gallery></div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Keep_alive&diff=50189Keep alive2023-01-26T09:46:46Z<p>Vincent@tygron.nl: </p>
<hr />
<div>The Keep Alive option can be found in the file menu of a project in the editor and is an option to keep a session running on the server, a so called Keep Alive session, even after the client is closed. The keep alive mode delays an automatic shut-down of your project session due to a time-out.<br />
<br />
There are a couple of scenarios where keeping a session alive in the Tygron Platform is desirable. This option is comonly used in the folowing use cases:<br />
<br />
* For other users to be able to join. This enables the project to be accessed by users with only join only access rights. This can be implemented in a stakeholder impact sessions, where an organisation has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the Tygron Platform.<br />
<br />
* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.<br />
<br />
* To finalize a long calculation. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automtically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.<br />
<br />
==How to use the Keep Alive option==<br />
{{howto|title=use the Keep Alive option|<br />
| Click on the [[File]] tab in the [[Editor]].<br />
| On the Details page, select the checkbox in the Keep Active section.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveCheckbox1.jpg|On the Details page, select the checkbox in the Keep Active section.<br />
</gallery><br />
<br />
==How to join a Keep Alive session==<br />
{{howto|title=join a Keep Alive session|<br />
| Select the Join option from the main menu.<br />
| Select the project to join from the list of available projects that are running.<br />
}}<br />
<br />
<gallery><br />
File:JoinOption1.jpg|Select the Join option from the main menu.<br />
File:SelectProjectToJoin1.jpg|Select the project to join from the list of available projects that are running.<br />
</gallery><br />
<br />
==How to end a Keep Alive session==<br />
{{howto|title=end a Keep Alive session|<br />
| Click on the File tab in the Editor.<br />
| On the Details page, deselect the checkbox in the Keep Active section.<br />
| Exit the project as usual.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveUnCheckbox1.jpg|On the Details page, deselect the checkbox in the Keep Active section.<br />
File:ExitProject1.jpg|Exit the project as usual.<br />
</gallery><br />
<br />
==See also==</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Keep_alive&diff=50187Keep alive2023-01-26T09:46:06Z<p>Vincent@tygron.nl: </p>
<hr />
<div>The Keep Alive option can be found in the file menu of a project in the editor and is an option to keep a session running on the server, a so called Keep Alive session, even after the client is closed. The keep alive mode avoids shut-down of your project session due to a time-out.<br />
<br />
There are a couple of scenarios where keeping a session alive in the Tygron Platform is desirable. This option is comonly used in the folowing use cases:<br />
<br />
* For other users to be able to join. This enables the project to be accessed by users with only join only access rights. This can be implemented in a stakeholder impact sessions, where an organisation has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the Tygron Platform.<br />
<br />
* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.<br />
<br />
* To finalize a long calculation. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automtically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.<br />
<br />
==How to use the Keep Alive option==<br />
{{howto|title=use the Keep Alive option|<br />
| Click on the [[File]] tab in the [[Editor]].<br />
| On the Details page, select the checkbox in the Keep Active section.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveCheckbox1.jpg|On the Details page, select the checkbox in the Keep Active section.<br />
</gallery><br />
<br />
==How to join a Keep Alive session==<br />
{{howto|title=join a Keep Alive session|<br />
| Select the Join option from the main menu.<br />
| Select the project to join from the list of available projects that are running.<br />
}}<br />
<br />
<gallery><br />
File:JoinOption1.jpg|Select the Join option from the main menu.<br />
File:SelectProjectToJoin1.jpg|Select the project to join from the list of available projects that are running.<br />
</gallery><br />
<br />
==How to end a Keep Alive session==<br />
{{howto|title=end a Keep Alive session|<br />
| Click on the File tab in the Editor.<br />
| On the Details page, deselect the checkbox in the Keep Active section.<br />
| Exit the project as usual.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveUnCheckbox1.jpg|On the Details page, deselect the checkbox in the Keep Active section.<br />
File:ExitProject1.jpg|Exit the project as usual.<br />
</gallery><br />
<br />
==See also==</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Keep_alive&diff=50186Keep alive2023-01-26T09:45:17Z<p>Vincent@tygron.nl: /* How does the Keep Alive option relate to the Tygron Geodesign Platform? */</p>
<hr />
<div>The Keep Alive option can be found in the file menu of a project in the editor and is an option to keep a session running on the server, a so called Keep Alive session, even after the client is closed. The keep alive mode avoids shut-down of your project due to a time-out.<br />
<br />
There are a couple of scenarios where keeping a session alive in the Tygron Platform is desirable. This option is comonly used in the folowing use cases:<br />
<br />
* For other users to be able to join. This enables the project to be accessed by users with only join only access rights. This can be implemented in a stakeholder impact sessions, where an organisation has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the Tygron Platform.<br />
<br />
* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.<br />
<br />
* To finalize a long calculation. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automtically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.<br />
<br />
==How to use the Keep Alive option==<br />
{{howto|title=use the Keep Alive option|<br />
| Click on the [[File]] tab in the [[Editor]].<br />
| On the Details page, select the checkbox in the Keep Active section.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveCheckbox1.jpg|On the Details page, select the checkbox in the Keep Active section.<br />
</gallery><br />
<br />
==How to join a Keep Alive session==<br />
{{howto|title=join a Keep Alive session|<br />
| Select the Join option from the main menu.<br />
| Select the project to join from the list of available projects that are running.<br />
}}<br />
<br />
<gallery><br />
File:JoinOption1.jpg|Select the Join option from the main menu.<br />
File:SelectProjectToJoin1.jpg|Select the project to join from the list of available projects that are running.<br />
</gallery><br />
<br />
==How to end a Keep Alive session==<br />
{{howto|title=end a Keep Alive session|<br />
| Click on the File tab in the Editor.<br />
| On the Details page, deselect the checkbox in the Keep Active section.<br />
| Exit the project as usual.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveUnCheckbox1.jpg|On the Details page, deselect the checkbox in the Keep Active section.<br />
File:ExitProject1.jpg|Exit the project as usual.<br />
</gallery><br />
<br />
==See also==</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Keep_alive&diff=50185Keep alive2023-01-26T09:45:08Z<p>Vincent@tygron.nl: /* What is Keep Alive? */</p>
<hr />
<div>The Keep Alive option can be found in the file menu of a project in the editor and is an option to keep a session running on the server, a so called Keep Alive session, even after the client is closed. The keep alive mode avoids shut-down of your project due to a time-out.<br />
<br />
==How does the Keep Alive option relate to the Tygron Geodesign Platform?==<br />
<br />
There are a couple of scenarios where keeping a session alive in the Tygron Platform is desirable. This option is comonly used in the folowing use cases:<br />
<br />
* For other users to be able to join. This enables the project to be accessed by users with only join only access rights. This can be implemented in a stakeholder impact sessions, where an organisation has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the Tygron Platform.<br />
<br />
* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.<br />
<br />
* To finalize a long calculation. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automtically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.<br />
<br />
==How to use the Keep Alive option==<br />
{{howto|title=use the Keep Alive option|<br />
| Click on the [[File]] tab in the [[Editor]].<br />
| On the Details page, select the checkbox in the Keep Active section.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveCheckbox1.jpg|On the Details page, select the checkbox in the Keep Active section.<br />
</gallery><br />
<br />
==How to join a Keep Alive session==<br />
{{howto|title=join a Keep Alive session|<br />
| Select the Join option from the main menu.<br />
| Select the project to join from the list of available projects that are running.<br />
}}<br />
<br />
<gallery><br />
File:JoinOption1.jpg|Select the Join option from the main menu.<br />
File:SelectProjectToJoin1.jpg|Select the project to join from the list of available projects that are running.<br />
</gallery><br />
<br />
==How to end a Keep Alive session==<br />
{{howto|title=end a Keep Alive session|<br />
| Click on the File tab in the Editor.<br />
| On the Details page, deselect the checkbox in the Keep Active section.<br />
| Exit the project as usual.<br />
}}<br />
<br />
<gallery><br />
File:FileTab1.jpg|Click on the File tab in the Editor.<br />
File:KeepAliveUnCheckbox1.jpg|On the Details page, deselect the checkbox in the Keep Active section.<br />
File:ExitProject1.jpg|Exit the project as usual.<br />
</gallery><br />
<br />
==See also==</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Requirements&diff=49794Requirements2023-01-19T12:46:01Z<p>Vincent@tygron.nl: /* Project Map */</p>
<hr />
<div>Below are the computer hardware requirements needed to run the Tygron Platform Client application.<br />
<br />
==Hardware==<br />
Your hardware is automatically categorized into the following scores. The total score of your computer is based on the lowest scoring component, and will affect both the default graphical settings.<br />
<br />
{| class="wikitable"<br />
|+<br />
|-<br />
|Graphics Setting<br />
|CPU (Processor)<br />
|Memory (RAM)<br />
|GPU (Videocard)''*''<br />
|Notes on score<br />
|- style="background-color:#ffb0b0"<br />
|LOW<br />
|Celeron<br />
|At least 4GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] below 1000<br>with OpenGL 4.0<br />
|Computers with this score are not fully supported. Graphical issues and slow responses can be expected.<br />
|- style="background-color:#b0ffb0"<br />
|MEDIUM<br />
|AMD Athlon<br>Intel Core 2<br>Intel Pentium<br />
|At least 8GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] above 1000<br />
|[https://tweakers.net/pricewatch/742855/hp-omen-desktop-870-242nd/specificaties/ HP Omen Desktop 870-242nd]<br>This model is currently in active use at Tygron.<br />
|- style="background-color:#b0ffb0"<br />
|HIGH<br />
|Intel i3, i5, AMD Ryzen 5<br />
|At least 16GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] above 4000<br />
|<br />
|- style="background-color:#b0ffb0"<br />
|EXTREME<br />
|Intel i7, AMD Ryzen 7, 9<br />
|At least 32GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] above 10.000<br />
|<br />
|- style="background-color:#b0ffb0"<br />
|}<br />
:''*'' We have found that NVIDIA cards provide the best stability in comparison to Intel and AMD. Therefore, we can strongly advise NVIDIA Geforce RTX 3050 (or better) for desktop and laptops computers. We recommend looking for cards in the high-end consumer segment (GeForce), as the {{software}} does not make use of the extreme-precision capabilities of the more expensive Quadro cards.<br />
<br />
In addition, your computer must have the following:<br />
<br />
{| class="wikitable"<br />
|+<br />
|-<br />
|Screen resolution<br />
|1280 x 800 pixels or higher<br />
|-<br />
|Operating system ''**''<br />
|Windows 10, 11 (64 bit)<br />
|-<br />
| Internet connection ''***''<br />
| Required<br />
|}<br />
:''**'' Only Windows (10/11) is currently officially supported. Although it's possible to download an experimental version for linux, usage of the {{software}} on this operating system is not officially supported, and at the user's own risk. An experimental Mac OSX version is at the moment not available.<br />
:''***'' There are no specific requirements to the internet connection. However, faster connections are better, especially when working with large data sets. We also strongly advise to test the performance and connectivity of the available connection when preparing for a session or presentation using the {{software}}.<br />
<br />
===Project Map===<br />
The amount of memory (RAM) determines the maximum Project Map size that the Client application can handle on a speciffic system. Note: you can also create bigger maps directly via the API, these just can't be visualized by the Client application on a system with a smaller then required amount of RAM.<br />
The exact maximum map size also depends on the graphics setting, the table below gives an approximation.<br />
<br />
{| class="wikitable"<br />
|+<br />
|-<br />
|Project Map<br />
|Memory (RAM)<br />
|Notes on score<br />
|- style="background-color:#ffb0b0"<br />
|10x10 KM<br />
|At least 4GB<br />
| Computers with this score are not fully supported. Graphical issues and slow responses can be expected.<br />
|- style="background-color:#b0ffb0"<br />
| 20x20 KM<br />
|At least 16GB<br />
|<br />
|- style="background-color:#b0ffb0"<br />
| 30x30 KM<br />
|At least 32GB<br />
|<br />
|- style="background-color:#b0ffb0"<br />
|60x60 KM<br />
|At least 64GB<br />
|[https://www.lalashops.nl/4k-8k-videobewerking-computer-ryzen-9-5950x-3080-ti-2tb-ssd-nvme-fluister-stil-vid-r9-a2 Davinci Computer]<br>This model is currently in active use at Tygron. <br />
|- style="background-color:#b0ffb0"<br />
|}<br />
<br />
===Multi-GPU systems===<br />
When the {{software}} detects a system with multiple GPU's, such as an Intel processor's integrated graphics chip as well as a dedicated Geforce video card, you may be prompted to [[dual videocard|ensure the more powerful of the two GPU]]'s is used to run the {{software}}. Specific settings to configure this may vary per vendor. Keep in mind that some systems be also be configured to deactivate the more powerful GPU when running in a power-saving or low-battery mode. In these cases ensure that either the performance mode of the system is changed, or that the more powerful GPU remains available for the {{software}}.<br />
<br />
===Virtualization===<br />
Virtual environments are currently not supported. The {{software}}'s 3D visualization is one of its basic functionalities. To properly render a 3D environment as performant as possible, the software requires being run on a physical computer. Virtualization software (such as Citrix or VMware) is currently not supported, because the speed of 3D rendering is significantly reduced by virtualization, which abstracts direct access to the GPU, slowing the process of rendering the 3D environment.<br />
<br />
==Software==<br />
In addition to hardware requirements, the following software is also required.<br />
<br />
===Video card Drivers===<br />
Please make sure you have the latest official drivers installed for your video card from the original manufacturer. In case you upgrade your videocard to a better one from a different manufacturere, please remove the old drivers before running the Tygron Geodesign Platform again. Not removing may result in the hardware check not recognizing your new video card, and thus the platform not starting.<br />
<br />
====NVIDIA====<br />
* [http://www.nvidia.com/content/drivers/ NVIDIA Drivers]<br />
<br />
====AMD ATI====<br />
* [http://support.amd.com/en-us/download AMD ATI Drivers]<br />
<br />
====Intel====<br />
* [https://downloadcenter.intel.com/ Intel Drivers]<br />
<br />
===Browsers===<br />
For web-based interactions with the {{software}}, such as the [[web interface]], the latest (stable) versions of the following browsers are supported:<br />
* Google Chrome<br />
* Mozilla Firefox<br />
<br />
==Explanation==<br />
<br />
===Hardware===<br />
Because the {{software}} is 3D visualization software, the various hardware requirements list above must all be met. A brief clarification of why each requirement is relevant:<br />
====CPU====<br />
The processor is the general "computing" part of a computer, performing most functions of a computer. General responsiveness and performance speed of the application and the computer itself are (partly) dictated by the processor.<br />
<br />
====RAM====<br />
The memory of a computer is what allows it to actively work with data. The more memory a computer has, the more data it can keep at the ready simultaneously.<br />
<br />
====GPU====<br />
Often in the form of a videocard, the graphical processor deals with all visualization matters. This component makes the 3D visualization of the {{software}} possible. A better GPU can handle higher quality textures for more detail, better visualizattion of shadows, more generic trees in wooded areas and more fluent movements with higher frame rates.<br />
<br />
====Screen resolution====<br />
The number of pixels a computer screen physically has, usually indicated in the dimensions Width x Height (ex: 1920 x 1080). The {{software}} is a complex tool, and requires sufficient screen space to allow an overview of all options and information panels.<br />
<br />
====Internet connection====<br />
The core technology of the {{software}} is cloud-based. Your computer needs to be able to visualize the application and keep data about the project available, but the really heavy lifting in terms of calculations is done in the cloud. This means you need to be connected to the internet, and the better your internet connection the more responsive the application will be when dealing with data updates.<br />
<br />
===Software===<br />
The ability to support the use of specific software can be based on a variety of decision. A brief clarification on the supported software:<br />
<br />
====Browser====<br />
At the time of writing, Microsoft's Internet Explorer is only available on Windows for legacy reasons, and Microsoft is actively encouraging users to switch to more modern browsers. Additionally, Microsoft's Edge browser is not fully supported.</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Requirements&diff=49790Requirements2023-01-19T12:44:19Z<p>Vincent@tygron.nl: /* Hardware */</p>
<hr />
<div>Below are the computer hardware requirements needed to run the Tygron Platform Client application.<br />
<br />
==Hardware==<br />
Your hardware is automatically categorized into the following scores. The total score of your computer is based on the lowest scoring component, and will affect both the default graphical settings.<br />
<br />
{| class="wikitable"<br />
|+<br />
|-<br />
|Graphics Setting<br />
|CPU (Processor)<br />
|Memory (RAM)<br />
|GPU (Videocard)''*''<br />
|Notes on score<br />
|- style="background-color:#ffb0b0"<br />
|LOW<br />
|Celeron<br />
|At least 4GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] below 1000<br>with OpenGL 4.0<br />
|Computers with this score are not fully supported. Graphical issues and slow responses can be expected.<br />
|- style="background-color:#b0ffb0"<br />
|MEDIUM<br />
|AMD Athlon<br>Intel Core 2<br>Intel Pentium<br />
|At least 8GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] above 1000<br />
|[https://tweakers.net/pricewatch/742855/hp-omen-desktop-870-242nd/specificaties/ HP Omen Desktop 870-242nd]<br>This model is currently in active use at Tygron.<br />
|- style="background-color:#b0ffb0"<br />
|HIGH<br />
|Intel i3, i5, AMD Ryzen 5<br />
|At least 16GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] above 4000<br />
|<br />
|- style="background-color:#b0ffb0"<br />
|EXTREME<br />
|Intel i7, AMD Ryzen 7, 9<br />
|At least 32GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] above 10.000<br />
|<br />
|- style="background-color:#b0ffb0"<br />
|}<br />
:''*'' We have found that NVIDIA cards provide the best stability in comparison to Intel and AMD. Therefore, we can strongly advise NVIDIA Geforce RTX 3050 (or better) for desktop and laptops computers. We recommend looking for cards in the high-end consumer segment (GeForce), as the {{software}} does not make use of the extreme-precision capabilities of the more expensive Quadro cards.<br />
<br />
In addition, your computer must have the following:<br />
<br />
{| class="wikitable"<br />
|+<br />
|-<br />
|Screen resolution<br />
|1280 x 800 pixels or higher<br />
|-<br />
|Operating system ''**''<br />
|Windows 10, 11 (64 bit)<br />
|-<br />
| Internet connection ''***''<br />
| Required<br />
|}<br />
:''**'' Only Windows (10/11) is currently officially supported. Although it's possible to download an experimental version for linux, usage of the {{software}} on this operating system is not officially supported, and at the user's own risk. An experimental Mac OSX version is at the moment not available.<br />
:''***'' There are no specific requirements to the internet connection. However, faster connections are better, especially when working with large data sets. We also strongly advise to test the performance and connectivity of the available connection when preparing for a session or presentation using the {{software}}.<br />
<br />
===Project Map===<br />
The amount of memory (RAM) determines the maximum Project Map size that the Client application can handle on a speciffic system. Note: you can also create bigger maps directly via the API, it just can not be accessed using the Client application on a system with a smaller then required amount of RAM.<br />
The exact maximum map size also depends on the graphics setting, the table below gives an approximation.<br />
<br />
{| class="wikitable"<br />
|+<br />
|-<br />
|Project Map<br />
|Memory (RAM)<br />
|Notes on score<br />
|- style="background-color:#ffb0b0"<br />
|10x10 KM<br />
|At least 4GB<br />
| Computers with this score are not fully supported. Graphical issues and slow responses can be expected.<br />
|- style="background-color:#b0ffb0"<br />
| 20x20 KM<br />
|At least 16GB<br />
|<br />
|- style="background-color:#b0ffb0"<br />
| 30x30 KM<br />
|At least 32GB<br />
|<br />
|- style="background-color:#b0ffb0"<br />
|60x60 KM<br />
|At least 64GB<br />
|[https://www.lalashops.nl/4k-8k-videobewerking-computer-ryzen-9-5950x-3080-ti-2tb-ssd-nvme-fluister-stil-vid-r9-a2 Davinci Computer]<br>This model is currently in active use at Tygron. <br />
|- style="background-color:#b0ffb0"<br />
|}<br />
<br />
===Multi-GPU systems===<br />
When the {{software}} detects a system with multiple GPU's, such as an Intel processor's integrated graphics chip as well as a dedicated Geforce video card, you may be prompted to [[dual videocard|ensure the more powerful of the two GPU]]'s is used to run the {{software}}. Specific settings to configure this may vary per vendor. Keep in mind that some systems be also be configured to deactivate the more powerful GPU when running in a power-saving or low-battery mode. In these cases ensure that either the performance mode of the system is changed, or that the more powerful GPU remains available for the {{software}}.<br />
<br />
===Virtualization===<br />
Virtual environments are currently not supported. The {{software}}'s 3D visualization is one of its basic functionalities. To properly render a 3D environment as performant as possible, the software requires being run on a physical computer. Virtualization software (such as Citrix or VMware) is currently not supported, because the speed of 3D rendering is significantly reduced by virtualization, which abstracts direct access to the GPU, slowing the process of rendering the 3D environment.<br />
<br />
==Software==<br />
In addition to hardware requirements, the following software is also required.<br />
<br />
===Video card Drivers===<br />
Please make sure you have the latest official drivers installed for your video card from the original manufacturer. In case you upgrade your videocard to a better one from a different manufacturere, please remove the old drivers before running the Tygron Geodesign Platform again. Not removing may result in the hardware check not recognizing your new video card, and thus the platform not starting.<br />
<br />
====NVIDIA====<br />
* [http://www.nvidia.com/content/drivers/ NVIDIA Drivers]<br />
<br />
====AMD ATI====<br />
* [http://support.amd.com/en-us/download AMD ATI Drivers]<br />
<br />
====Intel====<br />
* [https://downloadcenter.intel.com/ Intel Drivers]<br />
<br />
===Browsers===<br />
For web-based interactions with the {{software}}, such as the [[web interface]], the latest (stable) versions of the following browsers are supported:<br />
* Google Chrome<br />
* Mozilla Firefox<br />
<br />
==Explanation==<br />
<br />
===Hardware===<br />
Because the {{software}} is 3D visualization software, the various hardware requirements list above must all be met. A brief clarification of why each requirement is relevant:<br />
====CPU====<br />
The processor is the general "computing" part of a computer, performing most functions of a computer. General responsiveness and performance speed of the application and the computer itself are (partly) dictated by the processor.<br />
<br />
====RAM====<br />
The memory of a computer is what allows it to actively work with data. The more memory a computer has, the more data it can keep at the ready simultaneously.<br />
<br />
====GPU====<br />
Often in the form of a videocard, the graphical processor deals with all visualization matters. This component makes the 3D visualization of the {{software}} possible. A better GPU can handle higher quality textures for more detail, better visualizattion of shadows, more generic trees in wooded areas and more fluent movements with higher frame rates.<br />
<br />
====Screen resolution====<br />
The number of pixels a computer screen physically has, usually indicated in the dimensions Width x Height (ex: 1920 x 1080). The {{software}} is a complex tool, and requires sufficient screen space to allow an overview of all options and information panels.<br />
<br />
====Internet connection====<br />
The core technology of the {{software}} is cloud-based. Your computer needs to be able to visualize the application and keep data about the project available, but the really heavy lifting in terms of calculations is done in the cloud. This means you need to be connected to the internet, and the better your internet connection the more responsive the application will be when dealing with data updates.<br />
<br />
===Software===<br />
The ability to support the use of specific software can be based on a variety of decision. A brief clarification on the supported software:<br />
<br />
====Browser====<br />
At the time of writing, Microsoft's Internet Explorer is only available on Windows for legacy reasons, and Microsoft is actively encouraging users to switch to more modern browsers. Additionally, Microsoft's Edge browser is not fully supported.</div>Vincent@tygron.nlhttps://support.tygron.com/w/index.php?title=Requirements&diff=49786Requirements2023-01-19T12:42:14Z<p>Vincent@tygron.nl: /* Hardware */</p>
<hr />
<div>Below are the computer hardware requirements needed to run the Tygron Platform Client application.<br />
<br />
==Hardware==<br />
Your hardware is automatically categorized into the following scores. The total score of your computer is based on the lowest scoring component, and will affect both the default graphical settings.<br />
<br />
{| class="wikitable"<br />
|+<br />
|-<br />
|Graphics Setting<br />
|CPU (Processor)<br />
|Memory (RAM)<br />
|GPU (Videocard)''*''<br />
|Notes on score<br />
|- style="background-color:#ffb0b0"<br />
|LOW<br />
|Celeron<br />
|At least 4GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] below 1000<br>with OpenGL 4.0<br />
|Computers with this score are not fully supported. Graphical issues and slow responses can be expected.<br />
|- style="background-color:#b0ffb0"<br />
|MEDIUM<br />
|AMD Athlon<br>Intel Core 2<br>Intel Pentium<br />
|At least 8GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] above 1000<br />
|[https://tweakers.net/pricewatch/742855/hp-omen-desktop-870-242nd/specificaties/ HP Omen Desktop 870-242nd]<br>This model is currently in active use at Tygron.<br />
|- style="background-color:#b0ffb0"<br />
|HIGH<br />
|Intel i3, i5, AMD Ryzen 5<br />
|At least 16GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] above 4000<br />
|<br />
|- style="background-color:#b0ffb0"<br />
|EXTREME<br />
|Intel i7, AMD Ryzen 7, 9<br />
|At least 32GB RAM<br />
|[http://www.videocardbenchmark.net Benchmark score] above 10.000<br />
|<br />
|- style="background-color:#b0ffb0"<br />
|}<br />
:''*'' We have found that NVIDIA cards provide the best stability in comparison to Intel and AMD. Therefore, we can strongly advise NVIDIA Geforce RTX 3050 (or better) for desktop and laptops computers. We recommend looking for cards in the high-end consumer segment (GeForce), as the {{software}} does not make use of the extreme-precision capabilities of the more expensive Quadro cards.<br />
<br />
In addition, your computer must have the following:<br />
<br />
{| class="wikitable"<br />
|+<br />
|-<br />
|Screen resolution<br />
|1280 x 800 pixels or higher<br />
|-<br />
|Operating system ''**''<br />
|Windows 10, 11 (64 bit)<br />
|-<br />
| Internet connection ''***''<br />
| Required<br />
|}<br />
:''**'' Only Windows (10/11) is currently officially supported. Although it's possible to download an experimental version for linux, usage of the {{software}} on this operating system is not officially supported, and at the user's own risk. An experimental Mac OSX version is at the moment not available.<br />
:''***'' There are no specific requirements to the internet connection. However, faster connections are better, especially when working with large data sets that are externally stored. We also strongly advise to test the performance and connectivity of the available connection when preparing for a session or presentation using the {{software}}.<br />
<br />
===Project Map===<br />
The amount of memory (RAM) determines the maximum Project Map size that the Client application can handle on a speciffic system. Note: you can also create bigger maps directly via the API, it just can not be accessed using the Client application on a system with a smaller then required amount of RAM.<br />
The exact maximum map size also depends on the graphics setting, the table below gives an approximation.<br />
<br />
{| class="wikitable"<br />
|+<br />
|-<br />
|Project Map<br />
|Memory (RAM)<br />
|Notes on score<br />
|- style="background-color:#ffb0b0"<br />
|10x10 KM<br />
|At least 4GB<br />
| Computers with this score are not fully supported. Graphical issues and slow responses can be expected.<br />
|- style="background-color:#b0ffb0"<br />
| 20x20 KM<br />
|At least 16GB<br />
|<br />
|- style="background-color:#b0ffb0"<br />
| 30x30 KM<br />
|At least 32GB<br />
|<br />
|- style="background-color:#b0ffb0"<br />
|60x60 KM<br />
|At least 64GB<br />
|[https://www.lalashops.nl/4k-8k-videobewerking-computer-ryzen-9-5950x-3080-ti-2tb-ssd-nvme-fluister-stil-vid-r9-a2 Davinci Computer]<br>This model is currently in active use at Tygron. <br />
|- style="background-color:#b0ffb0"<br />
|}<br />
<br />
===Multi-GPU systems===<br />
When the {{software}} detects a system with multiple GPU's, such as an Intel processor's integrated graphics chip as well as a dedicated Geforce video card, you may be prompted to [[dual videocard|ensure the more powerful of the two GPU]]'s is used to run the {{software}}. Specific settings to configure this may vary per vendor. Keep in mind that some systems be also be configured to deactivate the more powerful GPU when running in a power-saving or low-battery mode. In these cases ensure that either the performance mode of the system is changed, or that the more powerful GPU remains available for the {{software}}.<br />
<br />
===Virtualization===<br />
Virtual environments are currently not supported. The {{software}}'s 3D visualization is one of its basic functionalities. To properly render a 3D environment as performant as possible, the software requires being run on a physical computer. Virtualization software (such as Citrix or VMware) is currently not supported, because the speed of 3D rendering is significantly reduced by virtualization, which abstracts direct access to the GPU, slowing the process of rendering the 3D environment.<br />
<br />
==Software==<br />
In addition to hardware requirements, the following software is also required.<br />
<br />
===Video card Drivers===<br />
Please make sure you have the latest official drivers installed for your video card from the original manufacturer. In case you upgrade your videocard to a better one from a different manufacturere, please remove the old drivers before running the Tygron Geodesign Platform again. Not removing may result in the hardware check not recognizing your new video card, and thus the platform not starting.<br />
<br />
====NVIDIA====<br />
* [http://www.nvidia.com/content/drivers/ NVIDIA Drivers]<br />
<br />
====AMD ATI====<br />
* [http://support.amd.com/en-us/download AMD ATI Drivers]<br />
<br />
====Intel====<br />
* [https://downloadcenter.intel.com/ Intel Drivers]<br />
<br />
===Browsers===<br />
For web-based interactions with the {{software}}, such as the [[web interface]], the latest (stable) versions of the following browsers are supported:<br />
* Google Chrome<br />
* Mozilla Firefox<br />
<br />
==Explanation==<br />
<br />
===Hardware===<br />
Because the {{software}} is 3D visualization software, the various hardware requirements list above must all be met. A brief clarification of why each requirement is relevant:<br />
====CPU====<br />
The processor is the general "computing" part of a computer, performing most functions of a computer. General responsiveness and performance speed of the application and the computer itself are (partly) dictated by the processor.<br />
<br />
====RAM====<br />
The memory of a computer is what allows it to actively work with data. The more memory a computer has, the more data it can keep at the ready simultaneously.<br />
<br />
====GPU====<br />
Often in the form of a videocard, the graphical processor deals with all visualization matters. This component makes the 3D visualization of the {{software}} possible. A better GPU can handle higher quality textures for more detail, better visualizattion of shadows, more generic trees in wooded areas and more fluent movements with higher frame rates.<br />
<br />
====Screen resolution====<br />
The number of pixels a computer screen physically has, usually indicated in the dimensions Width x Height (ex: 1920 x 1080). The {{software}} is a complex tool, and requires sufficient screen space to allow an overview of all options and information panels.<br />
<br />
====Internet connection====<br />
The core technology of the {{software}} is cloud-based. Your computer needs to be able to visualize the application and keep data about the project available, but the really heavy lifting in terms of calculations is done in the cloud. This means you need to be connected to the internet, and the better your internet connection the more responsive the application will be when dealing with data updates.<br />
<br />
===Software===<br />
The ability to support the use of specific software can be based on a variety of decision. A brief clarification on the supported software:<br />
<br />
====Browser====<br />
At the time of writing, Microsoft's Internet Explorer is only available on Windows for legacy reasons, and Microsoft is actively encouraging users to switch to more modern browsers. Additionally, Microsoft's Edge browser is not fully supported.</div>Vincent@tygron.nl