Geomedia Release Guide PDF

RELEASE GUIDE
GEOMEDIA DESKTOP
June 03, 2016

Contents
About This Release ........................................................................................................................ 5

GeoMedia Product Tiers ................................................................................................................ 5
GeoMedia Essentials ............................................................................................................ 5
GeoMedia Advantage ........................................................................................................... 5
GeoMedia Professional ......................................................................................................... 5
New Platforms ................................................................................................................................ 6
Operating Systems................................................................................................................ 6
Databases ............................................................................................................................. 6
Impacts ........................................................................................................................................... 6
GeoWorkspaces ................................................................................................................... 6
MGE Data Server .................................................................................................................. 6
FRAMME Data Server .......................................................................................................... 6
ArcInfo Data Server............................................................................................................... 6
GeoGraphics Data Server ..................................................................................................... 6
Future Impacts ............................................................................................................................... 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 ........................................................................................................................ 11

CAD data server ................................................................................................ 11
Oracle Object Model data server and Oracle Object LTT data server ............... 12
June 03, 2016 2

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
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 .............................................................................................................................. 19
Performance ...................................................................................................... 19
Data Capture....................................................................................................................... 20
GPS Tracking command.................................................................................... 20
Split Feature command ..................................................................................... 20
Data Management............................................................................................................... 21
Output to Offline command ................................................................................ 21
Post from Offline command ............................................................................... 21
Data Integration and Validation ........................................................................................... 22

Create Conflation Links command ..................................................................... 22
Auto Adjust Features command ........................................................................ 24
Query Connectivity command............................................................................ 24
Fix Connectivity command................................................................................. 25
June 03, 2016 3

Data Window....................................................................................................................... 26
DataView control ............................................................................................... 26
Layout Window ................................................................................................................... 26

Export Layout command .................................................................................... 26
Cadastral............................................................................................................................. 26
Command renaming .......................................................................................... 26
Support for SQL Server Spatial ......................................................................... 27
Libraries .............................................................................................................................. 27
Support for SQL Server Spatial Read-Write data server .................................... 27
Support for PostGIS Read-Write data server ..................................................... 28
Feature Caching ................................................................................................................. 28

Indexed Feature Cache (IFC) files ..................................................................... 28
Utilities ................................................................................................................................ 28
Batch Plotting .................................................................................................... 28
Database Utilities............................................................................................... 29
Define Symbol File ............................................................................................ 29
Schema Remodeler ........................................................................................... 29
Spatial Model Editor .......................................................................................... 30
System Requirements ................................................................................................................. 31

System Requirements Notes............................................................................................... 32
Issues Resolved ........................................................................................................................... 32
About Us ..................................................................................................................................... 105
June 03, 2016 4

About This Release
ABOUT THIS RELEASE

This document describes the enhancements for GeoMedia. 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 enhancements, see the New Technology
section. For information on fixes that were made to GeoMedia for this release, see the Issues Resolved 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 GeoMedia for more information.
The scope of this document is the GeoMedia Desktop (GeoMedia Essentials, GeoMedia Advantage, GeoMedia
Professional) as well as GeoMedia Viewer and GeoMedia Objects.
GEOMEDIA PRODUCT TIERS

GeoMedia® is a flexible and dynamic GIS package for creating, updating, managing and analyzing your valuable
geospatial information. Generate and update vector layers. Perform dynamic spatial analysis and generate reports.
Automatically create and update maps. Manage data and map production more efficiently. GeoMedia is available
in three product tiers, Essentials, Advantage, and Professional.
GEOMEDIA ESSENTIALS
GeoMedia Essentials enables you to query and analyse a wide variety of geospatial data sources. It also includes
ERDAS IMAGINE Essentials, giving you the ability to do simple image preparation.
GEOMEDIA ADVANTAGE
This tier has all the functionality of GeoMedia Essentials and is excellent for data collection and editing, processing
and analyzing elevation and terrain data including LiDAR. It also includes data validation and sophisticated raster
analysis tools.
GEOMEDIA PROFESSIONAL
This tier includes all of the features of the previous tiers and provides enterprise-wide, multi-user data
management and analysis. Manage linear networks, produce professional cartographic maps, conduct advanced
feature editing, manage parcel holdings, conduct utility network analysis, monitor and control changes, integrate
data from multiple sources, and assure overall data quality with GeoMedia Professional.
June 03, 2016 5

New Platforms
NEW PLATFORMS
OPERATING SYSTEMS
GeoMedia 2016 now supports Windows 10 64-bit, and Windows Server 2012 R2, 64-bit editions. Windows 10 32-
bit is considered viable.
DATABASES
GeoMedia 2016 now supports PostgreSQL 9.3 / PostGIS 2.1, and PostgreSQL 9.4 / PostGIS 2.2.
GeoMedia 2016 supports SQL Azure v12.
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.
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

GeoMedia 2016.
ARCINFO DATA SERVER

GeoMedia 2016.
GEOGRAPHICS DATA SERVER

GeoMedia 2016.
June 03, 2016 6

Future Impacts
FUTURE IMPACTS
None.
June 03, 2016 7

New Technology
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.
June 03, 2016 8

New Technology
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.
June 03, 2016 9

New Technology
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.
June 03, 2016 10

New Technology
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.
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.
June 03, 2016 11

New Technology
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.
June 03, 2016 12

New Technology
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.
June 03, 2016 13

New Technology
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.
June 03, 2016 14

New Technology
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.
June 03, 2016 15

New Technology
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.
June 03, 2016 16

New Technology
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
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).
June 03, 2016 17

New Technology
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
user who manually enters the expression in the dialog must also enclose aliased attribute names with these
delimiters.
June 03, 2016 18

New Technology
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.
LABELING
PERFORMANCE
See map labels faster
The display performance of dynamic labels is greatly improved.
June 03, 2016 19

New Technology
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.
June 03, 2016 20

New Technology
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
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.
June 03, 2016 21

New Technology
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.
June 03, 2016 22

New Technology
June 03, 2016 23

New Technology
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
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
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.
June 03, 2016 24

New Technology
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
Connectivity. The following problems may be fixed with this command: overshoots trimmed, undershoots
extended, crossing lines broken, and vertices inserted into crossing lines.
June 03, 2016 25

New Technology
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.
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.
June 03, 2016 26

New Technology
SUPPORT FOR SQL SERVER SPATIAL

All cadastral commands are enhanced to work with SQL Server Spatial data server.
LIBRARIES
SUPPORT FOR SQL SERVER SPATIAL READ-WRITE DATA SERVER
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.
June 03, 2016 27

New Technology
SUPPORT FOR POSTGIS READ-WRITE DATA SERVER

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.
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.
June 03, 2016 28

New Technology
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.
Now supports the PostGIS data server.
DEFINE SYMBOL FILE

Use a wider range of AutoCAD symbols
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.
June 03, 2016 29

New Technology
SPATIAL MODEL EDITOR

Perform spatial modelling on a GeoMedia Desktop seat
Use this new utility to create, edit, and run spatial models.
June 03, 2016 30

System Requirements
SYSTEM REQUIREMENTS
 32-bit: 2GHz microprocessor, Intel® Pentium® 4 HT, Core™ Duo, Xeon
Computer/ Processor
 64-bit: Intel 64 (EM64T), AMD 64, or equivalent (recommended)
Memory (RAM)  4 GB minimum, 8 GB recommended
 10 GB for software
Disk Space
 Data storage requirements vary by mapping project1
Software security (Intergraph Licensing 11.11.1) requires the following:

Peripherals
 Ethernet card
 Windows® 7 SP1 or higher, Professional and Ultimate (32-bit and 64-bit)2
 Windows® 8 (Standard), Professional and Enterprise (32-bit and 64-bit)2
 Windows® 8.1 (Standard), Professional and Enterprise (32-bit and 64-bit)2

2
Operating Systems
 Windows® 10.0 (Standard), Professional and Enterprise (32-bit and 64-bit)2
 Windows Server® 2008 R2 SP1 (64-bit)3
 Windows Server 2012 R2 (64-bit)3
 VMware ESX 5.1
 Oracle VM Virtual Box

Virtual Server and Virtual
App Technology
 XenApp 7.6
 Remote App (MS 2012 R2)
 Oracle® Server 11g, 32-bit and 64-bit
 Oracle Express 11g
 Oracle® Server 12.1, 64-bit
 SQL Server® 2012, 64-bit

Database Server Engines
 SQL Server Express 2012
 SQL Server 2014, 64-bit
 SQL Server 2014 Express
 PostgreSQL 9.3 with PostGIS 2.1
June 03, 2016 31

Issues Resolved
 PostgreSQL 9.4 with PostGIS 2.2
 Oracle Client 11g, 32-bit

Database Client Engines
 Oracle Client 12.1, 32-bit
SYSTEM
1
REQUIREMENTS NOTES
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 considered viable platforms.
Viable platforms are not an explicit requirement and have not been tested as a standard scenario in Hexagon
Geospatial’s Development and Quality Assurance cycles. However, the technology is similar to one of the
supported platforms that compatibility is practical. Although we expect our applications to be compatible with viable
platforms, we cannot guarantee contractual performance or high availability requirements.
3
GeoMedia runs on 64-bit systems in 32-bit emulation mode.
ISSUES RESOLVED
CR # SUMMARY Description / How to Reproduce
GeoMedia crashes Steps to Reproduce:

closing
geoworkspace 1. Invoke GeoMedia Professional. Create a blank Geoworkspace.
after closing
overview window. 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.

1-9AF33V
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.
12. Click on File>Close geoworkspace. Click on No button on message dialog. Observe that
June 03, 2016 32

Issues Resolved
application crashes.
Error followed by Steps to Reproduce:

crash on
performing Insert 1. Invoke GeoMedia Professional.
Traverse command
with category 2. Create a blank Geoworkspace.
features on
German OS. 3. Make Access R/W connection to USSampleData.mdb delivered with product.(IFC ON)
4. Add all the features to categories.

1-9B14LP
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.
7. 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.
FGDB Read Only Steps to reproduce:

shows English
strings on New 1. Invoke Japanese version of GeoMedia Professional.
connection dialog
1-9BHFUB in Japanese 2. Invoke New connection dialog.
version.
3. Observation: FGDB Read Write is displayed in Japanese language; however, Read Only is still
shown in English.
Export to GML the Export to GML The dialog size is fixed on size 8 dialog. On size 9 dialogs, the right side of the dialog is
dialog size is fixed truncated. Resizing subroutine is using the numerical value to adjust the position of items. Therefore the
on size 8 dialog. items on Size 9 dialog (Japanese and Chinese) are not correctly positioned and truncated at right side and
1-9BHG48
Truncated the bottom.
dialog items at right
side
GeoMedia crashes GeoMedia crashes while exiting the application from the task bar with options dialog in invoked state.
exiting the Steps to reproduce: Invoke GeoMedia. Select Blank Geoworkspace radio button. Open a Geoworkspace.
application from Select the Insert feature. Select options dialog from the vector control. Exit the Application from the Task
1-9BOVUL the task bar with bar. Observations: --------------------------- PMiscCmd --------------------------- Error exiting
options dialog in application.Source:GMCmdSuptDescription:Method '~' of object '~' failed --------------------------- OK --------
invoked state. ------------------- --------------------------- PProCtrl --------------------------- Run-time error '0' ---------------------------
OK --------------------------- Click Ok on the dialog GeoMedia Crashes.
GeoMedia crashes GeoMedia crashes exiting the application with Coordinate System dialog in invoked state. Steps to
exiting the reproduce:
application with
Coordinate System 1. Invoke GeoMedia.
1-9BOVZX dialog in invoked
state. 2. Select Blank Geoworkspace radio button.
3. Open a Geoworkspace.
June 03, 2016 33

Issues Resolved
4. Select the Insert feature.
5. Invoke the coordinate system from the vector control.
6. Exit the application from the task bar.
7. Observations: GeoMedia.exe still runs exit the application from the task bar.
GeoMedia.exe still GeoMedia.exe still runs exiting the application with the options dialog in invoked state from Queued Edit
runs after exiting control dialog. Steps to reproduce:
the application with
options dialog in 1. Invoke GeoMedia.
invoked state.
2. Select Blank Geoworkspace radio button.
3. Open a Geoworkspace.
1-
9BOW1Y 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.
8. Observations: GeoMedia .exe is still running in the task manager after exiting the application.
ShapeFile Data User exports GeoMedia GeoWorkSpace query containing double values then serves the data back into
Server: Attributes GeoMedia using Shape File data server. The field is correctly served back as double, but the values are all
of Type Double truncated to 0 digits of precision (value 77.1234 becomes 77); the values are rounded to zero decimal
Rounded or places.
Truncated As If
Integer. 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.
1-9C00AU 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"
4. 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.
GeoMedia.exe is GeoMedia.exe is still running after exiting the application from the task bar with Save As Dialog in invoked
still running exiting state of Edge Match rules dialog. Steps to reproduce: Pin GeoMedia to task bar.
1-961T3I
the application
from task bar with 1. Invoke GeoMedia
Save As dialog in
June 03, 2016 34

Issues Resolved
invoked. 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.
GeoMedia.exe is GeoMedia.exe is still running while inserting the feature with properties dialog in invoked state while
still running while exiting the application from the task bar.
inserting the
feature with 1. Invoke GeoMedia
properties dialog in
invoked state. 2. Select Blank Geoworkspace.
1-9625CJ
3. open a workspace
4. Select Insert feature from the Vector Tab.
5. End the feature.
6. Exit GeoMedia from the task bar.
Connection 1. Open GeoMedia.

properties dialog -
enable feature 2. Connect to USSampleData with caching off and add counties feature class to map window.
caching checkbox
state not persisted. 3. Verify cache is not created.
4. Open Warehouse Connections command.
5. Click properties button.

1-968SJL
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.
9. Open Properties dialog to see that enable feature caching checkbox is checked. This should not
happen.
Layout > Print > 1. Steps to reproduce:

Plot of WMS fails.
2. Open provided GeoWorkspace and zoom in to scale 1:50000.
1-96FA9R
3. Set nominal map scale to 1:50,000.
4. Open layout window.
June 03, 2016 35

Issues Resolved
5. Print to printer.
6. Result: Blank paper. No error message.
Aggregation Crash Customer supplied data demonstrates a crash of GeoMedia application without chance to save when
Using Within using Aggregation within distance operator. The problem appears to be data specific. Workflow:
Distance Spatial
Operator - Data 1. Save .zip to C:\Warehouses and extract to here which should create folder 1-96ZL03.
Specific.
2. Open Testing1.gws
1-96ZL03 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)
5. 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.
Geometry I wanted to use this command to see if the data referenced in a particular CR is clean and found some
validation gives errors. Steps to reproduce:
inappropriate
validation errors 1) Invoke GeoMedia and connect to attached test data (WFS_Test.mdb)
which was not
seen in 6.1.11.13 2) Select Toolbox>Validate Geometry and select feature class GRUNDNUTZUNG_WALD and
version. click [OK] on the Validate Geometry dialog.
1-97CCGB
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
Spatial intersection Spatial intersection throws a Method of object failed error and does not show an error message with
throws a Method of invalid query to oracle connection. Steps to reproduce:
object failed error
with invalid query. 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.

1-97DBUN
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.
June 03, 2016 36

Issues Resolved
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.
Problems with After exporting to shape files from a PostGIS database connection and then making an ArcView
Shapefile export connection to the exported files, the user is unable to display the ArcView features in the Map window.
from PostGIS Workflow:
database
1-9910J8 displaying in GWS. 1. Open a blank .gws and make an ArcView connection to the exported files.
2. 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.
Recordset access This was filed against the Oracle R/W data server when observing the behaviour of the Toggle Dynamic
is causing data Label command. The recordset access pattern in the Toggle Dynamic workflow is causing the data server
server to issue to issue selects to the database for each geometry row resulting in a performance hit.
1-8OH60M
selects to database
that is causing a
performance hit.
Invalid geometry Invalid geometry types enabled in Continue Geometry dockable control while trying to do Continue
types enabled in Geometry on a Spatial Query. Steps to reproduce:
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

1-8P174L
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
GeoMedia GeoMedia Professional crashes for Validate Geometry on Searched item in select set.
Professional
crashes for • Invoke GeoMedia Professional and create an access warehouse connection to USSampledata.mdb.
Validate Geometry
on Searched item • Select Search command and select States feature class.
in select set.
1-8SSXEF • 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.
June 03, 2016 37

