Jump to content
GMS, SMS, and WMS User Forum


  • Posts

  • Joined

Everything posted by khaled_haider

  1. Hello, I encountered a problem when I was trying to download Online Maps because the "Advanced button" is missed from "Get Online Maps" dialoge. I am using GMS 10.4.2. Any suggestions please.
  2. did you try to increase the number of time steps for that stress peroid ? it may help !
  3. I've faced the same problem with the ArcGIS 10.4.1. But it worked perfectly with an old version of ArcGIS, namely the version 10.2.
  4. Hi mina, you can compute the flow in and out of each part using two methods: 1- You can interactively select the cells of each part, and then compute the flow budget only for those selected cells and see the flow values for each part under the “HEAD DEP BOUNDS”. 2- You can define Zone Budget IDs for each part, either directly on the 3D Grid, or using a new coverage in the conceptual model and converting the conceptual model to Grid model. You have then to re-run the model and re-compute the Flow Budget. You can then see the flow budget for each zone,which in this case represents your model parts (instead of all cells).
  5. Hi Mark, first, I recommend you to use the Arc Hydro Groundwater (AHGW) from Aquaveo, which enables you to simply import the simulation results (including Draw down) into ArcGIS. If you don’t want to do that, you can follow the following tedious steps: 1- Go the project explorer- 3D grid data, and select the “top” in Global package to make it the active dataset. 2- Right click on the 3Dgird icon and then export the 3D grid as a shapefile (grid.shp). 3- In the windows of Export 3D Grid to shapefile select the “Active cells” and “Active dataset”, which in your case is the top elevation of the layer. 4- Once again, right click on the 3D grid icon and choose the commend “Convert To 2D Grid” and write 0 as the default Z value for 2D grid. 5- Now go to your MODFLOW Solution and select the DrawDown to be the active dataset. 6- Go to the Menu Bar and Select the “Grid” which is located between “Display” and “MODFLOW”. 7- Choose the commend ‘’3D data -> 2D data”. 8- A window will appear, change the option of “create dataset using”: into “value from k layer”. 9- Be sure to see DrawDown:all near the button 3D Dataset in this window, then click ok. 10- Accept the default dataset name “lay1_DrawDown”. 11- Now you have two dataset under your 2D Grid, you can delete the default, and select the lay1_DrawDown to be the active dataset. 12- Right click on the 2D grid and choose the commend “Convert to 2D Scatter Points”. You can change the name if you want. 13- Now you can choose which time step you want to export to ArcGIS. 14- Right click on the scatter points (which represent the DrawDown as points), and then choose the commend “Export..”, to be saved as type “Shapefile(.shp)”. 15- Now, you have 2 shapefiles. The first one is the Grid as polygons, and the second is the drawdown as points. 16- Import these two files into ArcMap. 17- In the table of content in ArcMap, right click on the Grid, and choose the commend “join and Relates” / join.. 18- In the field of “Choose the filed in this layer that the join will be based on”, choose the field “ID”. 19- In the filed of “ choose the table to join to this layer, or load the table from disk” , choose the drawdown, which is a point-shapefile. 20- In the field of “choose the filed in the table to base the join on” choose the field “NUMBER”. Then click ok. 21- Now you can display the drawdown, by right click on the Grid, then choose the Properties.. then Symbology, then Quantities , then choose the Value to be “Lay1_DrawD”. 22- You can choose the number of classes and the color ramp you want. 23- If you have a large number of cells, you may need to click on the button Classify, then increase the value of Maximum Sample Size, through the button Sampling in the Classification window. You have to increase the value to a number that is larger than the number of the cells in your model. If you don’t increase it, you will notice that not all cells are displayed. I hope this will help you. Khaled
  6. Thank you Alan for your reply I was working with the version MODFLOW-2005. When I switched to MODFLOW 2000 it worked perfectly, as shown in the figure below.
  7. Hi, Does anyone know why my GMS- MODFLOW Solution did not calculate the different type of errors e.g., Sum of Squared Weighted Residual (Head + Flow), as shown in this dialog ?. Thanks.
  8. Hello, did anyone notice that the option "Mark flooded cells" does not work in GMS- Version 10.3.6 ? or there is something wrong with me ?
  9. Dear GMS- development team, I was wondering if you you please could add the following options to the output control dialog: 1-Layer thickness. 2-Saturated thickness. 3-Depth to the water table below land surface. thanks
  10. Hello Niklas Jannok, I do not know how many errors do you get when you run the Model checker, but if the number is not very large, you can manually modify the bottom elevation of the cells that cause the errors. But it is recommended not to change the stream elevations.
  11. Hello, I was wondering if the computations using GMS-DATA CALCULATOR could be limited to only some selected cells of a 2D-Grid data set (and not for all cells of the dataset). Because sometimes I want to change the values of some cells that intersect with specific arcs or polygons and not all cells. thanks
  12. Hello, I was wondering if the computations using GMS-DATA CALCULATOR could be limited to only some selected cells of a 2D-Grid data set (and not for all cells of the dataset). Because sometimes I want to change the values of some cells that intersect with specific arcs or polygons and not all cells. thanks
  13. Thank you Calberts for answering my question. You helped me a lot. I was a little confused with the shortcut of the Unit of Discharge in Cubic meter per second “CMS”. I am used to the abbreviation m3/s.
  14. Hello, Does anyone know the cause or the meaning of this message” Event … is over due to flow below cutoff value” which appears in WMS Model Wrapper?
  15. Thanks Chris, I did not notice any significant change in my results when using a Time step = 300 seconds, except for a significant shortcut in the time necessary to complete the simulation. This encouraged me to try even greater values of time steps (for example 600 seconds) to see how this increase can affect the results. Nevertheless, one must be very careful when implementing this increase and must monitor all types of outputs and not focus on a specific output.
  16. Hello, I was trying to run a long-term simulation (for a period of 10 years) in GSSHA. The Precipitation file and the hydrometrological (HMET) file are relatively large. Because I do not want to wait a lot of time and because my meteorological data are hourly, I have chosen the Time step to be 300 seconds. However, the GSSHA Model Checker gave me an Error Message: The time step must be an integer divisible into 60. According to the GSSHA- User’s Manual (Version 1.43 for WMS 6.1), It is possible to choose Time steps which are multiple of 60 sec. Here is a Citation from 2.2 Time Steps and Process Updates: In GSSHA the user specifies the overall model time step, in seconds, that the model uses to loop through he processes, check update times, and update processes. To avoid missing updates of processes, such as rainfall, that may be specified at 1 minute interals, the overall model time step should be integer divisible into 60 seconds or an integer multiple of 60 s (i.e. 5, 10, 15, 20, 30, 60, 120, 180, 300). The model time step also must not be greater than the finest resolution of inputs, such as rainfall (which in my case is hourly). Typical time steps for GSSHA range from 10 to 300 seconds. Smaller time steps may be required for particularly difficult problems. Thanks.
  17. I'm sorry, my last sentence was not correct . the truth is that small values of porosity result in large values of Velocity vectors magnitude.The equation for calculating ground water velocity is: V= KI/n. (Darcy’s law). V stands for "groundwater velocity," K equals the "horizontal hydraulic conductivity," I is the "horizontal hydraulic gradient," and n is the "effective porosity."
  18. Regarding the porosity in MODFLOW, I have noticed that the values of Velocity vectors_Mag (which is produced using the option CCF-> Velocity vectors) are proportional to porosity. Small values of porosity result in small values of Velocity vectors magnitude.
  19. Sean, I believe you can not change the fonts and icon sizes in 10.3, because it is default depending on your display resolution. GMS 10.3 detects your display resolution and appropriately sizes icon bitmaps and fonts. see this link https://www.aquaveo.com/software/gms-whatsnew
  20. http://forum.aquaveo.com/topic/1734-creating-faults-in-gms/
  21. Junya, if you have several layer and want to define different boundary head for each layer, you can simply use CHD package. You can create new conceptual model with a number of coverages equal to the number of layers. You will define the boundary head for layer one in the first coverage, and the boundary head for layer two in the second coverage, etc… Then you can use layer range –Auto assign Layer (Use layer range) to assign each coverage with its corresponding layer. Finally, you convert the conceptual model (with all applicable coverages) from Map to MODFLOW. I hope, this will help you.
  22. excuse me, the unreadable values on Z-axis occur when the thickness of the layers is small relative to their horizontal extent.
  23. Thank you Michael Kennard for your reply on my requests. I would also like to ask if there is a possibility to address the unreadable values of Z-axis when displaying the Cross Sections, especially when the thickness of the layers is large.
  24. Thank you Sean Czarniecki for guiding me to where I can find the errors related to streambed altitude in MODFLOW output file. I have also noticed that not all versions of MODFLOW write down this information in the output file. For example MODFLOW 2000 and MODFLOW LGR do not record such errors in the output file, while MODFLOW 2005, NWT, and USG write down this information under the section / STREAMBED PROPERTIES AND STREAM DIMENSIONS/ REACHES WITH ALTITUDE ERRORS.
  25. Hello Alan Lemon, Thank you for your reply on my messages and my requests. I would like also to ask if it is possible to add another issue to the Model Checker in order to recognize an error that related to the SFR2 Package. I have noticed that the Model Checker does not compare the streambed-elevation (ELEVUP or ELEVDN) with the cell bottom elevation in a similar way as it works with the River Package (RIV1). This means that even if the elevation of the streambed is below the cell bottom elevation, which may cause many problems in some models, the Model Checker still give the green message that there is “No Errors or Warnings found in model inputs”. In order to clarify this issue, I sent you a very simple example as Attachment. Thanks Model_Chekcer_SFR2_versus_River.rar
  • Create New...