Jump to content
GMS, SMS, and WMS User Forum


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About KMM

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Thank you, This worked great for me, however TUFLOW recently released a new Tuflow_to_GIS.exe program that efficiently converts .dat .h5 and .xmdf files to ESRI compatible ascii files. It works much quicker than the grid to scatter to point to XY to interpolate map pathway. -KM
  2. Hi, Thank you for the suggestion. The process worked, I was able to create the scatter grid and save the x,y,depth file. It imported fine into ArcMap and from here I can build a raster. Unfortunately, the process is very slow (the file contained 869,176 pts), and I have *many* grids to convert. If you come accross a more efficient .ascii based method please share. Thank you, Kimberly
  3. Hi, I am working in SMS 10.1.11 with .2dm TUFLOW depth maps and I would like to export the .2dm depth quadrilateral mesh files to a format that I may import to an ESRI ArcGIS Grid format. The options for importing to an ESRI grid are binary and ascii formats (with header records). However, the header records expectd by ESRI are different than the exported versions (e.g. generic ascii file) I created using SMS | Export option. TUFLOW_to_GIS.exe program: I tried this program but received the following error message: "Did not find ""MESH2D"" in first 6 characters of first line Found: eHDF No geo-referencing information - This is probably an RMA2 2DM Mesh!!" Can you offer any advice for exporting the TUFLOW results to ArcMap? Thanks,
  4. Hi, I am modelling a very large floodplain area 30,000 acres using 10m cell TUFLOW grid. I am having a hard time setting my flow boundary conditions and need some advice for my input data. Over a single flood event my flow will rise from 90 cms up to 4,000 cms over a two-three week period. I only have mean daily data leading up the the event and a peak value for the flood crest. It is unreasonable to model the full real-time two week period, and I am trying to establish an arbitrary timescale for my BC hydro data and model controls. I am using time vs flow for my upstream boundaries and water surface elevation vs flow for my downstream boundaries. I have tried treating each mean daily value as a half an hour. For an event that spans 28 days, there are 14 hrs in the time series, with the map output interval to 1800 seconds, and the start time to 0, end time to 15.0 hrs. I am using a time step of 2.0. The model runs for about 8 hrs cpu time and upon completion, only a quarter of the floodplain is flooded. The flood is drastically underestimated by the TUFLOW model. I am quite sure it is an issue with my BC parameters and model control specifications. Are there rules for relating the time series inflow to the size of the event if you can not model real-time data? I do not mind the long run times, I just wish I could figure out an appropriate time period to let the model respond to the in flow. My terrain and bathymetry data is very good, so it is not a problem and my manning's n are specified correctly. Also the Mass Error % in the log file is always less than 1%. So my model is running fine, I just need help calibrating my inflows, and specifications in the model control interface. Please advise. Many Thanks, Kimberly