RELEASE GUIDE GEOMEDIA DESKTOP

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 As previously announced with the release of GeoMedia 2015, this data server is no longer supported with GeoMedia 2016. ARCINFO DATA SERVER As previously announced with the release of GeoMedia 2015, this data server is no longer supported with GeoMedia 2016. GEOGRAPHICS DATA SERVER As previously announced with the release of GeoMedia 2015, this data server is no longer supported with GeoMedia 2016. 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. This change was introduced with GeoMedia 15.1. 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 prerendered 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. This change was introduced with GeoMedia 15.1. 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. This change was introduced with GeoMedia 15.1. 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. This change was introduced with GeoMedia 15.1. 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. This change was introduced with GeoMedia 15.1. 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 Use SQL Server Spatial throughout GeoMedia All cadastral commands are enhanced to work with SQL Server Spatial data server. LIBRARIES SUPPORT FOR SQL SERVER SPATIAL READ-WRITE DATA SERVER Use SQL Server Spatial throughout GeoMedia The Library Connection dialog and Library Organizer command are enhanced to support SQL Server Spatial Read-Write data server. It is now possible to use a SQL Server Spatial database as a library. June 03, 2016 27

New Technology SUPPORT FOR POSTGIS READ-WRITE DATA SERVER Use PostgreSQL / PostGIS throughout GeoMedia The Library Connection dialog and Library Organizer command are enhanced to support PostGIS Read-Write data server. It is now possible to use a PostGIS database as a library. FEATURE CACHING INDEXED FEATURE CACHE (IFC) FILES Expanded capability for IFC files The format of indexed feature cache (IFC) files has been improved to include support for indexes on memo field types. Lack of support for indexing of memo fields manifested itself in the context of attribute queries and thematic legend entries built on memo fields. This change was introduced with GeoMedia 15.1. 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. Use PostgreSQL / PostGIS throughout GeoMedia 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 Computer/ Processor 32-bit: 2GHz microprocessor, Intel Pentium 4 HT, Core Duo, Xeon 64-bit: Intel 64 (EM64T), AMD 64, or equivalent (recommended) Memory (RAM) 4 GB minimum, 8 GB recommended Disk Space 10 GB for software Data storage requirements vary by mapping project 1 Peripherals Software security (Intergraph Licensing 11.11.1) requires the following: 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 Operating Systems 2 Windows 8.1 (Standard), Professional and Enterprise (32-bit and 64-bit) 2 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 Virtual Server and Virtual App Technology Oracle VM Virtual Box 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 Database Server Engines SQL Server 2012, 64-bit SQL Server Express 2012 SQL Server 2014, 64-bit SQL Server 2014 Express PostgreSQL 9.3 with PostGIS 2.1 June 03, 2016 31

PostgreSQL 9.4 with PostGIS 2.2 Database Client Engines Oracle Client 11g, 32-bit Oracle Client 12.1, 32-bit SYSTEM REQUIREMENTS NOTES 1 Disk I/O is usually the slowest task in geospatial data processing. Faster hard disks improve productivity. Reading data from one disk, writing temporary data to a second disk, and writing data to a third disk improves performance. Disk arrays improve productivity but some RAID options slow performance. Network disk drives are subject to network limitations. 2 Windows 7 32-bit, Windows 8 32-bit, Windows 8.1 32-bit and Windows 10 32-bit are 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 closing geoworkspace after closing overview window. Steps to Reproduce: 1. Invoke GeoMedia Professional. Create a blank Geoworkspace. 2. Make Access R/W connection to USSampleData. 3. Add Cities LE to map window. 4. Name the legend as legend1. 9AF33V 5. Invoke Overview window and add legend1 to it. 6. Now on overview window using legend add cities. 7. Save the workspace as TEST1. 8. Now close geoworkspace using File>Close. (In the same instance of GeoMedia) 9. Open workspace from recent documents. 10. Observe that workspace opens and overview window is blank. 11. Now delete this overview window using cross mark. 12. Click on File>Close geoworkspace. Click on No button on message dialog. Observe that June 03, 2016 32

