RELEASE GUIDE - Hexagon Geospatial...data, including raster, elevation, LiDAR and others. Extensive...

RELEASE GUIDE IMAGE SCOUT

October 19, 2016

October 19, 2016 2

Contents

About This Release ........................................................................................................................ 6

Image Scout.................................................................................................................................... 6

New Platforms ................................................................................................................................ 6

GeoMedia 16.00 and Core Components ................................ Error! Bookmark not defined.

Support for Windows 10 ........................................................................................................ 6

PhotoCommon ...................................................................................................................... 7

Impacts ........................................................................................................................................... 7

GeoWorkspaces ................................................................................................................... 7

New Technology ............................................................................................................................ 8

General ................................................................................................................................. 8

Product Tier Changes .......................................................................................... 8

GeoMedia Configuration Wizard .......................................................................... 9

.net Customization ............................................................................................... 9

Application Object ............................................................................................... 9

Online Help ........................................................................................................ 10

Explorer Window ............................................................................................... 11

Data Access ........................................................................................................................ 12

CAD data server ................................................................................................ 12

Oracle Object Model data server and Oracle Object LTT data server ............... 12

PostGIS data server .......................................................................................... 12

SQL Server data server and SQL Server Spatial data server ............................ 13

WMTS data server ............................................................................................. 14

WMS Info command .......................................................................................... 15

Connections command ...................................................................................... 15

Coordinate Systems .......................................................................................... 17

October 19, 2016 3

Analysis .............................................................................................................................. 18

Attribute Query command / Filter Dialog ............................................................ 18

Functional Attributes Dialog ............................................................................... 18

Map Display ........................................................................................................................ 19

PickQuickDialog API for Microsoft.NET Clients ................................................. 19

Thematic Legend Entries ................................................................................... 19

Picklist for Unique Value Legend Entry .............................................................. 19

Display Location dockable control ..................................................................... 19

Labeling .............................................................................................................................. 20

Performance ...................................................................................................... 20

Data Capture ....................................................................................................................... 20

GPS Tracking command.................................................................................... 20

Split Feature command ..................................................................................... 20

Data Management............................................................................................................... 20

Output to Offline command ................................................................................ 20

Post from Offline command ............................................................................... 21

Data Integration and Validation ........................................................................................... 22

Create Conflation Links command ..................................................................... 22

Auto Adjust Features command ........................................................................ 23

Query Connectivity command ............................................................................ 24

Fix Connectivity command ................................................................................. 25

Data Window ....................................................................................................................... 26

DataView control ............................................................................................... 26

Layout Window ................................................................................................................... 26

Export Layout command .................................................................................... 26

Cadastral............................................................................................................................. 27

Command renaming .......................................................................................... 27

Support for SQL Server Spatial ......................................................................... 27

October 19, 2016 4

Libraries .............................................................................................................................. 27

Support for SQL Server Spatial Read-Write data server .................................... 27

Support for PostGIS Read-Write data server ..................................................... 29

Feature Caching ................................................................................................................. 29

Indexed Feature Cache (IFC) files ..................................................................... 29

Utilities ................................................................................................................................ 30

Batch Plotting .................................................................................................... 30

Database Utilities ............................................................................................... 30

Define Symbol File ............................................................................................ 30

Schema Remodeler ........................................................................................... 31

Spatial Model Editor .......................................................................................... 32

Point Cloud Integration ........................................................................................................ 32

Viewshed Analysis .............................................................................................................. 33

Environmental Effects ......................................................................................................... 33

3D Preferences ................................................................................................................... 34

Image Light Table Plus 2016............................................................................................... 34

System Requirements ................................................................................................................. 36

System Requirements Notes ............................................................................................... 37

Issues Resolved ........................................................................................................................... 37

GeoMedia Professional ....................................................................................................... 37

GeoMedia Image Professional .......................................................................................... 114

GeoMedia 3D .................................................................................................................... 115

Deprecated ................................................................................................................................. 120

Windows 8.0 ..................................................................................................................... 120

32-bit Operating Systems .................................................................................................. 120

MGE Data Server .............................................................................................................. 120

FRAMME Data Server ...................................................................................................... 120

ArcInfo Data Server........................................................................................................... 121

GeoGraphics Data Server ................................................................................................. 121

About Us ..................................................................................................................................... 122

October 19, 2016 5

About This Release

October 19, 2016 6

ABOUT THIS RELEASE This document describes the enhancements for Image Scout. Although the information in this document is current as of the product release, see the Hexagon Geospatial Support website for the most current version.

This release includes both enhancements and fixes. For information on fixes that were made to Image Scout for this release, see the Issues Resolved section. For information on enhancements, see the New Technology section.

This document is only an overview and does not provide all of the details about the product's capabilities. See the online help and other documents provided with Image Scout for more information.

IMAGE SCOUT As a viewing and analysis tool, Image Scout allows you to combine multiple images into a virtual mosaic for seamless smooth roam over a vast and complex area. Using Image Scout, you can perform complex queries on spatial and attribute data from various sources and produce numerous views of highly sophisticated maps in a single GeoWorkspace. Furthermore, Image Scout lets you print those map views on a single sheet and add borders, marginalia, and other finishing touches.

Image Scout is composed of three different Hexagon Geospatial products:

GeoMedia Professional: An enterprise GIS that is the perfect tool for collecting and analyzing GIS data, populating an enterprise database, and turning information into precise finished maps for distribution and presentation. Includes a complete Grid tool kit for spatial and distributional analysis of any kind of gridded data, including raster, elevation, LiDAR and others. Extensive Help examples direct the user to many different types of analyses such as: hot spot analysis, least cost routing, contour generations and many more.

GeoMedia Image Professional: Provides image light table capabilities for creating virtual mosaics, image enhancements, image comparison, image annotation, research and negation, directed search over linear and area features, and much more: based on Overwatch Systems' Image Light Table Plus (ILT) product.

GeoMedia GeoDEX: A viewing and analysis tool for geographic information providing the capability for the user to create MGRS grids and work with specialized image data sets such as CADRG, CIB, and others.

Image Scout 3D also includes the following product:

GeoMedia 3D: Provides an integrated 3D visualization and analysis environment. You can visualize, navigate, analyse, and interact with 3D data natively in GeoMedia. In addition, you can dynamically integrate surfaces, imagery, feature data, and vector data to provide a 3D view of all data sources in a GeoMedia 3D map window.

NEW PLATFORMS

SUPPORT FOR WINDOWS 10 Image Scout now offers support for the Windows 10 64-bit operating system.

Impacts

October 19, 2016 7

PHOTOCOMMON PhotoCommon 16.00 has been built with latest ILTP, Ziphoto, and Common Raster Platform.

IMPACTS

GEOWORKSPACES GeoWorkspace files from GeoMedia 2015 and previous may be opened in GeoMedia 2016. GeoWorkspace files saved with GeoMedia 2016 cannot be opened in GeoMedia 2015 and previous.

New Technology

October 19, 2016 8

NEW TECHNOLOGY

GENERAL

PRODUCT TIER CHANGES Do more with GeoMedia Advantage

Four commands that were previously available only in the GeoMedia Professional tier are also now available in the GeoMedia Advantage tier. The commands are:

Insert Area by Face

Insert Interactive Area by Face

Dimensions

Insert Dimensions

The addition to the GeoMedia Advantage ribbon bar Home tab is:

The additions to the GeoMedia Advantage ribbon bar Vector tab are:

This change was introduced with GeoMedia 15.1.

New Technology

October 19, 2016 9

GEOMEDIA CONFIGURATION WIZARD Configure the Spatial Model Editor, too

This wizard, which runs automatically after product installation and can also be run any time from the Start menu in order to change the product tier, language, or licensing, now also performs configuration for the new Spatial Model Editor utility, including preparing its help files for use.

.NET CUSTOMIZATION Simplify and stabilize your .net applications

.NET commands/components no longer need to use Marshal.FinalReleaseComObject or Marshal.ReleaseComObject. Microsoft could not clearly define the behavior of these methods and as a result we were experiencing the over-release of underlying COM objects in certain scenarios. We have now resolved the need for these calls within the product. Application developers should stop calling these methods, for improved product quality.

Learn more about event processing with GeoMedia objects

A section on Event Processing has been added to the Overview section of the GeoMedia Object Reference help, for .NET programmers who program against GeoMedia objects using events.

APPLICATION OBJECT Achieve deeper customization with new Application API

Now provides a pair of events to notify listeners when a new MapWindow or DataWindow is created. These events are BeforeWindowNew and AfterWindowNew. The BeforeWindowNew event allows the event handler to cancel the task of creating a new window. The corresponding AfterWindowNew event provides the newly created window object.

Now provides a property ActiveCommandProgId that denotes the programmatic identifier of the currently active command, a method GetCommandProperties that returns the command type and modeless listener level of the specified command ProgId, and an event BeforeCommandActivated that notifies listeners when a command is activated or reactivated.

New Technology

October 19, 2016 10

ONLINE HELP Find up-to-date help content and an improved user experience online

Online Help is available from both the Start menu of Windows, and the Application menu within the GeoMedia Desktop ribbon. It activates the default internet browser to present the help page for GeoMedia. This page allows searching and browsing for topics in GeoMedia (all three tiers), GeoMedia 3D, GeoMedia Transportation Manager, and GeoMedia Viewer.

New Technology

October 19, 2016 11

EXPLORER WINDOW At-your-fingertips access to your GeoWorkspace content for easy display

The new Explorer window, toggled on/off by the Explorer command on the Home ribbon tab, provides a hierarchical visual representation of various objects in the GeoWorkspace such as Warehouse Connections, Feature Classes, Queries, and Categories. Certain activities are available from the right-click context menu, including ability to display data in a map window or data window. Much more capability is planned for the future.

New Technology

October 19, 2016 12

DATA ACCESS

CAD DATA SERVER Achieve higher-fidelity display of MicroStation v8 cells

For MicroStation v8 files, this data server now supports exploding of cells through use of the “SERVE CELL GEOMETRY EXPLODE” option in the warehouse configuration file.


ORACLE OBJECT MODEL DATA SERVER AND ORACLE OBJECT LTT DATA SERVER Submit more complex queries to Oracle

Any data server can receive queries that include both a spatial filter and an attribute filter. That combination is common with GeoMedia WebMap. This data server, when handling such a query, attempts to fuse the two filtering criteria into a single SQL statement transmitted to the underlying database engine. But when the attribute filter is comprised of complex SQL involving Oracle-specific syntax that cannot be parsed by GeoMedia, it has previously failed to execute the query. Now if a spatial filter is applied and the SQL cannot be parsed, the data server takes one of two paths: (1) If the token @SF@ is present in the SQL, then the native spatial filtering SQL generated by the data server is inserted in place of that token before submission to the database, permitting the creator of the SQL the opportunity to ensure that Oracle can process the full query. (2) If that token is not present in the SQL, then it submits the complex SQL to the underlying database as-is, and performs client-side spatial filtering within the data server instead of failing on the OpenRecordset call. This allows more flexibility in use of native Oracle syntax in conjunction with a spatial filter.

Take advantage of more Oracle data types

Now supports NVARCHAR2, NCHAR, and NCLOB data types.

POSTGIS DATA SERVER Use PostgreSQL / PostGIS throughout GeoMedia

A new read-write PostGIS data server is delivered. This data server is different from that available as open source for several years.

New Technology

October 19, 2016 13

The data server is supported throughout the GeoMedia Desktop, except for those commands formerly part of the GeoMedia Parcel Manager product which require a Cadastral connection, the ERDAS APOLLO Catalog Explorer command, and the GeoMedia catalog command set.

SQL SERVER DATA SERVER AND SQL SERVER SPATIAL DATA SERVER Submit more complex queries to SQL Server

Any data server can receive queries that include both a spatial filter and an attribute filter. That combination is common with GeoMedia WebMap. These data servers, when handling such a query, attempt to fuse the two filtering criteria into a single SQL statement transmitted to the underlying database engine. But when the attribute filter is comprised of complex SQL involving SQL Server-specific syntax that cannot be parsed by GeoMedia, it has previously failed to execute the query. Now if a spatial filter is applied and the SQL cannot be parsed, the data servers take one of two paths: (1) If the token @SF@ is present in the SQL, then the native spatial filtering SQL generated by the data server is inserted in place of that token before submission to the database, permitting the creator of the SQL the opportunity to ensure that SQL Server can process the full query. (2) If that token is not present in the SQL, then it submits the complex SQL to the underlying database as-is, and performs client-side spatial filtering within the data server instead of failing on the OpenRecordset call. This allows more flexibility in use of native SQL Server syntax in conjunction with a spatial filter.

New Technology

October 19, 2016 14

Use SQL Azure throughout GeoMedia

SQL Server Spatial data server now supports connection to a SQL Azure database.

Use SQL Server Spatial throughout GeoMedia

SQL Server Spatial data server is now supported throughout the GeoMedia Desktop, except for the GeoMedia catalog command set.

WMTS DATA SERVER Display maps from WMTS services

A new read-only data server for OGC Web Map Tile Service (WMTS) is delivered. This data server serves pre-rendered georeferenced map tiles.

New Technology

October 19, 2016 15

WMS INFO COMMAND Retrieve feature information from WMTS services

The WMS Info command is enhanced to support WMTS layers.

CONNECTIONS COMMAND Clear your feature cache in fewer steps

The Refresh Cache / Clear Cache functionality is removed from connection Properties dialog and is now available directly from the Connections command.

New Technology

October 19, 2016 16

A Clear Cache button is added to the Warehouse Connections command. This enables the user to delete or refresh the cache files associated with one or more selected connections, all at once, without having to invoke the connection Properties dialog.

See at a glance which warehouse connections are cached

A new mechanism of indicating the state of feature caching is added to Warehouse Connections command. Now three different glyphs are introduced to indicate that the caching is enabled on read-write, read-only, and closed connections.

New Technology

October 19, 2016 17

COORDINATE SYSTEMS Leverage more coordinate reference systems

Support has been added for the Royal Commission of Jubail Plant Grid. This is a preset grid system having no user-definable parameters. It is selected as the projection algorithm “RC Jubail Plant Grid.” This system adjusts the Plant Grid coordinates to earth via multiple steps that include a localized polynomial generated from control points. In conjunction with this new system, a new vertical datum value has been added into the system. This value, RC Jubail Local, represents the vertical reference for the RC Jubail Plant Grid system. The software handles it as an orthometric vertical reference.

Support has been added for the Molodensky-Badekas 10-parameter datum transformation. This model transforms between horizontal geodetic datums and may be used with either orthometric or geometric height coordinates. New syntax has been added within the autodt.ini datum transformation configuration file that allows users to specify parameters to use the Molodensky-Badekas transformation there.

Identify coordinate reference systems by EPSG codes

The Define Coordinate System control and dialog used by the GeoWorkspace Coordinate System command, the Define Coordinate System File utility, and other parts of GeoMedia, now have a Coordinate reference system

New Technology

October 19, 2016 18

authority frame on the General tab, offering the ability to enter an EPSG code in order to define a coordinate reference system, or to see the EPSG code corresponding to the current CRS definition (if any).

ANALYSIS

ATTRIBUTE QUERY COMMAND / FILTER DIALOG Use attribute aliases when performing attribute queries

Now supports use of attribute aliases for fields of feature classes that are served through a proxy data server.

Now encloses aliased attribute names in the SQL string using the delimiters “{#” and “#}”. This permits GeoMedia to rigorously replace the aliased names with the actual names when submitting the filter in a query. A user who manually enters SQL in the dialog must also enclose aliased attribute names with these delimiters.

FUNCTIONAL ATTRIBUTES DIALOG Use attribute aliases when defining functional attributes

Now supports use of attribute aliases for fields of feature classes that are served through a proxy data server.

Now encloses aliased attribute names in the expression string using the delimiters “{#” and “#}”. This permits GeoMedia to rigorously replace the aliased names with the actual names when the expression is evaluated. A

New Technology

October 19, 2016 19

user who manually enters the expression in the dialog must also enclose aliased attribute names with these delimiters.

MAP DISPLAY

PICKQUICKDIALOG API FOR MICROSOFT.NET CLIENTS Use native .NET API for the PickQuickDialog

A new PickQuickDialog API is now available. This is written with WPF, provides smoother usage from a .NET client, and supports RTL (right-to-left) languages as well.

All GeoMedia Desktop users experience this new dialog as part of the Select Tool and Measure Angle commands of the map window.


THEMATIC LEGEND ENTRIES Use attribute aliases when building thematic maps

UniqueValueLegendEntry and RangeLegendEntry now support the use of attribute aliases for fields of feature classes and queries.

PICKLIST FOR UNIQUE VALUE LEGEND ENTRY Automatically leverage picklists in thematic maps

The Unique Value Legend Entry control now uses descriptions from the Picklist table in the Label column if the selected attribute has a Picklist table defined.


DISPLAY LOCATION DOCKABLE CONTROL Observe a new look for named locations

The drop-down list of named locations is now grouped by expander controls rather than horizontal divider lines.


New Technology

October 19, 2016 20

LABELING

PERFORMANCE See map labels faster

The display performance of dynamic labels is greatly improved.

DATA CAPTURE

GPS TRACKING COMMAND Work with more GPS devices

Can now read data from some built-in GPS sensors.

Perform GPS tracking on Windows 8.1

Now works on Windows 8.1 and later, with restrictions on some devices (no satellite tracking information displayed, no NMEA log file).

SPLIT FEATURE COMMAND Split features with Z-aware logic

Has improved handling of Z values when splitting area features.

DATA MANAGEMENT

OUTPUT TO OFFLINE COMMAND Output data to an offline database for editing disconnected from the network

This new command lets you choose data from an Oracle or Oracle LTT connection that will be output to an offline read-write warehouse connection such as SQL Server Express. This happens so you can edit in an offline

New Technology

October 19, 2016 21

environment and then post back to the enterprise connection via the Post from Offline command. The offline database may be Access, SQL Server, SQL Server Express, or PostGIS.

POST FROM OFFLINE COMMAND Post data from an offline database which has been edited while disconnected from the network

This new command provides the ability to post back to the source Oracle or Oracle LTT connection those changes made to the offline data created by the Output to Offline command. Only inserted, updated, and deleted features are posted.

New Technology

October 19, 2016 22

DATA INTEGRATION AND VALIDATION

CREATE CONFLATION LINKS COMMAND Iteratively create conflation links at increasing distances

Now automatically creates links for all features. A new option Include All Features, when selected, automatically increases the buffer distance as specified, and decreases the certainty value for each subsequent iteration. It therefore progressively links and includes, until all the features have been linked or when the specified number of iterations has completed.

New Technology

October 19, 2016 23

AUTO ADJUST FEATURES COMMAND Automatically adjust features based on an offset to a centerline undergoing conflation

This new command automatically adjusts assets such as buildings, junction boxes, service locations etc., which have been previously located by measuring their offset to a centerline. It establishes the relationship between linked assets and their reference centerlines with the help of the Create Conflation Links command. This established relationship forms the Primary link set. Similarly the relationships that exist between the old centerlines and the newly-conflated centerlines are established as Secondary link sets. Finally the assets are adjusted and

New Technology

October 19, 2016 24

aligned to the new centerlines based on the offset/orientation that is extracted from the relationship between the Primary link sets and Secondary link sets.

QUERY CONNECTIVITY COMMAND Simply find anomalies in connectivity between two sets of features

This command is reintroduced into the product from prior releases, in response to customer requests. It was formerly named Validate Connectivity. It finds conditions caused by inaccurate digitizing, such as undershoots and

New Technology

October 19, 2016 25

overshoots. This command takes one or two feature classes or queries as input and creates a new query containing the resulting anomalies as output, based on the validating conditions that you select.

FIX CONNECTIVITY COMMAND Simply fix anomalies in connectivity between two sets of features

This command is reintroduced into the product from prior releases, in response to customer requests. It automatically corrects connectivity problems within and between feature classes in conjunction with Query

New Technology

October 19, 2016 26

Connectivity. The following problems may be fixed with this command: overshoots trimmed, undershoots extended, crossing lines broken, and vertices inserted into crossing lines.

DATA WINDOW

DATAVIEW CONTROL Achieve deeper customization with new DataView API

Now provides an event BeforeSetRecordset, which is fired when the SetRecordset method is called, just before the recordset is set on the control. The event handler receives the input recordset and may optionally modify or replace the recordset before passing it back to the DataView control.

LAYOUT WINDOW

EXPORT LAYOUT COMMAND Export more formats from the layout window

This command now supports export of two new raster formats (PNG and JPEG 2000). It also supports a new compression technique (LZ77) for TIFF and GeoTIFF formats.


New Technology

October 19, 2016 27

CADASTRAL

COMMAND RENAMING Enjoy more consistent naming of cadastral commands

The “Set Master Connection” command has been renamed to “Set Cadastral Connection”. When a Cadastral Connection is defined, the Cadastral tab appears on the Ribbon.

SUPPORT FOR SQL SERVER SPATIAL Use SQL Server Spatial throughout GeoMedia

All cadastral commands are enhanced to work with SQL Server Spatial data server.

LIBRARIES

SUPPORT FOR SQL SERVER SPATIAL READ-WRITE DATA SERVER Use SQL Server Spatial throughout GeoMedia

The Library Connection dialog and Library Organizer command are enhanced to support SQL Server Spatial Read-Write data server. It is now possible to use a SQL Server Spatial database as a library.

New Technology

October 19, 2016 28

New Technology

October 19, 2016 29

SUPPORT FOR POSTGIS READ-WRITE DATA SERVER Use PostgreSQL / PostGIS throughout GeoMedia

The Library Connection dialog and Library Organizer command are enhanced to support PostGIS Read-Write data server. It is now possible to use a PostGIS database as a library.

FEATURE CACHING

INDEXED FEATURE CACHE (IFC) FILES Expanded capability for IFC files

The format of indexed feature cache (IFC) files has been improved to include support for indexes on memo field types. Lack of support for indexing of memo fields manifested itself in the context of attribute queries and thematic legend entries built on memo fields.


New Technology

October 19, 2016 30

UTILITIES

BATCH PLOTTING Export more formats from batch plotting

This utility now supports output of two new raster formats (PNG and JPEG 2000). It also supports a new compression technique (LZ77) for TIFF and GeoTIFF formats. This change was introduced with GeoMedia 15.1.

Use attribute aliases in batch plotting

Now supports use of attribute aliases for fields of feature classes.

DATABASE UTILITIES Take advantage of more Oracle data types

Now supports NVARCHAR2, NCHAR, and NCLOB data types for Oracle.

Use PostgreSQL / PostGIS throughout GeoMedia

Now supports the PostGIS data server.

DEFINE SYMBOL FILE Use a wider range of AutoCAD symbols

New Technology

October 19, 2016 31

Now supports DWG files from more recent versions of AutoCAD.

SCHEMA REMODELER Use PostgreSQL / PostGIS and SQL Server Spatial throughout GeoMedia

Now supports SQL Server Spatial data server and PostGIS data server.

New Technology

October 19, 2016 32

SPATIAL MODEL EDITOR Perform spatial modelling on a GeoMedia Desktop seat

Use this new utility to create, edit, and run spatial models.

POINT CLOUD INTEGRATION In GeoMedia 3D 2016, you can now easily connect to point cloud data sources stored on a local or network hard drives, web servers, or ERDAS APOLLO Catalog servers and render these rich data sources regardless of their size directly within the 3D window.

With point cloud integration you can now leverage your accurate point cloud datasets in tandem with GIS operations, all fused directly in context with 3D models, imagery, and GIS data.

Use this new functionality to verify your GIS data against the point cloud data in order to confirm accuracy or make adjustments to your GIS database. Simply use point clouds as another source of geospatial information within GeoMedia Desktop.

The point cloud integration is provided via three new commands: Construct Hexagon Point Clouds, Insert Hexagon Point Clouds, and Query Hexagon Point Clouds.

New Technology

October 19, 2016 33

The Construct Hexagon Point Clouds command creates Hexagon Point Cloud (HPC) files from one or more input point cloud data files. Once created, you can add and display the HPC files in the 3D map window using the Insert Hexagon Point Clouds command. Points can then be stylized using a wide array of new point cloud style properties. With these properties, you can, for example, apply color sequences, display by classification, and change the point symbol used to represent each point on screen.

The Query Hexagon Point Clouds command allows you to retrieve attribute information from individual points within HPC point cloud files that have been displayed in the 3D map window. This attribute information displays on the Query Point Cloud modeless dialog.

VIEWSHED ANALYSIS In GeoMedia 3D 2016, viewshed features are represented by 3D polygons. These 3D polygons depict the visible areas from a specific location. Similar to other viewshed technologies, the Insert Viewshed command in GeoMedia 3D uses a number of inputs such as horizontal and vertical fields of view, pitch angle, viewing distance, and viewer height to guide the line-of-sight/ray tracing process. However, the Insert Viewshed command in GeoMedia 3D, unlike other viewshed approaches, takes 3D objects such as building models, feature models, and point clouds into consideration when calculating the visible areas. Given this, the Insert Viewshed command can

produce viewshed features that accurately reflect the real world.

Viewshed analysis has a wide variety of applications in security, government, infrastructure, resource development, and tourism. One particular area where viewshed analysis has been used extensively is in determining where to locate communication towers. Another way viewshed analysis can be used is to estimate the impact of the addition of a large building into an existing cityscape. This viewshed analysis would show all the areas from which the building could be seen, as well as any views that would be obscured.

ENVIRONMENTAL EFFECTS The ability to integrate visual effects, such as shadows and fog, within a 3D environment can prove extremely useful. However, with GeoMedia 3D 2016 you can now add even more realism to your 3D worlds using effects such as Rain, Snow, Wind, and Sky conditions.

These new effects can create immersive environments for peer or group review. They can also be paired with the improved flight path system to create fly-through’s and virtual tours to help advisory committees better understand planning concepts.

To accommodate the above enhancements, the 3D Effects tab has been modified to house all of this new

functionality.

As illustrated in the graphic above, the 3D Effects tab contains new commands that you can use to further control visualization variables within the 3D map window.

The Environment group, in addition to Fog and Oceans, now includes a collection of commands to control Rain and Snow conditions. Using these commands, you can dynamically add rain and snow to your 3D environment.

New Technology

October 19, 2016 34

The Wind group is completely new. This group contains a collection of commands that control the behavior of wind within the 3D map window. These commands are used to set the direction and speed of the wind effect. It should be noted that wind influences the direction of snow fall, rain fall, and cloud movement in the sky.

The Sky group has been expanded to include Color (options include: Spring, Summer, Fall, Winter, Winter Grey, and Custom colors), Texture (options include: None, Light, and Heavy), and Clouds (options include Static and Dynamic: Partial Coverage and Dynamic: Full Coverage).

3D PREFERENCES A wide variety of new preferences have been added to GeoMedia 3D and given this, the 3D Options dialog has been updated to show these new commands. The 3D Options dialog now has seven tabs (General, Effects, Navigation, Overlays, Editing, Analysis, and Advanced) instead of five.

The General tab contains options related to base content files and a variety of display settings.

The Effects tab contains options for illumination (lighting), environment (weather conditions), and time zone settings.

The Navigation tab contains a collection of options that control the default flight path settings and the settings for navigating within the 3D map window. This tab has been updated and now includes a collection of new navigation modes (Drag, Slide, Tilt and Turn) and a number of controls to modify keyboard and mouse speeds, the minimum navigation altitude, and the location of the surface for underground.

The Overlays tab contains a collection of options that control the display of graphics and other elements related to flight and camera positions. These contextual elements allow you to monitor your navigation without having to take your eyes off the 3D map window.

The Editing tab, which is new to GeoMedia 3D, contains options related to 3D locate, placement, editing, and measurement settings. With GeoMedia 3D 2016, we have greatly enhanced the manner in which you can interact with 3D objects. Most notably, we have improved the intuitiveness and fidelity of 3D selections and editing.

The Analysis tab, which is new to GeoMedia 3D, contains options related to the Insert Viewshed command.

The Advanced tab contains options to control the color balance, terrain quality, and other factors affecting the 3D

map window appearance.

IMAGE LIGHT TABLE PLUS 2016 Image Light Table Plus 2016 v23.0.4.46 has been integrated with this release of GeoMedia Image Professional. Image Light Table Plus 2016 includes the following new and enhanced features:

64-bit Application

Image Light Table Plus 2016 is now a 64-bit application for increased memory capacity and performance.

New Radar/SAR Improvements

Mensurate feature height from layover

Document fixed Look Direction annotation

Radar Tab and status bar support in Geo Mosaic and Compare Documents

New Technology

October 19, 2016 35

SICD data format support

Persist SAR metadata when saving to NITF

New Geo Accuracy Improvements

Mensurate angle between two line segments

EGM 2008 1x1 minute GEOID grid support

NITF-embedded elevation data support

New Product Generation Improvements

Document-fixed Up is Up annotation

Document-fixed Look Direction annotation

Direct access to Line Style on Format Tab

Translucent fill support for polygons

Display and Performance Improvements

BIIF data format support

ECWP stream client support

JPIP stream client support

Open file over HTTP support

Large vector graphic improvements

High resolution display improvements

Usability

User customizable Ribbon Tabs and Groups

Pan Window Stay on Top option

Quick Access Toolbar improvements

Layer selection indicator in explorer when image is selected

Multi-image View Group configuration

Close all documents to Right/Left option

Export to PowerPoint improvements

Resizable dialog size persistence

Zoom factor displayed on Status Bar

Remember and Apply annotation attributes

Optionally create reduced resolutions during save

System Requirements

October 19, 2016 36

SYSTEM REQUIREMENTS

Computer/ Processor Minimum 4 core Intel 64 or equivalent, 8 core or more recommended

Memory (RAM) Minimum 4 GB (dual channel systems) or 6 GB (triple channel systems) minimum, 8 GB (dual channel systems) or 12 GB (triple channel systems) or more recommended

Disk Space

4 GB for software

Data storage requirements vary by mapping project1

Graphics Boards

Minimum display resolution 1600 x 1200,

LCD <= 5 ms, higher refresh rate recommended

Dual monitors recommended

Graphics cards with 1 or 2 GB dedicated video memory, NVIDIA recommended

Graphics cards for stereo mode – Stereo capable NVIDIA™ Quadro

Peripherals

Software security (Intergraph Licensing 11.13.2) requires one of the following:

Ethernet card

One USB port for hardware key

Optional Installation:

Logitech® Dual-Action® Controller for GeoMedia 3D component of Image Scout 3D

Operating Systems2,3

Windows® 7 SP1 or higher, Professional and Ultimate (64-bit)

Windows® 8.1, Professional and Enterprise (64-bit)

Windows® 10, Professional and Enterprise (64-bit)

System Dependencies

Microsoft® .NET Framework 4.5

Microsoft® .NET Framework 3.5 4,5

Microsoft Primary Interoperability Assemblies 2005 4,6

Database Server Engines

Oracle® Server 11g, 32-bit and 64-bit

Oracle Express 11g

October 19, 2016 37

Oracle® Server 12.1, 64-bit

SQL Server® 2012, 64-bit

SQL Server Express 2012

SQL Server 2014, 64-bit

SQL Server 2014 Express

SQL Server 2016, 64-bit

SQL Server 2016 Express

PostgreSQL 9.3 with PostGIS 2.1

PostgreSQL 9.4 with PostGIS 2.2

Database Client Engines

Oracle Client 11g, 32-bit

Oracle Client 12.1, 32-bit

SYSTEM REQUIREMENTS NOTES 1 Disk I/O is usually the slowest task in geospatial data processing. Faster hard disks improve productivity. Reading data from one disk, writing temporary data to a second disk, and writing data to a third disk improves performance. Disk arrays improve productivity but some RAID options slow performance. Network disk drives are subject to network limitations.

2 Windows 7 32-bit, Windows 8 32-bit, Windows 8.1 32-bit and Windows 10 32-bit are no longer supported.

3 GeoMedia runs on 64-bit systems in 32-bit emulation mode.

4 Required for GeoMedia 3D only.

5 For information on installing .NET Framework 3.5 for Windows 8.1 and 10, see the Installing .NET Framework 3.5 (Windows 8.1 and 10 only) section in the GeoMedia 3D Installation Guide.

6 To install, right-click on <root-media>\Repository\Image Scout\GM 3D\Prerequisites\vs_piaredist.exe and select Run as administrator.

ISSUES RESOLVED

GEOMEDIA PROFESSIONAL CR # SUMMARY Description / How to Reproduce

Issues Resolved

October 19, 2016 38

1-9AF33V

GeoMedia crashes closing geoworkspace after closing overview window.

Steps to Reproduce:

1. Invoke GeoMedia Professional. Create a blank Geoworkspace.

2. Make Access R/W connection to USSampleData.

3. Add Cities LE to map window.

4. Name the legend as legend1.

5. Invoke Overview window and add legend1 to it.

6. Now on overview window using legend add cities.

7. Save the workspace as TEST1.

8. Now close geoworkspace using File>Close. (In the same instance of GeoMedia)

9. Open workspace from recent documents.

10. Observe that workspace opens and overview window is blank.

11. Now delete this overview window using cross mark.

Click on File>Close geoworkspace. Click on No button on message dialog. Observe that application crashes.

1-9B14LP

Error followed by crash on performing Insert Traverse command with category features on German OS.

Steps to Reproduce:

1. Invoke GeoMedia Professional.

2. Create a blank Geoworkspace.

3. Make Access R/W connection to USSampleData.mdb delivered with product.(IFC ON)

4. Add all the features to categories.

5. Add all the features from categories to map window.

6. Invoke Insert Traverse command. Select States (Categories) as Primary feature and Rivers (Categories) as component feature. Using Use Map and Add to Grid options place a point followed by two lines. Click on Apply button. Message displays that feature has to be closed. Click on Ok button. Click on Ok button on Properties dialog.

Observation: Observe that message like “invalid argument encountered” appears. From then you could not proceed further with any of the commands. Try to exit clicking on Exit button from application menu. Observe that GeoMedia Professional crashes.

1-9BHFUB

FGDB Read Only shows English strings on New connection dialog in Japanese version.

Steps to reproduce:

1. Invoke Japanese version of GeoMedia Professional.

2. Invoke New connection dialog.

Observation: FGDB Read Write is displayed in Japanese language; however, Read Only is still shown in English.

Issues Resolved

October 19, 2016 39

1-9BHG48

Export to GML the dialog size is fixed on size 8 dialog. Truncated the dialog items at right side

Export to GML The dialog size is fixed on size 8 dialog. On size 9 dialogs, the right side of the dialog is truncated. Resizing subroutine is using the numerical value to adjust the position of items. Therefore the items on Size 9 dialog (Japanese and Chinese) are not correctly positioned and truncated at right side and bottom.

1-9BOVUL

GeoMedia crashes exiting the application from the task bar with options dialog in invoked state.

GeoMedia crashes while exiting the application from the task bar with options dialog in invoked state. Steps to reproduce: Invoke GeoMedia. Select Blank Geoworkspace radio button. Open a Geoworkspace. Select the Insert feature. Select options dialog from the vector control. Exit the Application from the Task bar. Observations: --------------------------- PMiscCmd --------------------------- Error exiting application.Source:GMCmdSuptDescription:Method '~' of object '~' failed --------------------------- OK --------------------------- --------------------------- PProCtrl --------------------------- Run-time error '0' --------------------------- OK --------------------------- Click Ok on the dialog GeoMedia Crashes.

1-9BOVZX

GeoMedia crashes exiting the application with Coordinate System dialog in invoked state.

GeoMedia crashes exiting the application with Coordinate System dialog in invoked state. Steps to reproduce:

1. Invoke GeoMedia.

2. Select Blank Geoworkspace radio button.

3. Open a Geoworkspace.

4. Select the Insert feature.

5. Invoke the coordinate system from the vector control.

6. Exit the application from the task bar.

Observations: GeoMedia.exe still runs exit the application from the task bar.

1-9BOW1Y

GeoMedia.exe still runs after exiting the application with options dialog in invoked state.

GeoMedia.exe still runs exiting the application with the options dialog in invoked state from Queued Edit control dialog. Steps to reproduce:

1. Invoke GeoMedia.

2. Select Blank Geoworkspace radio button.

3. Open a Geoworkspace.

4. Select the features check box.

5. Click ok button.

6. Select options dialog from the Queued Edit control.

7. Exit the application from the task bar.

Observations: GeoMedia .exe is still running in the task manager after exiting the application.

1-9C00AU ShapeFile Data Server: Attributes of Type Double Rounded or

User exports GeoMedia GeoWorkSpace query containing double values then serves the data back into GeoMedia using Shape File data server. The field is correctly served back as double, but the values are

Issues Resolved

October 19, 2016 40

Truncated As If Integer.

all truncated to 0 digits of precision (value 77.1234 becomes 77); the values are rounded to zero decimal places.

Scope: Problem is known to occur when the GeoMedia user exports a merge query that contains a period <"."> Queries containing dot (".") as part of the query name is very common for Oracle users where the connection name and thus query names are prefixed by the schema owner. Example query name: Merge of OM_ALABAMA.ANTENNAS If the user selects the query name "Merge of OM_ALABAMA.ANTENNAS", the Export dialog automatically renames (possibly by design) the output shapefile to: "ANTENNAS”. Such renamed merge queries will have truncated values for fields of type Double.

Workflow:

1. Open GeoWorkSpace

2. Query "Q2 Merged.Institutions" should be displayed on the map. Notice the double values for the latitude and longitude attribute fields.

3. Use Manage Data tap, Export to > Export to Shapefile to export the Q2 Merge query, using the default output shapefile name "Institutions.SHP"

Use the Manage Data > Warehouse > New Connection to connect to exported shapefiles from step 3. Review attributes of the shapefile data and notice how the double values are rounded or truncated.

1-961T3I

GeoMedia.exe is still running exiting the application from task bar with Save As dialog in invoked.

GeoMedia.exe is still running after exiting the application from the task bar with Save As Dialog in invoked state of Edge Match rules dialog. Steps to reproduce: Pin GeoMedia to task bar.

1. Invoke GeoMedia

2. Select Blank geoworkspace.

3. Open a workspace

4. Select Edge match rules from the Edge Match frame from Tool box.

5. Click Add/Modify button from the Manage Edge Match Rules dialog.

6. Close the Add/Modify Edge match class matches dialog.

7. Open the Save As dialog

8. Exit the Application from the task bar.

1-9625CJ

GeoMedia.exe is still running while inserting the feature with properties dialog in invoked state.

GeoMedia.exe is still running while inserting the feature with properties dialog in invoked state while exiting the application from the task bar.

1. Invoke GeoMedia

2. Select Blank Geoworkspace.

3. open a workspace

4. Select Insert feature from the Vector Tab.

5. End the feature.

Exit GeoMedia from the task bar.

Issues Resolved

October 19, 2016 41

1-968SJL

Connection properties dialog - enable feature caching checkbox state not persisted.

1. Open GeoMedia.

2. Connect to USSampleData with caching off and add counties feature class to map window.

3. Verify cache is not created.

4. Open Warehouse Connections command.

5. Click properties button.

6. Check the enable feature caching checkbox.

7. A dialog appears asking if you want to create the cache. Press create/refresh cache (see cache is created).

8. Press Cancel.

Open Properties dialog to see that enable feature caching checkbox is checked. This should not happen.

1-96FA9R

Layout > Print > Plot of WMS fails.

1. Steps to reproduce:

2. Open provided GeoWorkspace and zoom in to scale 1:50000.

3. Set nominal map scale to 1:50,000.

4. Open layout window.

5. Print to printer.

Result: Blank paper. No error message.

1-96ZL03

Aggregation Crash Using Within Distance Spatial Operator - Data Specific.

Customer supplied data demonstrates a crash of GeoMedia application without chance to save when using Aggregation within distance operator. The problem appears to be data specific. Workflow:

1. Save .zip to C:\Warehouses and extract to here which should create folder 1-96ZL03.

2. Open Testing1.gws

3. Use Analysis > Queries to Display previously saved Aggregation query.

4. Observation: GeoMedia terminates without opportunity to save. Aggregation Query Information: Aggregation where summary feature=Leitung and detail feature=gebaeude_koeln using within distance of 10m to get the output from: MAX(Anzahlvonzahpunkt)

12. Other data observations: There are a few errors found in the geometry when using Validate Geometry however, even if we remove these records entirely, the crash persists.

1-97CCGB

Geometry validation gives inappropriate validation errors which was not seen

I wanted to use this command to see if the data referenced in a particular CR is clean and found some errors. Steps to reproduce:

1) Invoke GeoMedia and connect to attached test data (WFS_Test.mdb)

Issues Resolved

October 19, 2016 42

in 6.1.11.13 version.

2) Select Toolbox>Validate Geometry and select feature class GRUNDNUTZUNG_WALD and click [OK] on the Validate Geometry dialog.

