Jump to content
GMS, SMS, and WMS User Forum

C. Moebus

  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by C. Moebus

  1. Have you tried the LMG-solver instead? The PCGN-solver did not convince me mostly..
  2. The slow link in the model execution is most probably that you are not using a parallel version of MODFLOW (Check option in MODFLOW Global/Basic Package) or a not parallelised solver (LMG or PCGN). 2 x 12 processors = 24 processors - makes a max. of 4% usage per core if not parallelised...
  3. I will be a very helpful feature enhancement when using the DRT-Package to be able to select the Return-Points, Return-Arcs or Return-Polygons in the Map Coverage. At the moment one has to do that Cell based in the Modflow Menu and repeat this again everytime something is changed and mapped at the DRT-Coverage
  4. One major feature of MOFLOW-USG - besides the horizontal local refinement - is the possibility of being able to split cells vertically instead of splitting complete layers. At the moment, you can only split complete layers vertically, but it will be very helpful, being able to split only selected cells vertically, no matter in which layer you are. Being able to create a conceptual model, where you can create such a model (e. g. vertical and/or horizontal refinement around a well, vertical and/or horizontal refinement along selected boundaries like rivers etc.) automatically will be very helpful, also.
  5. This will be a helpful feature, as this is sometimes the case at our site also. Also to be able to generate Map polygons from other model features, like conductivity, recharge, etc. and to be able to create river, stream boundaries etc. from the model data in the Map coverages will be helpful.
  6. I am missing it also. It is unfortunately due to cost cuts of Aquaveo. Being able, to add own WMS-services with an adapted advanced button was still very helpful!!!
  7. Any updates on the Integration of that feature request?
  8. Yes, this is a bug, that exists unfortuantely since 10.3.6 !
  9. This is a good idea and support this feature request - it will be helpful!
  10. This will be very helpful - I have required this also quite a lot of times...I hope it comes soon
  11. GMS could report the cell id or cell IJK value where the particle was created in the pathline report instead - this will be an even more standardized approach
  12. The newly released MT3D-USGS integrate a lot of very helpful features for solvant transport and therefor it will be great, when it can be integrated into GMS quite quickly... See: http://water.usgs.gov/ogw/mt3d-usgs/
  13. As 3.5 years have past, can you give an update on the integration of this "overdue enhancement"
  14. Is there a plan to get the Database Access (Access-Database, MS SQLServer Database, PostgreSQL database .... - Import and Export!) back into GMS for both 64bit and 32bit-Versions in principle and if yes, when? :-)
  15. Sometimes we work with SRTM data as DEM for regional Groundwater models and these Datasets are very large (converting them to Scatter Points creates 36,000,000 points each). As these SRTM data have sometimes errors, we have to change some Z-values, delete points and add other points or calculate the z-values. All this is only possible with scatter data and not with raster.
  16. In my mind, it will be very helpful, to get the old Arc/Info Grid (*.asc Data) Import function of GMS 6 back into GMS 10.x as it was very helpful with using the SRTM-Data as DEM. As these are datsets with a lot of data, converting them to Scatterdata for use in GMS (e. g. calculations) is not possible, as it creates millions of data points that are not easy to use. With the old 6.0 import functions you could choose the region you wanted and therefor reduced the imported scatter point a lot!!!
  17. Yes, sorry that ("Direction arrows") was what I meant
  18. It will be an helpful option to add the possibility of converting Pathline Timemarkers to XYZ+F(Time)-Points and then be able to Export the Points to a Shape File (or alternatively to me able to Export the timemarkers directly to a shape file). At the moment it can be quite tedious to create good drawings for the timemarkers especially in different scales with the dxf-export option
  19. It will be a great enhancement, if GMS adds an Interface to TOUGH2 / TOUGH2-MP especially with the MVOC Options (= TOUGH2 TMVOC and/or TMVOC-MP). This will add a possibility to simulate 3D multi-phase flow what is sometimes needed (Transport of non--mixing DNAPL, LNAPL etc.).
  20. In my mind, It will be helpful to add some more shortcuts to GMS: Unselect all - e. g. "STRG+U"Rename - "F2" (for all objects that can be re-named like particle sets, coverages, conceptual models, etc.)Plan View for looking down - "STRG+D"...
  21. Hi Alan, I had some XMDF-error Messages like that when I re-opened a GMS 9.1/9.2 Project with GMS 9.0 or GMS 8.3.
  22. Hi Alan, no, the severe performance Problems ("Assiging Grid Node elevations" bug) started wih GMS 9.1 and still exists in GMS 9.2. I just had look in my sent emails to the Support Team - the first time I reported this bug was the 06/20/2013 - so it is more than 5 monhs ago... As nothing happened / changed in GMS 9.1 (+9.2) I reported it again the 11/27/2013. In our mind, the GMS 9.x series has principal performance Problems (that I also already reported to the Support Team together with some sample files) compared to GMS 8.3. One reason for that, we found out on our own - you must use a projection for all your GIS objects - especially images - otherwise every graphic Action gets extremely slow. When opening a steady-state model (already reported) I can see the display "Reading MODFLOW computed values for observations" for 1.5 Minutes now, this normally took some seconds for a steady state model. On top (also already reported) in GMS 9.2 editing values in the MODLFOW cell properties dialogue takes Ages now, when you leave with OK.
  23. Let it run and wait...either it will come back again or GMS will Crash - as it does at my PC- and try to send a bugtrap report
  24. We have the same problems here with GMS 9.0, 9.1 and 9.2 and it is getting even worse from GMS version to version! At the moment it comes to the point where GMS 9.1 and 9.2 crash all the time when mapping to MODFLOW so these a bit more complex GMS Projects are not usable anymore in GMS 9.x...perfect...
  • Create New...