Issues Resolved
The following error is displayed. --------------------------- Queued Edit Control --------------------------- The
connection associated with this queue is closed. The queue cannot be viewed. --------------------------- OK
--------------------------- Application crashes.
Warehouse Steps to Reproduce:

caching location
not validated by 1. Create a folder (in say C:\Temp) for the purpose of holding warehouse cache files
GeoMedia during
clear/refresh/enabl 2. Invoke GeoMedia with a blank new geoworkspace and using 'Options' change the Warehouse Cache
e stages. Files location to the folder created above
3. Close GeoMedia without saving GWS
4. Delete the folder manually

1-8U3XM5
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.
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.
Unable to Validate Connectivity in GeoMedia Pro no longer supports output to query.

Generate
Connectivity a) Queries can be output and/or exported to other required formats
Queries in
GeoMedia 2014 b) Queries are built once and preserved as part of the GeoWorkSpace:
and GM 2015.
1. Automatically updating when underlying data changes.
1-8VC1RJ 2. User does NOT have to recall correct settings (saved as part of the query)
3. 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.
'Method '~' of 'Method '~' of object '~' failed' error message pops up on giving invalid filter in Spatial Query Workflow to
object '~' failed' reproduce.
error message
pops up on giving 1. Invoke GM Pro and open a new geoworkspace.
invalid filter in
1- Spatial Query. 2. Make an Access connection to USSampleData.mdb.
8DRJWH
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.
June 03, 2016 38

Issues Resolved
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.
Add WMS Legend The "Add WMS Legend Entry" command calculates intersection from all bounding boxes selected to
Entry calculates display. As a result, if there are two layers with disjunct (non-intersecting) bounding boxes, nothing is
minimal bounding displayed and the request is not sent to the server. The command must calculate minimal rectangle
box of layer covering all bounding boxes, and request this coverage. The side effects of the current implementation
intersection, not are that if one of the bounding boxes is out of the map extent, no request is sent to the server although
union. 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.
1- 3 - Pan to the left so that the image footprint for Plavebna_brana completely disappears from the map.
8WF6AO
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.
Fails to display If the customer creates a non clustered index that contains the XLO,XHI,YLO,YHI and includes any other
feature class if column from the table, GeoMedia will fail to display the feature class and will return the error: Index,
1- index contains Geometry_XLO, not found for feature classes containing a large number of rows. Building optimal indexes
8WWKHE XLO,YLO, XHI, is very important and GMP should not fail on any index definition.
YHI and any other
column.
Selecting numeric When trying to update a numeric value from a picklist in the update attributes command, the following error
values from a is given: There are no valid value(s)/expression(s) defined. The field is defined as a number in Oracle. An
picklist in update entry in gpicklist exists to make this value appear in a list. This issue does not exist when selecting string
attributes values from the picklist. Workflow to reproduce:
command causes
an error. 1. Open geoworkspace and connect to Oracle database that was used for import above.
1-8XU0Z0 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'.
June 03, 2016 39

Issues Resolved
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.
Customizing the Customizing the Quick Access Toolbar (QAT) menu is not saved if the machine is rebooted. If a
Quick Access geoworkspace (.gws) QAT is setup with various commands and saved in the .gws and the machine is
1-8XXYNP Toolbar(QAT) is rebooted, the saved .gws when reopened does not show the saved QAT. In fact it adds multiple
not saved after a commands to the QAT.
machine reboot.
Ribbon bar Steps to reproduce:

disappears on
opening saved gws 1. Invoke GM
repeatedly.
2. Open saved GWS.
1-8Y4J0V
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 --------------------------- .
Diacritic For this particular WMS, the title names contain Czech Diacrtic characters. The customer has had to
Characters in Title remove the diacritic characters in order to get their WMS Service to work.
name are not
1-8ZG7HX
retained for Legend
Entry Name in GM
GUI w/WMS DS.
Cannot display Using the WMS Dataserver with a connection to a WMS Service, -- when the layer name contains a
WMS Layer when Diacritic character, the GM GUI gives error and will not display the layer.
1-8ZGFBQ
name contains
Diacritic Character.
Thematic Thematic classification displays Memo datatype error "This datatype could not be indexed". To reproduce:
classification
displays Memo 1. Open the attached USSampleData.gws and USSampleData.mdb.
datatype error
"This datatype 2. Create a unique thematic legend on the states feature using the attribute1 attribute which is memo type.
could not be
indexed". 3. Error appears "This datatype could not be indexed".
1-9094B3
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- GeoMedia Query When a GeoMedia query is created on an Oracle database field that is type Date and the query contains
June 03, 2016 40

Issues Resolved
7NJGUW using TRUNC the TRUNC operator, the query will display successfully without a Spatial Filter applied. When a Spatial
operator on Oracle Filter is applied over the query results, an error messages will display. Once the error message displays,
‘Date’ field with the query cannot be displayed again. The query can be recovered by removing the Spatial Filter, deleting
Spatial Filter. 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
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...
Feature Class Using Feature Class Definition to edit lots of attributes (names and types) simultaneously for a SQL Server
Definition - multiple feature (without saving the changes with the OK button between edits) will result in an ‘Out Of Memory’
edits to SQL error when you click OK to save the edits. To see the problem use the steps below.
Server feature
causes 'Out of 1. Create a new GeoWorkspace and make an SQL Read-Write data server connection to an existing SQL
Memory' error. 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’.
1-82XDCY
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”
June 03, 2016 41

Issues Resolved
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.
Output Name field Generate Static mode dialog Output Name field does not accept the 2-byte characters. (There is the
1-7PBOIU should accept 2 restriction of only accept alphanumeric characters and underscore). This is needed for Chinese,
bytes characters. Japanese and Russian.
Feature Model For Public Works functionality to work with the SQL Server Native spatial data server, Feature Model will
does not recognize need to be modified to recognize this new data server. That must happen before any testing can be done
1-6CR1Q9 the SQL Server using Public Works functionality with this new data server. This is also a major concern for customer who
Native Spatial data wish to use GMSC as GMSC has only limited support for features served from GDO based MS SQL
server. features.
Path to Default Steps to reproduce.

Symbol File has
changed, thus 1. Invoke GeoMedia.
Symbol file: field is
empty. 2. Activate Layout Window.
1-6XHG98
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.
Continued Label I continue to have problems when using styles in the label tools as well as performance issues on areas
Style Problems and where I have no labels to display. A separate CR was created for the styles issue. The performance
1-6YPVUD
Performance issues were handled. Some by documentation, some by code changes.
Issues.
Layout > Insert > When using Layout > Insert Map by X, I'm seeing 2 copies of the Drawing Toolbar, which consumes too
Insert Map by: much of my layout window screen area. There should only be one copy. The second copy appears to be
Duplicate Drawing simply a ghost image - the buttons don't function. X = Paper Size, existing shape, rectangle Map/Layout
1-70PSCY
Toolbar. Existing Window should not be maximized.
shape, paper size,
etc.
Display Scale is The MapWindow Display Scale which is displayed along the lower right portion of the application window
Greyed Out and is greyed out. This was not the case when compared to previous version.
1-70R94E Difficult to Read
Compared to
Previous Versions.
GeoMedia crashes GeoMedia crashes after abnormal memory and network usage growth on trying to add legend entries from
after abnormal PostGIS database. On trying to add several legend entries from a PostGIS database it was observed that
memory and the memory usage grew to over 3 GB very quickly and GeoMedia crashed. The memory and network
1-AA7ZCB
network usage usage growth was abnormal and also instantaneous. A screenshot taken during the growth has been
growth on trying to attached. At one case GeoMedia also displayed 'Out of memory' for map view. Note: If GeoMedia does
add legend entries. not crash with few legend entries, try adding some more in the same session. Steps to Reproduce:
June 03, 2016 42

Issues Resolved
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.
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.
GeoMedia Public GeoMedia Public Works Commands are not supported on PostGIS.
Works Commands
1-AA7ZF7
are not supported
on PostGIS.
Could not view the Could not view the inserted features unless connection is reopened-PostGIS. Installing the PostGIS GDO
inserted features for usage with GeoMedia. Steps to Reproduce:
unless connection
is reopened- 1. Invoke GeoMedia Professional. Make PostGIS connection with your credentials Using IFC ON.
PostGIS.
1-AA7ZGF 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.
PostGIS: Unable to PostGIS: Unable to generate static labels with Warehouse Connection. Steps to reproduce:
generate static
labels with 1. Invoke GM.
Warehouse
Connection. 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.
1-AA7ZJ6
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 ---------------------------
Selecting a Label Selecting a Label leader command and selecting a new geoworkspace will produce the following error
leader command message:
and selecting a
new geoworkspace The following unexpected exception occurred: COM object that has been separated from its underlying
1-AA7ZO3 will throw an error. 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.
June 03, 2016 43

Issues Resolved
GeoMedia is When loading a DGN in to GeoMedia, any cell is placed on level 0, regardless of which level they were
putting all cells placed inside the DGN. Looking though the connection, anywhere a cell name is populated, the level is 0.
from a dgn to level I've created the CSD from scratch and used the Display CAD Files tools from inside GeoMedia. The color,
0 regardless of dgn weight and style of the cell items are also being set to 0 regardless of dgn value. Steps to reproduce:
level.
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
1-AAC315
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.
Location label for Steps to reproduce:

Enable feature
caching checkbox 1. Invoke GeoMedia Professional and create blank GWS.
is missing for
Object Space 2. Invoke New Connection dialog.
1-AB9N5X connection type.
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.
Labeling Properties Labeling Manager > Properties > Label with symbols: The "Up" button is empty ("down" button has down
dialog - Label with arrow ) MapText: Labeling Manager > Properties > Label with symbols : The "Up" button is empty ("down"
symbols : The "Up" button has down arrow ) in the expanded pane.
1-ABAPN7
button is empty
("down" button has
arrow).
Document Must When generating static labels to warehouse with IFC on, labels are not shown on the Map when the
Refresh Cache to "Append Labels to Existing Output" option is selected until the cache is refreshed or IFC is turned off. To
view appended reproduce:
Static Labels with
1-ABAPO3 IFC on. 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.
June 03, 2016 44

Issues Resolved
4. Select Label checkbox for States feature class and set text as STATE_NAME.
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.
Add WMS Legend Region has indicated they have customers asking why the Legend > Add WMS Legend Entry command
Entry Results in cannot be used to add WMS Legend entries for a particular site. Selecting the Add WMS Legend Entry
1-9YR0IH Errors and Bad command results an error from .Net in GeoMedia states: "Expected DTD markup was not found. Line 1,
State (Continual position 3." Afterwards, the on-screen cursor stays in wait cursor mode which seems to indicate the
Wait Cursor). command is not exited cleanly and is in a bad state.
GeoMedia Steps to Reproduce:

Professional
crashes when 1. Invoke GeoMedia Professional.
redigitizing a long
text using “place at 2. Create blank Geoworkspace. Make Access R/W connection to USSampleData.mdb. Make
a point” option. MapInfo connection to \\GeoMedia\PVTDatasets\MapInfo\USA or
\\geotest2\PVTDatasets\MapInfo\USA
3. Add States LE from map info connection to map window.

1-A019KV
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).
6. 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.
Dialog margins are The dialogs listed below have issues with poor margins (usually at bottom and at right), sometimes
compromised for including no margin or actually even clipping off controls. Behavior varies according to the operating
resizable VB6 system.
dialogs.
Queued Edit, Search, Edit Text and Linear Link Zoom.
1-A23QOV 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
dialogs.
June 03, 2016 45

Issues Resolved
Catalog Connections and Catalog Explorer.
The issues can be classified under 3 categories:
dialogs.
Grid Calculator and Design Legend
1-A24ASV The issues can be classified under 3 categories:
dialogs
Dimensions and Dimension.
1-A24ATE The issues can be classified under 3 categories:
Display AutoCAD Customer provided data shows that using the Manage Data tab, Display CAD Files command to display
.dxf results in certain AutoCAD .dxf files can result in the crash of the GeoMedia Application without any opportunity to
application crash save GeoWorkSpace changes. To reproduce: Create a GeoWorkSpace and use Display CAD Files to
for certain data. display one or both of the provided .dxf files using the default settings.
1-A34UNQ
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.
Insert > When attempting to insert a TIFF file with suffix .tiff and worldfile, GeoMedia crashes when pushing the file
Georeferenced to the right side of the dialog. Changing the extension to .tif allows the file to be moved to the right side of
Images. TIFF file the Insert > Georeferenced Images dialog. Selecting the provided .csf file, then 'OK' generates an error:
1-A3MJFI
with suffix .tiff and
worldfile crashes --------------- GeoMedia Desktop . Error inserting or updating the specified coordinate system. ---------------
GeoMedia Pro. The file cannot be inserted.
June 03, 2016 46

Issues Resolved
Several res files Several res files contain string "Set the Master Connection in the Parcel Manager". This should be
contain string "Set changed to "GeoMedia" to reflect the inclusion of the former Parcel Manager commands into GeoMedia.
1-
the Master
9CJWWW
Connection in the
Parcel Manager".
View Precision Precision Coordinate dockable control disappears when switching back from Layout window. To
Coord dockable reproduce:
control disappears
when switching 1. Open .gws
back from Layout
1-9CM1H0 window. 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.
The documentation In the documentation for developers you can read for the FGDB connection that the ConnectInfo for the
is lacking the INI file location is "FOLDER=;INI=<full path and filename of the warehouse configuration file>" But the
necessary full customer received an error that was fixed only after the FOLDER parameter full path to the data folder
1-9CQ4U7 description for the was included. So, it needs to be documented like this: The problem is that it should be "FOLDER=<full
FOLDER path and filename of the warehouse folder>;INI=<full path and filename of the warehouse configuration
parameter for an file>" And the same for the FGDB write-Read.
FGDB connection.
Crash without User may get message "Error activating the command" message followed by an application crash when
opportunity to save using Dynamic Labelling. If the user has the Map Widow setup to navigate using selected records in the
when using data window, then Dynamic Labelling may crash, especially if the user attempts to use the Data Window,
labelling with Promote Rows command. Note: Map Window Properties are defined such that: "For items in select set"
common "Center at current scale". Workflowto reproduce:
GeoWorkSpace
settings. 1. Open GeoWorkSpace (references Madison County dataset)
2. Select Labelling > Toggle Dynamic so the Toggle Dynamic is enabled.

1-9CSOYK
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.
Multilingual When .Net-Custom commands are generated multilingual with resource files, the language files cannot be
generated .Net used in German. The custom command can't be loaded, as long as there is the directory "de" in directory
Custom commands of the command dlls (even if the directory is empty). In the English version the problem doesn’t occur.
not loaded to My
1-9CUJFS
Workflow on
German
GEOMEDIA
PROFESSIONAL.
1-9DJJPL Unload Query does Customer notes that even if he deletes his query(s) from the map legend AND uses the Analysis > Queries
not actually unload command to Unload all queries, the query is not unloaded from memory and the result is no savings in the
June 03, 2016 47

Issues Resolved
to allow edits to run time required to process.

without processing
the query. 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.
11. Again use the Edit Geometry to move a vertex of the UnInc feature. Note the time to complete.
(Support observes ~21 min).
Poor Query GeoMedia 2014 shows very poor performance for query update / notifications when compared to version
Notification 6.1. In a simple test using a Spatial Intersection query we can see that the time required for an edit
Performance in geometry move vertex in version 2014 on a Win7 system fails to exceed or meet the update time for the
2014 vs. 6.1. same operation when using 6.1 on XP. Testing here is limited to the time for notification and update to
1-9DJJT7
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.
Need official Summary: Request official support and documentation for running Configuration Wizard using the /q
Support For (Quiet) option. User has already found that running Intergraph.GeoMedia.ConfigurationWizard.exe /q
Launching works but request official support in conjunction with related regression CR defect (see also Related CRs).
Configuration Background: Administrator at large GeoMedia Application use site has requirement to provide non-admin
Wizard Using /q clients the ability to launch and see the unassisted installation and configuration of GeoMedia. This was
(quiet) Option. done in version 6.1 using a "Quiet" installation method which differs from "Silent" installation as it gives
1-
user installation feedback by showing dialogs and forms used during the installation process. The user
9DNBUO
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.
When attaching When attaching raster images that are in JPEG 2000 (.jp2) format, GeoMedia crashes to desktop
raster images that immediately with .Net runtime errors. Workflow to reproduce:
are in JPEG 2000
1-9KYBZZ
format, GeoMedia Using Insert>Georeferenced Image with automatic mode the application crashes when hitting ‘Ok’ or
crashes ‘Apply’.
immediately.
June 03, 2016 48

