PetroView November 2017 release

The Release Notes document (found in the dataset directory, or through the PetroView Help menu) lists the functionality changes in more detail, but to summarise:

  • The Multiple Dataset Installer has been updated following changes to our website: please make sure that you have downloaded the latest version ( of this tool to continue using it.
  • New Select tools have been added for blocks, wells, facilities and pipelines. This adds to the Select fields tool introduced in May 2017. The dialog doesn’t need any use of SQL in order to screen and filter asset tables.
  • An Operator filter has been added to all Select tools.
  • Wells with estimated KB_RT values are highlighted in the map layer showing the location of well formation top records.
  • Unknown lithology values are shown in grey in the Snapshot tool.
  • The Snapshot tool partnership pie chart sorts partners by their percentage interest.

 In our dataset content, we have made some advances in coverage:

  • Global Seismic Catalogue coverage increased to six companies: CGG, EMGS, ION, PGS, Spectrum, TGS.
  • Well formation tops coverage increased to 63 countries.
  • Reservoir characteristics completeness improved across 12 countries this quarter.
  • Initial in-place reserves and recovery factors aligned with other WoodMac products as part of our data integration work.
  • We added a detailed coastline layer to the map which is visible at large scales instead of the original coastline layer, which has less detail. This means that two coastline layers are visible in the table of contents, but only one should remain visible at any one time. If both layers are visible, use the Options dialog to reset the start-up layers settings to their defaults. This will also reset any custom changes that you have made to the layers, so if you would like help merging the settings then please let us know.
  • PetroView now has over 1.2 million well formation tops!
  • Block naming conventions have also started to change in the November release, so that they align with other Wood Mackenzie products.

Block naming conventions

As part of the ongoing work to align the PetroView database with other Wood Mackenzie services, and in line with the data alignment schedule, the block naming conventions will be gradually changed in releases starting from the November 2017 dataset releases. As part of our ongoing data alignment work, PetroView will use the same block names and naming conventions as used in other Wood Mackenzie services.

The main differences in the block naming conventions are:

  1. Block names in other Wood Mackenzie services are generally presented in title case; PetroView block names are currently in upper case.
  2. "Leading zeroes" are not used when numbers are in block names; PetroView often adds a leading zero to single- and double-digit numbers.

Many PetroView tables, including the blocks table, contain a PETROVIEW_ID column. This is a numeric, unique identifier that can be used to match records in the event of a name change.

PetroView December dataset release: field shape changes

We have completed a large integration task which will be fully available in the December release and partially available in the November release. Over 12,750 field outlines have been updated to reflect those in other Wood Mackenzie tools: a big step forward in our ongoing product integration efforts.

PetroView February 2018 release

In our February release, we are aiming to:

  • Stop supporting ArcGIS Desktop version 10.1, in line with Esri’s deprecation schedule. PetroView will be supported on ArcGIS Desktop versions 10.2 to 10.5 inclusive.
  • Add a basin dashboard to the Snapshot tool showing key metrics at the basin level, with links to the Wood Mackenzie portal.
  • Add farm-in and work commitment filters to the block Select tool.
  • Further enhance well formation tops and reservoirs coverage by continuing our country-by-country review to add and expand our records.
  • Add a new “relinquished” block status to the blocks layer: allowing relinquished blocks to be identified in the map and the table.
  • Add a new “fiscal system” column in the Available Blocks layer.

Relinquished blocks

In order to help identify relinquished blocks in the database and map, we will be adding a relinquished status ("REL") to the STATUS column in the BLOCKS table.

Since the August release, relinquished blocks have been identified using "(Rel)" in the name. As this convention is no longer needed, it will be removed.

Relinquished blocks will no longer be merged into open blocks; their original "split" shape will be kept instead.

If you have any questions, please don’t hesitate to contact me directly.


Craig Foot
PetroView Product Manager