3) Check that 3973 validation failures are listed in the Queue of Anomalies window out of which there are 3871 anomalies with Description "Invalid Geometry Component".

4) Observe each of these validation anomalies to understand that these validation failures are inappropriate.

Repeat the above workflow with 6.1.11.13 and check that none of these geometries are mentioned as anomalies. This seems to be regression after 6.1.11.13

1-97DBUN

Spatial intersection throws a Method of object failed error with invalid query.

Spatial intersection throws a Method of object failed error and does not show an error message with invalid query to oracle connection. Steps to reproduce:

1. Invoke GeoMedia

2. Make an oracle connection from Ware house from Manage Tab.

3. Add the legend entries and click OK.

4. Select Spatial intersection from Analysis Tab.

5. Select a feature From the Features in combo box and select filter button and select > symbol and click ok button. (Note: an error message is not popped up even though it is an invalid query).

6. Select a feature from the other Features in combo box.

7. Select filter button, select > symbol and click ok button.(an error message is not popped up even though it is an invalid query).

8. Click ok button.

Observations: Method of object failed. An error message is not popped up even though it is an invalid query. This behaviour is not observed with Access connection as a warning message pops up.

1-9910J8

Problems with Shapefile export from PostGIS database displaying in GWS.

After exporting to shape files from a PostGIS database connection and then making an ArcView connection to the exported files, the user is unable to display the ArcView features in the Map window. Workflow:

1. Open a blank .gws and make an ArcView connection to the exported files.

Click the Add legend entry and notice no features are available to choose from. The export appears to work fine, but the data cannot be displayed.

1-8OH60M

Recordset access is causing data server to issue selects to database that is causing a performance hit.

This was filed against the Oracle R/W data server when observing the behaviour of the Toggle Dynamic Label command. The recordset access pattern in the Toggle Dynamic workflow is causing the data server to issue selects to the database for each geometry row resulting in a performance hit.

1-8P174L Invalid geometry types enabled in

Invalid geometry types enabled in Continue Geometry dockable control while trying to do Continue Geometry on a Spatial Query. Steps to reproduce:

Issues Resolved

October 19, 2016 43

Continue Geometry dockable control.

1.Invoke GeoMedia Essentials and make an Access Connection to USSampleData.mdb available with the product

2.Invoke Analysis > Spatial Query

3.In the ‘Select features in’ combo-box, select Rivers FC

4.Select ‘are entirely contained by’ operator

5.Select ‘States’ from the Features in combo-box

6. Dismiss the Spatial Query dialog by clicking on OK.

7. Select a River from the Map Window that is returned from the Query.

8. Now click on Vector > Continue Geometry

Observe that in the Continue Geometry dockable control all geometry types are enabled (Point, Area & Line instead of just Line). However, on clicking on the invalid geometry (Point and Area), and trying to continue geometry, an error dialog with caption ‘GeoMedia’ appears, with the following content: GeoMedia Invalid geometry detected. Operation aborted. -2147219944 – GField::Value

1-8SSXEF

GeoMedia Professional crashes for Validate Geometry on Searched item in select set.

GeoMedia Professional crashes for Validate Geometry on Searched item in select set.

• Invoke GeoMedia Professional and create an access warehouse connection to USSampledata.mdb.

• Select Search command and select States feature class.

• Type 1 and click Search.

• Invoke Validate Geometry command.

• ON input tab, Select "GMSearchQueue" under SelectSet and Anomalies tab, select all check-boxes.

• Click OK.

The following error is displayed. --------------------------- Queued Edit Control --------------------------- The connection associated with this queue is closed. The queue cannot be viewed. --------------------------- OK --------------------------- Application crashes.

1-8U3XM5

Warehouse caching location not validated by GeoMedia during clear/refresh/enable stages.

Steps to Reproduce:

1. Create a folder (in say C:\Temp) for the purpose of holding warehouse cache files

2. Invoke GeoMedia with a blank new geoworkspace and using 'Options' change the Warehouse Cache Files location to the folder created above

3. Close GeoMedia without saving GWS

4. Delete the folder manually

5. Reopen GeoMedia and try clearing/refreshing/enabling cache. No errors pop up stating non-existing folder

6. However if you connect to a warehouse and add legend entries, the folder and relevant .ifc files get created.

Issues Resolved

October 19, 2016 44

While the above situation is fairly OK, in case of XenApp if you modify the caching location to one on your local machine (it looks like \\client\c$\temp\caches) and later invoke GeoMedia from the server (not through web browser at client end), the caching path does not change (not expected either). However, in addition to above issue, enabling caching/adding legend entries do not result in cache creation. Hence, the issue's impact is higher in XenApp than in normal GeoMedia operations.

1-8VC1RJ

Unable to Generate Connectivity Queries in GeoMedia 2014 and GM 2015.

Validate Connectivity in GeoMedia Pro no longer supports output to query.

a) Queries can be output and/or exported to other required formats

b) Queries are built once and preserved as part of the GeoWorkSpace:

1. Automatically updating when underlying data changes.

2. User does NOT have to recall correct settings (saved as part of the query)

Queries can be displayed outside the queued edit system as a whole making it easier to visualize the location of problems. GeoMedia Pro's validate connectivity command is used by many customers to generate queries that can be routinely checked. If the query contains connectivity errors the query can then be exported to shape file, Oracle or the appropriate format for easy shipment to other (non-GeoMedia) depts. so the errors can be corrected in the source format/data. This cannot be done in GeoMedia 2014 with the Fusion based static queues.

1-8DRJWH

'Method '~' of object '~' failed' error message pops up on giving invalid filter in Spatial Query.

'Method '~' of object '~' failed' error message pops up on giving invalid filter in Spatial Query Workflow to reproduce.

1. Invoke GM Pro and open a new geoworkspace.

2. Make an Access connection to USSampleData.mdb.

3. Invoke Spatial Query dialog and select Rivers feature in 'Select features in:'

4. Click on Filter button to display filter dialog.

5. In Filter Dialog, give an invalid expression 'ID >=' and click Ok.

6. In 'Features in' combobox, select Interstates feature.

7. Click OK by accepting all defaults.

Observe that error message pops up saying ' Method '~' of object '~' failed. ' The same issue is observed with Spatial Intersection and Spatial Difference commands. To reproduce the issue, repeat the same workflow by invoking Spatial Intersection and Spatial Difference commands.

1-8WF6AO

Add WMS Legend Entry calculates minimal bounding box of layer intersection, not union.

The "Add WMS Legend Entry" command calculates intersection from all bounding boxes selected to display. As a result, if there are two layers with disjunct (non-intersecting) bounding boxes, nothing is displayed and the request is not sent to the server. The command must calculate minimal rectangle covering all bounding boxes, and request this coverage. The side effects of the current implementation are that if one of the bounding boxes is out of the map extent, no request is sent to the server although other layers might be visible. To reproduce the issue:

1 - Clear or create GDOWMS.log file in your personal Temp folder (..\AppData\Local\Temp).

2 - Connect to the WMS site and run Raster > Image Footprints for two layers: Jaskyna and Plavebna_brana.

Issues Resolved

October 19, 2016 45

3 - Pan to the left so that the image footprint for Plavebna_brana completely disappears from the map.

4 - Run Add WMS Legend Entry with these two layers together.

5 - Check the GDOWMS.log, you can clearly see that no GetMap request has been sent so far.

6 - Pan back so that both image footprints are completely visible in the map view.

7 - Check the GDOWMS.log, the GetMap request has been sent now.

8 - Move mouse pointer inside the intersection of the two image footprints.

Even if you can see no data in the map, you can clearly see that the area requested for the WMS legend entry is the intersection of the two bounding boxes, not the bounding box of the union of the two.

1-8WWKHE

Fails to display feature class if index contains XLO,YLO, XHI, YHI and any other column.

If the customer creates a non clustered index that contains the XLO,XHI,YLO,YHI and includes any other column from the table, GeoMedia will fail to display the feature class and will return the error: Index, Geometry_XLO, not found for feature classes containing a large number of rows. Building optimal indexes is very important and GMP should not fail on any index definition.

1-8XU0Z0

Selecting numeric values from a picklist in update attributes command causes an error.

When trying to update a numeric value from a picklist in the update attributes command, the following error is given: There are no valid value(s)/expression(s) defined. The field is defined as a number in Oracle. An entry in gpicklist exists to make this value appear in a list. This issue does not exist when selecting string values from the picklist. Workflow to reproduce:

1. Open geoworkspace and connect to Oracle database that was used for import above.

2. Open data window for GDOSYS.GPICKLISTS.

3. Create picklist by inputting following: featurename = ROADS fieldname = ESZL picklisttablename = ROAD_POLY valuefieldname = ID1 descriptionfieldname = ID1 filterclause = 'leave blank'.

4. Vector Tab>Update Attributes.

5. Select ROADS and choose attribute 'ESZL'.

6. From the picklist select any value.

Once chosen the error will display. There are no valid value(s)/expression(s) defined. This is despite the attribute being a long integer and should be updateable with this value. Repeating the workflow using a STRING value into a text field and the error is not seen.

1-8XXYNP

Customizing the Quick Access Toolbar(QAT) is not saved after a machine reboot.

Customizing the Quick Access Toolbar (QAT) menu is not saved if the machine is rebooted. If a geoworkspace (.gws) QAT is setup with various commands and saved in the .gws and the machine is rebooted, the saved .gws when reopened does not show the saved QAT. In fact it adds multiple commands to the QAT.

1-8Y4J0V

Ribbon bar disappears on opening saved gws repeatedly.

Steps to reproduce:

1. Invoke GM

2. Open saved GWS.

Issues Resolved

October 19, 2016 46

3. Repeat step 2 multiple times (say 8-10)

4. On the message dialog saying 'Do you wish to save?' Click yes or no.

5. Error message is displayed and the ribbon bar disappears --------------------------- GeoMedia Desktop --------------------------- Encountered an improper argument. --------------------------- OK --------------------------- .

1-8ZG7HX

Diacritic Characters in Title name are not retained for Legend Entry Name in GM GUI w/WMS DS.

For this particular WMS, the title names contain Czech Diacrtic characters. The customer has had to remove the diacritic characters in order to get their WMS Service to work.

1-8ZGFBQ

Cannot display WMS Layer when name contains Diacritic Character.

Using the WMS Dataserver with a connection to a WMS Service, -- when the layer name contains a Diacritic character, the GM GUI gives error and will not display the layer.

1-9094B3

Thematic classification displays Memo datatype error "This datatype could not be indexed".

Thematic classification displays Memo datatype error "This datatype could not be indexed". To reproduce:

1. Open the attached USSampleData.gws and USSampleData.mdb.

2. Create a unique thematic legend on the states feature using the attribute1 attribute which is memo type.

3. Error appears "This datatype could not be indexed".

4. Click Ok.

5. States Thematic legend entry is added, but doesn't display.

6. Set the States Thematic legend entry to "Display on" and the thematic displays in the map window.

It appears "Display by scale" doesn't work initially, but works after changing from "Display on" to "Display by scale". Help states Memo is a valid data type for range and unique thematic legends.

1-7NJGUW

GeoMedia Query using TRUNC operator on Oracle ‘Date’ field with Spatial Filter.

When a GeoMedia query is created on an Oracle database field that is type Date and the query contains the TRUNC operator, the query will display successfully without a Spatial Filter applied. When a Spatial Filter is applied over the query results, an error messages will display. Once the error message displays, the query cannot be displayed again. The query can be recovered by removing the Spatial Filter, deleting the query, and then recreate the query without a Spatial Filter applied. The query with the TRUNC operator will display without a spatial filter but not when a spatial filter is applied. Steps to recreate the issue: Note: Use the warehouse access database, USSampleDataForDRW.mdb

1. Start GeoMedia Professional

2. Make an Access connection: USSampleDataForDRW.mdb

3. Make a Read/Write connection to any Oracle database

Issues Resolved

October 19, 2016 47

4. Run Warehouses > Output to Feature Classes. Select Source features to output: USSample Dataset for DRW > STATES. Select Target connection: Oracle connection. Click the Advanced tab and use Target Feature Class: Oracle:STATES. Click the OK button to produce the output.

5. Create a query using the TRUNC operator in the query on the Oracle: STATES table. You can copy/paste the example query below into the query Filter box to create the query. Example: Query name: TRUNC STATE DATE STATE_NAME LIKE 'M%' AND TRUNC(STATE_DATE) > '01-JAN-1818' Note: The query using the TRUNC operator will display in the map window.

6. Place a Spatial filter anywhere in the map window over the Oracle: STATES features. RESULTS: An error message will display. “GeoMedia Professional: An error was encountered loading data for TRUNC STATE_DATE legend entry. Do you want to continue loading remaining legend entries?”

7. Delete the query from the map legend

8. Select Legend > Add legend entry

9. Select the query TRUNC STATE DATE to add it to the map legend. RESULTS: A message will display. “Error creating legend entry for TRUNC...

1-82XDCY

Feature Class Definition - multiple edits to SQL Server feature causes 'Out of Memory' error.

Using Feature Class Definition to edit lots of attributes (names and types) simultaneously for a SQL Server feature (without saving the changes with the OK button between edits) will result in an ‘Out Of Memory’ error when you click OK to save the edits. To see the problem use the steps below.

1. Create a new GeoWorkspace and make an SQL Read-Write data server connection to an existing SQL Server database. For my tests I connected to the USA database.

2. Select Feature Class Definition and use the New button to create a new feature class (you can leave the default name of FeatureClass1 and type as Point). Select the Attributes tab and click in each row in the grid (until you get to the 10th row) so that you have created 10 new attributes named Attribute1 through Attribute 10 all of type Text. Click OK to save the new feature class. When the prompt appears stating “A feature class must have a primary key attribute. Do you want GeoMedia to generate a primary key of Autonumber data type?” Select ‘Yes’.

3. Now that you are on the main Feature Class Definition dialog again click the Edit button. The ‘FeatureClass1’ feature that you just created should still be highlighted so you will be editing that feature class. Now select the Attributes tab. On the Attributes tab change the data type for each of the Attributes (1 through 10) from Text to another Type (choosing a different type for each attribute if possible). Now change the name of each of the 10 attributes to something new. Now that all of the names have been changed, once again change the type of all of the attributes to a new value (using as many different types as possible). Finally change all of the names again to new names. Click the OK button to save the edits. This will typically result in an error message that states something like the following…

“The attribute someattributename could not be updated. Possible causes include attribute name duplication, maximum attribute name length exceeded, or invalid characters in the attribute name.

Out of memory”

If you click the ‘More’ button you see only an ‘Out of memory’ error on the dialog that is displayed.

Often when renaming the attributes and changing the types you will accidently set one of the types to AutoNumber resulting in the message that “Only one attribute of AutoNumber data type may be defined for a feature.”, so if you don’t see the Out of Memory error message initially try setting one of the types to AutoNumber during the workflow.

Issues Resolved

October 19, 2016 48

1-7PBOIU Output Name field should accept 2 bytes characters.

Generate Static mode dialog Output Name field does not accept the 2-byte characters. (There is the restriction of only accept alphanumeric characters and underscore). This is needed for Chinese, Japanese and Russian.

1-6CR1Q9

Feature Model does not recognize the SQL Server Native Spatial data server.

For Public Works functionality to work with the SQL Server Native spatial data server, Feature Model will need to be modified to recognize this new data server. That must happen before any testing can be done using Public Works functionality with this new data server. This is also a major concern for customer who wish to use GMSC as GMSC has only limited support for features served from GDO based MS SQL features.

1-6XHG98

Path to Default Symbol File has changed, thus Symbol file: field is empty.

Steps to reproduce.

1. Invoke GeoMedia.

2. Activate Layout Window.

3. Invoke Set Active Symbol command. Drawing Tab -> Insert Geometry Panel. It's the bottom right command in the first section. It's also on the Drawing toolbar.

4. This results in no default symbol.

1-6YPVUD

Continued Label Style Problems and Performance Issues.

I continue to have problems when using styles in the label tools as well as performance issues on areas where I have no labels to display. A separate CR was created for the styles issue. The performance issues were handled. Some by documentation, some by code changes.

1-70PSCY

Layout > Insert > Insert Map by: Duplicate Drawing Toolbar. Existing shape, paper size, etc.

When using Layout > Insert Map by X, I'm seeing 2 copies of the Drawing Toolbar, which consumes too much of my layout window screen area. There should only be one copy. The second copy appears to be simply a ghost image - the buttons don't function. X = Paper Size, existing shape, rectangle Map/Layout Window should not be maximized.

1-70R94E

Display Scale is Greyed Out and Difficult to Read Compared to Previous Versions.

The MapWindow Display Scale which is displayed along the lower right portion of the application window is greyed out. This was not the case when compared to previous version.

1-AA7ZCB

GeoMedia crashes after abnormal memory and network usage growth on trying to add legend entries.

GeoMedia crashes after abnormal memory and network usage growth on trying to add legend entries from PostGIS database. On trying to add several legend entries from a PostGIS database it was observed that the memory usage grew to over 3 GB very quickly and GeoMedia crashed. The memory and network usage growth was abnormal and also instantaneous. A screenshot taken during the growth has been attached. At one case GeoMedia also displayed 'Out of memory' for map view. Note: If GeoMedia does not crash with few legend entries, try adding some more in the same session. Steps to Reproduce:

1. Extract the contents of attached ZIP file to any folder

2. Register GMPsgCtl.ocx and PostGISGDO.dll using regsvr32. Run command prompt as Administrator.

Issues Resolved

October 19, 2016 49

3. PostGIS will start showing in new connections. Connect to the database with feature caching on. The crash might not happen if your machine has enough free memory but abnormal memory growth is evident. With IFC off both crash and memory growth were seen.

1-AA7ZF7

GeoMedia Public Works Commands are not supported on PostGIS.

GeoMedia Public Works Commands are not supported on PostGIS.

1-AA7ZGF

Could not view the inserted features unless connection is reopened-PostGIS.

Could not view the inserted features unless connection is reopened-PostGIS. Installing the PostGIS GDO for usage with GeoMedia. Steps to Reproduce:

1. Invoke GeoMedia Professional. Make PostGIS connection with your credentials Using IFC ON.

2. Add ACHSZAEHLER Feature Class to map window.

3. Using Insert Feature add a feature on map window.

Observation: Observe that feature is not displayed on map window. Now reopen the connection. Observe that inserted feature is displayed.

1-AA7ZJ6

PostGIS: Unable to generate static labels with Warehouse Connection.

PostGIS: Unable to generate static labels with Warehouse Connection. Steps to reproduce:

1. Invoke GM.

2. Make a PostGIS connection.

3. Add any Legend entry to MapWindow.

4. Invoke Label Manager, select any properties and dismiss the dialogs by clicking OK.

5. Invoke Toggle dynamic from Label tab to view the labels.

6. Invoke Generate Static label, choose Warehouse Connection and key in output name. Ensure the database chosen is PostGIS connection.

7.Click OK to dismiss the dialog and create static labels.

Observe, an error is displayed --------------------------- GeoMedia Desktop --------------------------- Failed to generate static labels. --------------------------- OK ---------------------------

1-AA7ZO3

Selecting a Label leader command and selecting a new geoworkspace will throw an error.

Selecting a Label leader command and selecting a new geoworkspace will produce the following error message:

The following unexpected exception occurred: COM object that has been separated from its underlying RCW cannot be used. --------------------------- OK ---------------------------

The problem is not related whether features are added or not and even though the command was exited the problem is observed. Simply select leader command and select New Geoworkspace. Problem will be reproduced.

1-AAC315 GeoMedia is putting all cells from a dgn to level

When loading a DGN in to GeoMedia, any cell is placed on level 0, regardless of which level they were placed inside the DGN. Looking though the connection, anywhere a cell name is populated, the level is 0. I've created the CSD from scratch and used the Display CAD Files tools from inside GeoMedia. The

Issues Resolved

October 19, 2016 50

0 regardless of dgn level.

color, weight and style of the cell items are also being set to 0 regardless of dgn value. Steps to reproduce:

1.Unzip data from data location.

2.Open a blank .gws.

3.Manage Data>Display CAD Files.

4. CAD type: Microstation V8. Select All .dgn from data location, and specify ENRHI3.csf as the coordinate system

5.Advanced tab can be left as default or for better observation select 'Create a separate legend entry for each selected level'

6. 'Ok'

7. All cells from all dgns will be placed on 'Default' feature class

8. Analysis>Attribute query to filter where cellname = 9ROSE1

Observe the ElementLevelNumber is 0 in all cases (color, weight and style as well). These cells are from Level 8 in the .dgn 10. Analysis>Attribute query to filter 'Default' where cellname = WP_FB 11.

Observe the ElementlevelNUmber is 0 in all cases (color, weight and style as well) The same process can be repeated for all cells. There is no way of knowing which level in the DGN they originated.

1-AB9N5X

Location label for Enable feature caching checkbox is missing for Object Space connection type.

Steps to reproduce:

1. Invoke GeoMedia Professional and create blank GWS.

2. Invoke New Connection dialog.

3. Select Object Space as the connection type.

Observe: Location label for Enable feature caching checkbox is missing while it is displayed for all other connection types.

1-ABAPN7

Labeling Properties dialog - Label with symbols : The "Up" button is empty ("down" button has arrow).

Labeling Manager > Properties > Label with symbols: The "Up" button is empty ("down" button has down arrow ) MapText: Labeling Manager > Properties > Label with symbols : The "Up" button is empty ("down" button has down arrow ) in the expanded pane.

1-ABAPO3

Document Must Refresh Cache to view appended Static Labels with IFC on.

When generating static labels to warehouse with IFC on, labels are not shown on the Map when the "Append Labels to Existing Output" option is selected until the cache is refreshed or IFC is turned off. To reproduce:

1. Open blank geoworkspace and connect to USSampleData.mdb with caching ON.

2. Add States and HighwayIntechange feature classes.

3. Zoom into Washington state area and Invoke Label Manager.

4. Select Label checkbox for States feature class and set text as STATE_NAME.

Issues Resolved

October 19, 2016 51

5. Generate Static labels to Warehouse. Set feature class name as IFCTEST.

6. Invoke Label Manager, deselect Label checkbox for States feature class.

7. Select Label checkbox for HighwayIntechange feature class and set text as ID.

8. Generate Static labels to Warehouse. Select feature class name as IFCTEST and select "Append Labels to Existing Output" option.

Observe labels for HighwayIntechange features do not appear on map. -Refresh cache or disable caching to view labels.

1-9YR0IH

Add WMS Legend Entry Results in Errors and Bad State (Continual Wait Cursor).

Region has indicated they have customers asking why the Legend > Add WMS Legend Entry command cannot be used to add WMS Legend entries for a particular site. Selecting the Add WMS Legend Entry command results an error from .Net in GeoMedia states: "Expected DTD markup was not found. Line 1, position 3." Afterwards, the on-screen cursor stays in wait cursor mode which seems to indicate the command is not exited cleanly and is in a bad state.

1-A019KV

GeoMedia Professional crashes when redigitizing a long text using “place at a point” option.

Steps to Reproduce:


2. Create blank Geoworkspace. Make Access R/W connection to USSampleData.mdb. Make MapInfo connection to \\GeoMedia\PVTDatasets\MapInfo\USA or \\geotest2\PVTDatasets\MapInfo\USA

3. Add States LE from map info connection to map window.

4. Invoke Insert Interactive label command. Select States (MapInfo connection). Add all the available attributes. Select “StateNameLabels” as “Output labels to”, use Orientation as “Place along existing geometry”. Click on Ok button.

5. Now place the text around Alaska (isolated state shown on top left).

Now select this text and invoke Redigitize text command. Using “Place at a point” option try to place it on map window. Observe that the application crashes.

1-A23QOV

Dialog margins are compromised for resizable VB6 dialogs.

The dialogs listed below have issues with poor margins (usually at bottom and at right), sometimes including no margin or actually even clipping off controls. Behavior varies according to the operating system.

Queued Edit, Search, Edit Text and Linear Link Zoom.

The issues can be classified under 3 categories:

1. Dialogs that are resizable.

2. Dialogs with controls that are dropped at runtime.

3. Dockable controls that are resizable.

1-A23QQ3



Issues Resolved

October 19, 2016 52

Catalog Connections and Catalog Explorer.





1-A24ASV



Grid Calculator and Design Legend





1-A24ATE

Dialog margins are compromised for resizable VB6 dialogs


Dimensions and Dimension.





1-A34UNQ

Display AutoCAD .dxf results in application crash for certain data.

Customer provided data shows that using the Manage Data tab, Display CAD Files command to display certain AutoCAD .dxf files can result in the crash of the GeoMedia Application without any opportunity to save GeoWorkSpace changes. To reproduce: Create a GeoWorkSpace and use Display CAD Files to display one or both of the provided .dxf files using the default settings.

Observation: The following error will be displayed:

“GeoMedia Desktop. An error was encountered loading data for TextGeometry of AllLayers legend entry. Method '~' of object '~' failed. Do you want to continue loading remaining legend entries?” Afterwards the GeoMedia application crashes without opportunity to save the workspace.

1-A3MJFI

Insert > Georeferenced Images. TIFF file with suffix .tiff and worldfile crashes GeoMedia Pro.

When attempting to insert a TIFF file with suffix .tiff and worldfile, GeoMedia crashes when pushing the file to the right side of the dialog. Changing the extension to .tif allows the file to be moved to the right side of the Insert > Georeferenced Images dialog. Selecting the provided .csf file, then 'OK' generates an error:

Issues Resolved

October 19, 2016 53

--------------- GeoMedia Desktop . Error inserting or updating the specified coordinate system. --------------- The file cannot be inserted.

1-9CJWWW

Several res files contain string "Set the Master Connection in the Parcel Manager".

Several res files contain string "Set the Master Connection in the Parcel Manager". This should be changed to "GeoMedia" to reflect the inclusion of the former Parcel Manager commands into GeoMedia.

1-9CM1H0

View Precision Coord dockable control disappears when switching back from Layout window.

Precision Coordinate dockable control disappears when switching back from Layout window. To reproduce:

1. Open .gws

2. Drag the View Precision Coordinates dockable control to middle of Map window.

3. Activate the Layout window

4. Activate the Map window and notice the View Precision Coordinates dockable control is no longer displayed. User has to select the View Precision Coordinates button on the ribbon bar to display again.

1-9CQ4U7

The documentation is lacking the necessary full description for the FOLDER parameter for an FGDB connection.

In the documentation for developers you can read for the FGDB connection that the ConnectInfo for the INI file location is "FOLDER=;INI=<full path and filename of the warehouse configuration file>" But the customer received an error that was fixed only after the FOLDER parameter full path to the data folder was included. So, it needs to be documented like this: The problem is that it should be "FOLDER=<full path and filename of the warehouse folder>;INI=<full path and filename of the warehouse configuration file>" And the same for the FGDB write-Read.

1-9CSOYK

Crash without opportunity to save when using labelling with common GeoWorkSpace settings.

User may get message "Error activating the command" message followed by an application crash when using Dynamic Labelling. If the user has the Map Widow setup to navigate using selected records in the data window, then Dynamic Labelling may crash, especially if the user attempts to use the Data Window, Promote Rows command. Note: Map Window Properties are defined such that: "For items in select set" "Center at current scale". Workflowto reproduce:

1. Open GeoWorkSpace (references Madison County dataset)

2. Select Labelling > Toggle Dynamic so the Toggle Dynamic is enabled.

3. Use the Select Tool (NW arrow) to fence select 2 or more of the displayed point geometries.

4. Click on the header bar of the DataWindow1 window.

5. Select the Table > Promote Rows

Observation: Get message from GeoMedia Desktop Error activating the command followed by application crash.

1-9CUJFS

Multilingual generated .Net Custom commands not loaded to My Workflow on German

When .Net-Custom commands are generated multilingual with resource files, the language files cannot be used in German. The custom command can't be loaded, as long as there is the directory "de" in directory of the command dlls (even if the directory is empty). In the English version the problem doesn’t occur.

Issues Resolved

October 19, 2016 54

GEOMEDIA PROFESSIONAL.

1-9DJJPL

Unload Query does not actually unload to allow edits to run without processing the query.

Customer notes that even if he deletes his query(s) from the map legend AND uses the Analysis > Queries command to Unload all queries, the query is not unloaded from memory and the result is no savings in the time required to process.

Workflow:

1. Unzip using Extract All or Extract to Here option to C:\Warehouses.

2. Open Query_Unload_Test.gws

3. Use Analysis > Queries to display the Spatial Intersection query, "Unincorporated Parcel Sections" to the map window only (not the data window).

4. Note time to display. (Support observes ~9sec).

5. Close the Queries dialog.

6. Select the UnInc polygon, then use the Vector tab, Edit > Edit Geometry to move a vertex.

7. Note time to complete. (Support observes ~7 min).

8. Exit the Edit command (select the Select Tool).

9. Turn off display of the "Unincorporated Parcel Sections" legend entry.

10. Use Analysis > Queries to unload all queries.

Again use the Edit Geometry to move a vertex of the UnInc feature. Note the time to complete. (Support observes ~21 min).

1-9DJJT7

Poor Query Notification Performance in 2014 vs. 6.1.

GeoMedia 2014 shows very poor performance for query update / notifications when compared to version 6.1. In a simple test using a Spatial Intersection query we can see that the time required for an edit geometry move vertex in version 2014 on a Win7 system fails to exceed or meet the update time for the same operation when using 6.1 on XP. Testing here is limited to the time for notification and update to map view window for Spatial Intersection Query. Notification times for other query types has not been tested/compared to version 6.1. It is notable that performance of 2014 exceeds or matches 6.1 If a Spatial Filter is applied to the data; even if the Spatial Filter encloses the entire data set such that no feature records are actually filtered. This seems to force 2014 into a different logic path.

1-9DNBUO

Need official Support For Launching Configuration Wizard Using /q (quiet) Option.

Summary: Request official support and documentation for running Configuration Wizard using the /q (Quiet) option. User has already found that running Intergraph.GeoMedia.ConfigurationWizard.exe /q works but request official support in conjunction with related regression CR defect (see also Related CRs). Background: Administrator at large GeoMedia Application use site has requirement to provide non-admin clients the ability to launch and see the unassisted installation and configuration of GeoMedia. This was done in version 6.1 using a "Quiet" installation method which differs from "Silent" installation as it gives user installation feedback by showing dialogs and forms used during the installation process. The user found however that GeoMedia 2014 does allow for "Quiet" installation (see also Related CRs) and so has been forced to write their own client system install process. The good news is that the customer indicated success by copying the edited Intergraph.GeoMedia.ConfigurationWizard.exe.config down to the client, where the configuration wizard can run in quiet mode running “Intergraph.GeoMedia.ConfigurationWizard.exe /q” to import the license server settings. This CR asks that GeoMedia support the quiet install option; esp. in light of related regression CR.

Issues Resolved

October 19, 2016 55

1-9KYBZZ

When attaching raster images that are in JPEG 2000 format, GeoMedia crashes immediately.

When attaching raster images that are in JPEG 2000 (.jp2) format, GeoMedia crashes to desktop immediately with .Net runtime errors. Workflow to reproduce:

Using Insert>Georeferenced Image with automatic mode the application crashes when hitting ‘Ok’ or ‘Apply’.

1-9L2ZTP

Setting a Spatial Filter together with Filter using 'Upper' fails.

Error 0x80040ACE (Error parsing SQL statement) is being returned when getting recordset from an originating pipe set with a spatial filter and attribute filter using 'Upper' Oracle function. This originated from having LegendEntry->LoadData() fail with 0x80040638 (GRecordset is invalid.) during WMPS/WebMap workflow of generating a map image. It happens when in the OriginatingPipe->Filter one sets a where-clause expression similar to "Upper(Name) LIKE Upper('pattern')" and so the retrieved recordset is placed in the legend to be rendered. WebMap then applies a spatial filter with the map range and invalidates the recordset, which in turn makes LoadData fail.

1-9MKS1M

'Simplify Geometry' and 'Smooth Geometry' commands are not working using culture information.

'Simplify Geometry' and 'Smooth Geometry' commands are not working if the Culture information of a custom command is changed (different from GeoMedia). To Reproduce:

1. Copy the ChangeLanguage_Command folder to your machine where GeoMedia Professional 2015 is installed.

2. Open command prompt from the folder you copied

3. Run Register.bat file.

4. One custom command 'Change Language' should be added under 'Workflow' tab of your GeoMedia.

5. Open GeoMedia and connect to any warehouse (e.g., USSAMPLE database) and run 'Simplify Geometry' and 'Smooth Geometry' commands from Toolbox -> BaseGeometry.

6. Notice that both the commands should be working fine. Both the commands should be adding the query to mapwindow if 'Display results in mapwindow' option is checked.

7. Now go to Workflow tab and invoke the supplied custom command.

8. Change the language, which is other than GeoMedia language (e.g., German) in the combo box so that it changes the culture information of that custom command and shows the respective string in selected language.

9. Click 'Ok'.

10. Execute 'Simplify Geometry' and 'Smooth Geometry' commands and observe that the query is not created or added to the map window.

11. Invoke the custom command again and change the language back to English (same as GeoMedia language).

Execute 'Simplify Geometry' and 'Smooth Geometry' commands and see that query is created and added to the map window.

1-9OBC33

Grid layer shows a lot of void pixels after rasterizing elevation points.

Grid layer shows a lot of void pixels after rasterizing elevation points. The problem occurs when defining the study area inside the elevation spots. As soon as the study area covers a larger area than the elevation spots, the rasterized result is ok.

Issues Resolved

October 19, 2016 56

1-9QYJ53

Inappropriate error when clicked on Show Values button for a FC which is not having values.

A message box with a message "property is read only" is displayed when show values button is clicked in the select reference features dialog box in GeoMedia. After clicking on "ok" button the cursor remains in a processing state due to which we cannot proceed further. Steps to reproduce:


2. Create a blank Geoworkspace.

3. Make an Access R/W connection to USSampleData.mdb delivered with the product.

4. Create a new feature class of geometry type area. ManageData > Features > New

5. Invoke spatial reference features ManageData > SpatialFilter > SpatiaFilterReferenceFeatures.

6. Add the newly added feature class which is created above.

7. Click the select reference features icon at the bottom.

8. Select the newly added feature.

9. Click on show values.

Observation Message Box with "property is read only" is displayed which is not appropriate as the dataset is R/W.

1-90UR3Z Continue Geometry fails to place hole in area.

Continue Geometry fails to place a hole in an area using Continue Geometry tool, and where points are inserted using precision input including elevation values. Points are placed, but on attempting to complete the feature, GM simply "pings" and does nothing else, no error message.

1-90WSU7

Bufferzone fails on Edit Query Properties when displayed in a datawindow.

Buffer zone query fails when running Edit Query properties and the buffer zone is display in a data window. The error message is "Recordset Buffer zones around C_LINE_NR is empty"

1-912BW5

Aggregation, can't select features if query field is empty.

When trying to verify that the Query name is empty, the two feature combo boxes (‘Aggregate to summary features in’ and ‘From detail features in’) are accessible to us to change the features." This is not true. Attempting to use the combo boxes results in a pop-up error alert, just as with any other items in the dialog.

1-91SQTJ

Deleting warehouse connections throws an error.

Steps to reproduce:

1. Invoke GM.

2. Make various connections. For example, use 5 different Access connections.

3. Add legend entries from any connections.

4. Using Insert command insert any feature.

5. Select al the warehouse connections and delete it.

Issues Resolved

October 19, 2016 57

6. Observe an error message is displaced, ' Are you sure you want to delete this connection'. Click yes and click on delete again.

7. Observe an error message is displayed:

--------------------------- GeoMedia Desktop --------------------------- Object variable or With block variable not set --------------------------- OK ---------------------------

8. Click Ok on the error message.

9. Continuing further also throws an error. Click on new button and select cancel on New Connection dialog.

--------------------------- GeoMedia Desktop --------------------------- Subscript out of range --------------------------- OK ---------------------------

1-9TWMFA

WMS features are not displaying on map window.

1. Start GeoMedia Professional and create a new GeoWorkspace.

2. Create a new connection using WMS data server. WMS URL – http://in-falconsqa/WMSPVTAuthenticated/Service.svc/get?request=GetCapabilities&service=WMS and Choose WMSCoordOrder.ini from Warehouse as the Warehouse Configuration file while making the connection.

3. Click Ok button and provide user name and password.

4. Using Add Legend Entries command, add the States feature class to map.

Observe that features are not displaying, just foot prints will be displayed. Note:- Copy WMSCoordOrder.ini file to your local warehouse directory. This behaviour is observed only when the user is Standard user not an administrator. Features will display properly if the user is an administrator.

1-9V4P39

Simplify Geometry Command Not Working.

Simplify Geometry command seems to have problems working with specific feature classes; possibly where the Simplify Geometry command encounters polylines with a large number of vertices. Example Workflow Using Provided Data:

1. Extract .zip to C:\Warehouses

2. Open C:\Warehouses\Simplify_Test1\Simplify_Testing.gws

3. Optionally, select the Long_Line feature displayed in the map view then use the right-click, Geometry Information command to observe the number of vertices=553.

4. Select Toolbox tab, Base Geometry > Simplify Geometry, the Simplify Geometry dialog will appear.

5. Set the input feature as: Long_Line

6. Set the Distance to 100.0 m (default value)

7. Display the results in the map window.

5) Observation: The Long_Line feature is NOT simplified. The number of vertices is still 553. If however we do the same procedure for the feature "Short_Line" then the Simplify command works as expected. Note: It is desirable to use Simplify with the feature class: County_Lines_ALL which is provided as part of the warehouse data.

Issues Resolved

October 19, 2016 58

1-9X6K1H

Overview window not invoked after closing existing overview window.

Steps to Reproduce:

1. Invoke GeoMedia Professional. Create blank Geoworkspace.

2. Make Access R/W connection to USSampleData.mdb.

3. Add all Legend entries to map window.

4. Now invoke another map window.

5. Add all Legend entries and name the Legend as “Legend”.

6. Now rename mapwindow2 toTest.

7. Close the geoworkspace. Name it as SAMPLe.gws. Exit application.


9. Invoke overview window.

10. Using open geoworkspace open SAMPLE.gws.

11. Close the overview window.

12. Now try to invoke overview window again.

Observation: Observe that Overview window is not displayed. Exit application. Sometimes process is left out.

1-A5D41R

"Validate Connectivity" terminates GeoWorkSpace Session without opportunity to save.

Problem: The "validate connectivity" tool crashes constantly with a given dataset. An error message in German gets displayed (even when GM is installed in English). The original content of the error message: "Automatisierungsfehler - Das aufgerufene Objekt wurde von den Clients getrennt" Translation: "Automation error - the called object got disconnected from clients" Steps to reproduce:

1. Unpack ZIP folder in C:\Temp and open GWS "HSV.gws"

2. Toolbox -> Validate Connectivity

3. Validate features in "A10_Wal_Waldfunktion" with features in "A10_Gem_Gemeindegrenze"; Anomalies: "Non-coincident Intersecting Geometry"

Above mentioned error message gets displayed as soon as the validate connectivity tools gets started with button "OK" - By clicking OK on the error message, it disappears. If the "validate connectivity" window is closed via the "Cancel"-button, GM crashes (something like "GeoMedia doesn't work no longer"). If it is closed via the white cross on the right upper corner of the window, GM does not crash.

1-A7YCWW

Spatial Analysis commands throws method of object failed error with invalid query in filter dialog.

Spatial Analysis commands throws method of object failed error with invalid query in filter dialog. Steps to reproduce:

1) Invoke GeoMedia.

2) Make an Access connection.

3) Add legend entries.

4) Select Spatial query and Select a feature.

Issues Resolved

October 19, 2016 59

5) Select Filter dialog and choose not equal operator and click ok.

6) Select feature and select ok button. Observations: method of object failed error problem is in the filter dialog - it should warn the user as an invalid query and it happens on all spatial commands from Analysis commands.

1-A7YNFR

Additional unexpected dialog comes up giving invalid value in Update Attributes.

Additional unexpected dialog comes up giving invalid value in Update Attributes. Issue observed with Win8.1-64 bit. Steps to Reproduce:


2. Create blank Geoworkspace.

3. Make Access R/W connection to USSampleData.mdb.

4. Invoke Update attributes command. Enter 6$ for POP attribute and tab out.

Observe that error displayed as “--------------------------- PAttrCmd --------------------------- expression = 6$ --------------------------- OK ---------------------------“

Click on Ok button. Observe that now relevant message “--------------------------- GeoMedia Desktop --------------------------- There are no valid value(s)/expression(s) defined. --------------------------- OK ---------------------------“is displayed.

1-A7YNJ7

Select Set Properties throws error while performing analytical merge using CURRENCY attribute-IFC ON.

Select Set Properties throws error while performing analytical merge using CURRENCY attribute-IFC ON. Steps to Reproduce:


2. Create blank Geoworkspace.

3. Make Access R/W connection to USSampleData.mdb with IFC ON. Using Feature Class definition add Attribute1 of type currency.

4. Double click on States having ID of 2 and 4. Enter currency value as 12.

5. Double click on States having ID of 35 and 42. Enter currency value as 13.

6. Invoke Analytical merge command. Select States. Select criteria as “attribute”. Select currency attribute and click on Ok button. Select the merged feature (merged features with 12 and 13) and invoke Select Set Properties command.

Observe that error displays as “Error populating a field”.

1-AC7Y8G

Spatial filter causes anomalous geometry display using SmartStore Warehouse.

Spatial filter causes anomalous geometry display using SmartStore Warehouse. Using an overlap spatial filter with SmartStore data results in phantom geometry displays.

1-ADA7F4

Exit and save > Map Window state not saved on exit.

Region reports they open a GeoWorkspace. GeoMedia Desktop is not maximised so they maximise the window. Close and save the GeoWorkspace. Open GeoMedia Desktop again and it is no longer maximised. Customer sees this behaviour when running GeoMedia Desktop directly on his laptop and when using external monitors.

Issues Resolved

October 19, 2016 60

1-ADCQ6S

Data Integration and Validation Training.zip file link in GeoMediaFusion_Training Guide.pdf.

The delivered GeoMediaFusionTraining Guide.pdf has the following statement: Login to

also copy the link and paste it in Internet Explorer to open the link) https://support.intergraph.com/documents/GeoMedia/GeoMedia Fusion/Data Integration and Validation Training.zip The link in the training guide (see statement above) however returns a HTTP 404 error indicating page not found. Document needs correction and data should be delivered with product.

1-AQDP7O

KML Data Server not reading/displaying some features.

Customer provided KML data in version 2.0. File could not be served by GeoMedia Desktop - wrong version error. Customer indicates some interchanges are missing after reviewing the data. We reviewed the original .kml and all intersections/interchanges were present. GeoMedia Desktop fails to serve KML data properly.

1-ARG6PP

Time & Date/Time Format lost for Date attribute on German GeoMedia after feature class edit

A SR was filed for a problem when using GeoMedia Desktop configured for the German language whereby attributes of type Date that have the Format set as Time or Date/Time do not retain the formatting. Specifically the formatting of the Date attribute is lost if Feature Class Definition is used to add another attribute to the feature or edit an existing attribute. For instance an attribute with the Data Type set to Date (a.k.a. Datum in German) with the format set to Time would have the format changed to Date for that attribute after using Feature Class Definition. The workflow below can be used to reproduce the problem:

1. Run the GeoMedia Desktop Configuration Wizard to change the configuration language for GeoMedia to German.

2. After the configuration completes start GeoMedia Desktop and create a new blank GeoWorkspace.

3. Use the New Warehouse command to create a new blank Access warehouse with a name of your choice (such as datetest.mdb).

4. Select the Feature Class Definition command and create a new Point featureclass with three attributes. I used the names Att_Date, Att_Time, and Att_DateTime, for my tests. Set the Type for each attribute to Date (Datum in German language) and the set the Format to Date (Datum in German) for the first attribute, Time (Zeit in German) for the second attribute and Date/Time (Datum/ Zeit in German) for the third attribute. Review the attributes before clicking the Ok button on the dialog to insure that the desired Format is set for each attribute. Click OK and answer Yes to the prompt to create a primary key. Then click Close on the main dialog to dismiss the Feature Class Definition command.

5. Next use the Insert Feature command to insert an instance of the Point feature that you just created.

6. Using Select Set Properties enter an attribute value such as ‘1/14/2015 4:15’ for all three attributes of the newly inserted point feature. This should result in values displayed like the following based on the Format defined for each Date attribute.

Att_Date = 1/14/2015

Att_Time = 4:15:00 AM

Att_DateTime = 1/14/2015 4:15:00 AM

Click OK to dismiss the Select Set Properties dialog.

7. Double-click on the point feature again to open Select Set Properties and confirm that the attribute values are formatted/displayed as expected (per step 6 above). Close the Select Set Properties dialog with the Cancel button.

8. Select the Feature Class Definition command again and choose the point feature that was created in step 4.

Issues Resolved

October 19, 2016 61

9. Click the Edit button on the dialog then on the Edit dialog select the Attributes tab. Click in the first empty row of the grid. This will create a new attribute with a default name (Attribute 1) of type Text. Click OK to save this new attribute. Then click the Close button on the main Feature Class Definition dialog.

10. Now double-click on the point feature that you previously inserted and review the attributes again in Select Set Properties where you will see that the attribute values are now shown as...

Att_Date = 1/14/2015

Att_Time = 1/14/2015

Att_DateTime = 1/14/2015

The values are displayed differently than when they were originally entered because the Format setting for each Date type attribute is now set to Date even though there was no change by the user to these Format settings when the feature class was edited with Feature Class Definition.

11. To verify that the Format settings have been changed open Feature Class Definition again and review the attribute definitions for the point feature class. Note that the Format is now set to Date for the Att_Time, and Att_DateTime attributes that were previously set to Time and Date/Time respectively.

1-ATFD54

Analytical Merge/Aggregation output functional attribute allows spaces in "Functional attribute name.

Analytical Merge/Aggregation output functional attribute allows spaces in "Functional attribute name". To reproduce:

1. Open attached ussample.gws.

1. 2. Create an attribute query of "Counties" selecting "AVETEMP" as the attribute with a criteria "AVETEMP <= 43.1". This results in the output query "Attribute Query of Counties".

2. Select Analytical Merge and use the "Attribute Query of Counties" as the input Merge feature. Then select any attribute i.e. "COUNTY_NAME".

3. In the Output functional attributes white area field right mouse click and click on "New Count(*)". Notice the functional attribute name is "CountOfAttribute Query of Counties". This is the problem which is the spaces in the functional attribute name "CountOfAttribute Query of Counties"

This problem also occurs with Aggregation query. Customer comments: When I create a thematic legend entry over an attribute that contains a space character in its name the legend entries are all empty. For example I calculated an attribute 'count of' using a query. Later on I want to visualize my data using 'unique value thematic' for this attribute. In the preview it looks fine (column count has reasonable numbers in it). When I apply the symbology all counts become zero and you cannot see anything in the map. This behaviour is very confusing for the customers. Either it should not be possible to create attributes with space characters or it should appear an error message that explains the behaviour in symbology.

1-AX4OMP

WMS connection fails with “is not a valid name” message, same WMS can be opened in other clients.

WMS data server fails to connect to http://geo.weather.gc.ca/geomet/?lang=E&request=GetCapabilities with the error message “RDPS_ETA___Snow_mass__kg_m²_ is not a valid name.” In Geospatial Portal the layer can be added to the legend, but no graphics are visible. This may be due to my lack of expertise in configuring Geospatial Portal however. To reproduce this problem, use these steps:

1. Start GeoMedia Desktop and create a new blank geoworkspace.

2. Select the New Warehouse Connection command.

Issues Resolved

October 19, 2016 62

3. Choose WMS from the ‘Connection type’ list on the New Connection dialog and in the Web Map Service (WMS) URL’ field enter the location value.

4. Click OK to make the connection and the familiar “Unable to connect to database…” message is displayed. Click on the More button and you will see the message “RDPS_ETA___Snow_mass__kg_m²_ is not a valid name.”

If this same workflow is attempted with GeoMedia Professional 2013 or GeoMedia Desktop 2014 the WMS connection fails as well, but the message is “RAQDPS_BASE___Particulate_concentration___Diam___10_Microns___µg_m³ is not a valid name.”

1-AXJYZ6

Client Seat Cannot Specify Server Cache Location Without Using Create/Refresh Cache.

The client side workflow to define a shared server cache location causes local cache files to be created. This is because it is not possible to set the Location of the cache without having to click on the Create/Refresh Cache option of the Enable Caching dialog. For example: Client user needs to specify server UNC path location to shared cache for a particular existing connection where some features are currently displayed in the map window. The current workflow on the connection properties dialog is:

1. Select Properties for a Connection and notice how the Location field for cache is greyed out.

2. Enable (check) the Enable feature caching option.

The Enable Caching dialog is displayed, where the user must click on the Create/Refresh Cache option.. Any features that are displayed are cached locally. This means the user must create a local cache just so he/she can then finally select the location of the desired shared cache location. It may be more logical to allow the user to select / set the Location without having to generate a local cache. It is believed that once the UNC is correctly pointed to the server cache location where the local client cache files will be ignored; the local cache files remain on the client system, even if caching is disabled and the Clear Cache option is used.

1-AXJZJ8

Help Topic For Feature Caching Difficult to Read Due to No Wrap.

The Help topic for Feature Caching does not wrap to the width of the Help dialog / interface; this forces the user to scroll extensively. It's easier to copy the help contents to MS Word where the wrapping occurs automatically. Example: Open Help and search for PublishIFC, select the 1 Rank topic and notice how you must scroll to read the material.

1-AYLHVV Symbol display is incorrect in GMDesktop 2015

Customer has a symbol "Tree (from above)" in the provided .fsm, which has its display 'scrambled' in the Map Window with GM Desktop 2015. In GM Desktop 2014 it is displayed correctly in the map window.

1-AZGBWW

Default Values for text fields behaviour in Access DB.

Inconsistent use of single vs double quotes in Access. If you define a feature class in GeoMedia in an Access warehouse, and set a default value for a field of type text, the default value is in single quotes in Access (e.g. 'My default value') If you do it directly in MS Access, Access uses double quotes (e.g. "My default value"), and this is how MS Access handles default values for text fields. This creates some problems when you transfer a feature class to another warehouse type, e.g. SQL server Spatial with "Output to Feature Classes". I have tested this and tried to tie down the exact symptoms. The customer creates an Access database using MS Access as standard templates for distribution across their customers. When such database is defined, Database Utilities are used to create metadata. The problem lies in Default Values. Access has a standard of using double quotes for text values. On the other hand, GeoMedia uses single quotes which is incorrect for Access DB design. DB Utilities will then evaluate the "standard" double quotes as additional characters and put them into the column definition instead of format conversion. This causes troubles when e.g. exporting to different Warehouse. Exact steps to reproduce:

1. Open ussample.mdb file in MS Access and define a default value for selected text column in states table.

Issues Resolved

October 19, 2016 63

2. Using DB Utilities, drop states metadata and re-insert states FC Metadata.

3. Open GeoMedia, connect to ussample.mdb.

4. Make a R/W connection to an MSSQL DB

5. Use Output to Feature Classes to export the states Feature Class from Access to MSSQL

6. Test by inserting MSSQL states feature class and select set properties.

7. The new record will contain defined default value but with additional double quotes

Observations: - The problem might have origins in the Literal Conversion interface - If default value is defined using GeoMedia then it contains single quote and Access can handle them somehow

1-B0WWOR

Insert georeferenced raster causes GM 2015 to crash (German Regional Settings).

GM is crashing in inserting Georeferenced Image if Georeference mode is set to Automatic (w/ world file)" or "World file" and regional settings are set to "German". Root cause is probably a decimal separator issue.

1-B4YTAU

Caching Help Topic Titles are Duplicated.

Help topics for caching are only listed under a very large Help section called Miscellaneous: The 3 Help topics for caching is titled as: Feature Caching, Feature Caching, Feature Caching. Suggest that: a) Important topics such as Feature Caching be integrated into main contents, not hidden under Miscellaneous. b) Considerations be given to give appropriate unique titles to the topics. Example: Feature Caching Explained Feature Caching Process Feature Caching Batch Publishing Note: It may be that these could be condensed to 1 or 2 topics. For example Caching Explained could be combined with Feature Caching Process. c) Feature Caching topics really belong under some major Help topic such as warehouse connections. Appropriate cross links would be expected between these important topics. For example, currently The Edit Warehouse Connections help topic fails to mention feature caching.

1-B715PR

Issues with multi-select mode of PickQuick.

Below issues are observed with multi-select mode of PickQuick dialog.

1. Using keyboard navigation keys user is not able to navigate through the PickQuick dialog, it works only after the user presses the tab key.

2. Shift+navigation key is selecting the item on the PickQuick dialog. Item should be selected only when the item is in focus and space bar is pressed i.e. Space+Shift+navigation.

3. GUI issue on PickQuick dialog, Ok and Cancel button position varies based on the navigation keys appearance.

4. GUI issue on Generic Vertical PickQuick dialog. "Done" button is broadened.

1-B715QG

PickQuick: Holding control key and then pressing space bar is not adding to the selection.

Holding control key and then pressing space bar is not adding to the selection or removing from the selection if the current item is already selected. This functionality works fine with mouse left click and control key.

Issues Resolved

October 19, 2016 64

1-B8676U

Missing Grid lines in GM 2014 - Layout Window - Insert Grid.

Missing Grid lines in GM 2014 - Layout Window - Insert Grid. This problem does not exist in GM 2015. The customer can't update to 2015 due to missing GIPS products for 2015. Please have a look into attached data set and screenshots. To Reproduce:

1. In GM 2014 open the Test_Grid.gws and correct path to Test_Grid.mdb.

2. Make sure the RAHMEN feature is displayed using the Fit cmd.

3. Switch to the Layout window and select the Insert Map command using the "InsertMap using existing Shape.PNG" snapshot.

4. Select the Insert Cartographic Grid command.

5. Load the "Grid GK.xml" and click OK to place the cartographic grid.

6. Notice the upper right 4 degree longitude grid line is missing as well as the upper center 36 degree latitude grid line is missing.

1-BAWR7K

Area legend key disappears when expression is used for Displayable style property (regression).

When using an expression for the Displayable property on the Style Properties ‘Advanced’ tab to control the display of an area feature the corresponding legend entry key is removed. This is a regression from GeoMedia Desktop 2104. To see the problem you can use the steps below.

1. Create a new geoworkspace and make an Access warehouse connection to USSampleData.mdb.

2. Use ‘Add Legend Entries’ to add Counties to the legend.

3. Right click on Counties legend entry and select ‘Style Properties’.

4. On the ‘Style Properties’ dialog select the Advanced tab.

5. Ensure that the ‘Simple Line Style’ node of the Area Style is selected on the tree view on the left.

6. In the ‘Attribute Based’ column for the Displayable property enter the expression: IF(DISPLAYSCALE()<4000000,TRUE(),FALSE())

7. Click OK to exit Style Properties dialog.

8. Notice that the legend key for Counties is no longer displayed.

This same problem occurs even if you use an expression that would always evaluate as True for the Displayable property such as: IF(DISPLAYSCALE()>=1,TRUE(),FALSE()) If this same workflow is performed in GeoMedia Desktop 2014, the legend key for the Counties feature remains displayed. Likewise if the same expression is defined for Line or Point feature legend entries (e.g. Interstates and Cities) the legend key remains displayed even in 2015. I suspect that this regression occurred as a result of the addition of the point style to area feature styles for 2015. I base this assumption on the fact that deleting the Symbol Style from the Point Style node for an Area Style in the Style Properties dialog will allow the legend key to remain displayed.

1-BB25V5

Getting Unexpected Coordinate System Translation Failure When Attempting FGDB Connection.

When attempting to connect to the FGDB data get: Unable to connect to the database. Please verify that your warehouse-connection parameters are correct and try again. If we select More... we see: Coordinate System Translation Failure. If we define .ini with COORDINATE SYSTEM keyword the error can be avoided however the user expected that the coordinate system parameters could be read directly the FGDB data without the need for the definition of .ini file.

Issues Resolved

October 19, 2016 65

1-BB29E8

FGDB Data Server Fails To Serve Any Graphic Features From Users FGDB Data.

FGDB is failing to serve any graphic features from customer supplied FGDB data containing a mix of graphic and non-graphic data. Some of the non-graphic tables contain no records which is expected. No errors are displayed and the user can only see non-graphic tables served into GeoMedia. No graphic features are exposed for adding to the map legend.

1-BBZ86B

Unable to install GeoMedia (any) 2015 on system where GeoMedia (any) 6.1 was installed.

Cannot install GM 15 (any level) on system which has had GM 6.1 (any level) installed, unless 6.1 is removed by same user that installed it. When running Configuration Wizard get: GeoMedia Desktop 2015 Configuration Wizard Requested registry access is not allowed. Problem is reproduced by : Install GeoMedia (Pro) 6.1 as User A Remove GeoMedia (Pro) 6.1 as User B Examine registry: Note that HKEY_LOCAL_MACHINE\Software\<32/64bit>\Intergraph\GeoMedia key is left. Properties of this key make removal by any user other than User A very difficult - beyond a normal user's capabilities without step by step instruction. Now, as User B, install GeoMedia (any) 15.0.0.725. Installation is fine until Configuration Wizard runs, then a series of errors pop dealing with .Net and registry edits/permissions. GeoMedia will not run. Problem is that permissions on GeoMedia (6.1) registry key are not set correctly Workaround is to remove all GeoMedia 15.0.0.725, install GeoMedia 13.X or 14.X, and remove GeoMedia 13.X or 14.X, then install GeoMedia 15.X. This works because previous (13.X and 14.X) versions were coded to correct the invalid permissions on this registry entry. These corrections were not included in 15.X version.

1-B3DB0X

Attribute columns of a feature/query are not available when creating pie charts or bar diagrams.

Attribute columns of a feature/query are not available when creating pie charts or bar diagrams for spatial queries on the fly. To reproduce:

1. Open GWS with USSample Data.

2. Add States to legend if needed

3. Feature States has 23 Attribute columns

4. Edit/Open the Style Properties for States and on the Advanced tab select the Attribute Based field for Alignment and select Expression. Notice the Expression dialog shows all the attribute columns for the States feature.

5. Create a Spatial Query where cities touch states and the style type is Bar Chart or Pie Chart. Use WHOP,HISPPOP,BLKPOP,ASIANPOP as the attributes for the chart.

6. Now do the same workflow as step 5, but click on the Style button> Properties button>Advanced tab and click in the Attribute Based field for Alignment and select Expression.

Notice the Expression dialog only shows the Input.PrimaryGeometryField attribute column and none of the other attribute columns for the States feature. User cannot create an expression on any attribute columns for Symbol, Bar Chart, Font, Picture, and Pie Chart styles on the fly for Spatial, Spatial Intersection, and Spatial Difference queries. Once the spatial query is created the user can create Symbol, Bar Chart, Font, Picture, and Pie Chart styles using expressions.

1-B3DPTR

Existing Non Cached Connections Do Not Honor / Read Default for Feature Cache Files Location.

When reviewing the properties of an existing non-cached connection, the default value of the cache Location property does not honor the location set in File > Options, File Locations tab for Feature Cache Files location. Example:

1. Create new GeoWorkSpace and create non-cached, warehouse connection (do not enable caching) to a warehouse that supports caching.

2. Select File > Options, File Locations tab to set the Feature Cache Files location to C:\Temp\GeoMediaCaches

Issues Resolved

October 19, 2016 66

3. Optionally if we look in the registry, we can see the new cache location defined in the users HKLU preferences for GeoMedia 2015.

4. Use the Warehouse Connections command to review the properties of an existing connection.

Observation:

Notice how the Location (greyed out) does not reflect the correct default value. This is a point of confusion in that the user can now easily have cache data created in a non-default location even after just changing the default location for cache data. When invoking the "New Connections" dialog, the default location for the Cache Folder IS correctly read from File > Options, File Locations tab, Feature Cache Files setting.

1-B4HJI8

Validate Geometry Returns Invalid Geometry Component for Polygons With Valid Arcs.

Have polygons inserted via GeoMedia's Insert Feature command which contain one or more arcs. The inserted polygons are presumed to be valid Composite Polygon Geometries but Validate Geometry classifies *all polygons containing an arc as: "Invalid Geometry Component".* Only circles are considered valid. It seems that Validate Geometry considers all arcs that are part of a CompositePolygonGeometry to be an Invalid Geometry Component. We suspect this is not true and that the Validate Geometry command to be in error. Other possibilities may be that: a) GeoMedia Insert Feature Arc Placement commands may be placing incorrect geometry. b) Validate Geometry needs to further define what constitutes invalid arcs Current 2015 Help on the topic of Invalid Geometry states: "Invalid Geometry Component refers to those features whose geometry is syntactically correct (i.e. passed the check as specified by the Invalid Geometry anomaly) but whose specification does not define a valid geometric component. Included in the definition of invalid geometries are the following: Invalid Arc - The radius, start end point of the arc are not valid. Invalid Boundary - The boundary's exterior or interior components are not polygons. Discontinuous Composite - The composite does not form a connected path."

1-BC9RVV

Search doesn’t give any records with category feature class

1. Invoke GeoMedia

2. Make an access connection to USSampleData.mdb

3. Create a category and Add “Rivers”, “Counties” feature class to the same category

5. Select Rivers from category in which you want to search and enter Mis* as search text

6. Observe 0 records have been identified.

1-BC9RX0

Object or Block variable not set dialog comes with Queued Edit command.

1. Invoke GeoMedia

2. Make an access connection to USSampleData.mdb

3. Invoke Queued edit from analysis > Utilities

4. Select Rivers from previous connection and Observe Queued edit Data window will come

5. Observe Status Review/Update combo box is disabled

6. Enter any value (say 50) into the current item number field and press Enter

7. Click on Status Review/Update combo box

8. Observe an error dialog with message “Object or Block variable not set” comes

Issues Resolved

October 19, 2016 67

1-BC9RXO

Bookmark Error with queued Edit control for Dynamic Queues.

1.Copy USSampleDatawithQueues.mdb. 2.Copy Queuetest.gws .Steps to reproduce:

1. Invoke GeoMedia

2. Open Queuetest.gws and select USSampleDatawithQueues.mdb If It prompts for mdb file location

3. Add all legend entries to the map window

5. Select DynamicQueues-> Counties with snowfall > 0 from the select feature combobox.

6. Go to the mapwindow and go to any record (say 50) on the Queued edit control.

7. Now open Queuededit mapwindow and invoke selectset to change the value of ANNULSNOW to 0 for next 5 to 6 records

8. Observe you will see the following message: The given bookmark is either bad or not created by this server (or this version of the server).

1-BDB90W

Editing Name Of GeoWorkSpace Coordinate System Can Result In Out Of Memory Error.

When editing the Coordinate System of GeoWorkSpace, if you clear the Name field (the optional coordinate system name), then click into the Description field, the following error occurs: CCSDefCS Out of memory. The error seems to be only disruptive and not destructive. It will continue to pop back up as long as the coordinate system name field is not defined. The problem does not seem to occur when running the define coordinate system utility (outside the .gws document).

1-DFA2B9

Output To Feature Classes is extremely slow/hangs when source is CAD (V8 DGN).

A SR was filed reporting that Output To Feature Classes is very slow in GeoMedia 2015 when the source connection is a CAD connection (MicroStation V8 design file) and the target connection is a new Access warehouse, whereas with GeoMedia 6.1 the same workflow completes quickly. I was able to reproduce this problem with GeoMedia 15.00.0000.120120. In my testing I observed that when using the Output to Feature Classes command in GeoMedia 06.01.11.13 to output the ‘Default’ feature class (containing 18953 features) from the customer’s CAD connection to a new Access warehouse the process takes 11 seconds. In GeoMedia 15.00.0000.10120 when the same ‘Default’ feature class with the 18953 features is output to a new Access warehouse the process takes 11 minutes and 36 seconds. In GeoMedia 6.1 it takes only 2 minutes and 8 seconds to output all 63 of the feature classes in the CAD connection. In GeoMedia 2015 if you attempt to output all 63 features classes, after an hour or more the Output to Feature Classes command appears to stall out while processing the Ebene_22 feature class, so it is not clear if the process will actually complete for all 63 feature classes using GM 2015. To reproduce this problem, extract the files from the provided OTFC_CAD.zip file and use the steps below.

1. Using GeoMedia 2015 create a new blank GeoWorkspace.

2. Select the Display CAD Files command and for ‘CAD type’ choose ‘MicroStation V8’

3. For the ‘Folder’ field, browse to the location of the Wasser.dgn file.

4. Check the Wasser.dgn file in the ‘Available files’ list.

5. For the ‘Coordinate System file’ filed browse for and select the GK3_DHDN_SISNET.csf file.

6. Click the Advanced tab and check the option ‘Create a separate legend entry for each selected level’.

7. Click the OK button to create the .csd file and make the CAD connection.

Issues Resolved

October 19, 2016 68

8. Use the New Warehouse command to create a new blank Access warehouse (e.g. OTFCCADTEST.mdb).

9. Select the Output to Feature Classes command and expand the ‘CAD Connection 1’ node, then check the Default feature class. (* If you select the top level ‘CAD Connection 1 node’ so that all feature classes are selected the process will likely fail to complete.)

10. The Target connection should be set by default to the Access warehouse, so click the OK button to begin the process.

11. Once the process completes, review the GMOTTS.log file in the C:\Warehouses folder and note the Start and End time for the output of the Default feature class.

Now repeat this workflow, but in step 1 use GeoMedia 6.1 and in step 11 when reviewing the GMOTTS.log file you will see a much shorter processing time.

1-DFLWW3

Batch plotting utility crashes while doing File-> Save and then File->Close.

Issue is reproducible in 6.1 As well. Steps to reproduce:

1) Open batch plotting utility and select new sheet composition mode.

2) Click on Geoworkspace Browse and select BPU_PVTTesting_ValidGWS.gws.

3) Browse and select any layout template.

4) Go to BaseMap tab and define the extent as "Attribute Query of States from Queries".

5) Select any attribute for sheet name and select "base Map" as map content.

6) In Map Rotation select any attribute from dropdown.

7) File->Save the .gbp and close batch plotting using file close. Observe batch plotting crashes.

1-DJOZQC

Create Conflation Links can lead to gaps in LRM when short links are evaluated against long links.

UPDATED DESCRIPTION BASED ON RESEARCH BY DEVELOPMENT: When there is a long link and a short link being evaluated and the long link is outside the zone - no link is made. This needs to be corrected. Practically these conditions will not exclusively exist in only one connection and percentages will appear in both connections. If the connections are reversed the link is made because the buffer is drawn around the long link and the short link is in the zone. However, if there are now 2 short links in the same zone, multiple links are made and the 2nd link is filtered out leaving an orphan segment without a link partner and a resulting gap in the output. A fix is needed to make a good (continuous) link in the situation where the link zone is drawn around the short link and the long link is outside the zone.

1-DB21OZ

Throwing "Out of Memory" error after emptying the storage center fields of Storage Space tab.

Steps to Reproduce:

1. Invoke Define Coordinate System File Utility.

2. Click on Storage Space tab.

3. Under Storage Center section, remove the Zeros (0.00) from the X text file.

4. Now try to click on "Y " text field.

Observation: Throwing "Out of memory" error. Expected Result: It could show better error message rather "Out of memory" error. Note: Issue not observed in GM 2014 SP2

1-DBFEHL "Coarse Overlap" misspelled as

Steps to Reproduce:

Issues Resolved

October 19, 2016 69

"Course Overalp" in Spatial Filter Dialog box help documentation.

1.Invoke GeoMedia

2.Invoke Spatial Filter command

3.Invoke Spatial Filter Options dialog

4.Press F1 for help Observation: "Coarse Overlap" misspelled as "Course Overlap"

1-D8VTJC

Incorrect icons are shown in "Custom Ribbon" form for custom ribbon bar with gm commands

In the GM GUI, the Customize Ribbon dialog is showing the incorrect icons for commands. In this test case, the screen prints show that the icon for a command in the right panel actually matches a command that is 2 commands/icons back from the current icon/command. The screen prints will help clarify the problem.

1-BYCUX8

Display Location Functions fail if locations.xml is not in c:\GeoWorkspaces.

This problem is in GM 2015 also. Display Location Functions fail if loacations.xml is not in C:\GeoWorkspaces because the registry entry for the GM preference set name "xmlPath" is set to "C:\GeoWorkspaces". The user is doing the following workflow resulting in the Display Location command not working:

1. Open .gws and select the far left File icon and select the Options>File Locations tab and change the GeoWorkspace Files location to D:\Temp\GeoWorkspaces folder

2. Exit and Save the geoworkspace.

3. In the C:\GeoWorkspaces folder the user selects all files including the locations.xml file, cuts the files and moves them to the D:\Temp\GeoWorkspaces folder.

Open the .gws from step 2 and try to use the Display Location cmds, but they do not work because the registry entry for the GM preference set name "xmlPath" is set to "C:\GeoWorkspaces". This can be reproduced using any dataset.

1-BZ6HI0

Dynamic Segmentation Creating Invalid / Corrupted Geometry.

Customer has noted noticed a serious problem where query results of Dynamic Segmentation in version 2015 is invalid. The customer points out that version 6.1 and version 2014, dynamic segmentation is considered correct whereas the same GeoWorkSpace when opened in 2015 produces invalid geometry collections.

The problem is causing invalid results for this query and all subsequent queries in user’s workflow. Workflow using supplied data:

(1) Open GeoWorkSpace file on version 6.1 or 2014 system.

(2) Observe the results and note how there are no collections.

(3) Open the same GeoWorkSpace file on a 2015 system.

Observations: Notice there are several collection geometries not seen in version 6.1 or 2014. Try selecting a collection geometry (shown in red) and right-click for Geometry Information. Notice the PolyLine component containing only one vertex. If use Tools > Validate Geometry using all of the "Standard Anomalies" options, we can see that the collection geometries are invalid.

1-CPZE0F

Attributes are not getting appended on selecting the attributes button

Attributes are not getting appended on selecting the attributes button from join command and it throws an error on GM. Steps to reproduce:

1. Invoke GeoMedia.

Issues Resolved

October 19, 2016 70

from join command.

2. Select Blank geoworkspace.

3. Make an Access connection (USSampledata.mdb) and select an new category.

4. Add features. Select interstate features and change the attribute names (State_Name).

5. Select Join Command and select the available attribute which is changed (select the attribute pairs).

6. Select attributes button (Duplicate attribute name. The name must be unique.)

Error message: Duplicate attribute name. The name must be unique. --------------------------- GeoMedia Desktop --------------------------- Duplicate attribute name. The name must be unique. --------------------------- OK ---------------------------

1-CQ5GK9

Grid > Utilities > Create Elevation Footprints. Command exits when the '+Add' button is selected.

During support workflow testing it was discovered that the '+Add' button will generate an unhandled exception.

Error message is: ----------------------- Create Elevation Footprints X Unhandled exception has occurred in a component in your application... Could not load type 'Intergraph.GeoMediaGrid.Private.Utilities.FootprintFileNotSupported' for assembly '3DMLHelper, Version=14.0.0.0, Culture=neutral, PublicKeyToken=41c4fcd3487160b5' -----------------------

Developer has replicated and diagnosed the error. They state: GeoMedia Grid delivers a file 3DMLHelper.dll. This is a C++ managed dll. The CI process for building and packaging GMGrid will stamp Win32 and .NET dll file versions if the project is rebuilt in CI. However, we do not have a process to stamp file versions for C++ managed dlls. A new version of 3DMLHelper.dll was delivered in GeoMedia 15.0.0.10XXX but the file version was not bumped. Because the file version was not bumped, it will not replace the original file when the patch is installed. The command works as designed on 15.00.0000.10120.

1-CF76CV

Properties dialog fails to display the correct value for SINGLE data type field.

When using new (WPF) Attribute Properties dialog, values are displayed incorrectly for data type SINGLE. Behaviour is a regression from 2014.

1. Edit a feature with SINGLE GeoMedia datatype.

2. Enter 10000000000000000000 in this SINGLE field.

Observations: The value is displayed in the dialog as 9.99999998050645 E +18 which is NOT correct. If we review the value in the database, the value is correctly stored as 1E+19. Labelling the value we also see the correct value displayed in the label. Doing steps 1 and 2 in version 2014 the value is correctly displayed as 1E+19.

1-CG91D5

Symbol style using MicroStation cell does not display correctly.

Text size and color fill problems using Microstation cell as symbol style. User has GeoMedia symbol style defined that references Microstation v8 cell. The cell displays correctly in GeoMedia 6.1 but when displayed in 2014 or 2015, some text components are not correctly sized/positioned and also some polygons are not correctly filled. Workflow:

1. Save attached .zip and save to C:\Warehouses and extract to here. Folder C:\Warehouses\1-741933221 is now available.

2. Copy or move the cell (.cel) library from C:\Warehouses\1-741933221 up to C:\Warehouses.

3. Open Sym2_cel.gws.

Issues Resolved

October 19, 2016 71

Observations: Notice how the text is not sized correctly. Notice also how the shapes representing the exclamation mark are not filled black.

1-CG91EB

Symbol style using MicroStation cell arcs do not display correctly.

User has GeoMedia symbol style defined that references Microstation v8 cell. The user has noted that the cell displays correctly in GeoMedia 6.1 but when displayed in 2014 or 2015, the arcs are not correctly displayed. Workflow:

1. Save attached .zip and save to C:\Warehouses and extract to here. Folder C:\Warehouses\1-741933221 is now available.

2. Copy or move the cell (.cel) library from C:\Warehouses\1-741933221 up to C:\Warehouses

3. Open Sym4_cel.gws.

Observations: Notice how arcs components of the symbol are not displayed.

1-CGDEXZ

Cannot Install Language Packs In Silent Mode.

It does not appear possible to install language packs in silent mode. Please provide a viable workflow. Currently the following 4 suggested steps fail:

1. Installing English GeoMedia : setup.exe /s GeoMedia /ni ACCEPT_EULA=1 (This command line should run against English installation Setup.exe)

2. Installing French Language Pack: setup.exe /s FrenchGM /ni ACCEPT_EULA=1 (This command line should run against Language pack installation Setup.exe) – Language Pack is the separate installation. So need to run the separate Setup.exe on Language Pack installation folder) French GeoMedia Desktop Name : “FrenchGM” French GeoMedia Viewer Name: “FrenchGMV”

3. Prepare to configure the French Language. Edit Intergraph.GeoMedia.ConfigurationWizard.exe.config file and set the language as French. (This file is under C:\Program Files (x86)\Hexagon\GeoMedia Professional\Program) This file should be placed under C:\Program Files (x86)\Hexagon\GeoMedia Professional\Program with Intergraph.GeoMedia.ConfigurationWizard.exe on each GeoMedia installation with the following value changed to 12. </setting> <setting name="RuntimeLCID" serializeAs="String"> <value>12</value> </setting>

Configure French Language setup.exe /s GeoMedia /c GeoMedia (This command line should run against English installation Setup.exe) It has been suggested that the problem is in step 4 where the Configuration Wizard fails to copy the localized files from the Languages folder to the GeoMedia Program folder.

1-CILA85

Boolean attribute with Default value of True is populated with value of False instead.

When ‘Feature Definition’ is used to add a Boolean attribute to an existing feature and the default value is set to True, the Boolean attribute is populated with the value of False instead of True when the feature is digitized with the Insert Feature command. Here is a summary of the steps to reproduce the problem:

1. Start GeoMedia with a blank geoworkspace.

2. Use the New Warehouse command to create a new Access warehouse.

3. Use the Feature Definition command to create a point feature class (e.g. FeatureClass1) with a single Boolean attribute (e.g. Attribute1) and set the Default value to True. Click OK to exit Feature Definition and when prompted “Do you want GeoMedia to generate a primary key of Autonumber data type?” click ‘Yes’.

Issues Resolved

October 19, 2016 72

4. Use the Insert Feature command to digitize one or more instances of the feature that you just created.

5. Use Select Set Properties to verify that the features that were inserted were populated with a value for True for the attribute of type Boolean.

6. Now open the Feature Definition command again and choose the feature class created in step 3 and click Edit. On the Attributes tab click in the empty row to add a new attribute (Attribute2) and set it to type Boolean and then set the Default value to True. Click OK to exit the dialog.

7. Choose the Insert Feature command again and digitize one or more additional features.

8. Use Select Set Properties to review one of the newly inserted features and notice that the new attribute (Attribute2) has a value of False even though the default value was set to True for this Boolean attribute.

It appears that these two conditions may be required to observe the problem:

- Feature Definition is used to add a new Boolean attribute to an existing feature.

- Insert Feature is used to insert one or more features prior to the Feature Class Definition edit to add the new attribute of type Boolean with the default value of True

This issue was reported by the customer with 15.00.0000.00725, but I have reproduced problem with version 15.00.0000.10120. This appears to be a regression from version 14.00.0002.0014 since the problem was not reproduced in that version when using the same workflow described above.

In 2015 it seems that if you exit GeoMedia and make a new connection to the Warehouse after making the Feature Class Definition edit, then the reconnect to the warehouse the correct default values are then populated for the boolean attribute.

1-CIMR6L

The title of profile chart has "and" in English on the localized version.

The title of profile chart has "and" in English on the localized version, This "and" is hard coded and needs to be externalized for the localization.

1-CJR6TD

Hard coded strings in modBatchPlotting.bas. Need to extract strings for the localization.

Hard coded strings in modBatchPlotting.bas. Need to extract strings for the localization. The English message displayed when Layout Template was not located on Sheet Composition. The corresponding string is defined in modBatchPlotting.bas. frmMissingInfo.Label1. There are more strings hardcoded in this file. Need to extract those strings to rc or drx files for localization.

1-CQSHDF

Thematic fill is not honored properly.

This is a latent issue observed on GM15.01 bld120 and GM16. Bld458 as well. Steps to Reproduce:

1. Invoke GeoMedia Professional. Create blank Geoworkspace.

2. Make AccessR/W connection to USSampleData.mdb.

3. Add States and create range thematic with default values. This works as expected.

4. Double click on the Legend icon. Change style to Standard and uncheck Fill.

5. Now double click on the legend. Select unique value thematic.

Issues Resolved

October 19, 2016 73

6. Click on Base Style and observe that fill is in checked status.

7. Click on Ok. Now select ANNULRAIN as attribute and click on Classify button.

Observe that color is not filled for Style. Click on Ok button and observe that unfilled entries are displayed. If we uncheck and check Fill option again at Step#6 then fill is shown properly.

1-CTH9RL

Unable to work with GPS Tracking after performing labelling workflow with leader line.

Unable to work with GPS Tracking after performing labelling workflow with leader line. Steps to reproduce:

1) Invoke GeoMedia.

2) Make an Access Connection (USSample Data.mdb).

3) Add legend entries states.

4) Select label manager and click properties button.

5) Select state name and click Ok button.

6) Generate static label to the warehouse.

7) Select the label and place the leader line.

8) Select GPS tracking command.

Observation. We are unable to work with GPS tracking command. Even though it is a latent, leader line is totally breaking the GPS tracking command

1-CVBVPB

Issues observed with OTFC 'Append', 'Append and Update', 'Update' modes to FGDB.

OTFC from FGDB to FGDB with 'Append and Update' or 'Update' mode and observe that it logs error message saying “Only Append operation can be done because the target primary key field is an autonumber field.” Error. And is displaying the existing records. This is observed even when we do OTFC from Access to FGDB. Also when we do OTFC from Access to FGDB with 'Append' mode, it is appending the new records with the existing.

1-CWCFKZ

Selecting the leader line and performing workflows related to map window throws an error.

Selecting the leader line and performing workflows related to map window throws an error. Workflow1: Steps to reproduce:

1. Invoke GeoMedia.

2. Make an Access Connection (USSample Data.mdb).

3. Add legend entries states.

4. Select label manager and click properties button.

5. Select state name and click Ok button.

6. Generate static label to the warehouse.

7. Select the label and place the leader line.

8. Select Add map new window.

Error: Simple steps to reproduce:

Issues Resolved

October 19, 2016 74

•Invoke GeoMedia. •select leader line. •

click ok on the warning message.

•select Add Map window

Workflow2: Steps to reproduce:

1. Invoke GeoMedia.

2. Make an Access Connection (USSample Data.mdb).

3. Add legend entries states.

4. Select label manager and click properties button.

5. Select state name and click Ok button.

6. Generate static label to the warehouse.


8. Select Queue edit from Analysis tab.

9. Select states from Queue edit control. Error:

Simple steps to reproduce:

1. Invoke GeoMedia.

2. Select leader line.

3. Click ok on the warning message.

Select Queue edit from Analysis tab.

1-CWFQBP

Oracle Data Servers Not Registered If Using Oracle XE.

Oracle XE 11.2 installed, but oracle dataserver not available for GeoMedia GeoWorkSpace connections after running configuration wizard. The same behaviour is found with versions 2014 and 2015 of GeoMedia. Environment: Windows 7x64 Oracle XE has been installed: (version x32 was used) http://www.oracle.com/technetwork/database/database-technologies/express-edition/downloads/index.html. Installed GeoMedia Professional version 2014 or 2015 but no Oracle data server connections are available. - GM database utilities allow us to log to database as well - When we open GeoMedia, no Oracle dataserver is available. Since Oracle XE 11.2 is supported it is expected that GeoMedia should register the oracle data servers. If we install GM6.1 in this environment, Oracle dataserver is present. Only with newer version we encounter this issue. Work-around: Manually create folder: C:\Program Files (x86)\Oracle\Inventory and re-run the GeoMedia Desktop Configuration Wizard.

1-CXFHK9

Active X error followed by Automation error while working with Copy Attributes definition command.

Steps to Reproduce:

1 .Invoke GeoMedia Professional. Create blank Geoworkspace. Make SQL connection to USSampleData. Issue observed with both IFC ON and OFF also

2. Invoke Copy Attributes Definition command. Select Rivers as Target and Interstates as source FC.

3. Click on Select All button and click on Ok button. Click Ok on the New Attributes dialog that pops up.

Issues Resolved

October 19, 2016 75

Observation: Observe that dialog is not dismissed immediately when tested with SQL Server for the first time on a fresh machine. Also Ok button on the Copy Attributes Definition dialog is still enabled. Now if within this short span of time if user clicks on Ok button on Copy Attributes Definition dialog follow errors are displayed:

--------------------------- GeoMedia Desktop --------------------------- Unable to set properties required to retrieve input feature class or query. --------------------------- OK

Click on Ok button Error displays as” --------------------------- PAttrCmd --------------------------- Run-time error '-2147217813 (80040e6b)': Unable to set properties required to retrieve input feature class or query. --------------------------- OK ---------------------------“

Click on Ok button Automation error displays. From then user cannot work with Copy Attributes definition command. Error displayed as “Active X component can’t create object”.

1-CXO14L

Error - Component Vtest6.ocx or one of its dependencies not correctly registered. GeoMedia 2015.

Selecting the Style Properties gives and error when large amount of images are loaded. To replicate open USSampleData.GWS. Add a large number of images. Display the images and the right click on a linear feature (Rivers) and select style properties and the errors will come up.

1-D3EBR2

Display CAD Files alters Z values on arcs.

Using Display CAD files causes the Z values of many (but not all) arcs that get ingested to have their Z values get altered by many feet. Have attached a data set that shows the problem, along with a screenshot showing that the Z value of the arc is over 13 feet different than the same point from the preceding segment. Problem occurs in GM 15 and 16, both on Windows 7 and Windows 8.1. Problem also occurs with both V7 and V8 DGN files.

1-C3DA26

Dynamic Labelling causes GM to crash.

Regression, unable to reproduce on GM 2014.

1. Connect to USSampleData.mdb

2. Add legend entries (Cities, States, Interstates)

3. In Label Manager setup States for dynamic labels using STATE_NAME as the text.

4. Toggle Dynamic Labels command to display State Name labels. 4. Use Fit to legend entry command on State Dynamic Labels

5. Toggle dynamic labels off.

6. Reorder legend entry by dragging Dynamic States label entry down in legend. Legend entries created by labelling are still visible and GM crashes. User cannot delete this legend entry (you can only hide legend entry) Also did workflow using MadisonCountyAL.mdb and was unable to create Dynamic Labels using the "Park" feature class so I used the "Institution" feature to produce the same GM crash using the above workflow.

1-C3DBIS

Documentation > Default CoordSystems folder does not exist.

GM2015 SP1 > Help > Search for 'coordsystems'. Under topic 'Advanced Options' document says: "The C:\Program Files (x86)\Common Files\Intergraph\CoordSystems\Program\EPSG folder is designated to be the default CoordSystems folder." This folder no longer exists with version 15 sp1. Document needs to be corrected. Search of the hard drive reveals two EPSG folders placed by installation of GeoMedia 15 sp1. C:\Program Files (x86)\Common Files\Intergraph\Coordinate Systems\3.0\EPSG and C:\Program Files (x86)\Common Files\Intergraph\GeoMedia\Program\EPSG. Customer asks which of these is used by GeoMedia. Support tested with ProcMon, looks like the second one is probably correct.

Issues Resolved

October 19, 2016 76

1-C67V6J

GeoMedia exe does not honor splash screen specified in frame stamp file.

The GeoMedia exe should replace the startup splashscreen with the one defined in the framestamp .xml passed in on the command line. This is not being honored in GM 2015.

1-C76BHX

Help Topic Executing Schema Remodeler from the Command Line Gives Incorrect PATH Info.

Help topic on "Executing Schema Remodeler from the Command Line" states that: To run Schema Remodeler from the command prompt, the syntax is: SchemaRemodeler.exe <parameter file>. You must be at the GeoMedia Professional\Program folder or have it in the path (for example, C:\Program Files\Hexagon\GeoMedia Professional\Program). While the path noted above does exists, it is NOT the correct location for running SchemaRemodeler.exe. The current target location (as of version 2015, build 10120) for SchemaRemodler.exe is: C:\Program Files (x86)\Hexagon\GeoMedia Fusion\Program. The user should include the location noted above as part of the system PATH or append the Fusion program folder to the PATH for the command window session using the following key-in: SET PATH=%PATH%C:\Program Files (x86)\Hexagon\GeoMedia Fusion\Program. Fusion development team should also review to make comments as to any other PATHS that might be expected by the SchemaRemodeler.exe. Unfortunately, the current Help topic does not mention any other requirements for PATH, other than the one that is currently incorrect.

1-C878KB

Display Locations regression for GSM-specific persistence logic.

The named locations UI layer was rewritten in C#. In doing this, the GSM-specific hook for plugging in a custom persistence mechanism was accidentally dropped. This capability needs to be reinstated.

1-AH5DID

WFS connection fails with GeoMedia 2013, same WFS works in 6.1 and GM 2014.

An SR was filed for the failure of GeoMedia 2013 to connect to a specific internal customer WFS (non-public). The customer notes that the same WFS works fine with GeoMedia 6.1 and GeoMedia 2014 WFS data server. Since the WFS is not public we cannot duplicate the issue, but problem appears to be similar to that reported in CR 1-9PHZ3X. That CR was filed on 6.1 and a fix was made in 2014, so it is believe that if the same fix is made in 2013 it may resolve this problem as well. The error from the customer WFS when the GM 2013 connection fails is as follows... /schema[1]/complexType[position() = 13 and @name = 'VW_GER_INDICADOR_CONDUCTORES_PType']/complexContent[1]/extension[1] Undefined <complexType>, '{http://www.opengis.net/gml}AbstractFeatureType' is used as a base type.

1-ANFOZW.

Setup - Desktop installs wrong version of .dlls.

Starting with version 14.00.0002.143, GeoMedia Desktop is installing files required by GeoSpatial Datapipe to C:\Program Files (x86)\Common Files\Intergraph\GeoMedia\Program\QD. The files delivered are out of date, causing that program to fail to run properly. The correct versions are delivered by GeoSpatial Datapipe, but they are not being loaded when GeoMedia Desktop starts, due to system pathing issues

1-BY42BJ

GMSmart client styles are not imported properly.

- Open the attached gws file.

- Invoke Styles from Home tab.

- Select the MyArea style and Export to -> GeoMedia Smart Client Style Definition.

- Give name as GMSmart.

- Invoke Import from -> GeoMedia Smart Client Style definition and select the GMSmart.xml.

- Click “Ok” on dialog.

Issues Resolved

October 19, 2016 77

- Observe GMSmart style is imported but with blank icon.

- Select the GMSmart style and observe the style properties are not displayed.

- Right click on States legend entry and select the Legend Entry Properties.

Observe only the MyArea style is displayed but GMSmart Style is not displayed in the list of available styles.

1-BY5XN3

Invalid row gets committed to IFC file but not in Oracle or SQL Server Database.

Invalid row gets committed to IFC file but not in Oracle or SQL Server Database. Note: This is also observed in 2015 release as well, but not observed in 2014 release. This is observed with both Oracle and SQL Server read-write connections with IFC ON, but not reproducible with Access RW connection. Steps to reproduce:

1. Create a RW Oracle or SQL Server connection with Feature Caching ON.

2. Create a new Point FeatureClass in the connection with two text attributes "Attribute1" and "Attribute2", both of type "Text" and mark Attribute1 attribute as primary key.

3. Create a new Data Window for the newly created FeatureClass.

4. Select a cell in first row and press tab twice to create a new record. You may either get a message "<This change could not be committed to the database.> Discard row?" - click No, or you a message "This change could not be committed to the database" click OK.

5. Observe that a row is added to the data window. Similarly add few more blank rows.

6. Now click on any row to enter value, an error message is thrown saying the bookmark is not valid. Actually these empty rows are created in IFC file, but not present in the database.

a. This did not happen in 2014 release even when IFC file was used. When IFC is OFF, then also a new blank is not added to the data window.

1-BY899F

Locations - Double clicking on list box scroll bar is invoking location properties dialog.

Locations - Double clicking on list box scroll bar is invoking location properties dialog. Workflow to reproduce:

1. Invoke GeoMedia and make a connection to USSampleData.mdb

2. Add Counties legend entry to Map Window. -Invoke Name Location command and enter a big name (not less than 100 characters) so that scroll bar will come in Locations command.

3. Click OK.

4. Now invoke Locations command. -Double click on scroll bar (or) arrow buttons of scroll bar.

5. Observe that Location properties for the selected location is invoked.

1-BY89GO

Display Location – Clicking OK on Display Location Options is clearing the location.

Clicking OK on Display Location Options is clearing the location from Named Locations drop-down menu. Workflow to reproduce:

1. Invoke GeoMedia and make a connection to USSampleData.mdb.

2. Add Counties legend entry to Map Window.

3. Select Display Location to make Display Location dockable control visible.

Issues Resolved

October 19, 2016 78

4. Select a location say “Location1” from Named Locations drop-down menu.

5. Invoke Display Location Options dialog and Click OK. –

Observe that location “Location1” selected above is not cleared in the Named Location drop-down.

1. Again invoke Display Location Options dialog.

2. Change the value in “Show this number of recent locations” using numeric up-down buttons.

3. Click OK.

Observe that location “Location1” is cleared in Named Locations drop-down menu. Expected result: Location1 shouldn’t be cleared in the Named Locations combobox.

1-BEF6HN

Database Utilities For MS SQL Spatial Warehouses May Display Incorrect Error Message Multiple Times.

On systems where SQL Server Native Client 10.0 or higher is not installed, users of MS SQL Spatial data will notice error messages stating that the Native Client software is required to correct metadata for date fields. Unfortunately this message appears up to eight times when working with warehouses that do not contain any date fields. While the problem is mostly a nuisance, it does indicate flawed logic that it's appearing multiple times and when date fields are not present. Example Workflow on system without any SQL Server Native Client 10.0 or higher is *installed:

1. Open Database Utilities and connect to MS SQL Native Spatial data (example: TSDB64VM NS_TENNESSEE ).

2. Delete metadata for some table (example: Antennas).

3. Insert Feature Class Metadata.

4. Select Table and add ( >) to right.

5. Select Table and select Properties.

Observation: The following error appears 8 times yet the table nor any table in the database does not contain any date fields what so ever. Additionally we see that this error logic is not applied at all when using the Edit Feature Class Metadata option which essentially allows the same controls to modify metadata for Data Types. --------------------------- Database Utilities --------------------------- The SQL Server Native Client 10.0 or higher is needed in order for Database Utilities to automatically create the correct GeoMedia metadata for date, time, and datetime2 data types. You may get SQL Server Native Client 10.0 or higher from the corresponding Microsoft websites. If the SQL Server Native Client is not installed on the system, you will need to manually choose Date as the data type from the dropdown combo box for these data types in the Feature Class Properties dialog and set the format properly. --------------------------- OK