Issues Resolved
Setting a Spatial Error 0x80040ACE (Error parsing SQL statement) is being returned when getting recordset from an
Filter together with originating pipe set with a spatial filter and attribute filter using 'Upper' Oracle function. This originated
Filter using 'Upper' from having LegendEntry->LoadData() fail with 0x80040638 (GRecordset is invalid.) during
1-9L2ZTP fails. 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.
'Simplify Geometry' 'Simplify Geometry' and 'Smooth Geometry' commands are not working if the Culture information of a
and 'Smooth custom command is changed (different from GeoMedia). To Reproduce:
Geometry'
commands are not 1. Copy the ChangeLanguage_Command folder to your machine where GeoMedia Professional
working using 2015 is installed.
culture information.
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
1-
the query to mapwindow if 'Display results in mapwindow' option is checked.
9MKS1M
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).
12. Execute 'Simplify Geometry' and 'Smooth Geometry' commands and see that query is created
and added to the map window.
Grid layer shows a Grid layer shows a lot of void pixels after rasterizing elevation points. The problem occurs when defining
lot of void pixels the study area inside the elevation spots. As soon as the study area covers a larger area than the
1-9OBC33
after rasterizing elevation spots, the rasterized result is ok.
elevation points.
Inappropriate error A message box with a message "property is read only" is displayed when show values button is clicked in
when clicked on the select reference features dialog box in GeoMedia. After clicking on "ok" button the cursor remains in a
Show Values processing state due to which we cannot proceed further. Steps to reproduce:
1-9QYJ53 button for a FC
which is not having 1. Invoke GeoMedia Professional.
values.
2. Create a blank Geoworkspace.
June 03, 2016 49

Issues Resolved
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.
Continue Geometry Continue Geometry fails to place a hole in an area using Continue Geometry tool, and where points are
1-90UR3Z fails to place hole inserted using precision input including elevation values. Points are placed, but on attempting to complete
in area. the feature, GM simply "pings" and does nothing else, no error message.
Bufferzone fails on Buffer zone query fails when running Edit Query properties and the buffer zone is display in a data
Edit Query window. The error message is "Recordset Buffer zones around C_LINE_NR is empty"
1-90WSU7 Properties when
displayed in a
datawindow.
Aggregation, can't When trying to verify that the Query name is empty, the two feature combo boxes (‘Aggregate to summary
select features if features in’ and ‘From detail features in’) are accessible to us to change the features." This is not true.
1-912BW5
query field is Attempting to use the combo boxes results in a pop-up error alert, just as with any other items in the
empty. dialog.
Deleting Steps to reproduce:

warehouse
connections throws 1. Invoke GM.
an error.
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.
1-91SQTJ 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 ---------------------------
June 03, 2016 50

Issues Resolved
OK ---------------------------
WMS features are 1. Start GeoMedia Professional and create a new GeoWorkspace.
not displaying on
map window. 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.
1-
3. Click Ok button and provide user name and password.
9TWMFA
4. Using Add Legend Entries command, add the States feature class to map.
5. 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.
Simplify Geometry Simplify Geometry command seems to have problems working with specific feature classes; possibly
Command Not where the Simplify Geometry command encounters polylines with a large number of vertices. Example
Working. 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
1-9V4P39
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.
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.
Overview window Steps to Reproduce:

not invoked after
closing existing 1. Invoke GeoMedia Professional. Create blank Geoworkspace.
overview window.
2. Make Access R/W connection to USSampleData.mdb.
3. Add all Legend entries to map window.

1-9X6K1H
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.
June 03, 2016 51

Issues Resolved
8. Invoke GeoMedia Professional.
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.
"Validate Problem: The "validate connectivity" tool crashes constantly with a given dataset. An error message in
Connectivity" German gets displayed (even when GM is installed in English). The original content of the error message:
terminates "Automatisierungsfehler - Das aufgerufene Objekt wurde von den Clients getrennt" Translation:
GeoWorkSpace "Automation error - the called object got disconnected from clients" Steps to reproduce:
Session without
opportunity to 1. Unpack ZIP folder in C:\Temp and open GWS "HSV.gws"
save.
2. Toolbox -> Validate Connectivity
1-A5D41R
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.
Spatial Analysis Spatial Analysis commands throws method of object failed error with invalid query in filter dialog. Steps to
commands throws reproduce:
method of object
failed error with 1) Invoke GeoMedia.
invalid query in
filter dialog. 2) Make an Access connection.
1- 3) Add legend entries.

A7YCWW
4) Select Spatial query and Select a feature.
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.
Additional Additional unexpected dialog comes up giving invalid value in Update Attributes. Issue observed with
unexpected dialog Win8.1-64 bit. Steps to Reproduce:
comes up giving
invalid value in 1. Invoke GeoMedia Professional.
Update Attributes.
1-A7YNFR 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$ ------
June 03, 2016 52

Issues Resolved
--------------------- OK ---------------------------“
Click on Ok button. Observe that now relevant message “--------------------------- GeoMedia Desktop -----------
---------------- There are no valid value(s)/expression(s) defined. --------------------------- OK ----------------------
-----“is displayed.
Select Set Select Set Properties throws error while performing analytical merge using CURRENCY attribute-IFC ON.
Properties throws Steps to Reproduce:
error while
performing 1. Invoke GeoMedia Professional.
analytical merge
using CURRENCY 2. Create blank Geoworkspace.
attribute-IFC ON.
3. Make Access R/W connection to USSampleData.mdb with IFC ON. Using Feature Class
definition add Attribute1 of type currency.
1-A7YNJ7
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”.
Spatial filter causes Spatial filter causes anomalous geometry display using SmartStore Warehouse. Using an overlap spatial
anomalous filter with SmartStore data results in phantom geometry displays.
1-AC7Y8G geometry display
using SmartStore
Warehouse.
Exit and save > Region reports they open a GeoWorkspace. GeoMedia Desktop is not maximised so they maximise the
Map Window state window. Close and save the GeoWorkspace. Open GeoMedia Desktop again and it is no longer
1-ADA7F4
not saved on exit. maximised. Customer sees this behaviour when running GeoMedia Desktop directly on his laptop and
when using external monitors.
Data Integration The delivered GeoMediaFusionTraining Guide.pdf has the following statement: Login to
and Validation https://support.intergraph.com using your access credentials. 
1- Training.zip file link copy the link and paste it in Internet Explorer to open the link)
ADCQ6S in https://support.intergraph.com/documents/GeoMedia/GeoMedia Fusion/Data Integration and Validation
GeoMediaFusion_ Training.zip The link in the training guide (see statement above) however returns a HTTP 404 error
Training Guide.pdf. indicating page not found. Document needs correction and data should be delivered with product.
KML Data Server Customer provided KML data in version 2.0. File could not be served by GeoMedia Desktop - wrong
1- not version error. Customer indicates some interchanges are missing after reviewing the data. We reviewed
AQDP7O reading/displaying the original .kml and all intersections/interchanges were present. GeoMedia Desktop fails to serve KML
some features. data properly.
Time & Date/Time A SR was filed for a problem when using GeoMedia Desktop configured for the German language
Format lost for whereby attributes of type Date that have the Format set as Time or Date/Time do not retain the
Date attribute on formatting. Specifically the formatting of the Date attribute is lost if Feature Class Definition is used to add
1-ARG6PP
German GeoMedia another attribute to the feature or edit an existing attribute. For instance an attribute with the Data Type
after feature class set to Date (a.k.a. Datum in German) with the format set to Time would have the format changed to Date
edit for that attribute after using Feature Class Definition. The workflow below can be used to reproduce the
June 03, 2016 53

Issues Resolved
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.
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.
June 03, 2016 54

Issues Resolved
Analytical Analytical Merge/Aggregation output functional attribute allows spaces in "Functional attribute name". To
Merge/Aggregation reproduce:
output functional
attribute allows 1. Open attached ussample.gws.
spaces in
"Functional 1. 2. Create an attribute query of "Counties" selecting "AVETEMP" as the attribute with a criteria
attribute name. "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".
1-ATFD54 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.
WMS connection WMS data server fails to connect to http://geo.weather.gc.ca/geomet/?lang=E&request=GetCapabilities

fails with “is not a with the error message “RDPS_ETA___Snow_mass__kg_m²_ is not a valid name.” In Geospatial Portal
valid name” the layer can be added to the legend, but no graphics are visible. This may be due to my lack of expertise
message, same in configuring Geospatial Portal however. To reproduce this problem, use these steps:
WMS can be
opened in other 1. Start GeoMedia Desktop and create a new blank geoworkspace.
clients.
2. Select the New Warehouse Connection command.
1-
3. Choose WMS from the ‘Connection type’ list on the New Connection dialog and in the Web Map
AX4OMP
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.”
Client Seat Cannot The client side workflow to define a shared server cache location causes local cache files to be created.
Specify Server This is because it is not possible to set the Location of the cache without having to click on the
Cache Location Create/Refresh Cache option of the Enable Caching dialog. For example: Client user needs to specify
Without Using server UNC path location to shared cache for a particular existing connection where some features are
Create/Refresh currently displayed in the map window. The current workflow on the connection properties dialog is:
Cache.
1. Select Properties for a Connection and notice how the Location field for cache is greyed out.
1-AXJYZ6
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
June 03, 2016 55

Issues Resolved
used.
Help Topic For The Help topic for Feature Caching does not wrap to the width of the Help dialog / interface; this forces the
Feature Caching user to scroll extensively. It's easier to copy the help contents to MS Word where the wrapping occurs
1-AXJZJ8
Difficult to Read automatically. Example: Open Help and search for PublishIFC, select the 1 Rank topic and notice how
Due to No Wrap. you must scroll to read the material.
Symbol display is Customer has a symbol "Tree (from above)" in the provided .fsm, which has its display 'scrambled' in the
1-AYLHVV incorrect in Map Window with GM Desktop 2015. In GM Desktop 2014 it is displayed correctly in the map window.
GMDesktop 2015
Default Values for Inconsistent use of single vs double quotes in Access. If you define a feature class in GeoMedia in an
text fields Access warehouse, and set a default value for a field of type text, the default value is in single quotes in
behaviour in Access (e.g. 'My default value') If you do it directly in MS Access, Access uses double quotes (e.g. "My
Access DB. 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
1- states table.
AZGBWW
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
Insert GM is crashing in inserting Georeferenced Image if Georeference mode is set to Automatic (w/ world file)"
georeferenced or "World file" and regional settings are set to "German". Root cause is probably a decimal separator
1- raster causes GM issue.
B0WWOR 2015 to crash
(German Regional
Settings).
Caching Help Help topics for caching are only listed under a very large Help section called Miscellaneous: The 3 Help
Topic Titles are topics for caching is titled as: Feature Caching, Feature Caching, Feature Caching. Suggest that: a)
Duplicated. Important topics such as Feature Caching be integrated into main contents, not hidden under
1-B4YTAU 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
June 03, 2016 56

Issues Resolved
important topics. For example, currently The Edit Warehouse Connections help topic fails to mention
feature caching.
Issues with multi- Below issues are observed with multi-select mode of PickQuick dialog.
select mode of
PickQuick. 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
1-B715PR
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.
PickQuick: Holding Holding control key and then pressing space bar is not adding to the selection or removing from the
control key and selection if the current item is already selected. This functionality works fine with mouse left click and
then pressing control key.
1-B715QG
space bar is not
adding to the
selection.
Missing Grid lines Missing Grid lines in GM 2014 - Layout Window - Insert Grid. This problem does not exist in GM 2015. The
in GM 2014 - customer can't update to 2015 due to missing GIPS products for 2015. Please have a look into attached
Layout Window - data set and screenshots. To Reproduce:
Insert Grid.
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.
1-B8676U 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.
Area legend key When using an expression for the Displayable property on the Style Properties ‘Advanced’ tab to control
disappears when the display of an area feature the corresponding legend entry key is removed. This is a regression from
expression is used GeoMedia Desktop 2104. To see the problem you can use the steps below.
for Displayable
style property 1. Create a new geoworkspace and make an Access warehouse connection to USSampleData.mdb.
(regression).
2. Use ‘Add Legend Entries’ to add Counties to the legend.
1-
BAWR7K 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())
June 03, 2016 57

Issues Resolved
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.
Getting When attempting to connect to the FGDB data get: Unable to connect to the database. Please verify that
Unexpected your warehouse-connection parameters are correct and try again. If we select More... we see: Coordinate
Coordinate System System Translation Failure. If we define .ini with COORDINATE SYSTEM keyword the error can be
1-BB25V5
Translation Failure avoided however the user expected that the coordinate system parameters could be read directly the
When Attempting FGDB data without the need for the definition of .ini file.
FGDB Connection.
FGDB Data Server FGDB is failing to serve any graphic features from customer supplied FGDB data containing a mix of
Fails To Serve Any graphic and non-graphic data. Some of the non-graphic tables contain no records which is expected. No
1-BB29E8 Graphic Features errors are displayed and the user can only see non-graphic tables served into GeoMedia. No graphic
From Users FGDB features are exposed for adding to the map legend.
Data.
Unable to install Cannot install GM 15 (any level) on system which has had GM 6.1 (any level) installed, unless 6.1 is
GeoMedia (any) removed by same user that installed it. When running Configuration Wizard get: GeoMedia Desktop 2015
2015 on system Configuration Wizard Requested registry access is not allowed. Problem is reproduced by : Install
where GeoMedia GeoMedia (Pro) 6.1 as User A Remove GeoMedia (Pro) 6.1 as User B Examine registry: Note that
(any) 6.1 was HKEY_LOCAL_MACHINE\Software\<32/64bit>\Intergraph\GeoMedia key is left. Properties of this key
installed. make removal by any user other than User A very difficult - beyond a normal user's capabilities without
1-BBZ86B 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.
Attribute columns Attribute columns of a feature/query are not available when creating pie charts or bar diagrams for spatial
of a feature/query queries on the fly. To reproduce:
are not available
when creating pie 1. Open GWS with USSample Data.
charts or bar
diagrams. 2. Add States to legend if needed
3. Feature States has 23 Attribute columns

1-B3DB0X
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
June 03, 2016 58

Issues Resolved
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.
Existing Non When reviewing the properties of an existing non-cached connection, the default value of the cache
Cached Location property does not honor the location set in File > Options, File Locations tab for Feature Cache
Connections Do Files location. Example:
Not Honor / Read
Default for Feature 1. Create new GeoWorkSpace and create non-cached, warehouse connection (do not enable
Cache Files caching) to a warehouse that supports caching.
Location.
2. Select File > Options, File Locations tab to set the Feature Cache Files location to
C:\Temp\GeoMediaCaches
1-B3DPTR 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.
Validate Geometry Have polygons inserted via GeoMedia's Insert Feature command which contain one or more arcs. The
Returns Invalid inserted polygons are presumed to be valid Composite Polygon Geometries but Validate Geometry
Geometry classifies *all polygons containing an arc as: "Invalid Geometry Component".* Only circles are considered
Component for valid. It seems that Validate Geometry considers all arcs that are part of a CompositePolygonGeometry to
Polygons With be an Invalid Geometry Component. We suspect this is not true and that the Validate Geometry command
Valid Arcs. to be in error. Other possibilities may be that: a) GeoMedia Insert Feature Arc Placement commands may
1-B4HJI8 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."
Search doesn’t 1. Invoke GeoMedia

give any records
with category 2. Make an access connection to USSampleData.mdb
feature class
3. Create a category and Add “Rivers”, “Counties” feature class to the same category
1-BC9RVV
4. Invoke Search From Analysis Utilitie s S e a rche s
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 1. Invoke GeoMedia

variable not set
June 03, 2016 59

Issues Resolved
dialog comes with 2. Make an access connection to USSampleData.mdb

Queued Edit
command. 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
Bookmark Error 1.Copy USSampleDatawithQueues.mdb. 2.Copy Queuetest.gws .Steps to reproduce:

with queued Edit
control for Dynamic 1. Invoke GeoMedia
Queues.
2. Open Queuetest.gws and select USSampleDatawithQueues.mdb If It prompts for mdb file location
3. Add all legend entries to the map window
4. Invoke Queued edit from analysis Utilitie s

1-
BC9RXO
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).
Editing Name Of When editing the Coordinate System of GeoWorkSpace, if you clear the Name field (the optional
GeoWorkSpace coordinate system name), then click into the Description field, the following error occurs: CCSDefCS Out
1-
Coordinate System of memory. The error seems to be only disruptive and not destructive. It will continue to pop back up as
BDB90W
Can Result In Out long as the coordinate system name field is not defined. The problem does not seem to occur when
Of Memory Error. running the define coordinate system utility (outside the .gws document).
Output To Feature A SR was filed reporting that Output To Feature Classes is very slow in GeoMedia 2015 when the source
Classes is connection is a CAD connection (MicroStation V8 design file) and the target connection is a new Access
extremely warehouse, whereas with GeoMedia 6.1 the same workflow completes quickly. I was able to reproduce
slow/hangs when this problem with GeoMedia 15.00.0000.120120. In my testing I observed that when using the Output to
source is CAD (V8 Feature Classes command in GeoMedia 06.01.11.13 to output the ‘Default’ feature class (containing
DGN). 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
1-DFA2B9 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’
June 03, 2016 60

Issues Resolved
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.
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.
12. 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.
Batch plotting utility Issue is reproducible in 6.1 As well. Steps to reproduce:

crashes while
doing File-> Save 1) Open batch plotting utility and select new sheet composition mode.
and then File-
>Close. 2) Click on Geoworkspace Browse and select BPU_PVTTesting_ValidGWS.gws.
3) Browse and select any layout template.

1-
DFLWW3
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.
Create Conflation UPDATED DESCRIPTION BASED ON RESEARCH BY DEVELOPMENT: When there is a long link and a
Links can lead to short link being evaluated and the long link is outside the zone - no link is made. This needs to be
gaps in LRM when corrected. Practically these conditions will not exclusively exist in only one connection and percentages
1- short links are will appear in both connections. If the connections are reversed the link is made because the buffer is
DJOZQC evaluated against drawn around the long link and the short link is in the zone. However, if there are now 2 short links in the
long links. 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.
Throwing "Out of Steps to Reproduce:

Memory" error after
emptying the 1. Invoke Define Coordinate System File Utility.
1-DB21OZ
storage center
fields of Storage 2. Click on Storage Space tab.
Space tab.
June 03, 2016 61

Issues Resolved
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
"Coarse Overlap" Steps to Reproduce:

misspelled as
"Course Overalp" 1.Invoke GeoMedia
in Spatial Filter
1-DBFEHL Dialog box help 2.Invoke Spatial Filter command
documentation.
3.Invoke Spatial Filter Options dialog
4.Press F1 for help Observation: "Coarse Overlap" misspelled as "Course Overlap"
Incorrect icons are In the GM GUI, the Customize Ribbon dialog is showing the incorrect icons for commands. In this test
shown in "Custom case, the screen prints show that the icon for a command in the right panel actually matches a command
1-D8VTJC Ribbon" form for that is 2 commands/icons back from the current icon/command. The screen prints will help clarify the
custom ribbon bar problem.
with gm commands
Display Location This problem is in GM 2015 also. Display Location Functions fail if loacations.xml is not in
Functions fail if C:\GeoWorkspaces because the registry entry for the GM preference set name "xmlPath" is set to
locations.xml is not "C:\GeoWorkspaces". The user is doing the following workflow resulting in the Display Location command
in not working:
c:\GeoWorkspaces
. 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
1-BYCUX8
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.
4. 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.
Dynamic Customer has noted noticed a serious problem where query results of Dynamic Segmentation in version
Segmentation 2015 is invalid. The customer points out that version 6.1 and version 2014, dynamic segmentation is
Creating Invalid / considered correct whereas the same GeoWorkSpace when opened in 2015 produces invalid geometry
Corrupted collections.
Geometry.
The problem is causing invalid results for this query and all subsequent queries in user’s workflow.
Workflow using supplied data:
1-BZ6HI0
(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
June 03, 2016 62

Issues Resolved
"Standard Anomalies" options, we can see that the collection geometries are invalid.
Attributes are not Attributes are not getting appended on selecting the attributes button from join command and it throws an
getting appended error on GM. Steps to reproduce:
on selecting the
attributes button 1. Invoke GeoMedia.
from join
command. 2. Select Blank geoworkspace.
3. Make an Access connection (USSampledata.mdb) and select an new category.
1-CPZE0F 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 ---------------------------
Grid > Utilities > During support workflow testing it was discovered that the '+Add' button will generate an unhandled
Create Elevation exception.
Footprints.
Command exits Error message is: ----------------------- Create Elevation Footprints X Unhandled exception has occurred in a
when the '+Add' component in your application... Could not load type
button is selected. 'Intergraph.GeoMediaGrid.Private.Utilities.FootprintFileNotSupported' for assembly '3DMLHelper,
Version=14.0.0.0, Culture=neutral, PublicKeyToken=41c4fcd3487160b5' -----------------------
1-CQ5GK9
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.
Properties dialog When using new (WPF) Attribute Properties dialog, values are displayed incorrectly for data type SINGLE.
fails to display the Behaviour is a regression from 2014.
correct value for
SINGLE data type 1. Edit a feature with SINGLE GeoMedia datatype.
field.
1-CF76CV 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.
Symbol style using Text size and color fill problems using Microstation cell as symbol style. User has GeoMedia symbol style
MicroStation cell defined that references Microstation v8 cell. The cell displays correctly in GeoMedia 6.1 but when
does not display displayed in 2014 or 2015, some text components are not correctly sized/positioned and also some
1-CG91D5 correctly. 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.
June 03, 2016 63

Issues Resolved
2. Copy or move the cell (.cel) library from C:\Warehouses\1-741933221 up to C:\Warehouses.
3. Open Sym2_cel.gws.
Observations: Notice how the text is not sized correctly. Notice also how the shapes representing the
exclamation mark are not filled black.
Symbol style using User has GeoMedia symbol style defined that references Microstation v8 cell. The user has noted that the
MicroStation cell cell displays correctly in GeoMedia 6.1 but when displayed in 2014 or 2015, the arcs are not correctly
arcs do not display displayed. Workflow:
correctly.
1. Save attached .zip and save to C:\Warehouses and extract to here. Folder C:\Warehouses\1-
741933221 is now available.
1-CG91EB
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.
Cannot Install It does not appear possible to install language packs in silent mode. Please provide a viable workflow.
Language Packs In Currently the following 4 suggested steps fail:
Silent Mode.
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”
1-
CGDEXZ 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>
4. 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.
Boolean attribute When ‘Feature Definition’ is used to add a Boolean attribute to an existing feature and the default value is
with Default value set to True, the Boolean attribute is populated with the value of False instead of True when the feature is
of True is digitized with the Insert Feature command. Here is a summary of the steps to reproduce the problem:
populated with
value of False 1. Start GeoMedia with a blank geoworkspace.
instead.
1-CILA85 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’.
4. Use the Insert Feature command to digitize one or more instances of the feature that you just
June 03, 2016 64

Issues Resolved
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.
The title of profile The title of profile chart has "and" in English on the localized version, This "and" is hard coded and needs
chart has "and" in to be externalized for the localization.
1-CIMR6L
English on the
localized version.
Hard coded strings Hard coded strings in modBatchPlotting.bas. Need to extract strings for the localization. The English
in message displayed when Layout Template was not located on Sheet Composition. The corresponding
modBatchPlotting.b string is defined in modBatchPlotting.bas. frmMissingInfo.Label1. There are more strings hardcoded in this
1-CJR6TD
as. Need to extract file. Need to extract those strings to rc or drx files for localization.
strings for the
localization.
Thematic fill is not This is a latent issue observed on GM15.01 bld120 and GM16. Bld458 as well. Steps to Reproduce:
honored properly.
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.
1-
CQSHDF 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.
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.
June 03, 2016 65

Issues Resolved
If we uncheck and check Fill option again at Step#6 then fill is shown properly.
Unable to work Unable to work with GPS Tracking after performing labelling workflow with leader line. Steps to reproduce:
with GPS Tracking
after performing 1) Invoke GeoMedia.
labelling workflow
with leader line. 2) Make an Access Connection (USSample Data.mdb).
3) Add legend entries states.
4) Select label manager and click properties button.

1-CTH9RL
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
Issues observed OTFC from FGDB to FGDB with 'Append and Update' or 'Update' mode and observe that it logs error
with OTFC message saying “Only Append operation can be done because the target primary key field is an
'Append', 'Append autonumber field.” Error. And is displaying the existing records. This is observed even when we do OTFC
1-CVBVPB
and Update', from Access to FGDB. Also when we do OTFC from Access to FGDB with 'Append' mode, it is appending
'Update' modes to the new records with the existing.
FGDB.
Selecting the Selecting the leader line and performing workflows related to map window throws an error. Workflow1:
leader line and Steps to reproduce:
performing
workflows related 1. Invoke GeoMedia.
to map window
throws an error. 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.

1-
CWCFKZ 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:
•Invoke GeoMedia. •select leader line. •
click ok on the warning message.
•select Add Map window
June 03, 2016 66

Issues Resolved
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.
4. Select Queue edit from Analysis tab.
Oracle Data Oracle XE 11.2 installed, but oracle dataserver not available for GeoMedia GeoWorkSpace connections
Servers Not after running configuration wizard. The same behaviour is found with versions 2014 and 2015 of
Registered If Using GeoMedia. Environment: Windows 7x64 Oracle XE has been installed: (version x32 was used)
Oracle XE. http://www.oracle.com/technetwork/database/database-technologies/express-
1- edition/downloads/index.html. Installed GeoMedia Professional version 2014 or 2015 but no Oracle data
CWFQBP 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.
Active X error Steps to Reproduce:

followed by
Automation error 1 .Invoke GeoMedia Professional. Create blank Geoworkspace. Make SQL connection to USSampleData.
while working with Issue observed with both IFC ON and OFF also
Copy Attributes
definition 2. Invoke Copy Attributes Definition command. Select Rivers as Target and Interstates as source FC.
command.
3. Click on Select All button and click on Ok button. Click Ok on the New Attributes dialog that pops up.
1-CXFHK9
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. ---------
June 03, 2016 67

Issues Resolved
------------------ 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”.
Error - Component Selecting the Style Properties gives and error when large amount of images are loaded. To replicate open
Vtest6.ocx or one USSampleData.GWS. Add a large number of images. Display the images and the right click on a linear
of its dependencies feature (Rivers) and select style properties and the errors will come up.
1-CXO14L
not correctly
registered.
GeoMedia 2015.
Display CAD Files Using Display CAD files causes the Z values of many (but not all) arcs that get ingested to have their Z
alters Z values on values get altered by many feet. Have attached a data set that shows the problem, along with a
1-D3EBR2 arcs. 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.
Dynamic Labelling Regression, unable to reproduce on GM 2014.

