• Existing zone - pick the top or base depth of a zone from another class, which does not contain intervals

• Well header depth - choose either the Depth datum or Final TD of the well

• User defined depth (SS) - enter a specific subsea depth value

OpenWorks users will appreciate the new Landmark Color Gradient Import feature. This allows you to create a Petrosys color gradient based upon the color gradient defined in OpenWorks, giving a similar display within OpenWorks, Petrosys Mapping and Petrosys 3D Viewer.

Map Sheet Selection Based On Date Created

Choosing a mapsheet via Mapsheet/Select allows ordering of listed mapsheet by creation date and last edited date. This data is now stored with each mapsheet, along with the user creating or editing a mapsheet. For existing mapsheets, the creation date will remain blank. Control over how mapsheet borders appear has also been enhanced, allowing thickness to be specified in absolute terms and alternative line styles to be selected. Control your preferences by using the right-mouse button, 'list preferences' option.

Browse Files, Launch Applications From Petrosys Reports

Now when a user double clicks on an item in the dbMap report or query window it will allow the user to directly view the document or image associated with the query result. This can be used to launch a 3rd party application to view a file if its full path is returned in a report. Contact Petrosys support if you would like further details on how to configure these options.

Release 16.7sp2

Petrosys release 16_7_2 [57 entries]

dbMap ... ... Enhancements

dbMap culture is now spatially enabled ...

The dbMap Culture module is now spatially enabled for clients with Petrosys dbMap Spatial option, with implementation based on the PPDM 3.8 "Spatial Descriptions" module. All existing dbMap Culture functionality has been retained, including edit and security functions.

All Petrosys dbMap modules have now been spatialised, making it possible to process all dbMap data in a spatial context. E.G. "give me all wells within a certain (culture) permit"; or "return all seismic lines going through a certain (culture) province".

As with all other spatialised dbMap modules, "spatial" coordinate data (known as "sdo" or "sdo_geometry" data) is automatically synchronized with the standard Culture module coordinate data.

Display/Spatial allows display of dbMap culture ...

dbMap culture has been made available for display via the Display/Spatial option, allowing the full use of Display/Spatial functionality, including thematic mapping.

General ... ... Enhancements

Culture group editor list has more appropriate list headers ...

The column headers of the group editors in the culture database editor had some outdated and hard to read strings, which made it difficult to work out the meaning of each column. The headers have been updated to be more appropriate and readable.

ESRI ArcMap Plugin - Add easier control of grid interpolation properties ...

A properties button has been added to the Petrosys Toolbar in ArcMap. This allows easy control over the way Petrosys grids are displayed and used by other ArcGIS plugins or applications. The grid interpolation can be turned off if it is causing a problem with other plugins that cannot handle the high resolution raster sets returned by the default Petrosys grid interpolation. Additionally the maximum pyramid level that ArcGIS sees for Petrosys grids can be controlled by the "Maximum grid interpolation" field.

Export/Arcview grid (BIL export) supports CRS information and floating point single band ...

The option to export BIL files (/File/Export/ArcView/Grid...) has been upgraded to automatically output the grid CRS into the .prj file and also to have the actual floating point grid values written in single band mode. This means that the grid will now be correctly georeferenced in ArcMap and you can use all the gradient shading options in ArcMap to render the surface coloring.

Key configuration help topics added to main help architecture ...

Petrosys has added detailed help topics to cover a number of configuration scenarios. The aim of these notes is to provide users with the key concepts of Petrosys Configuration to undertake various configuration tasks.

General ... ... Bug Fixes

Display sections one per picture uses Depth dialog for Time option ...

The option "Displays/Sections - one per picture/Time" to plot seismic profiles to PIC files incorrectly showed the Depth dialog. This led to the vertical scales being incorrectly honored. The correct Time dialog is now displayed allowing the option to function correctly.

ESRI ArcMap Plugin - Grid display gives continual license errors if no license available ...

The Petrosys ArcMap plugin is now more friendly when a grid is displayed in ArcMap and no Petrosys licenses are available. Previously it would give continual license errors and your only recourse was to kill ArcMap.

Grid interpolation was not working correctly when fault coordinates touched grid cell boundaries ...

Grid interpolation was not working correctly around faults which had coordinates located on grid cell boundaries. If this was the case, some of the cells around the faults would return no interpolation. This is now fixed.

Grid/Edit Grid Header used to store the project default CRS in grids without CRS without any user confirmation ...

When using the Edit Grid Header function to browse grids created in versions prior to the CRS (i.e. pre-16.X), the file would be automatically assigned the project default CRS and saved without notifying the user. This automatic assignment has been reverted so that the user now sees that the selected grid CRS is not assigned instead (the word "default" is used for the CRS name).

This problem was introduced in Petrosys version 16.6.

Solaris version was not working due to incorrect ArcSDE libraries ...

The Solaris version of 16.7sp1 Petrosys would fail to start due to an incorrect version of an ArcSDE library. This problem manifested itself as the following error appearing in the console window "ld.so.1: dbmap: fatal: libsde.so: open failed: No such file or directory"

Import and Export ... Enhancements

Support for new IHS Energy PPDM data model ...

IHS Energy has replaced the IPL data model used by many Canadian clients with a new PPDM datamodel. The existing IPL wells functionality available in Petrosys is now configured to run against the new IHS data model. Functionality includes:

Zokero SeisWare 3D surfaces can now be imported to Petrosys grid files ...

3D seismic surfaces from Zokero SeisWare can now be imported to Petrosys grid files using File/Import/SeisWare on the main Petrosys menu.

Import and Export ... Bug Fixes

Display/Contour - RMB export to polygon exports the selected contour ...

A problem with this option was introduced in version 16.7, which resulted in no polygon being created.

GeoFrame formations without feature boundaries can now be used in Petrosys ...

Previously when selecting formations for direct display or gridding, only formations linked to formation boundaries could be selected. All formations are now available for use.

GeoFrame survey polygon import precision improved ...

Previously importing survey polygons from GeoFrame into Petrosys polygon files rounded Easting/Northing points to six significant figures. The precision has been improved significantly to a minimum of four decimal places.

Improved error message when attempting a 2D SeisWorks connection to a project with no 2D lines ...

