Jump to content

Search the Community

Showing results for tags 'qgis'.

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

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 6 results

  1. Hello, I am trying to use the TUFLOW plugin flux plot tool to plot flow from the xmdf's depth layer. I followed the example shown in the TUFLOW wiki: https://wiki.tuflow.com/index.php?title=TUFLOW_Viewer#Plotting_Flow Drawing the flux line works fine, but when I right click to end the line, it either displays zero for the entire time period, or produces the python error copied below. This occurs for a line drawn on both the max depth result and depth at a time. There should be data there, as the PO line shows a hydrograph. I tried this in a blank QGIS map, with projection set and xmdf projection set, and in my working QGIS file. I tried this with multiple xmdf results files. QGIS version: 3.8.2 TUFLOW plugin version: Output is xmdf results every 30 min for 24hrs; other TUFLOW plugin viewing utilities (cross section, timeseries) work well TypeError: 'float' object is not subscriptable Traceback (most recent call last): File "C:/Users/jmital/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\tuflow\tuflowqgis_tuviewer\tuflowqgis_tuflowline.py", line 255, in rightClick self.createMemoryLayer() File "C:/Users/jmital/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\tuflow\tuflowqgis_tuviewer\tuflowqgis_tuflowline.py", line 330, in createMemoryLayer worked = self.tuPlot.tuPlot2D.plotFlowFromMap(None, feat) File "C:/Users/jmital/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\tuflow\tuflowqgis_tuviewer\tuflowqgis_tuplot2d.py", line 602, in plotFlowFromMap velMag = velDataValue[0] TypeError: 'float' object is not subscriptable
  2. We have been asked by several users about QGIS 3.4 and TUFLOW outputs. In QGIS 3.4, we have introduced MDAL so you can read TUFLOW results directly in QGIS without a plugin. For more info see here: https://www.lutraconsulting.co.uk/blog/2018/10/18/mdal/ Crayfish is now much more simplified and is used to generate animations and plots. There will be some more functionalities (grid calculator, conversion of mesh to raster, etc later). To add TUFLOW results: 1- Add 2dm as a Mesh layer 2- Right-click and open Properties 3- From Source tab > Assign Extra Dataset to Mesh 4- Point to your DAT or XMDF files. https://youtu.be/yW-s-umptQQ (not the best quality, but gives you the hints!). Many thanks Lutra
  3. Dear TUFLOW users, We have started a crowd-funding campaign to refactor and port Crayfish to QGIS 3. The current Crayfish will not work in the upcoming QGIS. In addition, we'd like to add support for 3D canvas and loading large files. http://www.lutraconsulting.co.uk/crowdfunding/qgis-crayfish-3/ We will prioritise support of the formats for users who contribute to the crowd-funding. Regards, Lutra Consulting
  4. Recently I've bumped into an issue with Crayfish being unable to load large XMDF result files. When result files exceed some unknown threshold of either number of cells or file size, the Crayfish plugin is unable to load the file. I've spoken to the good people at Lutra Consulting who developed the plugin and while they are aware of the issue, the plugin has taken on a life of its own and they can't continue to maintain and trouble-shoot it for everyone. This got me wondering: 1. Has anyone else come across this issue? If so, what have you found out about the limits and possible solutions / work-arounds? 2. Would there be interest from other users in pulling together a consortium to co-fund support and development of Crayfish into the future? Alternatively, a consortium could be assembled to fund the resolution of this specific issue only. 3. Are there plans for TUFLOW to expand their current QGIS plugin to offer more of the functionality of Crayfish? If not, would there be interest in leading and supporting a consortium? ds.
  5. Q: I have a QGIS query and hopefully you can easily answer it. I know how to do this with my eyes closed in MI, but, I was wondering if you have any tips for: • merging a grid (by grid order) in QGIS (layer stack merge never seems to work), and; • exporting a grid to .flt in QGIS I want to “read grid zpts” the grid(s) so if you don’t have a solution for the layer stack merging I can read them in order if I can export as .flt – I find ASCII’s produced by QGIS don’t behave like those created in MapInfo, do you also find this? A: If you want to merge a grid, I usually use raster>miscellaneous>merge. There is a useful tute here. I normally use this for adjacent grids, where they don’t overlap. If you need to get a bit more in depth then the SAGA tool box is the way to go. This stack exchange post is pretty much what I use. You can use first or last method to make sure that you get the right grid order. Exporting to flt is a bit trickier. QGIS currently does not export these perfectly. You can export as the ESRI BIL file and change the header. Here’s an example. Another option is to export as asci in QGIS then use the TUFLOW utility asc_to_asc to convert it. I usually use TUFLOW to read in the grids in the correct order, then typically work with the resulting DEM_Z.flt file. Sometimes, QGIS can default to the ‘golden surfer’ style of asci, which doesn’t have a fixed cell size. This may be why you’re seeing a difference. The ‘export asci in QGIS’ link above, there’s instructions on how to get around this.
  6. Hi all, I am trying to understand why the degree unit for MGA 56 (and other Transverse Mercator projections) is different between ESRI/Mapinfo and QGIS. After a bit of digging online I haven't had much luck. The below is a copy of the respective prj files. Note the Mapinfo Universal Translator (essentially FME) creates a prj file consistent with ESRI. ESRI/Mapinfo PROJCS["GDA_1994_MGA_Zone_56",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",10000000.0],PARAMETER["Central_Meridian",153.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0]] QGIS PROJCS["GDA94_MGA_zone_56",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GRS_1980",6378137,298.257222101]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",0],PARAMETER["central_meridian",153],PARAMETER["scale_factor",0.9996],PARAMETER["false_easting",500000],PARAMETER["false_northing",10000000],UNIT["Meter",1]] I believe all software packages suggest I am using EPSG 28356. I am concerned that the small difference in units can lead to very slight shifts in large datasets and issues with snapping. If you have experienced these issues or have any thoughts it would be great to hear from you. Kind regards, Mitch. ESRI_MGA56.prj.txt QGIS_MGA56.prj.txt
  • Create New...