d.campbell13

Members
  • Content count

    34
  • Joined

  • Last visited

Community Reputation

0 Neutral

About d.campbell13

  • Rank
    Advanced Member
  • Birthday
  1. I have a series of well locations defined by Latitude, Longitude, Easting metres and Northing metres values. These are based on WGS84/NAD83 UTM Zone 13 and I wanted to convert to State Plane Coordinates. Before I started I converted a single location from UTM to SPC using Global Mapper for comparison. I then converted the UTM locations to the State Plane Coordinate System (SPC Zone 3003 New Mexico West) with eastings and northings in US feet using both the RW17 Single Point Conversion tool and the RW17 Multiple Point tool. In both cases the results were incorrect, irrespective of whether I based the conversion on the Latitude/Longitude values or the Easting/Northing values. As a cross check I converted the "Correct" SPC coordinates to UTM using the RW17 conversion tools and was able to generate the correct answer. Have I done something wrong? Try converting the location below. Regards, David Campbell NAD83/UTM Zone 13 Longitude: -107.908842 Latitude: 36.309413 Easting: 238827.1146 Northing: 4022195.485 "CORRECT" Global Mapper US State Plane 83/ Datum NAD 83/ New Mexico West 3003 Longitude: -107.908842 Latitude: 36.309413 Easting: 2700844.73 usft Northing: 1931935.00 usft
  2. AArghhh. Thank you for spotting my dumb mistake. Regards, David Campbell
  3. Tom: database backup has been uploaded to http://rockware.com/upload/. Regards, David Campbell
  4. Tom: I have specified both monochromatic and gradational infill, with the same results. Regards, David Campbell
  5. I am trying to make a strip log section for a number of wells. Each well contains four columns showing p-data curves. The problem is that I can only get two out of four curves filled. The remaining two curves only show plot lines, no fill. I have tried reducing the number of columns to three - one column is plot line only. I have tried reducing the number of wells to one - same problem. What am I doing wrong? Regards, David Campbell
  6. When I used the 2D Striplog profile option I was able to see each of the deviated wells but...they were displayed with the deviation! I would like to display the deviated wells on a cross section as individual vertical striplogs (i.e. on a TVD scale) - like your first cross section above rather than the second. Any other ideas? Regards, David
  7. Thanks for the tip Tom. It works well. Regards, David Campbell
  8. I would like to male a strip log section of several deviated wells that originate from the same surface/ collar location. The purpose is to correlate reservoir units and structural elevations. I can make a 3D strip log but I would prefer a simple 2D strip log with each well shown with an arbitrary separation from the next. When I try to select wells by collar location on the 2D Strip log Section Selection Map I can only select one of the three wells. Any ideas on how I can get over this without changing the surface locations? Regards, David Campbell
  9. I wondered if anyone had attempted to classify and transform P-data into colours? I have looked for a method or an easy workaround and have failed, so would be grateful for advice. Why would I want to do this? Take a look at these web pages:​ http://www.kgs.ku.edu/stratigraphic/PROFILE/HELP/colorlith/index.html http://www.cwls.org/wp-content/uploads/2014/08/insite_2005_12.pdf (Article by Hall) I have looked at a number of options in RW16/17 and have come across some apparently limiting factors: 1. You are able to covert P-Data-> Lithology by first constructing a lithology predictor from two P-data logs provided you know what the original lithologies are; then you can apply the predictor to other wells containing the same P-data types. Obviously this doesn't help if you just want to classify data combinations or have a lithology predicted by more than two P-data types. 2. Colours in RW16/17 are not specified directly as RGB although there is a facility to convert individual colours to Munsell. 3. You can perform a number of arithmetic operations on P-data in columns (make ratios etc ) which is helpful but you cannot perform logical operations which might allow classification. However you can perform these operations on the data outside RW16/17 and then re-import. The problem then is that I cannot find a way of transforming P-values directly into colour and displaying them as a pseudo-lithology log. I hope someone can think of a workaround. Thanks. David Campbell
  10. With the change from Access (MDB) database structure in RW16 to SQL in RW17, are there any suggested size limits for an efficient RW17 project in terms of the number of wells or amount of data? Having used Access databases in a number of similar type programs, there seemed to be a limit of +/- 300 wells at which point database queries became very slow. Something similar occurs in RW16 when you have a lot of P-data (> 500k data points per well including nulls). ​Regards, David Campbell
  11. Tom, I guess this should make me feel better (i.e. I wasn't such an idiot user) ! Will the RW16 fix be released before the RW17 fix? Regards, David
  12. Thanks Tom, if the issue gets fixed (i.e. images can be depth-registered correctly and then depth-clipped in the striplog) then I shouldn't need to store separate images. I presume this problem didn't occur with RW16? Regards, David Campbell
  13. I want to display and compare bitmap images of logs from several wells on a similar scale. Bitmap import has worked smoothly with log images depth-registered top and bottom, and clipped above/below these depths to include log headers. When I display a single bitmap for an entire well everything appears OK (bitmap aspect ratio preserved, not limited to column width) but the image of course is tiny because of the length of the well log. The problem arises when I try to clip the diagram and focus on a zone of interest. The depth scale on the diagram is clipped but the bitmap image is not clipped and is incorrectly registered in depth. Does any have any tips on how to produce depth-clipped bitmap images without having to store separate images for each zone of interest?
  14. Tom, I am trying to import orientation data for wells that already have locations in the database. The excel files are in the same format as you show above (Borehole-Depth-Azimuth-Inclination). When I use the Multiple Tables option the following occurs: I can select the filename then The appropriate Block Selection (excel sheet -> orientation), and I can see that the Data Coordinates are OK, BUT When I try to allocate the columns /location fields I do not see an option for any of the four data types (Borehole-Depth-Azimuth-Inclination) and my columns are not recognized. I have looked at entering the data as ASCII text but the same issue occurs. What have I missed? Regards, David Campbell PS I would like to send you the excel file but the site tells me "Error You aren't permitted to upload this kind of file"!
  15. When loading a LAS file into Borehole Manager you are asked whether the file contains data columns for well bore azimuth and inclination. If these are not available in the LAS file then the only alternative I can find is to cut and paste data from an excel spreadsheet into the orientation datasheet for each separate well. Is there any way of transferring orientation data from multiple wells into Borehole Manager from an external file or from a utilities data sheet?