1-BET1VE

Incorrect Logic For FGDB Data Server Use of Initialization (.ini) Files.

FGDB forces users to make registry edits to use .ini files. User definition of an .ini file (when one is provided as part of the connection) should never be ignored. The current approach causes problems for multiple reasons: 1. GeoMedia users have expectation that .ini files will be used if specifically provided. There's a field to define an .ini file on the connection dialog. This field should not be ignored as a default action. 2. In the current implementation, defining a registry edit to use .ini files forces the user to provide .ini files for all FGDB data connections, even those where the user does not wish to define any keywords. In fact if the registry edit is set to use the .ini then we see connection errors when no .ini file is given: GeoMedia Desktop INI file not provided. This forces users to always create .ini files for ALL FGDB data connections. If the logic was to use the .ini when supplied by the user then no registry edit would be required

1-BFRULH

Display Locations Command:"Show

1. Launch GeoMedia.

Issues Resolved

October 19, 2016 79

recent locations" functionality is not working as expected.

2. Make a read-write connection to Access database.

3. Add Legend entries.

4. Invoke Display Locations command.

5. Add 3 locations.

6. Invoke "Display Locations Options" dialog box on Display Locations dockable control.

7. Set the "Show this number of recent locations" to zero and click "OK".

8. Click on "Locations" Icon on Display Locations dockable control.

9. Try to select the recently added location and click on "Display" repeat the above step (9) for one more location.

Observation: Recent Locations list is shown in Display Locations drop-down on Display Locations dockable control.

Expected Result: Recent Locations list should not show up in any named locations in drop-down as we set the "Show this number of recent locations" to zero.

1-BFUCZ3

Unique Value Thematic command throws an error while classifying "Currency" data type.

Steps to reproduce:

1. Copy ExportData.mdb to C:\Warehouses.

2. Make an Access read-write connection to Exportdata.mdb

3. Invoke Add Thematic Legend Entry. Select Input Feature as “SourceFeatureClass” and type as “UniqueValueThematic”.

12. Select “TestCurrency” as AttributeforClassification. Click on Classify button. Observe that an error message "Invalid procedure call or argument" pops up.

1-BFYPVT

Crash to Desktop when inserting valid BigTIFF image.

Region reports, support duplicates crash of product when attempting to insert their BigTIFF image in GMDesktop. Crash to desktop, possible data loss.

1-BKCGL3

Symbol styles that contain arcs are displayed in wrong direction in the GM map window.

Symbol styles that contain arcs are displayed in wrong direction in the GM map window. If using a GeoMedia Feature Symbol file style that contains an arc the symbol/arc is displayed in wrong direction (reflected) when using it for point geometry in the map window. Problem just occurs in GeoMedia Desktop 2015, in 2014 the same symbol style is displayed correctly. Tested with symbol styles that are created with the "Define Symbol File" utility in GeoMedia 2014 and 2015, problem occurs in both cases.

To reproduce:

1. Open the 2015.gws and correct the path to the access warehouse.

2. Open the 2014.gws in GM 2015 and the problem is displayed, but not if the 2014.gws is opened in GM 2014.

1-BKCHWJ

Automation error when running Validate Areas

1. Extract the attached rar file to C:\Temp.

Issues Resolved

October 19, 2016 80

command with Coarse Overlap spatial operator.

2. Open the ValidateIssue.gws from the attachments and modify the mdb paths if required.

3. Run validate areas command with options as below. FeaturesToValidate - RECORDED_FABRIC CompareToFeaturesIn - RECORDED_FABRIC_LINE Minimum area overlap- 90

4. Check display results in map window and uncheck display results in data window.

5. Click OK and observe that Automation error dialog is shown.

6. Click Ok on the error dialog and Click on cancel in validate areas.

7. In spatial filter options change the operator to Overlap and re-run the workflow.

Observe that there is no error.

1-BKGDM8

Legend Key Graphic size has changed from 2014.

9) The size of the key graphics in the Map Window Legend has changed from 2014 to 2015. In 2014 the size of the circle (predefined) keys and that of the square (from BaseMap.fsm) are roughly the same. In 2015, the symbols from the .fsm file are quite small in comparison. - Legend Properties do not account for this difference - they are identical in both .gws files.

1-BMOG1J

Unable to connect to File Geodataabse in GM 2015 and GM 2014. CoordSys Translation Failure

Unable to 3. connect to File Geodatabase (FGDB Read only) in GM 2015 and GM 2014. Connection error states "Coordinate System Translation Failure". Dataset attached:

1. Open blank .gws.

2. Create a FGDB Read only connection using the SAN_PABLO.gdb and San_Pablo.ini file.

10) 3. "Coordinate System Translation Failure" after click OK to create the connection.

1-BNO1HL

MS SQL Dynamic Labelling Performance Problem If Compared to Access GDO Dynamic Labelling.

Comparing Dynamic Labelling of identical linear feature class using same label definition (Label size/Rule) of Access vs. MS SQL shows that Access labels are generated up to ~98% faster than equivalent labels and features stored in MS SQL (GDO). In the test case ~600K Tennessee state-wide local roads are displayed but less than 50 are within the map window display (map view display scale is ~1:14,000). No Spatial filter is applied however it is expected that the label processing by design should only be working with the records/geometries displayed/overlapping the bounds of the map view.

Example Times Observed: Access Dynamic Labels: 4 to 11 seconds MS SQL (GDO) Dynamic Labels 7 to 9 minutes The difference in performance is dramatic yet the input and the label output are equivalent. When Dynamic Labels are created there is no opportunity for the user to stop the process other than terminating the application. It’s suggested that some usability study be done to better understand issues faced when working with large data sets and dynamic labelling.

1-BNWGSB

Schema Remodeler throws an error and unable to perform operations.

Schema Remodeler throws a CLSID error and unable to perform operations. Steps to reproduce:

1. Invoke GeoMedia.

2. Change the default path of geoworkspace location to some other location using File Locate Options dialog.

3. Invoke Schema remodelled.

4. Select new transformation warehouse.

Launch GeoMedia. Observation: Unable to perform any operations on Schema Remodeler.

Issues Resolved

October 19, 2016 81

1-BPQUZ9

GeoMedia crashes when trying to add any command from vector tab from Customise ribbon.

GeoMedia crashes when trying to add any command without selecting any command from vector tab from Customise ribbon. Observations: GeoMedia crashes. Solution: For the remaining tabs at least one command is in selection state. Here there is no selection of command. Hence if Add button is in enable state at least one command should be selected by default. This is the case even with the Grid tab. Steps to reproduce: Invoke GeoMedia Professional. Select Blank Geoworkspace. Select Customize Ribbon From File menu. Select vector commands from Choose commands drop down. Select New tab button. Click Add button.

1-BQVM9R

WMS display fails for specific EPSG codes on specific URLs when using German regional settings.

WMS display fails to display for specific EPSG codes on specific URLs when using German regional settings WMS display fails for Gauss Küger Projection with datum "Deusches Hauptdreiecksnetz" on several services when using German regional settings: To reproduce the problem:

1. Set Regional settings to “German – Germany”

2. Connect to the appropriate service.

3. Set GWS Coordinate System to EPSG 31467 (Gauss Küger Zone 3, Deusches Hauptdreiecksnetz)

4. Display one of the layers. The layer is not displayed.

This isn't a problem with English regional settings. OS Language and the configured GeoMedia Language doesn’t seem to matter.

1-BS1PO4

Failure to Open Old GeoWorkSpace in 2014.

I have an older version 6.1 GeoWorkSpace that fails to open in 2014 or 2015. GeoMedia application crashes as the GeoWorkSpace is opened. The same GeoWorkSpace opens fine in version 6.1. The problem may be related to thematic legend entries as if we use version 6.1 to delete all thematic legend entries (including any named legends stored in Legend > Legends) then the GeoWorkSpace will open in 2014 and 2015. Deleting the thematic however is not a valid solution as there are several important thematics that serve as principal components of the GeoWorkSpace.

1-JYHPDC

Properties dialog can fail to display attribute values when picklist filter in place.

The 2015 properties dialog may fail to display stored attribute values if the field is associated to a picklist that has an attribute filter in place. If the user has filter string applied to his/her picklist and an existing value for the field/record does not pass the SQL statement, the value is displayed blank on the properties dialog grid. Problem is a regression from behavior observed in version 6.1 and 2014. It is expected that if a value is stored in the database, that the value should be displayed on the Properties dialog even if a picklist associated SQL statement does not include the value. Currently the field is shown as "blank" on the properties dialog which is misleading to users. PickList associated SQL Filters should only control the list of values displayed when a click is issued into a field and the descriptions displayed on the dialog if the stored value matches a value in the picklist. If a stored (pre-existing) value cannot be matched to a picklist value/description, then the value itself should be displayed. The attribute dialog should not mislead users by showing a blank field value. Problem can be observed for both GPickLists as well as AFM based picklists. Workflow using supplied data:

1. Create .gws and connect to the supplied access warehouse, "Simple_PickListTest.mdb".

2. Display Water_Line feature in map window.

3. Double-click water line to review Properties.

Observations: If using version 2014, you will see a value for the Material_Type attribute field. If using 2015, the Properties dialog will NOT show a value although one is stored in the database.

1-JYJ7PQ Display Labels fails when GM is

A customer reported that when running the ‘Display Labels’ command under the ‘Labelling’ menu an error message was displayed stating that “An error occurred in the underlying database”. This problem

Issues Resolved

October 19, 2016 82

running on same machine with older MapText LabelEZ product.

was also reported to MapText and their development group discovered the cause of the problem and provided a patch via the LabelEditSupport.dll that fixed the problem in GeoMedia with the Display Labels command.

The Labelling Generate Static Labels tool creates a table named as <output name>_PRP. Previous versions of Label-EZ did not create this table; however the latest ones do. The customer has lots of data sets created using earlier versions of Label-EZ. The Labelling Display Labels tool was not checking for the existence of the <output name>_PRP table before trying to open it. A GeoMedia user solely using the Labelling tools would never encounter this problem since the Labelling Generate Static Labels tool creates this table. Since the customer is trying to use the Labelling Display Labels tool on an older Label-EZ generated dataset, they encountered this problem.

1-K168FQ

Text disappears using CAD .INI file SERVE CELL GEOMETRY:Explode USTN V8 DGN elements.

Text disappears/shifted using CAD .INI file SERVE CELL GEOMETRY:Explode for Microstation V8 DGN text elements (LO1 dataset) even though the text is not part of a cell. Also some data is rotated out of position (T2 dataset) when SERVE CELL GEOMETRY:Explode When the INI parameters are changed from SERVE CELL GEOMETRY:EXPLODE to SERVE CELL GEOMETRY:TRUE, the data issues of text not part of a cell disappearing is not a problem. Using the SERVE CELL GEOMETRY:TRUE is not an option for the customer due to the chart assembly process which requires splitting apart the cells to apply masking and ink since they have different color, level, styles and weights and was created for this reason.

Note that SERVE CELL GEOMETRY:EXPLODE was added by the product centre for the Microstation V8 format and works in a similar fashion to the AutoCAD Explode. Workflow to reproduce:

1. LO1 and T2 EXPLODE.gws has 4 map windows showing the problems.

2. Set up GIPS project and copy data to appropriate project folders.

3. Edit the .ini and .csd to reflect correct project folders path. Set the SERVE CELL GEOMETRY:TRUE in the .ini file to see the text displayed without any problem.

Set the .ini file to SERVE CELL GEOMETRY:EXPLODE to see the text not being displayed. Again, the text is not part of a cell. Will need to reopen connections once edits are done to the .ini file.

1-K1NZFP

Data Window: CURRENCY data type values fail to display from AFM enabled connection.

Currency values defined in AFM Model fail to display in data window views. If you attempt to sort the data window column of currency data type values, referenced in AFM enabled connection the following error message appears: --------------------------- GeoMedia Desktop Error sorting data view. If AFM is disabled for the connection, the error does not occur. Example workflow using supplied data:

1. Open GeoWorkSpace, correcting path to data warehouse as needed.

2. Notice that in the data window, all values for the column "Line_Value" are displayed as NULL. This is not true.

3. Optionally try sorting the "LINE_VALUE" column. Observe the error displayed "Error sorting data view".

4. Double-click some of the longer horizontal map graphic segments to review the attribute Properties.

Observe that the "Line_Value" is not always null as suggested by the incorrect data window display.

1-K1PM5G

Properties dialog displays NULL CURRENCY values as .00.

NULL values for CURRENCY are displayed as $.00 on the Select Set Properties dialog (Attribute properties). It is expected that a null value should be displayed as a blank. Unfortunately, a true value of 0 (zero) also displays as $.00 thus users cannot use the Properties dialog to determine if the value is NULL or 0 (zero).

Issues Resolved

October 19, 2016 83

1-K1PY1U

Currency values multiplied by x1000 for Insert Feature of AFM enabled MS SQL features.

User has noted the Placement and Editing option "Copy attributes from previous feature fails to correctly copy currency values for AFM enabled, MS SQL features. Problem occurs for both GDO and Spatial type MS SQL Server connections. The previous currency value copied to the next new feature is multiplied by 1000. The problem seems to be restricted to when Operational Class associations are defined with Event Handlers that keep the insert active for inserting the next connected line. Example Workflow:

1. User has File > Option, Placement & Editing tab option "Copy attributes from previous feature" enabled (checked).

2. User uses Insert feature to place a line (Line A), entering a value of 16 into an existing currency attribute field.

3. User Inserts another line (Line B), clicking OK on the Attribute Properties dialog.

4. User Inserts another line (Line C), again clicking OK on the Properties dialog.

Now go back and review the attributes for currency: Line A = $16.00 (as expected), Line B = $16,000.00 (off by factor of x1000), Line C = $16,000,000.00 (again off by factor of x1000 from previous value). Expected value of $16.00 for all 3 lines. Additionally, after inserting first line we can see that Properties dialogs for steps 3 and 4 do not show the previous value at all.

1-K3FXFK

Validate Connectivity to fix Unbroken Intersecting Geometry results in loss of data or invalid geometry.

Toolbox > Validate Connectivity for automatic fixing of Unbroken Intersecting Geometry may delete portions of arcs when processing oracle data. When processing Access GDO stored arcs, invalid geometry components are created.The problem as noted for Oracle represents a loss of data with no recovery, and with no warning/message to the user of data loss. Attempting to use Undo results in the following error: GeoMedia Desktop Method '~' of object '~' failed.

For example if an arc crosses a line then one half of the arc will be deleted, the other half will remain. If processing unbroken intersecting Access (GDO) arcs, the arc geometry is broken but the arc pairs resulting from the break will be a Geometry Collection with 2 arcs; one arc is correct, the other has zero length. These GDO arcs that have been broken do not pass Validate Geometry; flagged as having invalid Geometry Component. Possible work-around for GDO arcs that have been broken may be to run Update Attributes to update the Geometry field using an expression such as: MERGE(GEOMETRIES(Input.Geometry)).

1-K4DOCB

Performance using shared cache via PublishIFC is not as good as expected (compared to local cache).

Customer reports the following issue/observation when using Net Cached Shared files (PublishIFC with /cachemode Shared option): With newly created net cache file IO Load is almost exclusively Oracle.exe (Initially it’s primarily GeoMedia.exe then switches to Oracle.exe) Load time is slow (1 min). It seems that GeoMedia tries to use the Net Cache files then ends ups using Oracle instead. With old net cache files load takes substantially longer (~3 min). The reported slow load time is presumably when compared to Local Cache files since the customer reports the following observations when using Local Cache files: With newly created local cache files IO is almost exclusively GeoMedia.exe (eg most of the data are read from the cache files) Load times are very quick (< 20sec) With old local cache files IO load switches to Oracle.exe. Load times are slower (1 min).

1-K6P9AR

Publishing Version 8 CAD Data to SmartStore Format Slower in 2015.

User has noted a degradation of performance in the Publish to SmartStore command specifically when publishing MicroStation Version 8 CAD (.dgn) data. Support observes that a performance drop of 4x is seen when any Version 8 CAD graphic attribute value is published. Problem is a regression from the performance seen in version 6.1 Example times when publishing ~35K graphic features with 1 attribute. Version 6.1 requires 15 seconds to publish. Version 2015 requires 60 seconds to publish. The performance drop may increase with data set size and/or number of attributes exposed. Typical SmartStore users have larger data sets. Problem may be related to CR Defect 1-DFA2B9 (see Also Related CRs) Workflow using supplied data.

1. Extract .zip to C:\Warehouses Note: New folder C:\Warehouses\CAD_Test will be created

Issues Resolved

October 19, 2016 84

2. Double-click (execute) Publish_Version8_CAD_Profile.ssp The Publish to SmartStore dialog should appear

3. Define an output DDC file name.

4. Ready Timer and select File > Publish Now.

Note time to complete publish process is approximately 60 seconds in version 2015. Version 6.1 requires only 15 seconds

1-JJQ6GJ

Create Links can result in incorrect X and Y values in GMFLinear_Linked table.

Users may obtain incorrect X and Y values in the GMFLinear_Linked table results from the Create Links command. In the given data we see that an incorrect XY value for the Connection 2 End X and Y value. The value does not match that of the ending value from Geometry Information. The value also does not match the connection 2 start X and Y for next segment thus a very small gap is created. See also Attachments for screen shot and data. Zone tolerance = 20 SF Certainty = 70% Intersection enabled tolerance = 17 SF Note: This CR filed while testing with GM Pro 2014, build 163 and patch provided for MO 1-G9BJWG (FeatureLinkingPipe1.dll dated 11/18/2015).

1-JM0CWV

GTech Dataserver fails to update GTech record count after refreshing GTech data server connection.

GTech Dataserver fails to update GTech record count after refreshing GTech data server connection. For complete workflow see attached video. Dataset connection information attached. The GM_VELUMINAR_PT feature is added to the Map window from the GTech data sever connection which reads the flat View GM_VELUMINAR_PT. In GTech the GM_VELUMINAR_PT feature is edited/updated and posted. After the GTech post the GM_VELUMINAR_PT view is directly accessed through SQL in the database the amount of records are viewed. In GM if the GM_VELUMINAR_PT feature is queried from an Oracle data server connection the amount of records of the feature is the same as the amount of records that were queried directly in the Oracle Database. But with the GTech Dataserver connection even after refreshing the GTech connection in the geoworkspace the record count is one less from the Oracle connection.

1-JM7EZO

Legend entries are shown as being loaded despite having 'display off'.

The test workflow explains the problem. A new Legend Entry is loaded to the Legend and a feature that is currently set to Display Off is being loaded for display. In the customer's case, it is a legend entry with 200K plus records, so it is hindering load/display time. Here is a workflow that reproduces the problem on 2014 and 2015:

1. Open blank .gws and connect to USSample .mdb.

2. Add States and Cities to the map legend.

3. Zoom in to your favourite state.

4. Turn off display of States feature class legend entry

5. Apply Spatial Filter by Active Map Window Extent Observation: by design, the States record set is not loaded.

6. Add Counties to the legend by right-clicking and getting the Legend Context menu and select Add and add a Legend Entry with a small number of records.

Observation: The States record set is loaded.

1-JM8951

Attempting to select certain thematic classified items in mapview

Attempting to select certain thematic classified items in mapview results in bookmark error. Given problem is a regression from version 2014. User has provided data and workflow that results in bookmark errors. See attachments for data and graphic which depicts which graphics should be selected to see the problem. Attempting to select either of the graphic items noted results in the following errors: --------------------------- pservice --------------------------- The given bookmark is either bad or not created by this server (or this version of the server). --------------------------- OK ------------------------

Issues Resolved

October 19, 2016 85

results in bookmark error.

--- --------------------------- GeoMediaCommand(Properties.Activate) --------------------------- Object variable or With block variable not set --------------------------- OK ---------------------------

1-JMFEJP

Tooltip displaying connection info under Legend area rarely works

Tooltip displaying connection info under Legend area rarely works. To reproduce: Steps to reproduce: 1. Open any Geoworkspace 2. Hover over a legend entry in the legend. No tooltip is displayed.

1-JMO6UJ

Incorrect results using Edit Geometry command - Moving vertex results in 2x distance move.

When attempting to move a vertex with Edit Geometry, the selected vertex may be moved twice the intended distance. The problem seems to occur after use of the Move command when a click & drag action was used for the move. Customer / Region reports that the problem can subsequently lead to a application crash but this could not be reproduced by support. See also Attachments for video (.wmv) file. The problem in this case references .mdb format Access GDO warehouse data. The problem also occurs in version 6.1 and 2014. Workaround: Problem will persist while using the Maintain Coincidence option for the active session. User can turn off the Maintain Coincidence option if it is not needed. Workflow to reproduce the problem:

1. Open GeoWorkSpace connected to USSampledata.mdb.

2. Ensure that Maintain Coincidence is enabled.

3. Select a City point geometry.

4. Select the Vector > Move command.

5. Click and drag the point to a new location (a small move is fine but use click & drag method).

6. Select an Interstate geometry.

7. Select Vector > Edit > Edit Geometry 8. Click and drag a vertex Observation: Notice that the edit is twice (2x) the distance of the intended edit.

Observation: Notice that the edit is twice (2x) the distance of the intended edit. In 2014 the problem can also be reproduced by drawing an area feature then use Edit Geometry to move a vertex across the area and over the opposite side boundary.

1-JNGREY

Snap Vector Points option not available after registry edit.

Snap Vector Points option is not available on 2015 Build 10205, after adding the required registry entry which is a regression from 2014, build 143 and higher. The Snap vector points option is enabled based on user preference registry key. Create this registry entry under HKEY_CURRENT_USER\Software\Intergraph\GeoMedia Professional\15.00\PreferenceSet\SnapVectorPoints

1-JNH5SJ

Unable to insert a feature class on 3D view using the insert feature class command.

Workflow:

1) Launch GeoMedia Professional.

2) Select blank geoworkspace.

3) Make an Access Connection USSampledata.mdb.

4) Load 3D window using Toggle 3D from 3D tab.

5) Select insert feature class command

6) Select Cities from the dockable control and try to digitise the feature class and click end feature class using right click. Observations: --------------------------- GeoMedia Desktop ---------------------------

Issues Resolved

October 19, 2016 86

PProService Overflow --------------------------- OK --------------------------- GM Build:16.00.0000.00668 GM 3D build 16.00 79

1-FVUE2R

Need Oracle Performance Fix for Oracle LTT

There was a fixed done for the Oracle data server on GM 2014 to work with Oracle 12c. This addresses poor performance of that data server. That fix is in SP2 version 163. Development mentioned that this fix was not included into the Oracle LTT data server for 2014. The G&T business unit needs that fixed to be rolled up to the Oracle LTT data server for a benchmark we will be doing at Caltrans. We use Oracle LTT connections to temporally enable our LRS maintenance environment. We will need this as soon as possible as we will have to begin preparations for the benchmark. Jon mentioned he thought he could get it done by weeks end. Thank you for your help.

1-JGPJUR

WKT->CSF issue. Projection parameters and datum not loaded, results in incorrect placement of data.

We're using the GeoreferenceService to convert a WKT string to a Coordinate System. The projection parameters on the result coordinate system is all 0. The datum is also incorrectly interpreted as WGS84. Longitude of origin should be: 9:00:00.000 FalseX should be: 3500000 Datum should be: Deutsches Hauptdreiecksnetz WKT was generated from the "GetWellKnownText" function on the CoordSystem object. The WKT string is: PROJCS["DHDN / 3-degree Gauss-Kruger zone 3", GEOGCS["DHDN", DATUM["Deutsches_Hauptdreiecksnetz", SPHEROID["Bessel 1841",6377397.1550000003,299.1528128, AUTHORITY["EPSG","7004"]], AUTHORITY["EPSG","6314"]], PRIMEM["Greenwich",0, AUTHORITY["EPSG","8901"]], UNIT["degree",0.017453292519943299, AUTHORITY["EPSG","9122"]], AUTHORITY["EPSG","4314"]], UNIT["Meter",1], PROJECTION["Transverse_Mercator"], PARAMETER["latitude_of_origin",0], PARAMETER["central_meridian",9], PARAMETER["scale_factor",1], PARAMETER["false_easting",3500000], PARAMETER["false_northing",0]]

1-JJDYL5 The default Name is English. It should be localizable.

The default Name is English. It should be localizable. Add/Edit Feature Class Definitions dialog box >New > General tab "NewFeatureClass"

1-JJDYOD

The default names in Schema Manager are "PickList" is not localizable. Needs to be externalized.

The default names in Schema Manager are "PickList" is not localizable. Needs to be externalized Example Define PickList… > New "PickList" Add to Globals dialog "DeafultNamed Group" "NamedGroup"

1-JJFNMA

Legend Count of All Features incorrect for thematic legend entries.

A customer reported and provided data where we can see that the Count of All Features option is reporting incorrect values for legend entries associated to a range thematic. The problem is a regression from version 2014. For example in 2014 a thematic range of 0.90 to 1.0 may show 19/19 features where the same entry in 2015 may show: 0.90 to 1.0 19/14 features; notice how the count of all features is incorrect in 2015 (there are NO NULL geometries in the data). See Attachments for example screen shot, example data, and video. The data does have geometry problems as noted by Toolbox >Validate Geometry but the problem persist in 2015 even if the problematic geometries are fixed and/or deleted.

1-JJG4CN

Fence Select does not select all features.

Customer has provided data where we can see that attempting to select all features using a Fence selection results in many items that are NOT selected. The problem is a regression from 2014. In the given case the user has 20 legend entries which are part of a thematic classification. Steps to Reproduce:

1. Open GeoWorkSpace using 2015.

2. Use Fence Select to click and drag a large fence around given features.

Issues Resolved

October 19, 2016 87

Observation: Some features are not selected. Problem persists even if all geometry problems are either fixed or deleted.

1-JJHM1H

Hard Coded default names on Validation commands. Need to be externalized.

Hard Coded default names on Validation commands. Needs to be externalized for localization Validate Geometry/Connectivity > Input> Save As dialog "QueryNames" Validate Geometry/Connectivity > Anomalies Tab > Save As dialog "AnomalyDefinitions" Detect Void Areas > Output tab "VoidAreasQueue" Resulted Queued Edit "Void Area" Automated Validation> General "Connectivity" "Geometry".

1-JJK06H

WMS Layers fail to display when using German (Germany) format on Region and Language dialog.

A SR was filed with the following description (with corrections for typos/grammar): “This is a regression from GeoMedia 2014 where this worked fine. Attached WMS_GermanRS.gws demonstrates the problem. Open the GeoWorkspace with English regional settings and the layers will be shown. Then go to Control Panel and configure regional settings to German (Germany). Open the GWS again. The Layers won't be shown and the GeoMedia Map Window remains gray. WMS URL: http://www4.web-map.de/wms/request?SERVICENAME=stfl_lwk-sh&Service=WMS&Request=GetCapabilities Problem is caused by interpretation of Decimal and/or List separator and IMHO is related to Bounding Box calculation when this contains decimal values like <BoundingBox maxy="6.09939e+06" maxx="3.64919e+06" miny="5.91661e+06" minx="3.45425e+06" SRS="EPSG:31467"/>“ I’ve confirmed the behaviour reported in the SR. The steps to reproduce the problem and additional details are provided below: 1. On the Control Panel > Region and Language dialog verify that the Formats tab has the Format set to English (United States). 2. Using GeoMedia 2015 (e.g. 15.00.0000.10184) open the provided WMS_GermanRS.gws that has a WMS connection to the http://www4.web-map.de/wms/request?SERVICENAME=stfl_lwk-sh&Service=WMS&Request=GetCapabilities URL. 3. The ‘Naehrstoffgruppen’ layer will be successfully displayed in the map window. If you check the GDOWMS.log file you will see this GetMap request: http://www4.web-map.de/wms/request?SERVICENAME=stfl_lwk-sh&VERSION=1.3.0&REQUEST=GetMap&SERVICE=WMS&LAYERS=Naehrstoffgruppen&STYLES=&FORMAT=image/png&TRANSPARENT=TRUE&BGCOLOR=0xFFFFFF&EXCEPTIONS=BLANK&CRS=EPSG:31467&WIDTH=590&HEIGHT=553&BBOX=3454250,5916610,3649190,6099390 4. Exit GeoMedia and then select the Control Panel > Region and Language dialog again and on the Formats tab set the Format to ‘German (Germany) the click OK to save the change.

1-H4EPPV

A Manipulate Feature Web Service (WFS) does not support case-insensitive searches.

A Manipulate Feature Web Service (WFS) does not appear to support the filter 'matchCase' attribute to enable case-insensitive searches. The 'matchCase' attribute is allowed on the following binary comparison operators: PropertyIsEqualTo PropertyIsNotEqualTo PropertyIsLessThan PropertyIsGreaterThan PropertyIsLessThanOrEqualTo PropertyIsGreaterThanOrEqualTo ...well as: PropertyIsLike An example use of the 'matchCase' attribute is shown in the filter expression in example #1: <.-- Example #1 --> <ogc:Filter xmlns:ogc="http://www.opengis.net/ogc"> <PropertyIsLike escapeChar="\" singleChar="." wildCard="*" matchCase="false"> <PropertyName>Name</PropertyName> <Literal>*south*</Literal> </PropertyIsLike> </ogc:Filter> This filter should match a property called 'Name' whose value contains any of the following strings: south South SOUTH SoUtH If 'matchCase' is omitted on an operator where it is supported, its default value is 'true'. (That is, do NOT ignore case.) References: Filter 1.1.0 Schema http://schemas.opengis.net/filter/1.1.0/filter.xsd OGC 04-095 - Filter 1.1.0 http://portal.opengeospatial.org/files/?artifact_id=8340 OGC 06-058 Filter 1.1.0 Corrigendum http://portal.opengeospatial.org/files/?artifact_id=15503&version=1

1-H4Z5NJ

Edit Geometry result is incorrect for a triangle area feature in Oracle when vertex is moved twice.

A customer SR was filed reporting that using Edit Geometry on a triangle shaped area feature in Oracle where the feature class coordinate system was set to UTM Zone 11 with a WGS 84 datum would result in incorrect geometry after the edit. To reproduce the issue:

1. Open the UTM11WGS84.gws which has an Oracle Read-Write Connection to UTM11WGS84_JM/UTM11WGS84@TSDB64.

2. Click on one of the UTM11WGS84_JM.AREACLASS1 features displayed in the map window to add it to the select set, then choose the Edit Geometry command.

Issues Resolved

October 19, 2016 88

3. Select one of the vertex handles so that it is highlighted in purple, then click and drag that vertex to the opposite side of the triangle (as shown in the video).

4. Then click and drag the same vertex back to the original side of the triangle. This will result in the incorrect geometry shown in the video.

Notes and Observations: - In this workflow the Edit Geometry command is not exited between steps 3 and 4, but the mouse button is released after the click and drag in step 3, so that the user clicks on the vertex again to begin step 4.

The problem does not seem to occur with Access features that have the same geometry. This can be confirmed by performing the same workflow with the AREACLASS1 features from the UTM11WGS84.mdb Access warehouse. The AREACLASS1 features were created using Output to Feature Classes where the source features were the UTM11WGS84_JM.AREACLASS1 from the Oracle database.

1-HGIJ4U

Attempting to insert ERDAS .img files results in incorrect georeferencing mode selection.

When the user opens the Raster > Insert Georeferenced Images command, by default the georeference mode is 'Automatic'. After the user navigates to a folder with ERDAS .img files, and selects a file to push to the right side of the dialog, the georeferencing mode switches to 'world file'. This should not happen, since there is no world file present in the folder corresponding to the selected image. One of the files in question (ERDAS_large_87MB.img) can be inserted using 'other with internal coordinate system'. Most of them cannot be inserted at all, since there is no world file and, apparently, no internal coordinate system.

1-HHBFS3

Measure Area Command is broken on GeoMedia 3D.

Measure Area Command is broken on GeoMedia 3D. Steps to reproduce:

1. Install GeoMedia Professional and then install GM 3D.

2. Make an Access Connection USSampledata.mdb.

3. Load 3D Window using toggle 3D window from 3D tab.

4. Select Measure Area

Observations: Measure Area throws an PProService Overflow error. --------------------------- GeoMedia Desktop --------------------------- PProService: Overflow --------------------------- OK ---------------------------

1-I59SC2

SQL Server Spatial features created in 2015 do not display in previous versions.

SQL Server Spatial, area and line features created or edited in version 2015 cannot be displayed in previous versions of GeoMedia, even when using the GeoMedia SQL Server Native Spatial R/W Data Server Expansion pack data server. Example workflow:

1. Use 2015 to connect to some MS SQL Native Spatial database such as NS_Alabama in TSDB64.

2. Use Insert Feature command to insert/draw a linear or area feature for examle another county feature.

3. Use version 2014, 2013, or version 6.1 systems connect to same warehouse (using the MS SQL Native Spatial Data Server expansion pack).

4. Add Counties to the map view.

Observation: Features inserted or edited (edit geometry) in 2015 are not displayed in previous versions. The record is present in the record set but the geometry is not displayed. Customer points out that 2015 created geometry also fails to display in open GIS software package QGIS. This could represent a serious issue for sites that are using multiple versions or producing data for other GIS applications.