In previous 16.7 releases of Petrosys, an attempt to connect to a SeisWorks 2D project which had no 2D seismic lines resulted in the generic error message dbcnxnsw:1 "Unable to establish connection for '<project-name>'" being displayed.

This error message has been improved to specifically indicate that the connection failed due to the selected project not containing any 2D lines.

Note: While it is possible for Petrosys to filter the list of projects to only those that contain 2D lines, the Landmark function to query for the existence of seismic lines is quite slow, so to maintain reasonable performance all potentially valid 2D projects are listed.

Primary Oracle database is disconnected if SeisWorks connection fails ...

If you attempted to connect to a SeisWorks project from an option like Display/2D seismic/SeisWorks, and the connection failed (e.g. from insufficient licenses), it would silently disconnect from the primary Oracle dbMap database if you had one. This would result in dbMap related options not functioning correctly. e.g. Selecting a CRS for a mapsheet would not show any projected CRSs when you select a geographic one, Edit/Wells/dbMap created a list with no columns and you would not be able to add any wells to it.

This only affected clients who use a primary Oracle dbMap database.

SeisWorks R2003.12 import horizon names contained strange characters ...

Strange characters no longer appear at the end of horizon names when importing data from SeisWorks R2003.12 projects via File/Import/Landmark/SeisWorks direct link.

SeisWorks R5000 project disappears from list if not selected ...

If you had access to only one OpenWorks R5000 interpretation project, and did not connect to it the first time it appears in the list of available SeisWorks connections from Display/2D Seismic/SeisWorks, the next time you tried to select a SeisWorks connection for displaying seismic data the R5000 project would not be available. If you had access to more than one OpenWorks R5000 interpretation project, it was not a problem.

Spatial data translator creates columns in Petrosys culture point groups wide enough to handle loaded data ...

The Export/Spatial data translator option has been upgraded to allow unlimited column name size when writing to Petrosys culture file point groups. Previously string data was truncated to a maximum of 13 characters.

Mapping/Coordinate Reference Systems ... Enhancements

CRS matching improved when well known text matches more than one CRS ...

The process by which well known text is mapped to a CRS has been improved for the case where the well known text matches multiple CRSs by matching using the following precedence order:

EPSG database upgrade procedure. ...

This release updates the Petrosys CRS database to bring it in line with the EPSG database version 7.4 (25th November 2009).

The CRS database is updated by two different means, depending upon site configuration.

dbMap based sites:

All other sites (SQLite based):

The CRS changes included in this upgrade will not affect existing data, but there are some implications that may have an impact on sites (deprecated CRSs for example).

GeoFrame EPSG style datum names are handled automatically ...

GeoFrame projections can be specified via an EPSG Geographic CRS, such as "EPSG:4326_2", which are automatically mapped to a corresponding Petrosys CRS, without the need for any manual configuration.

Support added for additional projection types ...

Petrosys now supports several new CRS projection types:

Predefined EPSG CRSs that use these projection types are available for selection, and each of the projections may also be used when creating custom CRS entries.

All of these projection types are EPSG standards, except for the Hammer projection.

Mappings (where appropriate) to read data from OpenWorks and GeoFrame are also included.

Mapping/Coordinate Reference Systems ... Bug Fixes

Geographic CRS well known text with inverse flattening set to zero is matched to existing CRSs ...

An inverse flattening of 0 for an ellipsoid is a convention that indicates the ellipsoid actually represents a sphere. This was previously not being accounted for, resulting in a custom geographic CRS being incorrectly created.

Grid CRS crawler reported grid projection incorrectly for grids without an assigned CRS ...

Petrosys grid crawler now reports projection information correctly in the 'Legacy Projection' section, for grid files without an assigned CRS. A problem was introduced in Petrosys version 16.6, where the project default CRS was incorrectly reported for these grids.

Mapping/Wells ... Bug Fixes

Display/Wells with large selection file queried data multiple times before posting anything ...

Display/Wells for any data source apart from WDF, using a selection file (.wsl) with more than 254 wells, now only queries for the wells from the file in the map area once before posting data on the map. Previously it would re-query the well data multiple times, relative to the number of wells in the selection file divided by 254. e.g. if the selection file had around 1000 wells, it would query all wells 4 times. If the selection file had around 5000 wells, it would query all wells 20 times. If there were less than 254 wells in the selection file, it was fine.

This was not a problem if you used one of the other data selection methods (e.g. Using form or User defined) or if no selection method was used.

Mapping - Display/Wells was crashing when apwell license was not available ...

Fixed bug where Display/wells crashed mapping when no apwell license was available.

Web map server ... Enhancements

Display/WMS default display format changed to PNG ...

The default image format for the display of WMS imagery has been changed to PNG, which supports image transparency. The image formats available for selection depend upon the formats supported by a particular WMS server.

Web map server ... Bug Fixes

WMS server displays all types of data in correct locations on all map types ...

Previously, when the WMS server was used to display database based map layers on a geographic mapsheet, data could be drawn with a small offset from its correct location. In addition to database based map layers, this also affected all other map layers subsequently drawn.

WMS Server renders images requested using geographic coordinates correctly ...

The Petrosys WMS server allows images to be served using both rectangular and geographic CRSs. In previous versions, images served using geographic coordinates could be returned in incorrect positions. This has been corrected by changing the rendering method used by the WMS server, which also means that an alias CRS is no longer required to be selected to serve WMS images when using a geographic CRS.

Well data ... Enhancements

A default SRD elevation can now be stored in WDF files ...

A default Seismic Reference Datum elevation can now be stored in WDF files. The default value can be set on the Mapping/Wells/Edit/General screen.

Ability to copy WDF spreadsheet layouts ...

It is now possible to copy spreadsheet layouts within the WDF editor (Mapping/Wells), including the hard coded "Header summary", "Selected zones" and "Zone velocities" spreadsheets from the Well selection/Well header and Zone data folders in the tree widget.

After selecting any spreadsheet from the Well selection/Well header or Zone data folders in the tree widget, the new menu option Spreadsheet/Copy layout becomes available and prompts to enter the new layout name to copy the currently selected spreadsheet into. Once you press Ok, the new spreadsheet layout is created with the same columns as the current one, and the spreadsheet is then refreshed to display data using the new layout. You can then modify the new layout using the Spreadsheet/Edit layout option.

