GIS integration enhancements

Learn how Petrosys continues to extend the integration of sub-surface knowledge with GIS systems and data formats.

Petrosys continues to provide the energy industry with practical technology that integrates surface and sub-surface knowledge. Here are a few of the latest updates.

New Spatial Data Translator 

Interoperability of the Petrosys map canvas and other spatial views has received a dramatic boost through the introduction of the ability to export much of what can be displayed on a Petrosys map - independent of source - to popular spatial formats including Google Earth KML and Arc shape files.

Above: Seismic lines, contours and well information has been exported to KML for browsing in an earth viewer.

In addition to exporting rendered map content to GIS formats, the Petrosys spatial data translator will help move well, seismic, contour, fault, polygon and culture files into Petrosys polygon/contour files and dbMap culture format.

Above: A user has clicked on a seismic line on the Petrosys map. This could be any displayed layer from any data source. Using the right mouse button this is being exported to a shapefile via the spatial data translator.

Oracle Spatial support improved

Petrosys dbMap sites can now spatially index their PPDM well, seismic and dbMap lease and culture information to provide seamless access to this information from dbMap, Oracle, Esri and other GIS views.

This allows very large volumes of regional PPDM seismic navigation and well location data to be displayed in a few seconds as a spatial layer, without losing the ability to query the resulting display in the full context of the structured PPDM seismic or well data model.

Additionally, spatial relationships can be incorporated into queries to select wells within leases or near collections of seismic lines, or to compute the length of seismic lines in leases. Spatially determined data selections can be extended to the selection of information from any linked data, thereby linking the value of corporate data stores and GIS information management.

The link between dbMap and Oracle Spatial in the /Display/Spatial option supports the re-use of existing dbMap annotation and filtering queries when displaying the linked Oracle Spatial data.

/Display/Spatial also supports the selection of the symbols to use when displaying point data from a property of the data itself. This allows, for example, correct well symbols to be drawn for each well based on a database field or query storing a symbol code.

dbMap PPDM 3.8 culture support enhanced

The Petrosys dbMap culture solution has been enhanced to provide clients with the following key benefits:

• Easy-to-administer, centralised, cultural data repository, with robust and sophisticated security;
• Complete integration with structured E&P industry data (eg Well + Seismic knowledge);
• PPDM 3.8 compliant; storing Points, Lines, and Polygons, separately - but all three are accessible in a single interface; and
• Intuitive interactive options (via the right mouse button popup menu) to query header screens and attributes plus run spatial analysis.

Display/spatial of ZGF data

The EP industry has a large base of spatial information recorded in ZGF files, which are widely used in Landmark applications. Petrosys v16.4+ adds ZGF files to those supported by the Display/Spatial functionality. This allows Petrosys users to access this information without learning new functionality; and ZGF owners to view their data in Petrosys without having to convert or import it.

Plot maps to ECW and JPEG 2000 image formats

ECW and JPEG 2000 format output drivers are available as options under /View/Plot, allowing any Petrosys map to be saved to these image formats, which support muti-resolution rapid image display. To use these new drivers, a new plotter configuration must be defined. An alternative TIF driver has also been added to /View/Plot to allow creation of TIF files using the GDAL library. The GDAL driver has more robust handling of uncommon Coordinate Reference Systems.