application crashes. Error followed by crash on performing Insert Traverse command with category features on German OS. Steps to Reproduce: 1. Invoke GeoMedia Professional. 2. Create a blank Geoworkspace. 3. Make Access R/W connection to USSampleData.mdb delivered with product.(ifc ON) 9B14LP 4. Add all the features to categories. 5. Add all the features from categories to map window. 6. Invoke Insert Traverse command. Select States (Categories) as Primary feature and Rivers (Categories) as component feature. Using Use Map and Add to Grid options place a point followed by two lines. Click on Apply button. Message displays that feature has to be closed. Click on Ok button. Click on Ok button on Properties dialog. 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. 9BHFUB FGDB Read Only shows English strings on New connection dialog in Japanese version. Steps to reproduce: 1. Invoke Japanese version of GeoMedia Professional. 2. Invoke New connection dialog. 3. Observation: FGDB Read Write is displayed in Japanese language; however, Read Only is still shown in English. 9BHG48 Export to GML the dialog size is fixed on size 8 dialog. Truncated the dialog items at right side Export to GML The dialog size is fixed on size 8 dialog. On size 9 dialogs, the right side of the dialog is truncated. Resizing subroutine is using the numerical value to adjust the position of items. Therefore the items on Size 9 dialog (Japanese and Chinese) are not correctly positioned and truncated at right side and bottom. 9BOVUL GeoMedia crashes exiting the application from the task bar with options dialog in invoked state. GeoMedia crashes while exiting the application from the task bar with options dialog in invoked state. Steps to reproduce: Invoke GeoMedia. Select Blank Geoworkspace radio button. Open a Geoworkspace. Select the Insert feature. Select options dialog from the vector control. Exit the Application from the Task bar. Observations: --------------------------- PMiscCmd --------------------------- Error exiting application.source:gmcmdsuptdescription:method '~' of object '~' failed --------------------------- OK -------- ------------------- --------------------------- PProCtrl --------------------------- Run-time error '0' --------------------------- OK --------------------------- Click Ok on the dialog GeoMedia Crashes. 9BOVZX GeoMedia crashes exiting the application with Coordinate System dialog in invoked state. GeoMedia crashes exiting the application with Coordinate System dialog in invoked state. Steps to reproduce: 1. Invoke GeoMedia. 2. Select Blank Geoworkspace radio button. 3. Open a Geoworkspace. June 03, 2016 33

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 runs after exiting the application with options dialog in invoked state. GeoMedia.exe still runs exiting the application with the options dialog in invoked state from Queued Edit control dialog. Steps to reproduce: 1. Invoke GeoMedia. 2. Select Blank Geoworkspace radio button. 9BOW1Y 3. Open a Geoworkspace. 4. Select the features check box. 5. Click ok button. 6. Select options dialog from the Queued Edit control. 7. Exit the application from the task bar. 8. Observations: GeoMedia.exe is still running in the task manager after exiting the application. ShapeFile Data Server: Attributes of Type Double Rounded or Truncated As If Integer. User exports GeoMedia GeoWorkSpace query containing double values then serves the data back into GeoMedia using Shape File data server. The field is correctly served back as double, but the values are all truncated to 0 digits of precision (value 77.1234 becomes 77); the values are rounded to zero decimal places. Scope: Problem is known to occur when the GeoMedia user exports a merge query that contains a period <"."> Queries containing dot (".") as part of the query name is very common for Oracle users where the connection name and thus query names are prefixed by the schema owner. Example query name: Merge of OM_ALABAMA.ANTENNAS If the user selects the query name "Merge of OM_ALABAMA.ANTENNAS", the Export dialog automatically renames (possibly by design) the output shapefile to: "ANTENNAS. Such renamed merge queries will have truncated values for fields of type Double. 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. 961T3I GeoMedia.exe is still running exiting the application from task bar with Save As dialog in GeoMedia.exe is still running after exiting the application from the task bar with Save As Dialog in invoked state of Edge Match rules dialog. Steps to reproduce: Pin GeoMedia to task bar. 1. Invoke GeoMedia June 03, 2016 34

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. 9625CJ GeoMedia.exe is still running while inserting the feature with properties dialog in invoked state. GeoMedia.exe is still running while inserting the feature with properties dialog in invoked state while exiting the application from the task bar. 1. Invoke GeoMedia 2. Select Blank Geoworkspace. 3. open a workspace 4. Select Insert feature from the Vector Tab. 5. End the feature. 6. Exit GeoMedia from the task bar. 968SJL Connection properties dialog - enable feature caching checkbox state not persisted. 1. Open GeoMedia. 2. Connect to USSampleData with caching off and add counties feature class to map window. 3. Verify cache is not created. 4. Open Warehouse Connections command. 5. Click properties button. 6. Check the enable feature caching checkbox. 7. A dialog appears asking if you want to create the cache. Press create/refresh cache (see cache is created). 8. Press Cancel. 9. Open Properties dialog to see that enable feature caching checkbox is checked. This should not happen. 96FA9R Layout > Print > Plot of WMS fails. 1. Steps to reproduce: 2. Open provided GeoWorkspace and zoom in to scale 1:50000. 3. Set nominal map scale to 1:50,000. 4. Open layout window. June 03, 2016 35