It is also possible to do the same thing using the RMB/Copy layout menu option within the spreadsheet itself.

WDF files now support zone intervals to handle range data ...

WDF files now allow users to define zones that are intervals for which the top and base depth of the zone are based on one of the following:

The most common use is to define an interval to be between two existing zones.

Once you have defined what to use for the top and base depth of your zone interval, it is available for use with mapping and gridding in the same way as a normal zone.

For more information on creating zone intervals refer to the help topics WELL DATA FILE - ZONES and WELL DATA EDITOR - CREATING AND EDITING ZONES.

Well data ... Bug Fixes

WDF zone spreadsheets do not display TVD/SS or other computed values ...

A bug was introduced in version 16.7.1 which resulted in computed values such as Zone Top (SS) being blank in spreadsheets within the WDF editor (Mapping/Wells). The computed values were correctly used by gridding, map display and bubblemaps.

Release 16.7sp1

2D seismic data is now accessible from SeisWorks R5000 merged 2D/3D projects ...

2D seismic data from SeisWorks R5000 projects that contains both 2D and 3D data, is now available for direct import, display and gridding. Previously only 3D surveys were able to be selected as SeisWorks connections from a merged 2D/3D project.

Each SeisWorks R5000 interpretation project now appears in the list of SeisWorks connections available as a 2D project. This means that projects with no 2D data are also available for selection. The reason it does not restrict the list to only show projects that actually have 2D seismic data, is because checking if a SeisWorks R5000 project contains 2D data can be quite slow.

Accuracy improved for SeisWorks 2D coordinates ...

File/Import/Landmark/SeisWorks direct link now loads Easting/Northing coordinates for 2D seismic lines using two decimal places. Previously the Easting/Northing values were rounded to the nearest integer.

This improvement also occurs when reading 2D seismic data from SeisWorks using direct devkit access for display (Mapping/Display/2D seismic/SeisWorks) and gridding (Grid,contour,volumetrics/Grid/Create grid/Input data/Seismic/SeisWorks).

GeoFrame 4.5 support ...

GeoFrame 4.5 is now supported by Petrosys on RedHat Linux RHEL 4 and 5 platforms.

This includes direct import from IESX, Charisma and GeoFrame as well as direct display, gridding and contouring from IESX and GeoFrame.

Import of well data from OpenWorks & GeoFrame to WDF is now available on Windows ...

It is now possible to import well data from OpenWorks and GeoFrame to Petrosys WDF files on Windows. Well header information, directional survey and formation tops are supported.

On Windows the functionality is available from File/Import/Wells, Import/Geoquest/GeoFrame-wdf and Import/Landmark/Openworks-wdf.

On Linux and Solaris the functionality is still available from Import/Geoquest/GeoFrame-wdf and Import/Landmark/Openworks-wdf.

For help on configuring access to OpenWorks and GeoFrame from windows please contact Petrosys support.

Seismic data is now available from OpenWorks R5000 master projects ...

2D and 3D seismic data from OpenWorks R5000 master projects is now available for direct import, display and gridding using the following existing SeisWorks options:

When selecting a SeisWorks project to connect to, the relevant OpenWorks master projects appear in the list for selection. Previously, R5000 seismic data had to belong to an interpretation project before it was available for selection with these options.

WMS layers are requested as transparent format ...

The Display/Picture/Raster option displays served WMS layers with a transparent background where supported by the WMS server and requested format.

Bug Fixes

3D viewer is now ok when opening dbm file containing Petrel bin grids ...

The 3d viewer will now work when displaying a Petrosys DBM file that contains Seismic Bin Grids from Petrel.

All SeisWorks R5000 horizon versions are now available for import and gridding ...

OpenWorks R5000 introduced support for versions of horizons, which are now available when importing SeisWorks data (FILE/Import/Landmark/SeisWorks direct link) and gridding SeisWorks data (Grid, contour, volumetrics/Grid/Create grid/Input data/Seismic/SeisWorks). When selecting horizons, you will now see the horizon name, interpreter, attribute, and version as seen in OpenWorks. Previously only the horizon name was shown in the list.

Connecting to SeisWorks improved for multiple R5000 connections.xml entries ...

If you have multiple OpenWorks R5000 entries in connections.xml, getting a list of SeisWorks projects and connecting to the desired project is now much faster.

Previously, if you had four OpenWorks R5000 entries in connections.xml corresponding to four different databases, it would read the list of SeisWorks projects from each database four times. It now only reads from each database once. Also, when you selected a SeisWorks project to connect to, it would re-read the list of projects from each of the four databases. It now only re-reads the list of projects from the database relevant to the selected SeisWorks project.

Gridding from SeisWorks dispatch connection correctly interpolates locations for reverse SP lines ...

If you created a grid from SeisWorks horizon data using Grid/Create grid/Input data/Seismic/SeisWorks, the coordinates interpolated for lines that were in reverse shot point order could have been wrong, particularly if it was not a straight line.

Display/Picture/Raster - Incorrect error message removed when modifying ArcSDE layers ...

When displaying ArcSDE raster layers incorrect error messages could appear when nothing was wrong.

Display/Text draws correctly on rotated mapsheets ...

Previously, Display/Text layers on rotated mapsheet could incorrectly hide other map features in some circumstances.

EPSG oblique stereographic projection support ...

In previous versions of Petrosys, the stereographic projection has been based on USGS / Snyder equations. The EPSG oblique stereographic projection (EPSG code 9809) defines slightly different equations and this variation is now also available in Petrosys. Existing projected CRSs in the Petrosys CRS database that are based on the stereographic projection are automatically converted to use the EPSG compliant projection.

Any existing data (including mapsheets) that was created in a previous version of Petrosys and is based on a stereographic CRS will not be affected by this change. When data such as this is loaded, a equivalent custom CRS mapped to the USGS version of stereographic will be used, meaning that no shift in data will occur. Data can be manually reprojected to use an equivalent EPSG stereographic based CRS if required.

Please note that in the projected CRS editor, "Stereographic" corresponds to the previous USGS projection and "Oblique Stereographic" corresponds to the EPSG projection.

Flex Tools option operational on Vista and Windows 7 ...

The option /Maintain/Flex tools will now run on Vista and Windows 7. As this tool requires elevated privileges to run it will use the operating systems to prompt for the rights to run the program.

