RockWorks Revision History

(98) Bug Fix (09/30/06/JPR): The Grafix / Images / Rectify-Image program properly rectifies images that are angled to the northwest.

(97) New Feature (09/29/06/JPR): The Grafix / Images / Rectify-Image program now includes an option for automatically loading the final rotated/cropped image into RockPlot/2D based on the newly calculated image dimensions.

This means that the user can now proceed directly from the calibration process to appending other layers directly onto the image.

(95) New Feature (09/29/06/JPR): The Grafix / Images / Rectify-Image program now includes an option for automatically loading the final image dimension information into the Windows NotePad program (for subsequent use elsewhere).

(94) Cosmetic (09/29/06/JPR): The Grafix / Images / Rectify-Image program now uses a cross-hair cursor for selecting calibration points. The previous version used an arrow.

(93) Improvement (09/29/06/JPR): 18 new symbols have been added to the symbol library.

(92) Improvement (09/29/06/JPR): The maximum number of symbols within the symbol library has been increased from 326 to 1,000.

(91) Improvement (09/28/06/JPR): 33 new patterns have been added to the pattern library.

(90) Improvement (09/28/06/JPR): The maximum number of patterns within the pattern library has been increased from 250 to 1,000.

(89) New Feature (09/28/06/JPR): A new program titled "Stiff Map" has been added to the RockWare-Utilities / Hydrochemistry menu.

This program is used to plot a map of Stiff diagrams depicting the relative ion concentrations for multiple sample sites.

Once selected, the Stiff Map option will present the user with a menu that is very similar to the RockWare-Utilities / Hydrochemistry / Stiff program. The differences are described as follows;

There are no option for plotting a diagram title. Instead, the designated "ID" will be automatically centered within each diagram.
X and Y Coordinate Columns: The diagrams will be centered on these coordinates.
Stiff Dimensions: The program creates Stiff diagram maps by rescaling individual diagrams and centering them on the borehole collar locations. Since the diagrams may vary in terms of the aspect ratio (width/height) you may need to experiment with the x and y dimensions to achieve the optimal result.

Border: The Border option is used to plot an annotated border around the stereonet map. It contains the same sub-options as all of the other mapping programs within RockWorks.

When creating Stiff diagram maps, consider the idea of creating composite maps in conjunction with the RockWare Utilities / EZ-Map program;

(88) Improvement (09/28/06/JPR): The RockWare-Utilities / Hydrochemistry / Stiff program now includes a menu option for enabling/disabling the diagram border.

This option allows the user to control whether or not a border will be plotted around the entire diagram.

(87) Cosmetic (09/28/06/JPR): The "Polygons Per Page" and "Multipage Warning" options within the RockWare-Utilities / Hydrochemistry / Stiff program have been moved to the bottom of the menu.

(86) Bug Fix (09/27/06/JCJ): The program no longer generates an error message upon startup saying that the MDAC component needs to be updated. This error message occurred only with selected machine configurations. The error was caused by the user not having sufficient rights to the registry (i.e. not being an Administrator or Power User). Skipping the message would solve the problem, but it's now a "non-issue".

(85) New Feature (09/27/06/JCJ): The ASCII and Excel imports within the Borehole Manager have been extended to allow the user to import user-defined Location fields. For example, if the user defined a field called Operator, the user could add a column to the Location tab in Excel and import it into RockWorks. Once you choose the file to import; click on the Open File button and the fields will appear, thereby allowing you to change where they are stored in the Location table and even whether they are imported at all. The ASCII and Excel exports will also export user-defined fields.

(84) New Feature (09/27/06/JCJ): When transferring Locations from the RockWare Utilities back to the Borehole Manager, you can now adjust where (and if) the Utilities columns are stored in the Borehole Manager database fields. This includes adding new Location fields in the process. This allows the columns now to be in any order and unused columns do not need to be included. It will still be necessary to have one column for the Borehole name for the program to know which borehole to save the data to. If the borehole exists the data will be updated and any new rows will create new Location records in the database.

(83) New Feature (09/27/06/JCJ): When editing the color-fill table (from the Tables tab), it is now possible to import a Surfer Color Fill Table (*.lvl).

