Jump to content
RockWare Support Forum

All Activity

This stream auto-updates

  1. Last week
  2. Earlier
  3. 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.
  4. In RW20, is it possible to have the horizontal and vertical scales fitted to any ratio that is on an engineer's ruler (e.g., 1:10, 1:20, 1:30, etc.)? Thanks, Allison
  5. Hi Alison Zip file is uploaded. Appreciate technical review. Problem: Importing dxf into xyz points resulted in a 200' shift from actual. Database was state plane NM 3002, converted to utm zone 13N, triangulation contour map viewed in Google, contours not lined up with the mined backwall image. 200' - 250' Shift SW indicated. Thank you Craig
  6. Alison

    Gridded Topo

    Hi Craig, Here is a link to our client upload site: https://www.rockware.com/upload-for-rockware/ You may need to zip up the DXF file to get it to go through. Best Regards, Alison
  7. Appreciated. The dxf file is 33mb. Does Tech have a shared location? Thank you
  8. Alison

    Gridded Topo

    Craig, We'd be happy to take a look. Please send the DXF file over to tech@rockware.com along with information about the coordinate system you using, units, etc. Thanks, Alison
  9. I still show a 200' shift in the data. Can you review the Google KMZ [1.6mg] produced from the original dxf file [33mg]? The backwall contours should line up on the aerial photo in Google. Thank you
  10. Alison

    Gridded Topo

    Also, here is a KMZ file that I find really handy showing all of the State Plane zones. I often plot some Lat/Longs from my project along with this just to confirm that I'm using the correct zone.USA_State_Plane_Zones_NAD83.kml
  11. Alison

    Gridded Topo

    Are you seeing this shift when you export to Google Earth? If so, then yes, I think I would try reassigning the coordinate system in your project through the Coordinates tab. Unless you are working with some coordinates in your project that are in different units or a different coordinate system, I don't think you should need to re-scan your data to re-establish project dimensions.
  12. Good idea and trialed. A better solution was found examaning and adjusting project dimensions. I now have good gridded topo that appears shifted 250 feet east of actual. Since data originates as state plane coordinates, I suspect I need to choose the eastern zone of New Mexico. I have not run into this problem before and will advise results. If you have another suggestion, let me know. Thank you
  13. Vincent, Unfortunately, I am not able to reproduce this problem using our Sample dataset. Could you please contact tech@rockware.com with your menu settings? This might help us diagnose what the problem is. To create an RwMenu file, go to File|Export|I-Text and then click the Settings button in the upper right corner of the menu. Use the Save Current Menu Settings button to save the file. Best Regards, Alison
  14. Hi When exporting I-data (Text) I get following error in RW21 Can someone tell me how to solve this? Thanks in advance. Best regards Vincent Verswijvel
  15. New versions of LogPlot8 (32-bit and 64-bit) were uploaded to the RockWare website today and include the fix for importing excel sheets that contain empty worksheets through the Multi-sheet import process no longer causes a sorting error. This version also has improvements and the path fixed in the help for LAS Importing. You can also refer to the complete LogPlot revision list: https://www.rockware.com/rockworks/revisions/current_logplot_revisions.htm To download this build, use the Help | Check for Updates menu inside LogPlot8. Or visit the LogPlot Free Trial tab (https://www.rockware.com/product/logplot/) where you can download the installation program and install the new build right over the top of the existing program. (DO NOT UNINSTALL first.) Note that you will not be able to use this new build of the program if your maintenance has expired before September 30, 2021. If you would like to renew your maintenance, contact RockWare Sales or visit our Customer Portal (https://www.rockware.com/customer) and either create a new account (new visitors) or log in with your existing account. Katy Duncan RockWare Inc
  16. A new version of RockWorks2021 was uploaded to the RockWare website today, with new features, improvements, and bug fixes. The RockWorks Revision History has a complete list, by date, of all changes in the program. New Features: Users can now extract values from a solid model along the path of a borehole. The "speed buttons" along the left edge of the Playlist tab sheet now display the icons on the left side of the text versus the icons being positioned above the text. This decreases the likelihood that options won't be visible when the height of the Playlist tab sheet is vertically reduced. The borehole label font size that is used when plotting the index maps for profiles, sections, projected sections, and fence diagrams may now be adjusted by selecting the File / Options menu. A new option titled “Include Additional Contacts Defined Within RwDat File” has been added to the “Strat. Rules” tab that is shown within all programs that create stratigraphy models based on borehole data. A new program titled "Resample (Fine-to-Coarse)" has been added to the ModOps / Solid / Math sub-menu. This program is used to convert high-resolution solids to low-resolution solids based on a variety of options as shown below. The Borehole Operations / Lithology / 2D Isopach option now displays two options: Voxel-Based and Grid-Based. The Grid-Based option behaves just like the previous version meaning that it generates surfaces based on the uppermost and lowermost occurrences of the selected lithology and then subtracts the lower from the upper surface to create the isopach grid. The new Voxel-Based option simply adds the heights of all voxels that are equal to the designated lithotype to produce the isopach. This new approach will account for voxels in-between the uppermost and lowermost occurrences that don't equal the selected lithotype (i.e. interbeds). Improvements: The Stratigraphy Picker now has the option to snap stratigraphy to an existing lithology contact. Added the ability to extract values from a Solid Model based on XYZ points stored in a datasheet. Added a program to extract values from a grid based on XY points in a datasheet. Users can now use the Aquifer Pattern Table colors for water symbols in 2D and 3D Striplogs. Water level data can be appended to existing data, like T-Data allows. There is a check box on the block mapping tab for Water Levels to allow the user to make the choice to replace or append the data. File | Export | Stratigraphy, will now export for "All Units" or for a single Stratigraphy Unit/Type. The Lithology / 2D Isopach program no longer fits grids to the uppermost and lowermost contacts and subtracts them to produce an isopach grid. Instead, the program simply adds the heights of all voxels that are equal to the designated lithotype to produce the isopach. An option titled "Clear Output Tabs Whenever "Process Playlist" Button Is Clicked" has been added to the Playlist / Configure pull-down menu. If checked, any open output tabs will be closed before the Playlist processing begins. The result is identical to pressing the "Clear" button before pressing the "Process Playlist" button. The idea is to reduce the clutter left behind by any previous Playlist data processing. The default setting for this new option is "off". File | Export | Stratigraphy/Aquifers, will now export for "All Units" or for a single Stratigraphy Unit/Type. The unit type column was added to the output. The editor for editing a database memo field in the Borehole Manager, like the comments in Lithology, has been more streamlined. There is now an OK and Cancel button on the bottom of the editor to either save back to the database or cancel the changes. The Save button is not shown but if the user wants to write out to a text file they can still choose Save from the menu. Bug Fixes RockWorks no longer starts in the previous project if Select Project on Startup is selected on Preferences menu. The Highest Probability solid modeling algorithm now returns the correct values instead of nulls. The Fence Location dialog now updates the map when selecting locations from an XY Pair table. The Rockplot3D Window will never be opened minimized. The RockPlot2D Export to RockPlot3D now uses the transparency options for both draped and floating diagrams. RockWorks will now allow NULL values for the "Collar Elevation". This change will allow the user to not enter a value for this field. Then when RockWorks looks to use the value for Collar Elevation, if it is NULL at that time, we would use the Elevation value in its place. This gives the user the ability to set the Collar Elevation to 0.0 if they want and for 0.0 to not behave as if the user did not enter a value. If they set one of the other tables to "measure depths from the Collar" and the Collar is NULL, that borehole would use the Elevation value in its place. The update of the field to nullable now also updates SQL Server databases. GeoTIFF Import now honors "No Data" data values, converting them to the assigned grid NULL value. This true for the default "No Data" value of -32768 and when the Geo Key Directory of GDAL_NODATA is set. P-Data | Histogram by Lithology no longer causes an Access Violation error when there is no Lithology and a Lithology Unit is chosen in the LithoTypes table under diagram options. The Peripherals / Color Legend / Title may now be edited if the Title checkbox is checked. The "Average" smoothing method for non-lithology modeling menus will no longer be switched to "Classification" after the Lithology Modeling menu has been used. The Hybrid grid modeling no longer generates an Access Violation error inadvertently introduced during the previous update. The text position for IData, IText, TData, Stratigraphy Text and Lithology Text in 2D Striplogs is now honored. Project Folder | New - Creating a project based a custom coordinate system using an EPSG code no longer adds the "+init" to the parameter string (the +init was invalid). When tilting or warping I-Data, T-Data, etc. models in conjunction with superface or subface model truncation, the program no longer produces strange gaps between the model and the truncation surface. Special thanks to Alison for taking the time to illustrate the problem within a Playlist. It shaved at least a day off the de-bugging. We recommend that Network license users install the RockWare Network License Administrator v. 1.15. Contact support at rockware.com for a link to the latest version. To download this build, use the Help | Updates | Check for Updates menu inside RockWorks20. RockWorks Link, click on free trial tab: https://www.rockware.com/product/rockworks/ where you can download the installation program and install the new build right over the top of the existing program. (DO NOT uninstall first.) Note that you will not be able to use this new build of the program if your maintenance has expired before August 31, 2021. Contact RockWare Sales or visit our Customer Portal (https://www.rockware.com/customer/) if you would like to update your maintenance. Katy Duncan RockWare Inc
  17. Alison

    Gridded Topo

    Craig, The Spatial Filter tools at the top of the window will exclude data from the mapping calculations, but will not limit the extents of the grid. If you have a polygon that defines the extents of the xyz data, then you should turn on the Polygon clipping options during grid creation. Here, you can have the program create a polygon (using the Automatic settings), or reference a polygon file or table. You can set the grid cells outside of the polygon to null, so the contour lines in the map will not extent outside of the dataset area.
  18. Gridded topo model from utilities data, results in spider lines outside dinmensions. Constraining with spatial grid, poly clip does not exclude points outside dimensions. Looking for a suggestion to make checked spatial filter work. Thank you
  19. We recommend that users take a look at this new forum posting before following the instructions above: It appears that the installation of a patch posted on the RockWare website (related to a known bug in RockPack) may also fix this issue.
  20. Users have reported a DLL error running the Safety Factor Calculations in RockPack III on a Windows 10 64-bit computer: Class not registered. You need the following file to be installed on your machine. MSSTDFMT.DLL. This is a DLL which is apparently not installed with newer versions of Windows, and it is required by RockPack III. We have found that one easy solution to this problem is to install the RockPackIII Plane2Beta Patch, which is described on the RockPackIII support page: https://www.rockware.com/product/rockpack-iii/#tab-in8sync_rockware_support The patch was originally designed to resolves some known errors in the PLANE failure calculations when metric units are used. We have found that it also seems to install this missing DLL. If you run into this problem and the installation of the patch does not resolve this, please contact tech@rockware.com.
  21. Craig, I'm sorry you are having this problem. My guess is that this has something to do with your menu setting. Unfortunately, access violations can be hard to diagnose without looking at the data and menu settings. If you are willing to send us your project, we will take a look at it as soon as we can. To do this, you could simply zip up your project folder, removing any files that are not applicable to this problem. You can send this to tech@rockware.com. Best Regards, Alison
  22. ideas to resolve access violation address 4115CF, RW20, read of address 2. Gridding TOPO from datasheet ~1800 lines. Project dimensions scanned from topo data. Probably a simple correction I am overlooking Thank you
  23. Hello Vincent, Please send us the backup of your project database to (tech@rockware.com) - to get the backup please click under the Borehole Manager tab >File >Backup Database and save the zip file to your computer. The file should be small enough to send over. Include with your email the version of RockWorks that you currently running on your computer and the workflow you are seeing the issue with. Thanks for your time. Sincerely, Katy
  24. Hi Alison It doesn't seem to make a difference unfortunately. I'm afraid my project is pretty big and I have no clue what's the best way to send it. Best regards Vincent
  25. Vincent, I suspect that you need to change one of these columns to be hung off of the Collar Elevation datum, rather than the Elevation datum. This would be set at the top of the data table in the Borehole Manager database. If you continue to have problems, please feel free to send us your project (to tech@rockware.com) and we will take a look. Best Regards, Alison
  26. Hi Recently I've updated from RW17 to RW20 and I noticed a fault in all of the borehole operations that display 2D striplogs. The left bar represents the lithology while at the right you can see CPT-data. Lithology is measured from collar elevation and the CPT-data (P-data) is measured from elevation. This is something I inherited from the project in the past. However, both the lithology bar and the CPT-data should start (and end) at the same level. Left: RW20 Right: RW17 In RW17, the lithology bar and the CPT-data coincide perfect as you can see on the right picture. Is there a new setting in RW20 that I missed, or is this a bug? Kind regards Vincent Verswijvel
  1. Load more activity
×
×
  • Create New...