Improved support for MapInfo WMS servers ...

The request parameters used by the WMS display option have been adjusted to comply with stricter requirements for MapInfo WMS servers.

WMS images requested correctly from WMS version 1.3.0 servers ...

In previous versions, the WMS parameters were incorrectly specified when version 1.3.0 WMS data was accessed.

Menu option Query/Spatial is now operational ...

The menu option /Query/Spatial is now operational. Previously it would do nothing and you had to use the right mouse button option to get the query to work.

Opening corrupted grid files is now more robust ...

The software is now more tolerant to corrupt and truncated grid files. It will no longer crash when these files are encountered during operations such as the crawler.

WDF editor can crash when viewing spreadsheets with large amount of data on windows ...

When opening a WDF file on windows that has a large number of wells and zones and viewing a spreadsheet, it can cause the wdf editor to crash due to running out of memory.

A warning message is now displayed when this occurs and some enhancements have been made to help avoid crashing.

To avoid running out of memory you can select fewer wells or zones to view in the spreadsheet.

Release 16.7 - Enhancements

3D Viewer

Client specific

Connections, import and export

dbMap

General

General - graphics

General - User interface

Import and Export

Mapping

Mapping/Editors

Mapping/Images

Mapping/Map Sheets

Mapping/Spatial

Mapping/Wells

Petrel plugin

Surface modelling

Surface Modelling/Grid Operations

Surface Modelling/Gridding

Surface Modelling/Kriging

Web map server

Well data

Release 16.7 - Bug Fixes

3D Viewer

Administration/dbMap

Configuration

Connections, import and export

dbMap

General

General - User interface

Graphics/Plotting and Hardcopy

Import and Export

Mapping

Mapping/Editors

Mapping/Images

Mapping/Map Sheets

Mapping/Spatial

Mapping/Wells

Petrel plugin

Surface modelling

Surface Modelling/Contouring

Surface Modelling/Grid Operations

Surface Modelling/Gridding

Well data

Detailed Release Notes

Petrosys release 16_7 [116 entries]

3D Viewer ... Enhancements

Formation rules function now available for all database well data sources ...

When displaying formation tops in the 3D Viewer you can now specify precedence rules. This functionality is available for database data sources as well as Petrel and Petra.

Improved 3D Viewer north arrow has clearer indication of up and down sense ...

The north arrow in the 3D Viewer has been improved to allow easier recognition of whether you are looking up or down. The new north arrow is green when viewed from above and brown when viewed from below, has distinct sculpturing on the top and base, and includes E and W annotation.

Performance enhanced for the 3D Viewer on Windows ...

The 3D Viewer on the Windows platform has some significant speed improvements, particularly when rendering large grids. Additionally it has reduced memory usage and some increased stability. For example the time taken to render certain grids has dropped from 12 minutes to 12 seconds.

3D Viewer ... Bug Fixes

3D Viewer Display/Modify panel stability improvements ...

The 3D Viewer Display/Modify panel is now more robust when handling the system in a busy state.

3D Viewer exits gracefully when license not granted ...

3D Viewer no longer crashes when the appropriate license is not granted at start up.

3D Viewer viewpoint help updated ...

Help context on viewpoints brings up the correct help topic.

Prompt to save modified .3dm file when changing project added ...

Previously Petrosys 3D Viewer did not prompt to save the current .3dm file has been modified and the user attempted to change project.

In addition a number of enhancements have been made to the merging behaviour of 3D Viewer.

Administration/dbMap ... Bug Fixes

Handle Admin/Reports/Edit - 'Validate all queries...' when there are no queries correctly ...

dbMap no longer crashes if you press the 'Validate all queries...' button on the SQL editing screen when there are no queries in the list.

Client specific ... Enhancements

Added isopach display to Display/Wells for Santos ...

Santos now have the ability to display well formation thicknesses from their dbMap databases via the Isopach tab on the Display/Wells option.

Increased employee id field width on user security screen for Santos ...

On the Santos Admin/Reference tables/Wells/Business units/List users dialog, the 'Employee id' field length has been increased from 6 to 7 characters in line with database changes already in place.

Configuration ... Bug Fixes

64-bit Windows install always defaults to C: drive ...

When installing on 64bit windows the installer would sometimes try and install on the partition with the most free space, rather than the C: drive. It now always chooses the C: drive as the default.

Installation can now handle hand-edited multi-line redhat-release files ...

The installer is now more tolerant of Linux system files that have been hand edited to allow the system to appear to be a different version than it really is. When reading the /etc/redhat-release file to determine the current version Petrosys now handles a number of non-standard variations.

Linux/Solaris installer simplified - Does not prompt for type of software to install ...

The Linux/Solaris install script is now much simpler. It asks three less questions than the previous version, namely:

Connections, import and export ... Enhancements

Direct display of wells from Petra ...

It is now possible to display wells, directional surveys and formation tops directly from Petra projects in interactive mapping.

Direct display of wells from SeisWare ...

It is now possible to display wells, directional surveys and formation tops directly from SeisWare projects in interactive mapping and the 3d viewer.

File/Import/Wells now remembers the last data type imported ...

When you launch File/Import/Wells it now defaults the input data type to the value you last used.

Import of ODM wells to WDF now uses File/Import/Wells wizard ...

Import of wells from ODM now uses the File/Import/Wells wizard. This enables better support for importing formation tops and filtering the list of wells to be imported.

Multi-connect to ODM no longer requires connections.xml entry ...

Previously when using multi-connects to directly display or grid data from an ODM project, an entry had to exist for each ODM MSAccess database (.mdb) file in connections.xml. This is now no longer required, as the ability to dynamically select an ODM database (.mdb) file has been added to the connection manager.

This has been done in the connection manager Add screen, which now has ' -> Select *.mdb file' as the first entry in the list of available connections, in addition to all ODM projects listed in connections.xml. By selecting this item and pressing OK, you are prompted to select the desired ODM database file.

Petrosys now uses the GFDK development kit rather than IESX development kit for accessing IESX data ...

In 16.6.0 Petrosys released an alternative IESX direct connection plugin as a beta component. This plugin could be enabled through the use of an environment variable. After further testing Petrosys has concluded that the new plugin performs better than the earlier version and has now been switched to be the default plugin for direct connection to IESX data.

