Jump to content
RockWare Support Forum

Paul Crossett

Admin
  • Posts

    19
  • Joined

  • Last visited

Paul Crossett's Achievements

Member

Member (2/3)

0

Reputation

  1. Good afternoon Allison, At this time we do not have that option, but I have added it to our wishlist items so that it can hopefully be integrated into RockWorks down the road.
  2. Good morning Mark, We do still have the export options out to Groundwater Vistas as well as other options that you can use. Once you have created your model you can export it out of RockWorks by using the ModOps / Solid / Export tool. The export options include both Groundwater Vistas Matrix or Zone, and with the "Other Formats" option we also have the ability to export out your model to ASCII XYZG, NOeSYS, Slicer Dicer, ESRI Shape Point and netCdf.
  3. Good morning Edward, Could you please send a screenshot of the error message you are getting, as well as the bug report that is generated from this error message to our support email (tech@rockware.com)? I was unable to re-create this error within our samples data set.
  4. Mathieu, At this time we do not have a way to select different data for individual logs within a profile, the only option currently is a one log type for all where you select the data that will be presented for each log in the 2D striplog designer.
  5. Good morning Mathieu, What format is your bathymetric map in? Under the Graphics / Images Tools we do have a few options for Georeferencing an image to bring it into a RockPlot2D window, draping an image using an existing grid file, or floating an image at a specific elevation. Regarding the 2D profiles, are you using the bathymetric map to create a surface grid for your 2D profiles? Once you have brought an image into RockWorks and georeferenced it you can use the Graphics / Images / Digitize tool to digitize the contour lines within the image, and then using Utilities / Create / Grid -> XYZ you can create a grid of your digitized data.
  6. If you have changed your preferences to have the Help Documentation downloaded locally onto your computer, you may receive an Access Error violation when upgrading to RockWorks Revision 2021.2.9. This error occurs as there is an issue with correctly unzipping the updated Help Documentation onto your computer. If you do receive this error message, please follow the steps below to resolve this issue. The best way to correct this problem is to edit your RockWorks System.ini file. To get to this file you will need to go to C:\Users\Your User Name\AppData\Local\RockWare\RockWorks20, and then open the System.ini file in a text editor like Notepad. AppData is a hidden folder, so you can either type it into the file path at the top, or in your File Explorer options check the Hidden Items option. Once you have the System.ini file open in a text editor, you will need to scroll down to the HELP_FROM_INTERNET option and change it from =0 to =1, and then save the file. After you have saved the System.ini file with that change, then please start up RockWorks again and hopefully this should resolve the issue. After RockWorks has started up you can go back into the preferences option and re-select saving the help file locally.
  7. Good morning Doug, We have two links on our RockWorks 2020 help page that I have included below that may answer your question. Stereonet Gridding Options (https://help.rockware.com/rockworks/WebHelp/stereonet_grid.htm) Stereonet Statistical Summary (https://help.rockware.com/rockworks/WebHelp/stereonet_stats.htm) If you have any other questions please let us know!
  8. The issue that was causing this error was that there were boreholes that had dates listed as pre-1900. This is not an issue within RockWorks, but when exporting out to Excel you will receive the OLE error message as Excel's dating options technically do not start until 1/1/1900. Excel will halt the export as it views those dates being exported out pre-1900 as "negative dates." If the dates are updated to show after 1/1/1900 then the export should go through without issues.
  9. Chris, After discussing with one of our developers I believe the issue is the pound sign (#) that you have in your project name. For some reason Google Earth does not like that, but after we removed the pound sign from the project name it exported to Google Earth without any issues.
  10. Good morning Chris, Thank you very much for sending over the backup of your database. I am getting the same red X as you when I try to export your data into Google Earth. We believe the issue may be stemming from google earth itself as it appears to be having some outage issues at this time. I will monitor the issue and try again later today to see if it is corrected.
  11. Good afternoon Laure, Thank you very much for your question regarding bringing in your geophysical data into RockWorks17. What format is your geophysical data in by chance? If it is formatted in X/Y/Z/G data then you should be able to bring it into the datasheet. If you would like to send us your data at tech@rockware.com we would be happy to take a look at it and potentially come up with other options of bringing the data in as well.
  12. Good morning Laure, I have sent you an email regarding this issue.
  13. After receiving the data we are able to discern that there was a difference in coordinate systems from the Utilities datasheet and the project coordinates (UTM meters vs UTM feet). Once that was corrected the contours were projected inside the project dimensions correctly.
  14. Good morning Craig, Would you mind backing up your database and sending it to us at tech@rockware.com? I would like to make sure that I am using the correct coordinate system and grid/model dimensions as well as the same setting you were using as I am working with your .rwDat to see if I can replicate the issue that you are running into. Thanks!
  15. Good morning Mike, The error you are receiving is likely because your data dictionary is corrupted. I would suggest either deleting, or renaming the system folder for that project and that would let RockWorks rebuild the sql database again and see if that resolves the issue. If you receive the error again could you select Report Error / Restart and send the bug report to tech@rockware.com so we could take a look at that as well?
×
×
  • Create New...