Jump to content
RockWare Support Forum


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Brianna

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    Golden, CO
  • Interests
    Geology, Geochemistry, Programming

Recent Profile Visitors

364 profile views
  1. Recovery Interval

    Hi Abby, I'm not exactly sure what it is you're looking to do. Could you draw out what you want to do and send it to support@rockware.com Then I'll be able to come up with some suggestions if it's possible to do.
  2. Rock Slope Analysis

    You can plot up stereonets and a variety of maps showing strucutral data, but we do not have anything pertaining to safety factors and failure prediction. Here are the options in the "Planes" category.
  3. Import for Single Text File Not Working

    The Single table import was broken since the last build because of some internal changes to the program. We have a fix and we should be releasing this fixed version later today. Sorry for any inconvenience.
  4. RP2D I-Data text not showing up in x-section

    Jeremy, I can help you out with this if you send your project data to support@rockware.com. Without seeing what's happening it is hard to say specifically what the issue is. Cheers, Brian
  5. Selecting a font in the Keyword Editor

    Chris, Unfortunately in LogPlot7 this is not possible. Look for this feature in the next version of LogPlot coming soon.
  6. import excel data

    You can assign the vertical units to meters or feet when you create your project. You may not have switched that to feet when you created the project. You can reassign the units from the Settings/Coordinates/Reassign coordinate system and/or units without changing actual data
  7. Cross Section legend item text size

    Josh, The legend text is directly proportional to the size of the legend itself so by making the legend larger the text will get larger. Otherwise there is no direct way to change the size. Another indirect way would be to change the other dimensions in the legend to make more space for the text... so change the margins or the cell width.
  8. import excel data

    Craig, All boreholes that are input to the borehole manager need to have at least the following data fields: Easting Northing Z Elevation Collar Elevation Total Depth The Z elevation is the ground surface elevation. The collar elevation is an alternative elevation, typically above or below the ground surface, that might be used as a measuring point for water levels. If you don't have this information, you can use the Z Elevation. If you are having trouble importing from Excel, you can paste your values into the Utilities data sheet and transfer the values to the borehole manager using the File -> transfer -> Locations->Borehole Manager function Be sure to assign units to the column headers before transferring.
  9. hole to hole sections

    Craig, Check to see if your project dimensions are set properly so that your boreholes are within the project bounds. Generally, if the project dimensions are outside the borehole locations, it may appear that your boreholes are not showing up.
  10. Josh, Unfortunately we don't have any 3D clipping tools. What I would suggest is using either ARC 3D or AutoCad to clip it prior to importing it. I'm going to put this feature on the list for the developers for a future version.
  11. Importing large XYZ Dataset

    Josch, The method you are using to produce your grid surface will dictate how long it will take. More complex calculations will add time. When I generated a map from your data I used triangulation because it was a large set. I just ran Easy Map (which uses triangulation) and it took about 4 minutes. You can certainly do what you are wanting to do but you will need to think about your resolution of the model. A model space that is 200km2 is vary large. It's certainly fine, it's all about scaling. If you want to use your 50m DEM you would need to make your model in 50m spacing and that would be much too large. Depending on the spacing of your boreholes, I would consider a smaller number like 500m grid spacing. I say to go this large because it's a good way to make a faster model that you can get a sense of what's happening before you go into the detailed and more time consuming models at smaller increments. Use the Borehole manager for storing all of your data except for the grids. It's much more powerful than using the DataSheet. The datasheet has many uses, but the borehole manager will allow you do do things much more efficiently. There is a very 'loose' connection between the BH Manager and the DataSheet. The DataSheet doesn't save to the BH manager except for Stratigraphy and Locations ad those are manual commands. You will typically go back to do things in the Utilities but the Borehole manager is where you want to store all the XYZ data for your boreholes. Tips on your DEM: you can use the 50M DEM for cross sections and profiles for the surface, but for doing anything that involves grid math, the surface grid needs to be exactly the same size and dimensions as your model. So if you were going to make a 500m model, make a 500m spacing DEM. While you're at it, make some other resampled ones, maybe at 250, 200, and 100. You can use those later on when you refine your model. Brian
  12. Importing large XYZ Dataset

    This is a pretty large data set so you will want to load the file to make the grid instead of using the data sheet. I would stay away from using Local Coordinates, The maps you make here are small scale and UTM is much better for that. Here's what I did to make a map from your data: Be sure you make your project in UTM zone 32 (I used x/y and z meters) load your data to the datasheet convert the Lat/lon to UTM zone 32 You can scan the datasheet to get your model dimensions at this point based on the UTM export the data to a text file Load the text file using Map-> Gridbased map-> based on xyz Because you have such a huge data set I used triangulation and got a good result
  13. Onlap not working in 3D model

    It seems that the issue was coming from data issues. I think you have it worked out now.
  14. Josh, It turns out that the "Replace Nulls" was causing your issue. Turn that off and you should be good. We will work on a fix for that in an upcoming version. Brian
  15. Importing large XYZ Dataset

    Schelhorn, I took a look at your file and I noticed a few things. First question I have is if you are importing this into the database or into the Utilities data sheet? Your data is in this format: "d"; "xcoord_UTM[degree]"; "ycoord_UTM[degree]"; "elevation[m] "1";1.2345 ; 23.4567 ; 123 Your data is mixed with quoted text and float values. Ideally, you don't need to have quotes in your text. Having the quotes may cause issues if you want to import the data into the database. Cleaning this data up ahead of time is a good idea if you can. There's no need for quotes in the header or the names. When you are importing the text into the datasheet, be sure to select the delimiter (the second option) as a semi-colon ( . I suspect that one of these things is what was causing the import to hang up because I didn't have any problem importing the data. Be sure to use decluster when you make your maps because this could help keep it from hanging up. I opened the file in Notepad and Excel and only found 1000 data points, so you must have lost some data when you exported it. On a side note, your data are in Latitude/Longitude and not in UTM. Please be careful with using multiple coordinate systems and try to be consistent whenever possible.