5. Print to printer. 6. Result: Blank paper. No error message. Aggregation Crash Using Within Distance Spatial Operator - Data Specific. Customer supplied data demonstrates a crash of GeoMedia application without chance to save when using Aggregation within distance operator. The problem appears to be data specific. Workflow: 1. Save.zip to C:\Warehouses and extract to here which should create folder 96ZL03. 2. Open Testing1.gws 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. 97CCGB Geometry validation gives inappropriate validation errors which was not seen in 6.1.11.13 version. I wanted to use this command to see if the data referenced in a particular CR is clean and found some errors. Steps to reproduce: 1) Invoke GeoMedia and connect to attached test data (WFS_Test.mdb) 2) Select Toolbox>Validate Geometry and select feature class GRUNDNUTZUNG_WALD and click [OK] on the Validate Geometry dialog. 3) Check that 3973 validation failures are listed in the Queue of Anomalies window out of which there are 3871 anomalies with Description "Invalid Geometry Component". 4) Observe each of these validation anomalies to understand that these validation failures are inappropriate. Repeat the above workflow with 6.1.11.13 and check that none of these geometries are mentioned as anomalies. This seems to be regression after 6.1.11.13 97DBUN Spatial intersection throws a Method of object failed error with invalid query. Spatial intersection throws a Method of object failed error and does not show an error message with invalid query to oracle connection. Steps to reproduce: 1. Invoke GeoMedia 2. Make an oracle connection from Ware house from Manage Tab. 3. Add the legend entries and click OK. 4. Select Spatial intersection from Analysis Tab. 5. Select a feature From the Features in combo box and select filter button and select > symbol and click ok button. (Note: an error message is not popped up even though it is an invalid query). 6. Select a feature from the other Features in combo box. 7. Select filter button, select > symbol and click ok button.(an error message is not popped up even though it is an invalid query). 8. Click ok button. June 03, 2016 36

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. 9910J8 Problems with Shapefile export from PostGIS database displaying in GWS. After exporting to shape files from a PostGIS database connection and then making an ArcView connection to the exported files, the user is unable to display the ArcView features in the Map window. Workflow: 1. Open a blank.gws and make an ArcView connection to the exported files. 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. 8OH60M Recordset access is causing data server to issue selects to database that is causing a performance hit. This was filed against the Oracle R/W data server when observing the behaviour of the Toggle Dynamic Label command. The recordset access pattern in the Toggle Dynamic workflow is causing the data server to issue selects to the database for each geometry row resulting in a performance hit. 8P174L Invalid geometry types enabled in Continue Geometry dockable control. Invalid geometry types enabled in Continue Geometry dockable control while trying to do Continue Geometry on a Spatial Query. Steps to reproduce: 1.Invoke GeoMedia Essentials and make an Access Connection to USSampleData.mdb available with the product 2.Invoke Analysis > Spatial Query 3.In the Select features in combo-box, select Rivers FC 4.Select are entirely contained by operator 5.Select States from the Features in combo-box 6. Dismiss the Spatial Query dialog by clicking on OK. 7. Select a River from the Map Window that is returned from the Query. 8. Now click on Vector > Continue Geometry Observe that in the Continue Geometry dockable control all geometry types are enabled (Point, Area & Line instead of just Line). However, on clicking on the invalid geometry (Point and Area), and trying to continue geometry, an error dialog with caption GeoMedia appears, with the following content: GeoMedia Invalid geometry detected. Operation aborted. -2147219944 GField::Value 8SSXEF GeoMedia Professional crashes for Validate Geometry on Searched item in select set. GeoMedia Professional crashes for Validate Geometry on Searched item in select set. Invoke GeoMedia Professional and create an access warehouse connection to USSampledata.mdb. Select Search command and select States feature class. Type 1 and click Search. Invoke Validate Geometry command. ON input tab, Select "GMSearchQueue" under SelectSet and Anomalies tab, select all check-boxes. Click OK. June 03, 2016 37

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 caching location not validated by GeoMedia during clear/refresh/enabl e stages. Steps to Reproduce: 1. Create a folder (in say C:\Temp) for the purpose of holding warehouse cache files 2. Invoke GeoMedia with a blank new geoworkspace and using 'Options' change the Warehouse Cache Files location to the folder created above 3. Close GeoMedia without saving GWS 8U3XM5 4. Delete the folder manually 5. Reopen GeoMedia and try clearing/refreshing/enabling cache. No errors pop up stating non-existing folder 6. However if you connect to a warehouse and add legend entries, the folder and relevant.ifc files get created. 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 Generate Connectivity Queries in GeoMedia 2014 and GM 2015. Validate Connectivity in GeoMedia Pro no longer supports output to query. a) Queries can be output and/or exported to other required formats b) Queries are built once and preserved as part of the GeoWorkSpace: 1. Automatically updating when underlying data changes. 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. 8DRJWH 'Method '~' of object '~' failed' error message pops up on giving invalid filter in Spatial Query. 'Method '~' of object '~' failed' error message pops up on giving invalid filter in Spatial Query Workflow to reproduce. 1. Invoke GM Pro and open a new geoworkspace. 2. Make an Access connection to USSampleData.mdb. 3. Invoke Spatial Query dialog and select Rivers feature in 'Select features in:' 4. Click on Filter button to display filter dialog. 5. In Filter Dialog, give an invalid expression 'ID >=' and click Ok. June 03, 2016 38

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 Entry calculates minimal bounding box of layer intersection, not union. The "Add WMS Legend Entry" command calculates intersection from all bounding boxes selected to display. As a result, if there are two layers with disjunct (non-intersecting) bounding boxes, nothing is displayed and the request is not sent to the server. The command must calculate minimal rectangle covering all bounding boxes, and request this coverage. The side effects of the current implementation are that if one of the bounding boxes is out of the map extent, no request is sent to the server although other layers might be visible. To reproduce the issue: 1 - Clear or create GDOWMS.log file in your personal Temp folder (..\AppData\Local\Temp). 2 - Connect to the WMS site and run Raster > Image Footprints for two layers: Jaskyna and Plavebna_brana. 8WF6AO 3 - Pan to the left so that the image footprint for Plavebna_brana completely disappears from the map. 4 - Run Add WMS Legend Entry with these two layers together. 5 - Check the GDOWMS.log, you can clearly see that no GetMap request has been sent so far. 6 - Pan back so that both image footprints are completely visible in the map view. 7 - Check the GDOWMS.log, the GetMap request has been sent now. 8 - Move mouse pointer inside the intersection of the two image footprints. Even if you can see no data in the map, you can clearly see that the area requested for the WMS legend entry is the intersection of the two bounding boxes, not the bounding box of the union of the two. 8WWKHE Fails to display feature class if index contains XLO,YLO, XHI, YHI and any other column. If the customer creates a non clustered index that contains the XLO,XHI,YLO,YHI and includes any other column from the table, GeoMedia will fail to display the feature class and will return the error: Index, Geometry_XLO, not found for feature classes containing a large number of rows. Building optimal indexes is very important and GMP should not fail on any index definition. 8XU0Z0 Selecting numeric values from a picklist in update attributes command causes an error. When trying to update a numeric value from a picklist in the update attributes command, the following error is given: There are no valid value(s)/expression(s) defined. The field is defined as a number in Oracle. An entry in gpicklist exists to make this value appear in a list. This issue does not exist when selecting string values from the picklist. Workflow to reproduce: 1. Open geoworkspace and connect to Oracle database that was used for import above. 2. Open data window for GDOSYS.GPICKLISTS. 3. Create picklist by inputting following: featurename = ROADS fieldname = ESZL picklisttablename = ROAD_POLY valuefieldname = ID1 descriptionfieldname = ID1 filterclause = 'leave blank'. 4. Vector Tab>Update Attributes. 5. Select ROADS and choose attribute 'ESZL'. June 03, 2016 39

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. 8XXYNP Customizing the Quick Access Toolbar(QAT) is not saved after a machine reboot. Customizing the Quick Access Toolbar (QAT) menu is not saved if the machine is rebooted. If a geoworkspace (.gws) QAT is setup with various commands and saved in the.gws and the machine is rebooted, the saved.gws when reopened does not show the saved QAT. In fact it adds multiple commands to the QAT. 8Y4J0V Ribbon bar disappears on opening saved gws repeatedly. Steps to reproduce: 1. Invoke GM 2. Open saved GWS. 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 ---------------------------. 8ZG7HX Diacritic Characters in Title name are not retained for Legend Entry Name in GM GUI w/wms DS. For this particular WMS, the title names contain Czech Diacrtic characters. The customer has had to remove the diacritic characters in order to get their WMS Service to work. 8ZGFBQ Cannot display WMS Layer when name contains Diacritic Character. Using the WMS Dataserver with a connection to a WMS Service, -- when the layer name contains a Diacritic character, the GM GUI gives error and will not display the layer. 9094B3 Thematic classification displays Memo datatype error "This datatype could not be indexed". Thematic classification displays Memo datatype error "This datatype could not be indexed". To reproduce: 1. Open the attached USSampleData.gws and USSampleData.mdb. 2. Create a unique thematic legend on the states feature using the attribute1 attribute which is memo type. 3. Error appears "This datatype could not be indexed". 4. Click Ok. 5. States Thematic legend entry is added, but doesn't display. 6. Set the States Thematic legend entry to "Display on" and the thematic displays in the map window. It appears "Display by scale" doesn't work initially, but works after changing from "Display on" to "Display by scale". Help states Memo is a valid data type for range and unique thematic legends. 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