If you experience a problem with the new plugin the old version is still available by setting the PS_IESX_USE_OLD_PLUGIN environment variable. This can be done in two ways:

1. Set the environment variable in your session before launching Petrosys using (for csh):

setenv PS_IESX_USE_OLD_PLUGIN 1

This will use the old plugin for this session only.

2. Set the variable in the [USER] section of your petrosys.cfg file. This will cause all Petrosys users to use the old plugin.

Well paths from ODM can now be imported into WDF ...

It is now possible to import directional survey data for wells from ODM into a Petrosys well data file (WDF). This can be done via the File/Import/Wells wizard, or the File/Import/ODM option in the WDF editor (MAPPING/Wells)

Connections, import and export ... Bug Fixes

Charisma 2D import now supports the same line name being used in multiple surveys ...

Previously if you attempted to import a seismic line from Charisma whose name existed in more than one survey the data would not be imported. Now you will receive a warning that the project contains duplicate seismic line names and they can be imported if you disambiguate by assigning a prefix or a suffix to the lines.

GeoFrame grids and 3D surfaces may have been incorrectly CRS converted if assigned to a UTM projection ...

Previously when Petrosys accessed a grid or 3D surface from GeoFrame the associated CRS may have been read incorrectly if it was a UTM projection. This did not affect wells, seismic lines or 3D bin grid display.

Petra well paths are rotated correctly for grid north directional surveys ...

Previously, if you had wells in Petra with directional surveys that had the survey orientation set to "XY Grid North (Never Rotate For Map Projection)" and you imported them into a WDF via File/Import/Wells, or directly displayed them using 3D Viewer/Display/Wells, the well paths would not be rotated correctly to adjust for differences between coordinate reference systems.

Retrieving a list of GeoFrame projects could fail if Petrosys previously crashed ...

If Petrosys previously crashed it could cause some data to be written to panels.pnd that prevented a list of projects being extracted from GeoFrame. Changes have been made to avoid this data being written by and also to skip bad entries in existing panels.pnd files.

Retrieving a list of OpenWorks projects on Windows could fail if Petrosys previously crashed ...

On Windows, occasionally when you tried to connect to an OpenWorks project (e.g. from Display/Wells), and pressed the 'Add' button, no projects would appear in the list.

This only occurred if there was a Petrosys-dbMap connection called OW_PROJECT_RETRIEVAL in the File/Connection manager dialog.

This is a temporary internal connection used to get the list of OpenWorks projects and no longer appears in the connection manager, so the Add button now works correctly.

Support for GeoFrame horizons with embedded newlines within the property or attribute fields ...

Previously, in the GFDK-IESX plugin, if any horizon in a project had a newline character in either the property or attribute fields then Petrosys would be unable to access data from all horizons within that project. This has been corrected so Petrosys removes any newline characters from all fields, thus giving access to all horizons.

dbMap ... Enhancements

Added new dbMap SQL functions ps_well_path_map_dtm_lat and ps_well_path_map_dtm_lon ...

New dbMap SQL functions ps_well_path_map_dtm_lat and ps_well_path_map_dtm_lon have been added which compute the latitude/longitude at a specific depth along a well path and then datum convert to the datum of the current mapsheet. This is useful for ad hoc reports where you may want all locations to be reported in the same datum.

dbMap reports and map queries - Double clicking on an item in the list is now the same as selecting View/Image ...

When you double click on a row in dbMap report or map query window it will now perform the same functionality as selecting View/Image. This can be used to launch a 3rd party application to view a file if its full path is returned in a report. Contact Petrosys support if you would like further details.

dbMap ... Bug Fixes

Pressing delete on the asset item keyword screen when no keywords are selected could cause dbMap to crash on Windows ...

If you attempted to delete an Asset item keyword while there were none in the list it could cause dbMap to crash. This only occurred on Windows installations.

General ... Enhancements

Startup error message for invalid Petrosys - Linux version improved ...

The Linux start up scripts check for the correct platform and prints a user friendly error message if the Petrosys application can not be run. This would occur, for example, if a user tried to run a Petrosys version built for RedHat EL4 on a system that is running RedHat EL3.

General ... Bug Fixes

CRS Crawler handles locked and corrupt SDFs ...

The CRS crawler now reports any SDFs that could not be opened due to being locked or corrupt. Previously, crawling files such as these resulted in an invalid report file being generated.

General - graphics ... Enhancements

Default font in Petrosys maps set to Arial on Windows ...

Arial is now used as the default font for new projects on the Windows platform.

General - User interface ... Enhancements

Manual/Automatic redraw/recalculation icon - State now indicated by tooltip text ...

The redraw and recalculation mode icons in Mapping and Workflow Gridding now indicate their state in the tooltip text that pops up when the mouse pointer hovers over the icon. This makes it clear what will happen when you click on the icon.

General - User interface ... Bug Fixes

The Linux well symbol selector handles embedded bitmaps in well symbols ...

Custom well symbols with embedded bitmaps will now work correctly on Linux. Previously this would lead to a crash of the application.

Graphics/Plotting and Hardcopy ... Bug Fixes

View/Plot no longer reports an incorrect error for plotters that do not require an output filename ...

A bug was introduced into the 16.6 version of Petrosys where the View/Plot option could sometimes report a missing filename error for plotters that do not require a filename to be entered.

Import and Export ... Enhancements

Export spatial data such as shape, culture, and polygon files to Petrosys fault files ...

Petrosys fault file has been added as a supported output format for spatial data export functionality. This allows files such as shapefiles, polygon files, culture files, etc. to be written to a Petrosys fault file. This functionality is available in the following options:

Extended list of 3D surveys available from IESX ...

Within the GFDK interface provided by Schlumberger there is a specific bug that affects a small number of clients where the complete list of 3D surveys in their GeoFrame project is not returned. Petrosys has enhanced the GFDK-IESX plugin to work around this bug to allow access to all 3D surveys in the GeoFrame project.

Improved support for Z data in spatial export functionality ...

Exporting spatial data from Petrosys now includes 3rd dimension/Z values where possible (i.e. the input data contains Z values and the output format supports writing Z values). This is applicable for the following options:

Import and Export ... Bug Fixes

Date data is now written when spatial data is imported into a culture point group ...