causes GM to
crash. 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.
1-C3DA26 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.
Documentation > GM2015 SP1 > Help > Search for 'coordsystems'. Under topic 'Advanced Options' document says: "The
Default C:\Program Files (x86)\Common Files\Intergraph\CoordSystems\Program\EPSG folder is designated to be
CoordSystems the default CoordSystems folder." This folder no longer exists with version 15 sp1. Document needs to be
1-C3DBIS folder does not corrected. Search of the hard drive reveals two EPSG folders placed by installation of GeoMedia 15 sp1.
exist. 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.
GeoMedia exe The GeoMedia exe should replace the startup splashscreen with the one defined in the framestamp .xml
does not honor passed in on the command line. This is not being honored in GM 2015.
1-C67V6J splash screen
specified in frame
stamp file.
Help Topic Help topic on "Executing Schema Remodeler from the Command Line" states that: To run Schema
Executing Schema Remodeler from the command prompt, the syntax is: SchemaRemodeler.exe <parameter file>. You must
1-C76BHX
Remodeler from be at the GeoMedia Professional\Program folder or have it in the path (for example, C:\Program
the Command Line Files\Hexagon\GeoMedia Professional\Program). While the path noted above does exists, it is NOT the
Gives Incorrect correct location for running SchemaRemodeler.exe. The current target location (as of version 2015, build
June 03, 2016 68

Issues Resolved
PATH Info. 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.
Display Locations The named locations UI layer was rewritten in C#. In doing this, the GSM-specific hook for plugging in a
regression for custom persistence mechanism was accidentally dropped. This capability needs to be reinstated.
1-C878KB
GSM-specific
persistence logic.
WFS connection An SR was filed for the failure of GeoMedia 2013 to connect to a specific internal customer WFS (non-
fails with public). The customer notes that the same WFS works fine with GeoMedia 6.1 and GeoMedia 2014 WFS
GeoMedia 2013, data server. Since the WFS is not public we cannot duplicate the issue, but problem appears to be similar
same WFS works 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
1-AH5DID
in 6.1 and GM that if the same fix is made in 2013 it may resolve this problem as well. The error from the customer WFS
2014. 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.
Setup - Desktop Starting with version 14.00.0002.143, GeoMedia Desktop is installing files required by GeoSpatial
installs wrong Datapipe to C:\Program Files (x86)\Common Files\Intergraph\GeoMedia\Program\QD. The files delivered
1-
version of .dlls. are out of date, causing that program to fail to run properly. The correct versions are delivered by
ANFOZW.
GeoSpatial Datapipe, but they are not being loaded when GeoMedia Desktop starts, due to system
pathing issues
GMSmart client - Open the attached gws file.

styles are not
imported properly. - 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.
1-BY42BJ
- Click “Ok” on dialog.
- 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.
Invalid row gets Invalid row gets committed to IFC file but not in Oracle or SQL Server Database. Note: This is also
committed to IFC observed in 2015 release as well, but not observed in 2014 release. This is observed with both Oracle
file but not in and SQL Server read-write connections with IFC ON, but not reproducible with Access RW connection.
1-BY5XN3
Oracle or SQL Steps to reproduce:
Server Database.
1. Create a RW Oracle or SQL Server connection with Feature Caching ON.
June 03, 2016 69

Issues Resolved
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.
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.
Locations - Double Locations - Double clicking on list box scroll bar is invoking location properties dialog. Workflow to
clicking on list box reproduce:
scroll bar is
invoking location 1. Invoke GeoMedia and make a connection to USSampleData.mdb
properties dialog.
2. Add Counties legend entry to Map Window. -Invoke Name Location command and enter a big name
1-BY899F (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.
Display Location – Clicking OK on Display Location Options is clearing the location from Named Locations drop-down menu.
Clicking OK on Workflow to reproduce:
Display Location
Options is clearing 1. Invoke GeoMedia and make a connection to USSampleData.mdb.
the location.
2. Add Counties legend entry to Map Window.
3. Select Display Location to make Display Location dockable control visible.
4. Select a location say “Location1” from Named Locations drop-down menu.
1-BY89GO 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.
Database Utilities On systems where SQL Server Native Client 10.0 or higher is not installed, users of MS SQL Spatial data
1-BEF6HN For MS SQL will notice error messages stating that the Native Client software is required to correct metadata for date
Spatial fields. Unfortunately this message appears up to eight times when working with warehouses that do not
Warehouses May contain any date fields. While the problem is mostly a nuisance, it does indicate flawed logic that it's
June 03, 2016 70

Issues Resolved
Display Incorrect appearing multiple times and when date fields are not present. Example Workflow on system without any
Error Message SQL Server Native Client 10.0 or higher is *installed:
Multiple Times.
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
Incorrect Logic For FGDB forces users to make registry edits to use .ini files. User definition of an .ini file (when one is
FGDB Data Server provided as part of the connection) should never be ignored. The current approach causes problems for
Use of Initialization multiple reasons: 1. GeoMedia users have expectation that .ini files will be used if specifically provided.
(.ini) Files. 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
1-BET1VE
.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
Display Locations 1. Launch GeoMedia.

Command:"Show
recent locations" 2. Make a read-write connection to Access database.
functionality is not
working as 3. Add Legend entries.
expected.
4. Invoke Display Locations command.
5. Add 3 locations.
6. Invoke "Display Locations Options" dialog box on Display Locations dockable control.
1-BFRULH
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.
June 03, 2016 71

Issues Resolved
Unique Value Steps to reproduce:

Thematic
command throws 1. Copy ExportData.mdb to C:\Warehouses.
an error while
classifying 2. Make an Access read-write connection to Exportdata.mdb
1-BFUCZ3 "Currency" data
type. 3. Invoke Add Thematic Legend Entry. Select Input Feature as “SourceFeatureClass” and type as
“UniqueValueThematic”.
4. Select “TestCurrency” as AttributeforClassification. Click on Classify button. Observe that an

error message "Invalid procedure call or argument" pops up.
Crash to Desktop Region reports, support duplicates crash of product when attempting to insert their BigTIFF image in
when inserting GMDesktop. Crash to desktop, possible data loss.
1-BFYPVT
valid BigTIFF
image.
Symbol styles that Symbol styles that contain arcs are displayed in wrong direction in the GM map window. If using a
contain arcs are GeoMedia Feature Symbol file style that contains an arc the symbol/arc is displayed in wrong direction
displayed in wrong (reflected) when using it for point geometry in the map window. Problem just occurs in GeoMedia Desktop
direction in the GM 2015, in 2014 the same symbol style is displayed correctly. Tested with symbol styles that are created
map window. with the "Define Symbol File" utility in GeoMedia 2014 and 2015, problem occurs in both cases.
1-BKCGL3
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.
Automation error 1. Extract the attached rar file to C:\Temp.

when running
Validate Areas 2. Open the ValidateIssue.gws from the attachments and modify the mdb paths if required.
command with
Coarse Overlap 3. Run validate areas command with options as below. FeaturesToValidate -
spatial operator. RECORDED_FABRIC CompareToFeaturesIn - RECORDED_FABRIC_LINE Minimum area
overlap- 90
1-
4. Check display results in map window and uncheck display results in data window.
BKCHWJ
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.
Legend Key The size of the key graphics in the Map Window Legend has changed from 2014 to 2015. In 2014 the size
1- Graphic size has of the circle (predefined) keys and that of the square (from BaseMap.fsm) are roughly the same. In 2015,
BKGDM8 changed from the symbols from the .fsm file are quite small in comparison. - Legend Properties do not account for this
2014. difference - they are identical in both .gws files.
Unable to connect Unable to 3. connect to File Geodatabase (FGDB Read only) in GM 2015 and GM 2014. Connection error
1-
to File
June 03, 2016 72

Issues Resolved
BMOG1J Geodataabse in states "Coordinate System Translation Failure". Dataset attached:

GM 2015 and GM
2014. CoordSys 1. Open blank .gws.
Translation Failure
2. Create a FGDB Read only connection using the SAN_PABLO.gdb and San_Pablo.ini file.
3. "Coordinate System Translation Failure" after click OK to create the connection.
MS SQL Dynamic Comparing Dynamic Labelling of identical linear feature class using same label definition (Label size/Rule)
Labelling of Access vs. MS SQL shows that Access labels are generated up to ~98% faster than equivalent labels
Performance and features stored in MS SQL (GDO). In the test case ~600K Tennessee state-wide local roads are
Problem If displayed but less than 50 are within the map window display (map view display scale is ~1:14,000). No
Compared to Spatial filter is applied however it is expected that the label processing by design should only be working
Access GDO with the records/geometries displayed/overlapping the bounds of the map view.
1-BNO1HL
Dynamic Labelling.
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.
Schema Schema Remodeler throws a CLSID error and unable to perform operations. Steps to reproduce:
Remodeler throws
an error and 1. Invoke GeoMedia.
unable to perform
operations. 2. Change the default path of geoworkspace location to some other location using File Locate
1- Options dialog.
BNWGSB
3. Invoke Schema remodelled.
4. Select new transformation warehouse.
5. Launch GeoMedia. Observation: Unable to perform any operations on Schema Remodeler.
GeoMedia crashes GeoMedia crashes when trying to add any command without selecting any command from vector tab from
when trying to add Customise ribbon. Observations: GeoMedia crashes. Solution: For the remaining tabs at least one
any command from command is in selection state. Here there is no selection of command. Hence if Add button is in enable
1-BPQUZ9 vector tab from state at least one command should be selected by default. This is the case even with the Grid tab. Steps
Customise ribbon. 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.
WMS display fails WMS display fails to display for specific EPSG codes on specific URLs when using German regional
for specific EPSG settings WMS display fails for Gauss Küger Projection with datum "Deusches Hauptdreiecksnetz" on
codes on specific several services when using German regional settings: To reproduce the problem:
URLs when using
German regional 1. Set Regional settings to “German – Germany”
settings.
2. Connect to the appropriate service.
1-
BQVM9R
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.
June 03, 2016 73

Issues Resolved
Failure to Open I have an older version 6.1 GeoWorkSpace that fails to open in 2014 or 2015. GeoMedia application
Old crashes as the GeoWorkSpace is opened. The same GeoWorkSpace opens fine in version 6.1. The
GeoWorkSpace in problem may be related to thematic legend entries as if we use version 6.1 to delete all thematic legend
1-BS1PO4
2014. 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.
Properties dialog The 2015 properties dialog may fail to display stored attribute values if the field is associated to a picklist
can fail to display that has an attribute filter in place. If the user has filter string applied to his/her picklist and an existing
attribute values value for the field/record does not pass the SQL statement, the value is displayed blank on the properties
when picklist filter dialog grid. Problem is a regression from behavior observed in version 6.1 and 2014. It is expected that if
in place. 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
1-JYHPDC 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.
Display Labels fails A customer reported that when running the ‘Display Labels’ command under the ‘Labelling’ menu an error
when GM is message was displayed stating that “An error occurred in the underlying database”. This problem was
running on same also reported to MapText and their development group discovered the cause of the problem and provided
machine with older a patch via the LabelEditSupport.dll that fixed the problem in GeoMedia with the Display Labels command.
MapText LabelEZ
product. The Labelling Generate Static Labels tool creates a table named as <output name>_PRP. Previous
1-JYJ7PQ
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.
Text disappears Text disappears/shifted using CAD .INI file SERVE CELL GEOMETRY:Explode for Microstation V8 DGN
using CAD .INI file text elements (LO1 dataset) even though the text is not part of a cell. Also some data is rotated out of
SERVE CELL position (T2 dataset) when SERVE CELL GEOMETRY:Explode When the INI parameters are changed
GEOMETRY:Explo from SERVE CELL GEOMETRY:EXPLODE to SERVE CELL GEOMETRY:TRUE, the data issues of text
de USTN V8 DGN not part of a cell disappearing is not a problem. Using the SERVE CELL GEOMETRY:TRUE is not an
elements. 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.
1-K168FQ
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
June 03, 2016 74

Issues Resolved
GEOMETRY:TRUE in the .ini file to see the text displayed without any problem.
4. 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.
Data Window: Currency values defined in AFM Model fail to display in data window views. If you attempt to sort the data
CURRENCY data window column of currency data type values, referenced in AFM enabled connection the following error
type values fail to message appears: --------------------------- GeoMedia Desktop Error sorting data view. If AFM is disabled for
display from AFM the connection, the error does not occur. Example workflow using supplied data:
enabled
connection. 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.
1-K1NZFP 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.
Properties dialog NULL values for CURRENCY are displayed as $.00 on the Select Set Properties dialog (Attribute
displays NULL properties). It is expected that a null value should be displayed as a blank. Unfortunately, a true value of 0
1-K1PM5G
CURRENCY (zero) also displays as $.00 thus users cannot use the Properties dialog to determine if the value is NULL
values as .00. or 0 (zero).
Currency values User has noted the Placement and Editing option "Copy attributes from previous feature fails to correctly
multiplied by x1000 copy currency values for AFM enabled, MS SQL features. Problem occurs for both GDO and Spatial type
for Insert Feature MS SQL Server connections. The previous currency value copied to the next new feature is multiplied by
of AFM enabled 1000. The problem seems to be restricted to when Operational Class associations are defined with Event
MS SQL features. 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
1-K1PY1U
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.
Validate Toolbox > Validate Connectivity for automatic fixing of Unbroken Intersecting Geometry may delete
Connectivity to fix portions of arcs when processing oracle data. When processing Access GDO stored arcs, invalid
Unbroken geometry components are created.The problem as noted for Oracle represents a loss of data with no
1-K3FXFK Intersecting recovery, and with no warning/message to the user of data loss. Attempting to use Undo results in the
Geometry results in following error: GeoMedia Desktop Method '~' of object '~' failed.
loss of data or
invalid geometry. 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
June 03, 2016 75

Issues Resolved
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)).
Performance using Customer reports the following issue/observation when using Net Cached Shared files (PublishIFC with
shared cache via /cachemode Shared option): With newly created net cache file IO Load is almost exclusively Oracle.exe
PublishIFC is not (Initially it’s primarily GeoMedia.exe then switches to Oracle.exe) Load time is slow (1 min). It seems that
as good as GeoMedia tries to use the Net Cache files then ends ups using Oracle instead. With old net cache files
1-
expected load takes substantially longer (~3 min). The reported slow load time is presumably when compared to
K4DOCB
(compared to local Local Cache files since the customer reports the following observations when using Local Cache files:
cache). 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).
Publishing Version User has noted a degradation of performance in the Publish to SmartStore command specifically when
8 CAD Data to publishing MicroStation Version 8 CAD (.dgn) data. Support observes that a performance drop of 4x is
SmartStore Format seen when any Version 8 CAD graphic attribute value is published. Problem is a regression from the
Slower in 2015. 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

1-K6P9AR
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
Create Links can Users may obtain incorrect X and Y values in the GMFLinear_Linked table results from the Create Links
result in incorrect X command. In the given data we see that an incorrect XY value for the Connection 2 End X and Y value.
and Y values in The value does not match that of the ending value from Geometry Information. The value also does not
1-JJQ6GJ GMFLinear_Linked match the connection 2 start X and Y for next segment thus a very small gap is created. See also
table. 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).
GTech Dataserver GTech Dataserver fails to update GTech record count after refreshing GTech data server connection. For
fails to update complete workflow see attached video. Dataset connection information attached. The
GTech record GM_VELUMINAR_PT feature is added to the Map window from the GTech data sever connection which
count after reads the flat View GM_VELUMINAR_PT. In GTech the GM_VELUMINAR_PT feature is edited/updated
1- refreshing GTech and posted. After the GTech post the GM_VELUMINAR_PT view is directly accessed through SQL in the
JM0CWV data server database the amount of records are viewed. In GM if the GM_VELUMINAR_PT feature is queried from
connection. 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.
June 03, 2016 76

Issues Resolved
Legend entries are The test workflow explains the problem. A new Legend Entry is loaded to the Legend and a feature that is
shown as being currently set to Display Off is being loaded for display. In the customer's case, it is a legend entry with
loaded despite 200K plus records, so it is hindering load/display time. Here is a workflow that reproduces the problem on
having 'display off'. 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.

1-JM7EZO
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.
Attempting to Attempting to select certain thematic classified items in mapview results in bookmark error. Given problem
select certain is a regression from version 2014. User has provided data and workflow that results in bookmark errors.
thematic classified See attachments for data and graphic which depicts which graphics should be selected to see the
items in mapview problem. Attempting to select either of the graphic items noted results in the following errors: ----------------
1-JM8951
results in bookmark ----------- pservice --------------------------- The given bookmark is either bad or not created by this server (or
error. this version of the server). --------------------------- OK --------------------------- ---------------------------
GeoMediaCommand(Properties.Activate) --------------------------- Object variable or With block variable not
set --------------------------- OK ---------------------------
Tooltip displaying Tooltip displaying connection info under Legend area rarely works. To reproduce: Steps to reproduce: 1.
connection info Open any Geoworkspace 2. Hover over a legend entry in the legend. No tooltip is displayed.
1-JMFEJP
under Legend area
rarely works
Incorrect results When attempting to move a vertex with Edit Geometry, the selected vertex may be moved twice the
using Edit intended distance. The problem seems to occur after use of the Move command when a click & drag
Geometry action was used for the move. Customer / Region reports that the problem can subsequently lead to a
command - Moving application crash but this could not be reproduced by support. See also Attachments for video (.wmv) file.
vertex results in 2x The problem in this case references .mdb format Access GDO warehouse data. The problem also occurs
distance move. 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.

1-JMO6UJ
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
June 03, 2016 77

Issues Resolved
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.
Snap Vector Points Snap Vector Points option is not available on 2015 Build 10205, after adding the required registry entry
option not available which is a regression from 2014, build 143 and higher. The Snap vector points option is enabled based on
1-JNGREY after registry edit. user preference registry key. Create this registry entry under
HKEY_CURRENT_USER\Software\Intergraph\GeoMedia
Professional\15.00\PreferenceSet\SnapVectorPoints
Unable to insert a Workflow:

feature class on 3D
view using the 1) Launch GeoMedia Professional.
insert feature class
command. 2) Select blank geoworkspace.
3) Make an Access Connection USSampledata.mdb.

1-JNH5SJ
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 ---------------------------
PProService Overflow --------------------------- OK --------------------------- GM Build:16.00.0000.00668 GM
3D build 16.00 79
Need Oracle There was a fixed done for the Oracle data server on GM 2014 to work with Oracle 12c. This addresses
Performance Fix poor performance of that data server. That fix is in SP2 version 163. Development mentioned that this fix
for Oracle LTT was not included into the Oracle LTT data server for 2014. The G&T business unit needs that fixed to be
1-FVUE2R 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.
WKT->CSF issue. We're using the GeoreferenceService to convert a WKT string to a Coordinate System. The projection
Projection parameters on the result coordinate system is all 0. The datum is also incorrectly interpreted as WGS84.
parameters and Longitude of origin should be: 9:00:00.000 FalseX should be: 3500000 Datum should be: Deutsches
datum not loaded, Hauptdreiecksnetz WKT was generated from the "GetWellKnownText" function on the CoordSystem
results in incorrect object. The WKT string is: PROJCS["DHDN / 3-degree Gauss-Kruger zone 3", GEOGCS["DHDN",
1-JGPJUR placement of data. 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]]
The default Name The default Name is English. It should be localizable. Add/Edit Feature Class Definitions dialog box >New
1-JJDYL5 is English. It should > General tab "NewFeatureClass"
be localizable.
The default names The default names in Schema Manager are "PickList" is not localizable. Needs to be externalized
1-JJDYOD
in Schema Example Define PickList… > New "PickList" Add to Globals dialog "DeafultNamed Group" "NamedGroup"
Manager are
June 03, 2016 78

Issues Resolved
"PickList" is not
localizable. Needs
to be externalized.
Legend Count of A customer reported and provided data where we can see that the Count of All Features option is
All Features reporting incorrect values for legend entries associated to a range thematic. The problem is a regression
incorrect for from version 2014. For example in 2014 a thematic range of 0.90 to 1.0 may show 19/19 features where
1-JJFNMA thematic legend the same entry in 2015 may show: 0.90 to 1.0 19/14 features; notice how the count of all features is
entries. 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.
Fence Select does Customer has provided data where we can see that attempting to select all features using a Fence
not select all selection results in many items that are NOT selected. The problem is a regression from 2014. In the
features. given case the user has 20 legend entries which are part of a thematic classification. Steps to Reproduce:
1. Open GeoWorkSpace using 2015.

