Jump to content
RockWare Support Forum


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About dsweetkind

  • Rank

Profile Information

  • Gender
  • Location
    Denver Federal Center Lakewood CO
  • Interests
    USGS 3D subsurface mapping
  1. Guido, If all you want is to visualize your seismic lines along with the borehole data, it will be easier and quicker to spatially georeference a raster image of the seismic line and hang that in Rockworks 3D with your boreholes. Just use the RW Utilities function of hanging a raster image on a vertical panel. You can only hang the raster on a flat panel, so if your seismic line has bends in it, you will have to cit it up into multiple rasters and reference each piece separately. I am assuming your seismic data have been converted to depth sections and they are not time sections on the vertical axis.
  2. I am having trouble filtering a solid lithology model with a single grid. I am replacing G-values above the bounding grid with the null value -1e27. It appears that the solid model gets clipped correctly, but I lose my G-values in the resulting grid-filtered solid. If you look at the attached PDF, you will see that I am setting the color scheme to my lithology colorfill table, as correctly shown in the legend of the diagram, but the solid itself retains just a single G-value (appears to be a G-value of 1). I must be making a simple mistake, but cannot figure out where. Any thoughts/advice appreciated. Lithmodel_gridfiltered_01.pdf
  3. Capn -- You do not need to manually enter the start end endpoints of each profile. Set yourself up with an ascii text file of the profile endpoints and read this file in each time you want to create your sections. Get the endpoint X,Y coordinates from your sections fromgo your GIS. Export as a TXT file. Then, in RW>Striplogs>Multi-Log Sections go to the Section Selection Map tab; on the far right side you will see a data panel into which you can import your txt file to define your section locations. You can use a similar procdure to cut profiles through a DEM or other data and append them to your sections. Search in the Help for XY coordinate tables for help with formatting requirements and use
  4. Thank you -- yes of course that fixed it and was the problem. I even knew this little fact at one point in my life. And you folks have helpfully stated this on the instructions page for Grid / Grids -> Stratigraphic Model Program .... thanks again.
  5. I am trying to create a fairly simple stratigraphic model (4 units) from grids that represent the tops and bottoms of each of the 4 units (superface and subface). This is a basin with 3 basin-filling units, surrounded and underlain by a 4th unit representing older bedrock. I am able to create the "eggcrate" stratigraphic fence from the grids and can create a solid model (see attached PDF of strat fences; 4_layer model_strat fences.pdf). However,when I try to use the grids to create a stratigraphic model, all of the bedrock uplands in the model are hidden (white, not transparent) and the basin-fill units are only partly visible. I give each of the basin-filling units a polygon extent within which the unit elevation is controlled by well data, outside the polygon the unit's elevation = land surface. So, in the areas of bedrock outcrop, all basin-filling units have their strat tops at land surface and thickness = zero, execpt bedrock which extends to model base. I have been careful to filter all grids using high stop/low pass such that grids stack normally without crossing. I am using cutoff values for my units that are 50 m, which is the size of my Z-cell size. In the resultant strat model, when I turn the units on one-by-one, each unit is colored and gridded correctly inside of its unit extent, but outside of that where I have set the unit to land surface, the unit is colored white (not transparent as advertised in the help screen for "Manually Building 3D Stratigraphic Diagrams". See attached PDF of Strat model, 4_layer model_strat model.pdf, bedrock and one basin unit are shown; I did a screen capture while I was rotating the model so that the white grid outlines are visible (this is where the blue unit elevation is at land surface), otherwise the model is white outside blue unit. I am wondering if I am doing something wrong or if this is a Rockworks problem
  6. Joan -- One thing you need to do when doing the raster to ascii export in ArcToolbox is to modify your environment setiings. Hit the "Environments" button at the bottom of the Raster to ASCII dialog. Then go in an specify your exact extents of your grid. Also specify the units on the XY resolution and give your XY resolution a specific number of decimanl places, rather than letting XY resolution default to an integer.
  7. Both versions of RW can handle spatial data. There are a variety of possible workflows that you could use. If you work in ArcGIS, you might start by creating a polygon that corresponds to the boundaries of your Rockworks project. Then all other data can be clipped to this polygon. I personally get a lot of use out of the Global Mapper software, just because I have it. Using Global Mapper, I can import shapefiles and export as DXF, clipping to a defined area in the process. If you have spatial data like a shapefile, you can work within Rockworks -- import shapefile directly into Rockplot 2D and clip the extents there. If you do not have spatial data yet you can create it within Rockplot 2D by importing an image of a map and digitizing lines from the georeferenced image (you will need to know the bounding coordinates of the map area).
  8. There are a couple of ways to do this. In RW15, there is a new option in the Grafix>3D utilities that will create a fault curtain from polylines that represent structure contours on a fault surface. So if you are now using RW15, can create a couple of polyline files that represent contours, you can create a surface that can be used for visualization in R3D. In RW14, I have used the import function in Rockplot 3D to import a DXF of the fault plane. You can specify the elevation at which to import the line; so what I have done is do the DXF import of the same feature several times specifying different elevations, so you end up with a series of lines stacked vertically to represent the fault location.
  9. RESOLUTION OF PROBLEM: Import of .txt file was failing because I had some extraneous points that did NOT correspond to borehole locations. Once I removed these, the txt file imported with no problems into the Section Selection Map window using File --> Import. These extraneous points were section bends that were not located on boreholes -- I want to use these and will try and fool the program by putting these points into my borehole database as dummy wells. Problem is obvious in hindsight: the XY coordinate file I was using to cut irregularly-shaped sections through solid models cannot be automatically used to "cut" a section through the source borehole data, unless the XY data correspond to boreholes. Duh. Also of interest, I had some NAD83 NAD27 issues such that even the points that were intended to correspond to borehole locations did not have XY locations that exactly matched well locations in my borehole database. The program handled this discrepancy just fine and assumed I was wanting to snap to a nearby borehole location. So I import locations that are slightly off and the program loads the XY of my boreholes instead.
  10. I am having trouble importing txt or tab files to create user-defined multi-panel cross section traces. The goal is to import a list of section panel endpoints (from Excel, converted to ASCII via Wordpad or Notepad). I am trying to import, within the hole-to-hole log section>section selection map interface by importing my own .txt file, but my file XY points will not show up in the list. Instead, what comes in is the last profile I digitized by hand on the map view -- my .txt will not overwrite these vertices.
  • Create New...