Issues Resolved

October 19, 2016 89

While GeoWorkSpace objects are often not backwards compatible, we normally do not see compatibility issues for the spatial data itself.

1-I98R63

Validate Connectivity Unbroken Intersecting Geometry results in automation error.

Using the Validate Connectivity command to locate and fix (Auto correct = Yes) Unbroken Intersecting geometry can result in an unexpected error and failure to fix/break unbroken intersections.

The following error is observed when attempting to break water lines where they intersect water valves (a point feature class). --------------------------- GeoMedia Desktop --------------------------- Automation error The object invoked has disconnected from its clients. --------------------------- OK ---------------------------

When using the supplied data set, and the Auto correct option is set to Yes, then the error will occur and no static AnomaliesQueue will be created. The error is not observed and the AnomaliesQueue table is created when the Auto correction option is set to No. Problem also occurs in 2014, but in 2014 we do observe a crash of the application after selection of cancel on the Validate Connectivity dialog. In version 6.1 non-fusion based Validate Connectivity command the process of the same data completes without any errors where linear features are broken successfully where there are water valve point features.

1-FOMHL7

Unrecoverable ‘Encountered an improper argument’ error occurs opening .gws files with layout.

An SR was filed by a customer reporting that they were regularly seeing a failure when opening GeoWorkSpace where an error message with the title GeoMedia Desktop and the text “Encountered an improper argument.” was displayed. Upon researching this issue we discovered that the error occurs when opening a number of GeoWorkSpaces that contain a Layout Window within a single session. Specifically it appears that if you open more than five .gws files that contain a layout in a session the error appears consistently. The error message occurs when opening the sixth .gws. The ribbon bar also fails to display and you are usually unable to permanently dismiss the error message. This means you must use the Task Manager to kill the GeoMedia.exe process to recover from the error.

1-EH0BVX

Issue with Object Space Data Server GUI when invoked from IMAGINE

When we make a connection to Object Space data server in IMAGINE, Code Attribute name and Custom Attribute Names labels are not displayed properly. This problem is also seen in 16.00. Attached is the screen shot

1-EOAH7M

Add Legend Entries fails with very poor performance for MS SQL Native Spatial.

Region has noted a potentially serious performance issue for MS SQL Server Native Spatial data server logic when working with spatial filters and large feature classes. Display a spatial filter and add a point feature to the legend which takes 1 second (great performance). Delete the legend entry, then add the feature to the legend a second time for the same feature. The same feature with the same filter now takes 50 seconds. This is with a point feature of approximately 1 million records. User has point feature of 12 million records and is terminating the GeoMedia session due to lack of response.

1-G99UQI

Low certainty score values returned on short links where valence = 2.

Line to Line linking problem. We are seeing very low certainty scores assigned to small links which occur at internode (valence = 2) locations. It seems that the software is comparing the length of the one link to the entire projected distance of the other geometry resulting in a very low score. Problem background: It was noted in CR 1-FFFCS9 that nodes with valence = 2 (non-intersections) were being incorrectly treated / processed using the Intersection processing logic. A patch was provided where intersection processing logic was applied to only true intersections (valence > 2). The fix however seems to either have caused or uncovered a possible flaw with the logic used for certainty score weight calculations.

1-G9QWMW

Queued Edit Map Window does not use proper map window properties.

User has noticed that simply loading queued edit and navigating to next item in the queue, can cause the Map Window Properties to change to unexpected values that cannot be accounted for in either: a) Queued Edit options or b) Map window settings.

Issues Resolved

October 19, 2016 90

1-G9QWRR

Lose active map window properties after adding conflation link.

User has noticed that adding a conflation link in the active map window and navigating to next item in the queue can cause the Map Window Properties to change to unexpected values that cannot be accounted for in either: a) Queued Edit options or b) Map window settings.

1-GCY9A8

HardCoded message on Manage Edge Match Rules.

HardCoded message on Manage Edge Match Rules. The following strings need to be externalized for the localization,

' Prompt user to use save command before switching rules connections lUserResponse = MsgBox ("Changing rules connections without saving your changes will result in data loss." & vbNewLine & _ "Do you wish to save your changes?", vbYesNo + vbQuestion, gobjGeoApp.Caption).

1-GDG9H7

Validate Area on Cadastral does not work on the decimal point ",".

Validate Area on Cadastral does not work on the decimal point ",". The languages which has decimal point of "," are: European languages as well as Russian. When changing the decimal point to "." (Period), then this command works.

1-GL2AG2

Schema Remodeler: Hard coded default names need to be extracted for the localization

Schema Remodeler: Hard coded default names need to be extracted for the localization NewFeatureSet(frmFeatureSets.frm and ucFeatureSets.ctl) NewField(FuncAttributesBase.ctl) Sequence (modAttrValTableDefs.bas).

1-F4K6XI

Moving a shared vertex on area features will fail after move of fence selected features.

Moving a shared vertex on area features will fail after a group move of fence-selected features. Maintain Coincidence is turned on. Steps to reproduce:

1)Select area feature with shared edge/boundaries (highlight)

2) Select Vector->Edit

3)Move a vertex – successful – both area features adjust

4) Fence select features

5) Move features

6) Return to area feature (highlight)

7 )Select Vector->Edit

8) Move a vertex – fails – both edges move but one edge is offset from the other.” The customer is using an Oracle Object Model Read-Write warehouse, but I have been able to reproduce the problem with both Oracle Object Model and Access warehouses.

1-F55CQV

When editing 2 or more features, it does not maintain coincidence when you add a vertex and move it.

When editing two or more features, the features do not maintain coincidence when you add a vertex and move it. It creates the vertex on both lines. It doesn't matter how many lines are edited, maintain coincidence does not work when selected/enabled. Two features which share one coincident segment when edited do not maintain coincidence if edited. Simple dataset attached with recording showing workflow.

1. Create select set of both features with coincidence enabled

Issues Resolved

October 19, 2016 91

2. Select Edit and click in middle of coincident features and drag up or down

3. Notice one segment which is coincident does not move with the other coincident segment.

1-F6H46K

No tooltip displayed when hovering over legend entries with German language pack.

No tooltip is displayed when hovering over legend entries with German language pack. Unable to get the information for Warehouse connection by hovering over the legend entries. Sometimes it works, but mostly the tooltip doesn't bring back the connection and feature class name for legend entries.

1-F783Y1

GM Feature Symbol File fails to display correctly in GM 2015.

GM 2013 Feature Symbol File fails to display correctly in GM 2015. Regression from GM 2014 because FSM displays correctly in it.

1-FCYE6J

Load Styles > 'Match style names with thematic classes' option is documented incorrectly

The documentation for the Load Styles - ' 'Match style names with thematic classes' states that the style matching is based on the thematic label, but this is incorrect as it is actually based on the thematic value. The documentation for the checkbox currently states: "If the check box is checked, the option tries to match the thematic label with the matching style name before overriding the style." However the 'GMUniqueValueLegendEntry Control Design Specification' states: "If the “Match style names with thematic classes” check box is checked, the command tries to match the thematic value with the style name before overriding the style." I have verified via testing with GeoMedia 2015 that the software matches the behavior described in the design specification. Thus the documentation needs to state that the matching is performed on the thematic value rather than the thematic label.

1-FFFTQM

Can't open geoworkspace customer .gws

When trying to open attached geoworkspace GeoMedia Pro replies with: "Failed to open document”.

1-FFGIMU

German Language Pack 2015 SP1 not translated completely.

There are some missing translations in German Language Pack SP1 for the Layout - Drawing commands which were already translated in German language pack 2015. Please see attached doc file with examples.

1-DQ25R3

BatchPlotting and Define Symbol File Utility crash when invoked on a client machine - XenApp

Two utilities, Batch Plotting and Define Symbol File published through XenApp 7.6 crash on invocation when invoked on client machines. Surprisingly enough, they work fine on server machine where the application is installed and published from. GeoMedia 15.1 was published through XenApp 7.6. The last time we tested GeoMedia on XenApp, the XenApp version was 6.5. This points to a possibility that the issue is specific to newer XenApp version. Crash information: Batch Plotting - Problem Event Name:APPCRASH Application Name:BatchPlot.exe Application Version:16.0.0.557 Application Timestamp:55c286e5 Fault Module Name:PGEOMATH.DLL Fault Module Version:6.3.9600.17736 Fault Module Timestamp:550f42c2 Exception Code:c0000135 Exception Offset:0009d4f2 OS Version:6.3.9600.2.0.0.16.7 Locale ID:16393 Additional Information 1:1abe Additional Information 2:1abee00edb3fc1158f9ad6f44f0f6be8 Additional Information 3:1abe Additional Information 4:1abee00edb3fc1158f9ad6f44f0f6be8 Define Symbol File - Problem Event Name:APPCRASH Application Name:DefSymFile.exe Application Version:16.0.0.557 Application Timestamp:55c283ca Fault Module Name:CFCacheName.dll Fault Module Version:6.3.9600.17736 Fault Module Timestamp:550f42c2 Exception Code:c0000135 Exception Offset:0009d4f2 OS Version:6.3.9600.2.0.0.16.7 Locale ID:16393 Additional Information 1:1abe Additional Information 2:1abee00edb3fc1158f9ad6f44f0f6be8 Additional Information 3:1abe Additional Information 4:1abee00edb3fc1158f9ad6f44f0f6be8

Issues Resolved

October 19, 2016 92

1-DS10RR

Length of linear dynamic segmentation incorrect if use offset.

User has noted that when any offset is used with a linear dynamic segmentation query, the resulting dynamic segmentation geometry (dynseg geometry) is incorrect. The amount of error can vary from small (few meters) to very large (Kilometers). The problem prevents users from obtaining any reliable results if using offset for linear dynamic segmentation. The problem is a regression from version 2014. Example: User wants to map construction zone along a straight line that begins at 0.0 miles and ends at 8.0 miles. The construction zone table has a beginning log mile of 1.0 and a distance (duration) of 5.0. This means the dynamic segmentation geometry should extend from 1.0 to 6.0 along the 8.0 mile route. If no offset is applied, we see the expected result. If we offset by any amount (positive or negative value) such as 1 meter, then the construction zone extends from 1.0 mile to 8.0 miles (2.0 miles beyond where it should have stopped).

1-DS49Z8

Intermittent legend entry tooltip displayed.

Customer has noted and support has confirmed that legend entry tooltips do not reliably work and may seem at best intermittent. After one legend entry tool tip is displayed, the user must navigate the on-screen cursor over the map and back to the legend. Testing also shows that legend entry tooltips display most reliably in a zone just to the right of the legend entry text for record count.

1-E7FTI4

Expected Fusion Links Not Created After Running Create Links.

In certain data cases, the link creation process behaves as if it lacks the capability to create multiple associations to the same link ID. Ultimately this leads to a link table that may have missing link relationships which are needed for processing in other applications such as GeoMedia Transportation MRLS Conflation command. It is not known if all workflows require 1:Many or Many:1 link relations but in the case of MRLS, these type of relations are expected. Workflow using supplied data:

1. Open Linked.gws, correcting paths as needed. The links for this data has already been generated and stored in GMFLinear_Linked (seen in data window).

2. In the Queued Edit Data Window for GMFLinear_Linked, select the Conn1FeatureID column header then right-click to sort the n ascending order.

3. Scroll through the data records and locate Conn1FeatureID 872.

Observation: Notice how there is only 1 link for 872. It's elated to only Conn2FeatureID 1046. We expected that it should be linked to Conn2FeatureID 1043. The same situation occurs for Conn1FeatureID 876, where it fails to have a link to Conn2FeatureID 1000.

1-EDSINF

Customize Ribbon dialog displays wrong icons for commands in add-on application tabs.

To reproduce this problem:

1) First, install the GM3D add-on product (may happen with other add-ons too).

2) Start GM in a new, blank workspace. (The 3D and 3D Effects tabs should be just to the right of the Grid tab on the application ribbon bar.)

3) Right-click on an empty area of the ribbon bar and select the Customize Ribbon command.

4) On the Customize Ribbon dialog, expand the Main Tabs->3D->View group in the treeview list on the right side of the dialog. Notice that the icons shown for the Toggle 3D and New 3D commands are actually G/Tech Interface icons. All of the remaining 3D command icons are assigned to the incorrect 3D command. The icon assignments appear to be shifted by two places. If you select 3D from the Choose commands from pull down menu, the commands are listed with their correct icon assignments. The icon mismatching on the Customize Ribbon dialog appears to be a display-only problem and does not affect the ribbon or command functionality in other places.

1-EFJ4IH Select Set Properties shows

The select set properties shows incorrect record and attributes for the selected geometry in the map view when a Unique Value Thematic is displayed. Problem is a regression from 2014. For example: User has unique value thematic map of US Counties by statename. The user might double-click geometry for Madison County Alabama in the map window but the attribute properties dialog might

Issues Resolved

October 19, 2016 93

incorrect record and attributes.

show Orange County California. If the user does not edit the data and selects OK or Cancel the data is not harmed but users may make incorrect changes based on the invalid attributes displayed on the attribute properties dialog. This should be considered a serious problem. Workflow:

1. Open GeoWorkSpace connect to USSample data.

2. Try double-clicking on a County feature in the map window.

3. Compare the attribute properties to the highlighted data window record.

4. Repeat steps 2 and 3 if required to see the problem if needed.

1-EGCQ8F

Connectivity Validation and gws incompatibility.

GeoMedia 2015 fails to open a gws saved in a previous version, if the gws contains a query based on Connectivity Validation and Union Pipe. More precisely, the gws can be opened, however the query cannot be loaded. Attached is a sample warehouse and geoworkspace. The gws was saved with version 6.1 and it is possible to open it with GM 2013 and GM 2014.

1-EGF10C

CustomFieldsPipe and UnionPipe issues.

The recordset based on a UnionPipe cannot be loaded when the UnionPipe is derived from CustomFieldsPipe and the CustomFieldsPipe has added geometry field without the CoordSystem extension set. There are at least three issues here:

1. The framework displays a meaningless error message which does not help to trace the source of problem at all

2. This used to work without the extension in previous versions

3. If the CoordSystem extension is mandatory for geometry fields, it is not mentioned in the documentation. Attached is a sample command to test. The pipe creation logic is in the Activate method of the command (UnionPipeTest.cs) and the IGMCustomFieldService interface is implemented in CustPipe.cs. The key part of the code is in SetupFields method. The new field is created without the extension. There is also commented line above, which contains the extension. For GM 2014 the code works fine without the extension. Test it without the extension also on GM 2015 to see the meaningless error message. Then change the code so that the CoordSystem extension is passed to the pIGMCustomField.CreateField method. Then it should also work on GM 2015. (The sample requires a connection to USSampleData.mdb).

1-KMYUBT

Right click mouse menu on map window is not working after selecting leader line with static labels.

Right click mouse menu on Map window is not working on GeoMedia with static labels. Steps to reproduce:

1. Launch GeoMedia.

2. Make an Access connection and generate static labels.


4. Select New geoworkspace from File menu.

Observations: Right click context menu is not working.

1-KPS5IF

Grid F1 Help display English help instead of German.

Grid F1 Help displays English help instead of German. German help was included on 2015 SP1. Only Grid commands, F1 help display English Help instead of German help. Other commands on GeoMedia Desktop display German Help.

Issues Resolved

October 19, 2016 94

1-JNNOBD

Schema Remodeler - correction to GeoMedia documentation.

Need correction to GeoMedia Help documentation for Schema Remodeler - Add the directories required to be added to path for Schema Remodeler from the command line (GeoMedia v15.1): C:\Program Files (x86)\Hexagon\GeoMedia Fusion\Program C:\Program Files (x86)\Common Files\Intergraph\GeoMedia\Program Found that C:\Program Files (x86)\Hexagon\GeoMedia Professional\Program is not required for Schema Remodeler (but I believe is required for other utilities such as batch plotting).

1-JQF18C

Error getting field value is thrown when exporting features to GML for Cherokee data.

Invoke GeoMedia and make connection to FGDB dataserver and select the feature Cherokee_CHEROKEE_PlatLines with coordinate system as 4326. Observation: A dialog with error message error getting filed value is thrown.

1-K8QP68

Explode of Microstation V8 DGN elements results in rotating a section of map.

Customer reports a patch still has a problem with a tile rotating if the the .ini file contains the SERVE CELL GEOMETRY:EXPLODE setting. The data being referenced is not part of a Cell. If the .ini file contains SERVE CELL GEOMETRY:TRUE the tile data is not rotated. The data being referenced is not part of a Cell.

1-KBNY4A

Select Set Properties fails to display attributes for features from WFS connection.

The Select Set Properties dialog does not display the attributes for features served from some WFS connections. This is a regression from GeoMedia 2014 where the Select Set Properties dialog displays the successfully displays the attributes from the same features. Additionally other commands in the product display the attributes successfully, so this appears as it could be a problem caused by the conversion of the Select Set Properties dialog from VB. To reproduce the problem, use the steps below. 1. Start GeoMedia Professional 2015.

2. Select the New Connection command and choose WFS Read-Only.

3. For the Web Feature Service click OK to make the connection.

4. Use the Add Legend Entries command add the ‘zones’ feature class to the legend.

5. Double-click on one of the ‘zones’ area features displayed in the map window. Note that there are only two attributes displayed in the Select Set Properties dialog (gml_description and gml_name) and both of these attributes have blank values.

6. Now select the Feature Class Definition command and choose ‘zones’ from the ‘Feature classes’ list.

7. Click the ‘Review’ button and then make the ‘Attributes’ tab active.

Note that there are 18 additional attributes present for the ‘zones’ feature class that were not displayed on the Select Set Properties dialog. Other commands such as ‘Functional Attributes’ and ‘Attribute Selection’ also successfully display these attributes.

1-KGM1RZ

Errors for existing legend entries after disabling caching.

If you turn off (disable/uncheck) caching option for a cache enabled connection, you then get errors for existing legend entries: This method/property not yet implemented. And following message as cursor crosses map window: PClCmd1 --------------------------- Error from QueryInterface for IID_IGMLocatedObjectsCollection

Workflow to see problem:

1. Clear (delete) caches in caches folder (C:\Warehouses\Caches).

2. Create new blank GeoWorkSpace.

Issues Resolved

October 19, 2016 95

3. Establish Cache Enabled connection to Access warehouse, USSampledata.mdb.

4. Add most features (points, lines and areas) to the legend.

5. Exit and Save.

6. Reopen .gws file.

7. Use Manage Data > Warehouses > Warehouse Connections to edit the connection to turn off (disable) caching.

Observations: You get the message listed above.

1-KGXSKV

Caching not performant when legend entries are not set to display on status.

As a GeoWorkSpace is opened, GeoMedia has logic which reviews the display status (Display On, Display Off, Display by Scale status) of legend entries as a means to either load or not load a record set. Testing with exclusive caching of oracle data shows that caching seems to only improve performance for legend entries that are set to Display On. The use of caching where the legend entries are not displayed can degrade performance. Especially if legend entries are set to Display by Scale and the current scale is out of range, then caching may cause a 3x slower GeoWorkSpace open than when caching is disabled. Example observations when caching is enabled: Legend entries set to Display by Scale results in 3x slower .gws open Legend entries set to Display Off results in approximately equal time to open .gws Legend entries set to Display On results in 3x faster .gws open Thematic legend entries set to display by scale is approximately the same or marginally slower

1-JUSBMW

Square Geometry fails to run with “No angles processed” message if select set contains point feature.

The Square Geometry command fails to run if the select set contains one or more point geometries. However if the select set contains only area and/or line features the Square Geometry command runs successfully.

1-GO33OB

Unable to delete source connection on Schema Remodeler.

1. Invoke Schema Remodeler.

2. Select Source tab and make an access connection.

3. Select the connection.

4. Click on Delete Button.

5. Observe nothing happens.

76847_GM

Out of memory error is thrown with histogram command.

Open the *.gws mentioned in datapath and verify whether the warehouse Data paths are correct. Invoke Grid>Layer >Histogram command and select smooth result layer.

Observe: After some time following error message is displayed --------------------------- Error --------------------------- Out of memory --------------------------- OK ---------------------------

1-7O62Y0

Kriging suite command crashes GM2013 to the desktop.

Using the noted data and the following workflow, the Ordinary Kriging Suite command crashes GM2013 to the desktop. - open new workspace, create new access warehouse - import .mfm layer - using layer->Information, set the data units to svy_ft - run ordinary kriging suite - set distance units to svy_ft - set lag separation to 10.000001 (or 10,0000001 on German) - set number of pairs to 10 - press next - turn on covariance and correlogram options - press variogram tab - once processing is complete, press the Anisotropy tab – while the system is processing, quickly click the empty variomap combo box. - Note error - "Variomap Import Failed" - GM Crashes to desktop.

Issues Resolved

October 19, 2016 96

1-95KJGH

GeoMedia crashes exiting the application from the task bar with define new study area in invoked state.

GeoMedia crashes after exiting the application from the task bar with define new study area dialog in invoked state. Steps to reproduce:

1) Invoke GeoMedia.

2) Open a blank geoworkspace.

3) Open a workspace from the file menu.

4) Select define new from the study area panel.

5) Select a study area by rectangular fence by double click. Make sure that the Define new study area is invoked.

6) Exit the Application from the task bar.

Observations: Error exiting the application Source:GMCmdSupt Description method: method of object failed.

1-A27LBL

After import of a DEM (*.dt1) into GeoMedia Grid, DTED1 file appears about 10 times too big.

Customer intends to calculate isolines with GeoMedia Grid. Sourcelayer is a DEM (*.dt1-file) attached. After import of the *.dt1 into GeoMedia Grid, it displays about 10 times too large. If the customer proceeds to calculate the isolines from this layer, the isolines output seem to be calculated correctly. Inserting the image using the Raster > Insert Georeferenced Images command "Insert Georeferenced Images" command in GeoMedia, size and position are totally incorrect - they appear far outside the extents of the geographic .gws.

1-CQ6BVW

Grid > Study Area > Import of 32-bit Float GeoTIFF results in all zero value black rectangle.

In a blank .gws and .mdb, with no study areas defined, Select > Study Area > Import.

1. Browse to folder with attached 32-bit float GeoTIFF elevation file.

2. Select file, GeoTIFF > Next. File is processed without error.

3. Select Grid > Display to view the data - black rectangle.

4. Use drill down or Study Area > List. File is all zero value.

Workaround is to use the Grid > Utilities > Create Elevation Footprints, and then Elevation Workbench to create a new study area.

1-KJ45DZ

Grid Triangulation command does not honor the language set on GeoMedia

Grid Triangulation command does not honor the language set on GeoMedia. If the language is English on Japanese OS, then Japanese dialog box is displayed. If there is no Japanese satellite assembly existed, then English dialog is displayed. I have checked the recent build on Russian with the same situation, English dialog is displayed.

1-KJ4CP4

Grid Triangulation command displays an exception error message when clicking ""Add" button.

Grid Triangulation command throws an exception error message when clicking the "Add" button. This command does not honor the language set on GeoMedia. On English version on Japanese OS, Japanese dialog is displayed. In this situation, this command is working correctly (no exception error) with Japanese satellite assembly. This error seems to be coming from .NET.

Issues Resolved

October 19, 2016 97

1-KJ4CV9

GeoMedia Grid’s Elevation Workbench command contains a menu which is not localized.

The Elevation Workbench command dialog contains a menu. The dialog has been localized (strings for labels and such), but the Menu on the dialog has not. We need to pull the strings from a localized resource and update the Menu Text appropriately.

1-994BCC

Documentation needs to be corrected/updated and remove Symbol and Multiple Pattern Fill doc.

The GM API Object Reference for the Layout Window automation needs to be updated/corrected. It describes a FillStyle object that can have four different types of styles, but two of those are no longer available -- the Symbol Fill Pattern and the Multiple Fill Pattern. The customer wanted to use the Symbol Fill Pattern but it only the simple fill and hatch pattern styles seem to be accessible. The product Documentation needs to be corrected.

1-90DD0X

Spatial Operator of gmsqIsNearestTo with SpatialSubsetPipe always errors.

The customer is using the Spatial Operator of Intergraph.GeoMedia.PPipe.SQConstants.gmsqIsNearestTo with SpatialSubsetPipe. This always gives the error: The input parameter to the method or property was set incorrectly. Code example : objSSP = New Intergraph.GeoMedia.PPipe.SpatialSubsetPipe objSSP.InputRecordset = objRSSPFltRues objSSP.InputGeometryFieldName = "Geometry" objSSP.FilterRecordset = objRSSLine objSSP.FilterGeometryFieldName = "Geometry" objSSP.OutputStatusFieldName = "StatusSSP" objSSP.SpatialOperator = Intergraph.GeoMedia.PPipe.SQConstants.gmsqIsNearestTo objSSP.NotOperator = False objRSSSP = objSSP.OutputRecordset I duplicated the problem using ussampledata

1-8Z1JCB

GeoMedia crashes when KeyIn function is used on an LRS record with no geometry.

LRS Precision Location Service is crashing GeoMedia Pro and GeoMedia Web Map Pro when KeyIn function is used on an LRS record with no geometry. The problem was noticed with data where some LRS records could have null geometries as the backend database process is updating the geometry columns. The LRS Precision Location service should gracefully handle the null geometry condition by raising an error instead of crashing the host application which does not allow the user to save the workspace. Steps to reproduce:

1. Open an existing LRS warehouse.

2. Select any LRS record and delete the geometry field value.

Use LRS Precision Location tool to perform KeyIn by using LRS Key and Measure values from that record. - Notice that GeoMedia crashes once the OK button is clicked on LRS Key In dialog.

1-8XLEQ1

Custom linestyles are wrong when importing G/Tech legend through G/Tech interoperability tool.

Custom linestyles are wrong when importing G/Tech legend through G/Tech interoperability tool on machine with Danish regional setting. On a machine with Danish Regional setting and importing the G/Tech legend the custom lines styles are displayed in the Style Properties dialog as 1763888888888,89;3527777777777,78 which is incorrect. Correct display should be 0,176388888888889;0,352777777777778. It appears the decimal separator is not being interpreted correctly.

1-8DUMT0

GeoMedia fails to display the original Cyrillic layer names from a WMS connection.

When a WMS data server connection is made to a WMS that contains layer names with Cyrillic characters those layer names are not displayed with the original Cyrillic character in the Add Legend Entries command or in other commands that display the feature class names. Specifically instead of seeing the original Cyrillic characters in the name all of the Cyrillic characters are converted to underbars and the name is prefixed with an F character so that it appears like the following “F____________”. Since all of the layer names are converted to underbars with the F prefix it is impossible to distinguish one layer from another via the name presented in GeoMedia. Note that the

Issues Resolved

October 19, 2016 98

‘Add WMS Legend Entry’ command will display a category name in the original Cyrillic characters but the feature class/layer name is the same as in ‘Add Legend Entries’ (i.e. “F____________”.

To see this problem, use these steps:

1. Set your machine to recognize Cyrillic characters by selecting Control Panel > ‘Region and Language’. On the ‘Region and Language’ dialog select the Administrative tab. In the ‘Language for non-Unicode programs’ frame, click the ‘Change system locale…’ button. Then from the ‘Current system locale’ dropdown select ‘Bulgarian (Bulgaria)’. Restart your system as prompted.

2. Open a blank GeoWorkspace.

3. Make a new WMS data server connection .

Select the ‘Add Legend Entries’ command and note that the features are all shown as “F____________”.

1-8NRAHQ

Pressing F1 doesn't display Help content for few commands.

Pressing F1 doesn't display Help content for few commands/ This issue is observed with GeoMedia Professional tier. Commands which do not display help content: File tab > Customize > Customize Ribbon, Home tab > Select Set Properties, Home tab > Review Attributes, Vector tab > Insert Text, Vector tab > Smartsnaps (all Smartsnaps except intersection snap), Labelling > all commands. Help command for none of the commands are working in labelling tab Drawing tab > Links Drawing tab > Insert Object.

1-5FVY8E

Simplify Geometry Command.

A customer has a Shapefile that I have connected to in GeoMedia Professional 6.1. There are 6 polygons which have more than 8000 vertices, which we want to reduce. I ran an Attribute Query against the Shapefile to find the polygons that have a vertice count > 8000. I then ran the Simplify Geometry command against the Attribute Query with a distance of 100m. The resultant query reduces the original polygon to a polygon with five vertices. I tried other approaches with no success. I had really strange results and the only route that seemed to consistently work for me is to push the data to Access, place the six polygons in my select set, create a select set query and then use the Simplify Geometry command. This creates the results that I would expect.

1-54GPW9

GeoMedia Professional crashes on running a simplify geometry query on feature class from AutoCAD dataset.

Steps to reproduce:

1. Using Tools > Display CAD Files command, display AutoCAD 2008 files.

2. Invoke Tools > Simplify Geometry... command.

3. Select ‘AllLayers’ as the features to simplify and check the checkboxes to display the results both in map and data window.

4. Click OK. The below message dialog pops up:

--------------------------- GeoMedia Professional --------------------------- An error was encountered loading data for Simplified AllLayers legend entry. Do you want to continue loading remaining legend entries? --------------------------- Yes No ---------------------------

5. Click Yes on the message dialog.

Observation: As soon as Yes is clicked, GeoMedia Professional crashes.

1-54YK0O GeoMedia Professional crashed with BZ

Steps to Reproduce:

Issues Resolved

October 19, 2016 99

query on union query of Large dataset.

1. Invoke GeoMedia Professional. Create a blank Geoworkspace. Make Access R/W connection to Alabama.mdb.

2. Invoke Analysis Union Query, check on CENSUS_BLOCKS,CENSUS_TRACTS. Click on Advanced button select 'Intersection of schemas from all selected features' as the option and click on Ok button. Click on Ok on Union dialog.

3. Now invoke Analysis>BZ, select union query as the input, choose variable and 10m options ,check on 'Merge touching buffer zones' .Click on Ok button.

Observation: After some time error displays as "Error loading the loading entry....Do you want to continue with loading remaining legend entries". Click on Ok button. Now invoke Analysis>Queries, select the BZ QUERY created above. Click on Properties button. Uncheck 'Merge touching Buffer Zones' option and click on Display button to get the display in both data and map windows. Focus on mapwindow. Observe that GeoMedia Professional crashes.

1-647T8D

1-649EHZ

Simplify and Smooth commands with equal Z value issue.

Issue using the using the Simplify command. Simplify does not correctly simplify the second vertex when the Z values are equal. The Simplify function is not working when there are Z values that change across the line.

80844_GM

Place by Face is creating non-coincident output where arcs are present.

"Place by Face" is creating non-coincident edges where arcs are present in the source face (illustrated by opening the Workspace of "Untitled.gws" and examining the location where the source feature of "City_Limits_Bdy" is shown with the feature of " City_Whatever", which was placed with Place by Face).

The non-coincidence problem seems to be present just where arcs are present in the source data that was identified as the geometry to use as the template for "Place by Face". The original polygon created via tracing is the one found in the above mentioned feature class. This polygon was then placed in City_Whatever via Insert Area by Face. As seen after zooming in to say 1:1000 or so, both polygons overlap but should be coincident. I have not seen this anywhere else in my data where circular arcs exist but drawing processes of those may be different -- i.e. point to point. The original polygon here was not drawn via point to point but more likely arc by whatever.

82918_GM

Within distance 'distance' field needs to provide text feedback.

If spatial query command is run, features are defined, then if the option 'are within distance of' is selected and an invalid distance value is specified, and Ok is selected, normal GeoMedia warning/error messages are not displayed. Instead, the active is set to the distance keyin field. There is no indication to the user why this is occurring. The same result occurs if the Cancel button is pressed. Cancel should exit the dialog, but once again, no feedback is provided to the user. It is much more typical in GeoMedia for a command to provide a reason why an action by the user is not followed.

83226_GM

Connections command needs to delete the items in the Queues QueryFolder

The Connections command has to clean up the items within the Queues QueryFolder, similar to other QueryFolders like Features.

51721_GM

Wrong query is created if there is invalid distance and enter key is pressed.

Wrong query is created if there is invalid distance and enter key is pressed. Steps to reproduce:

1. Create read-write warehouse connection to USSampledata.mdb.

2. Invoke Spatial Query command.

3. Select Cities feature class from the first input feature class combo box.

Issues Resolved

October 19, 2016 100

4. Select "are within distance of" spatial operator and check the box for Not checkbox.

5. Enter abcd for distance.

6. Select Rivers feature class from the second input feature class combo box.

7. Press Enter from the Keyboard.

Observation: Error message is not displayed Spatial query is created with "touch" and NOT operator as can be seen in the Edit Query.

84787_GM

Default Style names in Style Properties dialog are not localizable

Default Style names displayed in Styles tree on Style Properties dialog box are not localizable (such as Area Style, Boundary Styles, Fill Styles and etc.). Those entries are displayed by using Registry entry key names (under HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\GeoMedia Professional\06.01\Drawing System\Styles), not values. Those entries should be separated from registry key names as the same as Style Type entries which have been localized by using Description values on each Registry entry key. The following are displayed in English: Displayed as Registry Key names ( No Description value has been set)

Area Style

Boundary Styles

Simple Line Style

Fill styles

Simple Fill Style

Compound style

Area Styles

Area Style

Boundary Styles (Under Collections)

Smile Line Style

Fill styles

Simple Fill Style

Linear Styles

Simple Line Style

Point Styles

Symbol Style

The below default Style names are also displayed in English as registry Key names (Description value has been set but not used) :

Compound style

Area Style

Image Style

Symbol Style

85504_GM

Duplicate messages on message dialog.

Duplicate messages on message dialog popped when creating Attribute selection for invalid Query. Steps to reproduce:

1. Create an access read-write warehouse connection to USSampledata.mdb.

2. Create an Attribute Query for Rivers with Filter 'ID > 3' and do not display in Map or data window.

3. Invoke Analysis > Queries , select the Attribute Query and click on Properties.

4. On Query Properties dialog, In Filter Edit box replace filter as 'ID > ' and click OK.

Issues Resolved

October 19, 2016 101

5. Close Queries dialog. Invoke Analysis > Attribute selection.

6. Select attribute Query of Rivers under Queries.

Observations: The following message dialog pops up which contains duplicate of message. --------------------------- GeoMedia Professional --------------------------- Unable to set feature class or query. Unable to set feature class or query. Object is invalid for operation. --------------------------- OK ---------------------------

85788_GM

'Object variable or With block variable not set' error pops up.

Error pops up when Spatial Difference is created on Union Query. Steps to reproduce:

1. Create a blank excel sheet blank.xls on desktop.

2. Open a blank Geoworkspace and create a New Warehouse 'GeoMedia.mdb'.

3. Invoke Warehouse > Feature Class Definition and click on attach button.

4. Select type as Excel 97and browse for blank.xls on the desktop.

5. Click OK on attach dialog.

6. Invoke Analysis > Union and select all sheets and click OK on Union dialog.

7. Invoke Analysis > Spatial Difference. Select Union Query in from feature in combo and click on Filter button.

8. Key in F1 = NULL and click OK on Union Query Filter dialog. Click OK on the dialog.

9. Now select Union Query in Subtract features in combo and click on filter button.

10. Key in F1 = NULL and click OK on Union Query Filter dialog.

Observations: The following error pops up. --------------------------- GeoMedia Professional --------------------------- Object variable or With block variable not set --------------------------- OK ---------------------------

86771_GM

Unable to use Queued Edit on copying renamed GMSearch queue from library.

Copy renamed GMSearch queue from library and try to use the same in queued edit throws error message. Steps to reproduce:

1. Invoke GeoMedia Professional blank GWS; Make an access r/w connection to USSampledata.mdb.

2. Invoke View>Search command and select Counties from combo, enter 22 in value to search combo. Click Search button.

3. Create a new library named ‘Lib_Test’ and copy ‘GMSearch Queue’ from GWS to library contents pane using Library organizer dialog.

4. Exit GeoMedia Professional and invoke GeoMedia Professional and connect to blank GWS.

5. Create a new library connection to the ‘Lib_Test’ library and rename Queue from ‘GMSearch Queue ‘ to ‘Test_Queue’ using ‘Rename’ in Library Organizer dialog.

6. Copy ‘Test_Queue’ from library to GWS contents pane using Library organizer dialog.

7. Invoke Tools>Queued Edit command and click on the down arrow of ‘Select a Feature class, Query, or Queue’ combo box.

Issues Resolved

October 19, 2016 102

Observe: The following error message is displayed. --------------------------- Queued Edit Control --------------------------- The requested query is not in the queries collection. --------------------------- OK ---------------------------

85423_GM

Spatial Filter is opening query recordset that has never been on legend.

A customer SR was received stating that when they have queries from an Oracle connection on the legend with the display turned off the queries were still evaluated when a spatial filter was applied. This seems to be confirmed by the entries written to GOracle.log file which shows that when a Spatial Filter is applied a spatially filtered query is created even though the legend entry for that query was not displayed. In addition to this observation I found when researching this issue that applying a spatial filter opens a spatially filtered recordset for queries that have never been on the legend at all (in other words the only place the query exists is in the query folder.)

62208_GM

Overwriting error reporting in AtEOF,

I pulled that latest changes to SDP and SIP from GM to G/Tech. When comparing the changes in G/Tech VSS with the GM source, I noticed that someone discovered and fixed one small flaw in SDP. The fix is in the method STDMETHODIMP GMSpatialDifferencePipe::DIBaseTableCallbackImp::AtEOF(void) the new code looks as follows: wrap up: if (bGeomCached) { ReleaseCacheReference( pThis->m_pInputGeometryField ); ReleaseCacheReference( pThis->m_pMaskGeometryField ); } If the hr contained an error code, the two calls to ReleaseCacheReference() most likely set it to NOERROR, thus it looked as if there were no (or less) output records, instead of reporting the real error.

1-4RHJ5M

Apply Spatial Filter Scans All Members of Category If Only One Member on Map Legend.

While researching Oracle performance issues, a user notes that the logic for Spatial Filter when opening a GeoWorkspace vs. Apply Spatial in active GeoWorkspace is different. Based on results of GOracle.log containing features unreferenced by the GeoWorkspace the user feels that there must be some problem with Apply Spatial Filter command in GeoMedia. Workflow:

1) Create New blank GeoWorkspace and connect Read-Write to Oracle spatial data warehouse.