1-JJG4CN
2. Use Fence Select to click and drag a large fence around given features.
Observation: Some features are not selected. Problem persists even if all geometry problems are either
fixed or deleted.
Hard Coded default Hard Coded default names on Validation commands. Needs to be externalized for localization Validate
names on Geometry/Connectivity > Input> Save As dialog "QueryNames" Validate Geometry/Connectivity >
1-JJHM1H Validation Anomalies Tab > Save As dialog "AnomalyDefinitions" Detect Void Areas > Output tab "VoidAreasQueue"
commands. Need Resulted Queued Edit "Void Area" Automated Validation> General "Connectivity" "Geometry".
to be externalized.
WMS Layers fail to A SR was filed with the following description (with corrections for typos/grammar): “This is a regression
display when using from GeoMedia 2014 where this worked fine. Attached WMS_GermanRS.gws demonstrates the problem.
German (Germany) Open the GeoWorkspace with English regional settings and the layers will be shown. Then go to Control
format on Region Panel and configure regional settings to German (Germany). Open the GWS again. The Layers won't be
and Language shown and the GeoMedia Map Window remains gray. WMS URL: http://www4.web-
dialog. 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
1-JJK06H
(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=&F
ORMAT=image/png&TRANSPARENT=TRUE&BGCOLOR=0xFFFFFF&EXCEPTIONS=BLANK&CRS=EP
SG: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.
A Manipulate A Manipulate Feature Web Service (WFS) does not appear to support the filter 'matchCase' attribute to
Feature Web enable case-insensitive searches. The 'matchCase' attribute is allowed on the following binary comparison
1-H4EPPV Service (WFS) operators: PropertyIsEqualTo PropertyIsNotEqualTo PropertyIsLessThan PropertyIsGreaterThan
does not support PropertyIsLessThanOrEqualTo PropertyIsGreaterThanOrEqualTo ...well as: PropertyIsLike An example
case-insensitive 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="."
June 03, 2016 79

Issues Resolved
searches. 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
Edit Geometry A customer SR was filed reporting that using Edit Geometry on a triangle shaped area feature in Oracle
result is incorrect where the feature class coordinate system was set to UTM Zone 11 with a WGS 84 datum would result in
for a triangle area incorrect geometry after the edit. To reproduce the issue:
feature in Oracle
when vertex is 1. Open the UTM11WGS84.gws which has an Oracle Read-Write Connection to
moved twice. 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.
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).
1-H4Z5NJ
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.
Attempting to insert When the user opens the Raster > Insert Georeferenced Images command, by default the georeference
ERDAS .img files mode is 'Automatic'. After the user navigates to a folder with ERDAS .img files, and selects a file to push
results in incorrect to the right side of the dialog, the georeferencing mode switches to 'world file'. This should not happen,
1-HGIJ4U
georeferencing since there is no world file present in the folder corresponding to the selected image. One of the files in
mode selection. 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.
Measure Area Measure Area Command is broken on GeoMedia 3D. Steps to reproduce:
Command is
broken on 1. Install GeoMedia Professional and then install GM 3D.
GeoMedia 3D.
2. Make an Access Connection USSampledata.mdb.
1-HHBFS3
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 ---------------------------
SQL Server Spatial SQL Server Spatial, area and line features created or edited in version 2015 cannot be displayed in
features created in previous versions of GeoMedia, even when using the GeoMedia SQL Server Native Spatial R/W Data
1-I59SC2
2015 do not display Server Expansion pack data server. Example workflow:
in previous
1. Use 2015 to connect to some MS SQL Native Spatial database such as NS_Alabama in
June 03, 2016 80

Issues Resolved
versions. 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. While
GeoWorkSpace objects are often not backwards compatible, we normally do not see compatibility issues
for the spatial data itself.
Validate Using the Validate Connectivity command to locate and fix (Auto correct = Yes) Unbroken Intersecting
Connectivity geometry can result in an unexpected error and failure to fix/break unbroken intersections.
Unbroken
Intersecting The following error is observed when attempting to break water lines where they intersect water valves (a
Geometry results in point feature class). --------------------------- GeoMedia Desktop --------------------------- Automation error The
automation error. object invoked has disconnected from its clients. --------------------------- OK ---------------------------
1-I98R63
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.
Unrecoverable An SR was filed by a customer reporting that they were regularly seeing a failure when opening
‘Encountered an GeoWorkSpace where an error message with the title GeoMedia Desktop and the text “Encountered an
improper argument’ improper argument.” was displayed. Upon researching this issue we discovered that the error occurs when
error occurs opening a number of GeoWorkSpaces that contain a Layout Window within a single session. Specifically
1-FOMHL7
opening .gws files it appears that if you open more than five .gws files that contain a layout in a session the error appears
with layout. 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.
Issue with Object When we make a connection to Object Space data server in IMAGINE, Code Attribute name and Custom
Space Data Server Attribute Names labels are not displayed properly. This problem is also seen in 16.00. Attached is the
1-EH0BVX
GUI when invoked screen shot
from IMAGINE
Add Legend Region has noted a potentially serious performance issue for MS SQL Server Native Spatial data server
Entries fails with logic when working with spatial filters and large feature classes. Display a spatial filter and add a point
1- very poor feature to the legend which takes 1 second (great performance). Delete the legend entry, then add the
EOAH7M performance for feature to the legend a second time for the same feature. The same feature with the same filter now takes
MS SQL Native 50 seconds. This is with a point feature of approximately 1 million records. User has point feature of 12
Spatial. million records and is terminating the GeoMedia session due to lack of response.
Low certainty score Line to Line linking problem. We are seeing very low certainty scores assigned to small links which occur
values returned on at internode (valence = 2) locations. It seems that the software is comparing the length of the one link to
1-G99UQI
short links where the entire projected distance of the other geometry resulting in a very low score. Problem background: It
valence = 2. 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
June 03, 2016 81

Issues Resolved
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.
Queued Edit Map User has noticed that simply loading queued edit and navigating to next item in the queue, can cause the
1- Window does not Map Window Properties to change to unexpected values that cannot be accounted for in either: a) Queued
G9QWMW use proper map Edit options or b) Map window settings.
window properties.
Lose active map User has noticed that adding a conflation link in the active map window and navigating to next item in the
1- window properties queue can cause the Map Window Properties to change to unexpected values that cannot be accounted
G9QWRR after adding for in either: a) Queued Edit options or b) Map window settings.
conflation link.
HardCoded HardCoded message on Manage Edge Match Rules. The following strings need to be externalized for the
message on localization,
Manage Edge
1-GCY9A8
Match Rules. ' 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).
Validate Area on Validate Area on Cadastral does not work on the decimal point ",". The languages which has decimal
1- Cadastral does not point of "," are: European languages as well as Russian. When changing the decimal point to "." (Period),
GDG9H7 work on the then this command works.
decimal point ",".
Schema Schema Remodeler: Hard coded default names need to be extracted for the localization
Remodeler: Hard NewFeatureSet(frmFeatureSets.frm and ucFeatureSets.ctl) NewField(FuncAttributesBase.ctl) Sequence
coded default (modAttrValTableDefs.bas).
1-GL2AG2
names need to be
extracted for the
localization
Moving a shared Moving a shared vertex on area features will fail after a group move of fence-selected features. Maintain
vertex on area Coincidence is turned on. Steps to reproduce:
features will fail
after move of fence 1)Select area feature with shared edge/boundaries (highlight)
selected features.
2) Select Vector->Edit
3)Move a vertex – successful – both area features adjust
4) Fence select features

1-F4K6XI
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.
June 03, 2016 82

Issues Resolved
When editing 2 or When editing two or more features, the features do not maintain coincidence when you add a vertex and
more features, it move it. It creates the vertex on both lines. It doesn't matter how many lines are edited, maintain
does not maintain coincidence does not work when selected/enabled. Two features which share one coincident segment
coincidence when when edited do not maintain coincidence if edited. Simple dataset attached with recording showing
you add a vertex workflow.
1-F55CQV and move it.
1. Create select set of both features with coincidence enabled
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.
No tooltip No tooltip is displayed when hovering over legend entries with German language pack. Unable to get the
displayed when information for Warehouse connection by hovering over the legend entries. Sometimes it works, but mostly
hovering over the tooltip doesn't bring back the connection and feature class name for legend entries.
1-F6H46K
legend entries with
German language
pack.
GM Feature GM 2013 Feature Symbol File fails to display correctly in GM 2015. Regression from GM 2014 because
Symbol File fails to FSM displays correctly in it.
1-F783Y1
display correctly in
GM 2015.
Load Styles > The documentation for the Load Styles - ' 'Match style names with thematic classes' states that the style
'Match style names matching is based on the thematic label, but this is incorrect as it is actually based on the thematic value.
with thematic The documentation for the checkbox currently states: "If the check box is checked, the option tries to
classes' option is match the thematic label with the matching style name before overriding the style." However the
1-FCYE6J documented 'GMUniqueValueLegendEntry Control Design Specification' states: "If the “Match style names with
incorrectly 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.
Can't open When trying to open attached geoworkspace GeoMedia Pro replies with: "Failed to open document”.
1-FFFTQM geoworkspace
customer .gws
German Language There are some missing translations in German Language Pack SP1 for the Layout - Drawing commands
Pack 2015 SP1 not which were already translated in German language pack 2015. Please see attached doc file with
1-FFGIMU
translated examples.
completely.
BatchPlotting and Two utilities, Batch Plotting and Define Symbol File published through XenApp 7.6 crash on invocation
Define Symbol File when invoked on client machines. Surprisingly enough, they work fine on server machine where the
Utility crash when application is installed and published from. GeoMedia 15.1 was published through XenApp 7.6. The last
invoked on a client time we tested GeoMedia on XenApp, the XenApp version was 6.5. This points to a possibility that the
machine - XenApp issue is specific to newer XenApp version. Crash information: Batch Plotting - Problem Event
1-DQ25R3 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
June 03, 2016 83

Issues Resolved
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
Length of linear User has noted that when any offset is used with a linear dynamic segmentation query, the resulting
dynamic dynamic segmentation geometry (dynseg geometry) is incorrect. The amount of error can vary from small
segmentation (few meters) to very large (Kilometers). The problem prevents users from obtaining any reliable results if
incorrect if use using offset for linear dynamic segmentation. The problem is a regression from version 2014. Example:
offset. User wants to map construction zone along a straight line that begins at 0.0 miles and ends at 8.0 miles.
1-DS10RR
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).
Intermittent legend Customer has noted and support has confirmed that legend entry tooltips do not reliably work and may
entry tooltip seem at best intermittent. After one legend entry tool tip is displayed, the user must navigate the on-
1-DS49Z8
displayed. 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.
Expected Fusion In certain data cases, the link creation process behaves as if it lacks the capability to create multiple
Links Not Created associations to the same link ID. Ultimately this leads to a link table that may have missing link
After Running relationships which are needed for processing in other applications such as GeoMedia Transportation
Create Links. 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).
1-E7FTI4
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.
Customize Ribbon To reproduce this problem:

dialog displays
wrong icons for 1) First, install the GM3D add-on product (may happen with other add-ons too).
commands in add-
on application tabs. 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.)
1-EDSINF 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.
June 03, 2016 84

Issues Resolved
Select Set The select set properties shows incorrect record and attributes for the selected geometry in the map view
Properties shows when a Unique Value Thematic is displayed. Problem is a regression from 2014. For example: User has
incorrect record unique value thematic map of US Counties by statename. The user might double-click geometry for
and attributes. Madison County Alabama in the map window but the attribute properties dialog might 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-EFJ4IH
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.
Connectivity GeoMedia 2015 fails to open a gws saved in a previous version, if the gws contains a query based on
1- Validation and gws Connectivity Validation and Union Pipe. More precisely, the gws can be opened, however the query
EGCQ8F incompatibility. 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.
CustomFieldsPipe The recordset based on a UnionPipe cannot be loaded when the UnionPipe is derived from
and UnionPipe CustomFieldsPipe and the CustomFieldsPipe has added geometry field without the CoordSystem
issues. 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

1-EGF10C
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).
Right click mouse Right click mouse menu on Map window is not working on GeoMedia with static labels. Steps to
menu on map reproduce:
window is not
working after 1. Launch GeoMedia.
selecting leader
1- line with static 2. Make an Access connection and generate static labels.
KMYUBT labels.
4. Select New geoworkspace from File menu.
Observations: Right click context menu is not working.
Grid F1 Help Grid F1 Help displays English help instead of German. German help was included on 2015 SP1. Only
1-KPS5IF display English Grid commands, F1 help display English Help instead of German help. Other commands on GeoMedia
help instead of Desktop display German Help.
June 03, 2016 85

Issues Resolved
German.
Schema Need correction to GeoMedia Help documentation for Schema Remodeler - Add the directories required
Remodeler - to be added to path for Schema Remodeler from the command line (GeoMedia v15.1): C:\Program Files
1- correction to (x86)\Hexagon\GeoMedia Fusion\Program C:\Program Files (x86)\Common
JNNOBD GeoMedia Files\Intergraph\GeoMedia\Program Found that C:\Program Files (x86)\Hexagon\GeoMedia
documentation. Professional\Program is not required for Schema Remodeler (but I believe is required for other utilities
such as batch plotting).
Error getting field Invoke GeoMedia and make connection to FGDB dataserver and select the feature
value is thrown Cherokee_CHEROKEE_PlatLines with coordinate system as 4326. Observation: A dialog with error
1-JQF18C when exporting message error getting filed value is thrown.
features to GML for
Cherokee data.
Explode of Customer reports a patch still has a problem with a tile rotating if the the .ini file contains the SERVE CELL
Microstation V8 GEOMETRY:EXPLODE setting. The data being referenced is not part of a Cell. If the .ini file contains
1-K8QP68 DGN elements SERVE CELL GEOMETRY:TRUE the tile data is not rotated. The data being referenced is not part of a
results in rotating a Cell.
section of map.
Select Set The Select Set Properties dialog does not display the attributes for features served from some WFS
Properties fails to connections. This is a regression from GeoMedia 2014 where the Select Set Properties dialog displays
display attributes the successfully displays the attributes from the same features. Additionally other commands in the
for features from product display the attributes successfully, so this appears as it could be a problem caused by the
WFS connection. 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.
1-KBNY4A
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.
Errors for existing If you turn off (disable/uncheck) caching option for a cache enabled connection, you then get errors for
legend entries after existing legend entries: This method/property not yet implemented. And following message as cursor
disabling caching. crosses map window: PClCmd1 --------------------------- Error from QueryInterface for
IID_IGMLocatedObjectsCollection
1-
KGM1RZ Workflow to see problem:
1. Clear (delete) caches in caches folder (C:\Warehouses\Caches).
2. Create new blank GeoWorkSpace.
June 03, 2016 86

Issues Resolved
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.
Caching not As a GeoWorkSpace is opened, GeoMedia has logic which reviews the display status (Display On,
performant when Display Off, Display by Scale status) of legend entries as a means to either load or not load a record set.
legend entries are Testing with exclusive caching of oracle data shows that caching seems to only improve performance for
not set to display legend entries that are set to Display On. The use of caching where the legend entries are not displayed
1- on status. can degrade performance. Especially if legend entries are set to Display by Scale and the current scale is
KGXSKV 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
Square Geometry The Square Geometry command fails to run if the select set contains one or more point geometries.
fails to run with “No However if the select set contains only area and/or line features the Square Geometry command runs
1- angles processed” successfully.
JUSBMW message if select
set contains point
feature.
Unable to delete 1. Invoke Schema Remodeler.

source connection
on Schema 2. Select Source tab and make an access connection.
Remodeler.
1-
3. Select the connection.
GO33OB
4. Click on Delete Button.
5. Observe nothing happens.
Out of memory Open the *.gws mentioned in datapath and verify whether the warehouse Data paths are correct. Invoke
error is thrown with Grid>Layer >Histogram command and select smooth result layer.
76847_GM histogram
command. Observe: After some time following error message is displayed --------------------------- Error ----------------------
----- Out of memory --------------------------- OK ---------------------------
Kriging suite Using the noted data and the following workflow, the Ordinary Kriging Suite command crashes GM2013 to
command crashes the desktop. - open new workspace, create new access warehouse - import .mfm layer - using layer-
GM2013 to the >Information, set the data units to svy_ft - run ordinary kriging suite - set distance units to svy_ft - set lag
1-7O62Y0 desktop. 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.
June 03, 2016 87

