Search results

Jump to navigation Jump to search
  • ...scription=The depth of the ground water level, relative to the [[Elevation model|surface]] ==Default data==
    1 KB (199 words) - 15:38, 23 February 2023
  • ...scription=The depth of the ground water level, relative to the [[Elevation model|surface]] ==Default data==
    1 KB (199 words) - 15:38, 23 February 2023
  • |Prepare a [[GeoJSON]] file with the desired data for the [[Sewer area (Water Overlay)|sewer area]]s, most importantly the [[ |Select the 'import' option. This will open the [[Geo Data Wizard|Geo data wizard]].
    1 KB (204 words) - 15:29, 30 January 2024
  • |description=Whether to use foliage data from [[Area]]s instead of the calculated foliage decks from functions with *[[Foliage height calculation model (Heat Overlay)]]
    648 bytes (83 words) - 14:41, 15 March 2024
  • {{Editor steps|title=import terrain height data |Your original DTM is replaced by the GeoTIFF where the GeoTIFF data overlapped with the project area.
    2 KB (271 words) - 14:51, 1 February 2024
  • * [[KNMI Weather data|KNMI Weather data]] * [[How to import KNMI weather data into Microsoft Excel]]
    811 bytes (106 words) - 14:34, 15 March 2024
  • ...a [[Session]], are collectively referred to as the {{software}}'s traffic model. ==Data==
    4 KB (655 words) - 16:27, 27 January 2023
  • ...evant for roads, intersections, and bridges. This is part of the [[traffic model]], in turn affecting the calculations for the [[Traffic Overlay]]s. | overwritten=based on data in the [[Project Sources|NSL]].
    637 bytes (84 words) - 14:33, 26 January 2024
  • ...evant for roads, intersections, and bridges. This is part of the [[traffic model]], in turn affecting the calculations for the [[Traffic Overlay]]s. | overwritten=based on data in the [[Project Sources|NSL]].
    635 bytes (84 words) - 14:33, 26 January 2024
  • ...evant for roads, intersections, and bridges. This is part of the [[traffic model]], in turn affecting the calculations for the [[Traffic Overlay]]s. | overwritten=based on data in the [[Project Sources|NSL]].
    641 bytes (84 words) - 14:40, 26 January 2024
  • ...evant for roads, intersections, and bridges. This is part of the [[traffic model]], in turn affecting the calculations for the [[Traffic Overlay]]s. | overwritten=based on data in the [[Project Sources|NSL]].
    635 bytes (84 words) - 14:40, 26 January 2024
  • ...ore this water indefinitely, slowly remove the water from the hydrological model, or let the water flow in a controlled fashion back onto the surface. Sewer ...assume there is an appropriate amount of water present in or added to the model for the sewer to function in a relevant capacity.
    3 KB (462 words) - 16:54, 30 January 2024
  • * No data values are not allowed. |seealso=*[[Surface model (Water Overlay)]]
    567 bytes (83 words) - 08:47, 26 January 2024
  • * No data values are not allowed. |seealso=*[[Surface model (Water Overlay)]]
    567 bytes (83 words) - 08:48, 26 January 2024
  • GeoTIFF is a file format for geographical raster data. It is an image file format containing additional Geo metadata, such as the ...import_a GeoTIFF to change the elevation model|Changing]] the [[Elevation model]] of the current situation of your project.
    2 KB (351 words) - 14:54, 1 February 2024
  • ...n height brush]] is used in selection mode, modifications to the elevation model are made in 2 explicit steps. {{howto|title=modify the elevation model in selection mode
    1 KB (175 words) - 16:26, 30 January 2024
  • A height sector is a data item which store the height data of the [[Elevation model]]. Each height sector is a square tile of 500m x 500m. Height values are st * [[How to change how the default elevation model is generated]]
    2 KB (272 words) - 14:32, 29 February 2024
  • ...for [[3D Visualization]]s or calculations, there are situations where the data from that file should also be included as other [[Item]]s which are entirel {{howto|title=import a CityGML/CityJSON file for 2d spatial data
    1 KB (235 words) - 15:13, 30 January 2024
  • ...between 0m and 100m. No data values are not allowed, although negative no data values will result in a foliage height of 0. {{HeatOverlay model attribute nav}}
    590 bytes (83 words) - 14:10, 25 January 2024
  • ...Map and the Data Interoperability extension to prepare and convert the BIM data to another 3D format and then importing this dataset in [[ArcGIS Pro]]. {{editor steps|title=prepare BIM data to import in ArcGIS Pro
    1 KB (208 words) - 15:54, 30 January 2024
  • ...for [[3D Visualization]]s or calculations, there are situations where the data from that file should also be included as other [[Item]]s which are entirel {{howto|title=import a SLPK file for 2D spatial data
    1 KB (244 words) - 15:25, 30 January 2024
  • ...polygons each have an associated [[Terrain Type]], which holds the actual data of what the Terrain polygon represents. Only the [[Terrain Type]] holds any {{main|Elevation model}}
    2 KB (302 words) - 14:32, 29 February 2024
  • ...nes exact heights on the desired reoslution, it is trivial to load in that data. However, sometimes some additional calculations are desired to create or r ...l, by taking the data of the indicated Overlay and adjusting the elevation model accordingly.
    3 KB (418 words) - 14:38, 1 February 2024
  • ...used [[GEO_Data|Geo data]] sets in the project and the by a user imported data. *the number of features in the 3D model (count).
    838 bytes (140 words) - 15:52, 30 January 2024
  • |description=Used for initializing the digital surface model used for this Heat Overlay. ...ues in this prequel grid are clamped between the mentioned min and max. No data values are not allowed. An [[Average Overlay]] can be used to fill in the {
    646 bytes (91 words) - 14:11, 25 January 2024
  • |description=Used for initializing the digital terrain model used for this Heat Overlay. ...ues in this prequel grid are clamped between the mentioned min and max. No data values are not allowed. An [[Average Overlay]] can be used to fill in the {
    643 bytes (91 words) - 14:11, 25 January 2024
  • * [[KNMI Weather data]] * [[How to import KNMI weather data into Microsoft Excel]]
    667 bytes (88 words) - 14:27, 15 March 2024
  • * [[KNMI Weather data]] * [[How to import KNMI weather data into Microsoft Excel]]
    782 bytes (103 words) - 14:42, 15 March 2024
  • * [[KNMI Weather data]] * [[How to import KNMI weather data into Microsoft Excel]]
    720 bytes (90 words) - 14:43, 15 March 2024
  • * [[How to import KNMI weather data into Microsoft Excel]] * [[KNMI Weather data|KNMI Weather data]]
    911 bytes (129 words) - 14:26, 15 March 2024
  • When working with the [[Ground model (Water Overlay)|complete groundwater model]] of the [[Water Overlay]], it is very likely that any initial configuratio ...on ends. To compensate for this, it is possible to prepare the groundwater data by setting up and running a stationary calculation for groundwater, allowin
    4 KB (582 words) - 15:03, 30 January 2024
  • * [[KNMI Weather data]] * [[How to import KNMI weather data into Microsoft Excel]]
    731 bytes (95 words) - 14:41, 15 March 2024
  • |description=Specifies the mode by which bridges are include in the elevation model, used for the water calculations. ...alculations. This setting defines how to include bridges in this elevation model:
    3 KB (398 words) - 10:58, 28 February 2024
  • * No data values are not allowed. *[[Surface model (Water Overlay)]]
    769 bytes (107 words) - 08:47, 26 January 2024
  • ..._to_the_Tygron_Platform|BAG]] building polygon, we look at the [[elevation model|DTM]] (height points every 50cm). ...et a sharp demarcation instead of fuzzy deviations in an inaccurate height model.
    2 KB (369 words) - 14:17, 2 March 2023
  • ===Dynamic traffic model=== ''A dynamic model changes (over time), according to changes made in the [[project]].
    4 KB (609 words) - 13:13, 30 January 2024
  • |Choose the [[Heat_DPRA_Module|DPRA model]] |In step 3.1 choose for the option import foliage areas (start geo data wizard).
    2 KB (349 words) - 15:27, 30 January 2024
  • |Prepare a [[GeoJSON]] file with the desired data for the [[Sewer overflow (Water Overlay)|sewer overflow]]s, most importantl |Select the 'import' option. This will open the [[Geo Data Wizard]].
    2 KB (229 words) - 12:04, 1 March 2024
  • This prequel serves as a replacement for the DTM, which is the elevation model without the [[Building]]s. The [[Water Overlay]] will still add the heights ...e values in this prequel grid are clamped between -10000.0 and 10000.0. No data values are not allowed.
    1 KB (192 words) - 16:48, 5 March 2024
  • ...hing between [[Water (Terrain Attribute)|land and water]], the [[elevation model]] is altered automatically based on the [[Terrain Type]]'s [[Attributes]]. ==Required data==
    4 KB (689 words) - 15:19, 30 January 2024
  • When using this prequel for an [[Average Overlay]], Vector data is not rasterized for that [[Overlay]]. * [[Grid model (Average Overlay)]]
    455 bytes (57 words) - 16:15, 2 February 2024
  • The [[elevation model]] defines the height of the terrain on and in which the hydrology is modele ...with water depths, or [[terrain height brush|manually modify the elevation model]].
    3 KB (519 words) - 16:50, 5 March 2024
  • | demographic= you if you are interested in GIS, BIM, data analysis, 3D visualization, urban planning and architecture | showcases= a 3D city model
    5 KB (790 words) - 09:18, 28 September 2023
  • ...scription=The depth of the ground water level, relative to the [[Elevation model|surface]] ==Default data==
    1 KB (201 words) - 13:53, 23 February 2023
  • ...scription=The depth of the ground water level, relative to the [[Elevation model|surface]] ==Default data==
    1 KB (201 words) - 13:53, 23 February 2023
  • ...ns to visualize 3D data. The Cesium platform follows an open-core business model with open source runtime engines such as CesiumJS. ...ated graphics, and is cross-platform, cross-browser, and tuned for dynamic-data visualization.
    1 KB (189 words) - 11:20, 5 March 2024
  • ...of [[3D Tiles]]. This allows for using the generated [[3D Visualization]] data in other application. | On the API website go to "3D Model Services (3D Tiles)" (api/session/3dtiles.html).
    758 bytes (118 words) - 17:02, 27 February 2024
  • |description=The default value used for a cell when no spatial data overlaps that cell. * [[Attribute model (Average Overlay)]]
    501 bytes (65 words) - 16:13, 2 February 2024
  • .../20-010.html] (last visited 2024-02-07)</ref> is an open standardized data model and exchange format to store digital 3D models of cities and landscapes. It CityJSON is a different exchange format which uses the same underlying data model as CityGML. Both formats can be imported into the {{software}}.
    3 KB (440 words) - 12:12, 7 February 2024
  • ...ing this prequel for an [[Distance Overlay]], Attribute values from vector data are not rasterized. * [[Grid model (Distance Overlay)]]
    571 bytes (69 words) - 15:36, 2 February 2024

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)