TIBCO OpenSpirit ArcGIS Extension Release Notes

Transcription

1 TIBCO OpenSpirit ArcGIS Extension Release Notes Software Release September 2012

2 ii Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, The Power of Now, TIBCO OpenSpirit Extension for ArcGIS are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

3 iii Contents Contents... iii Preface... iv Typographical Conventions...v Connecting with TIBCO Resources... vii How to Join TIBCOmmunity... vii How to Access All TIBCO Documentation... vii How to Contact TIBCO Support... vii Release Notes...1 New Features...2 Release Release Release Changes in Functionality...3 Release Release Release Deprecated and Removed Features...4 Release Release Release Migration and Compatibility...5 Release Release Release Closed Issues...7 Known Issues...8

4 iv Preface The TIBCO OpenSpirit Extension for ArcGIS is a spatial selection tool to view spatial data accessible via OpenSpirit and simultaneously integrate/interact with multiple OpenSpirit-enabled applications. The TIBCO OpenSpirit Extension for ArcGIS enables synchronization between your GIS and OpenSpirit-enabled applications and data stores. The TIBCO OpenSpirit Extension for ArcGIS is designated with U.S. Department of Commerce Export Control Classification Number EAR99.

5 v Typographical Conventions The following typographical conventions are used in this manual. Table 1 General Typographical Conventions Convention Use TIBCO_HOME ENV_HOME OSP_ HOME code font bold code font Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The default value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco. Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. An environment home directory is referenced in documentation as ENV_HOME. The default value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco. TIBCO < ProductName > installs into a directory referenced in documentation as OSP_HOME. The default value of OSP_HOME depends on the operating system. For example on Windows systems, the default value is C:\Progam Files\OpenSpirit. Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use MyCommand to start the foo process. Bold code font is used in the following ways: In procedures, to indicate what a user types. For example: Type admin. In large code samples, to indicate the parts of the sample that are of particular interest. In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable disable]

6 vi italic font Key combinations Italic font is used in the following ways: To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts. To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal. To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C. Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q. The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances. The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result. The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

7 vii Connecting with TIBCO Resources How to Join TIBCOmmunity TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to How to Access All TIBCO Documentation After you join TIBCOmmunity, you can access the documentation for all supported product versions here: How to Contact TIBCO Support For comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows. For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site: If you already have a valid maintenance or support contract, visit this site: Entry to this site requires a user name and password. If you do not have a user name, you can request one.

8

9 Release Notes 1 Release Notes Check the TIBCO Product Support web site at for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site. Topics New Features Changes in Functionality Deprecated and Removed Features Migration and Compatibility Closed Issues Known Issues

10 2 Release Notes New Features This section lists features added since the last major release of this product. Release There are no new features in this release. This release adds compatibility with ArcGIS Desktop version Release The following are new features in Release Added capability to send a map event image to other OpenSpirit enabled applications. Added capability to synchronize selections with other OpenSpirit enabled applications. These new features support integration with TIBCO Spotfire Professional and the TIBCO Spotfire Extension for OpenSpirit. Release There are no new features in this release.

11 Release Notes 3 Changes in Functionality This section lists changes in functionality since the last major (2010) release of this product. Release There are no changes in functionality in this release. Release There are no changes in functionality in this release. Release The following are changes in functionality in this release. CRS datum transformation when received events: o The Extension for ArcGIS will create the datum transformation based on the event CRS. Therefore, there is no datum transformation dialog displayed for user to select. User should check whether the datum transformation defined in ArcMap is their target datum transformation. o If there is no datum transformation available, then the dialog will be displayed as before. o The Extension for ArcGIS will check whether the ArcMap layer CRS has proper datum transformation to WGS 84 or not. If there is no one defined, then the datum transformation dialog will be displayed for selection. Compatible with OpenSpirit /64 bit release for ArcMap 9.3.1Multiple spatial data types including well, seismic and interpretation data types.

12 4 Release Notes Deprecated and Removed Features This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features. This section also lists features that are removed (if any). Release There are no deprecated or removed features in this release Release There are no deprecated or removed features in this release. Release There are no deprecated or removed features in this release.

13 Release Notes 5 Migration and Compatibility This section explains how to migrate from a previous release to this release and version compatibility. Release Migration There are no migration procedures in the release; any previous version of the OpenSpirit Extension for ArcGIS must be uninstalled before installing version Upgrading will not un-installed previously installed versions. Compatibility TIBCO OpenSpirit ArcGIS Extension requires the following products to be previously installed and available: OpenSpirit Runtime o v4.0.1 o v4.0.0 o v3.2.3 ArcGIS Desktop o v10.1 o v10.0 SP3 Certified Operating Systems Windows XP (32 & 64 bit) Windows Vista (32 & 64 bit) Windows 7 (64 bit) Release Migration There are no migration procedures in the release; any previous version of the OpenSpirit Extension for ArcGIS must be uninstalled before installing version Upgrading will not un-installed previously installed versions.

14 6 Release Notes Compatibility TIBCO OpenSpirit ArcGIS Extension requires the following products to be previously installed and available: OpenSpirit o v4.0.0 o v3.2.3 ArcGIS Desktop o v10.0 SP3 Certified Operating Systems Windows XP (32 & 64 bit) Windows Vista (32 & 64 bit) Windows 7 (64 bit) Release Migration There are no migration procedures in the release; any previous version of the OpenSpirit Extension for ArcGIS must be uninstalled before installing version Upgrading will not un-installed previously installed versions. Compatibility TIBCO OpenSpirit ArcGIS Extension requires the following products to be previously installed and available: OpenSpirit o v3.2.3 ArcGIS Desktop o v10.0 SP3 Certified Operating Systems Windows XP (32 & 64 bit) Windows Vista (32 & 64 bit) Windows 7 (64 bit)

