OpenWorks Changes to Enforce Interpretation ID Permissions on Well Header
OpenWorks R5000.0.0.2 starts the well security model with enforcement of well interpretation ID permission, much like it does for well picks and other interpreted data. A user can modify or delete a well only if that user has access to the data source or interpretation ID assigned to the well. This feature was added to R5000 in response to common requests from clients. Its addition is critical to R5000 well management because wells are shared between interpretation projects, and users with appropriate permissions can delete a well while connected to any interpretation project. By design, this action removes the well from the project database as well as all associated interpretation projects. This new well security model allows clients to enforce a policy that restricts the update or deletion of wells to privileged users.
continue reading »
Tagged as:
Database,
OpenWorks,
Security
An interpretation project can be created using a user-defined geographical area of interest (AOI) as the means to select data from the underlying OpenWorks software project. Data falling inside the AOI are included in the interpretation project, but sometimes data falling outside the AOI are also included – so what’s going on?
continue reading »
Tagged as:
AOI,
Area of Interest
Horizon data management has changed for the R5000 software from previous releases. The following post discusses the new horizon attribute header and horizon data changes. An example of an R2003 project horizon upgrade to R5000 will illustrate the process of upgrading horizons and making decisions about the creation of interpretation projects (IPs). Some best practices for QC of your upgraded horizons is included. Landmark advises a thorough QC for each project upgrade.
There are two primary tables in the database involved in cataloging and managing horizon data in OpenWorks: horizon attribute header and horizon data.
Horizon attribute header is the top-level definition of a horizon. Each row in this table represents one horizon that can be defined on any number of 3D surveys or 2D lines in an OpenWorks software project.
For each 2D line or 3D survey where a given horizon attribute header is interpreted, a row in the horizon data table is created. For a horizon created on a 3D survey, this row contains the name of the external file with the horizon data. For a horizon created on a 2D line, this row contains the horizon data defined for that line. There is no external file for 2D horizon data in R5000 software version. continue reading »
Tagged as:
Database,
Horizons,
OpenWorks,
Oracle,
SQL
An interpretation project has two areas of interest (AOI) defined, a selection AOI and a data AOI.
When an interpretation project is created or modified, the user can specify an area of interest. This AOI is the selection AOI. This can either be set explicitly by :
- Entering the coordinates of a rectangle or polygon.
- Defining a polygon in a map view and PD it to Project Create or Modify.
- Computing an AOI based on the data specifically identified to include in the interpretation project in the data selection portion of Project Create or Modify.
The selection AOI is determines which reference data continue reading »
Tagged as:
AOI,
OpenWorks,
Project
Landmark received feedback from several customers regarding the 2003 datum shifting behavior. The behavior in R2003.X was technically incorrect. Datum shifts are designed to convert between coordinates in different datums, not between coordinates in the same datum. No conversion is required between two coordinates with the same datum.
An OpenWorks software geographic cartographic reference system (CRS) consists of both a datum and a datum shift to a standard reference datum, normally WGS 1984. Two different geographic CRS definitions can have the same datum and different datum shifts to WGS84. continue reading »
Tagged as:
CRS,
Datum,
OpenWorks,
R5000
