Jump to content

Search the Community

Showing results for tags 'tuflow_to_gis'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • About This Forum and Announcements
    • How to Use This Forum
    • Forum Feedback
    • Announcements
  • TUFLOW Modelling
    • 1D/2D Linking
    • 1D Domains
    • 2D/2D Linking
    • 2D/2D Nesting
    • 2D Domains
    • Boundaries
    • Documentation & Tutorial Model
    • Dongles/Licensing/Installation
    • Ideas / Suggestions / New Features
    • Mass Balance/Mass Error
    • MATH Errors & Simulation Failure
    • Restart Files
    • Post-Processing
    • Software/Hardware Requirements
    • Text Files (.tcf, .tgc, .tbc, .ecf)
    • Utilities
    • Miscellaneous
  • Other Software
    • MapInfo/Vertical Mapper
    • miTools
    • Other GIS/CAD
    • SMS
    • XP-SWMM2D
    • UltraEdit/Excel
    • TUFLOW Apps


  • TUFLOW Calendar

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 6 results

  1. Question: Why can I see decimal values in my hazard results? How should these values be categorised? Answer: The hazard results in TUFLOW will be output as integer values in the .xmdf and .dat files at the cell corners. However, when exporting to grid (in either .flt, asc or .nc format), the raster output is north south aligned and a regular grid (but your TUFLOW model may be rotated, may have 1D triangles and may have multiple domains). Therefore, the TUFLOW results are interpolated onto a north-south grid when directly writing grids from TUFLOW or when using the TUFLOW_to_GIS utility. Since TUFLOW build 2013-12-AD when directly writing a gridded output (e.g. .asc, .flt, .nc) the hazard outputs (except for z0, which is the velocity - depth product) are always output as an integer value, i.e. you only get a value 1,2,3 or 4 when directly writing hazard output to .asc . This is done in by rounding to the nearest integer, e.g. when interpolating a hazard value of 3.05 this is output as 3.0. If using an older version of TUFLOW, or using TUFLOW_to_GIS to post process, this can result in decimal values in the .flt or.asc grids between the desired integer values for hazard classification. To be consistent with how the latest TUFLOW Build is categorising floating point decimal values to integers when it directly outputs hazard grids (described above), the approach would be to categorise to the nearest integer value, e.g. 1.500-2.499 as 2 etc. If you did wish to reclassify 1.001-2.000 as 2 etc, this would provide a conservatively high hazard classification for decimal values, as you would be counting anything greater than the absolute integer in the next band.
  2. Q: When trying to run a batch file to convert a maximum water level from .dat format into .asc format I get an unexpected error. The batch file line is: C:\TUFLOW\Utilities\w64\TUFLOW_to_GIS_w64.exe -asc -b -t99999 M01_5m_1%AEP_001_h.dat A: This is most likely that the percentage character is treated as a special character in a batch file. For a description on this, please see the Microsoft site here: https://support.microsoft.com/en-us/kb/75634 In general I would tend to avoid special characters such as % in filenames where possible, for example there is a list here: http://www.mtu.edu/umc/services/web/cms/characters-avoid/ Whilst the % characters should generally fine in TUFLOW, are supported by Microsoft, however, they may require additional effort in batch files, e.g. may need to be wrapped in quotes (“) or have escape characters ignored. Another thing to note is that TUFLOW can directly write the outputs to .asc grid. You can output multiple file formats from TUFLOW and can set the data types, output interval etc based on the output format. For example in the below, the model will output dat and asc formats with only the maximums for the asc. Map Output Format == dat asc Map Output Data Types == h V q d Map Output Interval == 300 ASC Map Output Interval == 0 !only maximums for asc format ASC Map Output Data Types == h V d Z0
  3. Q: I've got substantial differences between my time series and plot output data and the max grids. Why is this? A: There are a few things that could be going on here, depending on the differences that you’re seeing. BIG differences (>0.1m) The max WSL level is a tracked maximum, which means that at every time step Tuflow checks the current water level at the ZC and saves it if it’s a maximum for the model run. This is then effectively a max output calculated for every time step. Compare that to the TS output which is only at your time series output interval. Similarly, a WaterRide output is an envelope of the maximum grids at every output time, not of every cell at every time step. If you’re seeing a big difference in the gridded results and the TS results, it could be that the temporal resolution in WaterRide and your TS layer maybe missing a point of instability. Investigate the mass balance at that location to see if it spikes, also try seriously reducing the time series output interval (down to something close to your timestep if possible) to see if the TS can produce the same results as the grids. Small differences There are two mechanisms used to create ascii files that can influence the difference between grid and PO. The first one is the extrapolation from the cell centers to the cell corners. Tuflow calculates the water surface level at the ZC then when you grid results using Tuflow_to_GIS. It extrapolates out to the ZH’s on the cell edges and doesn’t preserve the ZC values. This is why you get a mapped grid cell size half of your modelled grid cell size This isn’t normally an issue except where you have really steep topography or incised channels. What you can do to help this is output the ascii files within Tuflow. When you write them from within Tuflow, you get the ZC values, IE, no extrapolation. This can help reduce the difference. (You could also use HIGH RES for an output option. This means that you will get output at cell centers, mid-sides and corners, but be aware that you output size will be about 4 times the size and some programs (such as TUFLOW to GIS and dat_to_dat) don’t yet recognise this format.) The second one is the north/south orientation of the ascii grid. Ascii grids are always north/south orientated. That is, the ascii cells do not line up with your modelled orientation. Thus, there is an interpolation to rotate the grids. This can also cause issues on steep topography where there are large changes in water level or ground level. Unfortunately, there is nothing you can do to fix this one. You can look at the tuflow .dat files for raw results and confirm to yourself that the modelled results are hitting the mark and that only the presentation of results is different.
  4. An updated version of the TUFLOW_to_GIS utility has been released. This is available on the TUFLOW downloads page: http://www.tuflow.co... Utilities.aspx Both 32 bit and 64 bit versions of the utility are available in the respective "w32" and "w64" folders. The changes to the utility are: Precision for output grid is determined from the max / min values in output (see http://www.tuflow.com/forum/index.php?showtopic=1279) Fix when output velocity to asc format (see: http://www.tuflow.com/forum/index.php?showtopic=1299#entry3432) Fix bug which ignored -out filename in some circumatsances Long profiles outputs now correctly assign the .csv extension type Added support for cell-centred .dat results, these are produced only by TUFLOW-FV. At this stage the only supported option is to export to regions in either -mif or -shp format. An example is TUFLOW_to_GIS_w64.exe -mif -region -t<timestep> cell_centred_results.dat Any issues, queries or feedback please contact support@tuflow.com. Regards Phillip
  5. Q: I have used the res_to_res utility to extract the maximum stream power from a simulation. I have used TUFLOW_to_GIS to export the maximum stream power to an ascii grid (.asc). However, when i import this to ArcMap some of the data is skewed. The depth and water level grids open without issue. A: We got hold of the stream power grids, which open correctly in MapInfo, but do not in ArcMap. After some investigation the following was determined to be the cause: The ascii grid is a space delimited file, in the stream power grids there were some high values. These values are "10000.000". In the .asc grid this looks like: 1374.2073 3335.155510000.000010000.0000 9174.210910000.000010000.000010000.000010000.000010000.0000 5478.9277 2581.2310 533.0659 13.5509 Using the default .asc output format, there is no separator (space) between the values (e.g. 10000.000010000.0000). This is causing the two numbers to be treated as a single number when imported to Arc, which results in the data being skewed. This is causing the issue when importing to Arc (but MapInfo seems to handle it). In order to get around the issue there are two options: Use a text editor to search and replace “10000.0000” with “ 10000.00 “. This should fix the issue for the grids already created. You can also specify the output format when using TUFLOW_to_GIS utility by using the "-prec" option. Recreating the grids using a precision will resolve the issue. -prec<u>.<d> sets the output precision for -asc and -mif options. Eg: -prec12.3 would output 12 characters (or 11 if the number is negative) with 3 numbers following the decimal place. Your batch file should like like: tuflow_to_gis.exe -asc -t111111 -prec12.3 <filename> However, these stream powers seem quite high. These can occur as the depth goes to zero. Bed Shear Stress (BSS) and Stream Power (SP) map output can be misleading at very shallow depths as the BSS formula divides by the depth. For the 2012-05 release of TUFLOW the BSS and SP outputs are linearly reduced to zero once the depth is below a threshold (by default, 0.1m). To change this threshold, use “BSS Cutoff Depth == <BSS_cutoff_depth>” in the .tcf file. Regards TUFLOW Support Team
  6. An updated version of the TUFLOW_to_GIS utility has been released. This is available on the TUFLOW downloads page: http://www.tuflow.com/Tuflow%20Utilities.aspx Both 32 bit and 64 bit versions of the utility are available in the respective "w32" and "w64" folders. The changes to the utility are: The ability to output multiple timesteps and data types from and XMDF file. Options include: -Folder”xmdf folder” Example: -Folder”Maximums” will output all of the "maximum" datasets in the .xmdf file. -s<scalar dataset ID> Example: -s1 will convert the 1st scalar dataset. -v<vector dataset ID> Example: -v2 will convert the 2nd vector dataset -TypeAll This will convert all xmdf datasets -tAll Will convert all timesteps Note -TypeAll –tAll will convert ALL timesteps for all datasets the in file, this may fill your hard drive up quickly! The utility now supports high resolution results (results stored at 9 locations around the cell instead of the cell corners). These have been run with the .tcf command: Map Output Format == SMS High Res When outputting results to points (.mif or .shp) you can now filter based on the Zpt type. E.g. -ptsC, will output results only at the cell centres (ZC locations). The defaults is for all points to be outputted i.e. –ptsCUVHT. T is used to define the 1D WLL for triangle points. New output option -region (to be used in conjection with either -mif or -shp). This will output a GIS layer containing the TUFLOW cells as region objects, the value assigned to the region is the value at the cell centre. This output is only valid for high resolution results. Any issues, queries or feedback please contact support@tuflow.com. Regards Phillip P.S. As a teaser for the 2013 TUFLOW release, a lot of the TUFLOW_to_GIS functionality has now been embedded directly in TUFLOW.
  • Create New...