The FILE/Import/Arc Shapefile option now correctly writes date attributes to the output culture file.

Spatial data translator handles null date attributes correctly ...

In previous versions, exporting null date attributes would result in a random date value in the output data. This has been corrected so the output value is set to null.

Mapping ... Enhancements

CGM keyword {BASE_CWD} added to show the base project name ...

You can now use the keyword {BASE_CWD} in title blocks and ASCII CGM file to substitute for the project name of the current project. It takes the base name of the current working directory.

Creation of backup files (.bak) when saving dbm files in mapping is now optional ...

The creation of backup files when saving dbm files in mapping is now optional and off by default.

To turn on this automatic backup file creation select the option 'Create backup (*.bak) of dbm file on save' from the File/Preferences/Mapping... dialog.

Import Landmark color gradient to Petrosys color gradient ...

An option to import Landmark color gradient files into Petrosys gradient files has been added. The option is available in the gradient selector under File/Import Landmark (*.clm)

Landgrid ease of use improvements ...

Petrosys now allows the configuration of a global landgrid file which is used in Display/Landgrid. The global landgrid settings can be configured in the File/Select menu option or from the main menu 'Select' button. This global setting is also saved into the dbm file and reloaded when the dbm file is opened. By default, Display/Landgrid will use the global landgrid file (if configured). The user has the option to override the default by choosing a different landgrid file.

Mapping ... Bug Fixes

Display Gip-Data does not allow display of value without symbol ...

The display of Gip data now allows the posting of just the value without a symbol.

Display layers with invalid connections are now inactive when opening a .dbm file ...

If you open a .dbm file that contains a database connection (e.g. Display/Wells/OpenWorks) and you are not able to connect to it when prompted, the layer that uses the connection will now be made not visible.

Previously, if you had a problem connecting to a database when opening a .dbm file, the layer would remain active, it would try to draw data from it, and you would get the error dbgen:150 'Make sure you are connected to a database before retrying this option.'

Display/Bubble map from WDF panel is more is stable ...

The bubble map display screen is now more robust when used on a slow machine and you click on the zones button whilst the panel is still loading.

Display/Map (dbm) file option handles missing files ...

The Display/Map (dbm) File option handles files missing from dbm files being displayed in an equivalent manner to loading the dbm file directly in Mapping.

Display/Map (dbm) file works correctly regardless of layer id numbers ...

In previous versions, using this option when the Petrosys internal layer id numbers were very large could lead to various problems such as not being able to change layer visibility, layers going missing, or crashes in the software. This behaviour has been corrected and large layer ids are now handled.

Full coordinate information is displayed when tracking on grid display layers ...

Previously, when a grid with a very long name was displayed and tracked, the coordinate information could be truncated.

Improved handling for Display/Text when displayed text is located outside the current mapsheet ...

In previous versions, Display/Text annotation displayed with a box could be erroneously drawn when the text lay a long way outside of the mapsheet being used. This problem would manifest with an empty text box being drawn as a vertical or horizontal bar across on the entire map

Landmark metafile display allows polygons to be displayed unfilled ...

The Display/Culture/Landmark metafile option now supports display of unfilled metafile polygons. Previous versions assumed that all polygons were filled, and if a fill color was not explicitly specified, black was assumed.

Missing file resolution handles title block image filenames correctly ...

Several issues were fixed relating to checking whether CGM files referenced in title blocks existed or not:

Missing file resolution now checks for missing child files ...

The file resolution functionality checks that all files referenced in a mapsheet are present when the mapsheet is loaded. Petrosys now includes better checking for files that are not directly referenced in a mapsheet, but referenced indirectly by other files instead. An example of this is a title block that references a CGM that references a raster image.

Mapping/Editors ... Enhancements

Default CRS for Edit/Create Single Polygon is the mapsheet CRS ...

When polygons are created in a Petrosys polygon file using the Edit/Create Single Polygon option, the default CRS is set to the mapsheet CRS. This ensures that the default settings will result in the created polygon being displayed on the current mapsheet.

Mapping/Editors ... Bug Fixes

Culture editor could crash when opening invalid culture files ...

Opening invalid culture files in the Culture Editor could potentially cause a crash in previous versions. This issue has been fixed and an error message is now displayed instead.

Culture Editor/Edit/Compute values option can be run multiple times ...

In previous versions, this option could cause a crash when run multiple times or using an invalid input formula.

Mapping/Images ... Enhancements

WMS Raster image display ...

Serving raster images via a WMS server is increasingly being recognised as a strategy to manage large collections of images. Petrosys supports display of WMS images through the Display/Picture/Raster option, which allows selection of WMS server and layers.

WMS images are requested from a server based on the current mapsheet extents (no interactive placement is possible, unlike other raster sources). WMS servers may allow a CRS to be selected to serve the imagery, and this will be used to reproject the served images for display on the mapsheet.

The Display/Picture/Raster WMS interface supports entering WMS server URLs directly, but also selection from a pre-populated list.

Mapping/Images ... Bug Fixes

Display/Picture/Raster image updated after modifications to layer parameters ...

In previous versions, changing parameters such as transparency on the Display/Picture/Raster panel and then pressing apply or cancel could have no effect due to a cached image being drawn.

Mapping/Map Sheets ... Enhancements

Map sheet border lines use standard line style selectors ...

Control over how mapsheet borders appear is enhanced by use of standard line style selectors. This allows thickness to be specified in absolute terms and alternative line styles to be selected.

Map sheet selection based on date created ...

Choosing a mapsheet via Mapsheet/Select allows ordering of listed mapsheet by creation date and last edited date. This data is now stored with each mapsheet, along with the user creating or editing a mapsheet. For existing mapsheets, the creation date will remain blank.

Mapping/Map Sheets ... Bug Fixes

Petrosys cancels quit process when problems encountered saving mapsheet ...

Previously the application would exit with a warning if a mapsheet definition file is read-only and a mapsheet had been modified. This has been fixed so the application now gives a warning that the save operation fails but does not exit, giving the user the opportunity to save their mapsheet elsewhere prior to closing Petrosys.

Mapping/Spatial ... Enhancements

Display/Spatial date templates include year-only and year-month varieties ...

In previous versions, date fields had to be displayed in a format including the day value. This is not always appropriate, so new formats allow dates to be displayed showing the year only or the month and year.

