(134) New Feature (09/30/09/JPR): Hint boxes (the little yellow messages that appear when a user "hovers" the cursor above a menu item), now appear as little 100 pixel wide boxes rather than long, single-line strips that could really be obnoxious, especially when displaying long messages on a three-screen system.

(133) New Feature (09/29/09/JPR): There are now three ways to adjust the "g" replacement value within the solid model editor when editing generic and I-data models.

1. Use the new slider bar up and down, relative to the color index.  Note how the "Color Index G-Value" (below) and the "Other Replacement Value" (within the Edit tab) will change as the slider is moved.

2. Click on a spot within the color index.

3. Enter the replacement value within the "Other" field (within the Edit tab).

(132) Bug Fix (09/28/09/JPR): Potentiometric symbols are now discarded if they fall outside the clipping region within a two-dimensional striplog (see example within item #131 below).

(131) Bug Fix (09/28/09/JPR): Aquifer annotation within clipped regions in two-dimensional striplogs are now properly clipped to the same dimensions as the shaded aquifer (the light-blue region within the following example).

(130) Improvement (09/27/09/JPR): The "rcl_06.rcl" sample file no longer creates a huge (and somewhat unusable) "montage" from the program output.  Instead, the program uses the new RCL/HTML capability (see item #128 below) to create an HTML report showing all of the output.  The montage capability is still demonstrated but with a much smaller dataset (four diagrams).

• The "montage.atd" file is no longer used by the rcl_04.rcl script to show all of the diagrams that are created within the rcl_04.rcl script.

(129) Improvement (09/27/09/JPR): The "rcl_04.rcl" sample file no longer creates a huge (and somewhat unusable) "montage" from the program output.  Instead, the program uses the new RCL/HTML capability (see item #128 below) to create an HTML report showing all of the output.  The montage capability is still demonstrated but with a much smaller dataset (four diagrams).

• The "montage.atd" file is no longer used by the rcl_04.rcl script to show all of the diagrams that are created within the rcl_04.rcl script.

(128) New Feature (09/27/09/JPR): It is now possible to save the output from RCL (RockWorks Command Language) sessions within an HTML (HyperText Markup Language) file for subsequent review within an HTML browser program (e.g. Amaya, Chrome, FireFox, Flock, Internet Explorer, Maxthon, Netscape Navigator, Mosaic, Opera, Sarari, Sea Monkey, etc.).  Sending output to an HTML file is accomplished via the following new RCL commands;

HTML_START: File name

• Any HTML listing must begin with this command.

• The HTML_START command must be accompanied by a parameter that specifies the name of the file in which the HTML content is to be saved.

• Example: HTML_START: Project 27 Report.html

• All files that contain an HTML_START command must also contain an HTML_END command after the HTML_START command.

HTML_PIC:  File name

• The HTML_PIC command must be accompanied by a parameter that specifies the name of the graphic file that will be added to the HTML script.  Note: This is any graphic file (e.g. PNG, BMP, JPG, WMF, etc.) that is compatible with the target browser.

• Images that are displayed within HTML files will be automatically centered relative to the left and right edges of the display.

• Any occurrence of the HTML_PIC command must be preceded by an HTML_START command.

• Any occurrence of the HTML_PIC command must be followed by an HTML_END command.

HTML_TEXT: String

• The HTML_TEXT command should be accompanied by a string that will be displayed within the HTML file.

• Text will be automatically centered relative to the left and right edges of the display.

• Any occurrence of the HTML_TEXT command must be preceded by an HTML_START command.

• Any occurrence of the HTML_TEXT command must be followed by an HTML_END command.

• A horizontal line will be drawn below the line of text.  This serves as a visual separator between the text and the next item within the HTML file.  As such, the HTML_TEXT command is primarily designed for annotating diagrams that are created by the HTML_PIC command.

HTML_END:

• The HTML_END command does not include any parameters.

• Any occurrence of an HTML_END command must be preceded by an HTML_START command.  In RCL, unlike life, you can't finish something that you didn't start in the first place.

• The HTML_END command will automatically load the designated file (as defined within the HTML_START command) into the default HTML/web browser such as Microsoft's Internet Explorer.

Example:  The following example shows a simple case in which an HTML file titled "Project 27 Report.htm" will be created.  A line of text at the top will say "Project 27 Report".  A picture (project_27.png) will then be displayed, followed by a caption reading "Project 27 Site Map".

HTML_START: Project 27 Report.htm

HTML_TEXT: Project 27 Report

HTML_PIC: project_27.png

HTML_TEXT: Project 27 Site Map

HTML_END:

(127) Improvement (09/25/09/JPR): Previous versions of the program would circumvent errors within flat-surface contouring by displaying a diagonal message across the map saying that "Error: Nothing to map..."  The program now simply skips the contouring step.  This change was made so that maps that include cell outlines, faults, etc. will still be plotted even if the surface is flat.

(126) Cosmetic (09/23/09/JPR): The Help / Execution History program now includes a listing that shows the number of times that various internal RockWorks commands have been issued.  This new capability serves no real purpose other than to help RockWare employees when testing the software (i.e. what's been tested and what hasn't after a major re-build).

(125) New Feature (09/22/09/JPR): The RCL program now includes an option for presenting the user with a report that lists all of the errors that were encountered after an RCL script file has been processed.

The report will be automatically opened within the RockWorks text editor.

(124) New Feature (09/22/09/JPR): The RCL program will now notify the user if a vestigial (outdated) command has been replaced with a new command.

(123) New Feature (09/22/09/JPR): The RCL program menu now includes an option that defines whether or not the session will be interrupted by error messages as errors are encountered (versus ignoring the errors and proceeding with the processing of the RCL script).

If an error is encountered, the script execution will be suspended and an error message will be displayed.  At this point, the user has the option to ignore the error and continue with the script processing or abort (cancel) the RCL processing altogether.

(122) New Feature (09/20/09/JPR): All programs that relied upon the Windows default text editor for viewing ASCII files now use the built-in RockWorks text editor.  This change was made because some configurations of Windows6 (Vista) will load the files into Microsoft Word in such a way that subsequent report will generate a error because Word has locked the file for editing.

(121) New Feature (09/17/09/JPR): A new button labeled "More Fault Options" has been added to the 3-D Surface Options menu.

This new button will present the user with some new fault display options.

This new menu includes the following options;

• Polylines:  Useful for displaying faults as polylines.  This option is best suited when plotting surface with little vertical exaggeration.

  • Color:  Color that will be used to display fault polylines.

  • Thickness:  Thickness (in pixels) for fault polylines.

  • Vertical Offset:  Vertical units (e.g. feet, meters) to plot the polylines relative to the grid surface.  This is useful if the fault polylines are not readily distinguishable (i.e. interfering) with the grid surface.

  • 

• Panels:  Display faults as vertical panels.

  • Panel Color:  Color that will be used to display fault panels.

  • Vertical Dimensions:  The height (and depths) of the fault panels may be determine in one of two ways;

    • Automatic:  The top of the fault panels will be set to an elevation equal to the highest grid node value.  Conversely the base of the fault panels will be equal to the lowest grid node value.

    • Manual:  The top of each fault panel will be determined by adding the "Upper Offset" (see below) to the corresponding node value.  The base of each fault panel will be determined by subtracting the "Lower Offset" (see below) to the corresponding node value.  The Manual setting is useful when plotting surface with little vertical exaggeration and lots of faults that would otherwise hide each other when compared with the Automatic setting.

    • 

      • Upper Offset:  This value determines the height of each fault panel.  Specifically, the top of each fault panel will be determined by adding the "Upper Offset" to the corresponding node value.

      • Lower Offset:  This value determines the elevation for the base of each fault panel.  Specifically, the base of each fault panel will be determined by subtracting the "Lower Offset" to the corresponding node value.

      • 

(120) New Feature (09/17/09/JPR): A new feature titled "Correlate Partially Defined Intervals" has been added to the Borehole Manager / Stratigraphy / Fence (ESRI) / Straight menu. This new capability performs the same function as that listed below (item #117) for the Borehole Manager / Stratigraphy / Section / Straight program.

(119) New Feature (09/17/09/JPR): A new feature titled "Correlate Partially Defined Intervals" has been added to the Borehole Manager / Stratigraphy / Fence (Google Earth) menu.

This new capability performs the same function as that listed below (item #117) for the Borehole Manager / Stratigraphy / Section / Straight program.

(118) New Feature (09/16/09/JPR): A new feature titled "Correlate Partially Defined Intervals" has been added to the Borehole Manager / Stratigraphy / Fence / Straight (Hole-to-Hole) menu.

This new capability performs the same function as that listed below (item #117) for the Borehole Manager / Stratigraphy / Section / Straight program.

(117) New Feature (09/16/09/JPR): A new feature titled "Correlate Partially Defined Intervals" has been added to the Borehole Manager / Stratigraphy / Section / Straight (Hole-to-Hole) menu.

This new feature is designed to address an aesthetic "issue" (formerly known as a "problem") within RockWorks-generated well-to-well stratigraphic correlations.  Specifically, the regions between boreholes were previously filled only if the intervals on either side included depth information for both the superface (top) and the subface (bottom) of a given stratigraphic unit.  From a scientific standpoint, this approach is sound.  On the other hand, some folks (with check-signing capabilities) prefer that these regions be filled.  Hence this new capability.

The following example illustrates how the program works with the new "Correlate Partially Defined Intervals" option disabled and enabled.  Notice how the upper section (Correlate Partially Defined Intervals = False) does not draw a correlation for the Potosi Formation between DH-35, DH-01, and DH-36.  This is because the base of the Potosi is not defined (blank) within DH-01.  In the lower section (Correlate Partially Defined Intervals = True), the program will consider the base of the Potosi within DH-01 to be equal to the total depth of the well for correlation purposes (i.e. it won't mess up the database).  The same logic applies to the missing Leadville correlations between DH-08, DH-19, and DH-33.

The new capability also applies to sections in which the top of a stratigraphic unit is missing.  The following example illustrates how the program works with the new "Correlate Partially Defined Intervals" option disabled and enabled.  Notice how the upper section (Correlate Partially Defined Intervals = False) does not draw a correlation for the A-Horizon between DH-36, DH-21, DH-08, and DH-29.  This is because the top of the A-Horizon is not defined (blank) within DH-21 and DH-08.  In the lower section (Correlate Partially Defined Intervals = True), the program will consider the top of the A-Horizon to be equal to the collar elevation for correlation purposes (i.e. it won't mess up the database).

The "Correlate Partially Defined Intervals" is turned on by default.  As always, aesthetics trumps scientific rigor.

Note: This new capability only applies to two types of scenarios;

1. The top of the first (uppermost) interval is missing.

2. The base of the last (lowermost) interval is missing.

Missing (blank) superface and subface depths for intervals other than the uppermost and lowermost intervals may produce erratic results and is therefore highly discouraged pending the completion of the optional anti-bonehead module.

(116) New Feature (09/16/JCJ): Archive Database will export the data in the database to a text file and then combine it with the Data Dictionary and INI files into a zip file with the option of adding a password.  This zip file is saved within the Backup folder.  It is in a format that can be sent to RockWare if we are working with you and your data.  Also if your data is stored in a database server like MSSQL Server, it allows an additional backup of your data separate from the database server’s backup.

(115) New Feature (09/16/09/JPR): The Borehole Symbol & Label Options submenu now includes options that determine how the program will handle missing data (e.g. undefined stratigraphic depths).

Consider the following scenario ... The user has elected to show contact depths, elevations, and/or thicknesses for a selected stratigraphic unit.  The relationship between the boreholes and the selected stratigraphic unit may fall into one of four categories;

• Top and base of unit encountered within borehole.

• Only top of unit encountered within borehole (i.e. borehole drilling terminated before encountering base of unit).

• Only base of unit encountered within borehole (i.e. top of unit eroded - above ground surface, borehole is being drilled upwards - raisebore).

• Neither top nor base of unit encountered within borehole (i.e. borehole not drilled deep enough to encounter unit).

The various possible combinations are now handled as follows;

• The thickness will be displayed if the top depth has been defined and the base depth has been defined.  Otherwise, the program will either omit the thickness value or list the value as "undefined", depending upon the "Missing Data" setting.

• Depth and elevation labels will behave in a similar fashion.

 If an item is listed as "Undefined", the suffix will be omitted because it looks stupid and ill-mannered (e.g. "Thickness = Undefined Feet" versus "Thickness = Undefined".).

(114) Improvement (09/14/09/JPR): Profile, Section, and Fence-Location Maps are now embedded as separate tab items within the following application menus;

(113) Improvement (09/14/09/JPR): Profile, Section, and Fence-Location Maps are now embedded as separate tab items within the following application menus;

• Utilities / Grid / Profile

• Utilities / Grid / Fence

• Utilities / Solid / Profile

• Utilities / Solid / Section

• Utilities / Solid / Fence

• Borehole Manager / Lithology / Profile

• Borehole Manager / Lithology / Section

• Borehole Manager / Lithology / Fence

• Borehole Manager / Stratigraphy / Profile

• Borehole Manager / Stratigraphy / Section / Modeled

• Borehole Manager / Stratigraphy / Section / Straight

• Borehole Manager / Stratigraphy / Fence / Modeled

• Borehole Manager / Stratigraphy / Fence / Straight

• Borehole Manager / I-Data / Profile

• Borehole Manager / I-Data / Section

• Borehole Manager / I-Data / Fence

• Borehole Manager / T-Data / Profile

• Borehole Manager / T-Data / Section

• Borehole Manager / T-Data / Fence

• Borehole Manager / P-Data / Profile

• Borehole Manager / P-Data / Section

• Borehole Manager / P-Data / Fence

• Borehole Manager / Fractures / Profile

• Borehole Manager / Fractures / Section

• Borehole Manager / Fractures / Fence

• Borehole Manager / Aquifers / Profile

• Borehole Manager / Aquifers / Section

• Borehole Manager / Aquifers / Fence

(112) Improvement (09/11/09/JPR): The 3D striplog elevation-based clipping now truncates interval-based data that spans the clipping planes.  The previous version would completely remove any intervals that encompassed a elevation clipping plane.  This improvement applies to lithologic, hydrologic, well-construction, I-data, P-data, and data.

(111) New Feature (09/11/09/JPR): The Borehole Manager maps now plots "callout boxes" for just the T-Data that meets the filter criteria.  In the following example, the only boreholes that are labeled/annotated are the holes in which arsenic was sampled on 8/6/07, and the arsenic value was greater than 0.01ppm, and the sampling depth was less than 90 feet.

(110) New Feature (09/10/09/JPR): The Borehole Manager maps now include options to plot selected a single type of T-Data (versus all of the T-Data values).

These new options provide more control over the T-data that is to be displayed adjacent to the borehole symbol.

(109) Cosmetic (09/09/09/JPR): The "Fault File" option within the gridding algorithm sub-menu has been renamed to "Fault Table" because faults are now stored within the project database as a table.

(108) Cosmetic (09/09/09/JPR): The Length-Based options have been removed from the Borehole Manager / Fractures / Rose Map program options because they make no sense.  Specifically, it's impossible to perform any length-based analyses when there's no length-based data to begin with.

(107) Cosmetic (09/09/09/JPR): The Length-Based options have been removed from the Borehole Manager / Fractures / Rose Diagram program options because they make no sense.  Specifically, it's impossible to perform any length-based analyses when there's no length-based data to begin with.

(106) Cosmetic (09/09/09/JPR): The Length-Based options have been removed from the Utilities / Grid / Directional Analyses / Grid -> Rose program options because they make no sense.  Specifically, it's impossible to perform any length-based analyses when there's no length-based data to begin with.

(105) Cosmetic (09/09/09/JPR): The Length-Based options have been removed from the Utilities / Linears / Rose Diagram / From Bearings program options because they make no sense.  Specifically, it's impossible to perform any length-based analyses when there's no length-based data to begin with.

(104) Cosmetic (09/08/09/JPR): The "Length Based Analysis" reference has been removed from the Utilities / Linears / Rose Diagram / From Endpoints (Length Based Analysis) program titles because the program can perform either frequency-based or length-based analyses/diagrams.  In addition, the menu has been slightly re-designed as shown below.

(103) New Feature (09/08/09/JPR): A new program titled "Replacement Filter" has been added to the Utilities / Solid / Filter menu.

This new tool is used to replace selected nodes within a model with the node values from another model.

Why would you want to use this filter?  Consider a situation in which stratiform geology has been intruded by metastasized dikes ...

<add discussion about setting up the lithology/stratigraphy tables> 

•  Step 1. Enter the downhole stratigraphic information just for the stratiform units and create a stratigraphic block (solid) model.

• Step 2.  Set up your lithology table by following these guidelines;

  • Make sure that the g-values for the intrusive units are not the same as the g-values for any of the stratigraphic units. 

  • It's a good practice to group the units by g-value.  In this example, we've assigned the A-Horizonal to a g-value of 1, the Spergen = 2, the Leadville = 3, and so on.  The intrusives might have g-values like Rhyolite = 100, Apalite = 101, Quartz Vein = 102, etc.  In this way, the g-filter (see item #102 - below) can be used to create intrusive-specific models for use within this program.

• Step 3.  Enter the downhole lithology information for all lithologic units; sedimentary and intrusive.  Be sure to use the assign the same g-values to the sediments within the lithology table that were used within the stratigraphy table.

• Step 4.  Create a lithologic model for the intrusive(s).  Be sure to use the g-filter option within the lithologic modeling program to create a model that only defines the intrusive units.

• Step 5.  Use the new Replacement Filter program to overwrite the sedimentary nodes with the intrusive nodes.  The output will be a lithology model that really a mix of stratigraphic and lithologic models.  As such, we call it a "geologic model."

• The changes described here and in items 102 and 101 (below) provide a means for combining lithology and stratigraphy to accommodate scenarios that can't be handled with a single approach.

(102) New Feature (09/08/09/JPR):  The lithology modeling options now include a special "G-Filter" that can be use to set all nodes outside a specified g-range to a null value.

This new capability allows the user to create a final model that is limited to specified lithotypes.  Here's an example of how this might be used;

(101) New Feature (09/08/09/JPR): A new type of lithologic modeling called "Closest Point" has been added to the lithology modeling menu.

This algorithm will set each node value to the g-value of the closest control point (i.e. the downhole lithology data).  Typical applications would involve complex non-stratiform geology (e.g. multiple intrusions, impact craters, karst, etc.). 

(100) New Feature (09/04/09/JPR): A new option has been added for specifying the number of tick marks that appear between the labeled intervals within two-dimensional striplogs.

This new option allows the user to control how many tick-marks will appear between the labeled intervals on a two-dimensional striplog depth-bar.

Notice that this option is labeled "Minor Tick Intervals" rather than "Tick Marks Per Interval".  A setting of "1" will result in no minor tick marks because they're overplotted by the major tick marks.  A setting of "2" will subdivide the major interval into two sub-intervals with a single tick mark, and so on.  This convention makes it much easier/intuitive compared with specifying 9 ticks in order to create 10 subdivisions.

(79) New Feature (09/03/09/JPR): The Utilities / Solid / Edit / 3D program now includes an option for adjusting the number of intervals within the legend when working with generic and I-Data models.

In reference to the example above, notice the difference in the legend when the Color Intervals are set to 10 versus the number of labels when the Color Intervals setting is changed to 29.

(78) New Feature (09/02/09/JPR): The 2D striplog designer now includes an option for including the elevation labels adjacent to the depth labels.

The elevation labels will enclosed in parentheses adjacent to the depth labels.

At first glance, you may wonder why we just didn't allow the user to specify depth or elevation labels and then plot the elevation labels at the appropriate intervals.  This would have worked for the vertical and inclined holes, but deviated holes (and horizontal inclined holes) represent an interesting problem.  Specifically, the elevation interval is not constant. 

(77) New Feature (09/02/09/JPR): It is now possible to manually specify the number of decimals places that are used when plotting 2D striplogs.

This new capability allows the user to override the automatic decimal determination and enter their own decimal preference.

(76) New Feature (09/01/09/JCJ): The File / Transfer / Stratigraphy -> Borehole Manager program now offers the user an option to backup the database before performing the import.

(75) New Feature (09/01/09/JCJ): The Utilities / File / Export option now allows the user to choose which fields to export and the type of the field.

(74) Improvement (09/01/09/JCJ):  The Utilities / File / Import / XY Pairs no longer assumes that the tab file is a polyline table.

(73) Improvement (09/01/09/JCJ):  When importing LogPlot keyword files, the program now imports the line width settings.

(72) New Feature (09/01/09/JCJ):  New to RockWorks15 is the ability to use Microsoft’s SQL Server as the data server in addition to Microsoft’s Access (Jet). 

There are many flavours of SQL Server, on the low end is SQL Server Express which is a free download from Microsoft to their Enterprise SQL Server.

·         More robust database

·         Faster data retrieval

·         4GB (for SQL Server Express, Enterprise Edition does not have a limit) database size, up from the 2GB MS Access allows

Database Engine – the engine that delivers the data to RockWorks

·         MS Access (Jet) what RockWorks has been using until RockWorks15

·         MS SQL Server

Server – this only applies to MS SQL Server and represents the SQL Server instance supplying the data.  Usually this is the name of the computer the server runs on.  For SQL Server Express 2008 the value for the Server on our test machine was “OBSIDIAN\SQLEXPRESS” for SQL Server 2005 it was just the name of the server.  The database server may contain multiple databases.

Show Login Prompt – If your database is setup to require a login and password this will show the login prompt allowing you to enter that info when opening the project.  MS SQL Server requires a login however SQL Server can be configured to pass through your network login (Windows NT Integrated Security) and this prompt need not be shown.  If Show Login Prompt is checked it is assumed you are using a database login and not your network login and conversely if it is unchecked it is assumed your network login is to be used.

Two authentication modes are available when connecting to an instance of SQL Server Database Engine:

Windows Authentication Mode (Windows NT Integrated Security)

Microsoft Windows Authentication mode allows a user to connect through a Windows user account.

SQL Server Authentication

When a user connects with a specified login name and password from a non-trusted connection, SQL Server performs the authentication itself by checking to see if a SQL Server login account has been set up and if the specified password matches the one previously recorded. If SQL Server does not have a login account set, authentication fails, and the user receives an error message.

Prompt for Data Source – Allows you to edit the connection to your database in case there are some fine-tuning settings that needs to be made.  This prompt is only show during the setup of a new project, if you need to edit it afterwards you can edit the connection string in the project’s Menu.ini.

Generate a SQL Script File without executing it – Will save the SQL script it generates instead of executing it, creating the database.  So by choosing this option the database will not be created, instead it will leave you back at the project you started with.  This allows greater control on where and how the database is created or handing off the script off to a Database Administrator to run if you do not have create rights in your database server for a new database or tables.

(71) New Feature (09/01/09/MIW):  It is now possible to tab between the various tabs within the new-style menus by pressing the <Ctrl> key and a number key.  For example, pressing Ctrl+1 will activate the first visible tab.  Pressing Ctrl+0 will activate the tree menu.

(70) New Feature (09/01/09/MIW):  A new option titled "Zoom Undo" has been added to the RockPlot-2D / View menu and the button bar.  This option will cancel the previous zoom operations.  Note that the Zoom Undo is not the same as the Zoom Out option.  Zoom Out replots the diagram at a scale that fits the window.  Pressing <Ctrl> and the "-" character serve as a hotkey for the Zoom Undo function.

(69) New Feature (09/01/09/MIW):  Polylines can now be saved to an XY Table for use within the Cross Section Picker (see item #62 below).

(68) New Feature (09/01/09/MIW):  RockPlot2D graphic items pasted into a zoomed window are now centered in that window.  If there's more than one item their relative positions are maintained.

(67) New Feature (09/01/09/MIW):   The font color that is used by the Color, Stratigraphy, Lithology and Well Construction Legends within the RockPlot/3D program is now automatically determined by the background color.  This color will contrasts with the background for greater visibility assuming that the initial color was set to black.

This option may be disabled by un-checking the "Automatic Text Color" option within the legend options menus.

(66) New Feature (09/01/09/MIW):  A new program titled "ESRI Shape File" has been added to the Utilities / Solid / Export menu.

This new program will convert the nodes within a RockWorks solid model into an ESRI "Shape Point" file.

(66) New Feature (09/01/09/MIW):  A new program titled "ESRI Shape File" has been added to the Utilities / Grid / Export menu.

This program has two export options;

• Elevations (PointZ):  This creates an ESRI "PointZ" shape file in which the z-values are included with the points.

• Values (Points):  This creates an ESRI "Point Shape" file with only the xy node locations.

(64) New Feature (09/01/09/MIW): A new option titled "Copy to New Window" has been added to the RockPlot-2D / View menu that is embedded within the various application menus.  This option will copy the contents of an embedded RockPlot-2D diagram into a new, un-embedded RockPlot-2D window.

(63) New Feature (09/01/09/MIW): A new option titled "Copy to New Window" has been added to the RockPlot-3D / View menu that is embedded within the various application menus.  This option will copy the contents of an embedded RockPlot-3D diagram into a new, un-embedded RockPlot-3D window.

(62) New Feature (09/01/09/MIW): Users can now create an XY Pairs Table or an XY Table from a group of selected Lines, Arrows, Polylines and Polygons within the RockPlot/2D program.  Polylines and Polygons will be exported as line segments.  Here's an example;

The options menu contains a variety of utilities for converting the selected item into a table that will be embedded within the project database for subsequent use by other programs (e.g. storing polylines to use as faults within the inverse-distance gridding). 

(61) New Feature (09/01/09/MIW): Fault vertices are now stored within the new XY Pair tables.  These tables are embedded within the project database.  Older polyline-based fault files can now be imported into these XY Pair tables.  The Fault category within the Project Manager has been removed.

(60) New Feature (09/01/09/MIW): The Distance Weighting gridding with Custom Sectors now uses a database table that is embedded within the project database.

(59) New Feature  (9/01/09/JPR):  The "Borehole Symbol & Label Options" menu (accessed from the Borehole Manager / Map / Borehole Locations menu) now includes an option for plotting T-Data adjacent to the borehole location.

This new option is used to plot T-Data within a borehole location map.

(58) New Feature  (9/01/09/JPR):  The "Borehole Symbol & Label Options" menu (accessed from the Borehole Manager / Map / Borehole Locations menu) now includes an option for disabling the date filtering altogether (i.e. show all aquifer data).

(57) New Feature  (8/30/09/JPR):  A new program titled "Degrees/Minutes -> Decimal" has been added to the Utilities / Coords menu.  This program converts degrees and decimal minutes into decimal degrees.  This is a format that is output by some configurations of GPS devices.

(56) New Feature  (8/30/09/JPR):  A new program titled "Decimals -> Degrees/Minutes" has been added to the Utilities / Coords menu.  This program converts decimal degrees to the degrees and decimal minutes format that is used within some GPS and GIS software.

(55) Improvement  (8/26/09/JPR):  The Directional Weighting / Custom menu now includes an option for specifying the "Default Exponent".  This number represents the weighting exponent that will be used for directions that are not specified within the Directional Weighting Table, thereby minimizing the amount of information that needs to be entered into the table.

(54) Cosmetic  (8/26/09/JPR):  The Directional Weighting / Custom menu now includes descriptive cartoons.

(53) Improvement  (8/25/09/JPR):  The Grafix / 3D-Utilities / Fault Contours -> Fault Surface program now generates an error message if a contour polyline only contains one point.

(52) New Feature  (8/21/09/JPR):  The "Borehole Symbol & Label Options" menu (accessed from the Borehole Manager / Map / Borehole Locations menu) now includes an option for showing the dates and times for aquifer data.

This new capability provides essential information when creating maps that show multiple sampling events for individual wells.

(51) Cosmetic  (8/21/09/JPR):  The "Borehole Symbol & Label Options" menu (accessed from the Borehole Manager / Map / Borehole Locations menu) has been redesigned such that it's far less intimidating (aka "cluttered").

(50) New Feature  (8/21/09/JPR):  The Grafix / 3D-Utilities / Fault Contours -> Fault Surface program now includes options for creating solid-fill color diagrams, mesh diagrams, or a combinations thereof.

Notice (below) how the various perturbations can be used to produce aesthetically interesting effects.