2) Select Warehouse > Categories and add 1 new Category and add all features as members of the category.

3) Add 1 simple (small number of records) item from the category to the map view.

4) Apply Spatial Filter.

5) Note: Tester used Spatial Filter Options, MBR and Overlap.

6) Exit and Save the GeoWorkspace.

7) Create C:\Temp\GOracle.log.

8) Open same GeoWorkspace and then Exit after data is displayed.

9) Make copy of GOracle.log to new name such as Open_GWS_Log.txt.

10) Create new C:\Temp\GOracle.log.

11) Open same GeoWorkspace and select Apply Spatial Filter by View then Exit the GeoWorkspace (do not save).

12) If you look at the last GOracle.log and search for feature names you will find that for some unknown reason the Apply Spatial Filter by View performed SQL statements for items not on the map legend.

Issues Resolved

October 19, 2016 103

1-4RLNQZ

GeoMedia Professional is crashed when trying to Load Simplified Geometry of ‘Places’ Feature class.

Error message is displayed when tried to create Simplify Geometry of 'Places' Feature class and also GeoMedia Professional crashes when tried to load the 'Simplified PLACES' legend entry. Steps to reproduce:

1. Invoke GeoMediaPro and choose Blank GeoWorkspace.

2. Create Read-Write access connection to “Alabama.mdb”.

3. Invoke Tools>Simplify Geometry.

4. Select ‘Places’ Feature Class for ‘Simplify features in’ dropdown. Enter 100 in the Distance field, and set Unit to ‘m’.

5. Uncheck the ‘Display results in data window’ window checkbox and click on OK button.

Observation:

1. It is observed that below error message is displayed and ‘SimplifiedPLACES’ legend entry displayed is in unloaded state. --------------------------- GeoMedia Professional --------------------------- An error was encountered loading data for Simplified PLACES legend entry. Do you want to continue loading remaining legend entries? --------------------------- Yes No ---------------------------“

2. Click on No button. Select the ‘Simplified PLACES’ legend entry, Right click and select ‘Load Data’ from the menu displayed. GeoMedia Professional crashes.

1-4STQET

Incorrect character replaces standard ... in Mapview menu title.

If the menu entry for either simplify or smooth commands is reviewed in the mapview of GeoMedia Professional, the '...' that follows each command name displays differently from other GeoMedia Professional commands. This is especially obvious if non-English operating systems are in use, such as Japanese and Chinese. The difference can be viewed in English, these two commands are followed by a single character triple dot representation, rather than three actual dots.

70779_GM

Select set to Query on an Outer Join Query crashes GM Pro.

Performing Select Set to Query on any Outer Join queries crashes GM Pro. Steps To reproduce:

1. Invoke GeoMedia Professional (06.00.34.07 Setup) with blank GWS and make a R/W connection to USSampleData.mdb.

2. Invoke Analysis > Join query cmd. Select Counties & State for Left & Right Side of Join respectively.

3. Select Annual Rain from Available attributes to Selected attribute Pairs. Select Full Outer join, display in Map Window and Click OK.

4. Select (Highlight) Join query in Legend and invoke Select by Legend Entry command in Edit menu.

5. Invoke Select Set to Query command and Click Ok.

Observe : GeoMedia Professional Crashes. --------------------------- GeoMedia.exe - Application Error --------------------------- The instruction at "0x77a24844" referenced memory at "0x0000ffff". The memory could not be "read". Click on OK to terminate the program Click on CANCEL to debug the program --------------------------- OK Cancel ---------------------------

Note: Crash observed with all Outer Joins. However, works fine with inner join.

1-6FLIAV Hooking AfterDocumentClose event prevents

Hooking AfterDocumentClose event during Initialize() call on a .NET command with custom enabling conditions prevents workspace from loading.

Issues Resolved

October 19, 2016 104

workspace from loading.

1-7S03LC

Match Geoworkspace and default warehouse coordinate systems.

I have found that the option 'Match GeoWorkspace and default Warehouse coordinate systems' when 'making first connection' and 'creating a new warehouse' is not honored if the initial warehouse connection fails. Workflow to reproduce: With both the 'Match Geoworkspace and default Warehouse coordinate systems' options active on the General tab complete the following workflow:

1. Open GeoMedia, and create a new blank GeoWorkspace. The default coordinate system for this is Geographic WGS84. Confirm by reviewing the 'Coordinate System' from the Home ribbon.

2. Create a new Warehouse connection using any Oracle Read/Write or Read Only dataserver, deliberately getting the host name wrong so that the connection will fail.

3. Go to Warehouse connections, edit the properties on the Oracle connection to the correct host name, and open the connection.

4. Go to legend and add any feature class and it will be displayed in Geographic WGS84, rather than the default co-ordinate system of the Oracle database. Review the coordinate system and confirm that the match to the Oracle connection did not occur.

Check this again in a new instance of GeoMedia, new GeoWorkspace but this time getting the Oracle connection parameters correct first time, and sure enough the data is then displayed in the appropriate coordinate system.

1-7U2BYV

Application crash with Aggregation command by using Select set query.

This issue is latent from GeoMedia Professional 2013 build 242. Perform buffer zone operation. Later choose any feature from bufferzone query and select set query operation. Perform Aggregation operation with select set query and any point geometry. Observed that application crashes. Steps to Reproduce

1) Invoke blank gws, Make an access r/w connection to ‘ussampledata.mdb’.

2) Invoke ‘Buffer Zone’ query, choose ‘cities’ FC. Key-in ‘constant’ value as ‘500’.

3) Click on ‘Ok’ button to dismiss dialog.

4) Select any city from 'buffer zone query' and perform ‘Select set query’ operation.

5) Now Invoke ‘Aggregation’ command, choose ‘Selected set query’ from ‘Aggregate summary features’, choose ‘Route shield’ from ‘detail feature in’ option.

6) Keep default settings, In ‘Output’ tab give ‘Count(*)’. Click on ‘Ok’ button to dismiss dialog. Observe that the error message pops up, finally Application crashes.

1-80R7CH

Using "Place by Circle" in "By Diameter" mode, Circle is placing at Zero height.

Steps to reproduce:

1. Invoke the GeoMedia and create a new geoworkspace.

2. Select the "Stereo -> Stereo On" from the menu. The stereo view displayed.

3. Select the new warehouse and create a new warehouse with an area feature.

4. Go to Tools->Options->Placement and Editing , set the Default height value to some value say 200

5. Select the Placement Mode as "Place by Circle".

Issues Resolved

October 19, 2016 105

6. Select the option as "By Diameter" in the "Place Circle" toolbar. 7. Digitize a circle and observe the geometry information of the circle.

Observation: Z value is setting to 0.0000 even though if we set it for 200. This issue is not reproducible if you digitize the circle in "By Center Point" and "By 3 Points" modes.

1-B4U3N5

Unique Thematic classification gives improper results.

Dynamic Labeling adds extra values to legend. Workflow1: Invoke Add Thematic Legend Entry.

1. Select States and Unique Value Thematic.

2. Select Annual Rain and click on classify.

3. Select Rain and click on classify. Observe three rows are populated with picklist descriptions

4. Select State_name and click on classify. Again Select Rain and click on classify. Observe five rows are populated with picklist descriptions which is not correct.

Workflow2: Invoke Add Thematic Legend Entry.

1. Select States and Unique Value Thematic.

2. Select Rain and click on classify.

3. Click on base style and give pie chart style.

4. Click Ok to dismiss the dialog.

Select States from legend view, right click and select legend entry properties and click on classify button. Observe that row is populated with duplicate values.

1-B3CUML

SQL Server 2012 database picklists not working on some features.

We created a handful of feature classes to capture castle and castle related complexes (e.g. CASTLE_P, CASTLE_S, CASTLE_COMPLEX_P, CASTLE_COMPLEX_S) in our SQL Server Express 2012 database. These features had several attributes with picklists on them (storing an integer but displaying a textual description). I've created a subset of our data model to test it out further. The picklists fail on CASTLE_P, CASTL_P and CAST_P in SQL Server but it worked on CAS_P. I've attached a text file containing a script to create my sample tables, sample picklist tables, and populate them in a SQL Server database as well as add the entries into the GPicklists table. Once created, I used the database utilities to add the feature class metadata (changed geometry type to spatial point and accepted default (WGS84) coordinate system). I then connected to the DB via GM Desktop and then inserted one of each feature classes (Vector > Insert Feature) and then tried to use the picklist. This impacts our workflows (bringing the data in, collection of additional data/population of attributes, and then outputting the data back out to its final format). In the interim we've gone with the CAS or CA feature class name so that picklists work but this adds additional steps for conversions of feature class names.

1-AX4KAE

The dropdown list in the select reference features dialog box does not list any features for select.

The dropdown list in the select reference features dialog box does not list any features for selection.

1-9YPR5I GeoMedia Mobile GPS positions are incorrect with

When running GeoMedia Mobile on a machine where the Format is set to ‘German (Germany) on the Region and Languages dialog the GPS tracking coordinates are incorrect. Specifically the GPS coordinate values are truncated, so that the complete precision of the points are lost. For instance you may only see Degrees and Minutes, with the Seconds ignored or the Seconds will be shown without

Issues Resolved

October 19, 2016 106

German regional settings.

any decimal precision. For instance in my testing a GPS position that should have been displayed at Longitude -86:44:32.496, Latitude 34:48:42.685 was displayed at Longitude -86:44:00, Latitude 34:48:00 instead. When using the German (Germany) Format settings the Decimal symbol is a comma (,) and the List separator is a semi-colon (;). It appears that GeoMedia Mobile is taking these settings into account when interpreting the NMEA stream which is causing the GPS coordinate values to be truncated. When using English (United States) Format settings where the Decimal symbol is a point (.) and the List separator is a comma (,) the correct GPS coordinate position is displayed (i.e. Longitude -86:44:32.496, Latitude 34:48:42.685 in my test case). This problem is evident when capturing features or writing to the GPSLog feature and it can be reproduced with live tracking as well as when using a simulation file.

1-A3Y3UW

Some geometries have their representation altered (fill disappears) based on the zoom scale.

Customer reports when the Map Window display scale is changed some objects lose their fill color.

1. Open provided .gws, connect to provided .mdb file if necessary.

2. Zoom in on displayed features

3. Fill color does not display for features at various zoom scales. Customer used geometries from Oracle and Access tables and the error occurs in both.

1-A24FS7

Define Symbol file utility crashes when a saved .fsm is used to add symbols.

1) Invoke Define Symbol File utility.