Display/Spatial RMB / Export spatial data option includes attribute data ...

Data exported from Display/Spatial via the RMB / Export spatial data option now includes all attribute information from the input data being displayed. This will only be written to output formats that support attribute data (for example shapefiles)

Mapping/Spatial ... Bug Fixes

Display/Spatial database layers store connection name only ...

When Display/Spatial SDE and Oracle Spatial layers are saved to a dbm file, the database connection name is saved as visible text. Previously, this information was stored in encrypted format, which made it difficult to modify the dbm file contents to refer to a different database server.

Display/Spatial default query attributes are used for new layers only ...

Display/Spatial stores any query names selected to be used as an annotation for a particular database/layer. These stored queries are used to populate the selected attributes by default when a new Display/Spatial layer is created. In previous versions, the default queries were also automatically selected at inappropriate times, such as when a layer was edited.

Display/Spatial displays multi-point shapefiles containing a single point without errors ...

Multi-point shapefiles that contain one or more multi-point geometries with a single point can now be displayed in Display/Spatial without an error being raised. In previous versions, data such as this was displayed correctly, but an error was also shown.

Display/Spatial point annotation works correctly at locations other than centre ...

In previous versions, displaying annotations for point data in Display/Spatial did not work unless there was at least one annotation displayed at a centre location.

Display/Spatial query attributes supports selection of a large number of attributes ...

In previous versions, if the total length of all attributes selected using the Display/Spatial query attributes option was greater than 256 characters, Petrosys mapping would become unresponsive.

Display/Spatial reads line style correctly from pre 16.0 dbm files ...

A line style setting stored in a dbm file is now honoured when displaying MapInfo and DGN files. Previously, the line style from the MapInfo or DGN file was used, regardless of whether this had been overridden.

Memory leaks in mapping - Oracle spatial, WDF display, shapefile display ...

On the Linux platform the use of Display/Spatial could slowly use up more and more memory until in some cases the application would stop responding or crash.

Shapefile date attributes may be selected as annotation in Display/Spatial ...

In previous versions, shapefile date attributes were not available for selection in the annotation selection list on the Display/Spatial panel.

Spatial data translator supported on Solaris ...

The PGC Spatial data translator now works on the Solaris platform. In previous versions, the option could crash when run on this platform.

The Display/Spatial panel freezed if the data source file did not exist at panel initialisation ...

In previous versions, Display Spatial dialog might hang if the selected data source did not exist or the user did not have read permission. It will now display an error message and allows the user to select another data source.

Thick lines drawn in X11 can render badly when zoomed in and lines are clipped ...

Certain types of long thick lines when drawn through X11 on the Linux and Solaris platforms could be drawn with the incorrect join style leading to ugly looking lines. These lines are now drawn more efficiently as well as correctly rendering the joins.

Mapping/Wells ... Enhancements

Well display improvements for 16.7 ...

The following improvements have been made to the display of well data in Mapping/Interactive and the 3D Viewer:

For more details on this functionality see help topic "DISPLAY WELLS".

Mapping/Wells ... Bug Fixes

Added check for no formations selected to Display/Wells/Geographix ...

Display/Wells for GeoGraphix now gives an error when OK or Apply is pressed when 'Display well tops' is turned on in the Tops tab and no formations have been selected. Previously, you could press OK and it would attempt to start drawing the wells, then give an error that you have not selected any formations and nothing would appear on the map.

Display of multiple GeoFrame well top layers overwrites tops selection ...

Display/Wells from GeoFrame no longer overwrites the formation selection from prior layers when more than one layer is displayed. Previously, if you had more than one Display/Wells layer for GeoFrame that posted selected tops on the map, then you went to Display/Modify for the first layer and pressed OK, the formation tops would disappear.

Display of well paths is no longer limited to 20000 points ...

Display/Wells now posts the full well path on the map for wells that have directional survey data with more than 20000 points.

Display/Wells/Geographix queried all wells in the database ...

When displaying wells from GeoGraphix on a map via Display/Wells, dbMap used to query all wells in the database. It now only queries wells within the current mapsheet boundary, which will improve the performance when displaying a sub-set of the wells from a database containing a large number of wells.

Duplicate Display/Well annotations no longer appear ...

Display/Wells/dbMap or another multi-connect data source could, if cancelled during the "Drawing wells" operation then redisplayed, result in well annotations being duplicated.

Picking wells no longer crashes when tracking coordinates is disabled ...

Picking a well that is displayed on a map with both 'Track latitude-longitude' and 'Track easting-northing' on the File/Preferences/Tracking dialog in interactive mapping turned off now correctly reports the name of the well and no longer crashes.

Robustness of well picking improved ...

Previous versions had problems with picking of wells (interactive selection on a map) in specific circumstances, including being able to select invisible wells, and not being able to select visible and valid wells.

Petrel plugin ... Enhancements

Petrel support for wells, polygons/lines and bin grids ...

The Petrosys plugin for Petrel has been extended to include the following functionality:

For more details on functionality available with the Petrosys plugin for Petrel see help topic "CONNECTING TO A PETREL PROJECT"

Petrel plugin ... Bug Fixes

Petrel fault import should not show input surfaces ...

File/Import/Petrel/Faults no longer shows "Input surface" grids in the list of items to select as they do not contain faults.

Surface modelling ... Enhancements

PGC window title displays Petrosys version ...

The Petrosys version number has been added to PGC window title. This is consistent with other applications within the Petrosys suite.

Surface modelling ... Bug Fixes

Incorrect syntax was generated when scripting PGC task fields to make them interactive ...

Incorrect syntax was generated when scripting PGC task fields to make them interactive. Prior to this fix, an extra dot was inserted, which had to be manually deleted by the user to make the script run correctly.

Null values for shapefile attributes are now ignored during surface modelling operations ...

Previously Petrosys treated null values in shapefile attributes as zero during surface modelling calculations. This could cause a distortion to the resultant grid. Null values are now ignored during surface modelling calculations, thus causing no distortion.

PGC handles an invalid geometry more gracefully ...

If a task file had an invalid geometry (such as a negative extent), running the task file previously caused the program to crash.

Surface Modelling/Contouring ... Bug Fixes

Contours produced using the "by cell" algorithm could have kinks at cell boundaries near faults ...

