openworks project managementread.pudn.com/downloads272/sourcecode/math/1240848/... · openworks...
TRANSCRIPT
OpenWorksProject Management
© 2003 Landmark Graphics Corporation
Part No. 161611 R2003.12.0 October 2003
© 2003 Landmark Graphics CorporationAll Rights Reserved Worldwide
This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed,
stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of:
Landmark Graphics Corporation2101 CityWest Blvd., Bldg. 1, Suite 200
Houston, TX 77079, U.S.A.Phone: 713-839-2000
Fax: 713-839-2200Web: www.lgc.com
Trademark Notice3D Drill View, 3D Drill View KM, 3Dview, Active Field Surveillance, Active Reservoir Surveillance, ADC, ARIES,
Asset Development Center, Asset Development Centre, Automate, BLITZ, BLITZPAK, CasingSeat, CDDM, COMPASS, Corporate Data Archiver, Corporate Data Store, DataStar, DBPlot, Decision Suite, Decisionarium,
DecisionDesktop, DecisionSpace, DecisionSpace AssetPlanner, DecisionSpace AssetView, DecisionSpace Atomic Meshing, DecisionSpace Power Grid, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace
TracPlanner, DecisionSpace Well Seismic Fusion, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Express3, DepthTeam Extreme, DepthTeam Interpreter, DESKTOP-PVT, DESKTOP-VIP, DEX, DFW,
DIMS, Discovery, Drill-to-the-Earth Model, Drillability Suite, DrillModel, DrillVision, DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube, EDM, eLandmark, Engineer’s Data Model, Engineer's
Desktop, EOS-PAK, EPM, Executive Assistant, ezFault, ezSurface, ezTracker, FastTrack, FZAP!, GeoDataLoad, GeoGraphix (stylized), GeoGraphix Exploration System, GeoLink, GeoProbe, GES, GESXplorer, GMAplus,
GRIDGENR, Handheld Field Operator, I2 Enterprise, iDIMS, IsoMap, Landmark, Landmark and Design, Landmark logo and Design, LandScape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Magic Earth,
MagicDesk, MagicStation, MagicVision, Make Great Decisions, MathPack, MIRA, Model Builder, MultiWell, MyLandmark, MyWorkspace, OpenBooks, OpenExplorer, OpenJournal, OpenOrigin, OpenSGM, OpenVision,
OpenWells, OpenWire, OpenWorks, OpenWorks Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PowerCalculator, PowerExplorer, PowerJournal,
PowerModel, PowerSection, PowerView, PRIZM, PROFILE, ProMAGIC, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx, QUICKDIF, QUIKCDP, QUIKDIG, QUIKRAY,
QUIKSHOT, QUIKVSP, RAVE, RAYMAP, Real Freedom, Real-Time Asset Management Center, Real-Time Asset Management Centre, Real Time Knowledge Company, RESev, ResMap, RMS, SafeStart, SCAN, SeisCube, SeisMap,
SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks MultiView, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisWorks PowerView, SeisXchange, Sierra, Sierra (design),
SigmaView, SimResults, SIVA, Spatializer, SpecDecomp, StrataAmp, StrataMap, Stratamodel, StrataSim, StratWorks, StressCheck, STRUCT, Surf & Connect, SynTool, System Start for Servers, SystemStart, SystemStart for Clients, System Start for Servers, SystemStart for Storage, T2B, TDQ, Team Workspace, TeamView, TERAS, Total Drilling Performance, TOW/cs The Oilfield Workstation, Trend Form Gridding, Turbo Synthetics, VIP, VIP-COMP,
VIP-CORE, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Web OpenWorks, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellXchange, WOW, Xsection, Xsource, You're in Control. Experience the difference, ZAP!, and Z-MAP Plus are
trademarks, registered trademarks or service marks of Landmark Graphics Corporation or Magic Earth, Inc.All other trademarks are the property of their respective owners.
NoteThe information contained in this document is subject to change without notice and should not be construed as a
commitment by Landmark Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any error that may appear in this manual. Some states or jurisdictions do not allow disclaimer of expressed or implied
warranties in certain transactions; therefore, this statement may not apply to you.
Landmark OpenWorks Project Management
ContentsContents
Introduction
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
What’s in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Supplementary Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Platform Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
For SeisWorks Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Understanding Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
What is an OpenWorks Project? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Accessing OpenWorks Projects Over a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Using OpenWorks Project Data with Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
OpenWorks Database Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
OW_ADMINISTRATOR Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
How does it work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
What about the project password? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
What impact is there on pre-R2003.x users? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
What impact is there on existing applications? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
How do I get the project password by hand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
If I have to change the password, how do I store the new one? . . . . . . . . . . . . . . . . . . . 12
How are roles granted to users now? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
How do I clean up a project that failed to delete properly? . . . . . . . . . . . . . . . . . . . . . . . 13
Where is the OWSYS password? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Who is the user with partial DBA access who actually creates the projects? . . . . . . . . . 13
Do ORASTAT and Project Query still work the same? . . . . . . . . . . . . . . . . . . . . . . . . . 13
Where do I make someone an OW_ADMINISTRATOR? . . . . . . . . . . . . . . . . . . . . . . . 14
How are the individual table privileges granted to the roles? . . . . . . . . . . . . . . . . . . . . . 14
How do I change the list of tables that are accessible by the Limited Interpreter? . . . . . 14
Units Handling in OpenWorks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Measurement Systems Available in OpenWorks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
R2003.12.0 Contents iii
OpenWorks Project Management Landmark
Project Measurement Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Session Measurement Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Measurement Systems Set by Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Surface Distance Units Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Interpreters
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
What is an Interpreter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Launching Interpreters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Viewing the Interpreters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Adding or Changing an Interpreter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Modifying an Interpreter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Deleting an Interpreter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Setting the Current Interpreter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Map Projection Editor
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Other References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Introduction to Cartographic Reference Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Understanding the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
The CRS Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
What You Need To Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Putting It All Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
How OpenWorks uses Cartographic Reference Systems . . . . . . . . . . . . . . . . . . . . . . . . 48
iv Contents R2003.12.0
Landmark OpenWorks Project Management
Launching the Map Projection Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Map Projection Editor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Using the Map Projection Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Creating a Geographic CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Creating a Projection CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Creating New Datum Shifts for Geographic Coordinate Systems . . . . . . . . . . . . . . . . . 72
Saving a New CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Changing an Existing CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Deleting a CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Testing a CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Exiting Map Projection Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Datum Shifts and Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Shift Methods Used in Map Projection Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Predefined Datum Shifts in Map Projection Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Commonly Used Projection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Universal Transverse Mercator System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
State Plane Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Self-reference (stand-alone) System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Geographic Latitude/Longitude System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Projection Types in Map Projection Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Projection Type Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Cartographic Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Table 1: Supported Spheroids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Table 2: Supported Linear Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Table 3: Supported Angular Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Table 4: State Plane Coordinate System Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Table 5: Parameters of the State Plane Coordinate Systems (Excerpt) . . . . . . . . . . . . . 135
Table 6: Universal Transverse Mercator Longitude Zones . . . . . . . . . . . . . . . . . . . . . . 136
Test Conversion Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Understanding the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Defining the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
R2003.12.0 Contents v
OpenWorks Project Management Landmark
Performing the Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Map Projection Editor Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Measurement System Manager
Launching Measurement System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Creating a New Measurement System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Deleting Unused Measurement Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Converting Projects to Release 2003
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Determining if a Project Has Been Converted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Determining the History of a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Automatically Converting Single Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Command Line Script to Convert Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Project Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
System Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Converting Multiple Projects in Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Correcting Incomplete Project Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Vector Data Converter Utilities
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
vi Contents R2003.12.0
Landmark OpenWorks Project Management
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Project Administration
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Launching Project Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Modifying a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Deleting Projects Using a Command Line Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Backing Up OpenWorks Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Backing Up Using the Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Backing Up Projects Using a Command Line Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Restoring OpenWorks Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Users’ Access Preserved During Project Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Restoring Using the Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Restoring Using a Command Line Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Managing Project Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Managing User Access by Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Managing Project Access by User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Checking Tablespace and User Access in Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Tuning Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Project Change
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Effect of Changing Projects On Current Applications . . . . . . . . . . . . . . . . . . . . . . . . . 199
Effect of Changing Projects On Session Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
R2003.12.0 Contents vii
OpenWorks Project Management Landmark
Starting Project Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Project Create
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Questions to Answer Before Creating an OpenWorks Project . . . . . . . . . . . . . . . . . . . . . . 202
Loading Data Into a New OpenWorks Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Launching Project Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Creating OpenWorks Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Selecting the Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Selecting the Project Cartographic Reference System (CRS) . . . . . . . . . . . . . . . . . . . . 207
Selecting the Project Measurement System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Setting Default Display Parameters for the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Setting the Areal Extents of the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Specifying Project Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Creating Projects Using the Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Project Status Tool
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Launching Project Status Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Setting the Oracle Instance (OWSYSSID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Setting the OpenWorks Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Setting the Measurement System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Setting the Interpreter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Selecting a Well List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Selecting a Well . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
viii Contents R2003.12.0
Landmark OpenWorks Project Management
Setting the Well List Sort Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Setting the Time Depth Conversion Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Setting the Well Order in a Well List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Setting the Well Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Saving Settings to a Session File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Project Data Transfer
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
If You Have an OpenExplorer Advanced License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Transferring Data Across ORACLE Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Access Levels Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Types of Data Transferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Typical Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Starting Project Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Choosing the Source and Target Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Selecting Data for Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Basic Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Well Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Lease Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Field Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Basin Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Facility Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
2D Seismic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
3D Seismic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
SeisWorks Fault Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Stored Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Strat Column Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Interpretation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Line Of Section Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
R2003.12.0 Contents ix
OpenWorks Project Management Landmark
Well Template Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
List Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Well Planning Project Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Techniques for Selecting Multiple Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Using the Search/Filter String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Clearing All Data Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Wildcard Characters and Examples of Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Excluding or Renaming Interpreters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Advanced Filter Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Handling New Data Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Transferring Data By Update Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Transferring Data By Areal Extent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Global Transfer Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Overwrite Data In Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Validate Source Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Force Transfer on Conversion Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Rename Faults, Surfaces, and Strat Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Setting Up Transfer Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Transferring the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Running Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Creating a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Editing a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Running the Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Command Line Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Performance Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Data Transferred in Chunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
PDT Configuration File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Project Server for Workgroup Users
x Contents R2003.12.0
Landmark OpenWorks Project Management
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
What’s in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Accessing Remote Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Appendix: Limited Interpreters Tables . . . . . . . . . . . . . . . . . . . . . . . 407
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
R2003.12.0 Contents xi
OpenWorks Project Management Landmark
xii Contents R2003.12.0
Landmark OpenWorks Project Management
Introduction
Overview
OpenWorks projects store well, curve, fault, and seismic navigation data.You must select an OpenWorks project to use with most Landmark applications and utilities. Please read this chapter carefully before using any of the project functions.
What’s in this Manual
This manual describes the OpenWorks project management utilities and contains the following sections or chapters
• Understanding Projects on page 5 describes OpenWorks projects and how they are accessed and used.
• OpenWorks Database Security on page 7 describes how OpenWorks handles access to projects.
• Units Handling in OpenWorks on page 16 describes how OpenWorks handles project units and the options provided for loading, storing, displaying, and exporting all measurable quantities in OpenWorks projects. This section also describes how surface distance units are handled in OpenWorks.
• Interpreters on page 25 describes how to build and maintain a list of interpreters that OpenWorks applications use to track data.
• Map Projection Editor on page 37 describes how to define a frame of reference for your project data within the scope of its geographic coordinates.
• Measurement System Manager on page 151 explains how to create a customized measurement system based on a standard OpenWorks measurement system.
• Converting Projects to Release 2003 on page 159 explains how to convert Release 1998.x projects for use with Release 2003.x.
R2003.12 Introduction 1
OpenWorks Project Management Landmark
• Vector Data Converter Utilities on page 167 explains how to convert vector data in OpenWorks projects from the Oracle 7.3.4 binary representation to the new, more performant Large Object form supported in Oracle 8.1.6.
• Project Administration on page 173 explains how to modify, delete, backup, restore, tune, and query OpenWorks projects. This section also describes how to add or remove users from a project, and how to change user access to a project.
• Project Change on page 199 explains how to select another OpenWorks project.
• Project Create on page 201 explains how to create new OpenWorks projects.
• Project Data Transfer on page 233 explains how to transfer data from one OpenWorks project to another OpenWorks project.
• Project Status Tool on page 217 explains how to change the current database server, OpenWorks project, measurement system, interpreter, and wells (or well lists, including well list sort preferences, sort order, and format).
• Appendix: Limited Interpreters Tables on page 407 explains how to manage which interpretive data users with Limited Interpreter access to a project can create or edit.
Supplementary Documentation
The data management programs described in this manual run in Landmark's OpenWorks environment. Other documentation that contains information relevant to data management are:
• OpenWorks Release Notes. Refer to this document for installation instructions and descriptions of the operating environment.
• OpenWorks Data Management. Refer to this manual for descriptions of the OpenWorks data management utilities. Of particular use in data loading are the Curve Dictionary and Well Symbol Editor utilities. These utilities create editable lists of well curves and well symbols that pertain to a particular project. Another utility is Well Data Manager, which can be used to enter small amounts of data into a project. On UNIX installations of OpenWorks, this manual is in two volumes.
2 Introduction: Overview R2003.12
Landmark OpenWorks Project Management
• OpenWorks Data Import/Export. Refer to this manual for the OpenWorks data loading and export programs, such as ASCII Loader, Curve Loader, and Well Data Export.
On Windows, this manual is in two parts. Export utilities are shipped with OpenWorks and are documented in the OpenWorks Data Export manual. Import utilities are purchased separately and are documented in the and OpenWorks Data Import manual.
• OpenWorks Data Model. Refer to this source for a complete discussion of the relational data model used by OpenWorks products. The documentation for the data model is available in the OpenWorks Software Development Kit and is also available on Landmark Graphics Corporation’s web site (www.lgc.com) under the Solutions tab.
Platform Notes
OpenWorks Data Import and Export Utilities
OpenWorks UNIX installations: All of the data import and export utilities and their documentation are available in the version of OpenWorks installed on a UNIX workstation.
OpenWorks Windows installations: The data export utility, Well Data Export, and its documentation, are available in the version of OpenWorks installed on a Windows workstation. The data import utilities, ASCII Loader and Curve Loader, and their documentation, are available on a Windows workstation only if GeoDataLoad is purchased.
Accessing the OpenWorks Project Utilities
On UNIX systems, the OpenWorks project utilities discussed in this chapter are all available under the Project menu on the OpenWorks Command Menu.
R2003.12 Introduction: Overview 3
OpenWorks Project Management Landmark
On Windows systems, the OpenWorks project utilities discussed in this chapter are all available from the Start menu under Landmark OpenWorks > Project Administration.
For SeisWorks Users
The current working project referred to in this manual is the currently selected OpenWorks project, not a SeisWorks/2D working project.
The utilities for creating, maintaining, backing up, and restoring 2D and 3D seismic projects can be found on the Seismic Project Manager Command Menu, which is launched by selecting Data > Management > Seismic Project Manager from the OpenWorks Command Menu.
The Seismic Project Manager is described in detail in the Introduction to Seismic Project Manager manual, available via its Help > Online Manual menu option.
Menus differ between UNIX and Windows versions
In the Windows version of OpenWorks, OpenWorks does not have a Command Menu window, but has a program group and items in the Windows Start menu from which you can start its elements and applications.
SeisWorks and Seismic Project Manager are only on UNIX systems.
The Seismic Project Manager is only accessible from the OpenWorks Command Menu on UNIX installations.
4 Introduction: Overview R2003.12
Landmark OpenWorks Project Management
Understanding Projects
The following sections explain the concept of OpenWorks projects, and how they are used in Landmark applications.
What is an OpenWorks Project?
A project is any logical set of data to be used together on your system. The amount of data is limited only by the disk space available. In most cases, you want to work with only a small subset of the available data – for example, certain well logs in a particular field, reservoir data for particular horizons, or part of a seismic survey. Projects provide the key to accessing data that is of interest to you.
Any project may have a variety of geoscience data associated with it, such as wells and interpreters. When you are working on a project, by definition, you are using a certain set of wells, interpreters, and other data. For this reason, you may need to change projects from time to time if you want to start working with a different set of data. The OpenWorks project you are currently working with at any given time is called the current working project.
Accessing OpenWorks Projects Over a Network
A project is stored in the Oracle database that is installed with the OpenWorks software. Users with large networks may have multiple databases installed at various locations on the network. Each workstation containing an installed database is called a database server or instance. Each of these servers may have various client workstations that do not have their own installed databases, but which can access the server database through network communications (NFS).
If the database servers are linked through peer-to-peer communication, it should be possible for any authorized user working on any of the clients to create, view, or modify projects on any of the servers. For example, in the previous illustration, it should be possible for a user on a client of Server C to access projects on all three servers. If peer-to-peer communication has not been installed, the client workstations will
Server A
Server B
Server C
Client Client Client Client Client Client Client
peer peer
R2003.12 Introduction: Understanding Projects 5
OpenWorks Project Management Landmark
only be able to access projects on their immediate server. In this case, the client of Server C would only see the projects on Server C.
Various OpenWorks project management options let you control server access. For example, when you create a project, you can specify the server where you want to create the project. Project managers can also use the Project Administration option to control access of various users to specific projects.
Using OpenWorks Project Data with Applications
You can create as many projects as needed for the various sets of data you plan to study. Administering multiple projects is easy using the Project Administration utility described on page 173.
Import data into the project, as explained in the OpenWorks Data Import/Export (UNIX) or OpenWorks Data Import (Windows) manual. Data loading provides the project with the necessary and pertinent information about well log, seismic, and well completion data.
Once projects are set up, you can start running applications using the loaded data. You can run several applications at the same time, all accessing the data in the same project. If any application creates, deletes, or modifies the data, all of the other applications are immediately aware of the change.
6 Introduction: Understanding Projects R2003.12
Landmark OpenWorks Project Management
OpenWorks Database Security
Prior to Landmark’s Release 2003, OpenWorks historically had two different environments dealing with the security of the database components. The default environment utilized the OWSYSP tablespace, which contained a copy of the password to each OpenWorks project. The LMSYS user was granted full DBA privileges, and was used for creation, modification, and deletion of users, tablespaces, and roles amongst other things. In the Enhanced Security environment, the OWSYSP tablespace was dropped, and the end user either had to supply a login and password for a DBA account, or needed to be a DBA themselves. In theory, the two should have behaved quite similarly. However, in practice there was too great an amount of overhead for users in maintaining the Enhanced Security environment, especially for situations when the project password is needed, such as during OpenWorks upgrades and extensions, and during metadata changes for products such as OpenExplorer.
With very few exceptions, all OpenWorks applications connect as an externally identified Oracle user. That is, their Oracle permissions are determined by their operating system login. Most applications never access the passwords in OWSYSP or use the DBA abilities of LMSYS. The exceptions are:
• OpenWorks Project Administration which needs permission to perform database administration functions to create, delete, backup, and restore projects.
• OpenWorks Project Upgrade Utilities which need access to the project password to create and delete new schema objects.
• The OpenExplorer data management utilities which access Oracle directly in some cases through Oracle forms and other tools and does not go through the OpenWorks API.
OpenWorks 2003.x contains a single merged environment that provides the security of the Enhanced Security model with a minimum of noticeable change to the end users of the default environment. Greater flexibility is available in allowing privileged users the ability to perform project management functions without having access to full Oracle DBA abilities.
R2003.12 Introduction: OpenWorks Database Security 7
OpenWorks Project Management Landmark
OW_ADMINISTRATOR Role
At the heart of the model is a Oracle role named OW_ADMINSTRATOR. A user who is granted this role is able to create new projects, restore backed up projects, and modify projects for which they have also been given Manager status. OW_ADMINISTRATOR is not a DBA. The role is not granted on a project by project basis. It is instead granted at the entire database level. However, a user who does not have the current level of Manager in a project cannot perform any administration tasks upon that project (more on why this is so later). This new role slightly changes the definition of the current roles as follows:
• Browse: May view, but not create or edit or delete any data.
• Interpreter: May view any data, and may create data, and may edit and delete the users own data only.
• Limited Interpreter: As Interpreter above, but may only create/edit/delete data in a subset of tables normally used for interpretation. The end users administrator can alter the list of tables. In the past a file in the OS was used to retrieve the list of tables. This list is now stored in a table in the database (OW_ADMIN_UTILS.L_INTERP_MASTER).
• Manage: May view any data, and may create data, and may edit or delete any other users data. May perform project management functions only if the OW_ADMINISTRATOR role is also granted.
Thus, a user can be a Manager of a project and be allowed to manage the data content of the project without being given any database administration abilities over that project. This change provides an additional level of control over the project from either of the previous environments.
How does it work?
Oracle stored procedures run with the access rights of the user who owns the stored procedure rather than those of the user that executes the procedure. This allowed us to implement stored procedures that perform the specific database administration functions needed to administer OpenWorks projects. Users may be granted access to these specific procedures without being granted general DBA privileges.
In both of the pre-R2003 security models, a DBA account, either LMSYS or a user-supplied one, is used directly to perform all tasks
8 Introduction: OpenWorks Database Security R2003.12
Landmark OpenWorks Project Management
requiring DBA authority. Doing it in this manner, the password of the DBA account must be made available to OpenWorks in some fashion. In the new model, the user who has access to perform the necessary DBA functionality does not need to be directly accessed, so the password never needs to be used, and can be changed by the end user. A new user, OW_ADMIN_UTILS, has been created and only granted the subset of DBA privileges required by OpenWorks. These include:
• CREATE TABLESPACE• CREATE USER• CREATE ROLE• DROP TABLESPACE• DROP USER• DROP ROLE• ALTER TABLESPACE• Select capability on a subset of DBA tables
A set of stored procedures owned by the above user is used to perform each of the administration tasks required by OpenWorks. The OW_ADMINISTRATOR role is given execute permission upon these procedures. These procedures run at the privilege level of their owner, and thus can perform the above subset of DBA functions even though run by the OW_ADMINISTRATOR. However, the procedures themselves are hard coded to only allow the exact commands required by OpenWorks to be run. They also check to make sure that the tablespace acted upon is one that the OW_ADMINISTRATOR in question is a Manager of. This will stop, for example, a user with OW_ADMINISTRATOR from being able to delete projects other than those they have been given Manage control over.
This model allows users to be trusted with necessary DBA functions (such as backing up, being able to add space to a project, etc.) upon a subset of projects without giving them DBA abilities upon the entire database. If a user with OW_ADMINISTRATOR tries to use a stored procedure to affect an OpenWorks project (or any other tablespace or user) which they are not a Manager of, the stored procedure will refuse to run. A user who is not an OW_ADMINISTRATOR does not have permission to run the stored procedures. Since at no time is the owner of the stored procedures needed to be logged in, the password may be changed as desired by the end user, keeping the only login with any DBA privileges secure.
As a further level of security, the stored procedures themselves are wrapped up in a package that allows a bare minimum of the DBA work to be made public. For example, creating a project requires creating a user, a tablespace, and a set of roles. A user with
R2003.12 Introduction: OpenWorks Database Security 9
OpenWorks Project Management Landmark
OW_ADMINISTRATOR is not able to perform any of these tasks individually. The user is only able to call a single public procedure from the package that does everything necessary to create an OpenWorks project.
What about the project password?
At times, such as during project extension or upgrade, the projects password is required. This is because in order to create schema objects such as tables, indexes, etc., the objects must be created by the project in question. In the pre-R2003.x model, the password is stored in OWSYSP. In the R2003.x model, the password is encrypted and stored within a table in the project itself. Only the project login has access to view this table. Even those with Manage access in the project do not have SELECT ability upon this new table. In a similar manner as to how the DBA functionality is being protected, a stored procedure within the project is the only way for the project password to be retrieved and decrypted. This stored procedure can only be run by having those who have granted both the OW_ADMINISTRATOR and the Manage role for that project.
What impact is there on pre-R2003.x users?
Pre-R2003.x users may be impacted in two ways. First, the method of allowing any user to extend a project in a new version of OpenWorks has changed. Instead, only a Manager who is also an OW_ADMINISTRATOR can extend or upgrade the project. This is necessary as only the Manager can retrieve the project password, and is a beneficial change from a security viewpoint.
The second thing that may impact existing users has to do with how backups and restores have traditionally been done. In the past, the Oracle exports were done using a DBA account. Because of this, only a DBA may import those backup files. There will have to be a transition period where a DBA account is available to do the import of backups from 1998.9 and previous versions of OpenWorks. Future backups and restores will be done as the project user. The implementation has been done so as to keep this as transparent to the end user as possible. OpenWorks Project Restore checks to see if the backed up project requires a DBA to be restored. If it does, LMSYS will attempt to be used. If LMSYS is not available or is not a DBA, then the current user will be tried, making it analogous to how the old enhanced security model worked. If the current user is not a DBA, the user can be prompted to supply the name and password of a DBA account.
10 Introduction: OpenWorks Database Security R2003.12
Landmark OpenWorks Project Management
Due to this, LMSYS will be retained by default, and will be a DBA. The password to LMSYS will be changed to something only the compiled applications will know. This password will not be stored anywhere. LMSYS can still be dropped, in which case the end user will have to be a DBA or supply a DBA login and password for a pre-2003.0 backup file to be restored.
The need for the DBA account will be completely phased out when all backups have come from a version of OpenWorks that no longer backs up as a DBA. Implementation should allow this issue to be completely transparent to any user users of the default environment, and at worst, appearing as little change to users of the Enhanced Security environment.
One additional note on impact is that users who are not as concerned about security can grant the OW_ADMINISTRATOR role to all users. Doing so would be analogous to the old default environment, while still providing a higher level of security by allowing fewer DBA functions to be performed, and never on a project which the user does not manage.
What impact is there on existing applications?
Applications connecting to OpenWorks using the OpenWorks API’s to read and write data should see no differences. They connect as the external user just as they always have and do not need access to database passwords or database administration functions. Applications connecting to Oracle directly without going through the OpenWorks Development Kit could be affected. Applications cannot count on logging in by using <project name>/<project password>, and should log on as the external user.
The normal connection sequence to OpenWorks in SQL is as follows:
connect /@<sid>alter session set current_schema=<project_name>;set role <security_level>_<project_name;
R2003.12 Introduction: OpenWorks Database Security 11
OpenWorks Project Management Landmark
How do I get the project password by hand?
In order to retrieve the project password by hand, a user (who is an OW_ADMINISTRATOR and a Manager of the project) would do the following, where projectname is replaced with the name of the OpenWorks project:
sqlplus /@$ORACLE_SID alter session set current_schema = ‘projectname’;set role ow_administrator;set role manage_projectname; select ow_prj_utils_pkg.ow_get_password( PROJECTNAME )from dual;
Note that this last command may sometimes take awhile to complete. It utilizes Java stored procedures, and if the Java VM is not already running in Oracle, it may take longer than one would expect as the virtual machine is started up.
If I have to change the password, how do I store the new one?
A new password cannot be put in the table via a normal insert, as it must first be encrypted. The following steps could be used to change a project login’s password and store the new password. In this case, TESTDATA is the project and newpassword is the password, on database sid.
While logged in as a DBA:
alter user testdata identified by newpassword;
connect testdata/newpassword@sidname delete from ow_prj_security;commit; execute ow_prj_utils_pkg.ow_store_password( TESTDATA, newpassword);commit;
Note that this last command may sometimes take awhile to complete. It utilizes Java stored procedures, and if the Java VM is not already running in Oracle, it may take longer than one would expect as the virtual machine is started up.
12 Introduction: OpenWorks Database Security R2003.12
Landmark OpenWorks Project Management
How are roles granted to users now?
Prior to R2003, the Manager of a project was granted all 4 roles with admin option. When a new user was added to the project, the manager was logged in to sqlplus as /, and was used to grant the appropriate roles to the new user.
In the R2003 model, the Manager only has the Manage role granted. The project login owns the four roles and is actually used to grant the roles to the new user.
All of this is transparent to the end user, who still uses Project Admin’s User Manager.
How do I clean up a project that failed to delete properly?
The existing project deletion scripts still work when run as a DBA, just as in the past. The only difference is that the LMSYS password is not available, so another DBA account such as SYS or SYSTEM should be used.
Where is the OWSYS password?
At present, the password to OWSYS is still kept within OWSYSP. It is the only password left in that tablespace. In a future release, the password will be moved into the OWSYS tablespace in a manner similar to that used for the projects. It was not moved in 2003.0 due to the impact to existing applications. The access to the OWSYS password does not give a user access to project data, so does not harm the security of the project data. When the OWSYS password is completely removed from OWSYSP, the OWSYS tables will still need to be viewable by all users.
Who is the user with partial DBA access who actually creates the projects?
OW_ADMIN_UTILS is granted partial DBA access. Users are not allowed to log in as OW_ADMIN_UTILS, the password is not given out or stored anywhere, and the end user will be able to (and encouraged to) change the password.
Do ORASTAT and Project Query still work the same?
For the most part. Orastat will only show the information about the datafiles if you are an OW_ADMINISTRATOR. If you are not, it will
R2003.12 Introduction: OpenWorks Database Security 13
OpenWorks Project Management Landmark
tell you that you are not, and so that information has been omitted. It no longer lists all project passwords. If you need a project password, you must be an OW_ADMINISTRATOR and a Manager of the project and use the sql statements already provided to obtain it.
Project Query can be run on any project, with or without OW_ADMINISTRATOR privileges. It provides information that may be useful to any user in it, such as a list of users who can access the project so a user will know who to speak to for access to the data.
Where do I make someone an OW_ADMINISTRATOR?
The orauser utility will grant OW_ADMINISTRATOR by default to a newly created user. Options have been added to orauser grant or revoke the OW_ADMINISTRATOR role.
How are the individual table privileges granted to the roles?
A stored procedure within the project grants permissions on each table and stored procedure to the four OpenWorks defined roles. It is fired off as part of a project creation, but may be run by hand to sync up the roles if hand edits have been done to a project. The command to do this by hand is:
sqlplus /@$ORACLE_SID alter session set current_schema = projectname;set role ow_administrator;set role manage_projectname; execute ow_prj_utils_pkg.ow_grant_role_privs( PROJECTNAME);
How do I change the list of tables that are accessible by the Limited Interpreter?
The list of tables accessible by the Limited Interpreter is kept in a table in OW_ADMIN_UTILS. The table is named L_INTERP_MASTER. Any user may view the list of tables, but only a DBA can change the list. The easiest way to change the list is to go into the runtime install to $OWHOME/dat/ow_admin_utils/l_inter_master.ctl.
Edit the list of tables in the bottom portion of the file. Then change the OW_ADMIN_UTILS password to something that you will know, and then load the file in sqlldr:
sqlplus sys/change_on_install@$ORACLE_SID
14 Introduction: OpenWorks Database Security R2003.12
Landmark OpenWorks Project Management
alter user ow_admin_utils identified by newpassword; exit; (from the command line again) cd $OWHOME/dat/ow_admin_utils
$ORACLE_HOME/bin/sqlldr ow_admin_utils/newpassword@$ORACLE_SID control=l_interp_master.ctl
R2003.12 Introduction: OpenWorks Database Security 15
OpenWorks Project Management Landmark
Units Handling in OpenWorks
In OpenWorks 1998 and subsequent versions, units handling was expanded to incorporate the concept of measurement systems. A measurement system provides a preferred unit for each type of measurement that can be handled in OpenWorks. This ensures that all data is handled consistently by OpenWorks applications.
This section describes the measurement systems available in OpenWorks and describes the options provided for storing, displaying, loading, and exporting measurable quantities of data.
• Project Measurement Systems (page 18) provide default units of measure handling for all measurable quantities stored in an OpenWorks project.
• Session Measurement Systems (page 19) provide default units of measure handling for all measurable quantities displayed and loaded during an OpenWorks session.
• Measurement Systems Set by Applications (page 21) are used to display, load, and export well data using units of measure that are different than those specified by the project and session.
In addition, the following topic is also discussed in this section
• Surface Distance Units Handling (page 22) describes how OpenWorks determines and stores surface distance units.
Measurement Systems Available in OpenWorks
The following measurement systems are provided with OpenWorks
• U.S. Oil Field• U.S. Oil Field (metric depth)• SPE Preferred Metric• Canadian Metric.
These are described in detail beginning on the next page. All four of these measurement systems are available for project, session, display, data loading, and data export purposes.
You may create new measurement systems based on these four measurement systems. Refer to the Measurement System Manager (page 151) chapter of this manual for complete details.
16 Introduction: Units Handling in OpenWorks R2003.12
Landmark OpenWorks Project Management
U.S. Oil Field
U.S. Oil Field is predominately U.S. English units with metric units for some log curve and engineering data, and with feet units for depths. The units are designed to correspond to those used by U.S. oil companies.
The U.S. Oil Field measurement system corresponds to the English measurement system in pre-Release 1998 versions of OpenWorks.
U.S. Oil Field Metric Depth
U.S. Oil Field Metric Depth is the same as U.S. Oil Field for all units except depths, which are in meters. This measurement system is intended for U.S. oil companies operating internationally.
U.S. Oil Field Metric Depth mirrors U.S. Oil Field, except
• depth measure is meters• length borehole is meters• elevation is meters
SPE Preferred Metric
SPE Preferred Metric represents the common metric units used in the oil field (the metric units also describe depth measurements). It is based on the publication “The SI Metric System of Units and SPE Metric Standard” from the Society of Petroleum Engineers.
SPE Preferred Metric corresponds to the Metric measurement system in pre-Release 1998 versions of OpenWorks.
Canadian Metric
Canadian Metric mirrors SPE Preferred Metric, except
• density hydrocarbon liquid is kg/m3 (not g/cm3)• density liquid is kg/m3 (not g/cm3)• density solid is kg/m3 (not g/cm3)• viscosity dynamic is Pa.s (not cP)
R2003.12 Introduction: Units Handling in OpenWorks 17
OpenWorks Project Management Landmark
Project Measurement Systems
A project measurement system provides default units of measure handling for all measurable quantities stored in a project.
You select a preferred storage unit for all measured quantities when you create a new OpenWorks project. The project measurement system cannot be changed, so it should be the most accurate measurement system for the project as a whole.
For information about how to select a measurement system when you create a project, refer to the Project Create (page 201) chapter of this manual.
Adjusting Unit Information in an OpenWorks Project
Two OpenWorks data management utilities are available to adjust unit information in an OpenWorks project.
• The General Units Converter allows project managers to see every unique combination of table name, column name, and original unit of measure (OUOM), as well as the expected database unit for each table name and column name, in an OpenWorks project.
• The Special Units Editor allows project managers to edit the unit types (what is being measured—for example, porosity, electric potential, and gamma count rate) and unit abbreviations (how it is being measured—for example, meters, MCF, and millidarcies) of certain types of data that are not automatically converted to the measurement system used by an OpenWorks project.
Refer to the OpenWorks Data Management manual for complete details regarding these utilities.
18 Introduction: Units Handling in OpenWorks R2003.12
Landmark OpenWorks Project Management
Session Measurement Systems
Even though you cannot change a project’s measurement system, you can change how OpenWorks displays and loads measurable quantities by specifying a session measurement system. A session measurement system provides default units of measure handling for all measurable quantities displayed and most measurable quantities loaded and exported during an OpenWorks session, so it should be the most accurate measurement system for the data you will be working with during a session. It can be the same as the project measurement system, or it can be different.
Once set, the session measurement system is the default used by all applications that you subsequently start during an OpenWorks session.
You set the session measurement system using Project Status Tool or by selecting a measurement system when you start many OpenWorks applications.
Setting the Session Measurement System Using Project Status Tool
Project Status Tool allows you to set the session measurement system before you start any OpenWorks applications and to change the session measurement system during a session.
For example, if you set the session measurement system using Project Status Tool and you then start Curve Dictionary, Curve Dictionary opens with the session measurement system as its default.
If you subsequently start Well Curve Viewer, Well Curve Viewer will use the session measurement system you set in Project Status Tool.
The session measurement system you set in Project Status Tool before you start the first Open-Works application…
…is then used by all applications that you subsequently start
R2003.12 Introduction: Units Handling in OpenWorks 19
OpenWorks Project Management Landmark
If you change the session measurement system during a session, the following will occur:
• Applications that you subsequently start will use the “new” session measurement system.
• Any measurement system-based data management applications (for example, Curve Dictionary and Well Data Manager) that were running before you changed the measurement system will be notified of the change and will use the new session measurement system.
• Measurement system-based data import and export applications (ASCII Loader and Well Data Export) that were running before you changed the measurement system will retain the previous session measurement system; they will, in effect, override the session measurement system.
• Applications that are not measurement system-based (for example, Curve Loader and Well List Manager) will not be affected at all.
For more information about using Project Status Tool to change the session measurement system, refer to “Setting the Measurement System” on page 221 of the Project Status chapter of this manual.
Setting the Session Measurement System When Applications are Started
If the session measurement system is not set, the first measurement system-based application that you start will prompt you to set the session measurement system.
Each application that you subsequently start during the session will use this measurement system.
For example, if the session measurement system is not set and you start Curve Dictionary, Curve Dictionary will prompt you to set the session measurement system.
If you subsequently start Well Curve Viewer, it will open using the session measurement system that you set when you started Curve Dictionary.
Setting the session measurement system when you start applications is discussed in the “Opening the Application” section of each application’s online documentation.
20 Introduction: Units Handling in OpenWorks R2003.12
Landmark OpenWorks Project Management
Measurement Systems Set by Applications
Three OpenWorks applications, Well Data Manager, ASCII Loader, and Well Data Export, allow you to override the session measurement system without redefining it for the session and without affecting any other applications.
Well Data Manager lets you display values using a measurement system other than the session measurement system. For example, if your session measurement system is S.P.E. Preferred Metric, but you want to view well depths using U. S. Oil Field, you simply set the Well Data Manager’s “View” measurement system to U. S. Oil Field. No other applications are affected by this setting in Well Data Manager. (For more information, refer to the Well Data Manager chapter in OpenWorks Data Management.)
ASCII Loader and Well Data Export allow you to load and export data using a measurement system other than those specified by the project and session. Refer to the “Units Handling” sections of these chapters in the Open Works Data Import/Export manual.
A note about original and storage units when loading data…
For data management purposes, the original units of the data as loaded is stored in fields with a _OUOM (Original Units Of Measure) suffix. If there is any question as to whether the correct conversions have been performed, you can compare the original units in the _OUOM field with the project storage units.
The session measurement systemcan be overridden using the View option in Well Data Manager.
R2003.12 Introduction: Units Handling in OpenWorks 21
OpenWorks Project Management Landmark
Surface Distance Units Handling
In OpenWorks, surface (linear) distance units are defined by the project cartographic reference system (CRS).
These surface distance units represent “cartographic distances” that are closely related to x, y coordinates. Units that are tightly tied to project x, y values, such as position log offsets, are stored using the surface distance units defined by the project CRS; they are not converted to the project measurement system.
In addition, these units are displayed using the surface distance units defined by the project CRS, not those defined by the session measurement system.
The table below lists surface distances that are stored and displayed using the surface distance units as defined by the project CRS.
Other surface distances (for example, seismic facility spacings and line lengths) are more descriptive in nature and are stored according to the project measurement system. These units convert between feet and meters and between miles and kilometers for displays using the units defined by the session measurement system.
Surface distances stored and displayed using the project CRS surface distance units
Table Description Table Name Column Name(s)
Description of a point in a directional survey dir_survey_pt x_offset, y_offset
Descriptive information pertaining to a fault. fault fault_heave_max
Header information defining an irregular geometric shape for a well target.
irregular_geometry offset_x, offset_y
Location of an individual conductor or slot on a plat-form.
platform_slot x_offset y_offset
Summary information about a wellbore geometry trace.
positional_log_hdr bottom_hole_x_off bottom_hole_y_off
Defines a regular geometric shape for a particular well target.
regular_geometry offset_x, offset_yorientation_radius perpendicular_radius
Information about a fault observed at a well bore-hole.
well_fault_obsv fault_obsv_heave
Cross-section view of a baseline. x_sec corridor_width
Free-form annotation for a cross-section. x_sec_polygon x_sec_poly_distance
A well belonging to a cross-section. x_sec_well_list x_sec_distance
22 Introduction: Units Handling in OpenWorks R2003.12
Landmark OpenWorks Project Management
The table below lists surface distances that are stored and displayed using the units defined by the project CRS and converted to the project and session measurement system.
Surface distances converted to the project and session measurement system
Table Description Table Name Column Name(s) Conversion
Summarizes the methods and costs planned to explore an opportunity.
exploration_program total_dist_2d_seismic miles/km
Describes and legally identifies a producing field or prospect.
field_prospect distance_fm_shorepipeline_distancefacility_distance
miles/kmmiles/kmmiles/km
Reference to data used as input to prospect evaluation.
property_reference_data distance_to_prospect miles/km
Evaluation and description of reservoir characteristics performed during prospect appraisal.
prospect_reservoir_eval distance_to_outcropdiscovery_dist
miles/kmmiles/km
Equipment used during seismic acquisition.
seismic_fcl element_spacingsection_lengthstreamer_lengthvib_moveup_dist
ft/mft/mft/mft/m
The geometry associated with a seismic acquisition.
seis_geom_nml surface_lengthdownline_far_ofstdownline_near_ofstupline_far_offsetupline_near_offsetoffset_maximumoffset_minimumrcv_ln_nom_spcrcv_pt_nom_spcsource_ln_nom_spcsource_pt_nom_spc
ft/mft/mft/mft/mft/mft/mft/mft/mft/mft/mft/m
Qualitative source rock description made during prospect evaluation.
source_rock_evaluation migration_distance miles/km
Mapping of seismic travel time to vertical depth in the wellbore.
time_depth_curve source_offset ft/m
List of wells that prove the effective-ness of reservoir formation.
well_proving_reservoir distance_to_prospect miles/km
List of wells that prove the effective-ness of a source rock formation.
well_proving_source distance_to_prospect miles/km
List of wells that prove the effective-ness of a trap.
well_proving_trap distance_to_prospect miles/km
R2003.12 Introduction: Units Handling in OpenWorks 23
OpenWorks Project Management Landmark
24 Introduction: Units Handling in OpenWorks R2003.12
Landmark OpenWorks Project Management
Interpreters
Overview
The Interpreters utility allows you to build and maintain a list of interpreters that OpenWorks applications use to keep track of data. Items in this list are most frequently interpreter’s initials, but they can also indicate the source of the data or some other meaningful designation. Using the Interpreters utility, you can reset the interpreter without exiting OpenWorks. You can also add new interpreters to the current project and modify or delete existing ones.
What’s in this Chapter
This chapter describes the Interpreters utility and covers the following topics:
• What is an Interpreter? on page 26 describes how OpenWorks and other Landmark software use the interpreter designation to track ownership of imported and interpreted data.
• Launching Interpreters on page 27 explains how to access the Interpreters utility, the layout of the utility’s main window, and the pulldown menus in the main menu bar.
• Viewing the Interpreters on page 30 explains how to view the interpreters for a project.
• Adding or Changing an Interpreter on page 31 explains how to create a new interpreter to the project or change an existing interpreter’s initials.
• Setting the Current Interpreter on page 34 explains how to set an interpreter to be the one currently working on the project.
R2003.12.0 Interpreters 25
OpenWorks Project Management Landmark
What is an Interpreter?
Any time you start any interpretation application, it requests an interpreter if one has not already been provided. This designation is necessary because each well top/pick or line event added to the database during data loading or interpretation is tagged with an interpreter. This tagging has three advantages:
• It permits the same events to be picked by different interpreters and to be managed separately if desired.
• It allows you to experiment with different interpretations, tagging each interpretation with a different interpreter.
• It allows you to tag data loaded from outside the system.
An interpreter definition is “owned” by a particular system user, usually the user who created the interpreter, and only people using this login can perform interpretations as that interpreter. However, you can designate interpreters as public to allow interpretations to be performed by more than one individual. Any system user can then log in and use the public interpreter. For example, if the system user oe1 creates three interpreters and designates one of these as public, anyone who logs in, regardless of the login account they used, can use the public interpreter created by oe1 (but not the other two interpreters created by oe1).
Because this allows several people to work on the same interpretation, you could, for example, have a project containing data for a large field divided into small regional areas, with a different person working on each area but with all working on a common interpretation.
The current interpreter remains in effect until it is changed. This means that you do not have to enter it every time you start a new application. However, it also means that you must log out if a another user with a different login takes over a shared workstation, and the new user must log in.
When you change the interpreter, you must start the application again for the change to take effect, because you can have multiple instances of the same applications open at the same time, using different interpreters.
You use the Project Admin utility to assign various levels of project access to interpreters (see “Managing Project Access” on page 191 of the Project Administration chapter in this volume).
26 Interpreters: What is an Interpreter? R2003.12.0
Landmark OpenWorks Project Management
Launching Interpreters
To run this utility, you must log on as an OpenWorks user who:
• is an External Oracle user with the OW_ADMINISTRATOR role in the Oracle database, and
• has been granted MANAGE access to the OpenWorks project
Use the following steps to launch the Interpreters utility:
• UNIX—From the OpenWorks Command Menu, select Project > Interpreters.
• Windows—From the Start menu, select Programs > Landmark OpenWorks > Project Administration > Interpreters.
Depending on which session parameters were set before you launched Interpreters, the system may prompt you to set the following parameter:
• project. This will also set the project for the OpenWorks session.
Make a selection from the dialog box that automatically appears. (This parameter is discussed in detail in the Project Status chapter of this manual.) After this parameter is set, the Interpreters window opens.
R2003.12.0 Interpreters: Launching Interpreters 27
OpenWorks Project Management Landmark
Window Layout
The Interpreters window contains the following areas.
• The menu bar contains pulldown menus to enter new interpreters and to change the contents of the Interpreters list.
• The interpreter information fields show details about a selected or new interpreter.
• The interpreters list displays all the interpreters in the current project or all the interpreters created by the current user.
• The buttons allow you to perform Interpreters tasks such as adding, modifying, and deleting interpreters, and setting the interpreter for the current session.
To exit Interpreters, select File > Exit.
Menu Bar
Interpreter Information fields
Buttons
Interpreters list
28 Interpreters: Launching Interpreters R2003.12.0
Landmark OpenWorks Project Management
Menus
Interpreters contains the following menus:
• The File menu allows you to enter a new interpreter or exit Interpreters.
• The View menu allows you to see all the interpreters in the current project or all the interpreters created by the current user.
• The Help menu allows you to view the online documentation for this utility.
Fields
The Interpreters window has the following fields:
• Current Interpreter shows the current ID for the session.
• Interpreter displays the interpreter you select from the list at right.
• Name shows the name associated with the interpreter ID.
• Description is a meaningful description associated with the interpreter ID.
• Owner shows the user account that owns the interpreter ID.
• Depending on the View option selected, the interpreters list displays all the interpreters in the current project or all the interpreters created by the current user.
Buttons
Use the four buttons at the bottom of the Interpreters window to add, modify, and delete interpreters, and to select an interpreter for the current session.
R2003.12.0 Interpreters: Launching Interpreters 29
OpenWorks Project Management Landmark
Viewing the Interpreters
You can view interpreters by user and by project.
• Select View > User to see only the interpreters that you created.
• Select View > Project to list all interpreters created by all project users.
The title of the Interpreters list reflects the view mode you select. If you choose the user view mode, the title is User Interpreters, as shown in the example below. If you choose the project view mode, the title is Project Interpreters.
30 Interpreters: Viewing the Interpreters R2003.12.0
Landmark OpenWorks Project Management
Adding or Changing an Interpreter
Use the Add and Modify buttons to add or modify an interpreter. When you create interpreters, they will be owned by you; that is, the owner will be your user login ID.
To add an interpreter
1. Select File > New.
2. Type the initials in the Interpreter text box. The initials must be unique within the project, and must be five characters or less.
3. Type the name in the Name text box.
4. Type a description of the interpreter or interpretation in the Description text box. This step is optional.
5. By default, the owner of the interpreter is you. To define this interpreter as a public interpreter (and so allow any system user to create interpretations using this interpreter ID), click on the List button next to the Owner field. The Owner Selection dialog box opens. Select PUBLIC and click on OK. The Owner definition changes to PUBLIC.
6. Click on Add. The new interpreter is added to the Interpreters list:
Use the Project Admin utility to set the interpreter’s level of access (browse, interpret, limited interpret, or manage) to the project. See “Managing Project Access” on page 191.
R2003.12.0 Interpreters: Adding or Changing an Interpreter 31
OpenWorks Project Management Landmark
Modifying an Interpreter
To modify an interpreter that you own
1. Select the interpreter that you want to modify from either the User Interpreters or the Project Interpreters list. View > User.
The information about the interpreter appears in the window:
2. Add or change the appropriate information.
3. Click on Modify.
The change is recorded in the current project.
32 Interpreters: Adding or Changing an Interpreter R2003.12.0
Landmark OpenWorks Project Management
Deleting an Interpreter
You cannot delete either the current interpreter or an interpreter that belongs to someone else. If you try to do so, you will receive an error message.
To delete an interpreter that you created
1. Select View > User.
2. Select the interpreter from the Interpreters list.
3. Click on Delete. A confirmation window opens.
4. Click OK. The interpreter is deleted from the User Interpreters list.
R2003.12.0 Interpreters: Adding or Changing an Interpreter 33
OpenWorks Project Management Landmark
Setting the Current Interpreter
You can set or change interpreters for the current session from within the Interpreters utility; however, you can only select an interpreter that you own or a public interpreter.
To set another interpreter as the current interpreter for the session:
1. Select an interpreter from the Project Interpreters list.
2. Click on Set. The interpreter appears as the current interpreter in the Interpreters window:
You can also use the Project Status Tool to set the interpreter for the current session (see “Setting the Interpreter” on page 222 of the “Project Status” chapter in this volume). The following example shows how the Interpreters and the Project Change utilities work together.
Changing Interpreters While Loading Data
If the interpreter is reset while the data loading utilities are running, the “new” interpreter will not be loaded as the Data Source. Landmark recommends selecting the “new” interpreter and restarting the data loading utility.
34 Interpreters: Setting the Current Interpreter R2003.12.0
Landmark OpenWorks Project Management
In the example, users OE1 and OE1L1 selected the same project, then each opened Interpreters.
Both users see all of the interpreters for the project, regardless of who created them. However, each user can modify only the interpreters they created.
When both users open Project Status to change interpreters, they see only their own interpreters and the public interpret-ers for the project; they do not see all of the interpreters in the project as they did in the Interpreters utility.
R2003.12.0 Interpreters: Setting the Current Interpreter 35
OpenWorks Project Management Landmark
36 Interpreters: Setting the Current Interpreter R2003.12.0
Landmark OpenWorks Project Management
Map Projection Editor
Overview
The Map Projection Editor utility allows you to define a frame of reference for your OpenWorks project data within the scope of its geographic coordinates.
Map Projection Editor incorporates third-party software licensed from Blue Marble™ Geographics. The Blue Marble software calculates datum shifts to convert between geographic systems with difference reference datums and also calculates map projections to convert between geographic coordinate systems and grid coordinate systems.
What’s in this Chapter
This chapter contains the following sections:
• Introduction to Cartographic Reference Systems on page 38
• Launching the Map Projection Editor on page 49
• Using the Map Projection Editor on page 52
• Datum Shifts and Methods on page 93
• Commonly Used Projection Types on page 97
• Projection Types in Map Projection Editor on page 104
• Cartographic Tables on page 123
• Test Conversion Example on page 139
• Map Projection Editor Glossary on page 146
R2003.12.0 Map Projection Editor 37
OpenWorks Project Management Landmark
Other References
The Map Projection Editor is simple to use, even though the underlying principles are complex. OpenWorks uses the POSC (Petrotechnical Open Software Corporation) Epicentre model to represent cartographic transformations. This model allows you to store the parameters that are used by the Blue Marble algorithms. This data model supports user-defined cartographic transforms between projection and geographic coordinate systems and between two geographic coordinate systems.
For an in-depth understanding of cartographic concepts and algorithms, Landmark suggests Map Projections—A Working Manual, a publication of the U.S. Geological Survey (Professional Paper 1395) which is available from the U.S. Government Printing Office in Washington, D.C. This is a trustworthy source book on the basic principles of cartography and the various cartographic projection types.
Introduction to Cartographic Reference Systems
This section contains a general discussion of the Map Projection Editor and an examination of the technical concepts you must know to define a cartographic reference system. This section also includes a discussion of how OpenWorks uses cartographic reference systems.
The main purpose of Landmark software is to provide accurate visualization of geophysical data. A major part of that accuracy lies in the ability of the software to pinpoint locations on a map with great precision.
Landmark’s Map Projection Editor helps ensure this precision by letting you define a Cartographic Reference System (CRS) for each project and each set of data that will be loaded into your system. The CRS creates a frame of reference for all calculations of latitude, longitude, northing and easting (x’s and y’s), and surface distance. CRS’s are stored in the OpenWorks database and so are available to any project using the same database.
Before you start creating a CRS, you should understand some of the basic terminology used in cartography. This chapter explains the basic information you need to know in order to define a CRS. Later chapters will explain how to define CRS’s using the Map Projection Editor.
38 Map Projection Editor: Introduction to Cartographic Reference Systems R2003.12.0
Landmark OpenWorks Project Management
Understanding the Problem
Whenever you try to locate a point on a map, you inevitably encounter the same problems encountered by surveyors and navigators throughout recorded history. Trying to represent the curved surface of the earth on the flat surface of a map always leads to distortions, no matter how carefully it is done.
The problem is fairly simple if you always use the same map and frame of reference — at least the distortions are constant. But what happens when you try to convert differences in degrees of latitude and longitude into northing and easting (x’s and y’s)? Or when you try to convert points on one kind of map to points on another type of map? A slight error can throw your calculations off by hundreds of feet.
For example, suppose you have a well located at 90o west longitude and 28o north latitude, and you want to place a new well 6400 meters south and 1300 meters west of the previous one. What will its location be? What is the relation between latitudes and longitudes (geographic coordinates), and northing and easting (x and y grid coordinates)? How can we show on a flat grid and in a consistent framework locations measured under different systems?
The CRS Solution
The problem can be solved through the use of a Cartographic Reference System (CRS). A CRS is not a map: instead, it is a way of describing a map that defines all of the assumptions and calculations on which the map is built, including
• spheroid• geodetic datum• prime meridian• projection type• projection parameters including false easting and northing, origin
latitudes and longitude, etc., or datum shift parameters• units of surface measure
Once a CRS is defined, it is possible to transform measurements made in any CRS to another CRS. Thus, the spatial relation between two points can always be seen by transforming them to a common CRS and viewing their images there. In general, this is how the Landmark software ensures accuracy in all of its coordinate positions.
R2003.12.0 Map Projection Editor: Introduction to Cartographic Reference Systems 39
OpenWorks Project Management Landmark
What You Need To Know
For each CRS that you create, you will need to know the geographic coordinate system, projection type, geodetic datum, surface units, and projection parameters to be used. If you do not know this information, ask the supplier of your data. The following pages explain each of these concepts in more detail for users who are unfamiliar with basic cartography.
There are two basic types of cartographic reference systems that you can create—those based on geographic coordinate systems using latitudes and longitudes, and those based on projection coordinate systems using x’s and y’s.
Projection Type
Any map is basically a projection of the curved surface of the earth onto a flat surface. There are dozens of different ways to project a map, but all are based on the three methods listed below and shown in the illustration on the next page:
• Cylinder. The surface of the earth is projected onto a cylinder, which is then cut and unfurled.
• Cone. The surface of the earth is projected onto a cone, which is then cut and laid flat.
• Plane. The surface of the earth is projected onto a plane.
40 Map Projection Editor: Introduction to Cartographic Reference Systems R2003.12.0
Landmark OpenWorks Project Management
GENERAL PROJECTION METHODS
TYPICAL PROJECTION TYPES
Cylinder
Cone
Plane Orthographic
Lambert Conic Conformal
Miller Cylindrical
R2003.12.0 Map Projection Editor: Introduction to Cartographic Reference Systems 41
OpenWorks Project Management Landmark
Each of these methods is imperfect, because it invariably produces distortion. To help reduce the distortion, cartographers have developed different projection types for use in different mapping applications. For example, a Lambert Conic Conformal projection seems to produce the least distortion when mapping an area like the State of California, due to the unique shape and size of the state. In general, the best method for any given purpose is the one that produces the least distortion in the region of the earth being studied.
Example of Projection
Map Projection Editor provides 35 common projection types. A complete list of the projection types available in Map Projection Editor is in “Projection Types in Map Projection Editor” on page 104. Detailed information about the characteristics of each projection type is in “Projection Type Properties” on page 105.
Spheroid
The problem of projecting the three-dimensional surface of the earth onto a flat map is further complicated because the earth is not a perfect sphere or spheroid, but a somewhat flattened sphere called an ellipsoid. The exact amount of flattening has been calculated in many different ways, with each calculation based on certain assumptions about the geoid — the shape of the earth at sea level. For example, the Clarke spheroid of 1886 was a calculation developed for North America that assumed a flattening of 1/294.98. The WGS 72 spheroid was developed by satellite observation in 1972 and assumes a flattening of 1/298.26. For the purposes of this utility, the words “spheroid” and “ellipsoid” will sometimes be used interchangeably.
Earth surface
Map surface
Least distortion
Most distortion
42 Map Projection Editor: Introduction to Cartographic Reference Systems R2003.12.0
Landmark OpenWorks Project Management
Geodetic Datum
To further enhance the precision of their maps, map makers develop a smooth mathematical surface called a geodetic datum that provides a “best fit” over the area being studied. The mathematical model of the ellipsoid/spheroid is fixed to a point on the earth.
For example, North American Datum 1927 (NAD27) uses the Clarke 1866 ellipsoid fixed at Meades Ranch in Kansas. The World Geodetic System1984 (WGS84) datum uses the ellipsoid fixed at the earth’s geocenter.
Geographic C.S.
When you are creating a new map projection CRS, the Map Projection Editor lets you select a geographic coordinate system from a standard list. For any selection, the Map Projection Editor automatically references the correct datum, spheroid., and prime meridian, applying a prime meridian and the equator to a geodetic datum to reference the latitude and longitude coordinates.
Datum Shift
When you create a new geographic CRS, the Map Projection Editor lets you apply a datum shift to WGS84 in several ways. You can select an existing datum shift, or select a shift method appropriate for the datum, or you can create a new datum shift. For more information about applying datum shifts, refer to “Datum Shifts and Methods” on page 93.
Units
Landmark software uses linear units for all measurements of distance and angular units for all latitude-longitude coordinates. When you are creating a CRS, the Map Projection Editor suggests the appropriate units for the projection type. Typical linear units include common feet, indian feet, imperial feet, international meters, etc. Typical angular units include radians, degrees of arc, minutes of arc, grads of arc, etc. “Table 2: Supported Linear Units” on page 126 and “Table 3: Supported Angular Units” on page 128 provide a complete list of linear and angular units available in Map Projection Editor.
R2003.12.0 Map Projection Editor: Introduction to Cartographic Reference Systems 43
OpenWorks Project Management Landmark
Projection Parameters
Certain projection parameters may also be required to further specify the mapping system. The parameters required vary by projection type. When you select a projection type in the Map Projection Editor, the correct parameters are listed automatically for you to fill in. Some of the most common parameters are explained on the following pages. For definitions of other parameters, see the “Map Projection Editor Glossary” on page 146.
Parallels and Meridians
You can segment a spheroid into 360 degrees both in a north-south direction and in an east-west direction. These angular measurements are called latitude (north-south angles) and longitude (east-west angles). When these measurements are projected as a grid onto the globe, the grid lines indicating latitude are called parallels and those indicating longitude are called meridians.
Some map projections are measured from the point where the reference cone, cylinder, or plane intersects the surface of the earth. Depending on the type of projection, the intersection may occur at one or two points. The latitudes where this occurs are called the standard parallels. For example, the following figure is adapted from Map
Parallels (latitude)
Meridians(longitude)
44 Map Projection Editor: Introduction to Cartographic Reference Systems R2003.12.0
Landmark OpenWorks Project Management
Projections—A Working Manual. It shows a Lambert Conic Conformal projection of North America, with two standard parallels at 20° and 60°.
Notice that this projection is centered on a central meridian of 100°. Many projection types use this type of parameter to indicate the central north-south axis of the map area.
Origin
Origin is where distortion of the area of geographical interest is minimal.
Once you know the point of origin, you can develop an x-y scale for measuring distances in linear units, with x as the east-west component and y as the north-south component. Each projection CRS has a “natural” or “intrinsic” origin where the latitude-longitude coordinate of the origin corresponds to (x, y) = (0, 0). This natural origin is commonly a point where the distortions are smallest. Hence, a common practice is to specify an origin that matches the center of geographical interest.
Positive latitudes refer to the northern hemisphere, negative latitudes refer to the southern hemisphere. Positive longitude is measured eastward from the reference meridian. Negative longitude is measured westward from the reference meridian.
Central meridian (100°)
Second standard parallel (20°)
First standard parallel (60°)
Lambert Conic Conformal Projection of North America
R2003.12.0 Map Projection Editor: Introduction to Cartographic Reference Systems 45
OpenWorks Project Management Landmark
False Easting and False Northing
When you place the origin at the center of the area being studied, it causes many coordinates to be negative, since many points will lie west of the y axis and south of the x axis (see diagram below). To avoid this inconvenience, you can adjust the origin so it lies southwest of the area being studied. This adjustment has the effect of putting the entire area into the positive quadrant of the two axes. The adjustments made to avoid negative coordinates are called false easting and false northing.
The figure below illustrates the concepts of false easting and false northing. In this figure, (x, y) represents the natural origin at the center of the area being studied and (X, Y) represents the adjusted origin after false easting and false northing have been applied. If X,Y is defined as 0,0, then all coordinates in the area of interest will be positive numbers.
Putting It All Together
As you can see, there are many specifications that go into a CRS, and often it is impossible to define a point on the map unless you know the assumptions underlying the CRS. For example, if the coordinates of a well are 2.5 and 58.3, this has no meaning until we know more about the CRS. If the CRS is specified as
• Prime meridian: Greenwich• Geodetic datum: European Datum 1950• Spheroid: International 1924• Surface measure: dega (degrees of arc)
Natural origin (x,y)
Adjusted origin (X,Y)
Area of interestFalse
northing
X = x + false eastingY = y + false northing
False easting
46 Map Projection Editor: Introduction to Cartographic Reference Systems R2003.12.0
Landmark OpenWorks Project Management
then we know that the well is near the middle of the North Sea. However, the same coordinates could be used to define a location near Houston, Texas, if the CRS specifications are as follows
• Projection Type: Transverse Mercator• Basis Geog. CS: North American Datum 1927• Prime Meridian: Greenwich• Geodetic datum: North American Datum 1927• Spheroid: Clarke 1866• Surface measure: meters• False Easting: 500000• False Northing: 0• Meridian Scale Factor: 0.9996• Origin Latitude: +29.5 (29.5° N)• Origin Longitude: -94.5 (94.5° W)
Notice that the parameters required to specify different CRS’s can vary widely, as shown by the two examples above. The Map Projection Editor manages storage and display of these specifications in an intelligent way. Since a Geographical CRS does not require a specification for “longitude of central meridian,” such an entry does not even appear in the on-screen display.
As much as possible, the Map Projection Editor reflects in its design and operation the correct conceptual relation between points, their coordinates, the CRS used to measure those coordinates, the projection type that serves as a template for the CRS, the parameters that make up those templates, and the units associated with the individual parameters.
“Projection Types in Map Projection Editor” on page 104 lists the projections available in Map Projection Editor. “Projection Type Properties” on page 105 describes each projection type.
R2003.12.0 Map Projection Editor: Introduction to Cartographic Reference Systems 47
OpenWorks Project Management Landmark
How OpenWorks uses Cartographic Reference Systems
When you create an OpenWorks project, you specify a CRS to use to store and calculate project map data. This is called the project CRS. The project CRS should be the same map projection system that was used to locate the original project data.
When you load data, you specify the CRS used when the data was recorded. If the CRS used when the data was recorded does not exist in OpenWorks, you can create it. If the project uses a different CRS, the loader converts the data to the project CRS at load time. This means that all data uses the same cartographic units.
When you export data, you select an appropriate CRS for export. If the CRS does not exist in OpenWorks, you can create it. If the project uses a different CRS, the exporter converts the data from the project CRS at export time.
The project CRS provides the default map display parameters for the project. However, you can use a display CRS that is different from the project CRS so that you can store project data using the most accurate reference system, and display project data using a more convenient or visually pleasing reference system. In addition, the surface distance units for a project are determined by the surface measure units used by the project CRS.
For more information about project and display CRS’s, refer to the “Project Create” (page 201) chapter in this manual.
Project CRS (geographic coordinate system)
CRS 1 (polyconic)
CRS 2 (orthographic)
Data A(polyconic)
Data C(orthographic)
Data B(orthographic)
Project Database
48 Map Projection Editor: Introduction to Cartographic Reference Systems R2003.12.0
Landmark OpenWorks Project Management
Launching the Map Projection Editor
This section explains how to access the utility, the layout of the utility’s main window, and the menus in the main menu bar.
To run this utility, you must log on as an OpenWorks user who:
• is an External Oracle user with the OW_ADMINISTRATOR role in the Oracle database, and
• has been granted MANAGE access to the OpenWorks project
Use the following steps to launch the Map Projection Editor:
• UNIX—From the OpenWorks Command Menu, select Project > Map Projection Editor.
• Windows—From the Start menu, select Programs > Landmark OpenWorks > Project Administration > Map Projection Editor.
Unlike the OpenWorks data management utilities, such as Well Data Manager, Data Domain Manager, and Curve Dictionary, Map Projection Editor does not require setting the project, interpreter, or measurement system. Thus you can create all of the CRS’s that you need before you even create a project or designate interpreters. In addition, all of the CRS’s that you create will be available to all of the OpenWorks projects using the session OWSYSSID (database server).
The Map Projection Editor main window appears as shown in the next section.
Other Ways to Start the Map Projection Editor
Most Landmark utilities that require you to select a CRS also let you start the Map Projection Editor by pushing a button. When you do so, the Map Projection Editor opens the same way it does here.
UNIX—You can also start the Map Projection Editor by typing the command xcsredit on any X terminal command line.
R2003.12.0 Map Projection Editor: Launching the Map Projection Editor 49
OpenWorks Project Management Landmark
Window Layout
The Map Projection Editor main window contains the following divisions.
The main window contains a series of pulldown menus and a list of all of the projection types and geographic coordinate systems predefined in OpenWorks.
available Projection Coordinate Systems
available Geographic Coordinate Systems
CS Details displays some basic information about the selected Projection or Geographic Coordinate System
50 Map Projection Editor: Launching the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Map Projection Editor Menus
The pulldown menus let you perform the following functions:
• The File menu includes options for creating a CRS, saving and deleting CRS’s, and exiting the utility. This functionality is described beginning on a following page.
• The Transform menu lets you test the conversion of data from one CRS to another and display the results. This is demonstrated at “Running a Test Conversion” on page 87.
• The Help menu provides access to the online documentation and release notes.
The main window includes lists of the available projection types and geographic coordinate systems. You can use these lists to select CRS’s for editing, viewing, or deleting.
R2003.12.0 Map Projection Editor: Launching the Map Projection Editor 51
OpenWorks Project Management Landmark
Using the Map Projection Editor
This section contains an explanation of everything you must do to use the Map Projection Editor, use its functions to create and edit geographic and projection coordinate systems, and exit the program. This section contains all the information you will need for most applications.
There are two basic types of cartographic reference systems that you can create—those based on geographic coordinate systems and those based on projection coordinate systems.
The steps you take to create each type are basically the same; however, the system provides entirely different default data for the two types of coordinate systems. For this reason, the steps to create the CRS’s are divided into the following topics containing complete instructions for creating new CRS’s:
• “Creating a Geographic CRS” on page 53
• “Creating a Projection CRS” on page 64
In addition, you may need to create a custom datum shift for the geographic coordinate system used by your geographic or projection CRS. Refer to “Creating New Datum Shifts for Geographic Coordinate Systems” on page 72 for complete instructions to perform this task.
You should create the CRS’s you need before you create a project or sit down to load or export data. However, OpenWorks allows you to start the Map Projection Editor from inside the Project Create, ASCII Well Loader, and Well Data Export utilities. Then use the instructions in this section to create CRS’s whenever necessary.
Warning: You can change a CRS after it is associated with a project.
You can change a projection or geographic CRS after it is associated with a project. This would be necessary if you need to define a datum shift transformation or to change a stand-alone into a valid projection type. However, changing a project CRS is dangerous; doing so can invalidate your project. For example, changing the Basis Geographic CS or prime meridian to a value that does not accurately represent your project data destroys the meaning of that data.
52 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Creating a Geographic CRS
To create a new geographic CRS, use the procedures in this section.
1. Select File > New in the Map Projection Editor main window. The following window appears.
2. Click on the List button next to Coord Sys Type.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 53
OpenWorks Project Management Landmark
A dialog box containing the available projection types opens. Select “Geographic Latitude/Longitude” from the list, as shown in the illustration below, and click OK.
54 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
When you select the “Geographic Latitude/Longitude” projection type, the Map Projection Editor window expands to reflect the most basic required entries for the geographic type, as shown in the example below.
The system automatically provides the default prime meridian and units of surface distance. You can change these if you desire. The instructions to reset these values are on the following pages.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 55
OpenWorks Project Management Landmark
3. If desired, you may change the Prime Meridian provided by the system. Click on the List button next to the Prime Meridian field.
A dialog box containing the available prime meridians opens, as shown in the illustration below. Select a prime meridian from the list and click on OK.
4. Since this is a geographic CRS, you must select a datum.
Click on the List button next to the Datum field.
56 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
A dialog box containing the available datums opens, as shown in the illustration below. Select the desired datum from the list and click on OK.
When you select the datum, the system posts default values in the Spheroid and the Shift Target Coordinate System fields, as shown in the following illustration. At this point, the Map Projection Editor should look similar to the illustration.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 57
OpenWorks Project Management Landmark
In this example, North American Datum 1983 was chosen as the datum. The system provided default values for the prime meridian, spheroid, shift target CS, and surface measure. You cannot change the spheroid or shift target CS, but you can change the other values, if desired.
The next steps are to enter the datum shift and shift method.
About default datums and shift target CS’s.
If the datum is North American Datum 1927, the Shift Target CS will always be North American Datum 1983. If any other datum is used, the Shift Target CS will always be World Geodetic System 1984.
58 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
5. Since this is a geographic CRS, you must also define the datum shift transformation. You can do this in one of two ways: either by selecting an existing datum shift or a datum shift method.
• In the first method, you select a datum shift. Click on the List button next to the Datum Shift field.
When the dialog box, containing the available datum shifts, opens (as shown in the illustration below), select the desired datum shift from the list and click on OK.
The system then automatically selects the appropriate shift method for the selected datum shift.
Datum Shift Methods in OpenWorks
OpenWorks utilizes four different datum shift methods: Mol = Molodensky, Bursa = Bursa-Wolf, NADCON = North American Datum Conversion, NATRAN = Canadian National Transformation, version 2. The system lists the name of the datum shift as:
Datum + Shift Mnemonic (if one exists) + Shift Method
For more information about datum shifts refer to “Datum Shifts and Methods” (page 93). You can create new datum shifts; refer to “Creating New Datum Shifts for Geographic Coordinate Systems” (page 72).
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 59
OpenWorks Project Management Landmark
• In the second method, you specify the datum shift by selecting a shift method.
Click on the List button next to the Shift Method field.
A the dialog box containing the available shift methods opens (as shown in the illustration below). You can create new datum shifts, if desired. Refer to “Creating New Datum Shifts for Geographic Coordinate Systems” on page 72.
Select the desired method from the list and click OK. The shift method is posted in the Shift Method field.
The system then automatically selects the appropriate datum shift for the shift method and posts it in the Datum Shift field.
At this point, the Map Projection Editor window for the new CRS should look similar to the following illustration.
60 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
In this example, Molodensky was chosen as the shift method.
The system provided the appropriate datum shift parameters for the selected shift method. (For more information about datum shifts refer to “Datum Shifts and Methods” on page 93.)
The next steps are to change or enter the surface measure and description. These steps begin on the following page.
Map Projection Editor window showing a new geographic CRS
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 61
OpenWorks Project Management Landmark
6. When you selected the projection type, the system posted the suggested units of surface distance in the Surface Measure field. The units of distance are derived from the project measurement system—it is not the unit of measure of the transformation data.
You can change the surface measure units, if desired. Click on the List button next to the Surface Measure field.
A dialog box containing the units of surface distance applicable to the projection type opens, as shown below. Select the desired units from the list and click on OK.
Angular Units supported by Map Projection Editor
The angular units supported by Map Projection Editor are listed in “Table 3: Supported Angular Units” on page 128.
62 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
7. Type a description for the new CRS in the Description field. Your description can be up to 80 characters of alphanumeric text.
8. Enter the translation parameters that define the datum shift from the datum referenced in the Datum field to the datum referenced in the Shift Target CS field (e.g., World Geodetic System 1984). See “Datum Shifts and Methods” on page 93.
9. Save the CRS. Refer to “Saving a New CRS” on page 80.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 63
OpenWorks Project Management Landmark
Creating a Projection CRS
Map Projection Editor allows you to create CRS’s based on a number of projection types.
To create a new projection CRS, move the mouse pointer into the Map Projection Editor main window and use the procedures on this and the following pages.
1. Select File > New. The following window appears.
64 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
2. Click on the List button next to Coord Sys Type.
A dialog box containing the available projection types opens, as shown in the following illustration.
Select a projection type from the list and click OK.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 65
OpenWorks Project Management Landmark
After you select a projection type, the Map Projection Editor window expands to reflect the required entries for the projection type, as shown in the following illustration.
The system posts the default units of surface distance for the projection type in the Surface measure field.
For most projection types, additional required parameters also appear in the bottom section of the window. For the State Plane and Universal Transverse Mercator projection types, a Zone field appears. There are no parameters for the New Zealand Map Grid projection type.
66 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
The next step is to select a geographic coordinate system.
3. Click on the List button next to the Basis Geog. CS field.
A dialog box containing the available geographic coordinate systems opens, as shown in the following illustration. (For information about how the geographic coordinate systems incorporate datum shifts, refer to “Datum Shifts and Methods” on page 93.) Select a coordinate system from the list and click on OK.
The spheroid associated with the geographic coordinate system you chose is posted in the Spheroid field.
At this point, the Map Projection Editor window for the new CRS should look similar to the following illustration.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 67
OpenWorks Project Management Landmark
In this example, Albers Equal Area Conic and North American Datum 1983 were chosen as the projection type and the geographic coordinate system, respectively.
The system provided default values for the prime meridian, datum, spheroid, and surface measure. You cannot change the first three values, since they are derived from the selected Basis Geog. CS; however, you can change the surface measure value, if desired.
The next steps are to change or enter the surface measure, description, and map projection parameters.
Map Projection Editor window showing new projection CRS
68 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
4. When you selected the projection type, the system posted the suggested units of surface distance in the Surface Measure field. The units of distance are derived from the project measurement system, not the units of the map projection parameters.
You can change these units, if desired. Click on the List button next to the Surface Measure field.
A dialog box containing the units of surface distance applicable to the projection type opens, as shown in the following illustration. Select the desired units from the list and click on OK.
5. Type a description for the new CRS in the Description field. Your description can be up to 80 characters of alphanumeric text.
Linear Units supported by Map Projection Editor
The linear units supported by Map Projection Editor are listed in “Table 2: Supported Linear Units” on page 126.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 69
OpenWorks Project Management Landmark
6. If you selected the State Plane or Universal Transverse Mercator projection type, you must define the appropriate zone. Click on the List button next to the Zone field.
A dialog box displays containing the zones applicable to the projection type opens.
Select the desired zone from the list and click OK.
If the projection type is Universal Transverse Mercator, indicate whether the mapping data is from the Northern or Southern hemisphere simply by selecting the zone with the appropriate suffix - either N or S.
If the projection type is State Plane, the Zones list will reflect the entry in the Basis Geog. CS field.
70 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
7. Depending on the projection type you chose, you will probably have to enter map projection parameters. These will be at the bottom of the window.
You can use the up and down arrow buttons to increase and decrease the values shown.
8. If you need to apply a datum shift, refer to “Creating New Datum Shifts for Geographic Coordinate Systems” on page 72.
9. Save the CRS. Refer to “Saving a New CRS” on page 80.
Entering Degrees
When entering latitude, longitude, or other angular units, the Map Projection Editor recognizes decimal numbers and positive or negative values.
Use decimal values to enter degrees, minutes, and seconds. For example, 20.5 is equal to 20 degrees, 30 minutes.
Use positive numbers to express degrees North and East and negative numbers for degrees West and South. For example, -30 latitude equals 30 degrees South.
Since both latitude and longitude are relative and have a maximum value of 360 degrees, the Map Projection Editor considers values equivalent if the sum of their absolute value equals 360. For example, +20 (degrees E) is the same as -340 (degrees W).
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 71
OpenWorks Project Management Landmark
Creating New Datum Shifts for Geographic Coordinate Systems
You can create new datum shifts for the geographic coordinate system used by a projection coordinate type CRS or by a geographic coordinate type CRS.
This ability to create datum shifts is useful when you upgrade an OpenWorks 4.x project to OpenWorks 5.0. Since previous versions of OpenWorks 4.x did not incorporate datum shifts, the CRS’s associated with your OpenWorks 4.x projects may not be as useful as they could now be.
The best course of action is to define a CRS that is exactly the same as the CRS you used in OpenWorks 4.x, but with the correct datum shift, before you upgrade a project to OpenWorks 5.0. Then upgrade the project. This will accomplish two things. First, it will associate the correct datum shift with the CRS. Second, the upgrade program will associate the redefined CRS with the upgraded project. The upgraded project will then be able to take advantage of the datum shift associated with its CRS.
Previous versions of OpenWorks and Map Projection Editor also did not allow you to make any changes to a project’s CRS. This version of Map Projection Editor allows you to make datum shift changes to the underlying geographic coordinate system associated with a project. Effectively, it allows you to make changes to a project’s CRS.
Without a datum shift transform defined, you cannot import data that was collected in a datum that is different from the project datum. You also cannot export data to a CS that has a different datum than the project. Applications that perform any kind of conversion from one CRS to another can potentially create an error if the conversion requires a datum shift and the datum shift is not defined. For example,
Upgrading projects
You can only upgrade a project in an installation of OpenWorks on a UNIX workstation, not on a Windows installation.
72 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
the Map Projection Editor Grid Test will fail if the source CS and target CS use different datums.
For a detailed discussion of the datum shifts and shift methods available in Map Projection Editor, refer to “Datum Shifts and Methods” on page 93.
Warning: Use extreme caution when applying a datum shift to a project CRS.
Only expert users should change the datum shift associated with a project CRS because of the potentially serious consequences of an incorrect datum shift being applied to a project.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 73
OpenWorks Project Management Landmark
To create a new datum shift, do the following
1. Select the desired geographic coordinate system in the Map Projection Editor main window. In the example, Observatorio 1939 was selected.
2. Select File > Open.
A Map Projection Editor window opens as shown on the next page.
74 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
The datum shift, shift method, and datum shift parameters for the coordinate system are posted in this window. Note that at this point, the datum shift parameters cannot be changed.
The values for these datum shift parameters cannot be changed at this time.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 75
OpenWorks Project Management Landmark
3. In the Shift Mnemonic field, enter a mnemonic. You can type up to 14 alphanumeric characters.
As you type in the Shift Mnemonic field, the following changes occur in the Map Projection Editor window, as shown below:
• the Datum Shift field becomes blank
• the datum shift parameters in the bottom of the window become active
Datum Shift field is now blank.
Datum shift parameters can now be changed.
76 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
4. Select a shift method. Click on the List button next to the Shift Method field.
A dialog box containing the shift methods applicable to the datum opens, as shown in the following illustration.
Select the desired method from the list and click OK.
In this section, the Molodensky method is used for illustrative purposes. For a detailed discussion of the datum shift methods available in Map Projection Editor, refer to “Predefined Datum Shifts in Map Projection Editor” on page 95.
The Delta X, Y, and Z fields became active when you started typing in the Shift Mnemonic field. These values define a transform from the datum referenced in the Datum field (i.e., Observatorio 1939) to the datum referenced in the Shift Target CS field (i.e., World Geodetic System 1984).
5. Enter the appropriate values in these fields. You can type the values or use the up and down arrow buttons to increase and decrease the values. The arrow buttons increase and decrease the values in increments of 10.
(If you had selected the Bursa-Wolf shift method, you would also have to enter datum shift parameters for Rotation X, Y, and Z, and
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 77
OpenWorks Project Management Landmark
the scale factor.)
6. Save the CRS. Refer to “Saving a New CRS” on page 80. The new datum shift will not be available until after you save the CRS.
After you have saved the CRS, the system posts the new datum shift in the Datum Shift field, as shown in the following illustration.
The system lists the name of the datum shift as
Datum + Shift Mnemonic + Shift Method
where Mol = Molodensky, Bursa = Bursa-Wolf, NADCON = North American Datum Conversion, and NATRAN = Canadian National Transformation, version 2.
The new datum shift is now available for other CRS’s using the same datum.
To see which datum shifts are now available for the datum, click on the List button next to the Datum Shift field.
78 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
The dialog box that opens contains all of the default datum shifts for the datum, plus the new datum shift you just created.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 79
OpenWorks Project Management Landmark
Saving a New CRS
After you have made all appropriate entries for the CRS, save the CRS.
1. Select File > Save As. (This option is only available when all of the entries for the CRS are complete.)
The Save As dialog box appears, as shown in the following illustration.
2. Enter a name to be used for saving this CRS. You can select a name from the list (if you want to replace an existing CRS) or click in the Selection field and type the desired name.
You cannot change preloaded CRS’s, but you can create new ones based on the preloaded CRS’s.
3. Click OK. The CRS is saved. The Cartographic Reference System window stays on the screen until you select File > Close.
Saving a CRS
You can save a CRS at any time by selecting File ➛ Save. This will not work; however, unless you have first used the Save As function to save the CRS. Save As will not work until you have filled in all appropriate entries for the CRS.
80 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
When you subsequently select the CRS in the Map Projection Editor main window, the details will be posted in the CS Details field.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 81
OpenWorks Project Management Landmark
Changing an Existing CRS
To change an existing CRS, use the steps in this section.
1. Select the desired CRS from the lists of available coordinate systems in the main window.
Warning: Use extreme caution when changing a CRS once it is asso-ciated with a project.
You can change a projection or geographic CRS after it is associated with a project. This would be necessary if you need to define a datum shift transformation or to change a stand-alone into a valid projection type. However, changing a project CRS is dangerous, because doing so can invalidate you project. For example, changing the Basis Geographic CS or prime meridian to a value that does not accurately represent your project data destroys the meaning of that data.
82 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
2. Select File > Open.
A window similar to the following opens with all of the specifications for the selected CRS.
3. Change any of the active settings desired.
4. Select File > Save.
5. Select File > Close when you are ready to close this window.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 83
OpenWorks Project Management Landmark
Deleting a CRS
To delete a CRS, use the procedure in this section.
1. Select the desired CRS from the list of available cartographic projections in the main window.
2. Select File > Delete.
If you selected a CRS that is being used by a project, a message box to that effect will open.
3. Click OK. You cannot delete this CRS because it is the default CRS for an active project.
If you selected a CRS that is not the default CRS for an active project, a message appears asking you to confirm the deletion.
4. Click OK to confirm the deletion. The CRS name disappears automatically from the list.
You cannot delete a Project CRS.
The Map Projection Editor will not let you delete any CRS currently defined as the default CRS for a project.
84 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Testing a CRS
As mentioned earlier in this chapter, the purpose of a CRS is to provide a consistent framework for converting raw data to project map coordinates. Once you have defined one or more CRS’s, you can use the Map Projection Editor to test them. (This option cannot be used with stand-alone systems.)
Understanding the Test Conversion
The Test Conversion feature lets you test how successfully coordinates are converted from a source coordinate system to a target coordinate system, then back again. To set up the test, you specify a central value to be tested from the source CRS, the incremental values for other test coordinates on either side of the central value, and the number of points to be tested on either scale.
Test Points
For example, if the central value for latitude and longitude is (-152.4, 60), the increment is 1.0, and you want to test three points in either direction, the latitude and longitude points to be tested will be:
-153.4, +59.0 -152.4, +59.0 -151.4, +59.0 -153.4, +60.0 -152.4, +60.0 -151.4, +60.0 -153.4, +61.0 -152.4, +61.0 -151.4, +61.0
Once you specify these values, the Map Projection Editor converts the points from the source to the target coordinate system, then back to the source coordinate system again. By comparing the final source
Central value (-152.4,+60.0)
Increments
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 85
OpenWorks Project Management Landmark
coordinates to the original source coordinates, you can determine how accurate the conversion is. The accuracy is perfect if the final source coordinates (after conversion) exactly match the original source coordinates (before conversion). “Test Conversion Example” on page 139 contains an example of a test conversion.
The steps to perform a test conversion begin on the next page.
Stand-Alone Test Not Supported
If either the source or target list contains a stand-alone CRS, you will not be allowed to select it from the list. Since a stand-alone CRS is by definition an unknown coordinate system, the Map Projection Editor cannot make the calculations necessary to transfer coordinate data to or from other projection types. For more information, see “Cartographic Tables” on page 123.
86 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Running a Test Conversion
To perform a test conversion, do the following
1. Select Transform > Grid Conversion. The Test Conversion window opens.
2. Select the source coordinate system from the Source CS list on the left side of the window.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 87
OpenWorks Project Management Landmark
Notice that the units of measure are updated to reflect the surface measure units associated with the Source CS.
3. Select the target coordinate system from the Target CS list on the right side of the window.
The units reflect those associated with the selected Source CS.
88 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Notice that the parameter fields in the bottom half of the window now contain values associated with the target coordinate system.
4. Enter the values requested in the bottom half of the window. Some defaults are already suggested.
Conversion can be slow—enter a small number of points.
Use a small (20-30) number of points when you test a conversion. The total number of data points converted is equal to the number of y-latitude points multiplied by the number of x-longitude points. The example above uses 25 points.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 89
OpenWorks Project Management Landmark
Entering Degrees
For entries of latitude, longitude, or other angular units, the Map Projection Editor recognizes decimal numbers and positive or negative values.
Use decimal values to enter degrees, minutes, and seconds. For example, 20.5 is equal to 20 degrees, 30 minutes.
Use positive numbers to express degrees North and East and negative numbers for degrees West and South. For example, if the latitude is 30 degrees South, enter -30.
Since both latitude and longitude are relative and have a maximum value of 360 degrees, the Map Projection Editor considers values equivalent if the sum of their absolute value equals 360. For example, an entry of +20 (degrees E) is the same as an entry of -340 (degrees W).
Map Projection Editor does not check that conversions “make sense.”
You can set up a conversion that makes no sense. For example
Source CS = North American Datum 1927-NADCON ConUS
Target CS = European Datum 1979
lat/lon = 0/50
will result in a conversion failure.
90 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
5. Press the Convert button to begin the test conversion. A report is generated and displayed automatically. For example:
Example of Test Conversion Report
This report shows the original source coordinates (upper left), the resulting coordinates after these were converted to the target system (upper right), and the round-trip conversion from target back to source (bottom left and right). A statistical summary is included below the round-trip conversion information.
6. When you have finished viewing the report, click Close to dismiss the report window.
7. You can use the Test Conversion window to run more tests, or click Close to exit.
The mid point target coordinates (point 13 in this case) show the degree of accuracy of the conversion.
R2003.12.0 Map Projection Editor: Using the Map Projection Editor 91
OpenWorks Project Management Landmark
Exiting Map Projection Editor
When you have finished using the Map Projection Editor, follow these steps to exit the utility:
1. Make sure you have saved all cartographic projections defined during this session.
2. Select File > Exit in the Map Projection Editor main window. The main window and all related windows close.
92 Map Projection Editor: Using the Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Datum Shifts and Methods
This section describes the datum shift transformations and shift methods available in Map Projection Editor.
Within OpenWorks, all datum shifts are defined from a source datum (i.e., the datum listed in the “Datum” field) to a common datum, either North American Datum 1983 or World Geodetic System 1984. The target datum (the field labeled “Shift Target CS”) is referenced in Map Projection Editor using the name of a geographic coordinate system that includes the target datum.
If the source datum is North American Datum 1927, the target datum is North American Datum 1983, and the “Shift Target CS” field will display “North American Datum 1983."
If the source datum is not North American Datum 1927, the target datum is World Geodetic System 1984, and the “Shift Target CS” will field display “World Geodetic System 1984.”
Shift Methods Used in Map Projection Editor
Map Projection Editor utilizes the following datum shift methods
• Molodensky
• Bursa-Wolf
• North American Datum Conversion (NADCON)
• National Transformation (NATRAN) version 2
Molodensky Shift Method
In general, the Molodensky shift method is the fastest and most universal transformation with accuracy of approximately five meters. It is a three parameter translation transformation from one datum to another; delta x, delta y, delta z.
As used in OpenWorks, this provides a translation from the source datum to the common datum, World Geodetic System 1984.
R2003.12.0 Map Projection Editor: Datum Shifts and Methods 93
OpenWorks Project Management Landmark
Bursa-Wolf Shift Method
In general, the Bursa-Wolf transformation is slower that Molodensky, but faster that NADCON or NATRAN, and more accurate than Molodensky but less accurate than NADCON or NATRAN.
Bursa-Wolf is typically used in small regions. The accuracy varies, but is expected to range from two to five meters.
Bursa-Wolf is a seven parameter translation transformation from one datum to another; delta x, delta y, delta z, rotation about x, rotation about y, rotation about z, and scale factor. As used in OpenWorks, this provides a translation from the source datum to the common datum, World Geodetic System 1984.
NADCON Shift Method
NADCON is used throughout North America and is defined to convert latitude and longitude from the North America Datum 1927 to the North America Datum 1983. However, this method can be used in other parts of the world if an appropriate grid shift data file is defined for that region.
In general, this transformation is slower than Bursa-Wolf, but more accurate. The accuracy of a NADCON transformation is expected to be approximately 1 meter. The NADCON transformation searches latitude and longitude grid files to determine which grid a latitude and longitude data pair falls within. It then interpolates between the high and low grid bound to determine the converted values.
OpenWorks grid files for the continental United States (conus), Puerto Rico and Virgin Islands (prvi), and Alaska (alaska) are located in $OWHOME/dat/carto. These files are obtained from the National Geodetic Survey (NGS) via anonymous ftp at the following internet address:
fpt://ftp.ngs.noaa.gov(pub/pcsoft/nadcon)
If the “Shift Method” is NADCON, Map Projection Editor allows users to specify the data file in the “NADCON FileNm” field. A table showing the range of each of these grid files appears in the next section “Predefined Datum Shifts in Map Projection Editor” on page 95.
94 Map Projection Editor: Datum Shifts and Methods R2003.12.0
Landmark OpenWorks Project Management
NATRAN version 2 Shift Method
NATRAN (the Canadian National Transformation) version 2, (NTv2) transformation is the standard datum shift method for Canada. It is used to convert latitude and longitude from the North America Datum 1927 to the North America Datum 1983. This method is very similar to NADCON; however, is more accurate than NADCON in the region of Canada. NTv2 uses the grid shift lookup scheme; however, the NTv2 data file contains subgrids and other features that produce better accuracy.
Like NADCON, the NATRAN data file name (ntv2_0) is displayed in the Map Projection Editor field labeled “NATRAN FilNm.”
The Canadian National Transformation, version 2, (NTv2) data is produced under license from Her Majesty the Queen in Right of Canada, represented by the Minister of Natural Resources.
For additional information, contact
Information ServicesGeodetic Survey Division, Geomatics CanadaNatural Resources Canada615 Booth StreetOttawa, Ontario, K1A 0E9 Canada
Telephone: (613) 995-4410email: [email protected]: http://www.geod.nrcan.gc.ca
Predefined Datum Shifts in Map Projection Editor
Map Projection Editor provides several predefined datum shifts using specific shift methods.
For example, if you open the geographic coordinate system 'Australian Geodetic 1984' and click the Datum Shift List button, two predefined datum shifts are listed:
• AGD84****Bursa is the datum shift using the Bursa-Wolf method
• AGD84****Mol is the datum shift using the Molodensky method
If you open 'North American Datum 1927' and click the Datum List button and then click the Datum Shift List button, four predefined NAD27 to NAD83 datum shifts are listed:
R2003.12.0 Map Projection Editor: Datum Shifts and Methods 95
OpenWorks Project Management Landmark
• NAD27 to NAD83**Alaska**NADCON is the NADCON method used in Alaska
• NAD27 to NAD83**Canada**NATRAN is the NATRAN method used in Canada
• NAD27 to NAD83**Continental USA**NADCON is the NADCON method used in the continental U.S.
• NAD27 to NAD83**PR, VI**NADCON is the NADCON method used in Puerto Rico and the Virgin Islands
Each of these NADCON datum shifts has a data file name associated with it. This data file appears in the NADCON FilNm field, as shown in the illustration below:
Each NADCON file is only valid in the area where the data file is defined, as shown in the table below.
Thus, selecting 'NAD27 to NAD83**Alaska**NADCON' as the datum shift method to convert latitude and longitude for referencing the continental US would result in erroneous data.
Area file name
min maxContinental U.S. conus
lat 20.0 50.0
lon -131.0 -63.0
Puerto Rico/Virgin Islands prvilat 17.0 19.0
lon -68.0 -64.0
Alaska alaskalat 46.0 77.0
lon -194.0 -128.0
The method appears here.When the method is NATRAN, this field will be labeled “NATRAN FilNm”
96 Map Projection Editor: Datum Shifts and Methods R2003.12.0
Landmark OpenWorks Project Management
Commonly Used Projection TypesThis section describes the CRS projection types most commonly used by Landmark users: Universal Transverse Mercator, State Plane, Geographic (Latitude/Longitude), and Self-Reference (Stand-Alone).
To reduce confusion resulting from the wide variety of possible reference systems, cartographers have agreed upon standardized types, which are particular projections with prespecified parameters designed to be used for particular geographical zones. Two of these standardized types are the Universal Transverse Mercator (UTM) System and the State Plane Coordinate System. Two other commonly used projection types are the Self-reference (or stand-alone) and the Geographic Latitude/Longitude projection types.
Other projection types are available in Map Projection Editor; these are listed in “Projection Types in Map Projection Editor” on page 104 and are described in detail in “Projection Type Properties” on page 105.
Universal Transverse Mercator System
The Universal Transverse Mercator System includes 120 zones that cover the entire earth. These zones are compounded from 60 longitudinal zones, each six degrees wide, and two latitudinal zones (the northern and southern hemispheres). Each of these zones has a prespecified Transverse Mercator projection with a central meridian at the center of the longitude zone and a prespecified false easting and false northing. The northern and southern zones for the same longitudes are identical except for their false northing values.
For the northern hemisphere, the equator at the central meridian is considered the origin. The false easting is 500,000 meters and the false northing is 0. For the southern hemisphere, the equator is still considered the origin. The false easting is 500,000 meters and the false northing is 10,000,000 meters. Maps made with this projection can be pieced together with a mismatch at their edges of no more than 1:1,000.
Military UTM
The UTM systems implemented by the Map Projection Editor are the civilian versions of earlier, more complex UTM military systems. The military UTM has many more latitudinal zones and uses Polar Stereographic projections for the poles. If you are dealing with maps that use the military UTM system, you cannot create appropriate CRS definitions using the UTM projection type provided by the Map Projection Editor. Instead, you must create the proper Transverse Mercator or Polar Stereographic projection based on the details given in Map Projections—A Working Manual.
R2003.12.0 Map Projection Editor: Commonly Used Projection Types 97
OpenWorks Project Management Landmark
Zon
e nu
mbe
rsU
nive
rsal
Tra
nsve
rse
Mer
cato
r P
roje
ctio
n (U
TM
)
98 Map Projection Editor: Commonly Used Projection Types R2003.12.0
Landmark OpenWorks Project Management
The figure on page 98 shows a world map with the UTM grid. Zone numbers are shown along the bottom. This figure is taken from Map Projections—A Working Manual. “Table 6: Universal Transverse Mercator Longitude Zones” on page 136 lists the UTM zones in both western and eastern coordinates.
When you create a CRS using the UTM projection type, you select a geographic coordinate system and the longitude zone and hemisphere. The system suggests the units of surface distance, and provides the prime meridian, datum, spheroid, and datum shift parameters.
See “Creating a Projection CRS” on page 64 for complete instructions to create a CRS using the UTM projection type.
Creating a UTM CRS
R2003.12.0 Map Projection Editor: Commonly Used Projection Types 99
OpenWorks Project Management Landmark
State Plane Coordinate System
The State Plane Coordinate System divides the United States and some of its territories into a series of zones. The boundaries of the zones follow county lines.
The ability to divide the states into horizontal or vertical zones produces a series of maps with minimal distortion. Each horizontally oriented zone is produced using a Lambert Conic Conformal projection that minimizes distortions around the standard parallel(s). Each vertically-oriented zone is mapped with a Transverse Mercator projection that minimizes distortion around the central meridian. The Alaskan Panhandle is a slanted strip that is mapped with an Oblique Mercator projection. The Guam zone uses a Polyconic projection. Consequently, maps made using State Plane systems can be pieced together with an edge mismatch of no more than 1:1,000.
State Plane Map (Partial)
An important feature of the State Plane system is its use of physical monuments implanted by surveyors. The (x, y) and latitude-longitude coordinates of these monuments have been computed and tabulated twice, first in 1927 and again in 1983. The survey results are known as the 1927 North American Datum and the 1983 North American Datum.
100 Map Projection Editor: Commonly Used Projection Types R2003.12.0
Landmark OpenWorks Project Management
Most state legislatures have given legal force to property maps using the State Plane system.
A map of the State Plane Coordinate System entitled Index of State Plane Coordinates (SPC) Zone Codes (NAD 1983) is published by the National Oceanic and Atmospheric Administration (NOAA).
When you create a CRS using the State Plane projection type, you specify the geographic coordinate system and the zone of interest. The system suggests the units of surface distance, and provides the prime meridian, datum, spheroid, and datum shift parameters.
See “Creating a Projection CRS” on page 64 for instructions to create a CRS using the State Plane projection type.
Creating a State Plane CRS
R2003.12.0 Map Projection Editor: Commonly Used Projection Types 101
OpenWorks Project Management Landmark
Self-reference (stand-alone) System
The Self-reference (or stand-alone) projection type can be used for cases where the cartographic system is unknown or the appropriate type is not supported by the Map Projection Editor. However, data stored under a self-reference CRS cannot be converted to or from another coordinate system.
When you create a CRS using this projection type, you specify the basis geographic coordinate system and enter a description of the CRS. The system suggests the linear units, and provides the prime meridian, datum, and spheroid.
See “Creating a Projection CRS” on page 64 for instructions to create a CRS using the Self-reference projection type.
Creating a Self-reference CRS
102 Map Projection Editor: Commonly Used Projection Types R2003.12.0
Landmark OpenWorks Project Management
Geographic Latitude/Longitude System
The Geographic Latitude/Longitude (also called Geodetic) System is a simple coordinate system based on latitudes and longitudes.
When you create a CRS using this projection type, you specify the datum, the datum shift, and enter a description of the CRS. The system suggests the prime meridian and angular units, and provides the spheroid that is appropriate for the datum.
You also select a shift method, and you enter values for delta x, y, and z, rotation x, y, and z, and a scale factor for a datum shift from the Datum to the Shift Target CS.
See “Creating a Geographic CRS” on page 53 for instructions to create a CRS using the geographic projection type.
Creating a Geographic CRS
R2003.12.0 Map Projection Editor: Commonly Used Projection Types 103
OpenWorks Project Management Landmark
Projection Types in Map Projection Editor
The following projection types are available in Map Projection Editor.
Projection Name Type
• Albers Equal Area Conic• Azimuthal Equal Area• Azimuthal Equidistant• Bonne• Cassini-Soldner• Equal Area Cylindrical• Equidistant Conic - 1 parallel• Equidistant Conic - 2 parallel• Equidistant Cylindrical• Geographic Latitude/Longitude• Gnomonic• Hotine Oblique Mercator - 1 point• Hotine Oblique Mercator - 2 points• Hotine Oblique Mercator - Azimuth Skew• Hungarian National System (EOV)• IMW Polyconic• Lambert Conic Conformal - 1 parallel• Lambert Conic Conformal - 2 parallel• Mercator• Miller Cylindrical• Mollweide• New Zealand Map Grid• Orthographic• Polar Azimuthal Equal Area• Polar Azimuthal Equidistant• Polar Stereographic• Polyconic• Robinson• Self-reference (stand-alone)• Sinusoidal• State Plane• Stereographic• Stereographic-European• Stereographic70• Transverse Mercator• Universal Transverse Mercator• Van der Grinten I
ConicAzimuthalAzimuthalConicCylindricalCylindricalConicConicCylindricaln/aAzimuthalCylindricalCylindricalCylindricalCylindricalConicConicConicCylindricalCylindricalPseudocylindricaln/aAzimuthalAzimuthalAzimuthalAzimuthalConicPseudocylindricaln/aPseudocylindricalCylindricalAzimuthalAzimuthalAzimuthalCylindricalCylindricalPseudocylindrical
104 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Projection Type Properties
This section provides the distinguishing characteristics of the projection types available in Map Projection Editor. Refer to Map Projections—A Working Manual for more details concerning these projection types.
For all of the projection types that require entering datum shift parameters:
• Standard Parallel 1 is Latitude of Northern Standard Parallel
• Standard Parallel 2 is Latitude of Southern Standard Parallel
Albers Equal Area Conic
The Albers Equal Area Conic projection is a map projection in which the parallels are unequally spaced arcs of concentric circles spaced closer to each other near the north and south edges of the map. The meridians are equally spaced and intersect the parallels at right angles. The Albers Equal Area Conic projection is used for equal-area maps of regions with predominant east-west expanse, such as the United States. It is used exclusively by the USGS for sectional maps of all 50 states.
When the Albers Equal Area Conic projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing• Latitude Projection Center• Standard Parallel 1• Standard Parallel 2
Azimuthal Equal Area
The Azimuthal Equal Area projection is an equal-area projection with the azimuthal property showing true directions from the center of the projection. Its scale at a given distance from the center varies less from the scale at the center than the scale of any of the other azimuthal projections. This projection is used to map the Pacific Ocean.
R2003.12.0 Map Projection Editor: Projection Types in Map Projection Editor 105
OpenWorks Project Management Landmark
When the Azimuthal Equal Area projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing• Latitude Projection Center• Longitude Projection Center
Azimuthal Equidistant
The Azimuthal Equidistant projection is neither an equal-area nor a conformal projection. The outer meridian of a hemisphere on the equatorial aspect is a circle. Distances and directions measured from the center are true. The Azimuthal Equidistant projection is recommended for coordinate systems in which distances are measured from an origin. The Azimuthal Equidistant projection is used in oblique aspect for atlas maps of continents, in world maps for aviation, and in quadrangles for Guam and Micronesia.
When the Azimuthal Equidistant projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing• Latitude Projection Origin
Bonne
The Bonne projection is pseudoconical and equal-area. The central meridian is a straight line. Other meridians are complex curves. Parallels are concentric circular arcs, but the poles are points. Scale is true along the central meridian and along all parallels. There is no distortion along the central meridian and along the standard parallel. The Bonne projection is used for atlas maps of continents and for topographic mapping of some countries, especially France, Ireland, Morocco, and some eastern Mediterranean countries.
106 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
When the Bonne projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing• Latitude Standard Parallel
Cassini-Soldner
The Cassini-Soldner projection is a cylindrical projection. It is neither equal-area or conformal. The central meridian, each meridian 90 degrees from the central meridian and the Equator are straight lines. Other meridians and parallels are complex curves. Scale is true along the central meridian and along lines perpendicular to the central meridian. Scale is nearly constant but not true along lines parallel to the central meridian. The Cassini-Soldner projection has been used for topographic mapping in England and several other countries.
When the Cassini-Soldner projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing• Origin Latitude• Origin Longitude
Equal Area Cylindrical
The Equal Area Cylindrical projection represents an orthographic projection of a sphere onto a cylinder. Like other regular cylindrical projections, the graticule of the normal Equal Area Cylindrical projection consists of straight equally spaced vertical meridians perpendicular to straight unequally spaced horizontal parallels. To achieve equality of area, the parallels are spaced form the Equator in proportion to the sine of the latitude. This is the simplest equal-area projection.
R2003.12.0 Map Projection Editor: Projection Types in Map Projection Editor 107
OpenWorks Project Management Landmark
When the Equal Area Cylindrical projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing• Latitude Standard Parallel
Equidistant Conic - 1 parallel
The Equidistant Conic is the simplest kind of conic projection. It is the projection most likely to be found in atlases of small countries, with its equally spaced straight meridians and equally spaced circular parallels.
“Equidistant Conic - 2 parallel” and “Equidistant Conic - 1 parallel” use the same map projection and algorithm. The 1 parallel projection is just a special case of the 2 parallel case when both Northern and Southern standard parallels are set to the same value.
When the Equidistant Conic - 1 parallel projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing• Latitude Projection Center• Standard Parallel 1
Equidistant Conic - 2 parallel
When the Equidistant Conic - 2 parallel projection is used, you must define the parameters for Equidistant Conic - 1 parallel and the following additional parameter:
• Standard Parallel 2
Equidistant Cylindrical
The Equidistant Cylindrical projection is probably the simplest of all map projections to construct and one of the oldest. Meridians and
108 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
parallels are equidistant straight lines, intersecting at right angles. Poles are shown as lines. This projection is used only in spherical form. If the Equator is made the standard parallel, true to scale and free of distortion, the meridians are spaced at the same distances as the parallels, and the graticule appears square. This form is often called the Plate Carree or the Simple Cylindrical Projection, and is used for United States and some State Index maps.
When the Equidistant Cylindrical projection is used, you must enter the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing• True Scale Latitude
The radius of the sphere is provided since only a spherical form of this projection is used. The radius of the sphere is used for forward and inverse projection from grid to geodetic coordinates within the system wherein this projection is incorporated. You are required to specify a geodetic datum when you use this projection as part of a coordinate system in order to perform geodetic datum shifts into other coordinate systems.
Geographic Latitude/Longitude
For detailed information about this projection, refer to “Geographic Latitude/Longitude System” on page 103. When the Geographic Latitude/Longitude projection is used, you must enter the following basic parameters:
• Prime Meridian• Datum• Datum Shift• Shift Method• Surface measure• Description
R2003.12.0 Map Projection Editor: Projection Types in Map Projection Editor 109
OpenWorks Project Management Landmark
Gnomonic
When the Gnomonic projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Origin Latitude• Origin Longitude• False Easting • False Northing
The radius of the sphere is provided since only a spherical form of this projection is used. The radius of the sphere is used for forward and inverse projection from grid to geodetic coordinates within the system wherein this projection is incorporated. You are required to specify a geodetic datum when you use this projection as part of a coordinate system in order to perform geodetic datum shifts into other coordinate systems.
Hotine Oblique Mercator - 1 point
The Hotine Oblique Mercator (HOM) projection is a cylindrical, conformal map projection. It is similar to the Mercator projection, except that the cylinder is wrapped around the sphere so that it touches the surface along the great circle path chosen for the central line, instead of along the earth's equator. Scale becomes infinite 90 degrees from the central line and is true along a chosen central line, along two straight lines parallel to the central line, or along a great circle at an oblique angle.
The HOM projection is used for geographic regions that are centered along lines that are neither meridians nor parallels, but that may be taken as great circle routes passing through the region, such as the Alaskan panhandle.
The Hotine Oblique Mercator - 1 Point projection is used throughout the world, particularly in Malaysia. This projection is equivalent to a HOM projection except that the defining parameters are different. You can specify a HOM projection by specifying a point and the azimuth defining the central line. This case allows for the entering of parameters for the RSO projection.
110 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
When the Hotine Oblique Mercator - 1 Point projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Azimuth Projection Center• False Easting • False Northing• Latitude Projection Center• Longitude Projection Center• Scale Factor Projection Center
Hotine Oblique Mercator - 2 points
When the Hotine Oblique Mercator - 2 Points projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing• Latitude Point 1• Latitude Point 2• Latitude Projection Center• Longitude Point 1• Longitude Point 2• Scale Factor Projection Center
Hotine Oblique Mercator - Azimuth Skew
“Azimuth Skew” represents the azimuth of the rectified to skew correction for the Hotine Oblique Mercator (1 pt and azimuth) case.
If there isn't a defined skew angle (State Plane Alaska Zone 1, for example), set the “Azimuth Skew” equal to “Azimuth of the Central Line.” If there is a defined skew angle (RSO Brunei Borneo, for example), set the “Azimuth Skew” to the published value.
When the Hotine Oblique Mercator - Azimuth Skew projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description
R2003.12.0 Map Projection Editor: Projection Types in Map Projection Editor 111
OpenWorks Project Management Landmark
• Azimuth Projection Center• False Easting • False Northing• Latitude Projection Center• Longitude Projection Center• Scale Factor Projection Center• Azimuth Skew
Hungarian EOV
The Hungarian EOV is a plane projection system used for Hungarian civilian base maps.
When the Hungarian EOV projection is used, you must define the following parameter:
• Description
IMW Polyconic
The IMW Polyconic projection is a modified Polyconic projection devised as a basis for the 1:1,000,000-scale International Map of the World (IMW) series. The IMW Polyconic projection differs from the ordinary Polyconic in two principle ways: all meridians are straight and two meridians are made true to scale.
When the IMW Polyconic projection is used, you must define the following parameters:
• Longitude Central Meridian• False Easting • False Northing• Standard Parallel 1• Standard Parallel 2• True Scale Longitude
Lambert Conic Conformal - 1 parallel
The Lambert Conic Conformal - 1 parallel projection is a map projection in which the scale is true along a single standard parallels, and the true shape of small areas is preserved. Parallels are unequally spaced arcs of concentric circles spaced closer to each other near the center of the map. The meridians are equally spaced and intersect the parallels at right angles. Coordinate systems based on this projection are used extensively in France.
112 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
When Lambert Conic Conformal - 1 parallel projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing• Meridian Scale Factor• Origin Latitude• Origin Longitude
Lambert Conic Conformal - 2 parallel
The Lambert Conic Conformal - 2 parallel projection is a map projection in which the scale is true along two standard parallels, and the true shape of small areas is preserved. Parallels are unequally spaced arcs of concentric circles spaced closer to each other near the center of the map. The meridians are equally spaced and intersect the parallels at right angles. The scale is true along two standard parallels. The Lambert Conic Conformal projection is widely used in atlases, in aeronautical charts, and in plane coordinate systems in surveying. It is also used in 7 1/2' and 15' quadrangles for 32 states, quadrangles for Puerto Rico, Virgin Islands, and Samoa, State Base Maps, quadrangles for International Map of the World, some State Index Maps, and the State Plane Coordinate System for states with large east-west extents.
When Lambert Conic Conformal - 2 parallel projection is used, you must define the following additional parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• Standard Parallel 1• Standard Parallel 2• Latitude Projection Origin• False Easting • False Northing
Mercator
The Mercator projection is a cylindrical, conformal map projection in which meridians and parallels are straight lines that cross at 90-degree angles. Angular relationships are preserved. To preserve conformality, parallels are placed increasingly farther apart with increasing distance
R2003.12.0 Map Projection Editor: Projection Types in Map Projection Editor 113
OpenWorks Project Management Landmark
from the equator. This results in extreme distortion at high latitudes. Scale is true along the equator or along two parallels equidistant from the equator. Despite its drawbacks, the Mercator projection is quite useful for navigation because rhumb lines, which show constant direction, are straight. The Mercator projection is also appropriate for conformal maps of equatorial regions.
When the Mercator projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting• False Northing• Origin Latitude• Origin Longitude
Miller Cylindrical
Meridians and parallels are straight lines, intersecting at right angles on the Miller Cylindrical projection. Poles are shown as lines. This projection is used only in spherical form and provides a compromise between Mercator and other cylindrical projections. It is used for world maps and the USGS National Atlas of the United States.
When the Miller Cylindrical projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing
The radius of the sphere is provided since only a spherical form of this projection is used. The radius of the sphere is used for forward and inverse projection from grid to geodetic coordinates within the system wherein this projection is incorporated. You must specify a geodetic datum when you use this projection as part of a coordinate system in order to perform geodetic datum shifts into other coordinate systems.
114 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Mollweide
The Mollweide projection is a pseudocylindrical equal-area projection. The central meridian is a straight line, 90th meridians are circular arcs, all other meridians are equally spaced elliptical arcs. Parallels are unequally spaced straight lines, parallel to each other. Poles are shown as points. This projection is used only in spherical form for world maps and very large region such as the Pacific Ocean.
When the Mollweide projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing
The radius of the sphere is provided since only a spherical form of this projection is used. The radius of the sphere is used for forward and inverse projection from grid to geodetic coordinates within the system wherein this projection is incorporated. You must specify a geodetic datum when you use this projection as part of a coordinate system in order to perform geodetic datum shifts into other coordinate systems.
New Zealand Map Grid
When the New Zealand Map Grid projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description
Orthographic
The Orthographic projection closely resembles a globe in appearance, since it is a perspective projection from infinite distance. Only one hemisphere can be shown at a time. This projection is used chiefly for pictorial views and is used only in spherical form.
When the Orthographic projection is used, you must define the following parameters:
• Basis Geog. CS
R2003.12.0 Map Projection Editor: Projection Types in Map Projection Editor 115
OpenWorks Project Management Landmark
• Surface measure• Description• False Easting • False Northing• Latitude Projection Center• Longitude Projection Center
The radius of the sphere is provided since only a spherical form of this projection is used. The radius of the sphere is used for forward and inverse projection from grid to geodetic coordinates within the system wherein this projection is incorporated. You must specify a geodetic datum when you use this projection as part of a coordinate system in order to perform geodetic datum shifts into other coordinate systems.
Polar Azimuthal Equal Area
The Polar Azimuthal Equal Area projection is an equal-area projection with the azimuthal property showing true directions from the center of the projection. Its scale at a given distance from the center varies less from the scale at the center than the scale of any of the other azimuthal projections. All meridians in the polar aspect are straight lines.
When the Polar Azimuthal Equal Area projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing• Latitude Projection Center• Longitude Projection Center
Polar Azimuthal Equidistant
When the Polar Azimuthal Equidistant projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting• False Northing• Latitude Projection Origin
116 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Polar Stereographic
The Polar Stereographic projection somewhat resembles other polar azimuthal projections, with straight radiating meridians and concentric circles for meridians. This projection is used for polar mapping within the Universal Polar Stereographic (UPS) coordinate system.
When the Polar Stereographic projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing• Latitude Projection Center• Longitude Projection Center• Scale Factor Projection Center
Polyconic
The Polyconic projection is neither an equal-area nor a conformal projection. Scale is true along each parallel and along the central meridian. Parallels of latitude are arcs of non concentric circles and the projection is free of distortion only along the central meridian. The Polyconic projection can be used to represent small areas on any part of the globe, preserving shapes, areas, distances, and azimuths in their true relation to the surface of the earth. Polyconic projections over large areas usually result in serious errors and exaggeration of details.
When the Polyconic projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing• Latitude Projection Center• Longitude Projection Center
R2003.12.0 Map Projection Editor: Projection Types in Map Projection Editor 117
OpenWorks Project Management Landmark
Robinson
The Robinson projection provides a means of showing the entire Earth in an uninterrupted form. The Robinson projection is destined to replace the Van der Grinten projection as the premier projection used by the National Geographic Society.
When the Robinson projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing
Self-reference (stand-alone)
For detailed information about this projection, refer to “Self-reference (stand-alone) System” on page 102.
When the Self-reference (stand-alone) projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description
Sinusoidal
The Sinusoidal projection is pseudocylindrical and equal-area. The central meridian is a straight line. All other meridians are shown as equally spaced sinusoidal curves. Parallels are equally spaced straight lines, parallel to each other. Poles are points. Scale is true along central meridian and all parallels. The Sinusoidal projection is used for maps of South America and Africa.
When the Sinusoidal projection is used, you must define the following additional parameters:
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing
118 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
• Longitude Central Meridian
State Plane
For detailed information about this projection, refer to “State Plane Coordinate System” on page 100.
When the State Plane projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• Zone
Stereographic
The Stereographic projection is the only known true perspective projection of any kind that is also conformal. The central meridian and a particular parallel (if shown) are straight lines. All other meridians and parallels are shown as arcs of circles. This projection is used for polar maps.
When the Stereographic projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting• False Northing• Scale Factor Projection Center• Latitude Projection Center• Longitude Projection Center
Stereographic-European
Stereographic-European is a conformal projection that has been conformally modified to optimize scale factor for Europe.
When the Stereographic-European projection is used, you must define the following parameters:
• Basis Geog. CS• Prime meridian• Datum
R2003.12.0 Map Projection Editor: Projection Types in Map Projection Editor 119
OpenWorks Project Management Landmark
• Spheroid• False Easting• False Northing• Scale Factor Projection Center• Latitude Projection Center• Longitude Projection Center
Stereographic70
Stereographic 70 is a conformal projection that has been conformally modified to optimize the scale factor for Romania.
When the Stereographic 70 projection is used, you must define the following parameters:
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing• Latitude Projection Center• Longitude Projection Center• Scale Factor Projection Center
Transverse Mercator
The Transverse Mercator projection is similar to the Mercator Projection, except that the axis of the projection cylinder is rotated 90 degrees from the polar axis. This projection does not have the straight meridians and straight parallels of the Mercator projection, except for the central meridian, the two meridians 90 degrees away, and the equator. Nor does the Transverse Mercator projection have the straight rhumb lines of the Mercator projection; rather, it is a conformal projection. Scale is true along the central meridian or along two straight lines equidistant from and parallel to the central meridian.
The Transverse Mercator projection is the projection used in the State Plane Coordinate System for states with predominant north-south extent. It is also the geometric basis for the UTM Coordinate System. The term Gauss-Kruger, or simply Gauss, refers to coordinate systems in parts of the world, for example, Germany and South America, based on the Transverse Mercator projection. This projection is also used for 7 1/2' and 15' quadrangles for 22 states.
When the Transverse Mercator projection is used, you must define the following parameters:
120 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
• Basis Geog. CS• Surface measure• Description• False Easting • False Northing• Meridian Scale Factor• Origin Latitude• Origin Longitude
Universal Transverse Mercator
The Universal Transverse Mercator (UTM) projection is the ellipsoidal Transverse Mercator to which specific parameters, such as central meridians, have been applied.
For detailed information about this projection, refer to “Universal Transverse Mercator System” on page 97.
When the Universal Transverse Mercator projection is used, you must define the following parameter:
• Basis Geog. CS• Surface measure• Description• Zone
Van der Grinten I
The Van Der Grinten I projection is neither conformal nor equal-arc. The Equator is true to scale, but there is great distortion in the polar areas. The central meridian and Equator are straight lines. All other meridians and parallels are arcs of circles. This projection is used for world maps, and only in spherical form.
When the Van der Grinten I projection is used, you must define the following additional parameters:
• Basis Geog. CS• Surface measure• Description• Longitude Central Meridian• False Easting • False Northing
The radius of the sphere is provided since only a spherical form of this projection is used. The radius of the sphere is used for forward and
R2003.12.0 Map Projection Editor: Projection Types in Map Projection Editor 121
OpenWorks Project Management Landmark
inverse projection from grid to geodetic coordinates within the system wherein this projection is incorporated.
You must specify a geodetic datum when you use this projection as part of a coordinate system in order to perform geodetic datum shifts into other coordinate systems.
122 Map Projection Editor: Projection Types in Map Projection Editor R2003.12.0
Landmark OpenWorks Project Management
Cartographic Tables
The first three tables in this section provide information on the spheroids, zones, and units supported by the Map Projection Editor. Other tables provide information on the State Plane zones and parameters and the Universal Transverse Mercator zones.
Table 1: Supported Spheroids
The following spheroids are supported by Map Projection Editor. For identification purposes, some spheroids are listed twice under different names. If a spheroid is listed twice, the alternate name appears in parentheses after the alphabetically listed name.
Spheroid NameSemi-major axis (meters)
Semi-minor axis (meters)
Eccentricity squared
“165” 6378165.000 6356783.011 0.0066935078654271
Airy 1830 6377563.396 6356256.910 0.0066705397615973
Airy Modified 6377340.189 6356034.448 0.0066705399999854
Australian National 1965 6378160.000 6356774.719 0.0066945419156245
Bessel 1841 6377397.155 6356078.963 0.0066743721749749
Bessel 1841 (Namibia) 6377483.865 6356165.383 0.0066743722212771
Bessel DHDN 6377397.155 6356078.963 0.0066743721738906
Bessel NGO 6377492.018 6356173.509 0.0066743722941680
Bessel RT90 6377397.154 6356078.962 0.0066743722295747
Clarke 1858 6378293.645 6356617.938 0.0067851614645563
Clarke 1858-1 6378293.639 6356617.982 0.0067851459211508
Clarke 1866 6378206.400 6356583.800 0.0067686579972912
Clarke 1866 Michigan 6378450.047 6356826.621 0.0067686579976096
Clarke 1880 6378249.145 6356514.870 0.0068035111421552
Clarke 1880 (Arc) 6378249.145 6356514.967 0.0068034809645859
Clarke 1880 (Benoit) 6378300.790 6356566.430 0.0068034827102971
Clarke 1880 (RGS) 6378249.145 6356514.870 0.0068035112828491
Clarke 1880 (SGA 1922) 6378249.200 6356514.997 0.0068034886019854
Clarke 1880 - French 6378249.200 6356515.000 0.0068034876462999
R2003.12.0 Map Projection Editor: Cartographic Tables 123
OpenWorks Project Management Landmark
Clarke 1880 - S. Africa 6378249.145 6356514.967 0.0068034808299283
Clarke 1880 ARC50 6378249.145 6356514.990 0.0068034735401242
Clarke 1880 IGN 6378249.200 6356515.000 0.0068034876462999
Clarke 1880 Jamaica 6378249.136 6356514.958 0.0068034809645860
Clarke 1880 Merchich 6378249.200 6356514.997 0.0068034886019854
Clarke 1880 Palestine 6378300.790 6356566.430 0.0068034828160751
Danish, Iceland 6377104.000 6355761.998 0.0066821208443710
Delambre 1810 6376428.000 6355598.000 0.0065227670160047
Everest 1830 6377276.345 6356075.414 0.0066378463614635
Everest 1830 (1967 Definition) 6377298.556 6356097.550 0.0066378466301996
Everest 1830 (1975 Definition) 6377301.243 6356100.231 0.0066378458075480
Everest 1948 6377304.063 6356103.039 0.0066378466301997
Everest 1956 6377301.243 6356100.228 0.0066378466301998
Everest 1969 6377295.664 6356094.668 0.0066378466301998
Everest Brunei 6377298.556 6356097.550 0.0066378466301996
Everest Modified 6377304.063 6356103.039 0.0066378466280601
Everest Pakistan 6377309.613 6356108.571 0.0066378466301998
Fischer 1960 (Mercury) 6378166.000 6356784.283 0.0066934218126982
Fischer 1968 (Mercury Modified) 6378150.000 6356768.337 0.0066934216993408
GEM 10C 6378137.000 6356752.314 0.0066943800699785
Geodetic Reference System 1967 6378160.000 6356774.516 0.0066946053569178
Geodetic Reference System 1980 6378137.000 6356752.300 0.0066943844420426
Hayford 1909 6378388.000 6356911.946 0.0067226700623167
Helmert 1907 6378200.000 6356818.170 0.0066934215066757
Hough 1956 6378270.000 6356794.343 0.0067226701580694
IAG 75 6378140.000 6356755.304 0.0066943800251638
IUGG 67 6378160.000 6356774.719 0.0066945418545876
IUGG 75 6378140.000 6356755.288 0.0066943849995880
Indonesian 1974 6378160.000 6356774.504 0.0066946090804091
International 1924 6378388.000 6356911.946 0.0067226700623167
Spheroid NameSemi-major axis (meters)
Semi-minor axis (meters)
Eccentricity squared
124 Map Projection Editor: Cartographic Tables R2003.12.0
Landmark OpenWorks Project Management
International 1967 6378160.000 6356775.019 0.0066944481600147
Kaula 6378165.000 6356344.388 0.0068305811061867
Krassovsky 1940 6378245.000 6356863.019 0.0066934215520398
Malayan 1830 6377304.063 6356103.039 0.0066378466280601
Mercury Modified 6378150.000 6356768.337 0.0066934216993408
Merit 83 6378137.000 6356752.298 0.0066943849995878
Modified Fischer 1966 (South Asia) 6378155.000 6356773.320 0.0066934217738299
NWL 10D 6378135.000 6356750.520 0.0066943177782667
NWL 9D 6378145.000 6356759.769 0.0066945420073108
OSU86F 6378136.200 6356751.517 0.0066943800699785
OSU91A 6378136.300 6356751.616 0.0066943800699786
Plessis 1817 6376523.000 6355863.022 0.0064695159933407
South American 1969 6378160.000 6356774.719 0.0066945419156245
Sphere 6371000.000 6371000.000 0.0000000000000000
Struve 1860 6378297.000 6356657.013 0.0067739954515677
Walbeck 6376896.000 6355834.847 0.0065945480941497
War Office 6378300.583 6356746.706 0.0067470821553595
World Geodetic System 1960 6378165.000 6356783.287 0.0066934216102894
World Geodetic System 1966 6378145.000 6356759.769 0.0066945420073108
World Geodetic System 1972 6378135.000 6356750.500 0.0066943240336952
World Geodetic System 1984 6378137.000 6356752.314 0.0066943800667647
Spheroid NameSemi-major axis (meters)
Semi-minor axis (meters)
Eccentricity squared
R2003.12.0 Map Projection Editor: Cartographic Tables 125
OpenWorks Project Management Landmark
Table 2: Supported Linear Units
The following linear units are supported in Map Projection Editor.
Linear Unit Conversion to Meters
1896India ft (Indian feet, 1896, W. Malay., Singapore) 0.304799735 meters
1959 ft (International foot) 0.3048 meters
1963 Indian ft (1963 India and Pakistan) 0.3047996 meters
angstrom (Angstrom) 1.0000E-10 meters
clarke link (Clarke link) .201166195 meters
cm (centimeters) .01 meters
dm (decimeter) .1 meters
Eng naut mi (English nautical miles) 1853.18771 meters
fathom (fathoms) 1.8288 meters
feet (Common feet) .30480061 meters
Imperial ft (Imperial feet) .304800749 meters
Imperial yd (Imperial yard) .914391795 meters
inches .0254 meters
India chain (Indian chains) 20.1168 meters
India yd (Indian yard) .914398543 meters
Kilometers 1000 meters
Malay feet (Indian feet, East Malaysia) .304800749 meters
meters (International meters) 1 meter
mil (milli-inch) .0000254 meters
miles (statute miles) 1609.344 meters
mm (millimeters) .001 meters
mod US ft (modified American foot) .304812253 meters
naut. mile (International nautical miles) 1852 meters
nm (nanometer) 1.0000E-09 meters
sci yd (scientific yards) 0.9144 meters
Se chains 20.1167651 meters
sears link (Sears link) .201167651 meters
Sears yd (Sears yard) .914398415 meters
126 Map Projection Editor: Cartographic Tables R2003.12.0
Landmark OpenWorks Project Management
Survey ft (US Survey feet) .30480061 meters
Thai feet (Indian feet - Myanmar and Thailand) .30479841 meters
um (microns) .000001 meters
US Survey mi (U.S. Survey mile) 1609.347 meters
USA yards .91440183 meters
Linear Unit Conversion to Meters
R2003.12.0 Map Projection Editor: Cartographic Tables 127
OpenWorks Project Management Landmark
Table 3: Supported Angular Units
The following angular units are supported in Map Projection Editor
Angular Unit Conversion/Format
c (cycle) 6.283185307
dega (degrees of arc) .01745329
gon (gons) .015707963
gr (gradient) .015707963
mina (minutes angular) .000290888
rad (radians) 1
seca (seconds angular) .00000484814
128 Map Projection Editor: Cartographic Tables R2003.12.0
Landmark OpenWorks Project Management
Table 4: State Plane Coordinate System Zones
The unique feature of the State Plane Coordinate System is its use of physical monuments implanted in the earth by surveyors. The (x, y) and latitude-longitude coordinates of these monuments have been computed and tabulated twice, first in 1927 and again in 1983. The survey results are known as the 1927 North American Datum and the 1983 North American Datum.
Each line of the following table gives the state, the name of the zone, the zone number, and the projection type. A zone number consists of a two-digit number for the state followed by a two-digit subdivision number for the zones within the state. If no subdivisions exist, the subdivision number is 00.
The Transverse Mercator projection is used for vertical zones. The Lambert Conic Conformal projection is used for horizontal zones. The Oblique Mercator projection is used to map a zone in Alaska that has an oblique orientation.
The nomenclature used in this table is adapted from Map Projections—A Working Manual (U.S.G.S. Professional Paper 1395) and is based on the 1927 Datum. The table applies this nomenclature to both the 1927 and the 1983 datums, even though some discrepancies exist between the two datums. For the 1983 datum, a few zones were either dropped or merged, but the types of projections used did not change. If you are using a 1983 Datum State Plane zone, you should examine the State Plane Parameters Table (Item 6 of the Cartographic Tables Menu) to see exactly how such discrepancies are resolved.
State Zone Zone No. Projection Type
Alabama East 101 Transverse Mercator
Alabama West 102 Transverse Mercator
Alaskaa Zone No. 1 5001 Oblique Mercator
Alaska Zone No. 2 5002 Transverse Mercator
Alaska Zone No. 3 5003 Transverse Mercator
Alaska Zone No. 4 5004 Transverse Mercator
Alaska Zone No. 5 5005 Transverse Mercator
Alaska Zone No. 6 5006 Transverse Mercator
Alaska Zone No. 7 5007 Transverse Mercator
Alaska Zone No. 8 5008 Transverse Mercator
R2003.12.0 Map Projection Editor: Cartographic Tables 129
OpenWorks Project Management Landmark
Alaska Zone No. 9 5009 Transverse Mercator
Alaska Zone No. 10 5010 Transverse Mercator
Arizona Central 202 Transverse Mercator
Arizona East 201 Transverse Mercator
Arizona West 203 Transverse Mercator
Arkansas North 301 Lambert Conformal
Arkansas South 302 Lambert Conformal
Californiab I 401 Lambert Conformal
California II 402 Lambert Conformal
California III 403 Lambert Conformal
California IV 404 Lambert Conformal
California V 405 Lambert Conformal
California VI 406 Lambert Conformal
California VII 407 Lambert Conformal
Colorado Central 502 Lambert Conformal
Colorado North 501 Lambert Conformal
Colorado South 503 Lambert Conformal
Connecticut ___ 600 Lambert Conformal
Delaware ___ 700 Transverse Mercator
Florida East 901 Transverse Mercator
Florida North 903 Lambert Conformal
Florida West 902 Transverse Mercator
Georgia East 1001 Transverse Mercator
Georgia West 1002 Transverse Mercator
Guam ___ 5400 Polyconic
Hawaiic 1 5101 Transverse Mercator
Hawaii 2 5102 Transverse Mercator
Hawaii 3 5103 Transverse Mercator
Hawaii 4 5104 Transverse Mercator
Hawaii 5 5105 Transverse Mercator
Idaho Central 1102 Transverse Mercator
State Zone Zone No. Projection Type
130 Map Projection Editor: Cartographic Tables R2003.12.0
Landmark OpenWorks Project Management
Idaho East 1101 Transverse Mercator
Idaho West 1103 Transverse Mercator
Illinois East 1201 Transverse Mercator
Illinois West 1202 Transverse Mercator
Indiana East 1301 Transverse Mercator
Indiana West 1302 Transverse Mercator
Iowa North 1401 Lambert Conformal
Iowa South 1402 Lambert Conformal
Kansas North 1501 Lambert Conformal
Kansas South 1502 Lambert Conformal
Kentucky North 1601 Lambert Conformal
Kentucky South 1602 Lambert Conformal
Louisiana North 1701 Lambert Conformal
Louisiana Offshore 1703 Lambert Conformal
Louisiana South 1702 Lambert Conformal
Maine East 1801 Transverse Mercator
Maine West 1802 Transverse Mercator
Maryland ___ 1900 Lambert Conformal
Massachusetts Island 2002 Lambert Conformal
Massachusetts Mainland 2001 Lambert Conformal
Michigand Central/L 2112 Lambert Conformal
Michigan Central/M 2102 Transverse Mercator
Michigan East 2101 Transverse Mercator
Michigan North 2111 Lambert Conformal
Michigan South 2113 Lambert Conformal
Michigan West 2103 Transverse Mercator
Minnesota Central 2202 Lambert Conformal
Minnesota North 2201 Lambert Conformal
Minnesota South 2203 Lambert Conformal
Mississippi East 2301 Transverse Mercator
Mississippi West 2302 Transverse Mercator
State Zone Zone No. Projection Type
R2003.12.0 Map Projection Editor: Cartographic Tables 131
OpenWorks Project Management Landmark
Missouri Central 2402 Transverse Mercator
Missouri East 2401 Transverse Mercator
Missouri West 2403 Transverse Mercator
Montanae Central 2502 Lambert Conformal
Montana North 2501 Lambert Conformal
Montana South 2503 Lambert Conformal
Nebraskaf North 2601 Lambert Conformal
Nebraska South 2602 Lambert Conformal
Nevada Central 2702 Transverse Mercator
Nevada East 2701 Transverse Mercator
Nevada West 2703 Transverse Mercator
New Hampshire ___ 2800 Transverse Mercator
New Jersey ___ 2900 Transverse Mercator
New Mexico Central 3002 Transverse Mercator
New Mexico East 3001 Transverse Mercator
New Mexico West 3003 Transverse Mercator
New York Central 3102 Transverse Mercator
New York East 3101 Transverse Mercator
New York Long Island 3104 Lambert Conformal
New York West 3103 Transverse Mercator
North Carolina ___ 3200 Lambert Conformal
North Dakota North 3301 Lambert Conformal
North Dakota South 3302 Lambert Conformal
Ohio North 3401 Lambert Conformal
Ohio South 3402 Lambert Conformal
Oklahoma North 3501 Lambert Conformal
Oklahoma South 3502 Lambert Conformal
Oregon North 3601 Lambert Conformal
Oregon South 3602 Lambert Conformal
Pennsylvania North 3701 Lambert Conformal
Pennsylvania South 3702 Lambert Conformal
State Zone Zone No. Projection Type
132 Map Projection Editor: Cartographic Tables R2003.12.0
Landmark OpenWorks Project Management
Puerto Rico ___ 5301 Lambert Conformal
Rhode Island ___ 3800 Transverse Mercator
Samoag ___ 5302 Lambert Conformal
South Carolinah North 3901 Lambert Conformal
South Carolina South 3902 Lambert Conformal
South Dakota North 4001 Lambert Conformal
South Dakota South 4002 Lambert Conformal
St. Croix ___ 5202 Lambert Conformal
Tennessee ___ 4100 Lambert Conformal
Texas Central 4203 Lambert Conformal
Texas North 4201 Lambert Conformal
Texas North Central 4202 Lambert Conformal
Texas South 4205 Lambert Conformal
Texas South Central 4204 Lambert Conformal
Utah Central 4302 Lambert Conformal
Utah North 4301 Lambert Conformal
Utah South 4303 Lambert Conformal
Vermont ___ 4400 Transverse Mercator
Virgin Islands ___ 5201 Lambert Conformal
Virginia North 4501 Lambert Conformal
Virginia South 4502 Lambert Conformal
Washington North 4601 Lambert Conformal
Washington South 4602 Lambert Conformal
West Virginia North 4701 Lambert Conformal
West Virginia South 4702 Lambert Conformal
Wisconsin Central 4802 Lambert Conformal
Wisconsin North 4801 Lambert Conformal
Wisconsin South 4803 Lambert Conformal
Wyomingi East 4901 Transverse Mercator
Wyoming East Central 4902 Transverse Mercator
Wyoming West 4904 Transverse Mercator
State Zone Zone No. Projection Type
R2003.12.0 Map Projection Editor: Cartographic Tables 133
OpenWorks Project Management Landmark
Wyoming West Central 4903 Transverse Mercator
a. Alaska is a special case with one Oblique Mercator zone for its panhandle, eight Transverse Mercator zones for the bulk of the state, and one Lambert Conformal zone for the Aleutian Islands. The Transverse Mercator zones are numbered from east to west.
b. California’s seven Lambert Conformal zones are numbered from north to south. California’s Zone VII was dropped in 1983. The CRS supplied if you select Zone VII is the 1927 CRS except that the 1983 spheroid (GRS 80) is used.
c. Hawaii’s five Transverse Mercator zones are numbered from east to west.
d. Michigan was zoned twice, once vertically with three transverse Mercator zones, now considered to be obsolete, and once horizontally with three Lambert Confor-mal zones.
e. Montana became one zone in 1983. If you select Montana North or Montana South, the CRS supplied is the CRS for the merged zone.
f. Nebraska became one zone in 1983. If you select Nebraska North or Nebraska South, the CRS supplied is the CRS for the merged zone.
g. Samoa was not changed to the 1983 datum. If you select Samoa, the same CRS is supplied as the 1927 CRS, except that the 1983 spheroid (GRS 80) is used.
h. South Carolina became one zone in 1983. If you select South Carolina North or South Carolina South, the CRS supplied is the CRS for the merged zone.
i. Wyoming systems for 1983 were not resolved as of 1987. If you select Wyoming East, Wyoming East Central, Wyoming West, or Wyoming West Central, the CRS supplied is the same as the 1927 version except that the 1983 spheroid (GRS 80) is used.
State Zone Zone No. Projection Type
134 Map Projection Editor: Cartographic Tables R2003.12.0
Landmark OpenWorks Project Management
Table 5: Parameters of the State Plane Coordinate Systems (Excerpt)
The following excerpt is provided as a sample of the format and content of the Table of the Parameters of the State Plane Coordinate Systems. The table itself is an option available for selection from the Cartographic Tables Menu. It consists of 135 parameter tables, one for each of the State Plane Coordinate System zones. The approximate center of each zone is shown after the @ symbol. The DIF? column flags differences between the 1927 datum and the 1983 datum.
1 ALABAMA EAST 101, Transverse Mercator
@ (32~50'N, 85~50'W) .........1927 DATUM................1983 DATUM........DIF?
1 Semi-major axis, meters = 6,378,206.400,00 6,378,137 D 2 Eccentricity squared = 0.006,768,657,997 0.006,694,380,023 D 3 Longitude, central meridian = 85~50'00.0000" W 85~50'00.000" W 4 Scale factor at cent. merid. = 0.999,960,000,000 0.999,960,000,000 5 Not used = 0 0 6 Not used = 0 0 7 Latitude, projection origin = 30~30'00.0000" N 30~30'00.0000" N 8 False easting, meters = 152,400.304,801 200,000 D
feet = 500,000 656,167.979,003 D 9 False northing, meters = 0 0
feet = 0 0 • • • • • • • • • • • •
135 WYOMING WEST CENTRAL 4903, Transverse Mercator
@ (43~00'N,108~45'W) .....................1927 DATUM................1983 DATUM........DIF?
1 Semi-major axis, meters = 6,378,206.400,00 6,378,137 D 2 Eccentricity squared = 0.006,768,657,997 0.006,694,380,023 D 3 Longitude, central meridian = 108~45'00.0000" W 108~45'00.000" W 4 Scale factor at cent. merid. = 0.999,941,176,471 0.999,941,176,471 5 Not used = 0 0 6 Not used = 0 0 7 Latitude, projection origin = 40~40'00.0000" N 40~40'00.0000" N 8 False easting, meters = 152,400.304,801 152,400.304,801
feet = 500,000 500,001.000,002 9 False northing, meters = 0 0
feet = 0 0
R2003.12.0 Map Projection Editor: Cartographic Tables 135
OpenWorks Project Management Landmark
Table 6: Universal Transverse Mercator Longitude Zones
The UTM longitude zones can be designated in either eastern or western coordinates. This table gives the equivalent coordinates for these two ways of designating each zone.
Zone Number
Zone Specification in Eastern
Coordinates
Zone Specification in Western Coordinates
1 180°E to 186°E 174°W to 180°W
2 186°E to 192°E 168°W to 174°W
3 192°E to 198°E 162°W to 168°W
4 198°E to 204°E 156°W to 162°W
5 204°E to 210°E 150°W to 156°W
6 210°E to 216°E 144°W to 150°W
7 216°E to 222°E 138°W to 144°W
8 222°E to 228°E 132°W to 138°W
9 228°E to 234°E 126°W to 132°W
10 234°E to 240°E 120°W to 126°W
11 240°E to 246°E 114°W to 120°W
12 246°E to 252°E 108°W to 114°W
13 252°E to 258°E 102°W to 108°W
14 258°E to 264°E 96°W to 102°W
15 264°E to 270°E 90°W to 96°W
16 270°E to 276°E 84°W to 90°W
17 276°E to 282°E 78°W to 84°W
18 282°E to 288°E 72°W to 78°W
19 288°E to 294°E 66°W to 72°W
20 294°E to 300°E 60°W to 66°W
21 300°E to 306°E 54°W to 60°W
22 306°E to 312°E 48°W to 54°W
23 312°E to 318°E 42°W to 48°W
24 318°E to 324°E 36°W to 42°W
25 324°E to 330°E 30°W to 36°W
136 Map Projection Editor: Cartographic Tables R2003.12.0
Landmark OpenWorks Project Management
26 330°E to 336°E 24°W to 30°W
27 336°E to 342°E 18°W to 24°W
28 342°E to 348°E 12°W to 18°W
29 348°E to 354°E 6°W to 12°W
30 354°E to 360°E 0°W to 6°W
31 0°E to 6°E 354°W to 360°W
32 6°E to 12°E 348°W to 354°W
33 12°E to 18°E 342°W to 348°W
34 18°E to 24°E 336°W to 342°W
35 24°E to 30°E 330°W to 336°W
36 30°E to 36°E 324°W to 330°W
37 36°E to 42°E 318°W to 324°W
38 42°E to 48°E 312°W to 318°W
39 48°E to 54°E 306°W to 312°W
40 54°E to 60°E 300°W to 306°W
41 60°E to 66°E 294°W to 300°W
42 66°E to 72°E 288°W to 294°W
43 72°E to 78°E 282°W to 288°W
44 78°E to 84°E 276°W to 282°W
45 84°E to 90°E 270°W to 276°W
46 90°E to 96°E 264°W to 270°W
47 96°E to 102°E 258°W to 264°W
48 102°E to 108°E 252°W to 258°W
49 108°E to 114°E 246°W to 252°W
50 114°E to 120°E 240°W to 246°W
51 120°E to 126°E 234°W to 240°W
52 126°E to 132°E 228°W to 234°W
53 132°E to 138°E 222°W to 228°W
54 138°E to 144°E 216°W to 222°W
Zone Number
Zone Specification in Eastern
Coordinates
Zone Specification in Western Coordinates
R2003.12.0 Map Projection Editor: Cartographic Tables 137
OpenWorks Project Management Landmark
55 144°E to 150°E 210°W to 216°W
56 150°E to 156°E 204°W to 210°W
57 156°E to 162°E 198°W to 204°W
58 162°E to 168°E 192°W to 198°W
59 168°E to 174°E 186°W to 192°W
60 174°E to 180°E 180°W to 186°W
Zone Number
Zone Specification in Eastern
Coordinates
Zone Specification in Western Coordinates
138 Map Projection Editor: Cartographic Tables R2003.12.0
Landmark OpenWorks Project Management
Test Conversion Example
This section contains an example of a test conversion from one CRS to another CRS.
The example shows how the Map Projection Editor’s Test Conversion feature can be used to test the integrity of a CRS defined with the Cartographic Reference System Editor.
The example tests a polyconic CRS that implements the polyconic model described in the U.S.G.S. technical publication Map Projections—A Working Manual.
Understanding the Example
To understand this example, refer to Table 19 on pages 132 and 133 of Map Projections—A Working Manual. This table shows a polyconic projection of latitude-longitude (degrees) to (x, y) (meters) over a rectangular latitude-longitude grid. The grid has 28 latitude values ranging from 28° to 50°, and four longitude values ranging from 0° to 3°. The projection employs a Clarke 1866 spheroid. The natural origin of the projection is 0° latitude, 0° longitude.
A portion of Table 19 is reproduced below, with the y values shown in parentheses below the x values.
Polyconic Projection Rectangular Coordinates
Longitude λ
Latitude Φ0° 1° 2° 3°
50 0(5,540,628) 1.000000
71,696(5,541,107)1.000063
143,379(5,542,545) 1.000252
215,037 (5,544,941) 1.000568
49 0 (5,429,409) 1.000000
73,172 (5,429,890) 1.000066
146,331 (5,431,336) 1.000263
219,465 (5,433,745) 1.000592
48 0 (5,318,209) 1.000000
74,626 (5,318,693) 1.000068
149,239 (5,320,144) 1.000274
233,827 (5,322,564) 1.000616
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
R2003.12.0 Map Projection Editor: Test Conversion Example 139
OpenWorks Project Management Landmark
To perform the test transform, a CRS definition was created that duplicates the projection used in the U.S.G.S. calculations shown in this table. The CRS definition differs from the U.S.G.S projection only in the following respect: the longitude origin in the CRS definition is 100°W rather than 0°. This adjustment enables the test to confirm that x coordinates are relative to the central meridian. As a result of this adjustment, the table longitudes of 0°, 1°, 2°, and 3° should correspond to the CRS definition longitudes of -100°, -99°, -98°, and -97°.
25 0 (2,765,896) 1.000000
100,951 (2,766,269) 1.000126
201,896 (2,767,386) 1.000503
302,831 (2,769,247) 1.001132
24 0 (2,655,136) 1.000000
101,753 (2,655,497) 1.000128
203,500 (2,656,580) 1.000511
305,237 (2,658,386) 1.001150
23 0 (2,544,390) 1.000000
102,523 (2,544,739) 1.000130
205,042 (2,545,788) 1.000519
307,551 (2,547,536) 1.001168
Polyconic Projection Rectangular Coordinates
Longitude λ
Latitude Φ0° 1° 2° 3°
140 Map Projection Editor: Test Conversion Example R2003.12.0
Landmark OpenWorks Project Management
Defining the Example
The parameters used to define the polyconic CRS used in this test are shown below.
Polyconic CRS Definition
R2003.12.0 Map Projection Editor: Test Conversion Example 141
OpenWorks Project Management Landmark
Performing the Test
To perform the coordinate transformation test, the Test Conversion window was filled out as shown in the following illustration. These entries duplicate the test points of Table 19. The only defaults pertinent in this case were the angular increments of 1°. Note that the center point of this pattern (latitude 36.5, longitude -98.5) is not one of the 112 points to be transformed.
142 Map Projection Editor: Test Conversion Example R2003.12.0
Landmark OpenWorks Project Management
Partial results of the forward conversion are shown below:
R2003.12.0 Map Projection Editor: Test Conversion Example 143
OpenWorks Project Management Landmark
Partial results of the reverse conversion are shown below:
144 Map Projection Editor: Test Conversion Example R2003.12.0
Landmark OpenWorks Project Management
The statistical summary for the transformation is shown below.
The least significant digits may vary from platform to platform due to different floating point implementations.
This statistical summary demonstrates that the greatest round trip error was on the order of |-2.5x10-9| degrees.
Since the input angles were on the order of 10+2 degrees, the round trip calculations were good to about 16 decimal places in the worst case. Double precision is usually good to about 17 places; therefore, all of the observed error may be attributed to round-off which did not get significantly magnified by the transformation algorithms.
Not all of the CRS type algorithms exhibit such precise performance. Errors will vary with the dimensions and placement of the test pattern.
R2003.12.0 Map Projection Editor: Test Conversion Example 145
OpenWorks Project Management Landmark
Map Projection Editor Glossary
This section contains a glossary specific to the Map Projection Editor.
azimuthal
A type of projection for which the bearing (or direction or azimuth) of any point with respect to the center is correct.
cartographic reference system (CRS)
A group of specifications that help to correctly position x-y coordinates on a map. The specifications include projection type, datum, spheroid, surface units, and parameters.
center of projection
The latitude-longitude of the projection point. See “projection point.”
central meridian
The meridian that runs through the center of interest in a given map area; the meridian on either side of which the map scale is symmetrical.
coordinate
A location on a map expressed in terms of distance from an origin (x, y) or latitude-longitude.
datum
A smooth mathematical surface that closely fits the mean sea-level surface throughout the area of interest.
easting
The x coordinate on a map grid. See also “false easting.”
ellipsoid
A flattened sphere used to approximate the surface of the earth. Note that most ellipsoids are not geocentric; their centers typically depart from that of the earth’s rotation by as much as a few
146 Map Projection Editor: Map Projection Editor Glossary R2003.12.0
Landmark OpenWorks Project Management
hundred meters. Elevations are reported relative to the geoid, not the ellipsoid.
false easting, northing
Adjustments to the origin of a grid so as to avoid negative easting and northing (x.y) values.
geocentric latitude
The angle made by a line to the center of the ellipsoid with the equatorial plane.
geodetic coordinates
A (latitude, longitude) ordered pair.
geodetic (geographic) latitude
The angle that a line perpendicular to the surface of the ellipsoid makes with the plane of the Equator. It is slightly greater than the geocentric latitude.
geoid
The shape of the Earth at mean sea level.
gnomonic projection
A perspective projection of the globe onto a plane that is tangent to the surface.
grid
A regular lattice that divides a map surface into zones. Most used in the United States are the Universal Transverse Mercator Grid and the State Plane Coordinate System. Before introduction of the UTM, the World Polyconic Grid was popular.
map coordinate
An (x, y) ordered pair.
R2003.12.0 Map Projection Editor: Map Projection Editor Glossary 147
OpenWorks Project Management Landmark
Mercator projection
A classic cylindrical projection in which all meridians and parallels are represented as straight vertical and horizontal lines. Many world maps use the Mercator projection.
origin
The central reference point on a map, from which all coordinates are measured (x = 0, y = 0).
orthographic
A projection onto a plane that is tangent to the earth’s surface, but from a perspective point that is an infinite distance from the earth. This perspective produces an almost photographic view of the globe.
northing
The y coordinate on a map grid. See also “false northing.”
perspective point
A point above, at, or below the surface of the earth used as a central origination point for all lines of projection.
projection, projection type
The method used to project the curved surface of the earth onto the flat surface such as a plane, cylinder, or cone. For example, a Miller cylindrical projection is a type of projection in which the surface of the earth is projected onto a cylinder and then adjusted mathematically to reduce the vertical distortion.
spheroid
A spherical shape, sometimes called an “ellipsoid.”
standard parallel
The parallel at which the projection cylinder or cone intersects the surface of the earth. This intersection may occur at a single parallel or at two parallels (if the projection surface penetrates the earth).
148 Map Projection Editor: Map Projection Editor Glossary R2003.12.0
Landmark OpenWorks Project Management
stereographic
A projection onto a plane that is tangent to the earth’s surface, but from a perspective point that is on the opposite side of the globe. (The perspective lines go through the earth and emerge on the other side before striking the tangent plane.)
surface measure
The labelled dimensions of observations. A distance might be given in terms of feet or kilometers, among other units; a pressure in dynes per square centimeter or kilopascals.
x-y or x, y
The measurements in an east-west (X) or north-south (Y) direction from a point of origin. Also called “easting-northing.”
zone
A predefined map area.
R2003.12.0 Map Projection Editor: Map Projection Editor Glossary 149
OpenWorks Project Management Landmark
150 Map Projection Editor: Map Projection Editor Glossary R2003.12.0
Landmark OpenWorks Project Management
Measurement System Manager
Overview
The Measurement System Manager allows you to create a customized measurement system for a new OpenWorks project that you plan to define subsequently.
This chapter includes the following topics:
• Launching Measurement System Manager on page 152
• Creating a New Measurement System on page 153
• Deleting Unused Measurement Systems on page 158
R2003.12.0 Measurement System Manager 151
OpenWorks Project Management Landmark
Launching Measurement System Manager
To run this utility, you must log on as an OpenWorks user who:
• is an External Oracle user with the OW_ADMINISTRATOR role in the Oracle database, and
• has been granted MANAGE access to the OpenWorks project.
Use the following steps to launch the Measurement System Manager:
• UNIX—From the OpenWorks Command Menu, select Project > Measurement System Manager.
• Windows—From the Start menu, select Programs > Landmark OpenWorks > Project Administration > Measurement System Manager.
The Measurement System Manager window appears as shown below.
When you are finished using the Measurement System Manager, select Meas. System > Exit.
152 Measurement System Manager: Launching Measurement System Manager R2003.12.0
Landmark OpenWorks Project Management
Creating a New Measurement System
This section explains the requirements for defining a new measurement system and shows an example.
When creating an OpenWorks project, as one requirement you must specify the measurement system that the new project will use. Four standard measurement systems are available choices:
• US Oil Field• SPE Preferred Metric• US Oil Field (metric depth)• Canadian Metric
Sometimes, however, your project needs to have one or more measurements taken in units that differ from those in any standard system you might choose. For such situations, the Measurement System Manager enables you to define a customized measurement system.
When defining a new measurement system, you should use as a template the standard system that most nearly matches the units your project will use. You will then modify only those measurements that need to use different units.
In the Measurement System Manager window, the Unit Types column lists the complete set of measurements types available to an OpenWorks project. In addition, the UNKNOWN type contains a list of items for which no measurement exists in any standard system. These unknowns will remain unknown in new measurement systems that you create.
Create a new measurement system before you define the project that uses it.
If you need a customized measurement system, define it first. OpenWorks does not allow you to change the measurement system of an existing project.
Also, be reassured that defining a new measurement system has no effect whatsoever on the OpenWorks project currently in use.
R2003.12.0 Measurement System Manager: Creating a New Measurement System 153
OpenWorks Project Management Landmark
1. To begin defining a new system, select Meas. Systems > Create Meas. Sys.
2. Then, in the Create New Measurement System window that appears, define a name for your new system, and click on the name of the standard system you want to use as the template for your new system.
When you click on OK, the Measurement System Manager creates a column for your new system, which contains the measurement units of the standard system you specified, as shown for Gulf Sys A1 in the next illustration.
154 Measurement System Manager: Creating a New Measurement System R2003.12.0
Landmark OpenWorks Project Management
You can now change any of the measurement units shown for your customized system, as appropriate. To assist in this process, you may want to see where various Unit Types are used by the project.
For example, if you click on the button in the Columns column beside the unit type “area earth surface,” the following window appears. You can click on any line to make the correspondence between
R2003.12.0 Measurement System Manager: Creating a New Measurement System 155
OpenWorks Project Management Landmark
a table and column more legible, if you wish. However, highlighting a row has no effect on the definition of a new measurement system.
The Tables/Columns dialogs show the structure of a project. When a new project is created, a predefined set of tables and columns is automatically established by OpenWorks. The user subsequently decides whether any given type of measurement is appropriate for the project and hence whether any data will be defined in those tables or columns.
For your current purposes, viewing the tables and columns that can contain an “area earth surface” measurement might help you decide whether your new system should retain its default measurement units or whether you should change the units. For example, the default units for measuring “area earth surface” in the new Gulf Sys A1 system are square kilometers (km2).
When you finish viewing the Tables/Columns dialog, click OK to close the dialog.
To see your options for changing km2, select Edit > Valid Values to open the following window of valid values.
Alternatively, you could open this window by pressing UNIX Mouse Button 3/NT Right Mouse Button
156 Measurement System Manager: Creating a New Measurement System R2003.12.0
Landmark OpenWorks Project Management
in the km2 cell in the “area earth surface” row of the Gulf Sys A1 column.
The List of Valid Values for measuring “area earth surface” appears. You could, for example, decide to record these measurements as square miles (mi2), by clicking on the mi2 row and on OK, as illustrated.
A similar process can be repeated to select a different measurement unit for any of the other Unit Types, as appropriate.
3. To save your changes, select Meas. Systems > Save.
When you subsequently open the Measurement System Manager, all measurement systems that you have defined will display, along with the
R2003.12.0 Measurement System Manager: Creating a New Measurement System 157
OpenWorks Project Management Landmark
four standard systems. If needed, you can later make more changes in the units used to take measurements. However, you cannot change which measurement system is designated for an existing project.
Deleting Unused Measurement Systems
This section describes the procedure for deleting an unneeded measurement system.
If you want to discard a measurement system that is not yet used by an OpenWorks project, select Meas. Systems > Delete.
The following window opens, listing all existing measurement systems you have created. Click the name of the system you want to delete, and click OK.
You will not be permitted to delete a customized measurement system that is used by an existing project. Also, be aware that you cannot change or delete any of the four standard measurement systems.
158 Measurement System Manager: Deleting Unused Measurement Systems R2003.12.0
Landmark OpenWorks Project Management
Converting Projects to Release 2003
Overview
This chapter describes the process of converting OpenWorks projects from Release 1998.x to Release 2003. No changes are needed for Release 2003.3.
Release 2003 applications require a Release 2003 data model. Release 1998.x data models must be converted to the Release 2003 data model before they are usable in Release 2003.
OpenWorks 2003 does not support conversion of OpenWorks projects prior to Release 1998.
The steps described in this chapter are performed after Oracle 8.1.6 and OpenWorks 2003 are installed. Landmark highly recommends backing up all projects before installing these products.
What’s in this Chapter
This chapter contains the following major sections:
• Determining if a Project Has Been Converted on page 160
Converting a project to OpenWorks 2003 can be performed:
• automatically the first time a project is opened by an OpenWorks 2003 application. See Automatically Converting Single Projects on page 162.
• project-by-project using a command line script. See Command Line Script to Convert Projects on page 163.
• Multiple projects can be converted in batch. See Converting Multiple Projects in Batch on page 164
• If problems occur, see Correcting Incomplete Project Conversions on page 165
R2003.12.0 Converting Projects to Release 2003 159
OpenWorks Project Management Landmark
Determining if a Project Has Been Converted
OpenWorks projects which have been converted to Release 2003 will have the RELEASE_ID column of the ow_prj_release table set to VERSION 6.0.
To check project PROJECT_NAME on database OW_SID_NAME, type the following in a UNIX or Command Prompt window:
sqlplus /@OW_SID_NAMEalter session set current_schema=PROJECT_NAME;set role manage_PROJECT_NAME;select * from ow_prj_release where release_id = ‘VERSION 6.0’;
For example:
sqlplus /@ownovaalter session set current_schema=flounder;set role manage_flounder;select * from ow_prj_release where release_id = ‘VERSION 6.0’;
• If the project has been converted, the screen will look like this:
PROJECT_NAME RELEASE_ID INSTALL_D-------------------- -------------------------------- ---------INSTALL_USER_ID REVISION-------------------------------- --------------------------------PROJECT VERSION 6.0 23-FEB-01OPENWORKS REVISION 0
• If the project has not been extended, the screen will look like this:
no rows selected
Determining the History of a Project
To check the upgrade history of an OpenWorks project, type the following in a UNIX or Command Prompt window:
sqlplus /@OW_SID_NAMEalter session set current_schema=PROJECT_NAME;set role manage_PROJECT_NAME;select * from ow_prj_release;
160 Converting Projects to Release 2003: Determining if a Project Has Been Converted
Landmark OpenWorks Project Management
The screen will look similar to this:
PROJECT_NAME RELEASE_ID INSTALL_D-------------------- -------------------------------- ---------INSTALL_USER_ID REVISION-------------------------------- --------------------------------PROJECT VERSION 4.0 15-FEB-96OPENWORKS
PROJECT VERSION 4.1.2 06-MAR-98OPENEXPLORER
PROJECT VERSION 5.0 20-AUG-99OPENWORKS REVISION 5
PROJECT VERSION 6.0 30-JAN-01OPENWORKS REVISION 0
In this example, the project was originally created on February 15, 1996 using OpenWorks 1998 (version 4.0). In March 1998, it was upgraded to OpenWorks 4.1.2 for use with Landmark’s OpenExplorer 1.0 software.
In August 1999 the project was upgraded to OpenWorks 1998.5 (version 5.5). In January 2001 it was converted to OpenWorks 2003 (version 6.0).
R2003.12.0Converting Projects to Release 2003: Determining if a Project Has Been Converted 161
OpenWorks Project Management Landmark
Automatically Converting Single Projects
For most OpenWorks users, automatic conversion is the most convenient method of extending projects.
After installing OpenWorks 2003, simply launch an OpenWorks application, such as Well Data Manager, and select the project you want to extend.
When the application detects that the project it has opened is at a Release 1998.x level, the Automatic Model Conversion Dialog will open.
This dialog will indicate that the project is at “release “5.0 revision x”, and that “release 6.0 revision 0” is required. Click on the Continue button in the dialog to convert the project. The conversion process may take 20 or more minutes to run.
When the process is complete, if an error is recognized, you will be informed via a popup message, and the application will exit. Otherwise the application will continue running normally.
162 Converting Projects to Release 2003: Automatically Converting Single Projects R2003.12.0
Landmark OpenWorks Project Management
Command Line Script to Convert Projects
Individual OpenWorks projects can be converted to Release 2003 by using a script with the appropriate command line arguments. The script is located in $OWHOME/bin.
To run this utility, you must log on as an OpenWorks user who:
• is an External Oracle user with the OW_ADMINISTRATOR role in the Oracle database, and
• has been granted MANAGE access to the OpenWorks project
The extendToOW6Rev0 script uses the following syntax:
extendToOW6Rev0 PRJNAME PRJSID TEMPDIR OWSYSPASSWD OWSYSSID
where:
PRJNAME is the name of the OpenWorks project.
PRJSID is the database instance the project resides on.
TEMPDIR is the full path to a directory to which log and temporary files can be written.
OWSYSPASSWD is the password of the owsys login for the OWSYSSID.
OWSYSSID is the database instance that has the owsys information for this project.
Project Tablespace
The project conversion script automatically turns on Oracle’s AUTOEXTEND to avoid a project running out of space during conversion. After conversion, AUTOEXTEND is returned to its previous state.
In order to allow the script to automatically turn AUTOEXTEND on, set the following variables:
setenv OW_DBA_USER <dba user>
setenv OW_DBA_PASSWD <dba user password>
R2003.12.0 Converting Projects to Release 2003: Command Line Script to Convert Projects 163
OpenWorks Project Management Landmark
System Tablespace
The convert script does not automatically turn on AUTOEXTEND for the system and other tablespaces. The database administrator should boost these tablespaces manually, or turn on AUTOEXTEND by doing the following:
% su - <oracle user>% cd $ORACLE_HOME/lgcowdb% sqlplus sys/<sys password>@<oracle SID name>SQLPLUS> @turn_on_autoextend.sqlSQLPLUS> exit
Log File
A log file will be created in the temporary directory with the name:
PRJNAME.log
Converting Multiple Projects in Batch
Multiple projects can be converted in batch by creating a script containing the convert script and arguments for each project. Set the AUTOEXTEND variables in the script.
164 Converting Projects to Release 2003: Converting Multiple Projects in Batch R2003.12.0
Landmark OpenWorks Project Management
Correcting Incomplete Project Conversions
If a project conversion is aborted or interrupted midway through, a subsequent attempt to access the project will recognize the conversion did not finish and will attempt to convert the project properly. However, depending on when the interruption occurred, the conversion program may think that the project is currently undergoing a conversion and will exit after starting.
Use the following steps to convert the project properly:
1. As a manager in the project, in the OpenWorks environment, for a project named PROJECT_NAME on database OW_SID_NAME, type the following in a UNIX window:
sqlplus /@OW_SID_NAME
alter session set current_schema=PROJECT_NAME;
set role manage_PROJECT_NAME;
delete from ow_prj_release where release_id = ‘VERSION 2003 Extend underway’;
commit;
exit;
2. Convert the project, either automatically (page 162) or using the single project conversion script (page 163).
Each project that requires this modification must be converted as an individual project; the script which converts all projects cannot be used.
R2003.12.0 Converting Projects to Release 2003: Correcting Incomplete Project Conversions 165
OpenWorks Project Management Landmark
166 Converting Projects to Release 2003: Correcting Incomplete Project Conversions R2003.12.0
Landmark OpenWorks Project Management
Vector Data Converter Utilities
Overview
OpenWorks 2003 provides two new utilities to convert vector data (for example, log curves) in OpenWorks projects from the Oracle 7.3.4 binary representation to the new, more performant Large Object form supported in Oracle 8.1.6. This new vector format provides faster data access for very large arrays.
What’s in this Chapter
This chapter contains the following major topics:
• Usage on page 168
• Procedure on page 169
• Example on page 171
R2003.12.0 Vector Data Converter Utilities 167
OpenWorks Project Management Landmark
Usage
The two utilities and syntax are:
exportVec.sh OWproject vectorDirectoryimportVec.sh OWproject vectorDirectory
Where:
exportVec.sh is the utility to export vectors from a project
importVec.sh is the utility to import vectors that were originally exported by exportVec.sh into a project
OWproject is the name of the OpenWorks project on the default SID (selected either via an OpenWorks application, or using the ORACLE_SID environment variable)
vectorDirectory is a pre-existing temporary directory that the user assigns to hold the vector data while it is exported and imported
The utilities generate the following log files:
vectorDirectory/OWproject/exportVec.logvectorDirectory/OWproject/importVec.log
• The X windows DISPLAY variable must be set in order to obtain the correct OpenWorks session settings.
• The export utility will fail if insufficient disk space is available to export all of the vector data.
• A log file (exportVec.log) is automatically created in the vector directory. Use it to verify the success of the export.
• If no export errors occur, import the vector data files back in to the project, replacing the existing vectors with the newer, faster format. The import log file is importVec.log.
• After the database vectors have been verified in their new form, the vector data files in the vector directory can be deleted.
168 Vector Data Converter Utilities: Usage R2003.12.0
Landmark OpenWorks Project Management
Procedure
The export utility can be run by any user who has access to the project.
To run the import utility, you must log on as an OpenWorks user who:
• is an External Oracle user with the OW_ADMINISTRATOR role in the Oracle database, and
• has been granted MANAGE access to the OpenWorks project
Use the following steps to convert vector data.
1. Back up the OpenWorks project. The export utility does not alter the project or its contents.
2. Enter the following commands in a UNIX or Windows window:
mkdir vectorDirectory chmod 777 vectorDirectoryexportVec.sh OWproject vectorDirectory
• The script creates a directory called vectorDirectory/OWproject.
• The export utility gets ORACLE_SID from the environment. If ORACLE_SID is not set in the environment, the utility will use the OWSYSSID setting in the $OWHOME/conf/lgcenv.cf file.
3. Check the export log file
more vectorDirectory/OWproject/exportVec.log
• If there are no errors listed in vectorDirectory/OWproject/exportVec.log, the export was successful.
• If sufficient disk space is not available to export all of the vector data, exportVec.sh will fail and a message to that effect will be written to the log file
• Export does not alter the project or it's contents, therefore no steps are required to get back to where you were before you exported. You may want to clean up the vectorDirectory to reclaim any space that was used during the export.
R2003.12.0 Vector Data Converter Utilities: Procedure 169
OpenWorks Project Management Landmark
4. Import the vector data
importVec.sh OWproj vectorDirectory
• The import utility gets ORACLE_SID from the environment. If ORACLE_SID is not set in the environment, the utility will use the OWSYSSID setting in the $OWHOME/conf/lgcenv.cf file.
• If Oracle is not able to extend the tablespace, the import utility will display the Oracle message indicating this.
• The utility will fail if it cannot find and/or read the exported data files from the vectorDirectory.
5. Check the import log file
more vectorDirectory/OWproj/importVec.log
• If there are no errors listed in vectorDirectory/OWproj/importVec.log, the import was successful.
• The import utility will fail if it cannot find and/or read the exported data files from the vectorDirectory.
6. Verify the vectors in their new form using Well Curve Viewer.
7. Remove the vectors and the directory
rm -r vectorDirectory
170 Vector Data Converter Utilities: Procedure R2003.12.0
Landmark OpenWorks Project Management
Example
For example, the following might represent an actual use:
exportVec.sh TESTDATA /pb/vectors
more /pb/vectors/TESTDATA/exportVec.log
importVec.sh TESTDATA /pb/vectors
more /pb/vectors/TESTDATA/importVec.log
In this example, the utilities would
1. create the TESTDATA subdirectory in /pb/vectors
2. export all 22 different kinds of vectors from the TESTDATA project and write them out as vector data files in the /pb/vectors/TESTDATA directory
3. import all 22 different kinds of vectors to the TESTDATA project
R2003.12.0 Vector Data Converter Utilities: Example 171
OpenWorks Project Management Landmark
172 Vector Data Converter Utilities: Example R2003.12.0
Landmark OpenWorks Project Management
Project Administration
Overview
You must select an OpenWorks project to use in most Landmark applications and utilities. You can create as many projects as needed to hold different sets of data for different well sites or geographic regions. If you are a new user, please read this chapter carefully before using any of the Project Administration utilities.
What’s in this Chapter
This chapter explains how to use the OpenWorks Project Admin utility to modify, delete, backup, restore, tune, and query OpenWorks projects. This section also describes how to add or remove users from a project, and how to change user access.
All of these tasks can be performed using the Project Administration tool, as explained on the following topics:
• Launching Project Administration on page 174
• Creating a Project on page 175
• Modifying a Project on page 175
• Deleting a Project on page 178
• Backing Up OpenWorks Projects on page 180
• Restoring OpenWorks Projects on page 186
• Managing Project Access on page 191
• Checking Tablespace and User Access in Projects on page 196
• Tuning Projects on page 197
R2003.12.0 Project Administration 173
OpenWorks Project Management Landmark
Launching Project Administration
To run this utility, you must log on as an OpenWorks user who:
• is an External Oracle user with the OW_ADMINISTRATOR role in the Oracle database, and
• has been granted MANAGE access to the OpenWorks project
Use the following steps to launch the Project Administration utility:
• UNIX—From the OpenWorks Command Menu, select Project > Project Admin.
• Windows—From the Start menu, select Programs >Landmark OpenWorks > Project Administration > Project Admin.
The Project Administration window opens.
This window contains a list of projects available on the current Oracle instance, and two pull-down menus that let you manage various aspects
174 Project Administration: Launching Project Administration R2003.12.0
Landmark OpenWorks Project Management
of the projects. The functions listed on these menus are explained on the following pages.
To exit Project Administration, select Project > Exit in the Project Administration window.
Creating a Project
OpenWorks allows you to create new OpenWorks projects from the Project Administration utility by selecting Project > Create from the Project menu. The Project Create window will open.
For more information about creating OpenWorks projects, see “Project Create” on page 201.
You can also launch Project Create as follows:
• UNIX—From the OpenWorks Command Menu, select Project > Project Create.
• Windows— From the Start menu, select Programs > Landmark OpenWorks > Project Create.
Modifying a Project
After you create an OpenWorks project, you can modify the project description, the project extent, the default map projection, scale and reference elevation, and the amount of disk space allocated to the project.
Use the following steps to modify a project.
1. Select the project in the Project Administration window; then select Project > Modify.
Starting Project Administration from the UNIX Command Line
You can also start the Project Administration utility by typing the following command in the console window or any xterm window:
admprj
R2003.12.0 Project Administration: Creating a Project 175
OpenWorks Project Management Landmark
The Project Administration: Modify window opens.
2. Change the following project information as needed.
Description. Edit the description, or enter a new one.
Areal Extent. Change the latitude and longitude of the project area geographic boundaries as needed. You can enter the coordinates as decimal numbers by clicking the Decimal button or as degrees-minutes-seconds by clicking the Deg-Min-Sec button. When you select a button, the entry fields change appropriately. Click Compute to compute the project boundaries based on the data currently loaded in the project. For more details on these entries, see page 212.
Default Display Parameters. Change the default display parameters that are used for display of map data, if desired. You can select a different map projection system from the list or
176 Project Administration: Modifying a Project R2003.12.0
Landmark OpenWorks Project Management
specify a new map scale factor or reference elevation. For more details on these entries, see page 210.
Disk Space Allocation. You can see the current size of the project and the amount of available free space in the database. These fields are not editable. However, you can allocate more tablespace for the project. Click By Size or By Location then click Add Project Space.
• If you select By Size, the Add Project Space window opens. Enter the amount of additional space desired for the project; then click OK.
• If you select By Location, the Add Space By Location window opens. Specify additional space at selected database
Note: Adding additional space to a project does not set the autoex-tend option on the new tablespace datafiles
Even if the autoextend setting is on for the project, you must turn the autoextend option on for the new space. See “Configuring AUTOEXTEND for Project Data Files” in the OpenWorks Managing the System manual.
R2003.12.0 Project Administration: Modifying a Project 177
OpenWorks Project Management Landmark
locations, as shown below, and then click OK.
3. When you have finished modifying the project, click OK in the Project Administration: Modify window.
Deleting a Project
You can delete any OpenWorks project that you have created. Deleting removes the project and all associated data and references from the database.
To delete an OpenWorks project:
1. Select the project in the Project Administration window, and then select Project > Delete.
2. When the confirmation message box appears, click OK.
• If you own the project it will be deleted.
• If you do not own the project you are trying to delete, an error message box will open. Click OK. The project owner must either delete the project or grant you access to the project so that you can delete it. For more information, refer to “Managing Project Access” on page 191.
178 Project Administration: Deleting a Project R2003.12.0
Landmark OpenWorks Project Management
Deleting Projects Using a Command Line Utility
The owdelete program is a command line utility that allows you to delete an OpenWorks project.
owdelete can be run from any command line interface using the arguments shown below. The program will work both with and without X running.
Usage:
owdelete <project_name>
Arguments:
Examples:
UNIX:
$OWHOME/bin/owdelete TESTDATA
Windows:
%OWHOME%\bin\owdelete TESTDATA
project name: the name of the project to delete
R2003.12.0 Project Administration: Deleting a Project 179
OpenWorks Project Management Landmark
Backing Up OpenWorks Projects
Practically all OpenWorks project data, including seismic navigation data, is stored in the Oracle database. However, OpenWorks does store certain types of data, notably TDQ velocity models and culture data, in external project files. SeisWorks and StratWorks also store some data in external project files.
The directories containing these files are specified by a file called $OWHOME/conf/owdir.dat, which is created when OpenWorks is installed. (For more information about the owdir.dat file, refer to the Managing the System manual.)
When you back up an OpenWorks project, you can back up only the database tables, only the external project files, or both. Because you are dealing with different data formats, you create two backup files: the database tables are written to (and restored from) an Oracle export file. The external project files are written to (and restored from) a tar file.
You can back up to any directory or storage device on the network. Backing up an OpenWorks project copies all project data to the desired location in a binary (coded) format. Project data copied in this manner can be restored to the project database using the Restore function discussed later in this chapter (page 186).
Warnings: Before you back up projects…
1. Make sure adequate space is available in the backup directory or on the backup device to store all backup files.
2. Make sure no other users are accessing the project when you begin the backup process.
3. If you select a storage device as the backup location, the device must be loaded with a tape or other appropriate medium and be ready to record the backup data.
Backing up SeisWorks projects.
The OpenWorks Backup utility does not back up SeisWorks projects. Use the Seismic Project Manager Backup/Restore utility to perform this task. Refer to the Seismic Project Utilities manual for details on the UNIX installation.
180 Project Administration: Backing Up OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
Backing Up Using the Graphical User Interface
To back up an OpenWorks project, do the following:
1. Select the OpenWorks project in the Project Administration window.
2. Select Project > Back Up. The Backup Type window opens.
3. Select the type of backup to perform, then click OK.
R2003.12.0 Project Administration: Backing Up OpenWorks Projects 181
OpenWorks Project Management Landmark
The appropriate backup window opens. In the example below, the All Project Data option was chosen.
4. Specify the backup media for the database tables:
• Click on File to back up to a specific file and directory, and then type the filename in the text field; or click List to select the filename from a list.
• Click on Device to back up to a logical device, and then type the device name in the text field; or click List to select the device from a list.
5. Specify the backup media for the flat file:
• Click on File to back up to a specific file and directory, and then type the filename in the text field; or click List to select the filename from a list.
• The Device option is not yet available; it will be implemented in a future release.
182 Project Administration: Backing Up OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
6. Click OK.
A confirmation message much like the example below appears:
7. Click OK. The backup may take from a few minutes to an hour depending on disk access and project size.
R2003.12.0 Project Administration: Backing Up OpenWorks Projects 183
OpenWorks Project Management Landmark
Backing Up Projects Using a Command Line Utility
owbackup
The owbackup program is a command line utility that allows you to back up the database tables in an OpenWorks project to a disk file. External files are not backed up, and external devices are not available.
owbackup can be run from any command line interface using the arguments shown below. The program will work both with and without X running.
To run owbackup as a cron job, you must first set OWHOME, ORACLE_HOME, and ORACLE_SID. OWSYSSID also must be set if it is not correctly set in $OWHOME/conf/lgcenv.cf.
Usage:
owbackup <project_name> <backup_file_name>
Arguments:
Examples:
UNIX:
$OWHOME/bin/owbackup TESTDATA $HOME/backup/TESTdata.dmp
$OWHOME/bin/owbackup WERTZ /backup/WERTZ-’date +”%d-%b-%y”’
Windows:
%OWHOME%\bin\owbackup TESTDATA D:\backups\TESTdata.dmp
project name: the name of the project to back up
backup file name: the name of the backup file
184 Project Administration: Backing Up OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
owbackup-all
The owbackup-all program is a command line utility that allows you to back up all of the OpenWorks project in a directory to which you have manage access to a disk file. External files are not backed up, and external devices are not available.
owbackup-all backs up each project in the specified directory using a file name consisting of the project name and an extension.
owbackup-all can be run from any command line interface using the arguments shown below. The program will work both with and without X running.
To run owbackup-all as a cron job, you must first set OWHOME, ORACLE_HOME, and ORACLE_SID. OWSYSSID also must be set if it is not correctly set in $OWHOME/conf/lgcenv.cf.
Usage:
owbackup-all <directory_name> [<extension>]
Arguments:
Examples:
UNIX:
$OWHOME/bin/owbackup-all /pa/backups
$OWHOME/bin/owbackup-all /export/home/backups ow987.bkup
Windows:
%OWHOME%\bin\owbackup-all D:\backups ow987.bkup
directory name: the directory where the backup file will be created
extension: the extension of the backup file; optional; .bkup will be used if no argument is pro-vided
R2003.12.0 Project Administration: Backing Up OpenWorks Projects 185
OpenWorks Project Management Landmark
Restoring OpenWorks Projects
The Restore option in Project Administration lets you restore OpenWorks projects that were backed up using the Backup option. You can restore a project to its previous condition, or create a new project.
The same functionality is also available in a command line utility. See “Restoring Using the Graphical User Interface” on page 187.
Users’ Access Preserved During Project Restores
Release 2003.3 includes an enhancement that preserves users’ access to restored projects. This improvement saves time and effort and enhances security because it eliminates the need to maintain lists of project users and their access levels.
An environment variable, RESTORE_PRJ_USERS, contained in $OWHOME/conf/lgcenv.cf causes the restore utility to retain the user and access level information contained in the project when it was backed up.
To override this variable, simply comment out the RESTORE_PRJ_USERS line in lgcenv.cf before using either version of the restore utility.
Change Limited Interpreters access before you restore projects.
If you want to make any changes to the tables that Limited Interpreters can access for this project, you must edit the ltd_interp.lst file before you restore the project for the changes to be in effect for the project.
For more information about Limited Interpreters, refer to “Managing Project Access” on page 191.
Restoring SeisWorks projects.
The OpenWorks Restore utility does not restore SeisWorks projects. Use the Seismic Project Manager Backup/Restore utility to perform this task. Refer to the Seismic Project Utilities manual for details on the UNIX installation of SeisWorks.
186 Project Administration: Restoring OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
Restoring Using the Graphical User Interface
To restore an OpenWorks project using the graphical user interface, do the following:
1. Select the OpenWorks project in the Project Administration window, and select Project > Restore. The Restore Type window opens.
2. Select the type of data you want to restore, and then click OK. The appropriate restore window opens. In the example, the All Project Data option was chosen.
R2003.12.0 Project Administration: Restoring OpenWorks Projects 187
OpenWorks Project Management Landmark
3. In the Restore Project Name field, enter a name for the restored project.
4. In the Instance field, type the Oracle instance where you want to store the restored project, or click List to select the Oracle instance from a list.
5. Use the options in the Read Oracle Backup From field to specify the source of the project database tables.
• Click on File to restore from a specific file and directory, and then type the filename in the text field; or click List to select the filename from a list.
• Click on Device to restore from a logical device, and then type the device name in the text field; or click List to select the device from a list.
6. Use the following options in the Read External Project Backup Files field to specify the source of the project flat file:
188 Project Administration: Restoring OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
• Click on File to restore from a specific file and directory, and then type the filename in the text field; or click List to select the filename from a list.
• The Device option is not available yet; it will be implemented in a future release of OpenWorks.
7. Click OK. The Project Restore window opens. Use this window to specify the size and location of the project you are restoring. There are two versions of this window, Novice and Advanced, depending on which project tablespace mode you select. Click on Advanced to specify the exact location and size of tablespace utilization, or click on Novice to describe the project size in more general terms.
• If you click Advanced, this window displays the available locations for database tablespace and the remaining space available. Enter the amount of space for the restored project to be distributed over each location. A total box shows the total amount of space you have specified.
• If you click Novice, select Small, Medium, or Large. The approximate sizes are shown for each selection.
8. Click OK. The restore process may take several minutes to complete. If you selected a device as the source of the restored data, make sure the correct tape or storage medium is loaded before you click OK.
R2003.12.0 Project Administration: Restoring OpenWorks Projects 189
OpenWorks Project Management Landmark
Restoring Using a Command Line Utility
The owrestore program is a command line utility that allows you to restore the database tables in an OpenWorks project that have been backed up to a disk file. External files are not restored, and external devices are not available.
owrestore can be run from any command line interface using the arguments shown below. The program will work both with and without X running.
Usage:
owrestore <project name> <sid> <size in MB> <backup file name>
Arguments:
Examples:
UNIX:
$OWHOME/bin/owrestore TESTDATA owstar 100 $HOME/backup/TESTdata.dmp
$OWHOME/bin/owrestore WERTZ owwertz 200 /backup/WERTZ-’date +”%d-%b-%y”’
Windows:
%OWHOME%\bin\owrestore TESTDATA owst 100 D:\backup\TESTdata.dmp
project name: the name of the project to restore
sid: the Oracle instance to restore the project to
size: the size of the OpenWorks project to create in Mb
backup file name: the name of the backup file
190 Project Administration: Restoring OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
Managing Project Access
When you create an OpenWorks project, you are the only person who can access it. You can grant other users access to your project, and you can control their level of access.
The table below shows the available levels of project access—Browse, Limited Interpret, Interpret, and Manage—and lists the actions each type of user can perform.
Limited Interpret access can be changed; for more information, refer to Appendix: Limited Interpreters Tables on page 407 of this manual.
Manage access can be also be controlled depending on your site’s preferences. See “OpenWorks Database Security” on page 7 for more information.
To manage access to an OpenWorks project do the following:
1. Select the OpenWorks project in the Project Administration window.
2. Select User > Manager. The Project User Administration window opens.
Use the steps in the next two sections to
• manage user access by project (page 192)• manage project access by user (page 194)
Access Permissions
Browse (B) Able to view project data, but cannot modify it.
Limited Interpret (L) Able to view project data, and can modify interpretive data (e.g., faults and picks), but cannot modify reference data (e.g., well master data).
Interpret (I) Able to view, create, and modify project data created.
Manage (M) Able to view and modify all project data regardless of who created it, and can grant other users’ access. User with manage access can also delete the project. May per-form project management functions only if the OW_ADMINISTRATOR role is also granted.
R2003.12.0 Project Administration: Managing Project Access 191
OpenWorks Project Management Landmark
Managing User Access by Project
The “Managing User Access by Project” method lets you choose which users can and cannot view, modify, and manage an OpenWorks project. You can add users, remove users, or modify access permission, as desired. Use the following steps to manage user access by project:
1. If it is not already selected, select Project View from the option button at the top of the Project User Administration window.
2. The current project name is in the Project field. Click List to select another project.
When you select a project, the lists in the middle of the window show which users can and cannot access the project.
3. To move users from one list to the other, select one or more users and click on the appropriate arrow button.
4. To change users’ access permissions, select one or more users, click on the appropriate access permission option, and then click on Modify. The letter corresponding to the access permission appears next to each user name.
192 Project Administration: Managing Project Access R2003.12.0
Landmark OpenWorks Project Management
Perform steps 3 and 4 until all the users you want to add are in the right-hand list. The example below shows that user “KD50” is now in the project, with “Browse” access.
5. Click OK or Apply to implement your changes.
R2003.12.0 Project Administration: Managing Project Access 193
OpenWorks Project Management Landmark
Managing Project Access by User
The “Managing Project Access by User” method lets you choose which of your projects a user can and cannot view, modify, and manage. You can add projects, remove projects, or modify access, as desired. Use the following steps to manage project access by user:
1. Select User View from the option button at the top of the Project User Administration window.
2. Click List to select a user.
When you select a user, the lists in the middle of the window show which projects the user can and cannot access. In the example above, user “KD50” cannot access any projects.
3. To move projects from one list to the other, select one or more projects and click on the appropriate arrow button.
4. To change access permissions, select all projects to which the user will have the same level of access. Then click on the appropriate access permission option and click Modify. The letter corresponding to the user’s access permission appears next to each project name.
194 Project Administration: Managing Project Access R2003.12.0
Landmark OpenWorks Project Management
Perform steps 3 and 4 until the user has the desired access to all the desired projects. The example below shows that user “KD50” now has “Browse” access to several projects.
5. Click OK or Apply to implement your changes.
R2003.12.0 Project Administration: Managing Project Access 195
OpenWorks Project Management Landmark
Checking Tablespace and User Access in Projects
You can generate a report that shows the location, size, and user access to database tablespaces for an OpenWorks project. This report is useful because it helps you monitor project size. If it ever appears that a project is about to overload its available tablespace, you must add more tablespace to the project to keep the database from failing.
To view a report on a specific OpenWorks project:
1. Select the project in the Project Administration window.
2. Select Project > Query. A report appears showing the project extent, locations, sizes, and user authorizations.
Use the scroll bars to move through this window.
3. Click OK to close this window.
196 Project Administration: Checking Tablespace and User Access in Projects R2003.12.0
Landmark OpenWorks Project Management
Tuning Projects
Tuning an OpenWorks project can reduce data retrieval times and enhance performance. This option runs an Oracle command to compute statistics on every table, including the amount and distribution of data. These statistics are used by the Oracle cost-based optimizer to build efficient query plans so it can retrieve data more efficiently.
To start the tuning process:
1. Select Project > Tune in the Project Administration window. A confirmation window like the one shown below appears.
2. Click Yes to tune the project.
Project Tune Statistics and SeisWorks Fault Retrieval Performance
While running OpenWorks Project Tune is generally useful in enhancing database performance, the statistics that it generates can cause severe degradation of performance in certain SeisWorks fault retrievals. (For example, if a seismic project has many fault segments and heaves, SeisWorks’ performance may deteriorate.)
The SeisWorks Fault Data Manager allows bulk removal of these statistics from certain SeisWorks fault tables. SeisWorks users should refer to the Fault Data Manager chapter of the Seismic Project Utilities manual for details.
R2003.12.0 Project Administration: Tuning Projects 197
OpenWorks Project Management Landmark
198 Project Administration: Tuning Projects R2003.12.0
Landmark OpenWorks Project Management
Project Change
Overview
You must select an OpenWorks project to use in most Landmark applications and utilities. If you are a new user, please read this chapter carefully before using any of the project functions.
What’s in this Chapter
This chapter describes the OpenWorks Project Change utility and explains how to select another OpenWorks project.
You can also change projects using the Change Project option of the Project Status Tool, which is described beginning on page 217.
Effect of Changing Projects On Current Applications
When you started OpenWorks, you were asked to select an OpenWorks project. The project that you selected became the current working project for all subsequent applications that you started.
When you change projects, OpenWorks changes the current working project for all open applications. This may cause some applications to close. This is normal behavior. When you restart these applications, they will use the new current working project.
Effect of Changing Projects On Session Parameters
When you change projects, the measurement system, interpreter, well list, and well will be unset. For this reason, if you plan to change the project, always change it before you set these options.
You can use the Project Status Tool (see page 217) to reset the session parameters. Alternately, you will be prompted to set one or more of these parameters when you start one of the OpenWorks data management, data import, or data export utilities.
R2003.12.0 Project Change 199
OpenWorks Project Management Landmark
Starting Project Change
Use the following steps to launch the Project Change utility and select another OpenWorks project on the current database server.
• UNIX—From the OpenWorks Command Menu, select Project > Project Change.
• Windows—From the Start menu, select Programs > Landmark OpenWorks > Project Administration > Project Change.
1. The Project Change window opens.
All of the OpenWorks projects on the current OWSYSSID to which you have access are listed.
Select a project and click OK. Selecting <Unset> deselects the current working project so that no OpenWorks project is selected.
To use a different OWSYSSID, see “Setting the Oracle Instance (OWSYSSID)” on page 219 of this manual.
In the UNIX version of OpenWorks, the project name is posted in the status line of the Command Menu.
If you select <Unset> in the Project Change dialog, the words <None Set> are posted in the project name field.
200 Project Change: Starting Project Change R2003.12.0
Landmark OpenWorks Project Management
Project Create
Overview
You must select an OpenWorks project to use in most Landmark applications and utilities. When creating an OpenWorks project, you specify:
• a project name and description• the database server to use for storing the project data (if you have
access to multiple databases)• the cartographic reference system to use for storing map
coordinates in the database• the default units of measure• the parameters to use for viewing well data• the geographic boundaries of the project area• the size of the project
These defaults are the standard settings that OpenWorks will use to store the data and for all applications where these settings are not already specified. You can improve the accuracy and performance of the system by selecting a set of defaults that best matches your project characteristics.
What’s in this Chapter
This chapter contains the following major topics:
• Questions to Answer Before Creating an OpenWorks Project on page 202
• Loading Data Into a New OpenWorks Project on page 203
• Launching Project Create on page 204
• Creating OpenWorks Projects on page 205
• Creating Projects Using the Command Line Interface on page 216
R2003.12.0 Project Create 201
OpenWorks Project Management Landmark
Questions to Answer Before Creating an OpenWorks Project
There are several major questions to answer before you create an OpenWorks project.
1. Which cartographic reference system (CRS) will define the project? Is datum shifting necessary?
OpenWorks comes with hundreds of predefined projection and geographic coordinate systems. If necessary, create a new CRS using the procedures in the “Map Projection Editor” on page 37 chapter of this manual.
2. Which measurement system will best handle most, if not all, of the measurable quantities that will be stored in the OpenWorks project?
OpenWorks comes with four measurement systems, which are explained in the section titled “Units Handling in OpenWorks” on page 16 in this manual. If necessary, create a customized measurement system using the procedures in “Launching Measurement System Manager” on page 152 of this manual.
3. Are the settings for interpreter access appropriate?
When you create or upgrade a project, the system assigns limited interpreter access as specified in the OW_ADMIN_UTILS.L_INTERP_MASTER table. You can customize limited interpreter access by adding or removing particular tables; however, you must make any changes before you create a project.
For more information about Limited Interpreters, refer to “OpenWorks Database Security” on page 7 and “Managing Project Access” on page 191 of this manual.
4. How much disk space will the project require and should AUTOEXTEND be turned on? See “Specifying Project Tablespace” on page 213 of this manual and the Managing the System manual.
After you have resolved these issues, you will be ready to create an OpenWorks project using the procedures described in this chapter.
202 Project Create: Questions to Answer Before Creating an OpenWorks Project R2003.12.0
Landmark OpenWorks Project Management
Loading Data Into a New OpenWorks Project
Typically, after creating a new project, you will load it with well, curve, and seismic navigation data.
UNIX users should refer to the OpenWorks Data Import/Export manual for instructions on importing data.
Windows users who have purchased GeoDataLoad should refer to the OpenWorks Data Import manual for instructions on importing data.
R2003.12.0 Project Create: Loading Data Into a New OpenWorks Project 203
OpenWorks Project Management Landmark
Launching Project Create
To create projects, you must log on as an OpenWorks user who:
• is an External Oracle user with the OW_ADMINISTRATOR role in the Oracle database, and
• has been granted MANAGE access to the OpenWorks project
Use one of the following steps to launch the Project Create utility.
• UNIX—From the OpenWorks Command Menu, select Project > Project Create.
• Windows—From the Start menu, select Programs > Landmark OpenWorks > Project Administration > Project Create.
• In a command line window—type crtprj. • From other OpenWorks applications—”Create Project” is an
option in some applications when you are asked to select a project.
The Project Create window opens.
When you have finished creating projects, click on Close in the Project Create window.
204 Project Create: Launching Project Create R2003.12.0
Landmark OpenWorks Project Management
Creating OpenWorks Projects
To create a new OpenWorks project, enter the parameters for the project in each of the fields in the Project Create window.
The procedure is briefly outlined below, with cross-references to more detailed explanations where appropriate.
1. Project Name. The project name must start with an alphabetic character, followed by any combination of letters, digits, or underscores (but no blank spaces) up to 32 characters long.
2. Project Type. The system selects OpenWorks as the default project type. The OpenExplorer option is for OpenExplorer regional projects only.
3. Instance. If you have access to multiple databases, use this field to enter the ID of the database server you want to use for storing the project (page 207).
4. Cartographic Reference. Enter the name of the CRS to use for storing and converting project map coordinates (page 207).
5. Measurement System. Select the default units of measure for this project (page 209).
6. Default Display Parameters. Enter the default display parameters to use for displaying map data (page 210).
7. Description. Enter as many lines of descriptive text as needed. Press Return after each line.
8. Areal Extents. This group of entries describes the geographic boundaries of the project area, entered as a minimum and maximum longitude and latitude. You can enter these coordinates as decimal numbers or as degrees-minutes-seconds (page 212).
9. Project Tablespace. Allocate tablespace for projects, depending on your experience level and knowledge of Oracle. Click on Novice or Advanced to indicate what type of user you are. Novice users select the size of the project (small, medium, or large). Advanced users can select specific sizes to use in each available tablespace location (page 213).
R2003.12.0 Project Create: Creating OpenWorks Projects 205
OpenWorks Project Management Landmark
10. Set As Current Working Project. If you want the new project to become the current OpenWorks project when you are finished creating it, click on this check box.
11. When you finish entering all parameters for the new project, click Apply.
The program checks to make sure all your entries are valid and that the project does not already exist. If there is a problem, an error message appears and you must correct the problem before the program can begin building the project database. If there are no detectable problems with your entries, a confirmation message box opens.
12. Click OK to begin creating the project.
Once the creation process begins, a status message appears advising you of the project creation progress. The amount of time to create a project will vary depending on your system configuration, but the usual time is 15-20 minutes. During this time the utility is creating the necessary data structures needed to hold the project. Wait until the creation process is finished before proceeding.
13. When the creation process has finished, a completion message appears. Start over at step 1 to create more projects, or click Close to close the Project Create window.
206 Project Create: Creating OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
Selecting the Instance
If you have access to multiple databases, use this field to enter the ID of the database server you want to use for storing the project. Click List to see a list of the available database servers.
The list shows the server IDs of the installed Oracle instances that are available. In a typical server ID, the server ID has a nodename component (for example, nova) preceded by the letters ow, producing an ID such as ownova.
Selecting the Project Cartographic Reference System (CRS)
A cartographic reference system (CRS) is a defined set of map specifications that are available from the OpenWorks Map Projection Editor. The CRS is the frame of reference for all calculations of latitude, longitude, and distance.
When you create a project, there are two types of CRS’s that you specify:
• Cartographic Reference is the CRS used to store and calculate project data. This will be the default project CRS. The project CRS determines the surface measure units for a project.
• Map Projection is the system used to display project data.
Two choices are provided because you may want to use one map projection system to store and calculate project coordinates, but a different map projection system to actually view the data.
Typically, the project CRS should be the same map projection system that was used to map the original data. For example, if all project map coordinates have been mapped in a UTM system, the project CRS must
R2003.12.0 Project Create: Creating OpenWorks Projects 207
OpenWorks Project Management Landmark
be a UTM type. The Map Projection CRS, however, could be any projection method that you find visually preferable.
To select the project CRS, you can either type the name of the cartographic system in the Cartographic Reference field or use the List button to select the cartographic system.
To select a CRS do the following
1. Click List beside the Cartographic Reference field. The CS Selection dialog box opens. This window contains all of the available CRS’s. If the appropriate CRS does not exist, you can create it now. Click Create in the CS Selection window and the Map Projection Editor main window opens. Create the CRS using the instructions in Map Projection Editor on page 37 of this manual. Your new CRS will appear in the appropriate coordinate system list in the CS Selection window.
2. Select the appropriate CRS from the CS Selection window.
3. Click OK. Your choice appears in the Cartographic Reference field of the Project Create window.
Warning: You cannot change a project’s CRS after you create a project.
After you create a project, you cannot change the default CRS to another CRS. For this reason, make sure you select the most appropriate CRS for the data at the time that you create your project. The most appropriate CRS is one which best matches the cartographic specifications of your project mapping data.
208 Project Create: Creating OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
Selecting the Project Measurement System
The project measurement system provides default units of measure handling for all measurable quantities stored in a project.
The measurement system sets the default units for storing data in the project database. All data is stored in project-specified units and converted at load time from incoming units to project units. (Most data types are converted to the project measurement system for storage at load time. Some data types, however, are not converted at load time; they are stored according to the measurement system set in the loader. For more information about how specific incoming data types can be stored, refer to the ASCII Well Loader and Curve Loader chapters of the OpenWorks Data Import/Export manual in the documentation for OpenWorks on a UNIX workstation.)
Landmark supplies the following four measurement systems (see the section titled “Units Handling in OpenWorks” on page 16 of the “Introduction” chapter of this manual):
• U.S. Oil Field• SPE Preferred Metric• U.S. Oil Field (metric depth)• Canadian Metric
Although Landmark applications can display data in any units, you should select the measurement system whose units are used most often, so that the OpenWorks performance is not slowed down by frequent unit conversions.
Warning: Project Measurement System Cannot Be Changed
After you create a project, you cannot change the default measurement system to another measurement system. For this reason, make sure you have selected the most appropriate measurement system for your data when you create a project.
However, you can select a session measurement system, and any applications you run during a session will use the session measurement system. Some applications allow you to locally override the session measurement system without re-defining it for the session and therefore not affecting any other applications. For more information, refer to “Session Measurement Systems” on page 19.
R2003.12.0 Project Create: Creating OpenWorks Projects 209
OpenWorks Project Management Landmark
Setting Default Display Parameters for the Project
When you select the project CRS, the system uses it to define the default display parameters used to display map data. You can change these parameters, if desired. Each option is discussed in detail below.
Map Projection
Map projection is the CRS to use for all map displays for this project. This CRS can be different from the project CRS so that you can store data using the most accurate reference system, and display data using a more convenient or visually pleasing reference system.
To select the CRS from a list, click List next to the Map Projection field. The CS Selection window opens. This window contains all of the projection types and geographic coordinate systems predefined in OpenWorks. If you do not see an appropriate CRS, you can create one using the steps outlined in “Selecting the Project Cartographic Reference System (CRS)” on page 207. For more information on the Map Projection Editor or cartographic reference systems in general, see the “Project Create” chapter starting on page 201.
Map Scale
Map scale is the default scale to use for all map displays for this project. For example, if the scale is 1 to 10000, the map display measurements will be 1/10,000 of actual scale. Setting the default scale here does not prevent you from using any zoom and rescale features in the individual applications.
Enter a map scale in the text field; or click on a field with Button 3, or with the right mouse button on a Windows workstation, to display a popup menu and to choose the maximum (100,000,000.0), minimum (1.0), or default (4,000.0) scale value.
210 Project Create: Creating OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
Reference Elevation
The reference elevation is the default elevation to use for all depth calculations for this project. Enter a reference elevation in the field, or click on a field with Button 3, or the right mouse button in Windows, to display a popup menu and to choose the minimum (-10,000.00), maximum (30,000.00), or default (.00) value.
Typically, depth measurements are calculated relative to sea level. For example, if you drill a well 750 feet deep from an elevation of 1,000 feet, the sub-sea elevation value of the bottom hole is reported as 250 feet, since the bottom of the hole is above sea level (see the left side of the following illustration).
Effect of Reference Elevation on Depth Measurements
However, if you set the reference elevation for the project at 1,000 feet, a well drilled 750 feet deep will have a sub-datum elevation value for the bottom of the well displayed as -750 feet. If your project involves multiple surfaces above sea level, select a datum at least equal to the shallowest KB, or kelly bushing (see right side of previous illustration).
The Reference Elevation represents a datum to which depth measurements are corrected. This field is provided for future use. Currently, OpenWorks data are all depth data relative to sea level.
This popup menu appears when you press Button 3, or the right mouse but-ton, in the field.
Reference Elevation = 0 Reference Elevation = 1000
Sea Level -1000
- 500
-1500
0
0
+500
- 500
+1000
+250 - 750Sea Level
Well A Well A
R2003.12.0 Project Create: Creating OpenWorks Projects 211
OpenWorks Project Management Landmark
Setting the Areal Extents of the Project
The areal extents are the minimum and maximum latitudes and longitudes of the geographical area covered by your project. Latitude and longitude degrees can be entered either as decimal numbers or literally as degrees-minutes-seconds.
When you click on the check boxes, the entry fields change appropriately.
• To enter degrees as decimals, click on Decimal. Use the value to the left of the decimal point as degrees and the value to the right of the decimal point as fractions of a degree. For example, enter 20 degrees, 30 minutes as 20.5.
• To enter degrees literally, click on Deg-Min-Sec. Use positive numbers to express degrees North and East, and negative numbers for degrees West and South. Valid latitudes range from -90 degrees to 90 degrees, and valid longitudes range from -180 degrees to 180 degrees. For example, enter 30 degrees South as -30 in the latitude boxes.
You can type the appropriate values in the text fields, or click on a field with Button 3, or with the right mouse button in Windows, to display a popup menu and to choose the maximum, minimum or default value.
212 Project Create: Creating OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
Specifying Project Tablespace
You must specify the size of the tablespace used to store the project.
You can always view the amount of available tablespace (using Project Administration and its Query menu option) and change it manually (using Project Administration and its Modify menu option). However, if you ever fill up the tablespace inadvertently, your database will fail. For this reason, it is very important that you allow more than enough tablespace at the beginning of a project to accommodate all the data you expect to load or generate for the project, but not so much that you waste space. Although you can add tablespace as your project grows, you will not be able to reduce the project’s tablespace.
A better alternative is to take advantage of Oracle’s AUTOEXTEND feature. With this feature on, the tablespace size for OpenWorks projects will automatically grow as they fill with data. This means that given enough disk space, you no longer have to closely estimate the storage requirements of a project. You can create a small project and it will grow as needed, eliminating worries of wasting unnecessary space on projects. However, you should still monitor your disk space usage so that you do not run out of disk space.
To set the AUTOEXTEND feature, ask your system administrator to perform the steps outlined in “Configuring AUTOEXTEND for Project Data Files” in the OpenWorks Managing the System manual, which is included in the installation of OpenWorks on a UNIX workstation.
Determining Project Size
There are reasonably simple formulas that you can use to estimate how much tablespace your project requires. Determining an exact tablespace requirement is difficult, however, because the distribution of tables can vary so much, and empty tables also add to space requirements.
If the initial project size that you estimate becomes too small, you can increase the size using AUTOEXTEND or using Project > Modify (from the Project Administration window).
Minimum OpenWorks Project Sizes
The minimum OpenWorks 2003 project size is 110 megabytes.
R2003.12.0 Project Create: Creating OpenWorks Projects 213
OpenWorks Project Management Landmark
When creating a new project, determine the current disk size of the raw curve data to be loaded into the project. Then use the following criteria:
• Raw data less than 20 megabytes. Set the project tablespace size to Small.
• Raw data greater than 20 megabytes. If the current set of curve data is greater than 20 megabytes, use the following formula to estimate the OpenWorks project tablespace size.
110MB + (1.5 × size of the raw data)
Defining the Project Tablespace
The Project Tablespace area of the Project Create window provides two ways to allocate tablespace for projects, depending on your experience level and knowledge of Oracle.
You can toggle between the two modes by clicking on the Advanced and Novice buttons. The following illustration shows the two views.
• Novice. If you are a novice user or if you prefer the convenience of describing the project in more familiar terms, you can specify the general size of the project.
OpenWorks 2003 project sizes are: small is 110 megabytes, medium is 200 megabytes, and large is 400 megabytes
• Advanced. If you are a more advanced user, you may want to view available tablespace locations and specify the actual amount of space to reserve for the project at each location.
214 Project Create: Creating OpenWorks Projects R2003.12.0
Landmark OpenWorks Project Management
In Advanced mode, you will see the names of all of the available tablespace locations and the available sizes. A blank field is provided for you to enter the amount of space you want to use for this project at each tablespace location. If you use space on more than one location, the total space that you specify appears in the Total box at the lower right.
R2003.12.0 Project Create: Creating OpenWorks Projects 215
OpenWorks Project Management Landmark
Creating Projects Using the Command Line Interface
The owcreate program is a command line utility that allows you to create an OpenWorks project in Novice mode.
owcreate can be run from any command line interface using the arguments shown below.
Usage:
owcreate <project_name> <sid> <CRS> <meas_sys> <size> [<project_type>]
Arguments:
Examples:
$OWHOME/bin/owcreate TESTDATA owrocky "UTM 12N - feet" "US Oil Field" 110 OW
$OWHOME/bin/owcreate NORTHSEA ownova "UTM 31" "SPM Metric" 400 OW
%OWHOME%\bin\owcreate NORTHSEA ownova "UTM 31" "SPM Metric" 400 OW
Differences between owcreate and Project Create:
Project Create allows you to set the following additional parameters:
• default display parameters• description• areal extents
You can set these parameters using the Project Modify option of the Project Admin utility. See Project Administration on page 173 of this manual for details.
project name: the name of the new project
sid: the Oracle instance where the project will be created
CRS: the Cartographic Reference System
meas sys: the measurement system
size: the size of the new project; 110, 200, or 400 Mb
project type: optional; type of project to create: OW for OpenWorks, OE for OpenExplorer
216 Project Create: Creating Projects Using the Command Line Interface R2003.12.0
Landmark OpenWorks Project Management
Project Status Tool
Overview
Use the Project Status Tool to set database, project, well, time-depth, and other parameters to use during an OpenWorks session. In addition, you can change the sorting methods used to display wells and well lists, or change the format for displaying well names and related well identifiers. You can also save favorite settings in a session file.
What’s in this Chapter
This chapter contains the following sections:
• Launching Project Status Tool on page 218
• Setting the Oracle Instance (OWSYSSID) on page 219
• Setting the OpenWorks Project on page 220
• Setting the Measurement System on page 221
• Setting the Interpreter on page 222
• Selecting a Well List on page 223
• Selecting a Well on page 224
• Setting the Well List Sort Preferences on page 225
• Setting the Time Depth Conversion Preferences on page 226
• Setting the Well Order in a Well List on page 229
• Setting the Well Format on page 230
• Saving Settings to a Session File on page 231
R2003.12.0 Project Status Tool 217
OpenWorks Project Management Landmark
Launching Project Status Tool
Use the following steps to launch the Project Status Tool:
• UNIX—From the OpenWorks Command Menu, select Project > Project Status.
• Windows—From the Start menu, select Programs > Landmark OpenWorks > Project Administration > Project Status Tool.
The Project Status Tool window opens, listing any current settings. Select Session > Exit to close the Project Status Tool window.
218 Project Status Tool: Launching Project Status Tool R2003.12.0
Landmark OpenWorks Project Management
Setting the Oracle Instance (OWSYSSID)
You can access OpenWorks projects on a different Oracle instance database server, also called the OWSYSSID.
To set the Oracle instance for the current OpenWorks session:
1. Click the button to the right of the OWSYSSID text field.
A list of all available database servers opens.
2. Select an OWSYSSID, and click OK.
The Oracle instance is posted as the OWSYSSID in the Project Status Tool window and also appears in the status line of the OpenWorks Command Menu of an OpenWorks installation on a UNIX workstation. You can now select OpenWorks projects from this Oracle instance.
Close applications before changing Oracle instance
Changing the Oracle instance unsets the project in all open applications.
When you change the Oracle instance, OpenWorks unsets the current project. The circumstance of an unspecified project is handled differently by different applications. Some applications will prompt you to select a new project. Other applications may close (if this occurs, simply restart the applications that closed).
R2003.12.0 Project Status Tool: Setting the Oracle Instance (OWSYSSID) 219
OpenWorks Project Management Landmark
Setting the OpenWorks Project
Use Change Project to set the OpenWorks project for the current OpenWorks session.
1. Click the button to the right of the Project text field.
A list of all of the OpenWorks projects available on the current Oracle instance opens.
2. Select a project from the list, and click OK.
The project name is posted in the Project Status window and also appears in the status line of the OpenWorks Command Menu of an OpenWorks installation on a UNIX workstation.
Changing project unsets the measurement system, interpreter, well list, and time depth conversion selections in all open applications.
When you change the project, OpenWorks unsets the current measurement system, interpreter, well list, and time depth conversion preference. Each application handles the circumstance of these unspecified settings differently. Some applications will prompt you to select a new measurement system and interpreter. Other applications may close, and if you want them restarted, you must restart them.
The preference for the time depth conversion method is not available in the version of the Project Status Tool in OpenWorks for Windows.
220 Project Status Tool: Setting the OpenWorks Project R2003.12.0
Landmark OpenWorks Project Management
Setting the Measurement System
Use the Change Measurement System option to set the measurement system for the current OpenWorks session. The measurement system you choose here will be used by all OpenWorks measurement system-based applications that you subsequently start during the session.
To set the measurement system for the current OpenWorks session:
1. Click the button to the right of the Measurement System text field.
A list of all the available measurement systems opens.
2. Select a measurement system, and click OK.
The selected measurement system is posted in the Project Status Tool window.
• Any measurement system-based applications that you start after you set the measurement system here will use this measurement system.
• Any measurement system-based applications that were running before you set the measurement system here will continue to use the previous session measurement system.
• How the session measurement system is used by OpenWorks applications is discussed in detail in the section titled “Session Measurement Systems” on page 19 of this manual.
R2003.12.0 Project Status Tool: Setting the Measurement System 221
OpenWorks Project Management Landmark
Setting the Interpreter
To change the interpreter currently used with an OpenWorks project:
1. Click the button to the right of the Interpreter text field.
The Change Interpreters window opens. This window contains a list of all available interpreters related to the current user. If no interpreters are available, the program will inform you.
2. Select an interpreter ID, and click OK.
The interpreter name is posted in the Project Status Tool window and also appears in the status line of the OpenWorks Command Menu of an OpenWorks installation on a UNIX workstation.
For more information on building and maintaining a list of interpreters, see the chapter titled “Interpreters” on page 25 of this manual.
Changing Interpreters While Loading Data
If the interpreter is reset while the data loading utilities are running, the “new” interpreter will not be loaded as the Data Source. Landmark recommends selecting the “new” interpreter and restarting the data loading utility.
222 Project Status Tool: Setting the Interpreter R2003.12.0
Landmark OpenWorks Project Management
Selecting a Well List
To change the OpenWorks session well list:
1. Click the button to the right of the Well List text field.
A list of all available well lists appears. A message indicates if no well lists are available.
2. Select a well list, and click OK. The well list name is posted in the Project Status Tool window.
For more information on building and maintaining well lists, see the chapter titled “Well List Manager” in the OpenWorks Data Management manual.
Change Well Lists Before Well
If you select a different well list, the Well field changes to None Selected. For this reason, if you plan to change the well list, always change it before changing wells.
R2003.12.0 Project Status Tool: Selecting a Well List 223
OpenWorks Project Management Landmark
Selecting a Well
Once you have selected a well list, you can select a well from that well list to use in the OpenWorks well-based applications.
To select the default well to use during an OpenWorks session:
1. Click the button to the right of the Wells text field.
A list of all available wells appears. Both the well ID and well name are shown.
2. Select a well, and click OK.
The well name is posted in the Project Status Tool window.
224 Project Status Tool: Selecting a Well R2003.12.0
Landmark OpenWorks Project Management
Setting the Well List Sort Preferences
To change the sorting method used to display the names of well lists:
1. Click the button to the right of the Well List Sort Preferences text fields.
A window appears listing available methods for sorting the names of well lists, plus an option to restrict this sorting method only to the currently active interpreter.
The Alphabetical item controls the display of alphanumeric names. It sorts the numeric names first and then the alphabetical names. Both Most Recent items sort the wells based on the dates when the well lists were created.
2. If you click on the Active Interpreter Only button, Interpreter is removed as a sorting option in the lists below.
3. Select a sorting method in the Sort By list. The selection activates the Then list. If you wish, you can select a method in the Then list as a secondary sorting method.
4. Click OK.
The selected methods are posted on the corresponding fields in the Project Status Tool window.
R2003.12.0 Project Status Tool: Setting the Well List Sort Preferences 225
OpenWorks Project Management Landmark
Setting the Time Depth Conversion Preferences
The depth-to-time conversion preferences allow you to set a project wide method for converting depth data to time data (or depth-to-depth) during a session and allows you to specify whether the use of the well’s depth-to-time data overrides the method selected in the Project Status Tool. These preferences are stored in the OpenWorks database for each interpreter of a well’s data.
To select a preferred method for depth-to-time conversions of well data, do the following:
1. Click the button to the right of the Time Depth Conversion Preferences text field.
The Project Status Tool displays the Change Time/Depth Conversion Preference dialog.
Time Depth Conversion Preferences
In OpenWorks for Windows, the Project Status Tool does not allow you to set the Time Depth Conversion Preferences. Only the version of OpenWorks in the UNIX environment allows you to change these preferences.
Changing the Project Deselects Conversion Preferences
If you change the OpenWorks project with Options ➛ Change Project (or with Project ➛ Project Change in the OpenWorks Command Menu), Project Status Tool will delete your depth-to-time preferences (in effect, entering None Selected in the text boxes in the Time Depth Conversion Preferences area).
226 Project Status Tool: Setting the Time Depth Conversion Preferences R2003.12.0
Landmark OpenWorks Project Management
2. Select a conversion method in the Preferred Method area.
• Always Use Well T-D: When selected, the applications will use the depth-to-time (or depth-to-depth) curve associated with a well.
• Always Use T-D Model: When selected, the applications will use the depth-to-time (or depth-to-depth) model or curve that you have selected in the Model/Curve Type area of this dialog.
• Use Preferred By Well: When selected, and if the Time_Priority (or Depth_Priority) setting in the well data is set to Well T/D, the applications will use the depth-to-time (or depth-to-depth) curve associated with a well; however, if the Time_Priority (or Depth_Priority) setting in the well data is set to Session, the applications will use the depth-to-time (or depth-to-depth) model or curve that you selected in the Model/Curve Type area.
• Unset: When selected, the applications will behave as they did before OpenWorks allowed you to make a time-depth preference in the Project Status Tool; however, if the well data has a Time_Priority (or Depth_Priority) setting of Session, some applications may request that you select a depth-to-time preference.
3. If you selected Always Use T-D Model or Use Preferred By Well, do the following:
• Select one of the radio buttons in the Model/Curve Type area:
T-D Curve: Selects a time-depth curve created in another application, such as Landmark’s SynTool.
TDQ Function Models: Selects a velocity model built from time-depth functions by Landmark’s TDQ.
Grid Models: Selects a compressed grid velocity model created in another application, such as Landmark’s DepthTeam Interpreter.
R2003.12.0 Project Status Tool: Setting the Time Depth Conversion Preferences 227
OpenWorks Project Management Landmark
• Click the List button associated with the radio button you selected. A dialog displays.
If the project does not have the type of conversion curve or model that you selected, Project Status Tool will display a dialog similar to the following:
Click OK to close the dialog. You may need to change projects or make sure that the that the conversion curve or velocity model is a part of the project that you selected.
• If the project has the type of conversion curve or model that you selected, Project Status Tool will display a dialog similar to the following to allow you to select the name of the curve or model:
Select a name in the list box, and then click OK. If you do not see a name to select, click Cancel.
4. Click OK in the Change Time/Depth Conversion Preference dialog to enter your preferences into the Project Status Tool window.
Or, click Cancel to leave the previous contents of the Time Depth Conversion Preferences area in the Project Status Tool window as they were.
228 Project Status Tool: Setting the Time Depth Conversion Preferences R2003.12.0
Landmark OpenWorks Project Management
Setting the Well Order in a Well List
To change the sorting method used to order well names within any selected well list:
1. Click the button to the right of the Well Order text field.
A window appears listing available methods for sorting wells in a well list. The Well List item sorts according to the order in which the wells were saved through the Well List Manager.
2. Select a well ordering type, and click OK.
The selected sorting method is posted in the Project Status Tool window.
These preferences are also reflected in the Well List field in Well Curve Viewer, Well Data Manager, and Well List Manager; and the Well Names field in Well Data Export.
R2003.12.0 Project Status Tool: Setting the Well Order in a Well List 229
OpenWorks Project Management Landmark
Setting the Well Format
This option allows you to select from a number of formats that can help identify each well, including the well name, well number, UWI (Unique Well Identifier), and operator.
To change the format used to identify each well:
1. Click the button to the right of the Well Format text field.
The Change Well Format window appears listing available methods for displaying the name and the other identifiers of a well:
2. Select a format type and click OK.
The selected well format type is posted in the Project Status Tool window.
These preferences are also reflected in the Well List field in Well Curve Viewer, Well Data Manager, and the Well Names field in Well Data Export.
230 Project Status Tool: Setting the Well Format R2003.12.0
Landmark OpenWorks Project Management
Saving Settings to a Session File
When you have selected a set of parameters that you would like to use on a regular basis, save them to a session file.
Session files have an “.ssm” extension and are saved in the run directory of your operating system home directory. The length of a session file name is limited by the operating system. Alphanumeric characters and the special characters + (plus) - (minus), _ (underscore), # (number sign), = (equals), , (comma) and . (dot) can be used in session file names. Characters which have meaning to the operating system, such as asterisks (*)and ampersands (&), and spaces cannot be used in session file names.
• The name of the current session file appears in the Project Status Tool title bar.
• Use Session > Save to save new sessions.
• Session > New clears all of the fields in the main window except OWSYSSID. It also unsets the project, interpreter, and measurement system in all open applications.
• Use Session > Open to change the parameters in all open applications with the parameters in the chosen session file.
• Session > Delete removes a session file.
• Use Session > Save As to save existing session files to new names.
• Use the Filter button in these dialogs to see session files you’ve recently added or changed.
Changing settings unsets the selections in all open applications
Close applications before changing Oracle instance.
When you change the project, OpenWorks unsets the current measurement system, interpreter, well list, and time depth conversion preference. Each application handles the circumstance of these unspecified settings differently. Some applications will prompt you to select a new measurement system and interpreter. Other applications may close, and if you want them restarted, you must restart them.
R2003.12.0 Project Status Tool: Saving Settings to a Session File 231
OpenWorks Project Management Landmark
232 Project Status Tool: Saving Settings to a Session File R2003.12.0
Landmark OpenWorks Project Management
Project Data Transfer
Overview
Project Data Transfer (PDT), available with the GeoDataLoad software, provides a quick method for transferring data from one OpenExplorer or OpenWorks project to another. It is used typically to
• combine data from several OpenWorks projects in a regional OpenExplorer project
• subset data from an OpenExplorer project into smaller, local OpenWorks projects.
When transferring data between two project in the same Oracle System Identifier (SID), the source project and target project can use different cartographic reference systems (CRSs) and different units of measure. Project Data Transfer will automatically convert the incoming data to the CRS and units of the target project. However, if the projects are in different SIDs, the ID for the CRS and the measurement system in both projects must be the identical.
What’s in this Chapter
This chapter contains the following sections:
• If You Have an OpenExplorer Advanced License on page 234
• Transferring Data Across ORACLE Instances on page 234
• Access Levels Required on page 235
• Types of Data Transferred on page 235
• Typical Work Flow on page 236
• Starting Project Data Transfer on page 237
• Choosing the Source and Target Projects on page 239
R2003.12.0 Project Data Transfer 233
OpenWorks Project Management Landmark
• Selecting Data for Transfer on page 241
• Excluding or Renaming Interpreters on page 306
• Advanced Filter Options on page 309
• Global Transfer Options Dialog on page 314
• Setting Up Transfer Reporting on page 321
• Transferring the Data on page 323
• Running Batch Jobs on page 325
• Command Line Arguments on page 328
• Performance Enhancements on page 330
• PDT Configuration File Format on page 331
If You Have an OpenExplorer Advanced License
If you have an OpenExplorer Advanced license, additional features become available which allow you to:
• set advanced filters for data transfer (page 309)• set up and run PDT jobs in batch mode, using a configuration file
(page 325). Batch jobs can be run from the command line or from the user interface.
For information about starting PDT in advanced mode, see “Starting Project Data Transfer” on page 237.
Transferring Data Across ORACLE Instances
You can transfer data between source and target projects that reside on different ORACLE instances (OWSYSSIDs) if the projects have the same CRS and measurement system or if OpenExplorer Advanced Project Management is installed. Advanced Project Management establishes a master-child relationship among multiple database servers so that projects residing on any one of them can be accessed by all of them. It also provides replication of cartographic reference systems among all the member ORACLE instances.
234 Project Data Transfer: Overview R2003.12.0
Landmark OpenWorks Project Management
Access Levels Required
At a minimum, you must have browse access for the source project (since you are only reading data) and limited interpreter access for the target project (since you are writing data).
Types of Data Transferred
You can transfer the following types of data with PDT:
• Basin Data• Field Data (including production data)• Lease Data (including production data)• Facility Data (including production data)• Well Data (including production data)• 2D Seismic Navigation Data• 3D Seismic Navigation Data• SeisWorks Fault Data• Stored Queries• Stratigraphic Column Data• Interpretation Data• Line of Section Data• Well Template Data• List Data• Well Planning Project Data
Do not use PDT with projects that are self-referencing.
If either the source project or target project has a standalone CRS, it is impossible to accurately project the x, y coordinates into the target project. PDT will not stop you from attempting such a transfer, but the coordinates will be meaningless.
If the source or target is self-referencing, PDT will give you the option to choose another project or continue without any cartographic conversions.
Preserve or overwrite existing data?
When both projects contain data for a given item, by default, PDT will preserve the data item that already exists in the target project and not load the data item from the source project.
However, you can instruct the application to overwrite existing data with incoming data. Additionally, if you have an OpenExplorer Advanced license, you can instruct PDT to update existing data objects without adding any new data objects. For more information, see “Handling New Data Objects” on page 310 in the “Advanced Filter Options” section.
R2003.12.0 Project Data Transfer: Overview 235
OpenWorks Project Management Landmark
Typical Work Flow
A basic work flow for using Project Data Transfer is outlined below.
If desired, set data specific filters, such as interpreters, log curves, and so forth.
Select the source project.
Select the data to be transferred. (Toggle on and set options for each data type.)
Transfer the data.
View transfer reports.
Using Project Data Transfer
If desired, set advanced filter parametersfor data to be transferred.
Or, set these job parameters automatically, using a saved configuration file (OpenExplorer Advanced license required). See page 327 for details.
If desired, set optional global data transfer options and transfer report options.
Select the target project.
If necessary, recompute areal extent of target project to accommodate the transferred data.
236 Project Data Transfer: Typical Work Flow R2003.12.0
Landmark OpenWorks Project Management
Starting Project Data Transfer
To run this utility, you must log on as an OpenWorks user who:
• is an External Oracle user of the Oracle database
• has access personations as an interpreter able to at least browse the source OpenWorks project
• has interpreter access permissions to the target OpenWorks project of at least limited interpreter level
Before starting Project Data Transfer, you can set the OWSYSSID to the appropriate ORACLE instance of the source project to prepare for Pointing Dispatcher (PD):
• If OpenExplorer Advanced Project Management has been installed, set OWSYSSID to the master instance. All the project management tables physically reside on that instance. (If your OWSYSSID is set to one of the child instances, Project Data Transfer will prompt you to change it.)
• If OpenExplorer Advanced Project Management has not been installed, set OWSYSSID to the instance where the source project resides so that you can access it.
See “Project Status Tool” on page 217 of this manual for instructions to set the OWSYSSID.
To start Project Data Transfer, do as follows:
• [UNIX] From the OpenWorks Command Menu, select Project > Project Data Transfer.
• [Windows] From the Start menu, select Programs > Landmark OpenWorks > Project Administration > Project Data Transfer.
To start Project Data Transfer in advanced mode:
• In a terminal window enter the following:
pdt -a &
R2003.12.0 Project Data Transfer: Starting Project Data Transfer 237
OpenWorks Project Management Landmark
• If you prefer to start PDT in advanced mode from the OpenWorks Command Menu, add the following line to launcher.dat (use only tabs to indent a line in launcher.dat):
"Project Data Transfer Advanced""pdt -a y 2>$HOME/run/pdt.err 1>&2 &"
To exit Project Data Transfer, select File > Exit from its menu bar.
238 Project Data Transfer: Starting Project Data Transfer R2003.12.0
Landmark OpenWorks Project Management
Choosing the Source and Target Projects
Project Data Transfer opens with the current project for the OpenWorks session listed as the source project. However, you can choose a different project as the data source if you wish. You do not have to use the current project.
Both the source project and the target project can use different CRSs (PDT will make the necessary conversions), but neither should be self-referencing.
To select the source and target projects, do as follows:
1. Start PDT (“Starting Project Data Transfer” on page 237).
The Project Data Transfer window opens.
R2003.12.0 Project Data Transfer: Choosing the Source and Target Projects 239
OpenWorks Project Management Landmark
2. For Source Project, click on List and choose a OWSYSSID and a project from the Source Project List dialog.
3. For Target Project, click on List. The Target Project List dialog displays, allowing you to make a choice of OWSYSSID and project as in the Source Project List.
PDT checks the areal extents of both projects and posts a message in the dialog box telling you if they overlap, do not overlap, or that the source project extends beyond the target project.
You can proceed with the data transfer in any case but may need to adjust the areal extent of the target project later, using the Project Modify utility.
4. If you do not want to use a Configuration File to set the transfer parameters, and if the text box contains any characters, click the adjacent Clear button to clear it. (If you want to use a configuration file, see page 325 for instructions.) This feature is only available with an OpenExplorer license.
The Pointing Dispatcher works only if the source project is the current project.
You can send data from other applications to Project Data Transfer via the Pointing Dispatcher only if the source project is the current project. This limitation is imposed because the data you select in the other application is drawn from the current project.
240 Project Data Transfer: Choosing the Source and Target Projects R2003.12.0
Landmark OpenWorks Project Management
Selecting Data for Transfer
You can transfer any of fifteen data types from the source project to the target project.
For stored queries and well planning projects, you select the items (like one or more queries or column names) that you want to transfer. Based on your selection, PDT retrieves all the data from the relevant database tables and loads it to the target project.
For all other data types—basins, fields, leases, facilities, wells, 2D and 3D seismic navigation, SeisWorks faults, stratigraphic columns, interpretation, line of section, well template, and lists—however, you have more control. With wells, for example, you can transfer all a well’s related data or choose particular categories of data. If you are transferring log curves, you can specify which curve types to transfer.
Basic Procedure
The basic procedure for selecting the data to transfer is as follows:
1. Toggle on the checkbox for the data type.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 241
OpenWorks Project Management Landmark
2. Click on the adjacent Options button for the data type. A dialog box, tailored for filtering the type of data to be transferred, appears.
3. Select the objects whose data you want to transfer.
Specific instructions for the various data types are provided below.
Well Data
By default, PDT will transfer all the existing data for the wells you pick, but you can select a more limited set of data items if you wish. If you are transferring log curves, you can specify which curve types should be included, and if you have interpreted data, you can specify the interpreters whose data you want to transfer. Additionally, you can specify the types of OpenWorks production data or Production Data Mart data you want to transfer.
Any well data that has been loaded to the database with the ASCII Loader, Curve Loader, or any of the OpenExplorer or OpenWorks data managers can be transferred.
Filtering the Well Data
With Well Data toggled on, click on the adjacent Options button to open the Well Data Options dialog box. This dialog box allows you to filter the data to be transferred.
Selecting multiple items and using the Search/Filter feature
For instructions on selecting multiple items in list boxes and panels, refer to “Techniques for Selecting Multiple Items” on page 302 For instructions on using the Search/Filter feature to find items or narrow the list of items, refer to “Using the Search/Filter String” on page 303.
242 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
The procedure to filter the well data to be transferred is briefly outlined and cross-referenced to details:
1. Select a well list (page 244).
2. Select the wells of interest from the list (page 244).
3. Select the categories of well information you want to transfer (page 245).
4. Select the OpenWorks production entities you want to transfer (page 246).
5. Select the Production Data Mart entities you want to transfer (page 247).
6. Specify the types of log curves you want to transfer (page 248).
7. Exclude and rename interpreters whose data you want to transfer (page 306).
OpenWorks production data that exists for the current source project
Production Data Mart data that exists for the current source project
Well categories that exist for the current source project
Wells in the selected list
Selected list
Search/filter list of wells
Lists in the current source project
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 243
OpenWorks Project Management Landmark
8. If you want to customize the advanced filters for well data, specify the desired options by clicking on Advanced Filter (page 250).
9. Apply the filter (page 250).
Details follow.
Select a Well List
1. In the Well Data Options dialog box, select a well list by clicking on it.
All the wells in that list are posted in the lower left panel. By default, wells are listed by Operator|Well Name|Well Number. Well categories that actually exist for wells in the current project are posted in the middle panel.
2. If you prefer to list wells by another identifier, choose the appropriate option from the Format option menu.
Select the Wells of Interest
1. Select the wells whose data you want to transfer. Use any of these techniques:
• Browse the list and select wells manually by clicking on their names or by using the Select All button. Click the button again if you want to unselect all wells. (Techniques for selecting multiple items are explained on page 302.)
244 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
• Use the Search/Filter String feature to find a particular well, or narrow the list of wells until only the wells you want to transfer are listed. You can then select those wells. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection of wells from another application via the Pointing Dispatcher.
Select Well Categories
1. Choose the categories of data you want transferred for all the selected wells. To select one or more of the categories, use these techniques:
• Click on categories to select them. While clicking, hold down the Shift key to select contiguous categories in the list, or hold down the Control key to select noncontiguous categories.
• Click on Select All to select all categories. (Click the button again if you want to unselect all categories).
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 245
OpenWorks Project Management Landmark
Select OpenWorks Production Entities
If you are transferring OpenWorks production data, you can either transfer some or all entities in the list, or you can filter the list to be transferred by volume start date and zone name.
1. Select the desired production data entities; to transfer all entities, click Select All.
2. To filter the production entities by volume start date and zone name, click Filter Options. The following dialog box opens.
• To filter by start date, toggle on Transfer volumes with production start dates in range: and indicate the date range of interest and click Apply or OK. Use the MM/DD/YYYY format. Enter the earliest desired date in the from field and the latest date in the to field.
—To select all entities within a specific date range, fill in the from and to fields (you must fill in all fields).
—To select just the entities whose start dates are greater than or equal to the date you specify, just enter the from range (you must fill in all from fields).
246 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
—To select just the entities whose start dates are less than or equal to the date you specify, just enter the to range (you must fill in all to fields).
• To select one or more zones of interest, toggle on Transfer data with zones, select the zones, and click Apply or OK.
—To select all zones, click the Select All button; to unselect all zones, click the Unselect All button (button toggles between Select All and Unselect All). Techniques for selecting multiple items are explained on page 302.
• After filtering the list, select the desired entities.
Select Production Data Mart Entities
1. If you are transferring Production Data Mart (PDM) data, specify the types of production entities, using these techniques.
• Click on entities to select them.
• Click on Select All to select all entities. (Click the button again if you want to unselect all categories).
• To further narrow the search, click on Filter Options to filter the list of PDM data by zone names. The following dialog box opens:
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 247
OpenWorks Project Management Landmark
—To filter PDM data by producing zone, toggle on Transfer data with zones:, click on the zones to select them, or click on Select All to select all zones. (Click the button again if you want to unselect all zones). Techniques for selecting multiple items are explained on page 302.
—Click OK to apply the selections and dismiss the dialog box.
• The list of PDM data will be filtered accordingly during the transfer process. Select the desired entities.
Specify Types of Log Curves
1. If you are transferring log curve data, specify which types of curves you want included as follows:
• Click on Log Curves to open a dialog box displaying the log curve types for the current project.
• By default, all curve types in the project are selected for transfer.
—Toggle on Transfer curves with type. Deselect the ones you do not want to transfer, and click OK.
248 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
—To transfer new curves for existing wells, but no new wells, make sure that Well Header (Header) is not selected in the Well Categories list box, and click on the Advanced Filter button. In the Advanced Filters dialog box, toggle on Create new data; select Transfer data with update timestamps; and specify the “from” date so that all curves created after that date will be transferred.
—To transfer new wells as well as new curves for existing wells, make sure that Well Header (Header) is selected in the Well Categories list box, and click on the Advanced Filter button. In the Advanced Filters dialog box, toggle on Create new data; select Transfer data with update timestamps:; and specify the “from” date so that all wells and curves created after that date will be transferred.
Exclude and Rename Interpreters
PDT will transfer data belonging to all interpreters in the source project, unless you specify otherwise. To exclude certain interpreters’ data or change the name of an interpreter when it is transferred, use the procedures starting on page 306.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 249
OpenWorks Project Management Landmark
Set Advanced Filter Options For Well Data
Advanced filter options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for well data, if you wish.
1. To customize the advanced filter options for well data, click on the Advanced Filter button in the Well Data Options dialog box.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the Well Data Options dialog box.
The number of wells you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
250 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Lease Data
By default, PDT will transfer all existing data for the leases you pick, but you can select a more limited set of data items if you wish. You can select the data items manually, or after displaying the list, you can broadcast in a selection with the Pointing Dispatcher.
Additionally, you can specify the types of OpenWorks production data or Production Data Mart data you want to transfer.
Filtering the Lease Data
With Lease Data toggled on, click the adjacent Options button to open the Lease Data Options dialog box. This dialog box allows you to filter the data to be transferred.
The procedure to filter the lease data to be transferred is briefly outlined and cross-referenced to details:
1. Select a lease list (page 252).
2. Select the lease or leases of interest (page 252).
Leases in the selected list
Selected list
Lease categories that exist for the current source project
OpenWorks production data that exists for the current source project
Production Data Mart data that exists for the current source project
Lists in the current source project
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 251
OpenWorks Project Management Landmark
3. Select the categories of lease information you want to transfer (page 253).
4. Select the OpenWorks production entities you want to transfer (page 246).
5. Select the Production Data Mart entities you want to transfer (page 247).
6. If you want to customize advanced filters for lease data, specify the desired options by clicking on Advanced Filter (page 254).
7. Apply the filter (page 254).
Details follow.
Select a Lease List
1. In the Lease Data Options dialog box, select a lease list by clicking on it.
All the leases in that list are posted in the lower left panel. Lease categories that exist for leases in the current project are displayed in the Lease Categories list box.
Select the Leases of Interest
1. Select the leases whose data you want to transfer. Use any of these techniques:
• Browse the list and select leases manually by clicking on their numbers in the Leases list box or by using the Select All button. Click the button again if you want to unselect all leases. (Techniques for selecting multiple items are explained on page 302.)
• Use the Search/Filter String feature to find a particular lease, or narrow the list of leases until only those you want to transfer are listed. You can then select those leases. (See page 303 for details on using the Search/Filter String feature.)
252 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
• Send in a selection of leases from another application via the Pointing Dispatcher.
Select Lease Categories
1. Choose the categories of data you want transferred for all the selected leases. To select one or more of the categories, use these techniques:
• Click on categories to select them.
• Click on Select All to select all categories. (Click the button again if you want to unselect all categories). Techniques for selecting multiple items are explained on page 302.
Select OpenWorks Production Entities
See page 246 for details.
Select Production Data Mart Entities
See page 247 for details.
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
Lease Parents
Lease Tract (Parent) and Licensing Round (Parent) are parent entities for leases. So, in order to transfer leases, the parent entities must be selected or they must already exist in the target project.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 253
OpenWorks Project Management Landmark
Set Advanced Filter Options For Lease Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for lease data, if you wish.
1. To customize the advanced filter options for lease data, click on the Advanced Filter button in the Lease Data Options dialog box.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the Lease Data Options dialog box.
The number of leases you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
254 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Field Data
By default, PDT will transfer all existing data for the fields you pick, but you can select a more limited set of data items if you wish. You can select the data items manually, or, after displaying the list, you can broadcast in a selection with the Pointing Dispatcher.
Additionally, you can specify the types of OpenWorks production data or Production Data Mart data you want to transfer.
Filtering the Field Data
With Field Data toggled on, click the adjacent Options button to open the Field Data Options dialog box. This dialog box allows you to filter the data to be transferred.
The procedure to filter the field data to be transferred is briefly outlined and cross-referenced to details:
1. Select a field list (page 256).
2. Select the field or fields of interest (page 256).
Fields in the selected list
OpenWorks production data that exists for the current source project
Production Data Mart data that exists for the current source project
Lists in the current source project
Selected list
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 255
OpenWorks Project Management Landmark
3. Select the field categories that you want to transfer (page 257).
4. Select the OpenWorks production entities you want to transfer (page 246).
5. Select the Production Data Mart entities you want to transfer (page 247).
6. If you want to set advanced filters for field data, specify the desired options by clicking on Advanced Filter (page 258).
7. Apply the filter (page 258).
Details follow.
Select a Field List
1. In the Field Data Options dialog box, select a field list by clicking on it.
All the fields in that list are posted in the lower left panel. Field categories that actually exist for fields in the current project are displayed in the middle panel.
Select the Fields of Interest
1. Select the fields whose data you want to transfer. Use any of these techniques:
• Browse the list and select fields manually by clicking on their names or by using the Select All button. Click the button again if you want to unselect all fields. (Techniques for selecting multiple items are explained on page 302.)
• Use the Search/Filter String feature to find a particular field, or narrow the list of fields until only those you want to transfer are listed. You can then select those fields. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection of fields from another application via the Pointing Dispatcher.
256 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Select Field Categories
1. Choose the categories of data you want transferred for all the selected fields. To select one or more of the categories, use these techniques:
• Click on categories to select them. While clicking, hold down the Shift key to select contiguous categories in the list, or hold down the Control key to select noncontiguous categories.
• Click on Select All to select all categories. (Click the button again if you want to unselect all categories).
Select OpenWorks Production Entities
See page 246 for details.
Select Production Data Mart Entities
See page 247 for details.
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 257
OpenWorks Project Management Landmark
Set Advanced Filter Options For Field Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for field data, if you wish.
1. To customize the advanced filter options for field data, click on the Advanced Filter button in the Field Data Options dialog box.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the Field Data Options dialog box.
The number of fields you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
258 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Basin Data
You can select basins manually, or, after displaying the list of basins, you can broadcast in a selection with the Pointing Dispatcher.
Filtering Basin Data
1. Select basin or basins of interest (page 259).
2. Select the categories of basin information you want to transfer (page 260).
3. If you want to set advanced filters for basin data, specify the desired options by clicking on Advanced Filter (page 261).
4. Apply the filter (page 261).
Details follow.
Select Basins of Interest
1. With Basin Data toggled on, click on the adjacent Options button to open the Basin Data Options dialog box.
All the basins contained in the project are listed in the lower left panel. Basin categories that actually exist for basins in the current project are displayed in the right panel.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 259
OpenWorks Project Management Landmark
2. Select the basins you want to transfer data for. Use any of these techniques:
• Select basins manually by clicking on their names or by using the Select All button. Click the button again if you want to unselect all basins. (Techniques for selecting multiple items are explained on page 302.)
• Use the Search/Filter String feature to find a particular basin, or narrow the list of basins until only those you want to transfer are listed. You can then select those basins. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection of basins from another application via the Pointing Dispatcher.
Select Basin Categories
1. Choose the categories of data you want transferred for all the selected basins. To select one or more of the categories, use these techniques:
• Click on categories to select them.
• Click on Select All to select all categories. (Click the button again if you want to unselect all categories).
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
260 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Set Advanced Filter Options For Basin Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for basin data, if you wish.
1. To customize the advanced filter options for basin data, click on the Advanced Filter button in the Basin Data Options dialog box.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the Basin Data Options dialog box.
The number of basins you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 261
OpenWorks Project Management Landmark
Facility Data
By default, PDT will transfer all existing data for the facilities you pick, but you can select a more limited set of data items if you wish. You can select the data items manually, or after displaying the list, you can broadcast in a selection with the Pointing Dispatcher.
Additionally, you can specify the types of OpenWorks production data or Production Data Mart data you want to transfer.
Filtering the Facility Data
With Facility Data toggled on, click on the adjacent Options button to open the Facilities Data Options dialog box. This dialog box allows you to filter the data to be transferred.
Facilities in the current project
OpenWorks production data that exists for the current source project
Production Data Mart data that exists for the current source project
262 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
The procedure to filter the facility data to be transferred is briefly outlined and cross-referenced to details:
1. Select the facilities of interest (page 263).
2. Select the OpenWorks production entities you want to transfer (page 246).
3. Select the Production Data Mart entities you want to transfer (page 247).
4. If you want to customize the advanced filters for facility data, specify the desired options by clicking on Advanced Filter (page 264).
5. Apply the filter (page 265).
Details follow.
Select the Facilities of Interest
1. Select the facilities whose data you want to transfer. Use any of these techniques:
• Browse the list and select facilities manually by clicking on their names or by using the Select All button. Click the button again if you want to unselect all facilities. (Techniques for selecting multiple items are explained on page 302.)
• Use the Search/Filter String feature to find a particular facility, or narrow the list of facilities until only those you want to transfer are listed. You can then select those facilities. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection of facilities from another application via the Pointing Dispatcher.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 263
OpenWorks Project Management Landmark
Select OpenWorks Production Entities
See page 246 for details.
Select Production Data Mart Entities
See page 247 for details.
Set Advanced Options For Facility Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for facility data, if you wish.
1. To customize the advanced filter options for facility data, click on the Advanced Filter button in the facility Data Options dialog box.
2. Set the desired parameters. (See page 309 for details).
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
264 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Apply the Filter
1. Click OK to apply the filter and close the Facility Data Options dialog box.
The number of facilities you selected is posted in the PDT main dialog box.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 265
OpenWorks Project Management Landmark
2D Seismic Data
PDT can transfer 2D seismic navigation data and header information that has been loaded to the database with the Seismic Data Loader or Seismic Navigation Data Manager.
Filtering 2D Seismic Data
The procedure to filter 2D seismic data to be transferred is briefly outlined and cross-referenced to details:
1. Select a line list, then select the seismic lines you want to transfer (page 267).
2. Select the categories of 2D seismic data you want to transfer (page 268).
3. If you want to set advanced transfer filters for 2D seismic data, specify the desired options by clicking on Advanced Filter (page 268).
4. Apply the filter (page 269).
Details follow.
266 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Select 2D Seismic Data
1. With 2D Seismic Navigation Data toggled on, click the adjacent Options button to open the 2D Seismic Data Options dialog box.
2. Select a seismic line list by clicking on it.
All the seismic lines in that list are posted in the lower panel.
3. Select the seismic lines you want to transfer. Use any of these techniques:
• Select individual seismic lines manually by clicking on their names or by using the Select All button.
• Use the Search/Filter String feature to find a particular seismic line, or narrow the list of seismic lines until only those you want to transfer are listed. You can then select those seismic lines. (See page 303 for details on using the Search/Filter String feature.)
Categories of seismic data that exists for the current source project
Selected seismic line list
Selected Seismic lines in the selected list
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 267
OpenWorks Project Management Landmark
• Send in a selection from another application via the Pointing Dispatcher.
Select 2D Seismic Data Categories
1. Choose the categories of data you want transferred for all the selected seismic lines. To select one or more of the categories, use these techniques:
• Click on categories to select them.
• Click on Select All to select all categories. (Click the button again if you want to unselect all categories).
Set Advanced Filter Options For 2D Seismic Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types.
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
2D Seismic Parents
Seismic Geometry Set 2D Survey (Parent) is a parent entity for seismic lines. So, in order to transfer seismic data, the parent entities must be selected or they must already exist in the target project.
268 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
However, you can customize the settings for 2D seismic data, if you wish.
1. To customize the advanced filter options for seismic data, click on the Advanced Filter button in the 2D Seismic Data Options dialog box, as appropriate.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the 2D Seismic Data Options dialog box.
The number of lines you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 269
OpenWorks Project Management Landmark
3D Seismic Data
PDT can transfer 3D seismic navigation data and header information that has been loaded to the database with the Seismic Data Loader or Seismic Navigation Data Manager.
Filtering 3D Seismic Data
The procedure to filter 3D seismic data to be transferred is briefly outlined and cross-referenced to details:
1. Select the seismic surveys you want to transfer (page 270).
2. Select the categories of 3D seismic survey data you want to transfer (page 271).
3. If you want to set advanced transfer filters for 3D seismic survey data, specify the desired options by clicking on Advanced Filter (page 272).
4. Apply the filter (page 272).
Details follow.
Select 3D Seismic Data
1. With 3D Seismic Navigation Data checked, click on the adjacent Options button to open the 3D Seismic Data Options dialog box.
270 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
All the 3D seismic surveys contained in the current project are listed.
2. Select the seismic surveys you want to transfer. Use any of these techniques:
• Select individual surveys manually by clicking on their names or by using the Select All button. Techniques for selecting multiple items are explained on page 302.
• Use the Search/Filter String feature to find a particular 3D seismic survey, or narrow the list of seismic surveys until only those you want to transfer are listed. You can then select those seismic surveys. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection from another application via the Pointing Dispatcher.
Select 3D Seismic Survey Categories
1. Choose the categories of data you want transferred for all the selected 3D seismic surveys. To select one or more of the categories, use these techniques:
• Click on categories to select them.
• Click on Select All to select all categories. (Click the button again if you want to unselect all categories).
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 271
OpenWorks Project Management Landmark
Set Advanced Filter Options For 3D Seismic Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for 3D seismic data, if you wish.
1. To customize the advanced filter options for seismic data, click on the Advanced Filter button in the 3D Seismic Data Options dialog box, as appropriate.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the 3D Seismic Data Options dialog box.
The number of surveys you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
272 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
SeisWorks Fault Data
PDT transfers SeisWorks fault data, that is, fault planes and fault segments created in SeisWorks and related geophysical interpretation products (FZAP!, SeisCube, EarthCube). It can also transfer fault data generated in the geologic products such as StratWorks. However, PDT does not transfer fault heaves, since those can be recalculated using SeisWorks.
By default, PDT will transfer all existing data for the fault list you pick, but you can select a more limited set of data items if you wish. If you have interpreted data, you can specify the interpreters whose data you want to transfer.
Filtering the Fault Data
The procedure to filter the faults data to be transferred is briefly outlined and cross-referenced to details:
1. Select fault data—select a fault set, and from it select the faults of interest (page 274).
2. Exclude and rename interpreters whose data you want to transfer (page 275).
3. If you want to filter segments for transfer according to how they were picked (time or depth domain), you can do so by clicking on Segments. You can also filter by the names of the originating surveys from which the line segments were interpreted (page 276).
4. If you want to customize the advanced filters for field data, specify the desired options by clicking on Advanced Filter (page 277).
5. Apply the filter (page 277).
Details follow.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 273
OpenWorks Project Management Landmark
Select Fault Data
1. With SeisWorks Fault Data toggled on, click on the adjacent Options button to open the Faults Data Options dialog box.
2. In the Fault Set Directory field, type the pathname of the directory containing the fault set files (*.fst) for the SeisWorks faults you are interested in, and click Filter. The fault sets in that directory will be posted in the Fault Sets list box.
3. Select a fault set from the Fault Sets list box by clicking on it.
All the faults in that set are posted in the lower panel.
4. Select the faults you want to transfer. Use any of these techniques:
• Select individual faults manually by clicking on their names or by using the Select All button. Choose <Unassigned segments> if you want to transfer unassigned segments that have no corresponding fault. Techniques for selecting multiple items are explained on page 302.
274 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
• Use the Search/Filter String feature to find a particular fault, or narrow the list of faults until only those you want to transfer are listed. You can then select those faults. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection from another application via the Pointing Dispatcher.
Exclude and Rename Interpreters
PDT will transfer fault data belonging to all interpreters in the source project, unless you specify otherwise. To exclude certain interpreters’ data or change the name of an interpreter when it is transferred, use the procedures starting on page 306.
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 275
OpenWorks Project Management Landmark
Filter Segments By Domain and Originating Surveys
If you want to filter fault segments for transfer by pick method (time or depth domain) or by the originating surveys from which the line segments were interpreted, click on Segments to open the Fault Segments Filter dialog box.
1. To transfer segments by pick method, toggle on Transfer segments with domain, and select Time to transfer faults picked in time domain, or Depth to transfer faults picked in depth domain.
2. To transfer faults by the originating surveys (from which the line segments were interpreted), toggle on Transfer data with surveys, select the survey names by clicking on them or by using the Select All button. Originating survey names can be seismic surveys, seismic lines, seismic horizons, depth surveys, or depth horizons.
3. Click OK to apply the filter and close the dialog box.
276 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Set Advanced Filter Options For Faults Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for faults data, if you wish.
1. To customize the advanced filter options for faults data, click on the Advanced Filter button.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the Faults Data Options dialog box.
The number of faults you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 277
OpenWorks Project Management Landmark
Stored Queries
PDT can transfer queries that were built with the OpenExplorer Query Tools (GeoData Query Builder, AdHoc SQL Query Builder, or Standard SQL) and stored in the database.
Filtering the Stored Queries
The procedure to filter the stored queries to be transferred is briefly outlined and cross-referenced to details:
1. Select the stored queries of interest (page 278).
2. If you want to customize the advanced filters for stored queries, specify the desired options by clicking on Advanced Filter (page 279).
3. Apply the filter (page 279).
Details follow.
Select Stored Queries
1. With Stored Queries toggled on, click the adjacent Options button to open the Stored Queries Data Options dialog box.
The option box opens with all the stored queries in the project listed.
278 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
2. Select the stored queries you want to transfer. Use either of these techniques:
• Select individual queries manually by clicking on their names or by using the Select All button. Techniques for selecting multiple items are explained on page 302.
• Use the Search/Filter String feature to find a stored query, or narrow the list of queries until only those you want to transfer are listed. You can then select those queries. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection from another application via the Pointing Dispatcher.
Set Advanced Filter Options For Stored Queries
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for stored queries, if you wish.
1. To customize the advanced filter options for stored queries, click on the Advanced Filter button in the Stored Queries Data Options dialog box.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the Stored Queries Data Options dialog box.
The number of stored queries you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 279
OpenWorks Project Management Landmark
Strat Column Data
PDT transfers all the stratigraphic column data that you select, but you can select a more limited set of data items if you wish. If you have interpreted data, you can specify the interpreters whose data you want to transfer.
Filtering the Strat Column Data
With Strat Column Data toggled on, click on the adjacent Options button to open the Strat Column Data Options dialog box.
Changes to Strat Column model for Release 2003.12
PDT now reads all surfs that belong to the column and are used in one of its units, all UNKNOWN counterparts to the surfaces just described, and all surfs that belong to the column that are not bound to one of its units. All of these will be transferred to the target with special care taken with the surfs that belong to the UNKNOWN column. The surfs that belong to the UNNKOWN column are only transferred to the target if they do not already exist. If they do exist, they are NOT overwritten even if the overwrite flag is on. The only way to overwrite surfs that belong to the UNKNOWN column is to transfer the UNKNOWN column.
280 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
The procedure to filter the strat column data to be transferred is briefly outlined and cross-referenced to details:
1. Select strat columns to transfer in the Strat Columns list box (page 281).
2. Exclude and rename interpreters whose data you want to transfer (page 282).
3. If you want to customize the advanced filters for column data, specify the desired options by clicking on Advanced Filter (page 283).
4. Apply the filter (page 283).
Details follow.
Select Strat Column Data
1. Select the strat columns you want to transfer. Use any of these techniques:
• Select individual strat columns manually by clicking on their names or by using the Select All button. Techniques for selecting multiple items are explained on page 302.
• Use the Search/Filter String feature to find a particular strat column, or narrow the list of strat columns until only those you want to transfer are listed. You can then select those strat columns. (See page 303 for details on using the Search/Filter String feature.)
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 281
OpenWorks Project Management Landmark
• Send in a selection from another application via the Pointing Dispatcher.
Exclude and Rename Interpreters
PDT will transfer strat column data belonging to all interpreters in the source project, unless you specify otherwise. To exclude certain interpreters’ data or change the name of an interpreter when it is transferred, use the procedures starting on page 306.
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
282 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Set Advanced Filter Options For Strat Column Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for strat column data, if you wish.
1. To customize the advanced filter options for strat column data, click on the Advanced Filter button.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the Strat Column Data Options dialog box. The number of strat columns you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 283
OpenWorks Project Management Landmark
Interpretation Data
PDT transfers all the interpretation data that you select, but you can select a more limited set of data items if you wish. PDT can transfer interpretation data of the following types: point set, grid, contour, mapping polygon, fault center line, surface profile, and fault profile. You can limit the amount of data transferred by selecting the surfaces, strat units, faults, interpretation data, and interpreters that you want PDT to transfer.
Filtering the Interpretation Data
With Interpretation Data toggled on, click on the adjacent Options button to open the Interpretation Data Options dialog box.
284 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
The procedure to filter the interpretation data to be transferred is briefly outlined and cross-referenced to details:
1. Select types of data to transfer in the Data Types list box (page 285).
2. Select the objects (surfaces, stratigraphic units, and faults) in the data types that you want transferred (page 285).
3. Exclude and rename interpreters whose data you want to transfer (page 286).
4. Select data in the Interpretation Data list box that you want to transfer (page 286).
5. If you want to customize the advanced filters for field data, specify the desired options by clicking on Advanced Filter (page 287).
6. Apply the filter (page 287).
Details follow.
Select Types of Interpretation Data
Select the types of data to transfer in the Data Type list box. Select data manually by clicking on their names or by using the Select All button. Click the button again to unselect all the data types. Techniques for selecting multiple items are explained on page 302.
Select Available Objects
Select the surfaces, stratigraphic units, and faults of the data types that you want to transfer. As with the data types, Select the data manually by clicking on the names or by using the Select All button. Techniques for selecting multiple items are explained on page 302.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 285
OpenWorks Project Management Landmark
Exclude and Rename Interpreters
PDT will transfer interpretation data belonging to all interpreters in the source project, unless you specify otherwise. To exclude certain interpreters’ data or change the name of an interpreter when it is transferred, use the procedures starting on page 306.
Select Interpretation Data
Select the interpretation data you want to transfer. Use any of these techniques:
• Select each datum manually by clicking on a row in the Interpretation Data list box or by using the Select All button associated with the list box. Techniques for selecting multiple items are explained on page 302.
• Use the Search/Filter String feature to find a particular set of interpretation data, or narrow the list of data until only those you want to transfer are listed. You can then select those data. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection from another application via the Pointing Dispatcher.
286 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Set Advanced Filter Options For Interpretation Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for interpretation data, if you wish.
1. To customize the advanced filter options for interpretation data, click on the Advanced Filter button.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
Click OK to apply the filter and close the Interpretation Data Options dialog box. The number of interpretation data you selected is posted in the PDT main dialog box.
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 287
OpenWorks Project Management Landmark
Line Of Section Data
You can select lines of sections manually, or after displaying the list of lines, you can broadcast in a selection with the Pointing Dispatcher.
Filtering Line of Section Data
With Lines Of Section Data toggled on, click on the adjacent Options button to open the Line Of Section Data Options dialog box.
The procedure to filter the lines of sections data to be transferred is briefly outlined and cross-referenced to details:
1. Select the lines of sections (page 289).
2. Select the categories (lines of sections or well projections) of data you want to transfer (page 290).
3. Exclude and rename interpreters whose interpretations you want to transfer (page 290).
4. If you want to filter lines for transfer according to whether a surface or fault has an interpretation, you can do so by clicking on the Surfaces and Faults buttons. (page 291).
5. If you want to set advanced filters for lines of sections, specify the desired options by clicking on Advanced Filter (page 292).
288 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
6. Apply the filter (page 292).
Details follow.
Select Lines of Sections
All the lines of sections contained in the project are listed in the Line Of Section list box on the lower left. Categories which exist for the lines in the current project are displayed in the Line of Section Categories box on the right.
1. Select the lines you want to transfer. Use any of these techniques:
• Select lines manually by clicking on their names or by using the Select All button. Click the button again if you want to unselect all lines. (Techniques for selecting multiple items are explained on page 302.)
• Use the Search/Filter String feature to find a particular line, or narrow the list of lines until only those you want to transfer are listed. You can then select those lines of sections. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection of basins from another application via the Pointing Dispatcher.
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 289
OpenWorks Project Management Landmark
Select Line of Section Categories
1. Choose the categories of data you want transferred for all the selected lines of sections. To select one or more of the categories, use these techniques:
• Click on categories to select them.
• Click on Select All to select all categories. (Click the button again if you want to unselect all categories).
Exclude and Rename Interpreters
PDT will transfer fault data belonging to all interpreters in the source project, unless you specify otherwise. To exclude certain interpreters’ data or change the name of an interpreter when it is transferred, use the procedures starting on page 306.
290 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Transfer Lines Of Sections with Interpreted Surfaces and Faults
If you only want to transfer lines of section data with surface or fault interpretation, click the Surfaces button to select the surfaces, or click the Faults button to select the faults, or both.
The dialogs function similarly. For instance, to select lines of section with surface interpretation:
1. Check the Transfer Cross Sections With Surface Interpretation box.
2. In the list box, select the surface names by clicking on them or by using the Select All button.
3. Click OK to apply the filter and close the dialog box.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 291
OpenWorks Project Management Landmark
Set Advanced Filter Options For Lines of Section Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for lines of section, if you wish.
1. To customize the advanced filter options for lines of section data, click on the Advanced Filter button in the Line Of Section Data Options dialog box.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the Line Of Section Data Options dialog box. The number of lines you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
292 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Well Template Data
PDT transfers all the well template data that you select, but you can select a more limited set of data items if you wish. If you have interpreted data, you can specify the interpreters whose data you want to transfer.
Filtering the Well Template Data
With Well Template Data toggled on, click on the adjacent Options button to open the Well Template Data Options dialog box.
The procedure to filter the well template data to be transferred is briefly outlined and cross-referenced to details:
1. Select well templates to transfer in the Well Templates list box (page 294).
2. Exclude and rename interpreters whose data you want to transfer (page 295).
3. If you want to customize the advanced filters for well template data, specify the desired options by clicking on Advanced Filter (page 295).
4. Apply the filter (page 295).
Details follow.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 293
OpenWorks Project Management Landmark
Select Well Template Data
1. Select the well templates you want to transfer. Use any of these techniques:
• Select individual well templates manually by clicking on their names or by using the Select All button. Techniques for selecting multiple items are explained on page 302.
• Use the Search/Filter String feature to find a particular well template, or narrow the list of templates until only those you want to transfer are listed. You can then select those well templates. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection from another application via the Pointing Dispatcher.
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
294 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Exclude and Rename Interpreters
PDT will transfer well template data belonging to all interpreters in the source project, unless you specify otherwise. To exclude certain interpreters’ data or change the name of an interpreter when it is transferred, use the procedures starting on page 306.
Set Advanced Filter Options For Well Template Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for well template data, if you wish.
1. To customize the advanced filter options for well template data, click on the Advanced Filter button.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
1. Click OK to apply the filter and close the Well Template Data Options dialog box. The number of well templates you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 295
OpenWorks Project Management Landmark
List Data
PDT transfers all the working sets, or list data, that you select, but you can select a more limited set of data items if you wish. Working sets can be made of lists of 2D seismic lines, faults, fields, leases, and wells. You can also specify the interpreters whose data you want to transfer.
Filtering the List Data
With List Data toggled on, click on the adjacent Options button to open the List Data Options dialog box.
The procedure to filter the list data to be transferred is briefly outlined and cross-referenced to details:
1. Select types of lists to transfer in the List Types list box (page 297).
2. Select the individual list data in the List Data list box (page 297).
296 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
3. Exclude and rename interpreters whose data you want to transfer (page 298).
4. If you want to customize the advanced filters for list data, specify the desired options by clicking on Advanced Filter (page 298).
5. Apply the filter (page 298).
Details follow.
Select Types of List Data
Select the types of list data you want to transfer by clicking on their names or by using the Select All button. Techniques for selecting multiple items are explained on page 302.
Select List Data
1. Select the list data you want to transfer. Use any of these techniques:
• Select the list data manually by clicking on their names or by using the Select All button. Techniques for selecting multiple items are explained on page 302.
• Use the Search/Filter String feature to find a particular list data, or narrow the list of data until only those data you want to transfer are listed. You can then select those list data. (See page 303 for details on using the Search/Filter String feature.)
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 297
OpenWorks Project Management Landmark
Exclude and Rename Interpreters
PDT will transfer list data belonging to all interpreters in the source project, unless you specify otherwise. To exclude certain interpreters’ data or change the name of an interpreter when it is transferred, use the procedures starting on page 306.
Set Advanced Filter Options For List Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for list data, if you wish.
1. To customize the advanced filter options for list data, click on the Advanced Filter button.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
Click OK to apply the filter and close the List Data Options dialog box. The number of sets of list data you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
298 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Well Planning Project Data
PDT transfers all the well planning project data that you select, but you can select a more limited set of data items if you wish.
Filtering the Well Planning Project Data
With Well Planning Project Data toggled on, click on the adjacent Options button to open the Well Planning Project Data Options dialog box.
The procedure to filter the well planning project data to be transferred is briefly outlined and cross-referenced to details:
1. Select well planning project data to transfer in the Well Planning Projects list box (page 300).
2. If you want to customize the advanced filters for well planning projects, specify the desired options by clicking on Advanced Filter (page 301).
3. Apply the filter (page 301).
Details follow.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 299
OpenWorks Project Management Landmark
Select Well Planning Projects
Select the well planning projects you want to transfer. Use any of these techniques:
• Select individual well planning projects manually by clicking on their names or by using the Select All button.
• Use the Search/Filter String feature to find a particular well planning project, or narrow the list of projects until only those you want to transfer are listed. You can then select those well planning projects. (See page 303 for details on using the Search/Filter String feature.)
• Send in a selection from another application via the Pointing Dispatcher.
Using the Pointing Dispatcher
When you send objects to PDT via the Pointing Dispatcher, a list of objects must already be displayed in the option box. The broadcast information is used to select from the currently displayed list. If the objects you are sending are not already listed in the option box, PDT cannot highlight them.
• If the dialog is open, but buried beneath other dialogs, it will pop to the top for you with the selections made but not applied.
• If the dialog has been dismissed by the Cancel or OK buttons, the PD send will still work, but the selections will automatically be applied.
Also, to use the Pointing Dispatcher, the source project must be the same as the current project for the OpenWorks session.
300 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Set Advanced Filter Options For Well Planning Project Data
Advanced options set using the Options > Global Advanced Filter option on the PDT main menu apply globally to all data types. However, you can customize the settings for well planning project data, if you wish.
1. To customize the advanced filter options for well planning project data, click on the Advanced Filter button.
2. Set the desired parameters. (See page 309 for details).
Apply the Filter
Click OK to apply the filter and close the Well Planning Project Data Options dialog box. The number of well planning projects you selected is posted in the PDT main dialog box.
Changes made to Global Advanced Filter settings overwrites all existing settings if that filter in the Global Advanced filter is enabled and the same filter in the data type-specific advanced filter is not enabled!
Keep in mind that if you subsequently make changes to the Global Advanced Filter settings, the new global settings, if enabled, will override all individual data type settings if they are not already enabled.
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 301
OpenWorks Project Management Landmark
Techniques for Selecting Multiple Items
In many panels and lists, Project Data Transfer allows you to select multiple items. Various lists in the Data Options dialog box, for instance, let you choose multiple items.
The various methods of selecting items are reviewed below. You can use any combination of these. Keep these two principles in mind:
• Button 1 starts a new selection. All previously selected items are deselected.
• Ctrl-Button 1 adds to the selection. Any previously selected items remain selected.
To select individual items, click on the first one with Button 1; then click on the others with Ctrl-Button 1.
To select a range of contiguous items, click on the first one with Button 1 or Ctrl-Button 1; then click on the last one with Shift-Button 1. Or click and drag from the first item to the last with Button 1 or Ctrl-Button 1.
To select all items in the list, click on any item with Button 1; then press Ctrl-/. Or use the Select All option which is provided in some dialog boxes.
To deselect an item that is highlighted, click on it with Ctrl-Button 1.
To deselect a range of highlighted items, click on the first one with Ctrl-Button 1; then click on the last one with Shift-Button 1. Or click and drag from the first highlighted item to the last with Ctrl-Button 1.
To deselect all highlighted items, press Ctrl-\; then click on the one item that remains highlighted with Ctrl-Button 1. Or use the Deselect All button, which is provided for the many lists.
302 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
Using the Search/Filter String
In the Data Options dialog boxes, you can use the Search/Filter String feature to Search for (highlight) a particular item, or narrow the list of items by applying Filter criteria.
For example, if your well list contains wells operated by different companies in the Gulf of Mexico, type the filter string Amoco* and click Filter to retrieve just Amoco wells. To search for a particular Amoco 49 well, #122, type 122 and click Search. The well will be highlighted.
Search
1. Type the search criteria you are looking for into the Search/Filter String field, along with wildcard characters (such as * . For more information about wildcard characters, see the following section, “Wildcard Characters and Examples of Strings” on page 304).
2. Check Match Case if you want to make the search case sensitive.
3. Click the Search button to highlight the first item matching the search criteria. Repeat to highlight other matches (if any).
Filter
1. Type the filter criteria into the Search/Filter String field, You may use wildcard characters (such as * . For more information about wildcard characters, see the following section, “Wildcard Characters and Examples of Strings” on page 304).
2. Click Filter to filter the list based on the criteria. Only those items meeting the criteria will remain in the list box.
Search/Filter String feature
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 303
OpenWorks Project Management Landmark
Reset
If you want to perform another filter operation, click Reset to remove any search filter set in the Search/Filter String box. After Reset is clicked, the items listed will be those belonging to the currently selected data type.
Clearing All Data Selections
To clear all the current selections for all the data types, simply select Controls > Clear All in the main Project Data Transfer dialog box.
Wildcard Characters and Examples of Strings
Search function allows you to enter the following wildcard characters as a part of a filter or find string: * (asterisk), ; (semicolon), ^ (caret), ! (exclamation mark), and ? (question mark).
Asterisk
A string with no wildcard characters has implied asterisks at the beginning and end of the string. For example, typing hello is the same as typing *hello* .
An asterisk can occur anywhere in a string and represents zero or more characters.
Semicolon
The semicolon is an implied or-operation and can occur anywhere in a string. In effect, the semicolon separates the string into two substrings.
Search/Filter String Matches
Ma*ey Maey, Mahey, Mahoney, etc.
*ney ney,oney, Mahoney, etc.
Mah* Mah, maho, Mahoney, etc.
304 Project Data Transfer: Selecting Data for Transfer R2003.12.0
Landmark OpenWorks Project Management
If either substring is found in a name, the filter or find operation will have a match.
Caret
As a wildcard character, the caret must occur at the beginning of a string or substring. In the first position, the caret forces the string to match at the beginning of a name and no where else. If the caret occurs anywhere else in a string, the filter and find operation will try to find the caret character in the name.
Exclamation Mark
As with the caret character, to be a wildcard character, the exclamation mark must occur at the beginning of a string or substring. In the first position, the exclamation mark acts as a not-operation. The filter and find operation will match all names which do not include the string. If the exclamation mark occurs anywhere else in a string, the filter and find operation will try to find the exclamation mark in the name.
Question Mark
The question mark can occur anywhere in the string and represents exactly one character.
Search/Filter String Matches
Mah*;*oney Everything Mah* matches and everything *oney matches
Search/Filter String Matches
^Mahoney Mahoney, Mahoney 1
Mahon^y Mahon^y
Search/Filter String Matches
!Mahoney Everything Mahoney doesn’t match
Maho! Maho!
Search/Filter String Matches
Ma?ey Mahey, Maxey
R2003.12.0 Project Data Transfer: Selecting Data for Transfer 305
OpenWorks Project Management Landmark
Excluding or Renaming Interpreters
Unless you specify otherwise, PDT will transfer data belonging to all interpreters in the source project. The following data types allow you to exclude interpreter’s data:
• Wells• Faults• Strat Columns• Interpretations• Lines Of Sections• Well Templates• Lists
You can also change an interpreter designation. For example, if both the source project and the target project have an interpreter named “MEL,” you might want to change the interpreter on the incoming data to “PDT” to make it clear that the data was imported and not actually created within the target project.
To exclude or rename interpreters, do as follows:
1. With data type from the list above toggled on, click on the adjacent Options button to open its Data Options dialog box.
2. In the Data Options dialog box, click on the Interpreters button.
A dialog box appears, listing all interpreters in the source project. By default, all are in the Transfer list.
3. To filter the interpreters during transfer, toggle on Transfer interpreted data according to:.
4. To keep from transferring an interpreter’s data, move that interpreter to the Do Not Transfer list.
• To move interpreters individually, click on the interpreter’s initials and then click on the left-facing arrow.
• To move all interpreters to the Do Not Transfer list, click on the Select All button beneath the Transfer list and click on the left-pointing arrow.
• Techniques for selecting multiple items are explained on page 302.
306 Project Data Transfer: Excluding or Renaming Interpreters R2003.12.0
Landmark OpenWorks Project Management
5. To change the interpreter designation that will be assigned to the imported data, do as follows:
• Click on the interpreter’s initials in the Transfer list.
• Click on Rename to open the Rename Interpreter dialog box.
• Enter the new name for the interpreter in the text field at the bottom of the dialog box.
• Click on Apply. The new name will be shown enclosed by parentheses, adjacent to the original name, in the Interpreter Options box.
All interpreters in target project
Interpreter in source project
Interpreter name to be used in target project
New interpreter name follows original name
R2003.12.0 Project Data Transfer: Excluding or Renaming Interpreters 307
OpenWorks Project Management Landmark
6. In some cases, data in an OpenWorks project does not have a set interpreter. By default, the Transfer data with NULL interpreter command is toggled on, allowing you to transfer data with NULL interpreters when the interpreter filter is enabled. If you do not want to transfer this type of data, you must toggle off Transfer data with NULL interpreters.
7. Click OK to close the Rename Interpreter and Interpreter Options dialog boxes.
308 Project Data Transfer: Excluding or Renaming Interpreters R2003.12.0
Landmark OpenWorks Project Management
Advanced Filter Options
If you have an OpenExplorer Advanced license, the Options menu will contain an additional item, Global Advanced Filters, which opens the Advanced Filters dialog box. Use the options in this box to set the following filtering parameters:
• Update the existing data objects for a project, and specify whether to add any new objects or just update existing objects.
• Transfer data based on the update date and time you specify.
• Transfer data falling within the areal extent you specify.
• If your project contains some data that does not have defined spatial coordinates (NULL data), you must toggle on Transfer data with NULL spatial coordinates to transfer the information when the areal extent filter is enabled. By default, the toggle is off.
Handling new data objects (page 310)
Transferring data by update date/time (page 311)
Transferring data by areal extent, except for Storied Queries, Stratigraphic Column, Well Template, List, and Well Planning Project data (page 312)
R2003.12.0 Project Data Transfer: Advanced Filter Options 309
OpenWorks Project Management Landmark
Handling New Data Objects
By default, the Create new data filter is toggled on. When toggled on, any new data that has been added to the source project will be transferred. To use Well data as an example, this means that any new wells will be transferred; for existing wells, any new curves will also be transferred.
If your project already has data in it, you can instruct PDT to update the existing data objects (wells, leases, fields, and so forth) only—without adding any new data objects—by toggling Create new data off.
This powerful feature is very useful for sites that have an “enterprise” project containing all their data, and working projects which are subsets of the “enterprise” project. Every time new data is obtained, the working projects need to be updated, but the update should be limited to the objects already in the working project—no new objects should be added. The behavior of the create and update toggles is the same for all data types whether they are “parent” or “child” data.
Advanced filters can be set globally and then customized for individual data types.
When you use Options > Global Advanced Filters to set filter parameters, the parameters you set apply globally to all data types if data type-specific filter parameters have not already been set and enabled. You can then customize the settings for individual data types by clicking the Advanced Filter button in the Data Options dialog box for the data type. However, setting global changes after that will take precedence over any data type-specific changes you make to some of the filters:
• The Global setting for the Create new data filter takes precedence over the data-specific filter setting.
• For the Transfer items with update timestamps filter and the Area extents filter, if these filters are enabled in the data-specific filter, then the Global filter will not disturb the settings.
310 Project Data Transfer: Advanced Filter Options R2003.12.0
Landmark OpenWorks Project Management
To specify how you want PDT to handle new data objects, do as follows:
1. Make sure that Options > Global Transfer Options > Overwrite data in target is toggled on.
2. Select Options > Global Advanced Filters. (If you are setting filters for a specific data type only, select Advanced Filter from the Data Options dialog box for that data type.)
3. In the Global Advanced Filters or Advanced Filters dialog box, specify how you want to handle new data objects for the project by toggling Create new data on or off.
• Off—does not add any new data objects to the project.
• On— adds any new data objects to the project. This is the default.
Transferring Data By Update Date and Time
You can instruct PDT to transfer only the data that was updated (changed, modified, or created) on or after a date and time you specify. PDT will examine the value in the update_date column present in all OpenWorks project tables. Only data updated between the dates and times you enter will be transferred.
To transfer items by update date and time:
1. In the Global Advanced Filters or Advanced Filters dialog box, click on the checkbox for Transfer Items with update timestamps.
2. Enter the update date range you want to filter by and click Apply or OK. Use the HH/MN/MM/DD/YYYY format. Enter the earliest desired date in the from field and the latest date in the to field. At the least, you must fill in the month (MM), day (DD), and year (YYYY) fields, but depending on how specific your transfer is, fill in the hour (HR) and minute (MN) fields to specify the data further.
— To transfer all items within a specific date range, fill in the from and to fields.
R2003.12.0 Project Data Transfer: Advanced Filter Options 311
OpenWorks Project Management Landmark
— To transfer just the items whose update dates/times are greater than or equal to the date/time you specify, just enter the from range (you must fill in all from fields).
— To transfer just the items whose update dates/times are less than or equal to the date/time you specify, just enter the to range (you must fill in all to fields).
Transferring Data By Areal Extent
If you are only interested in data for a particular region, you can instruct PDT to transfer data based on the areal extent you specify, except for Storied Queries, Stratigraphic Column, Well Template, List, and Well Planning Project data, which have no areal extents. PDT will examine the coordinates for all data objects, and transfer only those objects where one of the coordinates of an object is located within the specified region.
1. In the Global Advanced Filters or Advanced Filters dialog box, click on the checkbox for Areal extents.
2. Select the type of areal extent to filter by from the Extent type drop-down menu:
• Source project extents transfers data that lies within the source project areal extents. The areal extent for the source project will be displayed in the field boxes and shown relative to the source coordinate system.
• Target project extents transfers data that lies within the target project areal extents. The areal extent for the target project will be displayed in the field boxes and shown relative to the source coordinate system.
• Custom extents transfers data within a specified rectangular region relative to the source coordinate system. If you choose this option, define the areal extent coordinates.
— Toggle on X/Y or Lat/Lon to indicate the type of coordinates you want to use to define the areal extent. Only Lat/Lon is available when the source uses a geographic CRS. (PDT will automatically convert between the coordinate types, so data falling within
312 Project Data Transfer: Advanced Filter Options R2003.12.0
Landmark OpenWorks Project Management
the areal extent will still be found and transferred, regardless of the coordinate system used.)
— Enter the minimum and maximum coordinates for the rectangular region. Typically, a custom extent will be located in an area overlapped by the source and target areal extents.
3. Click OK to apply the filters and close the Advanced Filters dialog box.
About extents
At least one of the four corners of the bounding box for the source item must be located within the custom extent in order for the source item to transfer to the target project.
Target areal extent
Source areal extent
Custom areal extent
R2003.12.0 Project Data Transfer: Advanced Filter Options 313
OpenWorks Project Management Landmark
Global Transfer Options Dialog
To further control what data is transferred, you can set the following transfer options, which apply to all data types:
• Overwrite data in target
• Validate source coordinates
• Force transfer on conversion error
• Rename faults, surfaces, and strat units
Select Options > Global Transfer Options to display the dialog:
These options are explained below.
314 Project Data Transfer: Global Transfer Options Dialog R2003.12.0
Landmark OpenWorks Project Management
Overwrite Data In Target
Indicate how you want data duplications handled by toggling Overwrite data in target on or off.
• Off — Preserves the data item that already exists in the target project. The incoming data item is not written to the target project. This is the default.
• On — Replaces the existing data item in the target project with the incoming data item from the source project.
Additionally, if you have an OpenExplorer Advanced license, you can instruct PDT to update existing data objects (wells, leases, fields, and so forth) for a project without adding any new objects. See page 309 for details.
Validate Source Coordinates
Indicate whether or not to validate source coordinates by toggling Validate source coordinates off or on. The default is on.
Coordinates for most objects are stored in Preferred coordinates (x, y, lat, lon) and Original coordinates (org_crs_id, org_x_lon, org_y_lat). When this option is selected, PDT will ensure that the original coordinates when converted to the source project’s coordinate system match the preferred coordinates. If the original coordinates agree, the original coordinates are used to convert and transfer to the target; if they do not agree, PDT will ignore the original coordinates and use the preferred coordinates when transferring data to the target, making the preferred coordinates in the source the original coordinates in the target.
Force Transfer on Conversion Error
Indicate whether to force the transfer after encountering a conversion error of any kind by toggling Force transfer on conversion error off or on. By default, this option is off: data containing bad conversions are not transferred. Generally, it is not recommended to force a transfer.
R2003.12.0 Project Data Transfer: Global Transfer Options Dialog 315
OpenWorks Project Management Landmark
Rename Faults, Surfaces, and Strat Units
Project Data Transfer allows you to rename faults, surfaces, and stratigraphic units, when data is transferred to the target project, by prefixing a string to the name of the object. Conversely, you can also remove a string from the name of an object. Even though, you are renaming set of objects (faults, surfaces, or stratigraphic units), each item in the set may be referenced by another record (or related to another piece of data) in the OpenWorks database.
You must make sure that you maintain data relationships when you transfer the data to the target project.
Data Relationships
Data in the OpenWorks database have relationships with other data in the database. This relationship is partly based on the name of the object. When PDT renames objects, it only renames the objects in the target project, not the source. For instance, in the source project, fault interpretation data might refer to a fault by the name of faultname. In the target project, you might rename the fault to new_faultname.
If you transferred the fault and interpretation data in the same session while you were renaming the fault, the fault and the interpretation data would maintain its relationships. However, if you transferred them in separate sessions, you may break the relationship between the data. For instance, if you checked Rename Faults when you transferred the faults, but when you transferred the interpretation data, left the checkbox unchecked or with a different string in the Prepend String text box, the transferred interpretation data would refer to the original fault name (faultname) or another fault name in the target project, not new_faultname.
The following table shows some of the relationships between faults and other data, such as interpretation data, lists, and wells; between surfaces and other data, such as interpretation data, leases, wells, and
316 Project Data Transfer: Global Transfer Options Dialog R2003.12.0
Landmark OpenWorks Project Management
stratigraphic columns; and between stratigraphic units and interpretation data, fields, and leases. The table also relates the data to an OpenWorks table.
Data Option DialogData Category or
Data TypeOpenWorks Table
Fault References Interpretation Contour cntr_set
Interpretation Fault Center Line fault_center_line
Interpretation Fault Profile fault_profile
Interpretation Grid grid_hdr
Interpretation Mapping Polygon map_poly
Interpretation Point Set point_data_set
Interpretation Surface Profile fault_cut
List Fault fault_list_member
SeisWorks Fault Fault (Header) fault
SeisWorks Fault Fault Display fault_symbol
SeisWorks Fault Fault Plane Trimesh fault_plane
Well Key Well key_well
Well Strat Unit Summary strat_unit_summary
Well Strat Unit Summary strat_unit_summary
Well Well Fault well_fault_obsv
N/A N/A fault_surf
Surface References Interpretation Contour cntr_set
Interpretation Fault Center Line fault_center_line_set
Interpretation Grid grid_hdr
Interpretation Mapping Polygon mapping_polygon_set
Interpretation Point Set point_data_set
Interpretation Surface Profile fault_cut
Interpretation Surface Profile surface_profile
Lease Lease (Header) lease_master
Lease Lease (Header) lease_master
Strat Column <None> strat_unit
R2003.12.0 Project Data Transfer: Global Transfer Options Dialog 317
OpenWorks Project Management Landmark
Strat Column <None> strat_unit
Strat Column <None> surf
Strat Column <None> surf_symbol
Well Pick pick
Well Pick pick
Well Strat Unit Summary strat_unit_summary
Well Strat Unit Summary strat_unit_summary
Well Surface Key Well surf_key_well
N/A N/A fault_surf
N/A N/A surf_alias_group_member
N/A N/A surf_alias_group_member
N/A N/A surface_alias_group
N/A N/A trap_eval
Strat Unit References Field Field Prospect (Header) field_prospect
Interpretation Contour cntr_set
Interpretation Grid grid_hdr
Interpretation Point Set point_data_set
Strat Column <None> strat_unit
Strat Column <None> strat_unit
Well Blow Out blow_out
Well Casing casing
Well DST/RFT General dst_rft_gen
Well Interpreted Drilling Show intrp_drilg_show
Well Liner liner
Well Lost Circulation lost_circ
Well Paleo paleo
Well Paleo Sample Analysis paleo_sample_alys
Well Paleo Sample Analysis paleo_sample_alys
Well Pdm Production Hdr (Header)
pdm_production_hdr
Data Option DialogData Category or
Data TypeOpenWorks Table
318 Project Data Transfer: Global Transfer Options Dialog R2003.12.0
Landmark OpenWorks Project Management
Well Plugging plugging
Well Production Gas Analysis pden_gas_analysis
Well Production Oil Analysis pden_oil_analysis
Well Production Water Analysis pden_water_analysis
Well Squeeze squeeze_info
Well Strat Unit Summary strat_unit_summary
Well TD Information td_info
Well Tubing tubing
Well Well Completion well_completion
Well Well Core well_core
Well Well Core Formation well_core_formation
Well Well Core Sample Description
well_core_sample_desc
Well Well Fault well_fault_obsv
Well Well Fluid Contact well_fluid_contact
Well Well Interval well_interval
Well Well Perforation well_perforation
Well Well Pressure well_pressure
Well Well Pressure B H well_pressure_bh
Well Well Producing Zone well_prod_zone
Well Well Test well_test
Well Well Treatment well_treatment
Well Zone (Strat Unit) Attribute strat_unit_intrp
N/A N/A em_grid_region
N/A N/A petrophysical_parm_value
N/A N/A pool
N/A N/A prospect_reservoir_eval
N/A N/A source_rock_evaluation
N/A N/A strat_unit_resim_x
N/A N/A trap_eval
Data Option DialogData Category or
Data TypeOpenWorks Table
R2003.12.0 Project Data Transfer: Global Transfer Options Dialog 319
OpenWorks Project Management Landmark
Transferring Data and Renamed Objects
Renaming an object is fairly straightforward. For instance, to rename transferred faults as they are incorporated into the target project, you might do the following (assuming you have already selected the source and target projects):
1. Select Options > Global Transfer Options in the Project Data Transfer window. The Global Transfer Options dialog displays.
1. Toggle on Rename Faults.
2. Select the Add radio button associated with Rename Faults.
3. Enter a sequence of characters in the Prepend String text box.
4. Click OK to close the Global Transfer Options dialog.
5. In the Project Data Transfer window, toggle on the SeisWorks Fault Data checkbox.
6. Click the Options button associated with SeisWorks Fault Data. The Fault Data Options dialog displays
7. Select the faults you want to transfer, and click OK to close the Fault Data Options dialog.
8. Select the other data you want to transfer that has a relationship to the faults previously selected.
9. Select Controls > Transfer to transfer the faults to the target project. As the faults are transferred, they are renamed in the target.
Transferring Related Data
When you transfer the related data later, do the following:
• Toggle on the Rename checkbox for the object (faults, surfaces or strat units).
• Enter the same string in the Prepend String text box as during the previous transfer.
• Select Add or Remove as during the previous transfer.
320 Project Data Transfer: Global Transfer Options Dialog R2003.12.0
Landmark OpenWorks Project Management
Setting Up Transfer Reporting
Whenever you transfer data, PDT generates a report indicating what data was transferred and what, if any, errors were encountered. This report is displayed on screen during the transfer process so you can monitor the progress. It is also written to the file you specify.
You can choose any or all of the following report modes, which present different types of information:
• Errors• Warnings• Information.
You can also indicate whether you want to append to the previous transfer report file, or to overwrite the existing report file with new information.
An example from a report in information mode only is shown below. This dialog was generated during transfer of selected well and seismic data.
R2003.12.0 Project Data Transfer: Setting Up Transfer Reporting 321
OpenWorks Project Management Landmark
Before transferring data, you should select the desired report mode(s) and specify the destination file, as follows:
1. Select Options > Set Transfer Report.
2. Toggle on one or more Data modes to control the type of detail you want presented in the report:
• Errors• Warnings• Information
3. Set Write Mode to
• Append to add to reports previously recorded in this file• Overwrite to replace all existing information in this file.
4. Use the file filter to specify the directory path and name of the file where you want the report stored.
5. Click OK to close the Reporting Options dialog box.
322 Project Data Transfer: Setting Up Transfer Reporting R2003.12.0
Landmark OpenWorks Project Management
Transferring the Data
After you have selected the data, excluded any data you do not want transferred, and set the reporting mode, you are ready to run the job.
If the data you are importing lies beyond the areal extent of the target project, you need to recompute the project’s extent after the transfer is completed. Otherwise, you will not be able to see the data in applications such as OpenExplorer GIS.
The procedure is as follows:
1. Select Controls > Transfer.
2. When the confirmation screen appears, informing you of the number of wells to be transferred, click OK to proceed, or click Cancel to abort the transfer.
R2003.12.0 Project Data Transfer: Transferring the Data 323
OpenWorks Project Management Landmark
The transfer report is displayed on screen. The status area at the bottom shows how much of the job has been completed.
3. When the job is completed, close the Transfer Report Display.
4. If necessary, adjust the areal extent of the target project to accommodate the data you have added:
• From the OpenWorks Launcher, select Project > Project Admin.
• When the Project Administration dialog box opens, select the target project, and then select Project > Modify.
• In the Project Modify dialog box, click on Compute to recalculate the areal extent of the project based on all the data it now contains.
The transfer report is also stored in the file you designated and can be viewed or printed at any time. In addition, PDT holds the latest transfer report in memory and will redisplay if you select Options > View Transfer Report.
324 Project Data Transfer: Transferring the Data R2003.12.0
Landmark OpenWorks Project Management
Running Batch Jobs
Running PDT jobs in batch mode offers two main advantages:
• The job specifications you create for one PDT job can be reused for other jobs. So, you can save some setup time.
• You can initiate batch jobs from the command line and run the process in the background.
Creating a Configuration File
To run a PDT job in batch mode, you must first create and save a configuration file that sets all the parameters for the data transfer.
1. In the Project Data Transfer window, set all parameters for the batch job including
• source project• target project• how to handle existing data (overwrite/do not overwrite)• data to be transferred• name and path for transfer report file.
2. Select File > Save As.
A file filter appears. By default, it opens with your home directory displayed and looks for files with a .pdt extension.
R2003.12.0 Project Data Transfer: Running Batch Jobs 325
OpenWorks Project Management Landmark
3. Use the file filter to specify the full path and name for the file; then click on OK.
Editing a Configuration File
If you want to edit an existing configuration file before running a job, do as follows:
1. Open the configuration file in the PDT window by selecting File > Open.
2. Make the changes to the parameter settings.
3. Save the edited file by selecting one of the following:
• File > Save to overwrite the original file.
• File > Save As to save the edited file to a new name and preserve the original file.
Give configuration files a “.pdt” extension.
It’s a good idea to give all configuration files an extension of “.pdt” so you can easily identify and locate them. However, you are not required to do so.
326 Project Data Transfer: Running Batch Jobs R2003.12.0
Landmark OpenWorks Project Management
Running the Job
Once a configuration file has been created and saved, you can initiate the PDT batch job from the command line or from within the PDT main window.
From the Command Line
Enter this command at the system prompt:
pdt -cf path/ConfigFileName.pdt &
where path is the location of the configuration file, and ConfigFileName.pdt is the name of your configuration file.
From the PDT Main Window
1. Open the configuration file for the job by selecting File > Open.
The name of the configuration file is posted in the PDT window, and all the parameter settings specified in the file are set in the window.
2. If you want to save the changed parameters settings, you must save the configuration file. Select File > Save.
3. To run the job, select Controls > Transfer.
R2003.12.0 Project Data Transfer: Running Batch Jobs 327
OpenWorks Project Management Landmark
Command Line Arguments
Project Data Transfer can be run from the command line in a terminal window. The line has the following format:
pdt Arguments &
The Arguments in the command line can be the following:
Command Usage What it does
-a Executes PDT in advanced mode, which provides more transfer options. This option is automatically set if -cf is specified and requires an OpenExplorer Advanced license.
-cf ConfigFile Executes PDT in advanced and batch modes, prevents the user interface from displaying, and uses ConfigFile as its transfer instructions. If -ui is also included, PDT displays its user interface and does not enter batch mode. This option requires an OpenExplorer Advanced license.
-chunk Number Sets Number as the maximum number of objects read from the source project before writing to the target project. Without this option, the default is 500.
-console Opens a console window for displaying terminal output. (Windows 2000 only.)
-convert ConvertedConfigFile Converts a configuration file from an earlier version of PDT to the present version and places the converted file into ConvertedConfigFile. This option prevents the user interface from displaying. The command-line must also specify the original configuration file with -cf. Include -validate to verify the configuration file after conversion. If -ui is included, PDT displays its user interface and does not execute in batch mode.
-fast Uses a faster loading algorithm to initially populate the main data option dialogs for wells, leases, fields, basins, facilities, 2D seismic, and 3D seismic.
-help Prints PDT’s command-line options and their descriptions.
328 Project Data Transfer: Command Line Arguments R2003.12.0
Landmark OpenWorks Project Management
-history Number Sets Number as the maximum number of lines in the report window buffer. Without this option, the default is 1000. Whatever the value of this option, all lines are written to the report file.
-log Number Sets Number as the maximum amount of memory, in MB, used when transferring each log curve. Without this option, the default is 10.
-ui Displays PDT’s user interface when -cf, -convert, or -validate are used. This option requires an OpenExplorer Advanced license.
-validate Validates the configuration file specified with -cf as well and executes without its user interface. This option must be used with -cf and in conjunction with -convert. If -ui is included, PDT’s user interface displays.
-ver Prints PDT’s version information.
Command Usage What it does
R2003.12.0 Project Data Transfer: Command Line Arguments 329
OpenWorks Project Management Landmark
Performance Enhancements
You should notice a marked improvement in how quickly PDT jobs are completed, thanks to two major changes:
• transferring large chunks of data in each read or write operation
• better management of status reporting.
Data Transferred in Chunks
Every time PDT has to switch from reading data in the source project to writing data in the target project, time and computer resources are expended. To minimize these switches and the overhead they entail, PDT now “chunks” large amounts of data in memory before switching from the source project to the target project.
By default the “chunk” size is set to 500. That is, if you are transferring 1000 wells from project A to project B, then PDT will read the first 500 wells from A before it switches to B to write them. Only two context switches would be needed to transfer all 1000 wells.
In general, the larger the chunk size, the better the performance. However, you may reach a point of diminishing returns. Larger chunk sizes consume more memory, and when the memory capacity is exceeded, the computer has to resort to paging. For optimum performance, consider both the size of the transfer job and the amount of memory allocated for your system when setting the chunk size.
Typically, you would set this variable locally, in the terminal window from which you initiated OpenWorks, OpenExplorer, or PDT. Enter the appropriate command for the type of shell you are running:
pdt -chunk Integer
330 Project Data Transfer: Performance Enhancements R2003.12.0
Landmark OpenWorks Project Management
PDT Configuration File Format
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
Version (none) String No 2.5 2.5
This is version 2.5 of the configuration file format.
SourceOWSYSSID Main String No owshells
The owsyssid is where the source project is located.
SourceProject Main String No DSL_SOURCE
The name of the source project.
TargetOWSYSSID Main String No owshells
The owsyssid is where the target project is located.
TargetProject Main String No DSL_TARGET
The name of the target project.
ReportFileMode Report Options
Integer No 1
Legend 1: Append or overwrite an existing report file. (See “Legend 1” on page 393.)
ReportTypeMode Report Options
Integer No 7
Legend 2: Number created from OR’ing bit patterns to determine what to output to report file. (See “Legend 2” on page 393.)
ReportFileName Report Options
String No /home/ interphome/ interp1/pdt.report
Fully qualified filename to be used for report messages during a transfer.
GlobalTransferOptionsOverwrite DataFlag
Global Transfer Options
Integer No 1
Legend 3: Allow existing data to be overwritten. (See “Legend 3” on page 394.)
GlobalTransferOptionsValidate SourceFlag
Global Transfer Options
Integer No 1
Legend 3: When a data type has both preferred and original coordinate fields, allow PDT to check that the original coordinates when converted to the source project CRS match with the preferred coordinates. This takes an extra coordinate conversion. (See “Legend 3” on page 394.)
R2003.12.0 Project Data Transfer: PDT Configuration File Format 331
OpenWorks Project Management Landmark
GlobalTransferOptionsForce TransferFlag
Global Transfer Options
Integer No 0
Legend 3: Force the transfer of data; even though, an error was obtained during coordinate conversion. (See “Legend 3” on page 394.)
GlobalTransferOptionsRename FaultFlag
Global Transfer Options
Integer No 0
Legend 3: Rename faults using criteria specified in subsequent parameters for all fault-related data types that get transferred. (See “Legend 3” on page 394.)
GlobalTransferOptionsFault PrependText
Global Transfer Options
String Yes PRJ1-
The text to prepend onto or remove from all faults if renaming turned on.
GlobalTransferOptionsFault PrependAction
Global Transfer Options
Integer No 0
Legend 19: Specified whether to add or remove the prepend text from faults. (See “Legend 19” on page 402.)
GlobalTransferOptionsRename SurfaceFlag
Global Transfer Options
Integer No 0
Legend 3: Rename surfaces using criteria specified in subsequent parameters for all surface-related data types that get transferred. (See “Legend 3” on page 394.)
GlobalTransferOptionsSurface PrependText
Global Transfer Options
String Yes PRJ1-
The text to prepend onto or remove from all surface if renaming turned on.
GlobalTransferOptionsSurface PrependAction
Global Transfer Options
Integer No 0
Legend 19: Specified whether to add or remove the prepend text from surfaces. (See “Legend 19” on page 402.)
GlobalTransferOptionsRename StratUnitFlag
Global Transfer Options
Integer No 0
Legend 3: Rename strat units using criteria specified in subsequent parameters for all strat unit-related data types that get transferred. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
332 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
GlobalTransferOptionsStratUnit PrependText
Global Transfer Options
String Yes PRJ1-
The text to prepend onto or remove from all strat units if renaming turned on.
GlobalTransferOptionsStratUnit PrependAction
Global Transfer Options
Integer No 0
Legend 19: Specified whether to add or remove the prepend text from strat units. (See “Legend 19” on page 402.)
GlobalAdvancedFilterNewData Flag
Global Advanced Filter
Integer No 1
Legend 3: Allow the creation of new data. This is overridden by each major data type’s advanced filter settings. (See “Legend 3” on page 394.)
GlobalAdvancedFilterUpdateDate TimeFlag
Global Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter. This is overridden by each major data type’s advanced filter settings. (See “Legend 3” on page 394.)
GlobalAdvancedFilterFromDate Time
Global Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. This is overridden by each major data type’s advanced filter settings. (See “Legend 4” on page 394.)
GlobalAdvancedFilterToDateTime Global Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. This is overridden by each major data type’s advanced filter settings. (See “Legend 4” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 333
OpenWorks Project Management Landmark
GlobalAdvancedFilterArealExtent Flag
Global Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter. This is overridden by each major data type’s advanced filter settings. (See “Legend 3” on page 394.)
GlobalAdvancedFilterArealExtent Type
Global Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. This is overridden by each major data type’s advanced filter settings. (See “Legend 5” on page 394.)
GlobalAdvancedFilterArealExtent DataType
Global Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. This is overridden by each major data type’s advanced filter settings. (See “Legend 6” on page 394.)
GlobalAdvancedFilterCustom MinX
Global Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X. This is overridden by each major data type’s advanced filter settings.
GlobalAdvancedFilterCustom MaxX
Global Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X. This is overridden by each major data type’s advanced filter settings.
GlobalAdvancedFilterCustom MinY
Global Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y. This is overridden by each major data type’s advanced filter settings.
GlobalAdvancedFilterCustom MaxY
Global Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y. This is overridden by each major data type’s advanced filter settings.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
334 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
GlobalAdvancedFilterCustomMin Lat
Global Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude. This is overridden by each major data type’s advanced filter settings.
GlobalAdvancedFilterCustomMax Lat
Global Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude. This is overridden by each major data type’s advanced filter settings.
GlobalAdvancedFilterCustomMinLong
Global Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude. This is overridden by each major data type’s advanced filter settings.
GlobalAdvancedFilterCustomMaxLong
Global Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude. This is overridden by each major data type’s advanced filter settings.
GlobalAdvancedFilterTransferNull SpatialFlag
Global Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
BasinDataFlag Main Integer No 0
Legend 3: Listen to the basin data selections and transfer that basin data. (See “Legend 3” on page 394.)
BasinAdvancedFilterNewDataFlag Basin Advanced Filter
Integer No 1
Legend 3: Allow the creation of new basin data. (See “Legend 3” on page 394.)
BasinAdvancedFilterUpdateDate TimeFlag
Basin Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on basin data. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 335
OpenWorks Project Management Landmark
BasinAdvancedFilterFromDate Time
Basin Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no basin data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
BasinAdvancedFilterToDateTime Basin Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no basin data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
BasinAdvancedFilterArealExtent Flag
Basin Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
BasinAdvancedFilterArealExtent Type
Basin Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
BasinAdvancedFilterArealExtent DataType
Basin Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
BasinAdvancedFilterCustomMinX Basin Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
336 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
BasinAdvancedFilterCustomMaxX Basin Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
BasinAdvancedFilterCustomMinY Basin Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
BasinAdvancedFilterCustomMaxY Basin Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
BasinAdvancedFilterCustomMin Lat
Basin Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
BasinAdvancedFilterCustomMax Lat
Basin Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
BasinAdvancedFilterCustomMin Long
Basin Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
BasinAdvancedFilterCustomMax Long
Basin Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
BasinAdvancedFilterTransferNull SpatialFlag
Basin Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
BasinFilterString Basin Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the basin list.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 337
OpenWorks Project Management Landmark
BasinMatchCaseFlag Basin Data Options
Integer No 1
Legend 3: Match case during filtering and searching of basin list. (See “Legend 3” on page 394.)
Basins Basin Data Options
String List Yes Sorted “Basin_Name”, comma separated, no spaces after commas or <All>
Basin 1,Basin 2 or <All>
The basins to transfer
BasinCategories Basin Data Options
String List Yes Comma separated, no spaces after commas or <All>
Basin,Basin Boundary, Country Basin or <All>
Legend 14: The parts of the basins to transfer. (See “Legend 14” on page 401.)
FieldDataFlag Main Integer No 0
Legend 3: Listen to the field data selections and transfer that field data. (See “Legend 3” on page 394.)
FieldAdvancedFilterNewDataFlag Field Advanced Filter
Integer No 1
Legend 3: Allow the creation of new field data. (See “Legend 3” on page 394.)
FieldAdvancedFilterUpdateDate TimeFlag
Field Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on field data. (See “Legend 3” on page 394.)
FieldAdvancedFilterFromDate Time
Field Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no field data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
338 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
FieldAdvancedFilterToDateTime Field Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no field data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
FieldAdvancedFilterArealExtent Flag
Field Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
FieldAdvancedFilterArealExtent Type
Field Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
FieldAdvancedFilterArealExtent DataType
Field Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
FieldAdvancedFilterCustomMinX Field Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
FieldAdvancedFilterCustomMaxX Field Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
FieldAdvancedFilterCustomMinY Field Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 339
OpenWorks Project Management Landmark
FieldAdvancedFilterCustomMaxY Field Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
FieldAdvancedFilterCustomMinLat
Field Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
FieldAdvancedFilterCustomMax Lat
Field Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
FieldAdvancedFilterCustomMin Long
Field Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat, lon areal extent, specifies minimum longitude.
FieldAdvancedFilterCustomMax Long
Field Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
FieldAdvancedFilterTransferNullSpatialFlag
Field Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
FieldLists Field Data Options
String Yes <All Fields>
Field list to use when selecting fields. A special value of <All Fields> can be used to select from among all fields in the project.
FieldFilterString Field Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the field list.
FieldMatchCaseFlag Field Data Options
Integer No 1
Legend 3: Match case during filtering and searching of field list. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
340 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
Fields Field Data Options
String List Yes Sorted “Field_Name”, comma separated, no spaces after commas or <All>
Field 1,Field 2 or <All>
The fields to transfer.
FieldCategories Field Data Options
String List Yes Comma separated, no spaces after commas or <All>
Field Prospect,Field Boundary or <All>
Legend 13: The parts of the fields to transfer. (See “Legend 13” on page 401.)
FieldProdData Field Data Options
String List Yes Comma separated, no spaces after commas or <All>
Production Volume Record (legacy), Production Gas Analysis or <All>
Legend 9: The parts of the legacy production data to transfer. (See “Legend 9” on page 399.)
FieldProdDataFilterDateFlag Field Prod Data Filter
Integer No 0
Legend 3: Apply a start date filter on those production types that have a start date. (See “Legend 3” on page 394.)
FieldProdDataFilterFromDate Field Prod Data Filter
String Yes MM/DD/YYYY or <-Float Units> or <Now>
11/29/2000 or <-1.5 years> or <Now>
Legend 10: If filtering by start date, no production data will be transferred whose start date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDate where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 10” on page 400.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 341
OpenWorks Project Management Landmark
FieldProdDataFilterToDate Field Prod Data Filter
String Yes MM/DD/YYYY or <+Float Units> or <Now>
11/29/2000 or <+1.5 years> or <Now>
Legend 10: If filtering by start date, no production data will be transferred whose start date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDate where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 10” on page 400.)
FieldProdDataFilterZoneNameFlag Field Prod Data Filter
Integer No 0
Legend 3: Apply the zone name filter. (See “Legend 3” on page 394.)
FieldProdDataFilterZones Field Prod Data Filter
String List Yes Sorted, comma separated, no spaces after commas or <All>
N PADRE ISL A,N PADRE ISL A-10 JA,UNKNOWN,ZONE1,ZONE_1,ZONE_2,ZONE_3 or <All>
Only production data whose zone name is in this list are transferred. Valid values come from the VC_ZONE_NAME table.
FieldProdDataMart Field Data Options
String List Yes Comma separated, no spaces after commas or <All>
Pdm Production Hdr,Prod Daily Injection or <All>
Legend 11: The parts of the production data mart to transfer. (See “Legend 11” on page 400.)
FieldProdDataMartFilterZone NameFlag
Field Prod Data Mart Filter
Integer No 0
Legend 3: Apply the zone name filter. (See “Legend 3” on page 394.)
FieldProdDataMartFilterZones Field Prod Data Mart Filter
String List Yes Sorted, comma separated, no spaces after commas or <All>
N PADRE ISL A,N PADRE ISL A-10 JA,UNKNOWN,ZONE1,ZONE_1,ZONE_2,ZONE_3 or <All>
Only production data whose zone name is in this list are transferred. Valid values come from the VC_ZONE_NAME table.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
342 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
LeaseDataFlag Main Integer No 0
Legend 3: Listen to the lease data selections and transfer that lease data. (See “Legend 3” on page 394.)
LeaseAdvancedFilterNewDataFlag Lease Advanced Filter
Integer No 1
Legend 3: Allow the creation of new lease data. (See “Legend 3” on page 394.)
LeaseAdvancedFilterUpdateDate TimeFlag
Lease Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on lease data. (See “Legend 3” on page 394.)
LeaseAdvancedFilterFromDate Time
Lease Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no lease data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
LeaseAdvancedFilterToDateTime Lease Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no lease data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
LeaseAdvancedFilterArealExtent Flag
Lease Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
LeaseAdvancedFilterArealExtent Type
Lease Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 343
OpenWorks Project Management Landmark
LeaseAdvancedFilterArealExtent DataType
Lease Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
LeaseAdvancedFilterCustomMinX Lease Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
LeaseAdvancedFilterCustomMaxX Lease Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
LeaseAdvancedFilterCustomMinY Lease Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
LeaseAdvancedFilterCustomMaxY Lease Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
LeaseAdvancedFilterCustomMin Lat
Lease Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
LeaseAdvancedFilterCustomMax Lat
Lease Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
LeaseAdvancedFilterCustomMin Long
Lease Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
LeaseAdvancedFilterCustomMax Long
Lease Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
344 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
LeaseAdvancedFilterTransferNull SpatialFlag
Lease Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
LeaseLists Lease Data Options
String Yes <All Leases>
Lease list to use when selecting leases. A special value of <All Leases> can be used to select from among all leases in the project.
LeaseFilterString Lease Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the lease list.
LeaseMatchCaseFlag Lease Data Options
Integer No 1
Legend 3: Match case during filtering and searching of lease list. (See “Legend 3” on page 394.)
Leases Lease Data Options
String List Yes Sorted “Lease_No | Sublease_No | Tract_No”, comma separated, no spaces after commas or <All>
Lease 1,Lease 2 or <All>
The leases to transfer.
LeaseCategories Lease Data Options
String List Yes Comma separated, no spaces after commas or <All>
Lease,Lease Narrative or <All>
Legend 12: The parts of the leases to transfer. (See “Legend 12” on page 401.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 345
OpenWorks Project Management Landmark
LeaseProdData Lease Data Options
String List Yes Comma separated, no spaces after commas or <All>
Production Volume Record (legacy), Production Gas Analysis or <All>
Legend 9: The parts of the legacy production data to transfer. (See “Legend 9” on page 399.)
LeaseProdDataFilterDateFlag Lease Prod Data Filter
Integer No 0
Legend 3: Apply a start date filter on those production types that have a start date. (See “Legend 3” on page 394.)
LeaseProdDataFilterFromDate Lease Prod Data Filter
String Yes MM/DD/YYYY or <-Float Units> or <Now>
11/29/2000 or <-1.5 years> or <Now>
Legend 10: If filtering by start date, no production data will be transferred whose start date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDate where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 10” on page 400.)
LeaseProdDataFilterToDate Lease Prod Data Filter
String Yes MM/DD/YYYY or <+Float Units> or <Now>
11/29/2000 or <+1.5 years> or <Now>
Legend 10: If filtering by start date, no production data will be transferred whose start date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDate where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 10” on page 400.)
LeaseProdDataFilterZoneNameFlag
Lease Prod Data Filter
Integer No 0
Legend 3: Apply the zone name filter. (See “Legend 3” on page 394.)
LeaseProdDataFilterZones Lease Prod Data Filter
String List Yes Sorted, comma separated, no spaces after commas or <All>
N PADRE ISL A,N PADRE ISL A-10 JA,UNKNOWN,ZONE1,ZONE_1,ZONE_2,ZONE_3 or <All>
Only production data whose zone name is in this list are transferred. Valid values come from the VC_ZONE_NAME table.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
346 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
LeaseProdDataMart Lease Data Options
String List Yes Comma separated, no spaces after commas or <All>
Pdm Production Hdr,Prod Daily Injection or <All>
Legend 11: The parts of the production data mart to transfer. (See “Legend 11” on page 400.)
LeaseProdDataMartFilterZone NameFlag
Lease Prod Data Mart Filter
Integer No 0
Legend 3: Apply the zone name filter. (See “Legend 3” on page 394.)
LeaseProdDataMartFilterZones Lease Prod Data Mart Filter
String List Yes Sorted, comma separated, no spaces after commas or <All>
N PADRE ISL A,N PADRE ISL A-10 JA,UNKNOWN,ZONE1,ZONE_1,ZONE_2,ZONE_3 or <All>
Only production data whose zone name is in this list are transferred. Valid values come from the VC_ZONE_NAME table.
FacilityDataFlag Main Integer No 0
Legend 3: Listen to the facility data selections and transfer that facility data. (See “Legend 3” on page 394.)
FacilityAdvancedFilterNewData Flag
Facility Advanced Filter
Integer No 1
Legend 3: Allow the creation of new facility data. (See “Legend 3” on page 394.)
FacilityAdvancedFilterUpdateDate TimeFlag
Facility Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on facility data. (See “Legend 3” on page 394.)
FacilityAdvancedFilterFromDate Time
Facility Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no facility data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 347
OpenWorks Project Management Landmark
FacilityAdvancedFilterToDateTime Facility Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no facility data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
FacilityAdvancedFilterArealExtent Flag
Facility Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
FacilityAdvancedFilterArealExtent Type
Facility Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
FacilityAdvancedFilterArealExtent DataType
Facility Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
FacilityAdvancedFilterCustom MinX
Facility Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
FacilityAdvancedFilterCustom MaxX
Facility Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
FacilityAdvancedFilterCustom MinY
Facility Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
348 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
FacilityAdvancedFilterCustom MaxY
Facility Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
FacilityAdvancedFilterCustom MinLat
Facility Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
FacilityAdvancedFilterCustom MaxLat
Facility Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
FacilityAdvancedFilterCustom MinLong
Facility Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
FacilityAdvancedFilterCustom MaxLong
Facility Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
FacilityAdvancedFilterTransfer NullSpatialFlag
Facility Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
FacilityFilterString Facility Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the facility list.
FacilityMatchCaseFlag Facility Data Options
Integer No 1
Legend 3: Match case during filtering and searching of facility list. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 349
OpenWorks Project Management Landmark
Facilities Facility Data Options
String List Yes Sorted “Facility_Name”, comma separated, no spaces after commas or <All>
Facility 1,Facility 2 or <All>
The facilities to transfer.
FacilityProdData Facility Data Options
String List Yes Comma separated, no spaces after commas or <All>
Production Volume Record (legacy), Production Gas Analysis or <All>
Legend 9: The parts of the legacy production data to transfer. (See “Legend 9” on page 399.)
FacilityProdDataFilterDateFlag Facility Prod Data Filter
Integer No 0
Legend 3: Apply a start date filter on those production types that have a start date. (See “Legend 3” on page 394.)
FacilityProdDataFilterFromDate Facility Prod Data Filter
String Yes MM/DD/YYYY or <-Float Units> or <Now>
11/29/2000 or <-1.5 years> or <Now>
Legend 10: If filtering by start date, no production data will be transferred whose start date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDate where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 10” on page 400.)
FacilityProdDataFilterToDate Facility Prod Data Filter
String Yes MM/DD/YYYY or <+Float Units> or <Now>
11/29/2000 or <+1.5 years> or <Now>
Legend 10: If filtering by start date, no production data will be transferred whose start date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDate where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 10” on page 400.)
FacilityProdDataFilterZoneName Flag
Facility Prod Data Filter
Integer No 0
Legend 3: Apply the zone name filter. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
350 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
FacilityProdDataFilterZones Facility Prod Data Filter
String List Yes Sorted, comma separated, no spaces after commas or <All>
N PADRE ISL A,N PADRE ISL A-10 JA,UNKNOWN,ZONE1,ZONE_1,ZONE_2,ZONE_3 or <All>
Only production data whose zone name is in this list are transferred. Valid values come from the VC_ZONE_NAME table.
FacilityProdDataMart Facility Data Options
String List Yes Comma separated, no spaces after commas or <All>
Pdm Production Hdr,Prod Daily Injection or <All>
Legend 11: The parts of the production data mart to transfer. (See “Legend 11” on page 400.)
FacilityProdDataMartFilterZone NameFlag
Facility Prod Data Mart Filter
Integer No 0
Legend 3: Apply the zone name filter. (See “Legend 3” on page 394.)
FacilityProdDataMartFilterZones Facility Prod Data Mart Filter
String List Yes Sorted, comma separated, no spaces after commas or <All>
N PADRE ISL A,N PADRE ISL A-10 JA,UNKNOWN,ZONE1,ZONE_1,ZONE_2,ZONE_3 or <All>
Only production data whose zone name is in this list are transferred. Valid values come from the VC_ZONE_NAME table.
WellDataFlag Main Integer No 0
Legend 3: Listen to the well data selections and transfer that well data. (See “Legend 3” on page 394.)
WellOptionLogCurveFlag Log Curve Types
Integer No 1
Legend 3: Apply the log curve type filter. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 351
OpenWorks Project Management Landmark
WellOptionLogCurveNames Log Curve Types
String List Yes Sorted, comma separated, no spaces after commas or <All>
AZIM,Acoustic_Wave_Travel_Time,Effective_Porosity or <All>
If filtering by log curve type, only log curves whose type name is in this list are transferred. Valid values come from the VC_LOG_CRV_NAME table.
WellOptionInterpreterTransferFlag Well Interpreter Options
Integer No 0
Legend 3: Apply the interpreter filter. (See “Legend 3” on page 394.)
WellOptionInterpreterExcludes Well Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas
ABC,LGC,GQS
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is not transferred.
WellOptionInterpreterRenames Well Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas, original (rename)
FAI(HEL),SPC(TAR)
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is renamed to whatever is in parenthesis when transferred.
WellOptionInterpreterTransferNull Flag
Well Interpreter Options
Integer No 1
Legend 3: If filtering by interpreter, allow the transfer of data with NULL data source fields. (See “Legend 3” on page 394.)
WellAdvancedFilterNewDataFlag Well Advanced Filter
Integer No 1
Legend 3: Allow the creation of new well data. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
352 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
WellAdvancedFilterUpdateDate TimeFlag
Well Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on well data. (See “Legend 3” on page 394.)
WellAdvancedFilterFromDateTime Well Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no well data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
WellAdvancedFilterToDateTime Well Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no well data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
WellAdvancedFilterArealExtent Flag
Well Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
WellAdvancedFilterArealExtent Type
Well Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
WellAdvancedFilterArealExtent DataType
Well Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 353
OpenWorks Project Management Landmark
WellAdvancedFilterCustomMinX Well Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
WellAdvancedFilterCustomMaxX Well Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
WellAdvancedFilterCustomMinY Well Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
WellAdvancedFilterCustomMaxY Well Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
WellAdvancedFilterCustomMinLat Well Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
WellAdvancedFilterCustomMaxLat Well Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
WellAdvancedFilterCustomMin Long
Well Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
WellAdvancedFilterCustomMax Long
Well Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
WellAdvancedFilterTransferNull SpatialFlag
Well Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
354 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
WellLists Well Data Options
String Yes <All Wells>
Well list to use when selecting wells. A special value of <All Wells> can be used to select from among all wells in the project.
WellFormatType Well Data Options
Integer No 0
Legend 7: The format the wells are displayed in the well list. (See “Legend 7” on page 394.)
WellFilterString Well Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the well list.
WellMatchCaseFlag Well Data Options
Integer No 1
Legend 3: Match case during filtering and searching of well list. (See “Legend 3” on page 394.)
WellUWIs Well Data Options
String List Yes Sorted "Well_UWI", comma separated, no spaces after commas or <All>
ASCII_00001,ASCII_00002 or <All>
The wells to transfer.
WellCategories Well Data Options
String List Yes Comma separated, no spaces after commas or <All>
Well Header,Well Operator or <All>
Legend 8: The parts of the wells to transfer. (See “Legend 8” on page 394.)
WellProdData Well Data Options
String List Yes Comma separated, no spaces after commas or <All>
Production Volume Record (legacy), Production Gas Analysis or <All>
Legend 9: The parts of the legacy production data to transfer. (See “Legend 9” on page 399.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 355
OpenWorks Project Management Landmark
WellProdDataFilterDateFlag Well Prod Data Filter
Integer No 0
Legend 3: Apply a start date filter on those production types that have a start date. (See “Legend 3” on page 394.)
WellProdDataFilterFromDate Well Prod Data Filter
String Yes MM/DD/YYYY or <-Float Units> or <Now>
11/29/2000 or <-1.5 years> or <Now>
Legend 10: If filtering by start date, no production data will be transferred whose start date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDate where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 10” on page 400.)
WellProdDataFilterToDate Well Prod Data Filter
String Yes MM/DD/YYYY or <+Float Units> or <Now>
11/29/2000 or <+1.5 years> or <Now>
Legend 10: If filtering by start date, no production data will be transferred whose start date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDate where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 10” on page 400.)
WellProdDataFilterZoneNameFlag Well Prod Data Filter
Integer No 0
Legend 3: Apply the zone name filter. (See “Legend 3” on page 394.)
WellProdDataFilterZones Well Prod Data Filter
String List Yes Sorted, comma separated, no spaces after commas or <All>
N PADRE ISL A,N PADRE ISL A-10 JA,UNKNOWN,ZONE1,ZONE_1,ZONE_2,ZONE_3 or <All>
If filtering by zone name, only production data whose zone name is in this list are transferred. Valid values come from the VC_ZONE_NAME table.
WellProdDataMart Well Data Options
String List Yes Comma separated, no spaces after commas or <All>
Pdm Production Hdr,Prod Daily Injection or <All>
Legend 11: The parts of the production data mart to transfer. (See “Legend 11” on page 400.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
356 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
WellProdDataMartFilterZoneName Flag
Well Prod Data Mart Filter
Integer No 0
Legend 3: Apply the zone name filter. (See “Legend 3” on page 394.)
WellProdDataMartFilterZones Well Prod Data Mart Filter
String List Yes Sorted, comma separated, no spaces after commas or <All>
N PADRE ISL A,N PADRE ISL A-10 JA,UNKNOWN,ZONE1,ZONE_1,ZONE_2,ZONE_3 or <All>
Only production data whose zone name is in this list are transferred. Valid values come from the VC_ZONE_NAME table.
2DSeismicLineDataFlag Main Integer No 0
Legend 3: Listen to the 2D line data selections and transfer that 2D line data. (See “Legend 3” on page 394.)
2DSeismicLineAdvancedFilter NewDataFlag
2D Seismic Advanced Filter
Integer No 1
Legend 3: Allow the creation of new 2D seismic data. (See “Legend 3” on page 394.)
2DSeismicLineAdvancedFilter UpdateDateTimeFlag
2D Seismic Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on 2D seismic data. (See “Legend 3” on page 394.)
2DSeismicLineAdvancedFilter FromDateTime
2D Seismic Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no 2D seismic data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 357
OpenWorks Project Management Landmark
2DSeismicLineAdvancedFilterTo DateTime
2D Seismic Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no 2D seismic data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
2DSeismicLineAdvancedFilter ArealExtentFlag
2D Seismic Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
2DSeismicLineAdvancedFilter ArealExtentType
2D Seismic Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
2DSeismicLineAdvancedFilter ArealExtentDataType
2D Seismic Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
2DSeismicLineAdvancedFilter CustomMinX
2D Seismic Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
2DSeismicLineAdvancedFilter CustomMaxX
2D Seismic Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
2DSeismicLineAdvancedFilter CustomMinY
2D Seismic Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
358 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
2DSeismicLineAdvancedFilter CustomMaxY
2D Seismic Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
2DSeismicLineAdvancedFilter CustomMinLat
2D Seismic Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
2DSeismicLineAdvancedFilter CustomMaxLat
2D Seismic Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
2DSeismicLineAdvancedFilter CustomMinLong
2D Seismic Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
2DSeismicLineAdvancedFilter CustomMaxLong
2D Seismic Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
2DSeismicLineAdvancedFilter TransferNullSpatialFlag
2D Seismic Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
2DSeismicLineLists 2D Seismic Data Options
String Yes <All 2D Seismic Lines>
2D Seismic list to use when selecting 2D seismic lines. A special value of <All 2D Seismic Lines> can be used to select from among all 2D lines in the project.
2DSeismicLineFilterString 2D Seismic Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the 2D line list.
2DSeismicLineMatchCaseFlag 2D Seismic Data Options
Integer No 1
Legend 3: Match case during filtering and searching of 2D line list. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 359
OpenWorks Project Management Landmark
2DSeismicLines 2D Seismic Data Options
String List Yes Sorted “Seis2D_Unique_Line_Id”, comma separated, no spaces after commas or <All>
2DSeismic Line 1,2D Seismic Line 2 or <All>
The 2D lines to transfer.
2DSeismicLineCategories 2D Seismic Data Options
String List Yes Comma separated, no spaces after commas or <All>
Seis Geom Set2 D Line,Binset Grid2 D Shpt Trace or <All>
Legend 15: The parts of the 2D lines to transfer. (See “Legend 15” on page 401.)
3DSeismicSurveyDataFlag Main Integer No 0
Legend 3: Listen to the 3D survey data selections and transfer that 3D survey data. (See “Legend 3” on page 394.)
3DSeismicSurveyAdvancedFilter NewDataFlag
3D Seismic Advanced Filter
Integer No 1
Legend 3: Allow the creation of new 3D seismic data. (See “Legend 3” on page 394.)
3DSeismicSurveyAdvancedFilter UpdateDateTimeFlag
3D Seismic Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on 3D seismic data. (See “Legend 3” on page 394.)
3DSeismicSurveyAdvancedFilter FromDateTime
3D Seismic Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no 3D seismic data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
360 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
3DSeismicSurveyAdvancedFilter ToDateTime
3D Seismic Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no 3D seismic data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
3DSeismicSurveyAdvancedFilter ArealExtentFlag
3D Seismic Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
3DSeismicSurveyAdvancedFilter ArealExtentType
3D Seismic Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
3DSeismicSurveyAdvancedFilter ArealExtentDataType
3D Seismic Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
3DSeismicSurveyAdvancedFilter CustomMinX
3D Seismic Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
3DSeismicSurveyAdvancedFilter CustomMaxX
3D Seismic Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
3DSeismicSurveyAdvancedFilter CustomMinY
3D Seismic Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 361
OpenWorks Project Management Landmark
3DSeismicSurveyAdvancedFilter CustomMaxY
3D Seismic Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
3DSeismicSurveyAdvancedFilter CustomMinLat
3D Seismic Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
3DSeismicSurveyAdvancedFilter CustomMaxLat
3D Seismic Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
3DSeismicSurveyAdvancedFilter CustomMinLong
3D Seismic Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
3DSeismicSurveyAdvancedFilter CustomMaxLong
3D Seismic Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
3DSeismicSurveyAdvancedFilter TransferNullSpatialFlag
3D Seismic Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
3DSeismicSurveyFilterString 3D Seismic Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the 3D survey list.
3DSeismicSurveyMatchCaseFlag 3D Seismic Data Options
Integer No 1
Legend 3: Match case during filtering and searching of 3D survey list. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
362 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
3DSeismicSurveys 3D Seismic Data Options
String List Yes Sorted “Seis_Geom_Set_Nm”, comma separated, no spaces after commas or <All>
3D Seismic 1,3D Seismic 2 or <All>
The 3D surveys to transfer.
3DSeismicSurveyCategories 3D Seismic Data Options
String List Yes Comma separated, no spaces after commas or <All>
Seis Geom Set3 D Survey,Binset Grid3 D Grid or <All>
Legend 16: The parts of the 3D surveys to transfer. (See “Legend 16” on page 401.)
FaultDataFlag Main Integer No 0
Legend 3: Listen to the fault data selections and transfer that fault data. (See “Legend 3” on page 394.)
FaultOptionInterpreterTransferFlag Fault Interpreter Options
Integer No 0
Legend 3: Apply the interpreter filter. (See “Legend 3” on page 394.)
FaultOptionInterpreterExcludes Fault Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas
ABC,LGC,GQS
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is not transferred.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 363
OpenWorks Project Management Landmark
FaultOptionInterpreterRenames Fault Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas, original(rename)
FAI(HEL),SPC(TAR)
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is renamed to whatever is in parenthesis when transferred.
FaultOptionInterpreterTransfer NullFlag
Fault Interpreter Options
Integer No 0
Legend 3: If filtering by interpreter, allow the transfer of data with NULL data source fields. (See “Legend 3” on page 394.)
FaultSegFilterDomainFlag Fault Segment Filter
Integer No 0
Legend 3: Apply a domain filter on fault segment data. (See “Legend 3” on page 394.)
FaultSegFilterDomain Fault Segment Filter
Integer No 0
Legend 17: If filtering by domain, specifies which domain to transfer. (See “Legend 17” on page 401.)
FaultSegFilterSurveyNameFlag Fault Segment Filter
Integer No 0
Legend 3: Apply a survey name filter on fault segment data. (See “Legend 3” on page 394.)
FaultSegFilterSurveys Fault Segment Filter
String List Yes Sorted, comma separated, no spaces after commas or <All>
fl3d_nw,fl3d_sw or <All>
If filtering by survey name, only fault segments whose survey name is in this list are transferred. Valid values come from the LINE_SRC_SURVEY field of the FAULT_SEGMENT table.
FaultAdvancedFilterNewDataFlag Fault Advanced Filter
Integer No 1
Legend 3: Allow the creation of new fault data. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
364 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
FaultAdvancedFilterUpdateDate TimeFlag
Fault Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on fault data. (See “Legend 3” on page 394.)
FaultAdvancedFilterFromDate Time
Fault Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no fault data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
FaultAdvancedFilterToDateTime Fault Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no fault data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
FaultAdvancedFilterArealExtent Flag
Fault Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
FaultAdvancedFilterArealExtent Type
Fault Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
FaultAdvancedFilterArealExtent DataType
Fault Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 365
OpenWorks Project Management Landmark
FaultAdvancedFilterCustomMinX Fault Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
FaultAdvancedFilterCustomMaxX Fault Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
FaultAdvancedFilterCustomMinY Fault Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
FaultAdvancedFilterCustomMaxY Fault Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
FaultAdvancedFilterCustomMinLat
Fault Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
FaultAdvancedFilterCustomMax Lat
Fault Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
FaultAdvancedFilterCustomMin Long
Fault Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
FaultAdvancedFilterCustomMax Long
Fault Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
FaultAdvancedFilterTransferNull SpatialFlag
Fault Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
366 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
FaultSetsDir Fault Data Options
String Yes /home/filer1home/myhome
Fully qualified pathname to use when looking for fault set files (*.fst).
FaultSet Fault Data Options
String Yes <All Faults>
Fault set to use when selecting faults. A special value of <All Faults> can be used to select from among all faults in the project.
FaultFilterString Fault Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the fault list.
FaultMatchCaseFlag Fault Data Options
Integer No 1
Legend 3: Match case during filtering and searching of fault list. (See “Legend 3” on page 394.)
Faults Fault Data Options
String List Yes Sorted “Fault_Name”, comma separated, no spaces after commas or <All>
Fault 1,Fault 2 or <All>
The faults to transfer. A special value <Unassigned Segments> can be added to cause the transfer of those segments without and relation to a fault.
FaultCategories Fault Data Options
String List Yes Comma separated, no spaces after commas or <All>
Fault,Fault Display or <All>
Legend 18: The parts of the faults to transfer. (See “Legend 18” on page 402.)
QueryDataFlag Main Integer No 0
Legend 3: Listen to the query data selections and transfer that query data. (See “Legend 3” on page 394.)
QueryAdvancedFilterNewDataFlag Query Advanced Filter
Integer No 1
Legend 3: Allow the creation of new query data. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 367
OpenWorks Project Management Landmark
QueryAdvancedFilterUpdateDate TimeFlag
Query Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on query data. (See “Legend 3” on page 394.)
QueryAdvancedFilterFromDate Time
Query Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no query data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
QueryAdvancedFilterToDateTime Query Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no query data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
QueryAdvancedFilterArealExtent Flag
Query Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
QueryAdvancedFilterArealExtent Type
Query Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
QueryAdvancedFilterArealExtentDataType
Query Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
368 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
QueryAdvancedFilterCustomMinX Query Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
QueryAdvancedFilterCustomMaxX
Query Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
QueryAdvancedFilterCustomMinY Query Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
QueryAdvancedFilterCustomMaxY
Query Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
QueryAdvancedFilterCustomMin Lat
Query Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
QueryAdvancedFilterCustomMax Lat
Query Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
QueryAdvancedFilterCustomMin Long
Query Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
QueryAdvancedFilterCustomMax Long
Query Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
QueryAdvancedFilterTransferNull SpatialFlag
Query Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 369
OpenWorks Project Management Landmark
QueryFilterString Query Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the query list.
QueryMatchCaseFlag Query Data Options
Integer No 1
Legend 3: Match case during filtering and searching of query list. (See “Legend 3” on page 394.)
Queries Query Data Options
String List Yes Sorted “Query_Name | User_Name”, comma separated, no spaces after commas or <All>
Query 1,Query 2 or <All>
The queries to transfer.
StratColumnDataFlag Main Integer No 0
Legend 3: Listen to the strat column data selections and transfer that strat column data. (See “Legend 3” on page 394.)
StratColumnOptionInterpreter TransferFlag
Strat Column Interpreter Options
Integer No 0
Legend 3: Apply the interpreter filter. (See “Legend 3” on page 394.)
StratColumnOptionInterpreter Excludes
Strat Column Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas
ABC,LGC,GQS
If filtering by interpreter, all data that has a data source field with a value, matching one in this list, is not transferred.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
370 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
StratColumnOptionInterpreter Renames
Strat Column Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas, original (rename)
FAI(HEL),SPC(TAR)
If filtering by interpreter, all data that has a data source field with a value that matches one in this list is renamed to whatever is in parenthesis when transferred.
StratColumnOptionInterpreter TransferNullFlag
Strat Column Interpreter Options
Integer No 0
Legend 3: If filtering by interpreter, allow the transfer of data with NULL data source fields. (See “Legend 3” on page 394.)
StratColumnAdvancedFilterNew DataFlag
Strat Column Advanced Filter
Integer No 1
Legend 3: Allow the creation of new strat column data. (See “Legend 3” on page 394.)
StratColumnAdvancedFilterUpdate DateTimeFlag
Strat Column Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on strat column data. (See “Legend 3” on page 394.)
StratColumnAdvancedFilterFrom DateTime
Strat Column Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by the update or create date, no strat column data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 371
OpenWorks Project Management Landmark
StratColumnAdvancedFilterToDate Time
Strat Column Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no strat column data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
StratColumnAdvancedFilterAreal ExtentFlag
Strat Column Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
StratColumnAdvancedFilterAreal ExtentType
Strat Column Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
StratColumnAdvancedFilterAreal ExtentDataType
Strat Column Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
StratColumnAdvancedFilter CustomMinX
Strat Column Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
StratColumnAdvancedFilter CustomMaxX
Strat Column Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
StratColumnAdvancedFilter CustomMinY
Strat Column Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
372 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
StratColumnAdvancedFilter CustomMaxY
Strat Column Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
StratColumnAdvancedFilterCustomMinLat
Strat Column Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
StratColumnAdvancedFilter CustomMaxLat
Strat Column Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
StratColumnAdvancedFilter CustomMinLong
Strat Column Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
StratColumnAdvancedFilter CustomMaxLong
Strat Column Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
StratColumnAdvancedFilter TransferNullSpatialFlag
Strat Column Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
StratColumnFilterString Strat Column Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the strat column list.
StratColumnMatchCaseFlag Strat Column Data Options
Integer No 1
Legend 3: Match case during filtering and searching of strat column list. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 373
OpenWorks Project Management Landmark
StratColumns Strat Column Data Options
String List Yes Sorted "Column_Name", comma separated, no spaces after commas or <All>
Col 1,Col 2 or <All>
The strat columns to transfer.
InterpretationDataFlag Main Integer No 0
Legend 3: Listen to the interpretation data selections and transfer that interpretation data. (See “Legend 3” on page 394.)
InterpretationOptionInterpreter TransferFlag
Interpretation Interpreter Options
Integer No 0
Legend 3: Apply the interpreter filter. (See “Legend 3” on page 394.)
InterpretationOptionInterpreter Excludes
Interpretation Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas
ABC,LGC,GQS
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is not transferred.
InterpretationOptionInterpreter Renames
Interpretation Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas, original (rename)
FAI(HEL),SPC(TAR)
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is renamed to whatever is in parenthesis when transferred.
InterpretationOptionInterpreter TransferNullFlag
Interpretation Interpreter Options
Integer No 0
Legend 3: If filtering by interpreter, allow the transfer of data with NULL data source fields. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
374 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
InterpretationAdvancedFilterNew DataFlag
Interpretation Advanced Filter
Integer No 1
Legend 3: Allow the creation of new interpretation data. (See “Legend 3” on page 394.)
InterpretationAdvancedFilter UpdateDateTimeFlag
Interpretation Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on interpretation data. (See “Legend 3” on page 394.)
InterpretationAdvancedFilter FromDateTime
Interpretation Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no interpretation data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
InterpretationAdvancedFilterTo DateTime
Interpretation Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no interpretation data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
InterpretationAdvancedFilterAreal ExtentFlag
Interpretation Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
InterpretationAdvancedFilterAreal ExtentType
Interpretation Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 375
OpenWorks Project Management Landmark
InterpretationAdvancedFilterAreal ExtentDataType
Interpretation Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
InterpretationAdvancedFilter CustomMinX
Interpretation Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
InterpretationAdvancedFilter CustomMaxX
Interpretation Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
InterpretationAdvancedFilter CustomMinY
Interpretation Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
InterpretationAdvancedFilter CustomMaxY
Interpretation Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
InterpretationAdvancedFilter CustomMinLat
Interpretation Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
InterpretationAdvancedFilter CustomMaxLat
Interpretation Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
InterpretationAdvancedFilter CustomMinLong
Interpretation Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
InterpretationAdvancedFilter CustomMaxLong
Interpretation Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
376 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
InterpretationAdvancedFilter TransferNullSpatialFlag
Interpretation Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
InterpretationDataTypes Interpretation Data Options
String List Yes Comma separated, no spaces after commas or <All>
Point Set,Mapping Polygon or <All>
Legend 20: Which interpretation data types to show in bottom list. (See “Legend 20” on page 402.)
InterpretationSurfaces Interpretation Data Options
String List Yes Sorted, comma separated, no spaces after commas or <All>
Surface1,Surface2,Surface3 or <All>
Only interpretation data whose geo-type is SURFACE and geo-name is in this list are transferred. Valid values come from the VC_PICKSURF_NAME table.
InterpretationStratUnits Interpretation Data Options
String List Yes Sorted, comma separated, no spaces after commas or <All>
Unit1,Unit2,Unit3 or <All>
Only interpretation data whose geo-type is STRAT_UNIT and geo-name is in this list are transferred. Valid values come from the VC_STRATUNITNAME table.
InterpretationFaults Interpretation Data Options
String List Yes Sorted, comma separated, no spaces after commas or <All>
F1,F2,F3 or <All>
Only interpretation data whose geo-type is FAULT and geo-name is in this list are transferred. Valid values come from the FAULT table.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 377
OpenWorks Project Management Landmark
InterpretationFilterString Interpretation Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the interpretation list.
InterpretationMatchCaseFlag Interpretation Data Options
Integer No 1
Legend 3: Match case during filtering and searching of interpretation list. (See “Legend 3” on page 394.)
Interpretation Interpretation Data Options
String List Yes Sorted "Data_Type | Geo_Type | Geo_Name | Map_Data_Set_Name | Data_Source | Attribute", comma separated, no spaces after commas or <All>
Grid | FAULT | F1 | Map1 | LGC | Z_VALUE,Grid | FAULT | F2 | Map2 | LGC | Z_VALUE or <All>
The interpretation to transfer.
InterpretationAutomaticUpdateFlag Interpretation Data Options
Integer No 1
Legend 3: Specifies whether the bottom list is updated after every change to the upper four lists or if the user must hit the Update button to force a refresh. (See “Legend 3” on page 394.)
LineofSectionDataFlag Main Integer No 0
Legend 3: Listen to the line of section data selections and transfer that line of section data. (See “Legend 3” on page 394.)
LineofSectionOptionInterpreter TransferFlag
Line of Section Interpreter Options
Integer No 0
Legend 3: Apply the interpreter filter. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
378 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
LineofSectionOptionInterpreter Excludes
Line of Section Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas
ABC,LGC,GQS
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is not transferred.
LineofSectionOptionInterpreter Renames
Line of Section Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas, original (rename)
FAI(HEL),SPC(TAR)
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is renamed to whatever is in parenthesis when transferred.
LineofSectionOptionInterpreter TransferNullFlag
Line of Section Interpreter Options
Integer No 0
Legend 3: If filtering by interpreter, allow the transfer of data with NULL data source fields. (See “Legend 3” on page 394.)
LineofSectionOptionSurfaceFlag Surface Filter Integer No 0
Legend 3: Apply the surface filter. (See “Legend 3” on page 394.)
LineofSectionOptionSurfaces Surface Filter String List Yes Surface1,Surface2,Surface3 or <All>
Only line of section data that has a surface profile child with surface name in this list are transferred. Valid values come from the VC_PICKSURF_NAME table.
LineofSectionOptionFaultFlag Fault Filter Integer No 0
Legend 3: Apply the fault filter. (See “Legend 3” on page 394.)
LineofSectionOptionFaults Fault Filter String List Yes F1,F2,F3 or <All>
Only line of section data that has a fault profile child with fault name in this list are transferred. Valid values come from the FAULT table.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 379
OpenWorks Project Management Landmark
LineofSectionAdvancedFilterNew DataFlag
Line of Section Advanced Filter
Integer No 1
Legend 3: Allow the creation of new line of section data. (See “Legend 3” on page 394.)
LineofSectionAdvancedFilter UpdateDateTimeFlag
Line of Section Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on line of section data. (See “Legend 3” on page 394.)
LineofSectionAdvancedFilterFrom DateTime
Line of Section Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no line of section data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
LineofSectionAdvancedFilterTo DateTime
Line of Section Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no line of section data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
LineofSectionAdvancedFilterAreal ExtentFlag
Line of Section Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
LineofSectionAdvancedFilterAreal ExtentType
Line of Section Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
380 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
LineofSectionAdvancedFilterAreal ExtentDataType
Line of Section Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
LineofSectionAdvancedFilter CustomMinX
Line of Section Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
LineofSectionAdvancedFilter CustomMaxX
Line of Section Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
LineofSectionAdvancedFilter CustomMinY
Line of Section Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
LineofSectionAdvancedFilter CustomMaxY
Line of Section Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
LineofSectionAdvancedFilter CustomMinLat
Line of Section Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
LineofSectionAdvancedFilter CustomMaxLat
Line of Section Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 381
OpenWorks Project Management Landmark
LineofSectionAdvancedFilter CustomMinLong
Line of Section Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
LineofSectionAdvancedFilter CustomMaxLong
Line of Section Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
LineofSectionAdvancedFilter TransferNullSpatialFlag
Line of Section Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
LineOfSectionFilterString Line of Section Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the line of section list.
LineOfSectionMatchCaseFlag Line of Section Data Options
Integer No 1
Legend 3: Match case during filtering and searching of line of section list. (See “Legend 3” on page 394.)
LineOfSections Line of Section Data Options
String List Yes Sorted "Base_Line_Name", comma separated, no spaces after commas or <All>
Line1,Line2 or <All>
The line of sections to transfer.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
382 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
LineOfSectionCategories Line of Section Data Options
String List Yes Comma separated, no spaces after commas or <All>
Line of Section,Well Projections or <All>
Legend 22: The parts of the line of sections to transfer. (See “Legend 22” on page 402.)
WellTemplateDataFlag Main Integer No 0
Legend 3: Listen to the well template data selections and transfer that well template data. (See “Legend 3” on page 394.)
WellTemplateOptionInterpreter TransferFlag
Well Template Interpreter Options
Integer No 0
Legend 3: Apply the interpreter filter. (See “Legend 3” on page 394.)
WellTemplateOptionInterpreter Excludes
Well Template Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas
ABC,LGC,GQS
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is not transferred.
WellTemplateOptionInterpreter Renames
Well Template Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas, original (rename)
FAI(HEL),SPC(TAR)
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is renamed to whatever is in parenthesis when transferred.
WellTemplateOptionInterpreter TransferNullFlag
Well Template Interpreter Options
Integer No 0
Legend 3: If filtering by interpreter, allow the transfer of data with NULL data source fields. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 383
OpenWorks Project Management Landmark
WellTemplateAdvancedFilterNew DataFlag
Well Template Advanced Filter
Integer No 1
Legend 3: Allow the creation of new well template data. (See “Legend 3” on page 394.)
WellTemplateAdvancedFilter UpdateDateTimeFlag
Well Template Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on well template data. (See “Legend 3” on page 394.)
WellTemplateAdvancedFilterFrom DateTime
Well Template Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no well template data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
WellTemplateAdvancedFilterTo DateTime
Well Template Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no well template data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
WellTemplateAdvancedFilterAreal ExtentFlag
Well Template Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
WellTemplateAdvancedFilterAreal ExtentType
Well Template Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
384 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
WellTemplateAdvancedFilterAreal ExtentDataType
Well Template Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
WellTemplateAdvancedFilter CustomMinX
Well Template Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
WellTemplateAdvancedFilter CustomMaxX
Well Template Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
WellTemplateAdvancedFilter CustomMinY
Well Template Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
WellTemplateAdvancedFilter CustomMaxY
Well Template Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
WellTemplateAdvancedFilter CustomMinLat
Well Template Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
WellTemplateAdvancedFilter CustomMaxLat
Well Template Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 385
OpenWorks Project Management Landmark
WellTemplateAdvancedFilter CustomMinLong
Well Template Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
WellTemplateAdvancedFilter CustomMaxLong
Well Template Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
WellTemplateAdvancedFilter TransferNullSpatialFlag
Well Template Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
WellTemplateFilterString Well Template Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the well template list.
WellTemplateMatchCaseFlag Well Template Data Options
Integer No 1
Legend 3: Match case during filtering and searching of well template list. (See “Legend 3” on page 394.)
WellTemplates Well Template Data Options
String List Yes Sorted "Suite_Name | Data_Source", comma separated, no spaces after commas or <All>
Suite1 | LGC,Suite2 | LGC or <All>
The well templates to transfer.
ListDataFlag Main Integer No 0
Legend 3: Listen to the list data selections and transfer that list data. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
386 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
ListOptionInterpreterTransferFlag List Interpreter Options
Integer No 0
Legend 3: Apply the interpreter filter. (See “Legend 3” on page 394.)
ListOptionInterpreterExcludes List Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas
ABC,LGC,GQS
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is not transferred.
ListOptionInterpreterRenames List Interpreter Options
String List Yes Sorted, comma separated, no spaces after commas, original (rename)
FAI(HEL),SPC(TAR)
If filtering by interpreter, all data that has a data source field with a value that matches one in this list, is renamed to whatever is in parenthesis when transferred.
ListOptionInterpreterTransferNull Flag
List Interpreter Options
Integer No 0
Legend 3: If filtering by interpreter, allow the transfer of data with NULL data source fields. (See “Legend 3” on page 394.)
ListAdvancedFilterNewDataFlag List Advanced Filter
Integer No 1
Legend 3: Allow the creation of new list data.(See “Legend 3” on page 394.)
ListAdvancedFilterUpdateDate TimeFlag
List Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on list data. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 387
OpenWorks Project Management Landmark
ListAdvancedFilterFromDateTime List Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no list data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
ListAdvancedFilterToDateTime List Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no list data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
ListAdvancedFilterArealExtent Flag
List Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
ListAdvancedFilterArealExtent Type
List Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
ListAdvancedFilterArealExtent DataType
List Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
ListAdvancedFilterCustomMinX List Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
388 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
ListAdvancedFilterCustomMaxX List Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
ListAdvancedFilterCustomMinY List Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
ListAdvancedFilterCustomMaxY List Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
ListAdvancedFilterCustomMinLat List Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
ListAdvancedFilterCustomMaxLat List Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
ListAdvancedFilterCustomMin Long
List Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
ListAdvancedFilterCustomMax Long
List Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
ListAdvancedFilterTransferNull SpatialFlag
List Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 389
OpenWorks Project Management Landmark
ListTypes List Data Options
String List Yes Comma separated, no spaces after commas or <All>
2D Seismic Line,Fault,Well or <All>
Legend 21: Which list data types to show in bottom list. (See “Legend 21” on page 402.)
ListFilterString List Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the list.
ListMatchCaseFlag List Data Options
Integer No 1
Legend 3: Match case during filtering and searching of list. (See “Legend 3” on page 394.)
Lists List Data Options
String List Yes Sorted "List_Type | List_Name | Data_Source", comma separated, no spaces after commas or <All>
Fault | FaultList1 | LGC,Seismic | SeismicList1 | LGC or <All>
The lists to transfer.
WellPlanningProjectDataFlag Main Integer No 0
Legend 3: Listen to the well planning project data selections and transfer that well planning project data. (See “Legend 3” on page 394.)
WellPlanningProjectAdvanced FilterNewDataFlag
Well Planning Project Advanced Filter
Integer No 1
Legend 3: Allow the creation of new well planning project data. (See “Legend 3” on page 394.)
WellPlanningProjectAdvanced FilterUpdateDateTimeFlag
Well Planning Project Advanced Filter
Integer No 0
Legend 3: Apply an update/create date filter on well planning project data. (See “Legend 3” on page 394.)
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
390 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
WellPlanningProjectAdvanced FilterFromDateTime
Well Planning Project Advanced Filter
String Yes HH:MN MM/DD/YYYY or <-Float Units> or <Now>
13:25 11/29/2000 or <-1.5 years> or <Now>
Legend 4: If filtering by update/create date, no well planning project data will be transferred whose date occurs before this value. A special value of <-Float Units> can be used to specify an offset from the ToDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
WellPlanningProjectAdvanced FilterToDateTime
Well Planning Project Advanced Filter
String Yes HH:MN MM/DD/YYYY or <+Float Units> or <Now>
13:25 11/29/2000 or <+1.5 years> or <Now>
Legend 4: If filtering by update/create date, no well planning project data will be transferred whose date occurs after this value. A special value of <+Float Units> can be used to specify an offset from the FromDateTime where Float is any floating-point value and Units is any unit in the legend. A special value of <Now> can be used to specify the date and time when the configuration file was opened. (See “Legend 4” on page 394.)
WellPlanningProjectAdvanced FilterArealExtentFlag
Well Planning Project Advanced Filter
Integer No 1
Legend 3: Apply an areal extent filter on well data. (See “Legend 3” on page 394.)
WellPlanningProjectAdvanced FilterArealExtentType
Well Planning Project Advanced Filter
Integer No 2
Legend 5: If filtering by areal extent, specifies the source of the extent filter. (See “Legend 5” on page 394.)
WellPlanningProjectAdvanced FilterArealExtentDataType
Well Planning Project Advanced Filter
Integer No 0
Legend 6: If filtering by areal extent, specifies whether to use x,y or lat,lon data for the extent filter. (See “Legend 6” on page 394.)
WellPlanningProjectAdvanced FilterCustomMinX
Well Planning Project Advanced Filter
Float Yes -34
If filtering by a custom x,y areal extent, specifies minimum X.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 391
OpenWorks Project Management Landmark
WellPlanningProjectAdvanced FilterCustomMaxX
Well Planning Project Advanced Filter
Float Yes 500
If filtering by a custom x,y areal extent, specifies maximum X.
WellPlanningProjectAdvanced FilterCustomMinY
Well Planning Project Advanced Filter
Float Yes -1000
If filtering by a custom x,y areal extent, specifies minimum Y.
WellPlanningProjectAdvanced FilterCustomMaxY
Well Planning Project Advanced Filter
Float Yes -50
If filtering by a custom x,y areal extent, specifies maximum Y.
WellPlanningProjectAdvanced FilterCustomMinLat
Well Planning Project Advanced Filter
Float Yes Between -90 and 90
-45
If filtering by a custom lat,lon areal extent, specifies minimum latitude.
WellPlanningProjectAdvanced FilterCustomMaxLat
Well Planning Project Advanced Filter
Float Yes Between -90 and 90
30
If filtering by a custom lat,lon areal extent, specifies maximum latitude.
WellPlanningProjectAdvanced FilterCustomMinLong
Well Planning Project Advanced Filter
Float Yes Between -180 and 180
-160
If filtering by a custom lat,lon areal extent, specifies minimum longitude.
WellPlanningProjectAdvanced FilterCustomMaxLong
Well Planning Project Advanced Filter
Float Yes Between -180 and 180
-10
If filtering by a custom lat,lon areal extent, specifies maximum longitude.
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
392 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
WellPlanningProjectAdvanced FilterTransferNullSpatialFlag
Well Planning Project Advanced Filter
Integer No 0
Legend 3: Allow data with NULL spatial coordinates to pass through areal extent filter. (See “Legend 3” on page 394.)
WellPlanningProjectFilterString Well Planning Project Data Options
String Yes W*
Pseudo regular expression used for searching and filtering the well planning project list.
WellPlanningProjectMatchCase Flag
Well Planning Project Data Options
Integer No 1
Legend 3: Match case during filtering and searching of well planning project list. (See “Legend 3” on page 394.)
WellPlanningProjects Well Planning Project Data Options
String List Yes Sorted "Well_Planning_Project_Name", comma separated, no spaces after commas or <All>
WPP1,WPP2 or <All>
The well planning projects to transfer.
Legend for Configuration File Format Table
Legend No. Value Meaning
Legend 1 0 Append
1 Overwrite
Legend 2 0x01 Errors
0x02 Warnings
0x04 Information
PDT Configuration File Format
Parameter Name DialogValue
Data TypeValue
OptionalValue
FormatExample Value
R2003.12.0 Project Data Transfer: PDT Configuration File Format 393
OpenWorks Project Management Landmark
Legend 3 0 No (False)
1 Yes (True)
Legend 4 years years
months months
weeks weeks
days days
hours hours
minutes minutes
Legend 5 0 Target project extents
1 Source project extents
2 Custom extents
Legend 6 0 “X,Y”
1 “Lat,Lon”
Legend 7 0 Common Well Name
1 Operator | Well Name | Well Number
2 Operator | Well Number
3 UWI
4 UWI | Well ID
5 Well Name
6 Well Name | Well Number
7 Well Number
Legend 8 Bit Record Bit Record
Blow Out Blow Out
Computed Lithology Header Computed Lithology Header
Computed Lithology Curve Computed Lithology Curve
Legend for Configuration File Format Table
Legend No. Value Meaning
394 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
Carter Loc Carter Loc
Casing Casing
Congressional Location Congressional Location
Cost Cost
Daily Activity Daily Activity
Well Work Over Well Work Over
Daily Drilling Summary Daily Drilling Summary
Dipmeter Dipmeter
Directional Survey Directional Survey
Dls Loc Dls Loc
Drilling Log Drilling Log
Drilling Objective Drilling Objective
DST Job Header DST Job Header
RFT Run Header RFT Run Header
DST/RFT General DST/RFT General
DST/RFT Cushion DST/RFT Cushion
DST/RFT Fluid DST/RFT Fluid
DST/RFT Material Surface DST/RFT Material Surface
DST/RFT Pressure DST/RFT Pressure
DST/RFT Summary DST/RFT Summary
Elevation Information Elevation Information
Fps Loc Fps Loc
Geodetic Loc Geodetic Loc
Interpreted Drilling Show Interpreted Drilling Show
Liner Liner
Logging Job Logging Job
Logging Tool String Descent Logging Tool String Descent
Logging Tool Config Logging Tool Config
Logging Tool Equipment Logging Tool Equipment
Logging Tool Parm Logging Tool Parm
Legend for Configuration File Format Table
Legend No. Value Meaning
R2003.12.0 Project Data Transfer: PDT Configuration File Format 395
OpenWorks Project Management Landmark
Logging Tool Pass Logging Tool Pass
Logging Mud Test Logging Mud Test
Logging Tool Calib Logging Tool Calib
Logging Sensor Parm Logging Sensor Parm
Log Sample Framework Log Sample Framework
Log Curve Log Curve
Log Curve Qualifier Log Curve Qualifier
Lost Circulation Lost Circulation
Mudlog Header Mudlog Header
Mudlog Description Mudlog Description
Mud Report Mud Report
MWD Run MWD Run
Narrative Location Narrative Location
Ne Loc Ne Loc
North Sea Loc North Sea Loc
Nts Loc Nts Loc
OCS Location OCS Location
Ohio Loc Ohio Loc
Packer Packer
Paleo Paleo
Paleo Sample Analysis Paleo Sample Analysis
Paleo Sample Analysis Detail Paleo Sample Analysis Detail
Pick Pick
Plugging Plugging
Pos Log Pos Log
Rig Information Rig Information
Drilling Pump Drilling Pump
Side Track (legacy) Side Track (legacy)
Squeeze Squeeze
Surface Key Well Surface Key Well
Legend for Configuration File Format Table
Legend No. Value Meaning
396 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
Survey History Survey History
TD Information TD Information
Texas Location Texas Location
Time Depth Table Time Depth Table
Synth Seis Synth Seis
Preferred Synthetic Preferred Synthetic
Preferred Time Depth Curve Preferred Time Depth Curve
Tubing Tubing
Tubing Equipment Tubing Equipment
Well Afe Well Afe
Well Completion Well Completion
Well Core Well Core
Well Core Analysis Well Core Analysis
Well Core Analysis Method Well Core Analysis Method
Well Core Analysis Remark Well Core Analysis Remark
Well Core Description Well Core Description
Well Core Formation Well Core Formation
Well Core Remark Well Core Remark
Well Core Sample Analysis Well Core Sample Analysis
Core Property Analysis Core Property Analysis
Core Property Analysis Detail Core Property Analysis Detail
Well Core Sample Description Well Core Sample Description
Well Core Sample Remark Well Core Sample Remark
Well Core Shift Well Core Shift
Well Date Well Date
Well Drilling Summary Well Drilling Summary
Well Header Well Header
Well Fault Well Fault
Key Well Key Well
Strat Unit Summary Strat Unit Summary
Legend for Configuration File Format Table
Legend No. Value Meaning
R2003.12.0 Project Data Transfer: PDT Configuration File Format 397
OpenWorks Project Management Landmark
Well Fluid Contact Well Fluid Contact
Well Image Well Image
Well Interest Well Interest
Well Interest Scale Well Interest Scale
Well Interval Well Interval
Well Interval Value Well Interval Value
Alternate Well Location Alternate Well Location
Well Mineral Analysis Well Mineral Analysis
Well Mineral Percentage Well Mineral Percentage
Well Name History Well Name History
Well Note Pad Well Note Pad
Well Operator Well Operator
Well Perforation Well Perforation
Well Producing Zone Well Producing Zone
Well Remark Well Remark
Well Sieve Analysis Well Sieve Analysis
Well Sieve Screen Well Sieve Screen
Well Status History Well Status History
Well Study Well Study
Well Survey Well Survey
Well Test Well Test
Well Pressure Well Pressure
Well Pressure A O F Well Pressure A O F
Well Pressure AOF 4 Pt Well Pressure AOF 4 Pt
Well Pressure B H Well Pressure B H
Well Test Analysis Well Test Analysis
Well Test Recorder Well Test Recorder
Well Test Computed Analysis Well Test Computed Analysis
Well Test Recovery Well Test Recovery
Well Test Contaminant Well Test Contaminant
Legend for Configuration File Format Table
Legend No. Value Meaning
398 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
Well Test Cushion Well Test Cushion
Well Test Equipment Well Test Equipment
Well Test Period Well Test Period
Well Test Flow Well Test Flow
Well Test Flow Measurement Well Test Flow Measurement
Well Test Mud Well Test Mud
Well Test Press Well Test Press
Well Test Pressure Meas Well Test Pressure Meas
Well Test Remark Well Test Remark
Well Test Shutoff Well Test Shutoff
Well Treatment Well Treatment
Alternate Well Identifier Alternate Well Identifier
Zone (Strat Unit) Attribute Zone (Strat Unit) Attribute
Legend 9 Production Flow Measurement (legacy)
Production Flow Measurement (legacy)
Production Gas Analysis Production Gas Analysis
Production Gas Analysis Detail Production Gas Analysis Detail
Production Oil Analysis Production Oil Analysis
Production Oil Analysis Detail Production Oil Analysis Detail
Production Oil Viscosity Production Oil Viscosity
Production Volume Disposition (legacy)
Production Volume Disposition (legacy)
Production Volume Record (legacy)
Production Volume Record (legacy)
Production Water Analysis Production Water Analysis
Production Water Analysis Detail
Production Water Analysis Detail
Legend for Configuration File Format Table
Legend No. Value Meaning
R2003.12.0 Project Data Transfer: PDT Configuration File Format 399
OpenWorks Project Management Landmark
Legend 10 years years
months months
weeks weeks
days days
Legend 11 Prod Daily Injection Prod Daily Injection
Prod Daily Production Prod Daily Production
Prod Economic Prod Economic
Prod Economic Detail Prod Economic Detail
Prod Economic Monthly Prod Economic Monthly
Prod Economic One Line Prod Economic One Line
Prod Economic Owner Prod Economic Owner
Prod Economic P/Z Forecast Prod Economic P/Z Forecast
Prod Economic Summary Prod Economic Summary
Prod Facility Group Prod Facility Group
Prod Group Allocation Prod Group Allocation
Prod Monthly Injection Prod Monthly Injection
Prod Monthly Production Prod Monthly Production
Prod Annotation Prod Annotation
Pdm Production Hdr Pdm Production Hdr
Prod Cumulatives Prod Cumulatives
Prod Property Summary Prod Property Summary
Prod RMS Book Memo Prod RMS Book Memo
Prod RMS Book Delta Prod RMS Book Delta
Prod RMS Book Prod Prod RMS Book Prod
Prod RMS NonBook Memo Prod RMS NonBook Memo
Prod RMS Reserves Prod RMS Reserves
Legend for Configuration File Format Table
Legend No. Value Meaning
400 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
Legend 12 Lease Lease
Lease Commitment Lease Commitment
Lease Field Prospect Lease Field Prospect
Lease Interest Scale Lease Interest Scale
Lease Narrative Lease Narrative
Lease Tract Lease Tract
Lessee Lessee
Lessor Lessor
Licensing Round Licensing Round
Tract Boundary Tract Boundary
Legend 13 Field Boundary Field Boundary
Field Prospect Field Prospect
Legend 14 Basin Basin
Basin Boundary Basin Boundary
Country Basin Country Basin
Legend 15 Binset Grid2 D Shpt Trace Binset Grid2 D Shpt Trace
Seis Geom Set2 D Line Seis Geom Set2 D Line
Seis Geom Set2 D Survey Seis Geom Set2 D Survey
Legend 16 Binset Grid3 D Grid Binset Grid3 D Grid
Seis Geom Set3 D Survey Seis Geom Set3 D Survey
Legend 17 0 Time
1 Depth
Legend for Configuration File Format Table
Legend No. Value Meaning
R2003.12.0 Project Data Transfer: PDT Configuration File Format 401
OpenWorks Project Management Landmark
Legend 18 Fault Fault
Fault Display Fault Display
Fault Plane Trimesh Fault Plane Trimesh
Fault Segment Fault Segment
Legend 19 0 Add
1 Remove
Legend 20 Point Set Point Set
Grid Grid
Contour Contour
Mapping Polygon Mapping Polygon
Fault Center Line Fault Center Line
Surface Profile Surface Profile
Fault Profile Fault Profile
Legend 21 2D Seismic Line 2D Seismic Line
Fault Fault
Field Field
Lease Lease
Well Well
Legend 22 Line of Section Line of Section
Well Projections Well Projections
Legend for Configuration File Format Table
Legend No. Value Meaning
402 Project Data Transfer: PDT Configuration File Format R2003.12.0
Landmark OpenWorks Project Management
Project Server for Workgroup Users
Overview
Normally, you only have access to the projects on your own workstation or on the installed server for your workstation (assuming that your workstation is installed in a client-server configuration). If Landmark’s Workgroup feature is installed on your system, however, you can access projects remotely over the network.
The Workgroup feature adds an extra menu selection called Project Server to the OpenWorks Command Menu, as shown above. For users of seismic projects, this menu option lets you access projects stored on a controlled list of remote servers located elsewhere on the network (as defined in the serverlist file located in your home directory or in the directory $OWHOME/WorkGroup/bin).
In addition, if your system is configured to run certain applications remotely, the fact that you access a remote project causes the configured application to run on the remote server where the project is located, instead of running on your local workstation.
This feature improves system performance for data-intensive applications such as SeisWorks, since it allows the application to run on the same node where the data is located, instead of trying to access the data remotely over the network. Even though the application runs remotely, it still displays on your workstation.
Project Server is not included in OpenWorks on Windows workstations, but is included in some installations of OpenWorks on UNIX systems as an add-on.
What’s in this Chapter
This chapter describes the OpenWorks Project Server utility and explains how to access projects remotely over the network.
R2003.12.0 Project Server for Workgroup Users 403
OpenWorks Project Management Landmark
Accessing Remote Projects
If your workstation has the Workgroup feature installed, use the following steps to access remote projects:
1. Select Project > Project Server, then select either:
• Seismic Project to select a project to be used with seismic applications (such as SeisWorks or SeisCube). Go to step 2.
• Geologic Project to select a project to be used with geologic applications (such as StratWorks or GeoDataWorks). Go to step 5.
2. A list of your local projects appears, as shown in the following illustration. If no local projects are found, the system searches each available remote server until it finds a list of projects to display (see note on “Location of Seismic Projects” on page 404). If the listed projects are on a remote server, the name of the remote server appears above the list.
3. To display a list of projects from a different server, click on the List Servers button, then select the server from the list.
4. Once you see the desired list of projects from the desired server, select the project you want to use with the application and click the OK button. You have finished this procedure.
5. The Geologic Project option allows you to select only an application server. When you select the option, a server selection dialog box appears.
Location of Seismic Projects
The list of seismic projects for a given workstation is in a file called plist.dat located in the $OW_PMPATH directory (usually $OWHOME/conf). This file may be stored locally or on one of the remote servers.
The list of geologic projects is specified by OWSYSSID. If the local workstation is a database client, the project location is referenced by the user’s local settings for these variables. If the workstation is not a client, or if no geologic projects are found locally, the servers listed in the serverlist file are queried for a list of geologic projects. The list of projects displayed to the user come from the first server with such a list available.
404 Project Server for Workgroup Users: Accessing Remote Projects R2003.12.0
Landmark OpenWorks Project Management
Click on the server you wish to use, then select OK. After selecting an application server, you can choose a new project in the normal way (e.g., with Project Change).
Geologic project selection does not require using the WorkGroup Project Server application. To select a geologic project for use with applications such as StratWorks or Geodata Works, you can use the Project Change tool (see “Project Change” on page 199) or use the Project Status Tool (see “Project Status Tool” on page 217). The Project Status Tool handles changing OWSYSSIDs and selecting the identical project name on the new OWSYSSID.
R2003.12.0 Project Server for Workgroup Users: Accessing Remote Projects 405
OpenWorks Project Management Landmark
406 Project Server for Workgroup Users: Accessing Remote Projects R2003.12.0
Landmark OpenWorks Project Management
Appendix: Limited Interpreters Tables
When you create a project, you are the only person who can access it. You can grant other users access to your project and you can control their level of access using the steps described in the section titled “Managing Project Access” on page 191.
The table below shows the available levels of project access—Browse, Limited Interpret, Interpret, and Manage—and lists the actions each type of user can perform
Limited interpreters typically are given the power to create or edit interpretive data but can only view reference data. The database table controlling limited interpreter access is the OW_ADMIN_UTILS.L_INTERP_MASTER table.
When you create or update a project, the system assigns limited interpreter access to all the tables specified in the OW_ADMIN_UTILS.L_INTERP_MASTER table. The contents of this table can be changed; however, changes that you make to this list
Access Permissions
Browse (B) Able to view project data, but cannot modify it.
Limited Interpret (L) Able to view project data, and can modify interpretive data (e.g., faults and picks), but cannot modify reference data (e.g., well master data).
Interpret (I) Able to view, create, and modify project data created.
Manage (M) Able to view and modify all project data regardless of who created it, and can grant other users’ access. User with manage access can also delete the project. May per-form project management functions only if the OW_ADMINISTRATOR role is also granted.
R2003.12.0 407
OpenWorks Project Management Landmark
will not affect the current project; they take effect the next time you create, restore, or upgrade a project.
If you need to change limited interpreter access for the current OpenWorks project you must change the contents of the OW_ADMIN_UTILS.L_INTERP_MASTER table and then backup and restore the current project. The restore program will read the OW_ADMIN_UTILS.L_INTERP_MASTER table and the restored project will incorporate the new limited interpreter access.
To check which tables limited interpreters can write to, enter the following in a UNIX or Command Prompt window:
sqlplus <project>/<passwd>select table_name from user_tab_privs wheregrantee = 'L_INTERP_<PROJECT>' and privilege = 'INSERT';
Warning: Change the limited interpreters table file with caution.
Changing the limited interpreters table file is a system administration function. We recommend that only system administrators change the file, and that they do so with extreme caution.
408 : R2003.12.0
Landmark OpenWorks Project Management
Index
AadmprjSee command line utilities
Advanced license featuresProject Data Transfer 234
advanced modedefining tablespace when creating projects
214defining tablespace when restoring projects
189
Advanced Project Managementand Project Data Transfer 234
Albers Equal-Area Conic projection 105
areal extentdecimal degrees 212defining during project creation 212definition 212literal degrees 212modifying 176
AUTOEXTEND 202, 213
Azimuthal Equal Area projection 105
Azimuthal Equidistant projection 106
B
backing up a project 180-183
basin datafiltering in PDT 259transferring in PDT 259-261
batch jobs (PDT)running 327setting up 325-326
R2003.12.0
Bonne projection 106
Bursa-Wolf shift method 94
C
Canadian Metric measurement systemdefinition 17
Cartographic Reference System (CRS) 38-47changing an existing CRS 82-83creating a new CRS 52-80default project CRS 48, 207default project CRS units 48definition of 38, 39deleting a 84requirements for 40-47
datum shift 43geodetic datum 43parameters
origin 45adjusted 46false easting 46false northing 46intrinsic 45natural 45
parallels/meridians 44-45projection parameters 44-46projection type 40-42spheroid 42units of measure 43
selecting a CRSduring project creation 207for project map displays 210
testing conversion of 85See also Map Projection Editor
cartographic reference systemsand Project Data Transfer 233
Index 409
OpenWorks Project Management Landmark
central meridian 45, 97
changingcurrent OpenWorks project
in Project Status Tool 220current wells 224current working project 199-200interpreter
in Interpreters utility 34in Project Status Tool 222
measurement system 221Oracle instance (OWSYSSID) in Project
Status Tool 219well format 230well list 223well list sort preference 225
checking project tablespace and user access 196
Clarkeellipsoid 42
clearing Project Data Transfer 304
command line utilitiesadmprj to start Project Administration 175crtprj to start Project CreateextendToOW6Rev0 163owbackup to back up projectsowbackup-all to back up projectsowdelete to delete projectsowrestore to restore projects
configuration files for PDT batch jobscreating 325-326editing 326using 327
convertingRelease 1998.x projects to Release 2003
159-165
creating a project 205-216
CRSSee Cartographic Reference System
crtprjSee command line utilities
current OpenWorks projectalso called current working project 4, 5, 199,
200, 206
D
data retrieval time, reducing (Project Tune) 197
datum 39, 43selection of 67
datum shift methods in Map Projection Editor 93-95
predefined methods 95-96
default display parameters 210-211defining during Project Create 205differences between project CRS and
display CRS 210
defaultsfor project CRS 207for project CRS’s 48for project display parameters 48for project surface units of measure 48, 207
definitionof areal extent 212of map projection 210of map scale 210of project 5of project size 213of reference elevation 211
degrees of arc 43
degrees of latitude/longitude, entering 90
deleting a project 178
410 Index R2003.12.0
Landmark OpenWorks Project Management
E
elevation for project referencemodifying 177setting 211
ellipsoid 39, 42Clarke 42matching datum 57, 67WGS 72 42
enhancing performance 197
environment variablesPDT_STASH_SIZE 330
Equal-Area Cylindrical projection 107
Equidistant Conic - 1 parallel projection 108
Equidistant Conic - 2 parallel projection 108
Equidistant Cylindrical projection 108
exitingProject Data Transfer 238
exporting vector datasee vector data conversion utilities 167
F
facility datafiltering in PDT 262transferring in PDT 262-265
false easting 46, 97
false northing 46, 97
fault data (SeisWorks faults)filtering in PDT 273transferring in PDT 273-277
field data
filtering in PDT 255transferring in PDT 255-258
G
General Units Converterand project units 18
Geographic (Geodetic) CRS 47, 53, 103defining 53-63, 103saving 80-81
Geographic Latitude/Longitude projection 109
geoid 42
Gnomonic projection 110
grads of arc 43
H
Hotine Oblique Mercator - 1 Point 110
Hotine Oblique Mercator - 2 Points 111
Hotine Oblique Mercator - Azimuth Skew 111
Hungarian EOV projection 112
I
importing vector datasee vector data conversion utilities 167
IMW Polyconic projection 112
instance, setting 207
interpretation datafiltering in PDT 284transferring in PDT 284-287
R2003.12.0 Index 411
OpenWorks Project Management Landmark
interpreteradding 31changing in Project Status Tool 222deleting 33modifying 32setting
in Interpreters utility 34viewing project interpreters 30viewing user-created interpreters 30
interpretersexcluding some interpreters’ data in PDT
249, 275, 282, 306-308renaming for target project 249, 275, 282,
306-308
Interpreters utility 25-28definition of 26Delete option 33Exit option 28File menu 29overview 25project, selecting 27starting
UNIX 27Windows 27
View menu 29window layout 28
intrinsic origin 45
L
Lambert Conic Conformal - 1 parallel 112
Lambert Conic Conformal - 2 parallel 113
Lambert Conic Conformal projection 41, 42, 45, 100, 129
Large Object formsee vector data conversion utilities 167
latitude 71, 85, 90, 103definition of 44
how to enter 71, 90
latitude and longitudesetting minimum and maximum for project
212See also areal extent
launchingProject Data Transfer 237
lease datafiltering in PDT 251transferring in PDT 251-254
limited interpretersaccess to project 191, 407
line of section datafiltering in PDT 288transferring in PDT 288-292
linear units 43
list datafiltering in PDT 296transferring in PDT 296-298
longitude 71, 85, 90, 103definition of 44how to enter 71, 90
M
Manage accessand OW_ADMINISTRATOR role 191
map projectiondefinition 210modifying 176setting in Project Create 210
Map Projection Editor 37-149Azimuthal Equal Area projection 105Azimuthal Equidistant projection 106Bonne projection 106
412 Index R2003.12.0
Landmark OpenWorks Project Management
Bursa-Wolf shift method 94Cassini-Soldner projection 107changing an existing CRS 82-83Close function 80, 83, 91Convert button 91creating a new CRS 52-80datum shift methods 93-95default project CRS 48Delete function 84Equal-Area Cylindrical projection 107Equidistant Conic - 1 parallel projection 108Equidistant Conic - 2 parallel projection 108Equidistant Cylindrical projection 108exiting Map Projection Editor 92File menu 52-53, 64, 74, 80, 83-84Geographic (Geodetic) CRS 47, 53
creating new datum shifts 72-79defining 53-63saving 80-81
Geographic Latitude/Longitude projection 109
glossary of terms 146-149Gnomonic projection 110Hotine Oblique Mercator - 1 Point 110Hotine Oblique Mercator - 2 Points 111Hotine Oblique Mercator - Azimuth Skew
111Hungarian EOV projection 112IMW Polyconic projection 112Lambert Conic Conformal - 1 parallel 112Lambert Conic Conformal - 2 parallel 113map projection parameters 71menus for 51Mercator projection 113Miller Cylindrical projection 114Mollweide projection 115Molodensky shift method 93NADCOM data files 96NADCON shift method 94NATRAN version 2 shift method 95New function 53, 64New Zealand Map Grid projection 115Open function 74, 83Orthographic projection 115overview 38-47
Polar Azimuthal Equal Area projection 116Polar Azimuthal Equidistant projection 116Polar Stereographic projection 117Polyconic projection 117predefined datum shifts 95-96Projection CRS
defining 64-71saving 80-81
Robinson projection 118Save As function 80Save function 83Self-Reference (Stand-Alone) projection
118Sinusoidal projection 118source coordinate system 87source coordinates 91spheroids supported 123-125starting
UNIX 49Windows 49
State Plane projection 119State Plane System
list of zones 129-134table of parameters 135See also State Plane System
Stereographic 70 projection 120Stereographic projection 119Stereographic-European projection 119target coordinate system 88target coordinates 91Test Conversion example 139Test Conversion window 87Transform menu 87Transverse Mercator projection 97, 100,
120, 129two basic types of cartographic reference
systems 40units
angular 43supported 128
definition of CRS units 43linear 43
supported 126role in specification 39
Universal Transverse Mercator System
R2003.12.0 Index 413
OpenWorks Project Management Landmark
(UTM) 97, 121longitude zones table 136-138
Van Der Grinten I projection 121zones
selection of 66, 70State Plane 100Universal Transverse Mercator 97UTM longitude zones table 136-138
Map Projections—A Working Manual 38, 44, 97, 99, 129
map scaledefinition 210modifying 177setting in Project Create 210
Measurement System Manager 151-158deleting an unused measurement system 158exiting 152launching 152procedure to create a new measurement
system 153, 154-157requirements before creating a new
measurement system 153starting
UNIX 152Windows 152
window layout 152
measurement systemsavailable in OpenWorks 16Canadian Metric 17definition 16, 18project
General Units Converter 18Special Units Editor 18
projects 16, 18-21session 19-21
changing in Project Status Tool 221set by applications 16, 21setting for projects 205, 209SPE Preferred Metric 17
compared to Metric 17surface distance units
how OpenWorks determines and stores 16, 22
surface distance units handling 22-23U.S. Oil Field 17
compared to English 17U.S. Oil Field-Metric Depth 17
Mercator projection 113
meridiancentral 45definition of 44
Military UTM 97
Miller Cylindrical projection 41, 114
minutes of arc 43
modifying a project 175-178
Mollweide projection 115
Molodensky shift method 93
N
NADCOM data files 96
NADCON shift method 94
National Oceanic and Atmospheric Administration (NOAA) 101
NATRAN version 2 shift method 95
natural origin 45
networks, accessing projects 5
New Zealand Map Grid projection 115
North American Datum1927 100, 1291983 100, 129
414 Index R2003.12.0
Landmark OpenWorks Project Management
novice modedefining tablespace when creating projects
214defining tablespace when restoring projects
189
O
Oblique Mercator projection 100, 129
OpenWorks Security Model 7-15OW_ADMINISTRATOR role 8-14
ORACLE instancestransferring data across instances 234
ORACLE project backup 180-183
ORACLE tablespace 213
orauser utilityand OW_ADMINISTRATOR role 14
origin 45, 97adjusted 46intrinsic 45natural 45
Orthographic projection 41, 115
OW_ADMINISTRATOR role 8-14and Manage access 191
owbackupSee command line utilities
owbackup-allSee command line utilities
owdeleteSee command line utilities
owrestoreSee command line utilities
P
parallelsdefinition of 44standard parallels 44, 105
PDT_STASH_SIZE variable 330
Pointing Dispatcherusing in Project Data Transfer 240
Polar Azimuthal Equal Area projection 116
Polar Azimuthal Equidistant projection 116
Polar Stereographic projection 97, 117
Polyconic projection 100, 117
predefined datum shifts 95-96
project 1-23, 173-197, 199-200, 201-215accessing over a network 5accessing remote project 403areal extent 205
modifying 176setting 212
backing up 180-183changing current OpenWorks project
in Project Status Tool 220changing current working project 199-200changing interpreter 222changing measurement system 221changing Oracle instance (OWSYSSID) in
Project Status Tool 219changing time depth conversion preferences
226-228changing well format 230changing well list sort preference 225changing well lists 223changing well order in well list 229changing wells 224checking project tablespace 196checking user access 196converting from Release 1998.x to Release
R2003.12.0 Index 415
OpenWorks Project Management Landmark
2003 159-165creating 205-216
from Project Administration window 175data 6default display parameters 205
modifying 176definition 5deleting 178description 205
modifying 176determining size 213enhancing performance 197exiting Project Status Tool 218instance 205, 207managing user access 191map projection
modifying 176setting 210
map scalemodifying 177setting 210
measurement systems 16, 18-21selecting 205, 209
modifying 175-178name 205overview 5-6reducing data retrieval time 197reference elevation
modifying 177setting 211
remote projects 403-405restoring 187-189selecting a cartographic reference system
205, 207session measurement system 16, 19-21setting
in Interpreters utility 27setting as current working project in Project
Create 206size
determining 213minimum project size 213modifying 177
sizes 214tablespace 205, 213
tuning (Project Tune) 197type 205
Project Administration 173-197exiting 175starting 174
UNIX 174Windows 174
starting from xterm 175
Project Changestarting
UNIX 200Windows 200
Project Create 201-215default project CRS 207exiting 204setting areal extent 212setting latitude and longitude covered by a
project 212starting 204
from OpenWorks applications 204UNIX OpenWorks Command Menu 204Windows Start Menu 204
starting on command line
Project Data Transferaccess levels required 235Advanced license features 234and Advanced Project Management 234and cartographic reference systems 233and units of measure 233batch jobs
running 327setting up 325-326
choosing source project 239-240choosing target project 239-240clearing all selections 304configuration files
creating 325-326editing 326formats 331-402using 327
data types for transfer 235
416 Index R2003.12.0
Landmark OpenWorks Project Management
excluding some interpreters’ data 249, 275, 282, 306-308
exiting 238filtering
basin data 259facility data 262fault data 273field data 255interpretation data 284lease data 251line of section data 288list data 296queries 278seismic 2D and 3D data 266, 270strat column data 280well data 242well planning project data 299well template data 293
launching 237overview 233-235renaming interpreters for target project 249,
275, 282, 306-308running the job 323-324search/filter techniques 303selecting data for transfer 241-304selecting techniques 302setting up report 321-322stash size 330using Pointing Dispatcher 240work flow 236
project measurement systemsurface distance units converted to 22surface distance units not converted to 22
Project Query 196
Project Status Tool 217-231session files 231starting
UNIX 218Windows 218
Project Tune 197statistics and SeisWorks fault retrieval
performance 197
Projection CRSdefining 64-71saving 80-81
projection type 39Albers Equal-Area Conic 105Azimuthal Equal Area projection 105Bonne 106Cassini-Soldner 107complete list of supported types 104definition of 40Equal-Area Cylindrical 107Equidistant Conic - 1 parallel 108Equidistant Conic - 2 parallel 108Equidistant Cylindrical 108Geographic Latitude/Longitude 109Geographic or Geodetic 103Gnomonic 110Hotine Oblique Mercator - 1 Point 110Hotine Oblique Mercator - 2 Points 111Hotine Oblique Mercator - Azimuth Skew
111Hungarian EOV 112IMW Polyconic 112Lambert Conic Conformal 41, 42, 100, 129Lambert Conic Conformal - 1 parallel 112Lambert Conic Conformal - 2 parallel 113Mercator 113Miller Cylindrical 41, 114Mollweide 115New Zealand Map Grid 115Oblique Mercator 100, 129Orthographic 41, 115Polar Azimuthal Equal Area 116Polar Azimuthal Equidistant 116Polar Stereographic 97, 117Polyconic 100, 117Robinson 118selecting from a list 53, 65Self-Reference (Stand-Alone) 102, 118Sinusoidal 118State Plane 97, 100-101, 119Stereographic 119
R2003.12.0 Index 417
OpenWorks Project Management Landmark
Stereographic 70 120Stereographic-European 119Transverse Mercator 97, 100, 120, 129Universal Transverse Mercator System
(UTM) 97, 121longitude zones table 136-138
unknown/unsupported typesSee Self Reference (Stand-Alone) CRS
102Van Der Grinten I 121See also Map Projection Editor
projectschoosing source project in PDT 239-240choosing target project in PDT 239-240
Q
queriesfiltering in PDT 278transferring in PDT 278, 278-279
R
radians 43
reducing data retrieval time (Project Tune) 197
reference elevationmodifying 177setting for project 211
remote projects 403-405
RESTORE_PRJ_USERSvariable to retain user access when restoring
projects 186
restoring projects 186-189RESTORE_PRJ_USERS
variable to retain user access when restoring projects 186
Robinson projection 118
S
Search/Filter String featureProject Data Transfer
Search/Filter String feature 303, 304
search/filter techniquesin Project Data Transfer 303
seismic 2D and 3D datafiltering in PDT 266, 270transferring in PDT 266-269, 270-272
Seismic Project Managercontains utilities to manage seismic projects
4
seismic projectsutilities moved from OpenWorks Command
Menu to Seismic Project Manager 4
SeisWorks fault datatransferring in PDT 273-277
selecting techniquesin Project Data Transfer 302
Self-Reference (Stand-Alone) projection 118
session files 231
session measurement systemchanging 20changing in Project Status Tool 221compared to project measurement system
16, 19definition 16, 19overriding 21setting using Project Status Tool 19
shift methods in Map Projection Editor 93-95predefined datum shifts 95-96
Sinusoidal projection 118
418 Index R2003.12.0
Landmark OpenWorks Project Management
SPE Preferred Metric measurement system 17compared to Metric 17
Special Units Editorand project units 18
spheroid 42
stand-alone CRS 102
standard parallel 100, 105
State Plane System 66, 70, 97, 100-101Index of Coordinates 101list of zones 129-134parameters 135State Plane projection 119
Stereographic 70 projection 120
Stereographic projection 119
Stereographic-European projection 119
strat column datafiltering in PDT 280transferring in PDT 280-283
surface distance units 22-23determined by project CRS surface measure
units 48distances converted to project measurement
system 22distances not converted to project
measurement system 22how OpenWorks determines and stores 16,
22
T
tablespace, setting 205, 213
time depth conversion preferenceschanging
in Project Status Tool 226-228
transfer reportsetting up in PDT 321-322viewing in PDT 323-324
Transverse Mercator projection 97, 100, 120, 129
tuning OpenWorks projects 197
U
U.S. Geological Survey 38
U.S. Oil Field measurement system 17compared to English 17
U.S. Oil Field-Metric Depth measurement system 17
U.S. State Plane SystemSee State Plane System
units of measureand Project Data Transfer 233
Universal Transverse Mercator System (UTM) 97, 121
longitude zones table 136-138
utilitiesfor managing OpenWorks projects 3for managing seismic projects 4
V
Van Der Grinten I projection 121
vector data conversion utilities 167-171Large Object form 167procedure 169-170usage 168
R2003.12.0 Index 419
OpenWorks Project Management Landmark
W
well datafiltering in PDT 242transferring in PDT 242-250
well list, changing 223
well planning project datafiltering in PDT 299transferring in PDT 299-301
well template datafiltering in PDT 293transferring in PDT 293-295
wells, changing current 224
WGS 72 ellipsoid 42
work flow forProject Data Transfer 236
Workgroup 403-405access to projects 403
working projectdefined as current OpenWorks project 4, 5,
199, 200, 206
420 Index R2003.12.0