7NJGUW using TRUNC operator on Oracle Date field with Spatial Filter. the TRUNC operator, the query will display successfully without a Spatial Filter applied. When a Spatial Filter is applied over the query results, an error messages will display. Once the error message displays, the query cannot be displayed again. The query can be recovered by removing the Spatial Filter, deleting the query, and then recreate the query without a Spatial Filter applied. The query with the TRUNC operator will display without a spatial filter but not when a spatial filter is applied. Steps to recreate the issue: Note: Use the warehouse access database, USSampleDataForDRW.mdb 1. Start GeoMedia Professional 2. Make an Access connection: USSampleDataForDRW.mdb 3. Make a Read/Write connection to any Oracle database 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) > '0JAN-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... 82XDCY Feature Class Definition - multiple edits to SQL Server feature causes 'Out of Memory' error. Using Feature Class Definition to edit lots of attributes (names and types) simultaneously for a SQL Server feature (without saving the changes with the OK button between edits) will result in an Out Of Memory error when you click OK to save the edits. To see the problem use the steps below. 1. Create a new GeoWorkspace and make an SQL Read-Write data server connection to an existing SQL Server database. For my tests I connected to the USA database. 2. Select Feature Class Definition and use the New button to create a new feature class (you can leave the default name of FeatureClass1 and type as Point). Select the Attributes tab and click in each row in the grid (until you get to the 10th row) so that you have created 10 new attributes named Attribute1 through Attribute 10 all of type Text. Click OK to save the new feature class. When the prompt appears stating A feature class must have a primary key attribute. Do you want GeoMedia to generate a primary key of Autonumber data type? Select Yes. 3. Now that you are on the main Feature Class Definition dialog again click the Edit button. The FeatureClass1 feature that you just created should still be highlighted so you will be editing that feature class. Now select the Attributes tab. On the Attributes tab change the data type for each of the Attributes (1 through 10) from Text to another Type (choosing a different type for each attribute if possible). Now change the name of each of the 10 attributes to something new. Now that all of the names have been changed, once again change the type of all of the attributes to a new value (using as many different types as possible). Finally change all of the names again to new names. Click the OK button to save the edits. This will typically result in an error message that states something like the following The attribute someattributename could not be updated. Possible causes include attribute name duplication, maximum attribute name length exceeded, or invalid characters in the attribute name. Out of memory June 03, 2016 41