15 Release Notes 7 Closed Issues The table in this section list issues that were closed in the named releases. Closed in Release Key Summary CR Contours sent as GIS event from Petrel to ArcMap do not overlay with contour brought in as shape file.

16 8 Release Notes Known Issues The following table lists know issues in this release. Key Summary/Workaround The OpenSpirit Extension for ArcGIS must be uninstalled before upgrading ArcGIS from version 9.x to 10, and then reinstalled after the ArcGIS upgrade is complete. Any previous version of the OpenSpirit Extension for ArcGIS must be uninstalled before installing version Upgrading will not uninstalled previously installed version After removing the OpenSpirit Extension for ArcGIS from ArcMap, close and reopen ArcMap to allow ArcMap to cleanup directories The Help file needs to be manually removed. This file is located at: C:\Users\<username>\OpenSpirit\ArcGIS Extension 2010\help.chm ArcMap 10 hangs after selecting transformations during "Add data from project" operations. This issue is fixed with ArcMap10 Service Pack Save to SDE function requires an ArcEdit license When working on ArcMap 10, the Table of Contents needs to be set on the "List By Drawing Order" tab for the GIS event to retrieve the selected objects properly Unable to create a connection to SDE using the Add OpenSpirit Layers function. Workaround: Double-click on the selection rather than selecting and clicking Add Grids are not sent from the ArcGIS Extension if they contain more than 5,000,000 cells. Workaround: Resample the grid so it has fewer than 5,000,000 cells before sending as a GIS event ArcGIS displays NULL dates as 12/30/ :00:00 AM or 12:00:00 AM When saving in-memory features to shape files, ESRI only saves date information. It supplies a NULL time (or 12:00:00 AM) For workflows involving Petrel: Petrel does not recognize holes in polygons. Petrel represents the hole as another polygon Saving in-memory layers to SDE requires a name fewer than 25 characters.

17 Release Notes 9 Key Summary/Workaround Broadcasting log curves and/or checkshots to ArcMap does not generate layers Limitation on saving some NULL values to SDE. OpenWorks data stores may have e+37 as a value indicating null, and Kingdom has e+35. SDE does not allow values greater than 17 digits, so saving to SDE may fail. Workaround is to save to Shape file or File Geodatabase When switching the Select Type on the OpenSpirit Project Selector dialog, available layers for loading does not update so in some cases the OpenSpirit Project Selector dialog may erroneously show that seismic layers can be loaded for data sources that only support wells When multiple Horizon Fault Boundaries are imported at once, the attributes Num_Points and Primary Z_Exists exhibits the attributes of only one of the objects When broadcasting data from a GeoFrame project with ft. (0.1) as the units, a patch file is required. Contact OpenSpirit support to acquire the file and apply it to your v3.2.3 installation. The file is Unit.xml and it goes into %OSP_HOME%\xml\metadata\carto\ESRIWKT directory Coordinate system transformation pop-up dialog may be hidden if the active window is not ArcMap. ESRI Issue #NIM On ArcGIS 10, the ArcGIS extension tool bar will remains on ArcMap after deleting the add-in from ArcMap Add-in Manager Oval shape created in ArcMap with ArcMap tools is considered as a polyline object, Therefore the OpenSpirit Extension retrieves it as polyline but the beginning point and end point is on the same position that it turns out as a single point With ArcGIS 10 a new layer file Well_Bottom_DOT.lyr has been created to be able to display well bottom location data properly. The Extension for ArcGIS will backup user's LayerFile directory to LayerFile_Backup in order to install the new layer files. ESRI issue #NIM When an object is imported to ArcMap by Extension and the user adds a new field to the in-memory without setting value (leave it as null), the feature class won't be saved to File Geodatabase. Workaround: Save the object to shape file/other format before add the new field To map TIBCO OpenSpirit Scan 2011 feature class to the Extension for ArcGIS model view, the user will have to apply the layer file manually When retrieving feature dataset from the File Geodatabase, the user should click on 'Add' button after select target *.gdb. The Feature Dataset Selection dialog will be displayed with available feature dataset in this File Geodatabase.

18 10 Release Notes Key ESRI issue #NIMO64979 Summary/Workaround Need to connect to OpenSpirit before selecting the OpenSpirit help icon Send/Receive cursor tracking events can yield an unhandled exception. Deleting the AssemblyCache solves the problem. Please contact support for the proper procedure These ESRI transformation types will be converted to OpenSpirit transformation types: Geocentric_Translation 2. Position_Vector 3. Coordinate_Frame 4. Molodensky 5. Abridge Molodensky The other types either ESRI does not return the information properly or OpenSpirit does not support custom transformation for it. They will be prompted datum shift dialog for user to select proper transformation. It is strongly recommended to manually create the transform in ArcMap from their custom ArcMap CRS to WGS84, and make the transform available in the ArcMap map. It is also recommended to set transformation for special CRS When there is null value for integer, float and double field, the data will be converted as "0" when save to shapefile. This is the limitation from ESRI shapefile feature. The File Geodatabase and SDE will be preserved