Contouring by cell has been improved to stop producing artificial kinks in the contours when moving between grid cells near to faults.

Surface Modelling/Grid Operations ... Enhancements

Speed improvement when opening a grid with a large number of faults or polygons ...

The performance of grid files containing many faults or polygons has been improved.

Support export and import of rotated grids to node dump format ...

The ASCII dump and load of Petrosys grid files now supports rotated grids.

Surface Modelling/Grid Operations ... Bug Fixes

Export of grids to ASCII XYZ file would sometimes fail to reimport correctly ...

An XYZ file exported from a grid could sometimes fail to reload. This was caused by the X and Y fields being adjacent in the output file, so the import function could not distinguish that they were two fields. This is now fixed.

Grid statistics no longer truncates precision of cell size ...

Lat-Lon grid cell sizes were displayed in grid statistics rounded down to 4 decimal places. This rounding has been removed, so users can better see the true cell size of their data.

Grid/Edit grid header truncates precision of grid origin for lat-lon grids ...

Running Grid/Edit grid header would truncate the precision of grid origins to 2 decimal places. When running with lat-lon grids, which have only 2 significant places before the decimal place, the rounding error was significant - amounting to a shift of ~50-100 metres depending on the CRS used.

Grid/Processes/Arithmetic using user-defined geometry now works ...

When running grid/processes/arithmetic using output geometry settings, the results obtained were incorrect. This has been fixed.

Petrosys node dump format now supports lat-lon grids ...

The Petrosys node-dump format has been improved to better support lat-lon grids. Prior to this change, when reading and writing ASCII grid data with small magnitude cell sizes, there was a loss of precision causing the grid data to be displayed incorrectly. Lat-lon grids typically measure cell sizes in degrees with very small values such as 0.0008333333. These small cell sizes were rounded incorrectly causing the grid to have an incorrect geometry.

Obsolete formats for export, such as "row-block" and "header-info" have also been removed from Petrosys.

Surface Modelling/Gridding ... Enhancements

Gridding from WDF and Petra wells zone 'Data' type to be named 'Attribute' ...

Zone type 'Data' has been renamed to 'Attribute' for gridding WDF and Petra wells

Surface Modelling/Gridding ... Bug Fixes

Grid header editor corrected to show grid origin fields as read-only ...

In the grid header editor, the coordinates of the origin are now read-only. Prior to this change, users could edit the values, but their changes were not saved.

Grid interpolation improved in faulted regions ...

Two interpolation problems when using Petrosys grid files containing faults have been addressed.

Grid interpolation was incorrectly showing values in cells with missing values ...

Grid interpolation was returning values in invalid regions of the grid. This has been corrected. Cells not intersected by faults or polygons now need to have four valid nodes when interpolating within them. This change reverts behaviour to how it was in version 15.5.

Grid/Create using grid data source used to leave grid file open (Windows platform only) ...

Grid/Create using grid data source was not closing the input grid file properly which meant that if the workflow was re-run, it would fail. This problem was indicated by an error message (ut:42) about problems copying the output temporary file to the output file because the file was already open.

Gridding of non-culture well data sources produced inconsistent resultant grid compared to gridding equivalent culture file point group ...

When gridding point data from well data sources other than a culture file, different results were obtained when gridding the equivalent data in a culture point group. This change affects the following data sources:

Z-values from SMT faults were used incorrectly in "Grid/Create grid" option ...

When gridding SMT data sources, the Z values were sometimes inadvertently used and there was no obvious means to control their use.

This fix changes the panel to add the following fields to the SMT fault selection in the "fault" tab of the Grid/Create grid panel:

It also has a "Missing value" field (which defaults to 0.0) to allow users to override the default missing Z value (0.0) for SMT faults as per the direct import option.

Surface Modelling/Kriging ... Enhancements

Performance and user interface improvements in kriging ...

The kriging package within Petrosys has been improved as below:

Web map server ... Enhancements

WMS server enhancements ...

Several minor improvements have been made to the WMS server:

Well data ... Enhancements

Ability to copy data from one WDF to another ...

It is now possible to copy selected data from one WDF to another. In the WDF editor (Mapping/Wells) the new option File/Import/Copy WDF has been added, which allows copying well header, directional survey, zone top/base depths and zone attribute values. Currently there is a limitation in that computed attributes are not copied to the new WDF.

You can also get to this option via File/Import/Wells on the main menu, selecting WDF as the data source.

Ability to merge well selection files and zone selection files for WDF ...

The WDF editor now supports merging well selection files and zone selection files. This allows you to build up a list of active wells or zones using multiple selection files.

Support for checkshot surveys added to Well Data File ...

In 16.7 there have been several features added to help with working with checkshot survey data and depth converting time grids. New functionality includes:

For more details on this functionality see the help topic "WELL DATA FILE - CHECKSHOT SURVEY" or contact Petrosys support.

WDF Import option "PI 297" renamed to "IHS 297" ...

The WDF import option "PI 297" has been renamed to "IHS 297" to reflect the fact that IHS purchased PI.

Well data ... Bug Fixes

Display/Wells from WDF - Removing a zone annotation posting item could cause a crash ...

On the "Zones + Data" tab of the WDF well display a crash could be triggered by removing an item from the "Items to be posted" list.

WDF computed attributes referring to attributes containing "_SS" in their name do not work correctly ...

If you had a computed WDF zone attribute which referred to an attribute with "_SS" in its name then it would incorrectly return a blank value when displayed or used in gridding instead of the computed value.

WDF Editor - Tree widget icons can change to much larger size when changing zone items (Windows only) ...

On Windows the icons in the tree widget would expand to a much larger size when changing the selection in the "Zone selection" list.

WDF import merge-keep behaviour not working correctly for some well header fields ...

When importing some well header fields (Depth datum, Depth datum type, KB elevation) using Merge-Keep the fields were incorrectly being replaced.

WDF import now loads text and date zone attributes correctly ...

Importing text or date data from ASCII files to WDF zone attributes could previously cause unrelated numeric values to be stored. Dates and text attributes are now stored correctly.

WDF merge behaviour has been improved for importing zone attribute data ...

When importing zone attribute data the behaviour of merge keep and replace was confusing. The behaviour is now:

rlnt1672Copyright (c) 2010 Petrosys Pty Ltd