2) Invoke Add button and in Add From file dialog select the Files of Type as Microstation V8 Cell file (*.cel/*.dgn).

3) Input the file name as \\GeoMedia\Datasets\Symbols\DefSymFile\V8\Line.dgn.

4) After adding the symbol hit Insert button and hit close on the Add Symbols dialog.

5) Now save the symbol using Save As button to GeoMedia .fsm.

6) Now hit Remove and try to add the .fsm that is saved in step 5.

Observe that the utility crashes.

1-AC5BI3

Text rendered on specific canvas displays artifacts.

We have problem with generating png32 using IID_IGROMemoryCanvas. Color for legend text generated in WebMap is completely different than in GeoMedia Desktop. Example code to generate IID_IGROMemoryCanvas: m_MapServer->get_CoordSysMgr((IUnknown **)&CoordSysMgr); CoordSysMgr->get_CoordSystem(&CoordSys); m_MapServer->get_BackgroundAlpha(&lBGAlpha); TESTHR(m_IGMRenderSetup->SetCoordSystem(CoordSys)); TESTHR(m_RenderViewCanvases->get_Count(&lCount)); for(i = 0; i<lCount; ++i) { CComPtr<IGROCanvas> pCanvas; TESTHR(m_RenderViewCanvases->get_Item(i, &pCanvas)); if (SUCCEEDED(pCanvas->QueryInterface(IID_IGROMemoryCanvas, (void **)&m_MemoryCanvas))) TESTHR(m_MemoryCanvas->Initialize(m_Width, m_Height, groPixelFormat32bppARGB)); } TESTHR(m_IGMRenderSetup->SetCanvasRect(&rRefreshRect)); TESTHR(m_IGMBackgroundColorTool->SetColor(m_BGColor | (lBGAlpha << 24))); When we try to generate png32 without Alfa (using groPixelFormat32bppRGB), color for legend text generated in WebMap are the same as in GeoMedia Desktop, but we lose transparency.

1-9Y2UCN

GMLStorageService produces GML with incorrect coordinates order.

In WCTS implementation it is possible to read correct coordinates order from CSF file, but there is no way to pass that info to GMLStorageService. To allow that, GMLStorageService API needs to be extended - e.g. additional parameter should be added to TransformGML method that will specify the required coordinates order for output GML.

Issues Resolved

October 19, 2016 107

1-956C1D

GeoMedia throws a runtime error while attempting to load the query dialog.

GeoMedia throws a C++ runtime error while attempting to load the query command from the ribbon toolbar. The circumstances when this occurs is probably not typical but it is probable. I have a GeoWorkspace which contains a few hundred queries. For the client I’m working with, it’s required that each highway has its own display LRM query. In total that’s almost 300 queries. These queries are not all displayed on the map at the same time so the user must select the query function from the analysis tab and load the query dialog. It’s understandable that due to the large number of queries this function will take a few minutes to load. However, after about 10 minutes a runtime error is displayed. Below is the error message text:

--------------------------- Microsoft Visual C++ Runtime Library --------------------------- Runtime Error. Program: C:\Program Files ... This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. ---------------------------

1-JMFL7G

Unable to instantiate GeoMedia.Application in Desktop 2015

The customer was trying to create the GeoMedia.Application object (in a Driving GM application) in a C# program, but it always fails: The errors occurs in code line app = Activator.CreateInstance(Type.GetTypeFromProgID("GeoMedia.Application")) as Application; The error is: GeoMedia application does not work anymore. Program event name: APPCRASH Exception code: c0000005 Exception offset: 000a08f2 OP system: 6.1.7601.2.1.0.256.4 Area schema ID: 1031 Additional information 1: 0a9e Additional information 2: 0a9e372d3b4ad19135b953a78882e789 This problem did not occur on version 2014. I also tested the problem in a VB.NET program and received a System Distributed Com error in the Event Viewer: Unable to start a DCOM Server: {2645D1D1-E161-11D2-BFA6-006008A629D9}. The error: "193" Happened while starting this command: C:\Program Files (x86)\Hexagon\GeoMedia Professional\Program\GeoMedia.exe /.

1-IYSZLU

Cannot enter Arabic characters on custom dockable control text field.

The project has a custom dockable control command running in GeoMedia. The command was developed using VB.NET 2010 and is running on Windows 7. When attempting to key-in Arabic characters into a textbox on the dockable control, other non-Arabic characters appear. The dockable control also displays modal forms based on user actions. On the modal forms, Arabic characters can be entered and appear as expected.

1-JELCBZ

"Object is invalid for operation" error when Coordinate system is changed - Modeless command.

Below are the steps to reproduce the issue.

1. Please register GeoMedia custom command attached to the CR and run GeoMedia with blank workspace.

2. Invoke TestCommand button from MyWorkflow, it will add USSample.mdb connection from C:\Warehouse folder to the GeoMedia workspace and opens Window Form with MoveNext, MovePrevious, MoveFirst and MoveLast functionality.

3. Click on MoveNext couple of times and go to Home tab to change the coordinate system of the workspace.

4. Again click on MoveNext or MovePrevious buttons to observe the error "Object is invalid for operation".

1-FX8CU0

canEnable method is calling with same construction aide multiple times.

We observed that canEnable method is calling with same construction aid multiple times when we doing map operations, and also incrementing 1 for each operation. Please see below workflow for your understanding.

1) Add a legend entry on map.

2) Go to Vector tab and select Move command, observer that CanEnable method is called for each available construction aide.

Issues Resolved

October 19, 2016 108

3).Now discard command and reselect Move command, observer that CanEnable method is called two times for each construction aide.

1-DC5PKU

GM crashes on German OS when the length of the path of the GM custom commands .dll is too long.

Customer has created a test command that is registered in a directory such that the path to the DLL and the XML of the custom command are very long file paths. Using these long file paths on a German OS, Windows 7, Desktop 2015 RTD, the custom command is installed. But when the GM GUI is invoked to be opened, it never opens, and there are a couple of errors in the Event Viewer. If the directory name/file path is shortened, no error occurs.

1-DC6POO

Failure to instantiate an instance of GeoMedia as a background COM server.

Description from customer: I understand that in 2013 and forward, an application that internally launches an instance of GeoMedia as a background COM server needs to add an App Paths registry entry for itself and include in the Path value the same data found in the Path value for GeoMedia's App Paths key. This has always worked except now for one machine in our office that previously had GeoMedia 6.1 which was uninstalled and replaced with GeoMedia 2015 SP1. This machine has Windows 7 on it. On this machine, GeoMedia refuses to launch successfully as a COM server.

1-D3G4MW

Windows logging event warning while installing GeoMedia 2015.

Have new Win7 VM (Clean build). I installed GeoMedia Desktop SP1 2015 using Setup.exe and ran as Administrator (but same problem occurs if running Setup.vbs). Support believes this problem is why the Setup often instructs users that a reboot is required. Looking in Event Viewer we see some 200+ Warnings concerning registry keys.

1-CJSJ0G

G/Technology Synchronize Edits fail to appear in G/Tech 10.2

G/Technology Synchronize Edits fail to appear in G/Tech 10.2 After getting into a new G/Tech workspace and connecting to the database using gmsprod/gmsprod@empire I replaced the legend with the Electric Design (default) and then ran the Refresh> Database Changes command. Unfortunately, nothing was updated.

1-BUANP3

Patch fails to remove cleanly.

The 15.00.0000.10126 patch fails to remove cleanly. Files and folders are left in C:\Program Files (x86)\Common Files\Intergraph\Raster. These files are removed when version 15.00.0000.10120 is removed, so this is a regression in the patch only.

1-BY9RF2

Some text from DGN is displaying in the incorrect location.

Some text is not being displayed in the correct location. This can be solved by reassigning the font number to the text inside of MicroStation, then it will display correctly in GeoMedia. What is causing this shift in the first place? What is being incorrectly read that reassigning the font number fixes? We need this to work in GeoMedia without having to rely on MicroStation to make the reassignment in order to resolve in GeoMedia. More information is located in the attachment Some text incorrect placement.docx.

1-C9J8OT

Connection performance very poor on Oracle 12C.

The OOM data server is getting increasingly slower on initial connections to Oracle. This is caused by the use of 4 queries on the initial connection that utilize ALL_OBJECTS. These queries need to be changed (12c only) to return to a normal connection speed.

1-CAEBQA

Need full step-by-step workflow describing the add-on development from scratch of Ribbon Bar.

Customer needs a document describing in detail the full process to add a new add-on in GM 2015. The customer/Intergraph AE made tests with a partner, and the behavior was often really surprising. The new tab correctly appears in the interface, but when invoking a command, it was generic GM commands which were run, (for example, 'New Data Window'). Our need is a step-by-step workflow to create a full add-on from scratch in GM 2015. The current Ribbon Bar Customization for Developers is missing necessary information.

Issues Resolved

October 19, 2016 109

1-C733QP

Using ExportToGMLService with a recordset based off UnionPipe causes memory leaks.

GeoMedia WebMap is using ExportToGMLService extensively and in one case passes to it recordsets which are the output of a UnionPipe. This seems to be causing memory leaks. Using umdh.exe from the Windows Debugging Toolkit shows that the memory allocated is being held by references created in PDBPipe1.GMUnionPipeGRecordset:get_GFields. This does not happen when manually enumerating GFields in code without having a usage of ExportToGMLPresent.

1-C75HZC

Arabic font not displayed properly in Layout Window when copied from Data Window / Properties dialog.

Arabic font is not displayed properly in Layout window when copied from Data window or Feature Properties. The issue was solved in GM2014 patches but appear again in GM2015. I install the latest patch of GM2015” A screenshot was provided of an Arabic text value displayed in the Select Set Properties and the same text string after it was copied into a text box in the Layout Window. The text that is pasted into the Layout Window ‘Text Box’ does not match that from the Select Set Properties dialog.

1-C75P6P GeoMedia 6.1.2.4 and 6.1.11.13 - Uninstall fails.

With a clean machine having GeoMedia 6.1.2.4 installed, I am unable to uninstall the product. It fails after 75% processing. No workaround exists except to clean your machine.

1-BMNTDX

Geometry Information displays incorrectly filename for the raster geometry.

Workflow to reproduce:

1. Invoke GeoMedia Make connection to USSampleData.mdb

2. Add to the legend USSampleImage.

3. Select the image.

4. Invoke Geometry Information command.

Resize the dialog to see entire filename. Observe: Now you can see the added characters at the end of the file name.

1-BK4ODW

GMOUTPUTTOTABLESERVICE fails with System.AccessViolationException.

The GMOUTPUTTOTABLESERVICE execute method fails with System.AccessViolationException. Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. This service fails if a recordset obtained from the GeoMedia.Application is passed in and try to output the recordset to a new database.

1-JTPHVO

Performance problem loading large thematically classified record sets (Open GWS vs. Display On).

Thematic legend entries on the map legend load much slower if loaded when performing a File > Open GeoWorkSpace. If instead the features are loaded by right-click Load or Display, the features load much faster. For example: Have GeoWorkspace with two unique value thematics entries which constitute some 300+ legend entries via Oracle connection. If the thematics are in a “display off” state on the map legend, the GeoWorkSpace file may open in 9 seconds. If we then right-click to set to “Display On” for the 2 thematic entries, the time required is 23 seconds. Total time: Open + Load/Display = 32 seconds. If instead the GeoWorkSpace is opened with the 2 thematics in a display on state, the time required is 2 minutes, 24 seconds to open. Expected that the time required would be opening + viewing to be less than 35 seconds. The problem can be seen with or without Caching, it just takes longer to observe when caching is not used.

1-BC15RF GM15.01 HBA Step 14 of PVT SpatialDiff1AccRW is generating Area

Execute PVT till step 13. Step14 says that the default style that appears is compound style, but,the default style that appears on the style button is Area style.

Issues Resolved

October 19, 2016 110

style instead of Compound style

1-DA10DI

Setting GeoMedia application MainWnd as a parent window.

A standalone custom application’s main Form (.NET) behaves oddly when GeoMedia AppMainhWnd is set as a parent. The form (and also GeoMedia) flickers, cannot be resized, minimized, maximized, closed, and also GM Map Window consumes most of the mouse input. This worked fine on Windows XP and GeoMedia 6.1.

1-BMJ6JO

CONFLATION: Reversing the connections for conflation yields different results.

If you reverse the sources for connection 1 and connection 2 when conflating you will get different results, especially in regards to a long to short segment comparison.

1-K9XEUP

Custom Cmd crash caused by new code statement in GM 2015 Cmd Wizard template.

My two custom commands of Leader Line and Reposition in Labeling are failing due to a new code statement in the Initialize routine of the .vb template and code creation file of the command wizard when creating a View Listener command with Mask of 18 or 24 and possibly other Mask values.

1-KNHOUH

Development Migration from AFM 6.1 to 2015 fails.

Customer is migrating component Intergraph.GeoMedia.PAFM.GEventHandler from AFM 6.1 to Geomedia Professional 2015 and cannot add new command with "create event handle".

1-7173SP

Duplicate Label command fails to copy a label with IFC turned on.

This problem does not occur when IFC is turned OFF. When the Duplicate Label command is invoked, the following error appears: -------------------------------------- Failed to finish execution of this tool because of an unexpected error. Object is invalid for operation. --------------------------------------

All other editing commands work when IFC is turned on, and GeoMedia's Copy command works on the same label when IFC is turned on.

1-7HLZR8

Layout Window / Insert Cartographic Grid: Default Geographic extent values are not complete.

By using the projected Coordinate System 'Switzerland LV95' the geographic extent's properties aren't complete shown in the 'Insert Cartographic Grid' control (Layout Window) if the method 'projected frame' was used by inserting the related map. The proper coordinates appear in Map Graphic Properties. Changing .gws CS to LV03 shows the same behavior. Seems to only relate to using 'Projected Frame' method for defining the map graphic.

1-KYR0DT

Ctrl-Enter for new-line does not work in ‘Select Set Properties’ command dialog.

When using the ‘Select Set Properties’ dialog invoked by double-clicking an existing feature class or selecting a feature and right-clicking to choose ‘Select Set Properties’ does not accept the Ctrl+Enter key combination to add a new line. This is a regression from previous versions of GeoMedia (including 2014). To reproduce the problem, use the following workflow.

1. Open USSampleData.gws.

2. Double-click one of the States features in the Map Window to display the Select Set Properties dialog.

3. Highlight the Value field for the STATE_NAME attribute and attempt to enter two words (such as ‘Test Name’) by entering the word ‘Test’ followed by the ‘Ctrl+Enter’ key combination and then the word ‘Name’. You will find that this is not possible because as soon as the Ctrl+Enter key combination is entered the cursor moves to the next attribute value field (i.e. STAABBRV) in this workflow. In

Issues Resolved

October 19, 2016 111

GeoMedia 2014 this same workflow would have successfully edited the STATE_NAME attribute value to create a string that includes the new-line between Test and Name so that when the value was labeled it would appear with the word Test above the word Name as shown below: Test Name.

1-AQDRB0

Help Example For FORMAT ATTRIBUTE Function Results In Help For Replace Function.

User has noted that the example for the FORMATATTRIBUTE function incorrectly links to help for the

Replace Function. The customer writes: "The Help Link for examples is wrong for the functional

attribute FORMATATTRIBUTE. The example for functional attribute REPLACE is coming up."

Workflow:

1. Analysis Tab, Functional Attributes.

2. Select some feature class and select New button.

3. Press F1 key. Help for Functional Attribute Dialog Box appears.

4. In the second paragraph, select the "Expression Function Packages" link. The Expression

Function Packages list of functions appears.

5. In the Text section, select the FORMATATTRIBUTE expression. Help for

FORMATATTRIBUTE is displayed.

Select the FORMATATTRIBUTE Example link. Observation: The example displayed is for "REPLACE"; expected example for FORMATATTRIBUTE.

Installation Guide Incorrect Information Concerning Language Options for Silent Installation.

Installation Guide Incorrect Information Concerning Language Options for Silent Installation. The Installation guide leads users to believe they can set a RuntimeLCID for configuration of the language. If the language can be configured in silent installation, it’s important to provide an example configuration file (Intergraph.GeoMedia.ConfigurationWizard.exe.config) that demonstrates how the language is defined.

1-JY358F

SmartStore features containing a single point do not display when spatially filtered

SmartStore (.ddc) feature classes consisting of a single point feature do not display when spatially filtered. Problem is considered serious as it represents missing data that may not be noticed by the user. The same issue can also be observed when the .ddc single point feature is published in routines that use spatial filtering. For example, Publishing the .ddc single point feature to WMS fails to publish the point. Workflow: Display smartstore data in GeoWorkSpace map window. Apply spatial filter. Notice how any .ddc layer containing a single point is no-longer displayed.

1-K5VIC2

Time to load record sets 5x slower after reboot when using caching.

After rebooting, the time required to load a record set from a connection where caching is slower and in most cases observed to be more than 5x slower than subsequent loads (even in different GeoWorkSpace sessions). See also attachments for example times observed. Example: User has Oracle connection with caching enabled. The cache files already exist in users’ local client side C:\Warehouses\Caches folder.

1. After first invocation of .gws after reboot, time required to load and display is 3 min and 32

seconds.

2. Now exit the GeoWorkSpace (does not matter if you save or not).

3. Reopen GeoWorkSpace Now notice that the same record set loads in only 36.5 seconds.

Monitoring %TEMP% we see that for each legend entry loaded, that a .tmp file is created. The performance seen in the load time was parallel to the time required for these tmp files to reach their max size (size for .tmp files was constant for each test). Key point: After rebooting the .tmp files were slower to build up even when cache files exist.

1-KZBAUZ Edit Geometry/Precisio

When editing a geometry with a vertex selected, entering the coordinates of another point and holding ctrl when pressing enter should select the vertex at the specified coordinate. Instead the selected vertex is being moved to the new coordinate. I believe this is a problem with the coordinate control. I think it is

Issues Resolved

October 19, 2016 112

n Coordinate Control - missing ctrl functionality.

missing logic to handle ctrl + enter. This happens on 15.1 as well but not on 14 SP2. GM 15 introduced the new WPF precision coordinate control. 1. Digitize a line with several points 2. Select a point and record the coordinates of the point. 3. Select another point. 4. In the coordinate control, enter the coordinates of the first point. 5. Hold ctrl and press enter. 6. The first point should be selected. Instead the second point is moved to the coordinates of the first point.

1-KPA1UX

Originating pipe & Spatial filter pipes are giving different results for the points on border of polygon.

The customer has an EGIS custom Insert Feature workflow implementation. They need to cancel insert feature operation if the newly inserted feature is outside of Geoworkspace spatial filter (Inside operator - 6). To implement above behaviour, the customer tried by using OriginatingPipe and SpatialFilterPipe, but both pipes are giving different results for point features which are on border of spatial filter geometry (This problem is reproducible only for Oracle). OriginatingPipe: Resulting point features which are on boarder of spatial filter geometry as outside of filter. SpatialFilterPipe: Resulting point features which are on boarder of spatial filter geometry as inside of filter.

1-L3S0TK

After upgrade to WebMapEP05 &GM Desktop .10203, text layers no longer display properly in GUI on VM.

After upgrade to WebMapEP05 &GM Desktop .10203, text layers no longer display properly in GM GUI on a VM machine. The problem does not occur on a physical machine with a higher-end graphics card. These text layers are labels created with the "old" GM label creation. If the new Registry Key of Direct2DMode is modified from a value of 1 to a value of zero, it resolves the problem. Dataset and Geoworkspace attached as well as email with screen prints showing the difference in text display with and without the Direct2DMode set to 1 on a VM machine.

1-KDRU4S

Load dgn layout template displays black.

Customer provides MicroStation V7 .dgn that they have previously loaded as a layout template (in version 2014 Desktop). When loading this dgn file the whole screen becomes dark. This is not the case in the Version 14. Tested on 15.00.0000.10203 and 14.00.0002.00143. Steps to reproduce: 1. Open a new gws 2. Create a Layout Window 3. Import the dgn file. Support did note that if the V7 .dgn template is loaded into GMDesktop 2014, then the .gws is saved, this saved .gws displays fine in Desktop 2015. Indicates the error is in the load of the data from the .dgn file?

1-BQKXVR

FGDB read connection errors with "Coordinate System Translation Failure" using EPSG5514.csf file.

FGDB read connection errors with "Coordinate System Translation Failure" using EPSG5514.csf file. Unable to connect to File Geodatabase(FGDB Read only) in GM 2015 and GM 2014. Connection error states "Coordinate System Translation Failure". 1. Open blank .gws. 2. Create a FGDB Read only connection using the TestSM5.gdb and 708953711.ini file. 3. "Coordinate System Translation Failure" after click OK to create the connection.

1-F29OC9

GM2016 HBC :"Object variable or with block variable not set0" error while using "Continue Geometry"

Steps to Reproduce:(GM2016 HBC ) 1.Install GM 2016 668 build 2.Make a connection to "Access" Database 3.Add "SampleImages" legend entry 4.Insert a State feature using "Insert Feature" command 5.Now select the inserted feature and select the "Continue Geomentry" 6.Now try to click on the Image edges Actual Result: throwing "Object varibale or block varibale not set0" error.

Issues Resolved

October 19, 2016 113

1-ANFOZW

Setup - Desktop installs wrong version of .dlls

Starting with version 14.00.0002.143, GeoMedia Desktop is installing files required by GeoSpatial Datapipe to C:\Program Files (x86)\Common Files\Intergraph\GeoMedia\Program\QD. The files delivered are out of date, causing that program to fail to run properly. The correct versions are delivered by GeoSpatial Datapipe, but they are not being loaded when GeoMedia Desktop starts, due to system pathing issues. Per development lead for GeoSpatial Datapipe, problem can be worked around by a registry edit: ---------------------------------------- The problem is due to another PATH key in registry. This sub-key (“Path”) can be found under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\GeoMedia.exe The “Path” sub-key has the following in my system C:\Program Files\Common Files\Intergraph\GeoMedia\Program;C:\Program Files\Common Files\Intergraph;C:\Program Files\Common Files\Intergraph\CoordSystems\Program;C:\Program Files\Common Files\Intergraph\GeoMedia\Program\QD;C:\Program Files\Intergraph\GeoMedia Professional\Program; This path includes the folders that GeoMedia needs to look at and it has C:\Program Files (x86)\Common Files\Intergraph\GeoMedia\Program\QD folder path in it. I tried adding “C:\win32app\ingr\Share” folder path as the first entry before “C:\Program Files (x86)\Common Files\Intergraph\GeoMedia\Program\QD” in this registry key. The GeoSpatial Datapipe (14.00.0035.00004) command works fine after adding this path. You might have to exit and reopen GeoMedia Professional after making changes to the Path variable ---------------------------------------- Please see attached emails. There is no 'installation' or 'setup' component - used 'Cmds - Application - GM' instead.

1-9D66LF

ProgID for MapInfo data server in the help and the generated are different.

GM2015 HS BC Observed this while running Exploratory tests. This is not a regression. Observed the same on GMPro 14.00.0002.00088 Open a blank GWS and make a MapInfo data server connection with IFC on and add some feature classes to the legend. Open the generated cache.manifest file created in the given caches folder and observe that the ProgID is written as MI.GDatabase. But in the GeoMedia Object Reference help file the ProgId of mapinfo data server is given as MapInfo.GDatabase. Also CGP data source list file indicates the progId of MapInfo data server is MapInfo.GDatabase. All the three should be in sync

1-ILEZEJ

Incorrect ProgID documented for ArcView connections

There is an incorrect ProgID for ArcView (ShapeFile) connections in the object reference. Documented: "ArcView.GDatabase" Should be: "AV.GDatabase"

1-AUYMC3

Quick object reference, CoordSystem and GeoMedia 2015.

System continue shown as In the section Quick Reference Object that is in the developer help of GeoMedia 2015 for the CoordinateSystem components continue saying Typelib: PCSS. This is incorrect.

83024_GM

Focus shifts to last attribute on clicking 'Select All'

Steps To Reproduce:

1. Invoke GMPRo and connect to USSampleData.mdb.

2. Invoke Analysis > Attribute Selection command.

3. Select States for 'Select Attributes from' field.

4. Select 'Pop'.

5. Click 'Unselect All' and then 'Select All'.

Observe that focus shifts to the bottom most attribute, unlike in 6.0 where the focus shifts to top most attribute. This causes a difference in enabling of arrows.

Issues Resolved

October 19, 2016 114

GEOMEDIA IMAGE PROFESSIONAL CR # Summary Description / How to Reproduce

1-QVUOYO

Image Light Table Plus 2014 22.0.13.8, is not annotating the accurate GeoCusor location

In Options, set geographic to DMS(lat/lon). Open a sample image (I used Boston area image_1.ntf) Select Cursor Tracking --> input the coordinates --> click on arrow (Go to location specified in the coordinate fields) click Button --> Drop a marker at the cursor track location.

The input coordinates is for example 42 21 21 N, 71 04 04 W but the annotation is showing 42 21 20.97 N 71 03 53.28 W. Customer SR reports their location information : "The input coordinates is for example 35 25 25 N, 031 35 35 E the annotation is showing 35:25:32 N 031:35:14 E."

1-A3YGXZ

Installation of Microsoft Visual C++ 2005 Service Pack 1 redistributable package (KB 2538242).

GMIP 15.0 includes VC++ redis. SP1 and installs during GMIP setup. Since all the GMIP 15.0 sources are upgraded to VS 2013, VC++ 2005 redistributable is not required. Confirm this by removing from the setup and test.

1-9OIAPI

Unable to Insert CIB/CADRG image.

Open a new/blank .gws. Connect to world.mdb. Place "countries" feature on legend. Create a new warehouse (I called mine CIB_CADRG2.mdb). Select the command Image Pro > Load Images from > CIB/CADRG. Browse to location of provided CIB/CADRG dataset, browse down the file structure until you get to the A.TOC file (CIB5\rpf\A.TOC). Select this .TOC file. Change the Warehouse to CIB_CADRG2. Select OK. You will see a number of error messages: 1. In createtransformrecordset : Item not found in collection 2. Err:Error: No recordset was provided. Customer is unable to load his CIB/CADRG image. This error may relate to the default Feature class: name. It seems the auto increment logic is screwed up. Even when this image is the first one in a new warehouse, the default feature class name is something like 'Image1113', apparently it remembers from session to session what the last CIB/CADRG feature class name was and increments it, rather than starting at 'Image1' when a new .gws and new warehouse is selected.

1-A3T7QL

Unable to Load Image in a saved GWS if workspace has Closed warehouse connection.

Close one of the warehosue connection', save GWS. Now, unable to Load images on re-opening GWS. Steps: 1. Open blank GWS 2. Make r/w connection ot USSampledata.mdb 3. Make another r/w connection to MadisonCountyAL.mdb 4. Save and Exit GWS 5. Re-open saved GWS 6. Invoke Load Image from Browse and select - boston area image 1.ntf (delivered w/ ILT) - Check 'Display in Mapd window' - Check 'Create Virtual Mosaic' Run the command 7. Observe, Image opens in Image Window but it didn't inserted in warehouse, not displayed in Map window.

Issues Resolved

October 19, 2016 115

GEOMEDIA 3D CR # Summary Description / How to Reproduce

1-CHDIPO 3D Effects Date/Time slider is visible in 2D when opening a GeoWorkspace.

When a GeoWorkspace that contains a 2D and a 3D window and the 2D window is in front of the 3D window, the Date/Time slider is in front of the ribbon tabs in the 2D window.

1-AUOBMB Help URL’s go to wrong web site.

Click on Help URL’s found in the CHM file.

1-AAD85F

Edit Flight Path toolbar can cause GeoMedia to crash on exit.

1. Invoke GeoMedia with a blank workspace.

2. Toggle to 3D.

3. Invoke the Edit Flight Path toolbar.

4. Open a new blank workspace from the File menu without exiting GeoMedia.

5. Invoke the Edit Flight Path toolbar.

6. Exit GeoMedia.

1-AA2KGI

ERDAS APOLLO connection - image randomly disappears/reappears from legend.

Zoom in and out on an image from an ERDAS APOLLO WMS service, the image served up by the ERDAS APOLLO WMS service will randomly disappear/reappear in the 3D map window.

1-AA2KDY

The Flight Path control is caching a Flight geometry even when nothing is selected in the active map window.

When the Flight Path control is visible, de-selected geometry is being cached.

1-9DCQMS GeoMedia 3D 2014 has an SSL vulnerability.

GeoMedia 2014 includes OpenSSL 1.0.1c. As per OpenSSL (http://www.openssl.org/news/secadv_20140605.txt) mitigation for the latest CVEs currently means upgrading OpenSSL 1.0.1_ to 1.0.1h.

1-8MJOCB

Thematic display by scale legend entries can fail to load in 3D.

Legend entries defined as thematic and also set to display by scale can fail to load their data when displaying a 3D view. This can occur when loading a workspace persisted in 3D or when changing the display mode after conversion to 3D (when the legend features are currently outside the viewable display scale range). This can be avoided somewhat by carefully adjusting the workflow to convert to 3D after properly setting up the legend entries, but many datasets already configure such displays and will easily encounter the problem.

1-7ZO3HP

Measure Distance command dynamics do not initially display in an empty GeoWorkspace for GeoMedia 3D.

When running the Measure Distance command in a 3D window, the dynamics (polyline and text) do not display when using an empty GeoWorkspace. The dynamics will begin to display when (1) data is loaded into the legend, (2) a zoom in/out operation is performed or (3) the focus is changed from the GeoMedia application to another program (and back).

Issues Resolved

October 19, 2016 116

1-62ZM8B

Linear feature with a geometry collection fails when used as select set input to Fly Flight Path command.

If a linear feature that has a geometry collection is input as a select set to Fly Flight Path command, the command will fail to use the feature and return the error message: GeoMedia Professional: One or more selected features are not linear. See notes for data and feature record details.

1-62ZM84

Positive speed value returns error noting value must be greater than 0.

If a positive decimal value such as 0.01 is entered in the Speed field on the Options dialog, an error is returned when the user exits the field. The error message is not accurate, since 0.01 is greater than 0. Error says: Invalid speed value. Enter a value that is greater than zero.

1-60XVMJ

GeoMedia 3D Options command should include controls to allow operator to control underground mesh location.

3D platform software allows the user to define the underground location of the mesh below the surface. This is necessary for modelling 3D objects underground, such as utilities or other structures. This should be added in the 3D Options dialog.

1-5RU3W2 Enable threat dome functionality within 3D platform.

3D platform software allows the user to define threat domes. This should be added to the GeoMedia 3D product.

1-5RU3VW Enable viewshed functionality within 3D platform.

3D platform software allows the user to define viewsheds. This should be added to the GeoMedia 3D product.

1-5R1AJ9 Files are left in GeoMedia 3D product folder after product is uninstalled.

If GeoMedia 3D product is uninstalled after the Import 3D Object Utility has been run successfully (i.e. output 3D files), a collection of files will be left in the GeoMedia 3D folder.

1-5QQNB3 Accuracy of selection must be sufficient to support security workflows.

Security workflow requires accurate point selection (right click must equal world point). It appears that GeoMedia 3D may be modifying this.

1-5QQNAV Feature highlighting speed must be sufficient to support security workflows.

Feature highlighting can experience delays when in the 3D map window.

1-5Q6TFM Need to have the capability to interact with security products in GeoMedia 3D.

Would like to be able to control the security products (cameras, alarms, events & units) similarly to how this is done in GeoMedia, using the GeoMedia 3D map window.

1-5NSX8B

Need control over the responsiveness of navigation hot keys and user experience.

The speed or responsiveness of the hot keys (S, X, A, Z, Q, W for example) varies according to the workspace. They are inconsistent. In some cases they are too fast to be useful. The user needs to be able to control the responsiveness of the hot keys and they should not vary among different workspaces. Need to expose minimum altitude, underground surface, select navigation speed (keyboard and mouse), select navigation speed (joystick).

1-5J2WS5

Cannot select GSM security features in map window if window is 3D.

Geospatial Monitor has a requirement to be able to run using a 3D window. Currently, if the user attempts to select an event or unit in the 3D map window, it is impossible to select/locate a graphic element utilizing a single select mode. The event feature is a 2D symbol where the settings are offset using a relative altitude and the display facing upright option whereas the Unit feature/symbol is a 3D symbol of a police car (HonoluluCrwnVic.xpl). If the user attempts to select items in the 3D map window using a fence selection method, it is only slightly better, if there are multiple items within a close proximity, the items within the fence may be selected (selected) but they are not all located (visible on GSM's PickQuick style dialog), one feature might be located and the others at that location are missed. All of the items are fully selectable/locatable in a 2D window but are not in a 3D window.

Issues Resolved

October 19, 2016 117

1-5H5NRA Improve 3D Measurement tools within GeoMedia 3D.

Users want the ability to measure distances in 3D such as true distance, surface distance, vertical height, vertical depth etc. in the 3D map window.

1-5FISMN GeoMedia 3D uninstall does not completely remove product files.

If uninstall is run for GeoMedia 3D, some folders and files may be left after the process has completed. These files need to be removed as part of the uninstall process.

1-5F9JCI Request ability to visualize/interact with point cloud data in GeoMedia 3D.

The user should have the ability to read, stylize, measure, and visualize extremely large point cloud datasets within GeoMedia 3D.

1-5AB724

Tutorial data 3A extrusion with translucency flickers when zooming in/out.

1. Use the GeoMedia 3D exercise 3A tutorial data.

2. Define the buffer zones base feature for the thematic legend entry as extruded areas.

3. Define the fill with a translucency of 30 to 40.

4. Toggle to 3D.

5. Zoom in and out of the view.

Notice that the colors flash or flicker, and do not display a consistent color.

1-58N284 Fly Flight Path command needs a time line or progress indicator.

There needs to be a time line or progress indicated that also includes the start and end times, with a progression indicator.

1-55UO8Q

3D platform settings need to be available in the GeoMedia 3D Options command.

There are a number of important optional settings available in the 3D platform that can affect the performance, correctness and control of the model by the user. Currently, these are unavailable in GeoMedia 3D. Some of these need to be added to the Options command.

1-DB31NP Flight default values on option dialog do not honor Default settings button.

The controls on the Options dialog -> Navigation tab -> Flight defaults group box do not return to their default values when the Default settings button is selected.

1-BL9537

Surface Optimization fails in certain scenarios.

In some cases surface optimization can fail when using the Add surfaces command in tandem with the Optimize surface option. The cause of the error is: Unable to cast COM object of type 'SLMpu.CreateMPUClass' to interface type 'SLMpu.ICreateMPU'.

1-AA2KHD

Previous location is not being saved when exiting a GeoWorkspace and then returning.

Open a GeoWorkspace. Toggle to 3D. Navigate to a location. Make sure tilt is used. Save the GeoWorkspace. Exit GeoMedia. Re-open the GeoWorkspace. Notice that the location is different.

1-7P00MN When toggling from 2D to the 3D window, features in the select set are removed.

Open a GeoWorkspace. Select several features. Toggle to 3D. Notice that the select set is lost (i.e. the features are no longer selected).

1-60DB4J

The Measure Distance/Area command is not working properly for "Area" method in the 3D map window.

1. Open a Blank workspace. 2. Make an R/W warehouse connection to ussampledata.mdb. 3. Select Legend >Add legend entries>warehouse connection>add some

4. features (river, cities, states). 4. Toggle to 3D. 5. Select Tools>Measure Distance/Area. Set "Method" value to Area.

Check "Measure in 3D". 6. Click on the map window at different point to complete an area. After

clicking on the last point without moving the cursor, observe that the

Issues Resolved

October 19, 2016 118

value shown in the map window is different from the value shown in the "Measure Distance/Area Dialog Box".

1-5GPECT

The Name Location command does not save location correctly.

1. Open a workspace. 2. Navigate to a location. 3. Run the Name Location command and name the location. 4. Navigate to another location. Use the previous named location. 5. Observe the location is different.

1-AA7OM3

Three files being incorrectly delivered to "...\GeoMedia 3D\Program\EN" folder during Setup.

GeoMedia 3D is delivering three files to the “GeoMedia 3D\Program\EN” folder that are not supposed to be there. All the GM 3D tutorials are supposed to be delivered via the Web. These files also didn't get updated with the Hexagon branding.

1-C1MK37

Can't use Date/Time slider in Illumination tab in Chinese GeoMedia 3D 2015

The Date/Time Slider in Illumination tab of 3D Effects can't be adjusted on a Chinese OS with Chinese language pack installed.

If I adjust the time by this tool, GeoMedia 3D and GeoMedia would crash to desktop. All other commands/effects are working as designed.

1-EGG1YP

Improve performance of refresh for features in 3D that are outside of the 2D map window client area.

In the course of fixing another issue (GM-35305 - Editing features in 3D that are outside of the 2D map window client area are not updated), the performance of editing features when using very large datasets was negatively impacted. The fix should be revised to ensure that only the feature(s) being edited are refreshed. Currently, only the edited feature is rendered, but the workflow may cause a pass over the entire legend entry of the feature. In large datasets, this can result in double digit seconds (to even minutes) of processing time. An enhancement can reduce this processing to an instantaneous update.

1-F2HA6L

3D Options for Tilt and Rotations are not working properly.

1. Set the Tilt and Rotation properties on the 3D Options->Navigation tab to a value other than zero.

2. Click the Apply button and then the Close button. 3. Bring up the 3D Options dialog again and notice that the Tilt and

Rotation properties are not set to the entered values.

1-F2HA8U

3DML command crashes during shapefile export step

Steps to reproduce:

1. Select a large building dataset to convert 2. During the first step of the conversion process, click on GeoMedia.

Observe the screen will go white with the message: GeoMedia has stopped responding.

1-F2HADJ The extrusion height for 3D polygons and opaque extrusions should be the same

When the "Use geometry Z values" option is NOT selected, the height for 3D polygons and standard extruded footprints are not the same. They should be the same for all combinations of altitude settings.

1-F2HAHF The display for 2D polygons can disappear when the translucency value is changed

Sometimes the display for 2D polygons will disappear when the value for certain style properties are changed (i.e. the translucency, etc.).

1-FKARLD Cannot locate viewshed objects that partially fall under the terrain.

It is difficult (or impossible) to properly locate viewshed objects when part of the viewshed (due to pitch angle, etc.) is underneath the surface.

1-FKD3QA Create HPC command fails with large LAS files containing more than 2 billion points

Create HPC command fails with large LAS files containing more than 2 billion points. Our software was using a signed integer to contain the "number of points" value and it was overflowing.

Issues Resolved

October 19, 2016 119

1-FOH8Y3

Clicking on Style properties resulting in error on opening saved gws

Steps to reproduce:

1. Copy GeoMedia 3D Tutorial to C:\ drive.

2. Open Exercise 4c.gws or "C:\GeoMedia 3D Tutorial\GEOWORKSPACES\Exercise 6a.gws"

3. Click on Traffic lights entry icon to invoke Properties.

4. Click on Properties button.

Observe that error displayed as PStylCtl, Property Animated not found

1-FONH5R

KMZ files are not rendering properly, Google Earth seems to have a much better rendering.

GeoMedia 3D customer wants to see the KMZ files in GeoMedia 3D. We did try the import option but they do not render well within 3D, however the same thing renders pretty well in Google Earth. We have tried this with the latest 3D setup. Can share the KMZ file, not able to upload it via web portal currently.

1-FUABZF

Grid Layer displays in 3D map window even when its display is toggled off.

1. Open a GWS with MDB that has some data. 2. Create Study Area. 3. Rasterize a Feature Class 4. Toggle to 3D Window 5. Display the Grid layer in the map window. 6. Toggle Grid Layer display off. 7. Use the Grid > Legend command to apply new color sequence.

Note that when the OK button is clicked, the Grid layer is displayed even though it is toggled off.

1-JJO3HX

Getting a Type mismatch error defining target .csf for .las file

Steps to reproduce:

1. Open the Construct Hexagon Point Cloud dialog and add the auswahl_innen.las file.

2. Define the source .csf using sourceCSF.csf

3. Define the target .csf using targetCSF.csf, might get a mismatch error.

4. If no error, click Ok on the Construct Hexagon Point Cloud dialog and get a "Could not load file or assembly "Intergraph.GridAnalysis" error message. See attached snapshot.

Clicking Ok on the error dialog the completed processing dialog displays, but no .hpc file is created.

1-JVADEB

GM FSM Symbols do not appear in GeoMedia 3D map window.

To reproduce:

1. Open Exercise3c.gws and notice Sewer_Man_Holes in legend with "Church-bold" GM Feature Symbol File assigned.

2. Toggle to 3D map window and notice none of the man holes are displayed.

1-JWXKQP

GM 3D > HPC PointClouds > Construct. Command errors off when ingesting .las/.laz. Version conflict

While trying to construct an HPC point cloud from the attached .laz file, we see this error:

Could not load file or assembly 'Intergraph.GridAnalysis, Version=3.2.0.0, Culture =neutral,PublicKeyToken=c7a31bd12735fde5' or one of its dependencies. The system cannot find the file specified.

October 19, 2016 120

1-KHE5UZ

Viewshed eye point with a 3D model does not clean up after editing operations.

When a viewshed feature eye point (point symbol) is replaced with a 3D model, its display is not properly cleaned up during all delete and editing operations (for example):

1. Delete feature

2. Move feature

3. Attribute/property updates (which affect the rotation of the point symbol feature)

This issue results in extra 3D objects being left in the view with each operation. The 3D view must be closed and re-opened to clear the extraneous objects.

IG-3200

Problem trying to use Motion Video Analyst while GeoMedia 3D is installed

To reproduce this problem:

1. Start GeoMedia in a workspace with multiple map windows. 2. Click on the title bars of different map windows to change the active map window. 3. Display the Video Center dialog and change the video map window setting.

An error message will be displayed indicating that a COM object has been separated from its underlying RCW.

If GM3D is uninstalled (or its startup command is disabled in the registry), then the workflow steps above will work fine.

DEPRECATED

WINDOWS 8.0 Support for the Windows 8.0 operating system is no longer supported.

32-BIT OPERATING SYSTEMS Windows 7 32-bit, Windows 8 32-bit, Windows 8.1 32-bit and Windows 10 32-bit are no longer supported.

MGE DATA SERVER As previously announced with the release of GeoMedia 2015, this data server is no longer supported with GeoMedia 2016.

FRAMME DATA SERVER As previously announced with the release of GeoMedia 2015, this data server is no longer supported with GeoMedia 2016.

Deprecated

October 19, 2016 121

ARCINFO DATA SERVER As previously announced with the release of GeoMedia 2015, this data server is no longer supported with GeoMedia 2016.

GEOGRAPHICS DATA SERVER As previously announced with the release of GeoMedia 2015, this data server is no longer supported with GeoMedia 2016.

About Us

October 19, 2016 122

ABOUT US Hexagon Geospatial helps you make sense of the dynamically changing world. We enable you to envision, experience and communicate geographic information. Our technology provides you the form to design, develop and deliver solutions that solve complex, real-world challenges. Ultimately, this is realized through our creative software products and platforms.

CUSTOMERS. Globally, a wide variety of organizations rely on our products daily including local, state and national mapping agencies, transportation departments, defense organizations, engineering and utility companies, and businesses serving agriculture and natural resource needs. Our portfolio enables these organizations to holistically understand change and make clear, reliable decisions.

TECHNOLOGY. Our priority is to deliver products, platforms and solutions that make our customers successful. Hexagon Geospatial is focused on developing technology that displays and interprets information in a personalized, meaningful way. We enable you to transform location-based content into dynamic and useable business information that creatively conveys the answers you need.

PARTNERS. As an organization, we are partner-focused, working alongside our channel to ensure we succeed together. We provide the right platforms, products, and support to our business partners so that they may successfully deliver sophisticated solutions for their customers. We recognize that we greatly extend our reach and influence by cultivating channel partner relationships both inside and outside of Hexagon.

TEAM. As an employer, we recognize that the success of our business is the result of our highly motivated and collaborative staff. At Hexagon Geospatial, we celebrate a diverse set of people and talents, and we respect people for who they are and the wealth of knowledge they bring to the table. We retain talent by fostering individual development and ensuring frequent opportunities to learn and grow.

HEXAGON. Hexagon’s solutions integrate sensors, software, domain knowledge and customer workflows into intelligent information ecosystems that deliver actionable information. They are used in a broad range of vital industries.

Hexagon (Nasdaq Stockholm: HEXA B) has more than 16,000 employees in 46 countries and net sales of approximately 3.4bn USD. Learn more at hexagon.com and follow us @HexagonAB.

About Us

October 19, 2016 123

Copyright

© 2016 Hexagon AB and/or its subsidies and affiliates. All rights reserved. Hexagon has registered trademarks in many countries throughout the world. Visit the Trademarks Page for information about the countries in which the trademarks are registered. See Product Page and Acknowledgments for more information.

Product Documentation Terms of Use

PLEASE READ THESE TERMS CAREFULLY BEFORE USING HEXAGON GEOSPATIAL’S DOCUMENTATION ("DOCUMENT"). USE OF THIS DOCUMENT INDICATES ACCEPTANCE OF THIS AGREEMENT WITHOUT MODIFICATION. IF YOU DO NOT AGREE TO THE TERMS HEREOF ("TERMS"), DO NOT USE THIS DOCUMENT.

Use Of This Document

All materials in this Document are copyrighted and any unauthorized use may violate worldwide copyright, trademark, and other laws. Subject to the terms of this Agreement, Hexagon Geospatial (a Division of Intergraph Corporation) and Intergraph’s subsidiaries ("Intergraph") hereby authorize you to reproduce this Document solely for your personal, non-commercial use. In consideration of this authorization, you agree to retain all copyright and other proprietary notices contained therein. You may not modify the Materials in any way or reproduce or publicly display, perform, or distribute or otherwise use them for any public or commercial purpose, except as specifically authorized in a separate agreement with Hexagon Geospatial.

The foregoing authorization specifically excludes content or material bearing a copyright notice or attribution of rights of a third party. Except as expressly provided above, nothing contained herein shall be construed as conferring by implication, estoppel or otherwise any license or right under any copyright, patent or trademark of Hexagon Geospatial or Intergraph or any third party.

If you breach any of these Terms, your authorization to use this Document automatically terminates. Upon termination, you will immediately destroy any downloaded or printed Materials in your possession or control.

Disclaimers

ALL MATERIALS SUPPLIED HEREUNDER ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. Hexagon Geospatial does not warrant that the content of this Document will be error-free, that defects will be corrected, or that any Hexagon Geospatial Website or the services that make Materials available are free of viruses or other harmful components.

Hexagon Geospatial does not warrant the accuracy and completeness of this Document. Hexagon Geospatial may make changes to this Document at any time without notice.

Limitation Of Liability

IN NO EVENT SHALL HEXAGON GEOSPATIAL BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY YOU OR ANY THIRD PARTY, WHETHER IN AN ACTION IN CONTRACT OR TORT, ARISING FROM YOUR ACCESS TO, OR USE OF, THIS DOCUMENT.

Indemnification

You agree to defend, indemnify, and hold harmless Hexagon Geospatial, its officers, directors, employees, and agents from and against any and all claims, liabilities, damages, losses or expense, including reasonable attorneys’ fees and costs, arising out of or in any way connected with your access to or use of this Document.

Use Of Software

Use of software described in this Document is subject to the terms of the end user license agreement that accompanies the software, if any. You may not download or install any software that is accompanied by or includes an end user license agreement unless you have read and accepted the terms of such license agreement. Any such software is the copyrighted work of Hexagon Geospatial, Intergraph or its licensors.

Links To Third Party Websites

This Document may provide links to third party websites for your convenience and information. Third party websites will be governed by their own terms and conditions. Hexagon Geospatial does not endorse companies or products to which it links.

http://www.hexagongeospatial.com/legal/trademarks

About Us

October 19, 2016 124

Third party websites are owned and operated by independent parties over which Hexagon Geospatial has no control. Hexagon Geospatial shall not have any liability resulting from your use of the third party website. Any link you make to or from the third party website will be at your own risk and any information you share with the third party website will be subject to the terms of the third party website, including those relating to confidentiality, data privacy, and security.

Trademarks

The trademarks, logos and service marks ("Marks") displayed in this Document are the property of Hexagon Geospatial, Intergraph or other third parties. Users are not permitted to use Marks without the prior written consent of Hexagon Geospatial, Intergraph or the third party that owns the Mark. "Intergraph" is a registered trademark of Intergraph Corporation in the United States and in other countries. Other brands and product names are trademarks of their respective owners.

Find additional trademark information.

Procedure For Making Claims Of Copyright Infringement

Notifications of claimed copyright infringement should be sent to Hexagon Geospatial by mail at the following address: Intergraph Corporation, Attn: Intergraph Legal Department, P.O. Box 240000, Huntsville, Alabama 35824.

US Government Restricted Right

Materials are provided with "RESTRICTED RIGHTS." Use, duplication, or disclosure of Materials by the U.S. Government is subject to restrictions as set forth in FAR 52.227-14 and DFARS 252.227-7013 et seq. or successor provisions thereto. Use of Materials by the Government constitutes acknowledgment of Hexagon Geospatial or Intergraph’s proprietary rights therein.

International Use

You may not use or export Materials in violation of U.S. export laws and regulations. Hexagon Geospatial makes no representation that Materials are appropriate or available for use in every country, and access to them from territories where their content is illegal is prohibited.

Hexagon Geospatial provides access to Hexagon Geospatial international data and, therefore, may contain references or cross references to Hexagon Geospatial products, programs and services that are not announced in your country. These references do not imply that Hexagon Geospatial intends to announce such products, programs or services in your country.

The Materials are subject to U.S. export control and economic sanctions laws and regulations and you agree to comply strictly with all such laws and regulations. In addition, you represent and warrant that you are not a national of, or otherwise located within, a country subject to U.S. economic sanctions (including without limitation Iran, Syria, Sudan, Cuba, and North Korea) and that you are not otherwise prohibited from receiving or accessing the Materials under U.S. export control and economic sanctions laws and regulations. Hexagon Geospatial makes no representation that the Materials are appropriate or available for use in every country, and access to them from territories where their content is illegal is prohibited. All rights to use the Materials are granted on condition that such rights are forfeited if you fail to comply with the terms of this agreement.

Revisions

Hexagon Geospatial reserves the right to revise these Terms at any time. You are responsible for regularly reviewing these Terms. Your continued use of this Document after the effective date of such changes constitutes your acceptance of and agreement to such changes.

Applicable Law

This Document is created and controlled by Hexagon Geospatial in the State of Alabama. As such, the laws of the State of Alabama will govern these Terms, without giving effect to any principles of conflicts of law. You hereby irrevocably and unconditionally consent to submit to the exclusive jurisdiction of the United States District Court for the Northern District of Alabama, Northeastern Division, or the Circuit Court for Madison County, Alabama for any litigation arising out of or relating to use of this Document (and agree not to commence any litigation relating thereto except in such courts), waive any objection to the laying of venue of any such litigation in such Courts and agree not to plead or claim in any such Courts that such litigation brought therein has been brought in an inconvenient forum. Some jurisdictions do not allow the exclusions or limitations set forth in these Terms. Such exclusions or limitations shall apply in all jurisdictions to the maximum extent allowed by applicable law.

Questions

Contact us with any questions regarding these Terms.

http://www.hexagongeospatial.com/about-us/contact-us

Date post:	07-Aug-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times