Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
0
Release Notes
September 2010
Copyright
Copyright © 2008‐2009 Intergraph Corporation. All Rights Reserved.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and
international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.
U.S. Government Restricted Rights Legend
Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at
private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of
the Commercial Computer Software ‐ Restricted Rights clause at 52.227‐19 of the Federal Acquisition Regulations ("FAR") and its successors,
and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense
("DoD"): This is "commercial computer software" as defined at DFARS 252.227‐7014 and the rights of the Government are as specified at
DFARS 227.7202‐3.
Unpublished ‐ rights reserved under the copyright laws of the United States.
Intergraph Corporation
P.O. Box 240000
Huntsville, AL 35813
Street address: 170 Graphics Drive, Madison, AL 35758
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the licensee
has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software
product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to
the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable
number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for
licensee's internal, non‐commercial use. The documentation may not be printed for resale or redistribution.
Warranties and Liabilities
All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software or
applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this document or its
contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this
publication is accurate as of its publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable technical
product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this
license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or
its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE
SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users
should verify for themselves that the data is accurate and suitable for their project work.
Trademarks
Intergraph and the Intergraph logo are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks
of Microsoft Corporation. Other brands and product names are trademarks of their respective owners.
Contents
About this Release ...................................................................................................................................... 5
Database-Software Version Compatibility .............................................................................................. 5
New Platforms ......................................................................................................................................... 6
Windows Server 2008, 32-bit and 64-bit .......................................................................................... 6
Windows 7 - SP1 .............................................................................................................................. 6
Internet Explorer 8 (IE8) ................................................................................................................... 7
Installation and Setup ....................................................................................................................... 7
Support for Oracle 11g - SP1 (1-4PL3T5) ...................................................................................... 10
Oracle 11g Client is supported - SP1 (1-573PQQ) ........................................................................ 10
Intergraph Common Platforms .............................................................................................................. 10
Identity and Access Management Services ................................................................................... 10
Common Raster ............................................................................................................................. 11
Common Coordinate System ......................................................................................................... 11
Rendering ....................................................................................................................................... 15
New Technologies ................................................................................................................................ 16
Translucency .................................................................................................................................. 16
Support for Web Source Data ........................................................................................................ 16
Developer Enhancements ..................................................................................................................... 17
.NET API Enhancements ............................................................................................................... 17
PDF API - SP1................................................................................................................................ 18
NetExport.................................................................................................................................................... 37
Database or Metadata .......................................................................................................................... 37
G/Technology 10.1.0 Release Notes 3
Contents
4 G/Technology 10.1.0 Release Notes
SECTION 1
G/Technology 10.1.0 Release Notes 5
About this Release
read previously published subsets, so those subsets do not have to be republished with version
10.1.0.
See the Database‐Software Version Compatibility topic in Help for complete information about
database‐software compatibility.
New Platforms
Windows Server 2008, 32‐bit and 64‐bit
The following applications support Windows Server 2008, 32‐bit and 64‐bit:
G/Technology Administrative tools
G/Technology client
NetExport Client
Viewer applications
See the G/Technology Supported Environments document on the delivery media, or for the
most current details see the Intergraph SG&I Support Web page
(http://support.intergraph.com/).
Windows 7 ‐ SP1
G/Technology now supports the Microsoft Windows 7 operating system.
Although Internet Information Services (IIS) and Microsoft Message Queuing (MSMQ) are
installed along with the Windows 7 operating system, WebDAV is not. WebDAV is an
extension of IIS, and if you need WebDAV, you must manually install it.
For more information about installing WebDAV, see the Installing WebDAV on Windows Vista
or Windows Server 2008 topic in Help.
Microsoft Windows 7 and Windows Vista *.gvp projects are saved at a different path than
earlier windows versions. The location of the file depends on the version of the Microsoft
Windows operating system you are using.
Windows Vista C:\Users\<userLogin>\AppData\Roaming\Intergraph\
GTechnology\VBAProjects\<configuration name>
Windows 7
6 G/Technology 10.1.0 Release Notes
About this Release
Windows XP C:\Documents and Settings\<user account>\Application Data\Intergraph\
GTechnology\VBAProjects\<configuration name>
Internet Explorer 8 (IE8)
The NetViewer and MobileViewer applications are supported with IE8; however, they still use
the embedded control. There is no visual change to either application.
Installation and Setup
G/Technology software installation has changed. Use the Intergraph Setup Manager
(Setup.exe) on the delivery media to begin the installation process.
The delivery media contains:
Setup.exe
AllowSetupEXEtoLaunchFromNetworkShare.bat, which enables setup launch across a
network.
Autorun.inf, which allows you to automatically start the Intergraph Setup Manager when
the media is inserted and the AutoRun feature is enabled on a computer.
The language subfolders, for example, \en, \de, \fr, which contain the SetupResources.dll.
The \Installs folder, which contains subfolders for the software delivered on the media.
EULA
G/Technology Release Notes
G/Technology Issues Resolved ‐ SP1
G/Technology Supported Environments ‐ SP1
G/Technology Installation Guide ‐ SP1
A link to the Intergraph SG&I Support Web page ‐ SP1
See the Intergraph Setup Manager Overview topic and the Installing G/Technology topic in
Help for more information:
Other changes include:
G/Technology document links are available from the Intergraph Setup Manager without
installing any software.
G/Technology 10.1.0 Release Notes 7
About this Release
Setup will check your computer for prerequisite software that supports the software you
have selected to install. If Setup does not find the required software, it displays a list of
missing prerequisite software. You must install the missing prerequisite software to
continue installation.
See System Dependencies in the G/Technology Supported Environments document for
more information.
You can add complementary software to the core application software delivery.
Intergraph provides an XML file to help with this task.
See the Complementary Software Setup Help topic in the Intergraph Setup Manager for
more information.
The All Applications Configuration Wizard configures the installed G/Technology
applications.
See the Configuring the Installed Applications topic in Help for information.
As shown in the G/Technology Setup tree, the names of the on‐line services have changed,
and several wizards are now available to configure the services.
See the Application Software Descriptions topic in Help for more information.
Before you uninstall a G/Technology application, open the Intergraph Setup Manager and
remove the configuration.
See the Changing or Removing a G/Technology Configuration topic in Help for more
information.
You can silently install, upgrade, and uninstall the G/Technology applications. You can
silently configure the client applications.
See the Using G/Technology Setup in Batch Mode topic and the topics that follow in Help
for more information.
The GTechnology.msi location has been changed from \Main to \Installs\GTechnology.
Setup - SP1
Before upgrading to a new released version of G/Technology software, you must uninstall the
existing G/Technology software released version, for example, upgrading from 9.4.3 or 10.0.2
to 10.1.0 and higher. However, you can upgrade to maintenance or service pack versions of a
released version (10.1.0 and above) without uninstalling the software first.
8 G/Technology 10.1.0 Release Notes
About this Release
See the following topics in Help for more information:
Upgrading G/Technology Software
Silently Upgrading a Large Network
G/Technology Application and Display Names, which lists the individual G/Technology
applications and their configuration requirements.
The Intergraph Setup Manager has a slightly changed interface. You no longer have to select
the application you want to install from a drop‐down list. Also, the Issues Resolved document
is now available from the list of documentation. The Issues Resolved document is also
available from the Intergraph Support Web site.
See the following topics in Help for more information:
Intergraph Setup Manager Dialog Box
Intergraph Setup Manager Icons
Example Intergraph Setup Manager dialog box:
G/Technology 10.1.0 Release Notes 9
About this Release
Support for Oracle 11g ‐ SP1 (1‐4PL3T5)
In Oracle 11g, passwords are case sensitive by default. Connecting with an Oracle 10g Client
forces the password to uppercase. Therefore, a user who has a mixed case or lowercase
Oracle password will not be able to login from a G/Technology product if passwords are case
sensitive in Oracle 11g and the user is running with an Oracle 10g client. To avoid this
problem, the administrator must set the Oracle parameter sec_case_sensitive_logon to FALSE
to allow Oracle 11g to support case‐insensitive passwords.
See the following topics in Help for more information:
Oracle Connection Problems
Oracle Database
Setting Operating System Authentication
Oracle 11g Client is supported ‐ SP1 (1‐573PQQ)
Oracle 11g Client is supported in G/Technology 10.01.0001.
When you install Oracle 11g Client, ODP.NET is installed during the installation. When you
install Oracle 10g Client, installing ODP.NET is a separate step. However, when you are
installing Oracle Server, ODP.NET is a check box on the user interface.
See the Installing Oracle Client for G/Technology 10.1.0 topic in Help for more information.
10 G/Technology 10.1.0 Release Notes
About this Release
Provide automatic login with Windows Authentication credentials.
Provide single sign‐on capability.
Control access to individual applications through users’ application roles.
Support mapping Windows authentication credentials to other database connection
credentials.
Support custom authentication schemes.
Windows NT authentication workflows do not require a user name/password input and might
not require any user input if a configuration is specified.
Database connection mapping is moved from the G3E_LOGINMAPPING table to the Identity
and Access Management Services identity store, and the InstallUserMapping.exe utility is
updated to use the identity store and to migrate existing G3E_LOGINMAPPING data.
The Intergraph Identity and Access Management Services server is installed from the
Intergraph Setup Manager.
See the Identity and Access Management Help for further information.
Intergraph Identity and Access Management Services must be configured for the primary
desktop and viewer G/Technology applications. The Intergraph Identity and Access
Management Services clients are configured with the G/Technology All Applications
Configuration Wizard.
See the following topics for more information:
G/Technology Identity and Access Management Administration
Configuring the Installed Applications
Common Raster
Historically, multiple copies of the raster software were maintained by various product
organizations, which delayed incorporation of fixes and enhancements. In G/Technology
10.1.0, the core raster software is incorporated through merge modules (MSMs) delivered with
G/Technology Setup provided by a centralized team.
See the Supported Raster Formats topic for a list of the formats with specifications.
Common Coordinate System
G/Technology now uses the Common Coordinate System (CCS) in place of the Coordinate
System Services (CSS).
See the Intergraph.CoordSystems Namespace topic in the Help for more information.
G/Technology 10.1.0 Release Notes 11
About this Release
The coordinate system API is the same as in previous versions of G/Technology. The
enhancements to the CCS capabilities are noted below.
Coordinate Formats
Support is now provided for the Degrees and decimal minutes (“d:m”) coordinate format for
readout and key‐in.
Projections
Support is now provided for additional zones in the Gauss‐Kruger projection and for the
following projections:
ARC (Equal Arc‐second Raster Chart/Map)
Budapest Stereographic
EOV
Gauss‐Boaga (Italian zones)
Gauss Conformal (South Africa)
Gauss‐Kruger (6‐degree)
HR_HDKS
Hungarian Oblique Cylindric HDR
Hungarian Oblique Cylindric HER
Hungarian Oblique Cylindric HKR
Japan Plane Rectangular (JGD2000)
Japan Plane Rectangular (Tokyo)
KKJ (Finnish zones)
MK_TM
New Brunswick Stereographic (ATS77)
New Brunswick Stereographic (NAD83)
New Zealand Transverse Mercator 2000
RD (Amersfoort)
RT 90
SI_TM
Stereographic
SWEREF 99
Geodetic Datums
12 G/Technology 10.1.0 Release Notes
About this Release
Support is now provided for the following geodetic datums:
Datum Base SE (Porto Santo 1995)
D48
Geocentric Datum of Malaysia (GDM2000)
HDKS (HR1901)
International Terrestrial Reference Frame 2000 (ITRF 2000)
MAGNA‐SIRGAS
MK
SIRGAS 2000
SWEREF 99
Timbalai (Sabah)
Timbalai (Sarawak)
Vertical Datums
It is now possible to reference and transform data between different vertical datums including
ellipsoid‐geoid conversion. Vertical datums can reference the geoid (orthometric height) or
the ellipsoid (geometric height), or they can be undefined. Geoid undulation is handled as a
vertical datum transformation.
Vertical datum information is now carried with the definition of a coordinate system through
the user interface, the programmer interface, and the storage system.
The following vertical datums are supported. The height storage type is orthometric for all
cases, except where noted.
Australian Height Datum 1971
Brazilian Vertical Datum (Imbituba)
Canadian Vertical Reference 1928
Deutsches Haupthöhennetz 1992 (DHHN92)
Earth Gravitational Model (EGM96)
Ellipsoid
International Great Lakes 1955
International Great Lakes 1985
National Geodetic Vertical Datum 1929
New Zealand Geoid (NZGeoid05)
North American Vertical Datum 1988
G/Technology 10.1.0 Release Notes 13
About this Release
Ordnance Newlyn Third Geodetic Leveling
RH 00
RH 2000
RH 70
Tsingtao
United European Leveling Network 1955
United European Leveling Network 1973
United European Leveling Network 73‐81
United European Leveling Network 95‐98
United States Gravimetric Geoid 2003
Unspecified
User‐defined (non‐standard)
Vertical datum transformations are supported as new datum transformation model types
within the DatumTransformation object and the autodt.ini configuration file. The following
vertical datum transformations are supported:
VERTCON (NGS Version 2.10)
NGA Earth Gravity Model (EGM96)
GEOID (NGS hybrid geoid)
USGG (NGS gravimetric geoid)
14 G/Technology 10.1.0 Release Notes
About this Release
Autodt.ini File
The format of this file is changed to accommodate vertical datums. A new version of this file
is delivered with G/Technology, so the impact is only on users who customize autodt.ini.
These users must consider the extended structure of the file when performing those edits and
reapply their edits after installing the product.
An autodt.ini file using the old format will be used as follows:
In processing autodt.ini, if the software encounters an entry in the old format, that entry and
all following entries will be interpreted as having the old format, which does not include
vertical datum information. All such old‐format entries will be interpreted as though both the
input and output vertical datum definitions are csvdUserDefined (the user‐defined vertical
datum). Most existing data stores (created when the vertical datum definition was not
available in the user interface) should by default use the user‐defined vertical datum, so their
handling when such an old‐format autodt.ini file is in use should be essentially the same as
with prior versions of the software.
The new vertical transformations require autodt.ini entries in the new format, so they will not
be available when an old format autodt.ini is in use. Mixing of new and old formats in
autodt.ini is not supported.
Rendering
The entire rendering system has been replaced with Intergraph’s common rendering platform
in G/Technology 10.1. Display metadata, styles and legend entries, are compatible with
previous versions. Any style metadata that was configured before version 10.1.0 should still
yield the same, or very similar, display results in version 10.1.0. In a few specific cases, a
minor metadata change is required in some data models based on the true type font definition.
See the Point Style Alignment Differences and Text Size Differences topics in Help for more
information.
The Point Size Conversion Utility is provided for the administrator to use after reviewing the
data.
See the Point Size Conversion Utility topic in Help for information.
G/Technology was upgraded to DWGDirect 2.7.3 for both native CAD display and for
ExportToAutoCAD.
G/Technology 10.1.0 Release Notes 15
About this Release
New Technologies
Translucency
G/Technology 10.1 introduces the translucency capability. You can change the translucency
value of a feature so that you can see any features or background behind it. A translucency
value of 0 means that the feature is opaque, and nothing is visible behind it. A translucency
value of 100 means that the feature is invisible, and everything behind the feature is visible.
Translucency definitions occur in several places in G/Technology:
Individual styles in metadata.
Legend entries in metadata. If this is defined, it overrides the individual styles.
User override by way of the Display Control in map or plot windows.
By way of the map output control for queries and traces.
The translucency override button on the Display Control has two parts:
A drop‐down that lets you pick translucency from a list. This overrides both the normal and
the fill translucency.
Button selection that displays the Translucency dialog box. This dialog box lets you alter
the two different translucencies separately and enter values not available from the
drop‐down list.
In the viewer applications, you can override the translucency values for Display Control entries,
for the redline properties, and for the Analysis Options.
See the following topics in Help for more information:
Translucency
Translucency in Viewer Applications
Configuring Translucency
Support for Web Source Data
Web Source Data is the generic term for data from Open Geospatial Consortium’s (OGC) Web
Map Service (WMS) and Web Feature Service (WFS). WMS/WFS support in G/Technology
provides dynamic raster/vector backdrop maps from external data providers, such as regional
governments. You configure the metadata to expose these additional features in the
G/Technology legend. The user then has the ability to view the data. Utilization in
placement and edit is also viable.
16 G/Technology 10.1.0 Release Notes
About this Release
Define the connection to the WMS/WFS with the Web Source Connection command.
Generate metadata for the Web Source with the Generate WMS Metadata or Generate
WFS Metadata command.
Desktop/Viewer:
View Web Source data when a legend containing entries for WMS or WFS data is used.
Review WFS feature attributes in Feature Explorer and WMS layer attributes using the
WMS Get Feature Info command in the desktop or in viewer.
See the WMS Get Feature Info Command topics in Help for desktop or viewer for more
information.
In the desktop, during placement and edit commands:
Snap to WFS data.
Use WFS data with Construction Aids.
New Get Feature Info command
A new command, Get Feature Info, was added for WMS data review.
See the following topics in Help for more information:
Defining a Web Source Connection
Generating WMS Metadata
Generating WFS Metadata
WMS Get Feature Info
Developer Enhancements
.NET API Enhancements
The G/Technology .NET API has changed in this release. While the API is functionally
equivalent, there is a slight syntax change that you must react to before you can deploy 10.1.
In previous releases, the .NET objects were defined as classes. They are now defined as
interfaces. This technology change allows the product flexibility in enhancing, packaging, and
delivering the automation layer.
If you are still using the VBA customization interfaces, no changes are necessary. However,
the VBA layer is deprecated and will phase out at some point in the future. As such, all new
customization should use the .NET interfaces.
See the Updating .NET API References topic in Help for more details about the necessary
changes.
G/Technology 10.1.0 Release Notes 17
About this Release
PDF API ‐ SP1
The IGTExportService API has been enhanced to provide methods and properties that perform
the following tasks:
SaveAsPDF is an overloaded method that saves a Map or Plot window’s contents to a PDF
file; you can save to a new file or append to an existing file.
AppendPDF is an overloaded method that either appends an existing PDF file to another
existing PDF file or appends two existing PDF files to create a new PDF file.
PDFLayersEnabled is a property that enables or disables PDF layer output; it applies to
SaveAsPDF methods only.
G/Technology uses software provided from AMYUNI to create and manipulate PDF files.
AMYUNI currently has a defect that prevents you from appending PDF files that contain layers.
Until AMYUNI’s fix is included in a G/Technology release, custom programmers must set the
PDFLayersEnabled property to FALSE before calling the new SaveAsPDF routines if an Append
operation is requested. If the PDFLayersEnabled property value is TRUE and an Append
operation is attempted, G/Technology will crash.
18 G/Technology 10.1.0 Release Notes
SECTION 2
Administrator
Implementation Efficiency
Implementation efficiency enhancements give you more tools to upgrade and configure the
system.
Desktop (Designer/Analyst and Administrator)
Database or Metadata
Enhancements that include major database or metadata changes deepen, expand, and enrich
the product. This release includes the following Database or Metadata enhancements:
20 G/Technology 10.1.0 Release Notes
Desktop (Designer/Analyst and Administrator)
protocol by which a map server provides georeferenced map images. Web Feature Service
(WFS) refers to the protocol by which a map server answers more detailed requests for
individual geographical features over the Internet using platform‐independent calls.
WMS/WFS support in G/Technology provides dynamic raster/vector backdrop maps from
external data providers like regional governments. The administrator must provide the initial
configuration:
Define the connection to the WMS/WFS with the Web Source Connection command.
Generate metadata for the Web Source with the Generate WMS Metadata or Generate
WFS Metadata command.
See the following topics in Help for more information:
Defining a Web Source Connection
Generating WMS Metadata
Generating WFS Metadata
Legends
Legends configuration was changed to allow for faster swapping out of legend settings (Display
Status, Locate Status, Display Scale Status, and Display Scale Range) when switching between
settings based on the same legend definition. This restructuring requires new and updated
metadata which means that the metadata must be up‐to‐date on the desktop and viewer
clients for the new functionality to work properly. The new metadata tables and their use are
listed below:
G3E_LEGENDSETTINGS ‐ New table that lets you define multiple ways to represent the
same legend. Several columns from the G3E_LEGEND table have been moved to this new
table.
G3E_SETTINGSTABLE (Sample) ‐ A sample table that contains one or more groups of legend
settings information for a single legend. These groups define multiple ways to view the
same legend. G3E_LEGEND.G3E_SETTINGSTABLE contains the actual name of the table.
The following topics pertaining to legends have been updated in Help:
Defining a New Legend in Metadata Explorer
Detail Metadata
Legend Display Control Table (Sample)
Legends Table
Deleting a Legend in Metadata Explorer
Defining a New Legend (GPT)
G/Technology 10.1.0 Release Notes 21
Desktop (Designer/Analyst and Administrator)
Adding Components to a Legend (GPT)
Copying and Pasting a Legend Entry (GPT)
Defining a New Legend Entry (GPT)
The following help topics pertaining to legends have been added in Help:
Adding Legend Settings to a Legend (GPT)
Updating Legend Entry Settings in Metadata Explorer
Updating a Legend in Metadata Explorer
Updating a Legend Entry in a Legend Definition Table in Metadata Explorer
Updating a Legend Display Control in Metadata Explorer
Defining Legends in GPT (GPT)
Adding Legend Settings to a Legend (GPT)
Copy and Paste Legend Settings (GPT)
Deleting a Legend or Legend Settings (GPT)
Update Legend Settings (GPT)
22 G/Technology 10.1.0 Release Notes
Desktop (Designer/Analyst and Administrator)
Developer Implementation
IGTDisableEditTool
Custom implementations of IGTDisableEditTool cannot change the contents of the select set.
IGTMapWindow
The BackColor property allows you to set or return the background color of a map window.
IGTPlotMap
The BackColor property allows you to set or return the background color of a map window. The
Rotation property allows you to set or retrieve the rotation of an embedded map.
3-D
Active‐Z and Element‐Z functionality can be controlled by the API. Refer to the ActiveZ and
UseActiveZ properties on the IGTApplication object.
G/Technology 10.1.0 Release Notes 23
Desktop (Designer/Analyst and Administrator)
Legend API
New legend API allows you to:
Get and set the information on a legend entry or legend group.
Apply ad hoc filters programmatically.
Replace with a metadata‐defined legend or workspace legend.
These interfaces are implemented in both VBA and .NET. The following are the new interfaces.
24 G/Technology 10.1.0 Release Notes
Desktop (Designer/Analyst and Administrator)
Relationship Modeling
Break linear features (interior connectivity)
When a Break operation occurs, the Break subsystem properly maintains interior node‐edge
connectivity relationships. The Break subsystem attempts to automatically maintain the
relationship using proximity to determine the proper node assignments to make. For
ambiguous cases, the Break subsystem displays the Resolve Node‐Edge Connectivity dialog
box to give you an opportunity to make the proper node assignments. If the broken feature
cannot relate to another feature with the same FNO, two new node IDs are generated. In
versions before 9.4.3, these node IDs are set to 0. In version 9.4.3, two new node IDs are
assigned.
See the following topics in Help for details:
Resolving Node‐Edge Connectivity
Interior Node‐Edge Connectivity Node Assignment Algorithm
G/Technology 10.1.0 Release Notes 25
Desktop (Designer/Analyst and Administrator)
Work Management
STORMS work points: work point features will only be placed automatically by the Send To
STORMS command where a CU's job ID matches the active job ID.
See the Send to STORMS Command topic in Help for more information.
OTDR Trace Operations ‐SP1 (1‐56SK1X)
The STOP_CRITERIA and CUSTOM_STOP_CRITERIA columns are now mandatory, so they are
included in the G3E_TRACE table by default. You no longer have to add them manually; the
Upgrade Wizard updates existing tables.
See the OTDR Compute Stop Criteria Procedure topic in Help for more information.
DDCScan Tool ‐ SP1
The DDC Scan tool (DDCScan.exe) is a batch process that helps you find a problem with
connecting to a configuration by processing all the component views in the DDC file. The
processing uses only the forward traversal paradigm, which runs through the data file from
beginning to end (of the particular component view’s data). Therefore, it does not access the
key index nor the spatial index. Because corruption can also occur in the indexes, the
DDCScan tool has been expanded to include both the key index and the spatial index in the
processing.
Therefore, the DDCScan tool now provides greater coverage of the processing methods used in
the product.
The Event Identifier 2002 was removed, and a command line modifier (‐M (Max check)) was
added to the 2001 Event Identifier. It is recommended that you use the ‐M option.
See the Validating DDC Files topic in Help for more information.
Replicating Data for Field Work ‐ SP1
With Oracle 10g, G/Technology used the USER_DEPENDENCIES view as a tool during
replication to identify anything that may have been missed during the replication, ensuring
that the replicated database is complete and workable. Oracle 11g does not maintain the
USER_DEPENDENCIES view. To overcome this change, replication was modified to generate
the list of objects in the master database during metadata publish or on demand.
26 G/Technology 10.1.0 Release Notes
Desktop (Designer/Analyst and Administrator)
The field database table G3E_REPLICATED_OBJECTS contains an entry for every object
replicated. Because USER_DEPENDENCIES cannot be used in the field database to identify any
database objects that have not been replicated, the population of this table was moved to the
master database. This ensures that all objects are accounted for and that the field database
is accurate.
Each procedure in the REPLICATE package issues a query to the master database to identify
objects that are to be replicated. After the object is replicated, an entry is put into
G3E_REPLICATED_OBJECTS. With the new approach, the master database uses the same
identification process to populate the new table, G3E_REPLICATION_OBJECTS, with the
MG3EREPLICATIONUTILS database package.
The replication process was modified to copy the G3E_REPLICATION_OBJECTS to the field
database. The identification queries in the dependency procedure in the REPLICATE package
were modified to query G3E_REPLICATION_OBJECTS to identify which database objects are to
be copied to the field database.
See the Replicating Data for Field Work topic in Help for more information.
Tolerant Data Publishing ‐ SP1 (1‐4PJK6H)
The introduction of the interoperability wizard for exposing GeoMedia data to G/Technology
also exposed geometry types new to G/Technology. When the publishing software
encountered one of these types, it displayed an error message, and the publish operation of
the entire component view was terminated.
Depending on the GeoMedia geometry type, one of the following solutions was implemented:
The GeoMedia‐G/Technology Interface expansion pack produces different metadata.
The publishing software recognizes and converts these types appropriately.
The following table lists the affected GeoMedia geometry types and the solution:
linears with arcs All linears are classified in metadata as
composite polylines. This classification covers
all other linear types because it is the most
complete.
G/Technology 10.1.0 Release Notes 27
Desktop (Designer/Analyst and Administrator)
polygons, All polygons are classified in metadata as
including boundaries. This classification covers all other
composite polygonal types because it is the most
polygons and complete.
polygons with
holes.
collections Changed the publishing software to handle
collections for secondary data.
TextPoint The publishing software now handles GeoMedia
geometries TextPoint geometries.
(different from
However, unicode‐based and RTF processing
G/Technology
in G/Technology are not supported.
TextPoint
geometries)
Oriented Point The publishing software now handles GeoMedia
geometries OrientedPoint geometries.
See the following topics in Help for more information:
Creating Log Files
Publishing Facility Data
Configuring Export to CAD Limitations
Trace Picklist ‐ SP1 (1‐4OXRSP )
In previous versions, G/Technology substituted picklist values for any attribute substitution for
traces, instead of the picklist keys. This made the filters difficult to construct for
multi‐language configurations.
To improve the filtering process, the G3E_USEPICKLISTKEY column was added to the
G3E_TRACE table. The new column specifies whether to use the picklist value or the picklist
key.
0 = use value. Use this for most legacy traces. This value is assigned to all existing trace
metadata.
1 = use key (default). Use this for all new traces.
28 G/Technology 10.1.0 Release Notes
Desktop (Designer/Analyst and Administrator)
The G3E_USEPICKLISTKEY column determines attribute value substitution for these columns:
G3E_FILTERCRITERIA
G3E_STOPCRITERIA
G3E_PATHCOST
See the following topics in Help for more information:
G3E_TRACE
G3E_TRACE.G3E_USEPICKLISTKEY
Area Reports ‐ SP1 (1‐4VX5GW / 1‐4ZGAHJ)
The log file generated when Area Reports are generated writes to a system‐generated
temporary folder. To provide flexibility, you can now specify the folder for the log file. You
can also create a limited version of the log file.
The following arguments have been added to the Area Reports utility (AreaReportUtility.exe):
LogFileDirectory= <name of the folder to use to write the AreaReport.log file>.
If no folder is specified, the software uses the system‐defined temporary folder.
If that folder does not exist, the AreaReport.log file will be created in the system‐defined
temporary folder to inform the user about the invalid folder.
ShortLogFile= <True or False>.
If set to TRUE, the SQL used to process the feature keys is not written to the log file. If set
to FALSE or if the parameter is omitted, the SQL used to update the key tables is written to
the log file.
See the Area Reports topic in Help for more information.
Obsolete Commands
The following functionality is replaced or obsolete for G/Technology versions 9.4.3 and 10.1.0.
These commands have been removed from the G3E_ROLEASSOCIATION table that displays in
Metadata Explorer under Access Control > Menu Access Control <command type node>:
Administrative > Edit Metadata Tables
Administrative > Display > Legends
G/Technology 10.1.0 Release Notes 29
Desktop (Designer/Analyst and Administrator)
Designer/Analyst
Usability
Vector Data
Supported AutoCAD versions are now R14 through 2009.
See the Attaching Vector Data topic in Help for more information.
Output Capabilities
Support for AMYUNI PDF Converter 4.0
G/Technology has upgraded to AMYUNI PDF Converter 4.0, and it now supports hatches.
Redlines in a map window or a plot window that have fill style of type ‘hatch’ are displayed
when exported to PDF.
Operator Productivity
3-D Workflow Enhancements
Default-Z/Element-Z
You can configure a default Active‐Z value in metadata.
See the Configuring Z Coordinates topic in Help for more information.
The default Z value can be overridden with a calculated Z based on the geometry and the
placement/edit operation.
30 G/Technology 10.1.0 Release Notes
Desktop (Designer/Analyst and Administrator)
See the Continuing Geometry topic in Help for more information.
3-D measurement
Length measurements can be calculated in 3‐D.
Data Entry
Placing a temporary geometry
After you select a temporary geometry for placement, you can click Pan, Zoom In, or Zoom Out
to move around on the map view before you place the temporary geometry.
See the Placing Temporary Geometry and Placing Features or Placement Configuration topics
for details.
G/Technology 10.1.0 Release Notes 31
Desktop (Designer/Analyst and Administrator)
See the Project Orthogonal ‐ Baseline topic in Help for details.
Navigation
Select multiple features
The Polygon Select Tool lets you draw an irregularly shaped fence to select multiple features.
See the Selecting Features with a Freehand Polygon Fence topic in Help for more information.
Find commands
G/Technology software now detects an apostrophe in the Value controls of the different query
types supported by the Find command.
Output Capabilities
Print preview
The Print Preview area at the bottom of the Page Setup dialog box gives you a chance to see
how the settings you have made on the Page Setup tabs will affect your final output.
See the Print Preview Examples topic in Help for more information.
32 G/Technology 10.1.0 Release Notes
Desktop (Designer/Analyst and Administrator)
G/Technology 10.1.0 Release Notes 33
Desktop (Designer/Analyst and Administrator)
not associated detail components. The administrator determines the user name of the
component in metadata, and specifies whether the component is available for placement in a
geographic or detail window. Similarly, depending on metadata configuration, the New
Component dialog box displays only the graphic component, not the associated detail
component.
See the following topics in Help for more information:
Placing Features or Placement Configurations
Placing a Placement Configuration
Adding Components Using New Component
Adding Components Using Feature Explorer
New Component
All Components — Sets the select mode to all components of a feature whether they are
within the fenced area or not.
All Components in the Active Legend — Sets the select mode to all components in the
active legend.
Only Selected Components — Sets the select mode to only selected components inside the
fenced area.
Map Window Properties — Determines certain settings for the map windows in your
workspace.
34 G/Technology 10.1.0 Release Notes
Desktop (Designer/Analyst and Administrator)
FROM
5 View change commands can interrupt another command for view
manipulation. For example, Zoom Out and Pan are view change
commands.
TO
6 Sub‐view commands can interrupt another command for view
manipulation. For example, Zoom Out and Pan are sub‐view commands.
See the G3E_CUSTOMCOMMAND.G3E_COMMANDCLASS topic in Help for more information.
G/Technology 10.1.0 Release Notes 35
SECTION 3
NetExport
Database or Metadata
NetExport supports FMEObjects version 2008.0.0.5193, allowing writing MicroStation graphic
cells with relative mode. This change affects MicroStation output format only.
See the G3E_EXPORTSTYLEx.G3E_CELLNAMEMAP topic in Help for more information.
G/Technology 10.1.0 Release Notes 37
NetExport
38 G/Technology 10.1.0 Release Notes
SECTION 4
NetPlot
Usability
Support for Print to PDF
You can use the G/Technology PDF printer driver through NetPlot to send PDF printer
properties as part of the plot request to the NetPlot Application Server. NetPlot supports the
generation of layered PDF output using G/Technology PDF Converter.
See the following topics for more information:
RemotePlottingRequest XML
Output Element
GTechPDFPrinter Element
Paper Size and Scale ‐ SP1
The Map Window Page Setup dialog box is now available for active plot sheets as well as active
map windows.
When you use the Page Setup dialog box with an active plot sheet, all page setup controls that
do not affect a plot sheet (margins, scale, fit to specified number of pages, custom scale) are
disabled.
See the Paper Size and Scale topic in Help for more information.
Implementation Efficiency
Developer Enhancements
NetViewer to NetPlot
The following enhancements are now supported:
Ad hoc attachments are supported in a Plot.
Translucency overrides.
Legend entry filter overrides.
G/Technology 10.1.0 Release Notes 39
NetPlot
40 G/Technology 10.1.0 Release Notes
SECTION 5
Viewer Applications
Administrator
Administering the Web Client Context Database ‐SP1 (31762_U)
To configure the Web Client Context (webcc) database using SQL Server, you now need to
specify the SQL Server Instance name and the mixed mode authentication (including sa
Password) for the instance of the database that you want to use.
To verify that the Web Client Context is actually attached to an SQL Server instance, do the
following:
1. Run the following command line query:
sqlcmd -S .\<Instance name> -U sa -P Password -Q "select name from
sys.databases"
2. Verify that “WebClientContext” appears in the results.
Example
If ‘NAMEDINSTANCE1’ is the instance name, the following query determines
whether webcc is attached to the NAMEDINSTANCE1 instance:
sqlcmd -S .\NamedInstance1 -U sa -P Password -Q "select
name from sys.databases”
Registry Entries ‐ SP1 (31974_U / 1‐553ITT)
In NetViewer/MobileViewer, trace highlighted components that were not configured for the
active legend.
Trace now highlights only the components of the active legend. This was accomplished by
using a new registry variable, ExcludeNonLegendGraphics (Type :REG_DWORD) under
'HKEY_LOCAL_MACHINE > SOFTWARE > Intergraph > GNetViewerServer > 09.00 > MapServers'.
This is similar to the UseLegendEntryFilterForQuery entry. To use this functionality, define
this registry variable manually and set the value to one (1).
G/Technology 10.1.0 Release Notes 41
Viewer Applications
NetViewer Printing Improvements ‐SP1 (1‐54GOD0 / 1‐4W47YV)
A new command, PrintMapTemplate, has been added as WPFPrintingSample, a sample add‐on
CAB module. It is delivered with the product's source code so that project teams can alter the
end user workflow.
See the following topics in Help for more information:
CAB Custom Samples
Example CAB Module Registry
NetPlot and NetViewer Printing Enhancements ‐ SP1 (1‐4VVZS6)
The default value for each kind of printer, local or network, is initially set to 0. The
GDR_COLORMODE value states the capability and the default color selection for each printer.
Valid values are 0, 1, and 2. Any other value or the absence of this field is treated as a
GDR_COLORMODE value of 0.
There are two methods NetViewer uses to determine the color capability of a printer. The
method used is dependent on the type of printer. The two types of printers are Network and
Local. Network printers are defined as printers installed on the Plot Server. Local printers are
defined as printers installed on a local computer and shared on the network.
Even if a printer supports color, you can set this value to 0 to prevent users from printing in
color.
See the following topics in Help for more information:
GDR_GNVPRINTERS (Available Printers for Plotting Table)
GDR_GNVPLOTCONFIG (GDR_GNVPLOTCONFIG View)
RemotePlottingRequest XML Documents
Sending Plots to NetPlot
Defining Plots Along a Line
Usability
Web Client Context Database
G/Technology NetViewer and MobileViewer Web Client Context Database supports all versions
of Microsoft SQL Server 2005 and 2008, including the following:
SQL Server 2008 is simpler to install and manage.
42 G/Technology 10.1.0 Release Notes
Viewer Applications
SQL/DMO from compatibility pack is required for SQL Server 2008.
DTS from compatibility pack is required for both 2005 and 2008.
Common Viewer Architecture
The main goal of these enhancements is to make the creation and management of a global
command GUI much easier for CAB module developers. It is now possible for a module to
declaratively specify its global command GUI in its .config file and have the IngrViewer
framework automatically create the button or menu item on toolstrips and manage the
enabling/disabling and checked/unchecked states of those items.
See the following topics in Help for more information:
Configuring MobileViewer and NetViewer
Commands Element
CAB Module Registry
Operator Productivity
Miscellaneous User Enhancements
Feature Explorer Workflow
The Feature Explorer workflow is improved. By default, the result page is minimized on
startup so you do not see an empty page when you open the application. The result page will
automatically show itself if a command workflow outputs to one of the result page tabs and
the result page is currently collapsed. If Feature Explorer is collapsed, you can double click a
single feature to automatically display it. If the locate operation selects more than one feature,
both features are displayed in the results page.
G/Technology 10.1.0 Release Notes 43
Viewer Applications
Analysis Workflow
The Analysis workflow is improved. You can type or select an attribute value for a query from a
picklist. Users click a back arrow to exit the Analysis Options page. You can type or select a
line weight value on the Analysis Options page.
44 G/Technology 10.1.0 Release Notes
Viewer Applications
Implementation Efficiency
Implementation efficiency enhancements give you more tools to upgrade and configure the
system.
Developer Enhancements
API and the Redline Properties
API and the Redline Properties dialog box support alignment style.
NetViewer to NetPlot
The following enhancements are now supported:
Ad hoc attachments are supported in a Plot.
Translucency overrides are supported.
Legend entry filter overrides are supported.
Analysis Reporting
Analysis reporting is improved. You can configure the number of rows displayed on a report
page. You can also sort query results by a column header. When you scroll a page of query
results, the column headers remain fixed.
Running on SQL Server 2008 Express Instances Other than the Default
G/Technology NetViewer, MobileViewer, and PublishSubset are now configurable to run on
SQL Server 2008 Express instances other than the default. Subsets automatically upgrade from
2005 to 2008. However, the 2008 subsets are not backwardly compatible to 2005.
G/Technology 10.1.0 Release Notes 45
Viewer Applications
Viewer Configuration
You no longer have to manually stop the G/Technology services before uninstalling and
upgrading.
Because the G/Technology services are now configured with wizards, and because you
must run the wizard and remove any configuration before you uninstall and upgrade,
manually stopping the services is no longer a requirement.
See the Configuring the Installed Applications topic in Help for more information.
Web Client Context
A confirmation message displays when resetting the Web client context database.
See the Administering the Web Client Context Database topic in Help for more information.
You can set the following variables in Customize.inc:
ViewResultPane so that Feature Explorer results are displayed on application startup.
ReportRowsThreshold to produce a warning on a report result if you select or type a
number that exceeds the value. The threshold value is set to prevent the report
display from taking an excessive amount of time.
The ReadoutKeyinCoordSystemDefault to specify the default coordinate system to be
used for readouts and keyins.
DetailMinFitDistanceDefault to set the minimum distance that Zoom Area and Fit
Selected will show for details.
If you are upgrading from prior versions of oneMobile, NetViewer Server, or MobileViewer
to 9.4.3 or 10.1, make sure you upgrade appropriately using the Intergraph Setup
Manager.
For example, when the /r parameter is used by the Intergraph Setup Manager, you must
add the new entry ReadoutKeyinCoordSystemDefault to the restored prior version’s
Customize.inc. When parameter /a is used by the Intergraph Setup Wizard, you must
reapply your modifications to an installed new version of user‐configurable resources.
See the following topics in Help for more information:
Custimize.inc
Installing G/Technology
Support for https
HTTPS support in NetViewer lets you run NetViewer over a more secure network, ensuring
encrypted transmission of data.
46 G/Technology 10.1.0 Release Notes
Viewer Applications
See the Applications Element topic in Help for more information.
Store four corners of plot box
The RemotePlottingRequest XML > MapFrameAssignment > RemotePlottingRequest >
PlotBoxVertices element stores the four corners of a plot box. The corners are stored as x1,
y1; x2, y2; x3, y3; x4, y4. The plot box points are included in the request to allow you to use
the NetViewer to NetPlot customization hooks to keep a log of the geographic areas that
had been plotted.
Database or Metadata
Viewer Application Developer Enhancements
You can set the default width of the left‐hand command panel in metadata.
Viewer Configuration
The G3E_DISPLAYMODE, G3E_LOCATABLE, and G3E_USEDISPLAYSCALE columns have been
added to the G3E_NETANALYSISOPTIONS table so you can determine the initial setting of
analysis results appended to the Display Control. The G3E_ROWSPERPAGE column in
G3E_NETANALYSISOPTIONS lets you set a default value for the number of rows displayed per
analysis results page. You can override this default.
Changes in the G3E_NETPAGES Table
A new column, G3E_INPUTFRAMESIZE, has been added to the G3E_NETPAGES table.
You can use G3E_NETPAGES.G3E_ASP (WMSAttributes.aspx) to configure multiple WMS
Get Feature Info commands or to restrict which WMS views can be used for this command.
See the following topics in Help for more information:
G3E_NETPAGES
G3E_NETPAGES.G3E_ASP
G/Technology 10.1.0 Release Notes 47
SECTION 6
Documentation
The look and behavior of G/Technology Help has changed. The Search Tips button is no
longer available on the Help toolbar. Read the topic Searching Help, available near the top of
the Help file, for information on how to find the information you need in Help.
To search for a specific help topic and find it in the table of contents:
a. Type a search string in the search for field.
b. Select the topic from the resulting list.
c. When the topic displays in the right‐hand window, click in it.
d. Click the Contents tab to locate the topic in the table of contents. (The Locate button is
no longer available on the Help toolbar.)
Press F5 or select Options > Refresh to refresh the display after searching. (The Refresh
button is no longer available on the Help toolbar.)
You can no longer press SHIFT and click a link to display the linked topic in a separate
window.
The new Index tab lists the name of every topic in Help.
These release notes and several new documents are available from the Intergraph Setup
Manager dialog box as follows:
G/Technology Installation Guide
G/Technology Supported Environments
G/Technology Database‐Software Version Compatibility
The documentation delivered with G/Technology is listed in the Document Set for
G/Technology topic in the Administrator’s Guide to G/Technology Help.
G/Technology 10.1.0 Release Notes 49
Documentation
New Topics
The following Help topics are new in G/Technology 10.01:
G/Technology Authentication and Connection Mapping
G/Technology Identity and Access Management Overview
Installing an Upgrade
Removing, Changing, or Repairing G/Technology Using the Control Panel
Selecting Features with a Freehand Polygon Fence
Silently Removing a Configuration
Uninstalling a G/Technology Patch
Update Access to Coordinate System Objects
Use these Legacy Filters when Upgrading Databases
User Demand Exceeds System Resources ‐ Provides information regarding health
monitoring of your NetViewer map servers. This topic contains a link to the description of
the registry entries you can configure to monitor server performance.
Updated or Improved Topics
The following help topics were updated or improved:
NET API References
Area ReportsVisual Basic for Applications Development Procedure
CAB Custom Samples
Clearing the Job(s)
Configuring Export to CAD Limitations
ConnectionLogins Element
Copying Jobs
CopyJob Method
Creating a Job
Creating Log Files
CreateJob Method
Fitting the Job(s) in the View
G3E_AREASTYLE (Area Style Table)
G3E_ATTRIBUTE (Attribute Properties Table)
G3E_CUSTOMCOMMAND.G3E_COMMANDCLASS
50 G/Technology 10.1.0 Release Notes
Documentation
G3E_FILTERCRITERIA
G3E_JOB (Job Table (Example))G3E_PATHCOST
G3E_MANYOWNERSHIP (Many‐to‐Many Ownership Relationship Table) (Sample)
G3E_NETPAGES
G3E_NETPAGES.G3E_ASP
G3E_NODEEDGECONNECTIVITY (Node‐Edge Connectivity Relationship Table) (Sample)
G3E_NODEORDCONNECTIVITY (Node‐Ordered Connectivity Relationship Table) (Sample)
G3E_OWNERSHIP (Ownership Relationship Table) (Sample)
G3E_STOPCRITERIA
G3E_TRACE (Trace Table)
G3E_WRAPTEXT
Installing G/Technology
Installing IIS and MSMQ on Windows XP
Installing Oracle Client for G/Technology 10.1.0
Installing Required Windows Software
Installing Subsets
Installing User Mapping
Installing WebDAV on Windows Vista or Windows Server 2008
Intergraph Setup Manager Overview
Jobs
MobileViewer Configuration Wizard
MobileViewer Configuration Wizard Parameters
NetPlot Installation
NetPlotService.exe.config
Oracle Connection Problems
Oracle Database
OTDR Compute Stop Criteria Procedure
Ownership Metadata
Paper Size and Scale
Presentation Fields in G3E_ATTRIBUTE
Publishing
Publishing a Full Subset
G/Technology 10.1.0 Release Notes 51
Documentation
Publishing Incremental Subsets
Publishing Facility Data
Publishing Subset Jobs
Remote Plotting XML Schemas
Replicating Data for Field Work
Reviewing Pending Job(s) Edits
Running G/Technology Executables with Elevated Privileges
Selecting Features with PickQuick
Sending Plots to NetPlot
Setting Operating System Authentication
Setting Select Tool Options
Silently Configuring Installed Applications
Silently Installing G/Technology
To Implement a Custom Command Object
To Implement a Custom Construction Aid Object
Translucency
Validating DDC Files
Removed Topics
The following topics are obsolete and were removed from Help:
RemotePlotting XML Documents (and all subtopics).
PlotStatus Element (and all subtopics).
Custom Plot XML Example.
52 G/Technology 10.1.0 Release Notes
Documentation
G/Technology 10.1.0 Release Notes 53
SECTION 7
Upgrade Wizard
If an LTT view is defined in metadata to be a published picklist, the metadata publish will
fail during the upgrade from 9.43 to 10.1. This is due to schema changes in 10.1 that caused
the package LTT_USER to be invalid at this point in the process. (TR 31899)
Workaround: Run the Upgrade Wizard as normal. When you receive the metadata
publish error, modify the resume file to skip the metadata publish and proceed to loading
the runtime PL/SQL. After the upgrade has completed, publish the metadata manually.
To modify the resume file, replace the contents of the second line with RUNTIMEPLSQL,
delete the contents of the third line, and make sure there is a blank line after it. The
modified resume file should look like the following example:
10.01.0000.14001
RUNTIMEPLSQL
FALSE
FALSE
The version number in the first line may be different, but the rest of the lines should look
like the example.
In the G3E_UNITFORMAT table, the G3E_ZHEIGHTUNIT field has a check constraint that
prevents invalid units from being entered in the field. If your database’s zheightunit is in
meters, G3E_UNITFORMAT.G3E_ZHEIGHTUNIT must be a lowercase ‘m’ in order for the
constraint to be honored – and for the software to work. However, in many databases,
the field was defaulted to a capital ‘M’. Before running the upgrade wizard, check this
value and if it is an uppercase ‘M’, change it to a lowercase ‘m’. (TR 31520)
API
Custom code that contains the ADO option parameter adExecuteNoRecords along with
adStoredProc will result in an error.
G/Technology 10.1.0 Release Notes 55
G/Technology 10.1.0 Known Open Issues
Workaround: Remove the adExecuteNoRecords option from the code. (TR 30179)
Setup/Configuration Wizards
In G/Technology 10.1, new configuration wizards were added, and the existing configuration
wizards were enhanced. The configuration wizards for the corresponding products must be
run before running the products. If the configuration wizards are not run, users will
encounter various issues. Refer to the Configuring the Installed Applications administrative
Help topic for additional details on the configuration wizards.
When installing MobileViewer or OneMobile in batch mode, the path to the configuration
file (/f switch) must not contain spaces. (TR 31742)
The configuration wizard for Work Management displays both configuration options (JLC
and Message Monitor) even if only one was installed. Note that the configuration wizard
will configure the correct option, even though both are displayed. (TR 31539)
When using the All Applications configuration wizard, if an invalid value is entered for the
license server .lic source file, the user cannot go to the next step or go back to the previous
step.
Workaround: The user must enter a valid path and file name. (TR 31357)
56 G/Technology 10.1.0 Release Notes
G/Technology 10.1.0 Known Open Issues
When you use the Attach Raster Backdrop command to place a raster feature interactively
in such a way that the image is skewed, the raster outline might not be visible. (TR 31196)
When you use the File > Export to PDF command to export to PDF, the
G3E_GENERALPARAMETER PDFLayersVsTranslucency value is honored if there are features
to be exported that are translucent. The resulting PDF file will not contain layers even
though PDF layers are defined in metadata.
Schematics:
If translucency is applied to traces in schematics, the trace will disappear in the
schematics window. (TR 31717)
Schematics output to XML will show different symbology when XML is input to another
schematic. (TR 31201)
Selected schematics do not show up in select color. (TR 31214)
Desktop
The G3E_USERNAME in some of the styles has a single leading space. In previous
versions, these spaces were handled, but in 10.1 leading spaces result in errors. (TR 31678)
Example: When a new Plot Window is opened and you attempt to draw redlines, the
control that allows you to override styles, and so on, gives errors. If you attempt to select
a style, the drop‐down list is empty.
Workaround: Trim the leading spaces and publish the metadata.
Embedded object frames in plot windows may be crooked or partially drawn. (TR 31677)
Printing with translucent features might cause CAD graphics to print lighter than normal.
(TR 31574)
The North Arrow fill color will not be exported to PDF on a Windows Server 2008 machine.
(TR 31632)
When double clicking a workspace to open and use Windows Authentication, some
dockable controls might be turned off. (TR 31356)
Inserting a record into G3E_ATTRUBTE for a field defined as SDO_GEOMETRY will
incorrectly set the G3E_DATATYPE value to ‐1. It should be 32 (gdbSpatial). (TR 31386)
The translucency buttons on the display control will disappear when the display control is
re‐sized very small. (TR 31448)
Pan does not interrupt Rotate Map in a plot window when the map frame is active. (TR
31484)
G/Technology 10.1.0 Release Notes 57
G/Technology 10.1.0 Known Open Issues
When you insert an object displayed as an icon, it will not display correctly. (TR 31553)
Changing the color of an attached raster might not automatically update the display. (TR
31560)
Workaround: Select the View > Refresh > Map Windows command to refresh the
display with the correct color.
The Erase Raster command only supports the deletion of raster data in binary tiff formats.
(TR 31646).
A marker will not be placed in the detail window if the marker is on the first cable section in
the detail window. (TR 31652)
In the Edit > Features > Explore Feature command, the column type of number in
dimension tables might display an error if the scale and precision of the value exceeds 28
digits. (TR 31667)
Display Web Source data might be slow. (TR 31698)
Workaround: Set the Web Source data display to a reasonable scale to prevent slow
display.
The Fit All command in the display control does not exclude display control filtered data.
Any data that may be filtered out by a display control filter will be included in the fit even
though it is not visible. (TR 31719)
Issuing queries that return large amounts of data might fail with an out‐of‐memory
exception. (TR 31741)
Generated 3D MicroStation V8 files might not fit correctly when viewed in MicroStation V8.
(TR 31753)
During connection you may get the "Unspecified DDC file" error message with no file name.
(TR 31760)
Workaround: Reboot the file server where the DDC files are located.
The Polygon Select Tool errors when selecting secondary data in which the geometry field
name is not G3E_GEOMETRY. (TR 31774)
Export to PDF will not export WMS data if the coordinate system between G/Technology
and WMS are not the same. (TR 31777)
Selecting or locating an area feature will fill the area with the select or locate color. (TR
31779)
The Update Mobile command is unable to delete an installed job if the job name contains
an apostrophe. (TR 31799)
The Measure Area command is unable to measure the area of a WFS feature. (TR 31844)
58 G/Technology 10.1.0 Release Notes
G/Technology 10.1.0 Known Open Issues
The ConvertFVRedlines utility (ConvertFVRedlines.exe), which converts FRAMME Field View
Redline Files to an XML File compatible with the G/Technology Redlines.xsd XML schema
definition, does not execute. (TR 31887)
G/Technology 10.1.0 Release Notes 59