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

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