(82) Bug Fix (09/27/06/JCJ): The RockWare-Utilities / Stats / Histogram program no longer skips the first data point.

(81) Bug Fix (09/27/06/MIW): The RockPlot/2D / Rescale utility now access the proper dimension variables (as defined by the user).

(80) Enhancement (09/27/06/MIW): An appropriate error message is issued if the RockPlot/2D / Rescale program is used with a scale less than or equal to zero or a coordinate range less than or equal to zero.

(79) Bug Fix (09/27/06/MIW): Adding a legend to an empty RockPlot/2D diagram no longer generates files with bad coordinates dimensions.

(78) Bug Fix (09/27/06/MIW): The ReportWorks program no longer offsets text in legends and margins for raster images when scaling to fit a smaller printer page.

(77) Bug Fix (09/27/06/MIW): The RockPlot/2D / File / Import / Shape program now honors the Polygon settings.

(76) New Feature (09/27/06/JPR): A new program titled "Stereonet Map" has been added to the Borehole-Manager / Fractures menu.

This program is used to plot a map with stereonets of downhole fractures centered over each borehole location. The following collage shows how fractures are displayed within a 3-dimensional striplog diagram versus a stereonet map.

Once selected, the Stereonet Map option will present the user with a menu that is very similar to the Borehole-Manager / Fractures / Stereonet program (see item #75 directly below). The differences are described as follows;

Minimum Fractures: The "Minimum Fractures" setting defines how the program will handle boreholes that either contain no fractures or not enough fractures to generate a contoured net. Specifically;
- A setting of zero will plot the radial/concentric background grids for all boreholes.
- A setting of one will omit nets for boreholes that don't have at least one fracture. If a borehole contains less than three fractures, the radial/concentric background grid will be plotted along with symbols depicting the projected fracture points.
- A setting of three will only plot the contourable nets.

Stereonet Dimensions: The program creates stereonet maps by rescaling individual diagrams and centering them on the borehole collar locations. Since the diagrams are typically circular (assuming that the color legends, etc. have been disabled), the x and y dimensions should be set to the same value.

If your diagrams contain additional information (e.g. titles, color legends, statistical summaries, etc.), you will need to experiment with x/y settings that produce circular diagrams;

Border: The Border option is used to plot an annotated border around the stereonet map. It contains the same sub-options as all of the other mapping programs within RockWorks.

(75) New Feature (09/27/06/JPR): A new program titled "Stereonet" has been added to the Borehole-Manager / Fractures menu.

This program is used to plot a stereonet depicting the fractures for all "enabled" boreholes. The following collage shows how fractures are displayed within a 3-dimensional striplog diagram versus a contoured stereonet.

Once selected, the Stereonet option will present the user with the following menu;

The menu for this new program is very similar to the Geological Utilities / Planes / Stereonet program. The differences are described as follows;

The program assumes that the downhole fracture data represent planes. There are no options for "Input / Data Types" (i.e. planes, lineations, or rakes).
The program assumes that the downhole fracture data is recorded in dip-direction parlance. There are no options for "Input / Data Convention" (i.e. right-hand rule versus dip-direction). This limitation is designed to maintain compatibility with the other programs that read the downhole fracture data (e.g. striplogs and fracture modeling.
The Symbols option allows the user to either set uniform symbols (i.e. all the same), or symbols that are defined within the borehole location tab.

The Labels option will automatically assign the borehole title as the point label. Many other additional options are included, including the automatic-offset capability;

(74) New Feature (09/26/06/JPR): The Borehole-Manager / Fractures / Export / Utilities-DataGrid program now creates an output column titled "Symbols". This column contains the associated borehole symbol whereas the color of the symbol is based on the color that was assigned to the fracture.

(73) Cosmetic (09/13/06/JPR): The default labeling for the map border has been changed from "Easting (Feet)" and "Northing (Feet)" to just "Easting" and "Northing". The reference to "feet" was causing undue confusion.

(72) Cosmetic (09/08/06/JPR): The background color used by the Graphix / Images / Rectify Images program has been changed from gray to white.

(71) Bug Fix (09/08/06/JPR): The following bugs have been fixed within the Graphix / Images / Rectify Images program;

The program now clips the image properly if the "Clip Image / Based On Custom Dimensions" option is used. The previous version would set the y-max clipping boundary to the x-max setting.
The program now sets the final image to fully enclose the original, rotated image if the clipping is diabled.
The program no longer plots labels (e.g. "#1") which end up within the final image.

(70) New Feature (09/07/06/JPR): A new program for converting gamma counts-per-second data to uranium grades has been added to the Borehole Manager / P-Data / Analyze menu.

Once selected, the Gamma Counts -> Uranium Grade program will present the user with the following menu;

Menu Options;

Gamma (P-Data) Track: Input track (gamma - counts per second).
Grade (I-Data) Track: Output track. Note that this is an I-Data column that must already exist.
Sample Interval: Interval at which to perform resampling.
All Boreholes vs. Currently Highlighted Borehole: The program may be used to perform the conversion for a single borehole or for all of the boreholes.
Constants: The constants (Dead-Time, K-Factor, Water-Factor, or Casing-Factor) may be either specified within the menu (in which case the same constants will be used for all boreholes), or defined within the Location tab. Note: If you're using the Location tab, the fields must already exist.

Conversion Equation:

uranium grade = dead_time_adjusted_counts * k_factor * water_factor * casing_factor * ( 1 / interval_thickness )

dead_time_adjusted_counts = raw_counts / ( abs ( 1 - ( raw_counts * dead_time * 1.0e-6 ) )

Note: Before using this utility, you must create a column (e.g. "Uranium Grade") within the I-Data tab in which to store the output.

(69) Bug Fix (09/06/06/MIW): The redrawing of the patterns within the pattern-selection dialog is now performed correctly when the number of cells exceeds the maximum number of patterns (250).

(68) Improvement (09/06/06/MIW): The RockPlot/3D / Export / ESRI Shape utility has been expanded to include solid models, polygons and any entities that are drawn as solids (e.g. triangles).

(67) Removal (09/06/06/JCJ): The Borehole Manager ASCII and Excel import routines no longer perform the following implicit filtering with stratigraphic interval data;

If both the top and base depths are missing, the previous version would skip the interval.

If the top-depth was greater than the total depth (TD), the program would skip the interval.

If the base-depth was greater than the total depth, the program would set the base depth to the total depth.

If the top depth was less than zero, the program would reset the top depth to zero.

These "smarts" were well intentioned, but have proven to be limiting for some users. Please note that the File / Check Data Integrity option can be used to check for these options.

(66) Bug Fix (09/05/06/JCJ): The GeoTools have been rewritten such that they only allocate memory as needed. The previous version would start out by running all of the programs in the background, thereby consuming unnecessary amounts of memory.

(65) Bug Fix (09/05/06/JPR): The resampling distance filter for 2D I-Data logs now works correctly.

(64) New Feature (09/02/06/JPR): The Geological Utilities / Hydrochemistry / Piper Diagram program menu now includes an option for automatically offsetting control point labels such they do not overplot adjacent symbols or other control point labels.

Examples:

(63) New Feature (09/01/06/JPR): The Geological Utilities / Hydrochemistry / Piper Diagram program menu now includes an option for plotting "leader lines" that connect the point symbols and the point labels.

Examples (with and without leader lines);

(62) New Feature (09/01/06/JPR): The Borehole Manager / Map / Borehole Locations program menu now includes an option for automatically positioning the borehole labels such that they do not overplot adjacent symbols or labels.

Examples;

(61) New Feature (09/01/06/JPR): The Borehole Manager / Map / Borehole Locations program menu now includes an option for plotting "leader lines" that connect the borehole symbols and the borehole labels.

Examples (with and without leader lines);

(60) New Feature (08/31/06/JPR): A new program called "Multi-Log Map" has been added to the Borehole Manager / Striplogs menu.

This program allows the user to create maps in which striplogs are plotted adjacent to the borehole location as shown by the following diagram;

The Log Map menu allows the user to vary the relative scaling of the logs as well as the offset relative to the actual borehole location.

Scaling:

The X and Y scaling provide a means for adjusting the relative sizes of the logs;

To increase the relative width, increase the X-Scaler.

To decrease the relative width, decrease the X-Scaler

To increase the relative height, increase the Y-Scaler.

To decrease the relative height, decrease the Y-Scaler.

Note: Non-vertical logs will be distorted if the x-scaler does not equal the y-scaler.

Offset: The offset refers to the distance between the borehole location and the top of the log. The offset represents a percentage of the project size (e.g. 1 = 1% of the distance from the southwest corner of the project area to the northeast corner of the project area).
Leader Lines: If selected, lines will be plotted from the borehole location to the log.
Auto-Offset: This feature will automatically re-position the logs such they do not overplot adjacent borehole locations and other logs. Compare the following example with the example listed at the top of this write-up.

The automatic offsetting can become obnoxious if the logs are too large (e.g. leader lines crisscrossing the project area). Some experimentation may be necessary in order to gain the optimal output (i.e. the largest logs with the least amount of offset).

The following example show the pitfalls of setting the x and y scalers too high;

X-Scaler = 3, Y-Scaler = 3

(59) Bug Fix (08/31/06/MIW): The Borehole Manager / P-Data / Statistics option no longer produces sporadic "Invalid Floating Point" errors.

(58) Bug Fix (08/31/06/JCJ): The program now works correctly with all versions of gINT.

(57) New Feature (08/31/06/JCJ): The IHS, GDS, and Tobin importing programs now allow the user to choose which items are to imported into the Borehole location tab. In addition, the user can not define if these items should be saved within a field or within the Comments listing. If a field is selected, and it does not yet exist, it is now created "on-the-fly".

Also: The Borehole Name may now be "composed" from various input fields. For example, you may wish to create a borehole name by combining the lease name, well number, and operator.

(56) New Feature (08/30/06/JPR): A new program titled "Rose Map" has been added to the Borehole Manager / Fractures menu.

Once selected, the user will be presented with a menu that is almost identical to the the Rose Diagram program within the Geological Utilities. Minor differences include the Rose Dimensions (expressed as a percentage of the project dimensions) and the Border options.

The Rose Map output will include rose diagrams centered on each borehole that contains fracture data. The fractures within each borehole will be used to generate the associated diagram.

(55) New Feature (08/29/06/AA): The following files have been added to the sample folder;

File	Size (kilobytes)
building_boundary.tab	1
lithology_before_excavation.mod	1,463
RockWorks data import.xls	1,908
streets.dbf	6
streets.shp	19
streets.shx	2
Total:	3,399

These files are referenced by the latest RockWorks hands-on training manual.

(54) New Feature (08/29/06/JPR): A new program titled "Rose Diagram" has been added to the Borehole Manager / Fractures menu.

Once selected, the Rose Diagram option will present a menu that is identical to the Geological Utilities / Linears / Rose Diagram menu.

This program is used to create a rose diagram that is based on the downhole fracture data for all enabled boreholes.

(53) New Feature (08/29/06/JPR): A new program titled "Add Random" has been added to the Borehole Manager / P-Data / Analyze menu.

This program is used to add random numbers to a p-data track.

The random numbers range between the user-specified "Minimum Value" and "Maximum Value". If the original value plus the random value is less than zero, the result will be set to zero if the "No Values < 0" options is checked.

(52) New Feature (08/29/06/JPR): A new program titled "Logarithm" has been added to the Borehole Manager / P-Data / Analyze menu.

This program is used to compute the logarithm of a given p-data column.

Operation Type:

Natural Logarithm. The natural logarithm, formerly known as the hyperbolic logarithm, is the logarithm to the base e, where e is equal to 2.718281828459... (continuing infinitely). The result will be set to zero if the original value (x) is less than or equal to -1. For more information, visit http://en.wikipedia.org/wiki/Natural_logarithm.
Natural Logarithm of X+1. The result is more precise for small values of x. The result will be set to zero if the original value (x) is less than or equal to -1.
10-Base Logarithm. The result will be set to zero if the original value (x) is less than or equal to zero.
2-Base Logarithm. The result will be set to zero if the original value (x) is less than or equal to zero.

Logarithmic conversions are useful when you want to show the variations within the low values despite high values that otherwise "squish" the curve when using the autoscale option.

(51) Improvement (08/29/06/MIW): The Excel import now skips cells that contain formulas in which the formulas contain an errors.

(50) Bug Fix (08/28/06/MIW): The ReportWorks program now formats "world files" in dot-decimal format. The previous version would use the Windows "Regional Settings" which caused problems with non-US configurations.

(49) Bug Fix (08/28/06/JPR): The Borehole Manager / Map / Adjust-Coordinates / Longitude-Latitude->Easting/Northing program no longer produces erroneous and sporadic results if the UTM zone selection is set to "Automatic" and the first borehole is disabled. Instead, the program now defines the UTM zone based on the first enabled borehole.

(48) New Feature (08/25/06/JPR): A new option titled "Resample" has been added to the Borehole Manager / P-Data / Analyze menu.

Once selected, this program allows the user to create a new track (or overwrite the existing track) that contains data from another track which has been "resampled" at a different interval.

This program can be used to either make the data more dense or less dense.

Original P-Data curve (red) sampled a 1' intervals and resampled (blue) data based on 0.1' intervals.

Original P-Data curve (red) sampled at 1' intervals and resampled (blue) data based on 10' intervals.

(47) Cosmetic (08/25/06/JPR): A new submenu titled "Analyze" has been added to the Borehole Manager / P-Data menu.

(46) New Feature (08/25/06/JPR): A new option titled "Truncate" has been added to the Borehole Manager / Stratigraphy / Fence / Modeled menu. This option is identical to the new Truncate options described below (items #44 & #45).

This new option allows the user to view only the stratigraphy between two elevations. This capability is especially useful for users who are interested in detailed analysis of areas that are overlain by thick sequences of overlying stratigraphy (e.g. oil and gas).

(45) New Feature (08/25/06/JPR): A new option titled "Truncate" has been added to the Borehole Manager / Stratigraphy / Section / Modeled menu. This option is identical to the new Profile / Truncate option described below (item #44).

(44) New Feature (08/24/06/JPR): A new option titled "Truncate" has been added to the Borehole Manager / Stratigraphy / Profile menu.

When using the new profile truncation, it may also be desirable to activate the log clipping such that overplotted strip logs only plot within the area of interest. It may also be desirable to adjust the border annotation the the "automatic" setting such that the vertical scale bars only plot within the zone of interest.

(43) Improvement (08/24/06/JPR): The two-dimensional striplog options menu (used by a variety of programs) now includes a "Clip" option with the sub-menu that is triggered by selecting the "Other" button. This option was previously available only by selecting the "Summary" button.

(42) Bug Fix (08/17/06/MIW): The fill and border settings now work correctly when exporting RockPlot/2D labels to RockPlot/3D.

(41) Bug Fix (08/17/06/MIW): The "Include 3D Legend" option within a variety of menus is now "honored" by the RockPlot/3D program.

(40) Cosmetic (08/17/06/MIW): The default contour line color within RockPlot/2D has been changed to dark gray.

(39) Bug Fix (08/17/06/JCJ): A recently introduced bug in the automatic revision update notice has been repaired.

(38) Improvement (08/17/06/MIW): The ReportWorks program no longer generates an "unknown exception" error when attempting to load an invalid world raster image.

(37) Improvement (08/17/06/MIW): The DXF Export option within RockPlot/3D has been enhanced to add support for points, lines and text. In addition the user can select a default color and layer or allow the program to automatically assign colors and create layers based on its scene caption.

Limitations:

No raster images or legends will be exported.
Color assignments may not exactly match.
Line widths may not match.
Point sizes aren't used.
Text will always be aligned with the X axis.

(36) Cosmetic (08/15/06/JCJ): The GeoTools / Geologic Time Chart subdivision menu ("time tree") now includes a plus sign next to items that contain subdivisions. As a consequence, the ellipses have been removed from the same items. In addition, a vertical "splitter bar" now allows the user to control the area that is used to display the time tree versus the event window.

(33) Improvement (08/11/06/JPR): The Geological Utilities / Transfer program now uses the titles to transfer the data back to the Borehole Manager. The previous version required that the data columns be in the same relative order. This created problems with optional fields that were set to be non-visible.

(32) Improvement (08/11/06/JPR): The automatic "Check for newer version on startup." option within the Tools / General Preferences menu now performs the download as a "thread" meaning that you can keep working while the newer version is copied onto your machine.

(31) Cosmetic (08/10/06/JPR): The total-rows field at the base of the Geological Utilities window has been widened to show more digits (and commas).

(30) New Feature (08/03/06/JPR): A new option titled "Translate" has been added to the Geological Utilities / Edit / Columns sub-menu.

Once selected, the Translate option will present the user with a menu asking for the input column, output column, and translation table.

The Translation Table contains a list of target and replacement terms. These terms will be used when converting data within the Target Column to the Replacement Column.

(29) New Feature (08/03/06/JPR): A new submenu titled "Google Earth" has been added to the Geological Utilities / Map menu.

Placemark Map

The "Placemark Map" program will create a Google Earth KMZ (Keyhole markup-language binary) file based on the contents of a Geological Utilities datasheet containing point location data.

An example of an input datasheet is depicted below;

The fields (columns) within an input datasheet consists of;

Name (required): This column defines the text that will appear above each placemark.

Longitude (required): Longitude, in decimal format, for the placemark.

Latitude (required): Latitude, in decimal format, for the placemark.

Description (optional): One or more columns of information that will be automatically displayed within the Google Placemark window.

Icon (optional): This column is used to define a 16x16 pixel image (e.g. .png) that will be associated within the placemark. This icon will be displayed within the Google Earth "sidebar" (located along the left side of the screen) as well as the Google Earth map. Note: Icons must be located within the same folder as the datasheet.

The Google Earth Placemark Map menu is depicted below;

The Placemark Map menu options are described as follows;

Input Columns: The following settings are used to define how the program will process the contents of the input datasheet;

Caption (required): Column that contains text that will be displayed within the Google Earth "sidebar" as well as the label that will be plotted adjacent to each placemark on the Google Earth map.

Longitude (required): Column that contains the placemark longitude. Note: Longitudes must be specified in decimal degrees.

Latitude (required): Column that contains the placemark latitude. Note: Latitudes must be specified in decimal degrees.

Description Start (optional): Column that contains the first item that will be included within the placemark descriptions. This setting will be ignored if the "Include Descriptions" option (see below) is unchecked.

Description End (optional): Column that contains the last item that will be included within the the placemark descriptions. This setting will be ignored if the "Include Descriptions" option (see below) is unchecked.

Icon File (optional): Column that contains the name of the icon file that will be displayed within the Google Earth "sidebar" (located along the left side of the screen) as well as the Google Earth map. Note: Icons must be located within the same folder as the datasheet. This setting will be ignored if the "Custom Icons" option (see below) is unchecked.

Output (KMZ) File: A KMZ (Keyhole Markup language Zipped) file is a compressed version of a KML (Keyhole Markup Language) file. These files contain all of the information that Google Earth needs to plot a map. We chose KMZ over KML for the following reasons;

KMZ files are much smaller than KML files.

Google Earth processes KMZ files faster than KML files.

KMZ files contain all of the sub-files (e.g. linked images) and may therefore be emailed without worrying about other linked images.

Folder Name: The Google Earth "sidebar" (located along the left side of the Google Earth menu) groups items into folders. This is where you should enter some meaningful text that can be used to reference the data (e.g. "Kansas Oil Wells").

Viewer Position:

Range: This setting represents the distance from the viewer to the object on the ground. For large features (e.g. volcanoes), we recommend a setting of 7,500 meters. For smaller features (e.g. mine sites), try 2,000 meters.

Tilt: This setting represents the angle between the viewer and the feature of interest. An angle of zero represents straight-down while 90 represents a horizontal view. For optimum results, try 45 degrees.

Heading: This setting represents the direction that the viewer will be relative to the feature of interest.

Float Labels: If checked, this option will plot the labels above the ground surface at elevation that is determined by the Offset setting (see next item).

Offset: Distance (in meters) from the ground surface to the placemark icon/label.

Include Descriptions: If checked, the program will add data from the designated description columns to the descriptions that appear when the user double-clicks on an icon.

Custom Icons:

Unchecked: The program will use the default Google Earth icon (the pushpin).

Checked: The program will use the icon specified within the Icon File column setting.

Include Legend: This option allows the user to plot a bitmap (e.g. PNG, BMP, etc.) file in the lower-left corner of the main Google Earth display area.

Legend File: If the "Include Legend" option is checked, this is where the name of the file that will be plotted within the lower-left corner of the main Google Earth display area. Note: The legend file must be in the same folder as the datasheet.

Launch Google Earth: Once the KMZ file has been created, this option will start the Google Earth program, using the associated KMZ file.

Download Google Earth

The "Download Google Earth" sub-option will activate your web browser and load the Google Earth web page from which you can download the latest version of Google Earth.

"Google" is a trademark of the Google corporation.

(28) Improvement (08/01/06/JPR): A new option titled "Image" has been added to the list of data types within the Geological Utilities datasheet. This menu is activated by right-clicking on a column title.

If a column data-type has been set to an "Image" type, the program will automatically display a file-selection dialog, with an image-preview screen, whenever the user clicks on a cell within that data column. This is very similar to the "File" data type except that the dialog now previews the image.

(27) Improvement (07/28/06/JPR): The Geological-Utilities / File / New templates that deal with Jeffersonian coordinates now include a meridian field.

(26) Improvement (07/27/06/JPR): The Geological-Utilities / Coords / Jeffersonian Polygons -> Cartesian program now skips any row in which the meridian, range, township, or section are blank.

(25) New Feature (07/27/06/JPR): The "lease_map.atd" sample file now includes a new column titled "Meridian". This column is intended to illustrate the new Meridian option described within Item #24 (see below).

The new Meridian column is set to a Meridian data-type, meaning that if the user clicks on this column, a map will appear, prompting the user to select a meridian (see item #8 below).

(24) New Feature (07/27/06/JPR): The Geological Utilities / Coords / Jeffersonian Polygons -> Cartesian program now includes an option for specifying the column within the input file that contains the meridian that will be used for the data conversion. The previous version required that a single meridian be specified with the right-side of the menu (under RockWare LandBase). This limited the program to only working within a single meridian at one time. As a consequence, it is now possible to perform conversions with data files that span two or more meridians.

(23) Improvement (07/27/06/JPR): The Geological-Utilities / Coords / Jeffersonian Points -> Cartesian program now skips any row in which the meridian, range, township, or section are blank.

(22) New Feature (07/27/06/JPR): The "spot.atd" sample file now includes a new column titled "Meridian". This column is intended to illustrate the new Meridian option described within Item #21 (see below).

The new Meridian column is set to a Meridian data-type, meaning that if the user clicks on this column, a map will appear, prompting the user to select a meridian (see item #8 below).

(21) New Feature (07/27/06/JPR): The Geological Utilities / Coords / Jeffersonian Points -> Cartesian program now includes an option for specifying the column within the input file that contains the meridian that will be used for the data conversion. The previous version required that a single meridian be specified with the right-side of the menu (under RockWare LandBase). This limited the program to only working within a single meridian at one time. As a consequence, it is now possible to perform conversions with data files that span two or more meridians.

(20) New Features (07/27/06/JCJ): A new program titled "Newmont Assay Mdb" has been added to the Borehole-Manager / File / Import menu;

This program imports data from a Newmont Assay Mdb file into the RockWorks Borehole Manager database. Three tables are expected in the Access database, named as follows:

Collar
- Fieldname ........ Type
- Hole_Id .......... Text
- Easting .......... Double
- Northing ......... Double
- Elevation ........ Double
- Td ............... Double
Survey
- Fieldname ........ Type
- Hole_Id .......... Text
- Depth ............ Double
- Azimuth .......... Double
- Inclination ...... Double
Assays
- Fieldname ........ Type
- Hole_Id .......... Text
- From ............. Double
- To ............... Double
- Length ........... Double
- Interval(1..n) ... Double (there can be text fields but will be ignored)

How-To Summary

Access the Borehole Manager.
Open the project folder (if necessary) in which the well records are to be created.
Choose the File / Import / Newmont Assay Mdb option.
Select the database that contains the assay information to import.
Click OK to continue.

(19) New Features (07/24/06/JPR): A variety of new options have been added to the Geological-Utilities / File / Import / Garmin-Txt (From MapSource) program;

Longitude/Latitude Input Formats: The program now supports three different types of input formats; decimal degrees, decimal minutes, and decimal seconds.
Input Elevations: By specifying the elevation units for the input data, the output (see next item) can be converted from one format to another.
Output Elevations: The program will now convert elevations to feet or meters independent of the output format for the easting and northings (e.g. UTM-Feet vs. UTM-Meters).

These new options provide greater flexibility when working with GPS data that has already been gathered. For example, the previous version required that the user set the GPS to decimal degrees and the altitude units to meters BEFORE conducting the survey. Now, it's possible to conduct the survey using a variety of configurations and convert the data to the desired format and units during the import.

(18) Bug Fix (07/24/06/JPR): The Geological-Utilities / File / Import / Garmin-Txt (From MapSource) program no longer always sets the first elevation to zero.

(17) Cosmetic (07/19/06/JPR): The LandBase downloading screen now list the correct percentage completed.

(16) New Feature (07/19/06/JCJ): A new suite of sample files are now included for demonstrating the new GDS (Geological Data Services) import capability. These files are named;

rw4527a.csv: Green River Basin (5 wells). Excel flat file format.
rw4527a.dat Green River Basin (5 wells). GDSII (ASCII) file format.
rw4527b.csv Denver-Julesburg Basin (5 wells). Excel flat file format.
rw4527b.dat Denver-Julesburg Basic (5 wells). GDSII (ASCII) file format.
rw4528a.csv SE New Mexico (172 Wells). Excel flat file format.
rw4528a.dat SE New Mexico (172 Wells). GDSII (ASCII) file format.
rw4528b.csv Green River Basin (35 Wells). Excel flat file format.
rw4528b.dat Green River Basic (35 Wells). GDSII (ASCII) file format.

These files were provided as a courtesy by Geological Data Services. Please visit their web site at www.GDSDataMaps.com.

(15) Bug Fix (07/17/06/JCJ): The Borehole-Manager / File / Import / GDS (Geological Data Services) program no longer generates multiple error messages if the GDSII file does not contain any tops. In addition, the import program no longer omits the last (deepest) top.

(14) Improvement (07/17/06/JCJ/TRA): The following data has been added to the RockWare LandBase;

187 townships (courtesy of the Oklahoma Center for Geospatial Information - www.seic.okstate.edu) have been added to the Cimarron Meridian dataset.
2,342 townships (courtesy of the Kansas Geological Survey - www.kgs.ku.edu) have been added to the 6th Principal Meridian dataset.
1,885 townships (courtesy of the Oklahoma Center for Geospatial Information - www.seic.okstate.edu) have been added to the Indian Meridian dataset.

Note: In order to use the LandBase-related programs, you will need to download the latest version of the LandBase files because the internal format has changed.

The following table summarizes the data that is contained within the current LandBase database;

Meridian	BLM #	Townships	Sections	Township		Range
5th	5	877	29,569	60S	164N	107W	25E
6th	6	7,214	249,250	35S	58N	121W	25E
Black Hills	7	163	5,544	12N	23N	1E	18E
Boise	8	2,216	75,688	16S	65N	8W	46E
Choctaw	10	21	756	2N	8N	6E	10E
Cimarron	11	187	5,914	2S	6N	1E	28E
Gila-Salt River	14	3,394	114,727	24S	42N	25W	32E
Humboldt	15	16	453	5S	4N	6E	8E
Indian	17	1,885	64,799	11S	29N	27W	28E
Michigan	19	148	5,178	11N	28N	18W	9E
Montana	20	4,172	146,900	17S	37N	35W	63E
Mount Diablo	21	4,720	157,292	34S	48N	19W	71E
Navajo	22	1	15	5N	5N	10W	10W
New Mexico	23	3,686	121,998	34S	51N	22W	39E
Salt Lake	26	2,076	68,580	44S	15N	20W	26E
San Bernardino	27	971	28,471	19S	31N	17W	27E
Uintah	30	136	3,993	23S	5N	26W	3E
Ute	31	14	456	4S	2N	3W	3E
Willamette	33	2,568	87,613	41S	32N	16W	51E
Wind River	34	120	3,637	2S	9N	6W	6E

(13) New Feature (07/12/06/JCJ): The Borehole-Manager / Location tab now includes a field for the Range & Township principal meridian. This new field allows the user to enter range and township data for regions that span more than one principal meridian. For example, let's say that you have a large project that includes wells within Colorado, Kansas, and Oklahoma.