Issues Resolved
GeoMedia crashes GeoMedia crashes after exiting the application from the task bar with define new study area dialog in
exiting the invoked state. Steps to reproduce:
application from
the task bar with 1) Invoke GeoMedia.
define new study
area in invoked 2) Open a blank geoworkspace.
state.
3) Open a workspace from the file menu.
1-95KJGH
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.
After import of a Customer intends to calculate isolines with GeoMedia Grid. Sourcelayer is a DEM (*.dt1-file) attached.
DEM (*.dt1) into After import of the *.dt1 into GeoMedia Grid, it displays about 10 times too large. If the customer proceeds
GeoMedia Grid, to calculate the isolines from this layer, the isolines output seem to be calculated correctly. Inserting the
1-A27LBL
DTED1 file image using the Raster > Insert Georeferenced Images command "Insert Georeferenced Images"
appears about 10 command in GeoMedia, size and position are totally incorrect - they appear far outside the extents of the
times too big. geographic .gws.
Grid > Study Area In a blank .gws and .mdb, with no study areas defined, Select > Study Area > Import.
> Import of 32-bit
Float GeoTIFF 1. Browse to folder with attached 32-bit float GeoTIFF elevation file.
results in all zero
value black 2. Select file, GeoTIFF > Next. File is processed without error.
1- rectangle.
CQ6BVW 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.
Grid Triangulation Grid Triangulation command does not honor the language set on GeoMedia. If the language is English on
command does not Japanese OS, then Japanese dialog box is displayed. If there is no Japanese satellite assembly existed,
1-KJ45DZ
honor the language then English dialog is displayed. I have checked the recent build on Russian with the same situation,
set on GeoMedia English dialog is displayed.
Grid Triangulation Grid Triangulation command throws an exception error message when clicking the "Add" button. This
command displays command does not honor the language set on GeoMedia. On English version on Japanese OS, Japanese
an exception error dialog is displayed. In this situation, this command is working correctly (no exception error) with Japanese
1-KJ4CP4
message when satellite assembly. This error seems to be coming from .NET.
clicking ""Add"
button.
GeoMedia Grid’s The Elevation Workbench command dialog contains a menu. The dialog has been localized (strings for
Elevation labels and such), but the Menu on the dialog has not. We need to pull the strings from a localized
1-KJ4CV9
Workbench resource and update the Menu Text appropriately.
command contains
a menu which is
June 03, 2016 88

Issues Resolved
not localized.
Documentation The GM API Object Reference for the Layout Window automation needs to be updated/corrected. It
needs to be describes a FillStyle object that can have four different types of styles, but two of those are no longer
corrected/updated available -- the Symbol Fill Pattern and the Multiple Fill Pattern. The customer wanted to use the Symbol
1-994BCC and remove Fill Pattern but it only the simple fill and hatch pattern styles seem to be accessible. The product
Symbol and Documentation needs to be corrected.
Multiple Pattern Fill
doc.
Spatial Operator of The customer is using the Spatial Operator of

gmsqIsNearestTo Intergraph.GeoMedia.PPipe.SQConstants.gmsqIsNearestTo with SpatialSubsetPipe. This always gives
with the error: The input parameter to the method or property was set incorrectly. Code example :
SpatialSubsetPipe objSSP = New Intergraph.GeoMedia.PPipe.SpatialSubsetPipe objSSP.InputRecordset =
1-90DD0X always errors. 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
GeoMedia crashes LRS Precision Location Service is crashing GeoMedia Pro and GeoMedia Web Map Pro when KeyIn
when KeyIn function is used on an LRS record with no geometry. The problem was noticed with data where some
function is used on LRS records could have null geometries as the backend database process is updating the geometry
an LRS record with columns. The LRS Precision Location service should gracefully handle the null geometry condition by
no geometry. raising an error instead of crashing the host application which does not allow the user to save the
workspace. Steps to reproduce:
1-8Z1JCB
1. Open an existing LRS warehouse.
2. Select any LRS record and delete the geometry field value.
3. 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.
Custom linestyles Custom linestyles are wrong when importing G/Tech legend through G/Tech interoperability tool on
are wrong when machine with Danish regional setting. On a machine with Danish Regional setting and importing the
importing G/Tech G/Tech legend the custom lines styles are displayed in the Style Properties dialog as
1-8XLEQ1
legend through 1763888888888,89;3527777777777,78 which is incorrect. Correct display should be
G/Tech 0,176388888888889;0,352777777777778. It appears the decimal separator is not being interpreted
interoperability tool. correctly.
GeoMedia fails to When a WMS data server connection is made to a WMS that contains layer names with Cyrillic characters
display the original those layer names are not displayed with the original Cyrillic character in the Add Legend Entries
Cyrillic layer names command or in other commands that display the feature class names. Specifically instead of seeing the
from a WMS original Cyrillic characters in the name all of the Cyrillic characters are converted to underbars and the
connection. 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 ‘Add WMS Legend Entry’ command will
1-8DUMT0 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
June 03, 2016 89

Issues Resolved
prompted.
2. Open a blank GeoWorkspace.
3. Make a new WMS data server connection .
4. Select the ‘Add Legend Entries’ command and note that the features are all shown as
“F____________”.
Pressing F1 Pressing F1 doesn't display Help content for few commands/ This issue is observed with GeoMedia
doesn't display Professional tier. Commands which do not display help content: File tab > Customize > Customize Ribbon,
1-
Help content for Home tab > Select Set Properties, Home tab > Review Attributes, Vector tab > Insert Text, Vector tab >
8NRAHQ
few commands. 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.
Simplify Geometry A customer has a Shapefile that I have connected to in GeoMedia Professional 6.1. There are 6 polygons
Command. 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
1-5FVY8E
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.
GeoMedia Steps to reproduce:

Professional
crashes on running 1. Using Tools > Display CAD Files command, display AutoCAD 2008 files.
a simplify geometry
query on feature 2. Invoke Tools > Simplify Geometry... command.
class from
AutoCAD dataset. 3. Select ‘AllLayers’ as the features to simplify and check the checkboxes to display the results both in
map and data window.
1-54GPW9
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.
GeoMedia Steps to Reproduce:

Professional
crashed with BZ 1. Invoke GeoMedia Professional. Create a blank Geoworkspace. Make Access R/W connection to
query on union Alabama.mdb.
query of Large
dataset. 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.
1-54YK0O
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
June 03, 2016 90

Issues Resolved
click on Display button to get the display in both data and map windows. Focus on mapwindow. Observe
that GeoMedia Professional crashes.
Simplify and Issue using the using the Simplify command. Simplify does not correctly simplify the second vertex when
1-647T8D
Smooth commands the Z values are equal. The Simplify function is not working when there are Z values that change across
with equal Z value the line.
1-649EHZ
issue.
Place by Face is "Place by Face" is creating non-coincident edges where arcs are present in the source face (illustrated by
creating non- opening the Workspace of "Untitled.gws" and examining the location where the source feature of
coincident output "City_Limits_Bdy" is shown with the feature of " City_Whatever", which was placed with Place by Face).
where arcs are
present. The non-coincidence problem seems to be present just where arcs are present in the source data that was
80844_GM 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.
Within distance If spatial query command is run, features are defined, then if the option 'are within distance of' is selected
'distance' field and an invalid distance value is specified, and Ok is selected, normal GeoMedia warning/error messages
needs to provide are not displayed. Instead, the active is set to the distance keyin field. There is no indication to the user
82918_GM
text feedback. 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.
Connections The Connections command has to clean up the items within the Queues QueryFolder, similar to other
command needs to QueryFolders like Features.
83226_GM delete the items in
the Queues
QueryFolder
Wrong query is Wrong query is created if there is invalid distance and enter key is pressed. Steps to reproduce:
created if there is
invalid distance 1. Create read-write warehouse connection to USSampledata.mdb.
and enter key is
pressed. 2. Invoke Spatial Query command.
3. Select Cities feature class from the first input feature class combo box.
4. Select "are within distance of" spatial operator and check the box for Not checkbox.
51721_GM
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.
Default Style Default Style names displayed in Styles tree on Style Properties dialog box are not localizable (such as
84787_GM names in Style Area Style, Boundary Styles, Fill Styles and etc.). Those entries are displayed by using Registry entry key
Properties dialog 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
June 03, 2016 91

Issues Resolved
are not localizable 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
Duplicate Duplicate messages on message dialog popped when creating Attribute selection for invalid Query. Steps
messages on to reproduce:
message dialog.
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.
85504_GM
4. On Query Properties dialog, In Filter Edit box replace filter as 'ID > ' and click OK.
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 ---------------------------
'Object variable or Error pops up when Spatial Difference is created on Union Query. Steps to reproduce:
With block variable
not set' error pops 1. Create a blank excel sheet blank.xls on desktop.
up.
2. Open a blank Geoworkspace and create a New Warehouse 'GeoMedia.mdb'.
85788_GM
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.
June 03, 2016 92

Issues Resolved
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 ---------------------------
Unable to use Copy renamed GMSearch queue from library and try to use the same in queued edit throws error
Queued Edit on message. Steps to reproduce:
copying renamed
GMSearch queue 1. Invoke GeoMedia Professional blank GWS; Make an access r/w connection to USSampledata.mdb.
from library.
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.
86771_GM
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.
Observe: The following error message is displayed. --------------------------- Queued Edit Control ----------------
----------- The requested query is not in the queries collection. --------------------------- OK ------------------------
---
Spatial Filter is A customer SR was received stating that when they have queries from an Oracle connection on the
opening query legend with the display turned off the queries were still evaluated when a spatial filter was applied. This
recordset that has seems to be confirmed by the entries written to GOracle.log file which shows that when a Spatial Filter is
85423_GM never been on applied a spatially filtered query is created even though the legend entry for that query was not displayed.
legend. 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.)
Overwriting error I pulled that latest changes to SDP and SIP from GM to G/Tech. When comparing the changes in G/Tech
reporting in AtEOF, 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
62208_GM 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.
Apply Spatial Filter While researching Oracle performance issues, a user notes that the logic for Spatial Filter when opening a
1-4RHJ5M
Scans All Members GeoWorkspace vs. Apply Spatial in active GeoWorkspace is different. Based on results of GOracle.log
of Category If Only containing features unreferenced by the GeoWorkspace the user feels that there must be some problem
June 03, 2016 93

Issues Resolved
One Member on with Apply Spatial Filter command in GeoMedia. Workflow:

Map Legend.
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.
GeoMedia Error message is displayed when tried to create Simplify Geometry of 'Places' Feature class and also
Professional is GeoMedia Professional crashes when tried to load the 'Simplified PLACES' legend entry. Steps to
crashed when reproduce:
trying to Load
Simplified 1. Invoke GeoMediaPro and choose Blank GeoWorkspace.
Geometry of
‘Places’ Feature 2. Create Read-Write access connection to “Alabama.mdb”.
class.
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’.
1-4RLNQZ
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.
Incorrect character If the menu entry for either simplify or smooth commands is reviewed in the mapview of GeoMedia
replaces standard Professional, the '...' that follows each command name displays differently from other GeoMedia
1-4STQET ... in Mapview Professional commands. This is especially obvious if non-English operating systems are in use, such as
menu title. 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.
June 03, 2016 94

Issues Resolved
Select set to Query Performing Select Set to Query on any Outer Join queries crashes GM Pro. Steps To reproduce:
on an Outer Join
Query crashes GM 1. Invoke GeoMedia Professional (06.00.34.07 Setup) with blank GWS and make a R/W connection to
Pro. 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.
70779_GM
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.
Hooking Hooking AfterDocumentClose event during Initialize() call on a .NET command with custom enabling
AfterDocumentClos conditions prevents workspace from loading.
1-6FLIAV e event prevents
workspace from
loading.
Match I have found that the option 'Match GeoWorkspace and default Warehouse coordinate systems' when
Geoworkspace and 'making first connection' and 'creating a new warehouse' is not honored if the initial warehouse connection
default warehouse fails. Workflow to reproduce: With both the 'Match Geoworkspace and default Warehouse coordinate
coordinate systems' options active on the General tab complete the following workflow:
systems.
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.
1-7S03LC
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.
5. 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.
Application crash This issue is latent from GeoMedia Professional 2013 build 242. Perform buffer zone operation. Later
with Aggregation choose any feature from bufferzone query and select set query operation. Perform Aggregation operation
command by using with select set query and any point geometry. Observed that application crashes. Steps to Reproduce
1-7U2BYV Select set query.
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’.
June 03, 2016 95

Issues Resolved
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.
Using "Place by Steps to reproduce:

Circle" in "By
Diameter" mode, 1. Invoke the GeoMedia and create a new geoworkspace.
Circle is placing at
Zero height. 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.
1-80R7CH 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".
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.
Unique Thematic Dynamic Labeling adds extra values to legend. Workflow1: Invoke Add Thematic Legend Entry.
classification gives
improper results. 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.
1-B4U3N5 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.
SQL Server 2012 We created a handful of feature classes to capture castle and castle related complexes (e.g. CASTLE_P,
database picklists CASTLE_S, CASTLE_COMPLEX_P, CASTLE_COMPLEX_S) in our SQL Server Express 2012 database.
not working on These features had several attributes with picklists on them (storing an integer but displaying a textual
1-B3CUML
some features. 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
June 03, 2016 96

Issues Resolved
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.
The dropdown list The dropdown list in the select reference features dialog box does not list any features for selection.
in the select
reference features
1-AX4KAE
dialog box does not
list any features for
select.
GeoMedia Mobile When running GeoMedia Mobile on a machine where the Format is set to ‘German (Germany) on the
GPS positions are Region and Languages dialog the GPS tracking coordinates are incorrect. Specifically the GPS
incorrect with coordinate values are truncated, so that the complete precision of the points are lost. For instance you
German regional may only see Degrees and Minutes, with the Seconds ignored or the Seconds will be shown without any
settings. 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.
1-9YPR5I 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.
Some geometries Customer reports when the Map Window display scale is changed some objects lose their fill color.
have their
representation 1. Open provided .gws, connect to provided .mdb file if necessary.
1- altered (fill
A3Y3UW disappears) based 2. Zoom in on displayed features
on the zoom scale.
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.
Define Symbol file 1) Invoke Define Symbol File utility.

