Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jleister

  • Rank

Profile Information

  • Gender
  • Location
  1. Hi David, Apologies for the delayed response to your post. We are aiming for a release by the end of September 2017. I am currently looking to finalise some of the graphing tools and will then do some final testing to make sure everything is behaving. Thanks for your patience. Joel Leister miTools Support and Development
  2. The miTools 2016-05 release is now available. This update fixes a reported bug in the TUFLOW message utility and reinstates access to the Flood Modeller Related Tools (formerly the ISIS Related Tools) through the miTools menu. If you are currently using miTools 2016-03, please update the miTools using the download link below: miTools 2016-05 Download miTools 2016-05 Release Notes Any queries or issues, please don’t hesitate to email miTools@tuflow.com. Best Regards, Joel Leister (miTools Support and Development)
  3. Hi Amy, There was an error in both the 2015 and 2016 releases of the miTools that had prevented the "ISIS Related Tools" menu options appearing in the miTools drop down menu. These tools have subsequently been renamed "Flood Modeller Related Tools" and the error that had prevented them from loading has been fixed. I plan on posting the updated tools onto the website (http://tuflow.com/miTools%20Latest%20Release.aspx) tomorrow, and will post an announcement on this forum once the updated tools are available for download. Cheers, Joel (miTools Support)
  4. An update to the miTools 2016-03 release is now available. This update fixes reported bugs in the ‘Import Check” and “Plot Long Section” utilities. If you are currently using miTools 2016-03, please update the ‘Import Check” and “Plot Long Section” utilities using the download link below: miTools 2016-03 Patch 1 miTools 2016-03 Release Notes Any queries or issues, please don’t hesitate to email miTools@tuflow.com. Best Regards, Joel Leister (miTools Support and Development)
  5. We are pleased to announce the miTools 2016-03 release is now available. This interim release of miTools includes some enhancements and bug fixes to existing tools, a new tool to assist with licence management and provides compatibility with the new TUFLOW 2016-03 time series output format. To download the release and the associated release notes, please use the links below: miTools 2016-03 Download miTools 2016-03 Release Notes miTools Manual (unchanged) The next major release (see Release Notes for details) is scheduled for July/August 2016. Any queries or issues, please don’t hesitate to email miTools@tuflow.com. Best Regards, Joel Leister (miTools Support and Development)
  6. An update on the next miTools release miTools is currently undergoing some final testing ahead of a January 2016 release (timed to coincide with the next release of TUFLOW classic). This release will include: - changes to existing tools to ensure compatibility with new and changed TUFLOW output formats - updates to the licensing to prevent the miTools from 'timing out' as frequently - new tools to assist with the management of miTools within MapInfo - bug fixes to existing tools If you have any questions regarding the upcoming miTools release, want to make suggestions for future tools or report bugs, please contact mitools@tuflow.com Kind Regards, Joel Leister
  7. Hi David, There are plans for an update to the miTools to allow the xmdf format to be used in the TUFLOW_to_GIS mapinfo interface (and it is something that I am currently working on). There will also be some additional changes/enhancements to the interface based on user comments/feedback. The updated version of TUFLOW_to_GIS mapinfo interface will be included in the next miTools release. Cheers, Joel
  8. Hi Paul, BMT WBM is currently developing a tool that will do as you describe and will be included as part of the miTools package in the future. For more information regarding this tool or the miTools in general please contact mitools@tuflow.com Cheers, Joel
  9. Hi Archana, Once you have imported your zpts, you need to use vertical mapper to do a point inspection. This process will assign an elevation to every zpt located within the bounds of any open DEM. Once this has been completed, you need to do one of two things; either update the elevation column with the elevation data from the point inspection (Using Table\Update Column), or change the table structure (Table\Maintenance\Table Structure) to ensure the inspected points are in the fourth column. The heading does not need to be elevation and by leaving the heading as generated by MapInfo will allow you to trace back the data to a particular DEM (good QA!!). To delete unwanted zpts (those assigned a null value, typically -9999), you need to go to Query\Select then select from table (your zpt layer) where the elevation column = -9999. If no points are selected, then there are no zpts with a null value. You do not need to delete these zpts provided that they occur outside you active 2d domain. Hope this helps, Cheers, Joel
  10. Hi Richie, In reference to your first question, the size of the TUFLOW model is only limited by the capabilities of your computer and what you would consider an acceptable run time. Under the 'software/hardware' section of this forum there are a number of posts that discuss extremely large TUFLOW models and the limits of these models in terms of your computer's RAM. As your model is reading zpts, then your computer has been able to allocate the required memory to your model. The 99,999 value for the zpts would indicate that they have not be initialised, ie: had there value changed from the default zpt value in the empty zpt file. Some possible checks that you may want to try include: - checking that you have set an active code polygon over the entire model area; - check that the attribute containing the elevation data is in the column that TUFLOW is looking for it; - check that the polygons you are using cover all the zpts (normally you would Read MID Zpts or Read TIN Zpts to set the base topography and read in polygons to modify the topography as required - eg: fill platforms, etc); - if you have multiple lines defining the topography, you can write zpt files after each to determine if the topography is being modified as you expect. If you are still having problems with TUFLOW defining the zpts on the large grid, it may be helpful to attach your tgc file to a post in this topic. Users on the forum would then be able to help you troubleshoot any issues that may be evident. If you decide to split the model up into multiple models, you would need to ensure there is enough overlap to prevent boundary effects from either the downstream or upstream boundary affecting you results. You would also need to make some assumptions on the downstream boundary to apply to the individual models and do some sensitivity tests to ensure that the results upstream are not be influences by your choice of downstream boundary. Hope this helps, Cheers, Joel
  11. jleister

    miGIS tool

    Hi Amul, To install the gis tools, you should follow the instructions contained within the document that is included as part of the zip file that you have downloaded from the TUFLOW website. Your dongle may be valid for TUFLOW, however, unless you have paid for the gis tools utilities, your dongle will not recognise the miTools.mbx and therefore it will not run. If you have paid for the gis tools, I suggest that you contact gis_tools@wbmpl.com.au with your dongle number so that it can be checked out. If you have not paid for the tools, but want to get a quote (the cost is dependant upon the type and number of TUFLOW dongles you have), contact gis_tools@wbmpl.com.au Cheers, Joel
  12. Hi Richie, The extract you have included doesn't look like it is M11 processed data. It has been a while since I have used M11 processed data to define cross sections, however, the processed data used to contain information about the level, cross sections area, hydraulic radius, width and resistance factor for each section. It is these columns that TUFLOW uses to define the section. I would initially check to make sure that you have exported the processed data. (File/Export All Sections/Export Processed Data). Processed data should look like: LICS_300604 Werribee 10016.000 COORDINATES 0 FLOW DIRECTION 0 PROCESSED DATA Level Cross sec Hydraulic Width Add. fl. Resist. (m) area (m2) radius (m) (m) areas (m2) factor 96.480 0.000 0.000 0.000 0.000 1.000 97.050 2.367 0.306 7.640 0.000 1.000 97.620 7.775 0.689 10.819 0.000 1.000 98.190 14.279 1.109 11.632 0.000 1.000 98.760 21.008 1.491 11.978 0.000 1.000 99.330 28.286 1.660 14.471 0.000 1.000 99.900 37.842 1.689 19.691 0.000 1.000 100.470 50.807 1.836 24.801 0.000 1.000 101.040 65.858 2.118 28.008 0.000 1.000 101.610 82.737 2.396 31.216 0.000 1.000 102.180 101.444 2.673 34.424 0.000 1.000 102.750 121.980 2.948 37.631 0.000 1.000 103.320 145.193 3.133 42.366 0.000 1.000 103.890 170.092 3.455 45.000 0.000 1.000 104.460 196.493 3.771 47.634 0.000 1.000 105.030 224.397 4.056 50.620 0.000 1.000 105.600 263.579 3.220 77.071 0.000 1.000 106.170 308.657 3.587 81.100 0.000 1.000 106.740 356.032 3.946 85.128 0.000 1.000 107.310 405.198 4.383 87.250 0.000 1.000 Hope this helps. Cheers, Joel
  • Create New...