utility crashes
when a saved .fsm 2) Invoke Add button and in Add From file dialog select the Files of Type as Microstation V8 Cell file
is used to add (*.cel/*.dgn).
symbols.
3) Input the file name as \\GeoMedia\Datasets\Symbols\DefSymFile\V8\Line.dgn.
1-A24FS7
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.
Text rendered on We have problem with generating png32 using IID_IGROMemoryCanvas. Color for legend text generated
specific canvas in WebMap is completely different than in GeoMedia Desktop. Example code to generate
1-AC5BI3
displays artifacts. 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-
June 03, 2016 97

Issues Resolved
>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.
GMLStorageServic In WCTS implementation it is possible to read correct coordinates order from CSF file, but there is no way
e produces GML to pass that info to GMLStorageService. To allow that, GMLStorageService API needs to be extended -
1-9Y2UCN
with incorrect e.g. additional parameter should be added to TransformGML method that will specify the required
coordinates order. coordinates order for output GML.
GeoMedia throws a GeoMedia throws a C++ runtime error while attempting to load the query command from the ribbon
runtime error while toolbar. The circumstances when this occurs is probably not typical but it is probable. I have a
attempting to load GeoWorkspace which contains a few hundred queries. For the client I’m working with, it’s required that
the query dialog. 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
1-956C1D
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. ---------------------------
Unable to The customer was trying to create the GeoMedia.Application object (in a Driving GM application) in a C#
instantiate program, but it always fails: The errors occurs in code line app =
GeoMedia.Applicati Activator.CreateInstance(Type.GetTypeFromProgID("GeoMedia.Application")) as Application; The error
on in Desktop 2015 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
1-JMFL7G
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 /.
Cannot enter The project has a custom dockable control command running in GeoMedia. The command was developed
Arabic characters using VB.NET 2010 and is running on Windows 7. When attempting to key-in Arabic characters into a
1-IYSZLU on custom textbox on the dockable control, other non-Arabic characters appear. The dockable control also displays
dockable control modal forms based on user actions. On the modal forms, Arabic characters can be entered and appear as
text field. expected.
"Object is invalid Below are the steps to reproduce the issue.

for operation" error
when Coordinate 1. Please register GeoMedia custom command attached to the CR and run GeoMedia with blank
system is changed workspace.
- Modeless
1-JELCBZ command. 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.
June 03, 2016 98

Issues Resolved
4. Again click on MoveNext or MovePrevious buttons to observe the error "Object is invalid for operation".
canEnable method We observed that canEnable method is calling with same construction aid multiple times when we doing
is calling with same map operations, and also incrementing 1 for each operation. Please see below workflow for your
construction aide understanding.
multiple times.
1) Add a legend entry on map.
1-FX8CU0
2) Go to Vector tab and select Move command, observer that CanEnable method is called for each
available construction aide.
3).Now discard command and reselect Move command, observer that CanEnable method is called two
times for each construction aide.
GM crashes on Customer has created a test command that is registered in a directory such that the path to the DLL and
German OS when the XML of the custom command are very long file paths. Using these long file paths on a German OS,
the length of the Windows 7, Desktop 2015 RTD, the custom command is installed. But when the GM GUI is invoked to be
1-DC5PKU
path of the GM opened, it never opens, and there are a couple of errors in the Event Viewer. If the directory name/file
custom commands path is shortened, no error occurs.
.dll is too long.
Failure to Description from customer: I understand that in 2013 and forward, an application that internally launches
instantiate an an instance of GeoMedia as a background COM server needs to add an App Paths registry entry for itself
1- instance of and include in the Path value the same data found in the Path value for GeoMedia's App Paths key. This
DC6POO GeoMedia as a has always worked except now for one machine in our office that previously had GeoMedia 6.1 which was
background COM uninstalled and replaced with GeoMedia 2015 SP1. This machine has Windows 7 on it. On this machine,
server. GeoMedia refuses to launch successfully as a COM server.
Windows logging Have new Win7 VM (Clean build). I installed GeoMedia Desktop SP1 2015 using Setup.exe and ran as
1- event warning Administrator (but same problem occurs if running Setup.vbs). Support believes this problem is why the
D3G4MW while installing Setup often instructs users that a reboot is required. Looking in Event Viewer we see some 200+
GeoMedia 2015. Warnings concerning registry keys.
G/Technology G/Technology Synchronize Edits fail to appear in G/Tech 10.2 After getting into a new G/Tech workspace
Synchronize Edits and connecting to the database using gmsprod/gmsprod@empire I replaced the legend with the Electric
1-CJSJ0G
fail to appear in Design (default) and then ran the Refresh> Database Changes command. Unfortunately, nothing was
G/Tech 10.2 updated.
Patch fails to The 15.00.0000.10126 patch fails to remove cleanly. Files and folders are left in C:\Program Files
1-BUANP3 remove cleanly. (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.
Some text from Some text is not being displayed in the correct location. This can be solved by reassigning the font
DGN is displaying number to the text inside of MicroStation, then it will display correctly in GeoMedia. What is causing this
1-BY9RF2 in the incorrect shift in the first place? What is being incorrectly read that reassigning the font number fixes? We need this
location. 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.
Connection The OOM data server is getting increasingly slower on initial connections to Oracle. This is caused by the
performance very use of 4 queries on the initial connection that utilize ALL_OBJECTS. These queries need to be changed
1-C9J8OT
poor on Oracle (12c only) to return to a normal connection speed.
12C.
June 03, 2016 99

Issues Resolved
Need full step-by- Customer needs a document describing in detail the full process to add a new add-on in GM 2015. The
step workflow customer/Intergraph AE made tests with a partner, and the behavior was often really surprising. The new
1- describing the add- tab correctly appears in the interface, but when invoking a command, it was generic GM commands which
CAEBQA on development were run, (for example, 'New Data Window'). Our need is a step-by-step workflow to create a full add-on
from scratch of from scratch in GM 2015. The current Ribbon Bar Customization for Developers is missing necessary
Ribbon Bar. information.
Using GeoMedia WebMap is using ExportToGMLService extensively and in one case passes to it recordsets
ExportToGMLServi which are the output of a UnionPipe. This seems to be causing memory leaks. Using umdh.exe from the
ce with a recordset Windows Debugging Toolkit shows that the memory allocated is being held by references created in
1-C733QP
based off PDBPipe1.GMUnionPipeGRecordset:get_GFields. This does not happen when manually enumerating
UnionPipe causes GFields in code without having a usage of ExportToGMLPresent.
memory leaks.
Arabic font not Arabic font is not displayed properly in Layout window when copied from Data window or Feature
displayed properly Properties. The issue was solved in GM2014 patches but appear again in GM2015. I install the latest
in Layout Window patch of GM2015” A screenshot was provided of an Arabic text value displayed in the Select Set
1-C75HZC
when copied from Properties and the same text string after it was copied into a text box in the Layout Window. The text that
Data Window / is pasted into the Layout Window ‘Text Box’ does not match that from the Select Set Properties dialog.
Properties dialog.
GeoMedia 6.1.2.4 With a clean machine having GeoMedia 6.1.2.4 installed, I am unable to uninstall the product. It fails after
1-C75P6P and 6.1.11.13 - 75% processing. No workaround exists except to clean your machine.
Uninstall fails.
Geometry Workflow to reproduce:

Information
displays incorrectly 1. Invoke GeoMedia Make connection to USSampleData.mdb
filename for the
raster geometry. 2. Add to the legend USSampleImage.
1-
BMNTDX 3. Select the image.
4. Invoke Geometry Information command.
5. Resize the dialog to see entire filename. Observe: Now you can see the added characters at the
end of the file name.
GMOUTPUTTOTA The GMOUTPUTTOTABLESERVICE execute method fails with System.AccessViolationException.

BLESERVICE fails Additional information: Attempted to read or write protected memory. This is often an indication that other
1-
with memory is corrupt. This service fails if a recordset obtained from the GeoMedia.Application is passed in
BK4ODW
System.AccessViol and try to output the recordset to a new database.
ationException.
Performance Thematic legend entries on the map legend load much slower if loaded when performing a File > Open
problem loading GeoWorkSpace. If instead the features are loaded by right-click Load or Display, the features load much
large thematically faster. For example: Have GeoWorkspace with two unique value thematics entries which constitute some
classified record 300+ legend entries via Oracle connection. If the thematics are in a “display off” state on the map legend,
sets (Open GWS the GeoWorkSpace file may open in 9 seconds. If we then right-click to set to “Display On” for the 2
1-JTPHVO
vs. Display On). 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.
June 03, 2016 100

Issues Resolved
GM15.01 HBA Execute PVT till step 13. Step14 says that the default style that appears is compound style, but,the default
Step 14 of PVT style that appears on the style button is Area style.
SpatialDiff1AccRW
1-BC15RF
is generating Area
style instead of
Compound style
Setting GeoMedia A standalone custom application’s main Form (.NET) behaves oddly when GeoMedia AppMainhWnd is set
application as a parent. The form (and also GeoMedia) flickers, cannot be resized, minimized, maximized, closed, and
1-DA10DI
MainWnd as a also GM Map Window consumes most of the mouse input. This worked fine on Windows XP and
parent window. GeoMedia 6.1.
CONFLATION: If you reverse the sources for connection 1 and connection 2 when conflating you will get different results,
Reversing the especially in regards to a long to short segment comparison.
1-BMJ6JO connections for
conflation yields
different results.
Custom Cmd crash My two custom commands of Leader Line and Reposition in Labeling are failing due to a new code
caused by new statement in the Initialize routine of the .vb template and code creation file of the command wizard when
1-K9XEUP code statement in creating a View Listener command with Mask of 18 or 24 and possibly other Mask values.
GM 2015 Cmd
Wizard template.
Development Customer is migrating component Intergraph.GeoMedia.PAFM.GEventHandler from AFM 6.1 to

1- Migration from Geomedia Professional 2015 and cannot add new command with "create event handle".
KNHOUH AFM 6.1 to 2015
fails.
Duplicate Label This problem does not occur when IFC is turned OFF. When the Duplicate Label command is invoked, the
command fails to following error appears: -------------------------------------- Failed to finish execution of this tool because of an
copy a label with unexpected error. Object is invalid for operation. --------------------------------------
1-7173SP
IFC turned on.
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.
Layout Window / By using the projected Coordinate System 'Switzerland LV95' the geographic extent's properties aren't
Insert Cartographic complete shown in the 'Insert Cartographic Grid' control (Layout Window) if the method 'projected frame'
Grid: Default was used by inserting the related map. The proper coordinates appear in Map Graphic Properties.
1-7HLZR8
Geographic extent Changing .gws CS to LV03 shows the same behavior. Seems to only relate to using 'Projected Frame'
values are not method for defining the map graphic.
complete.
Ctrl-Enter for new- When using the ‘Select Set Properties’ dialog invoked by double-clicking an existing feature class or
line does not work selecting a feature and right-clicking to choose ‘Select Set Properties’ does not accept the Ctrl+Enter key
in ‘Select Set combination to add a new line. This is a regression from previous versions of GeoMedia (including 2014).
Properties’ To reproduce the problem, use the following workflow.
command dialog.
1-KYR0DT
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’.
June 03, 2016 101

Issues Resolved
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 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.
Help Example For User has noted that the example for the FORMATATTRIBUTE function incorrectly links to help for the
FORMAT
Replace Function. The customer writes: "The Help Link for examples is wrong for the functional attribute
ATTRIBUTE
Function Results In FORMATATTRIBUTE. The example for functional attribute REPLACE is coming up." Workflow:
Help For Replace
1. Analysis Tab, Functional Attributes.
Function.
2. Select some feature class and select New button.
1-
AQDRB0 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.
6. Select the FORMATATTRIBUTE Example link. Observation: The example displayed is for
"REPLACE"; expected example for FORMATATTRIBUTE.
Installation Guide Installation Guide Incorrect Information Concerning Language Options for Silent Installation. The
Incorrect Installation guide leads users to believe they can set a RuntimeLCID for configuration of the language. If
Information the language can be configured in silent installation, it’s important to provide an example configuration file
Concerning (Intergraph.GeoMedia.ConfigurationWizard.exe.config) that demonstrates how the language is defined.
Language Options
for Silent
Installation.
SmartStore SmartStore (.ddc) feature classes consisting of a single point feature do not display when spatially filtered.
features containing Problem is considered serious as it represents missing data that may not be noticed by the user. The
a single point do same issue can also be observed when the .ddc single point feature is published in routines that use
1-JY358F
not display when spatial filtering. For example, Publishing the .ddc single point feature to WMS fails to publish the point.
spatially filtered Workflow: Display smartstore data in GeoWorkSpace map window. Apply spatial filter. Notice how any
.ddc layer containing a single point is no-longer displayed.
Time to load record After rebooting, the time required to load a record set from a connection where caching is slower and in
sets 5x slower after most cases observed to be more than 5x slower than subsequent loads (even in different GeoWorkSpace
reboot when using sessions). See also attachments for example times observed. Example: User has Oracle connection with
caching. 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.
1-K5VIC2
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.
When editing a geometry with a vertex selected, entering the coordinates of another point and holding ctrl
Edit when pressing enter should select the vertex at the specified coordinate. Instead the selected vertex is
Geometry/Precisio being moved to the new coordinate. I believe this is a problem with the coordinate control. I think it is
n Coordinate missing logic to handle ctrl + enter. This happens on 15.1 as well but not on 14 SP2. GM 15 introduced the
Control - missing new WPF precision coordinate control.
1-KZBAUZ
ctrl functionality.
1. Digitize a line with several points
2. Select a point and record the coordinates of the point.
June 03, 2016 102

Issues Resolved
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.
Originating pipe & The customer has an EGIS custom Insert Feature workflow implementation. They need to cancel insert
Spatial filter pipes feature operation if the newly inserted feature is outside of Geoworkspace spatial filter (Inside operator -
are giving different 6). To implement above behaviour, the customer tried by using OriginatingPipe and SpatialFilterPipe, but
1-KPA1UX results for the both pipes are giving different results for point features which are on border of spatial filter geometry (This
points on border of problem is reproducible only for Oracle). OriginatingPipe: Resulting point features which are on boarder of
polygon. spatial filter geometry as outside of filter. SpatialFilterPipe: Resulting point features which are on boarder
of spatial filter geometry as inside of filter.
After upgrade to After upgrade to WebMapEP05 &GM Desktop .10203, text layers no longer display properly in GM GUI on
1-L3S0TK WebMapEP05 a VM machine. The problem does not occur on a physical machine with a higher-end graphics card.
&GM Desktop These text layers are labels created with the "old" GM label creation. If the new Registry Key of
.10203, text layers Direct2DMode is modified from a value of 1 to a value of zero, it resolves the problem. Dataset and
no longer display Geoworkspace attached as well as email with screen prints showing the difference in text display with and
properly in GUI on without the Direct2DMode set to 1 on a VM machine.
VM.
Load dgn layout Customer provides MicroStation V7 .dgn that they have previously loaded as a layout template (in version
template displays 2014 Desktop). When loading this dgn file the whole screen becomes dark. This is not the case in the
black. Version 14. Tested on 15.00.0000.10203 and 14.00.0002.00143. Steps to reproduce:
1-KDRU4S 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?
FGDB read FGDB read connection errors with "Coordinate System Translation Failure" using EPSG5514.csf file.
connection errors Unable to connect to File Geodatabase(FGDB Read only) in GM 2015 and GM 2014. Connection error
1- with "Coordinate states "Coordinate System Translation Failure".
BQKXVR System Translation
Failure" using 1. Open blank .gws.
EPSG5514.csf file.
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.

GM2016 HBC Steps to Reproduce:(GM2016 HBC ) 1.Install GM 2016 668 build 2.Make a connection to "Access"
:"Object variable or Database 3.Add "SampleImages" legend entry 4.Insert a State feature using "Insert Feature" command
with block variable 5.Now select the inserted feature and select the "Continue Geomentry" 6.Now try to click on the Image
1-F29OC9 not set0" error edges Actual Result: throwing "Object varibale or block varibale not set0" error.
while using
"Continue
Geomentry"
Setup - Desktop Starting with version 14.00.0002.143, GeoMedia Desktop is installing files required by GeoSpatial
1- installs wrong Datapipe to C:\Program Files (x86)\Common Files\Intergraph\GeoMedia\Program\QD. The files delivered
ANFOZW version of .dlls 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
June 03, 2016 103

Issues Resolved
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.
ProgID for MapInfo GM2015 HS BC Observed this while running Exploratory tests. This is not a regression. Observed the
data server in the same on GMPro 14.00.0002.00088 Open a blank GWS and make a MapInfo data server connection with
help and the IFC on and add some feature classes to the legend. Open the generated cache.manifest file created in the
1-9D66LF generated are given caches folder and observe that the ProgID is written as MI.GDatabase. But in the GeoMedia Object
different. 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
Incorrect ProgID There is an incorrect ProgID for ArcView (ShapeFile) connections in the object reference. Documented:
documented for "ArcView.GDatabase" Should be: "AV.GDatabase"
1-ILEZEJ
ArcView
connections
1- Quick object System continue shown as In the section Quick Reference Object that is in the developer help of
AUYMC3 reference, GeoMedia 2015 for the CoordinateSystem components continue saying Typelib: PCSS. This is incorrect.
CoordSystem and
GeoMedia 2015.
Focus shifts to last Steps To Reproduce:

attribute on clicking
'Select All'
1. Invoke GMPRo and connect to USSampleData.mdb.
2. Invoke Analysis > Attribute Selection command.
83024_GM
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.
June 03, 2016 104

About Us
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.
June 03, 2016 105

About Us
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.
June 03, 2016 106

About Us
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.
June 03, 2016 107

About Us
June 03, 2016 108

Geomedia Release Guide PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Geomedia Release Guide PDF

Încărcat de

Drepturi de autor:

Formate disponibile

RELEASE GUIDE

June 03, 2016

About This Release ........................................................................................................................ 5

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

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

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

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

Data Access ........................................................................................................................ 11

June 03, 2016 2

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

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

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

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

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

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

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

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

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

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

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

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

Auto Adjust Features command ........................................................................ 24

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

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

June 03, 2016 3

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

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

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

Feature Caching ................................................................................................................. 28

Define Symbol File ............................................................................................ 29

Schema Remodeler ........................................................................................... 29

Spatial Model Editor .......................................................................................... 30

System Requirements ................................................................................................................. 31

June 03, 2016 4

ABOUT THIS RELEASE

GEOMEDIA PRODUCT TIERS

June 03, 2016 5

GeoMedia 2016 supports SQL Azure v12.

MGE DATA SERVER

FRAMME DATA SERVER

ARCINFO DATA SERVER

GEOGRAPHICS DATA SERVER

June 03, 2016 6

June 03, 2016 7

• Insert Area by Face

This change was introduced with GeoMedia 15.1.

June 03, 2016 8

GEOMEDIA CONFIGURATION WIZARD

.NET commands/components no longer need to use Marshal.FinalReleaseComObject or

Learn more about event processing with GeoMedia objects

June 03, 2016 9

June 03, 2016 10

This change was introduced with GeoMedia 15.1.

June 03, 2016 11

Take advantage of more Oracle data types

Now supports NVARCHAR2, NCHAR, and NCLOB data types.

POSTGIS DATA SERVER

June 03, 2016 12

June 03, 2016 13

Use SQL Azure throughout GeoMedia

Use SQL Server Spatial throughout GeoMedia

WMTS DATA SERVER

June 03, 2016 14