GeoMedia Desktop 15.01 Issues Resolved - Hexagon Geospatialcommunity.hexagongeospatial.com/.../GeoMedia_Issues_Resolved_15.01_SP1.… · GeoMedia Desktop 15.01 Issues Resolved 1 Row

GeoMedia Desktop 15.01 Issues Resolved

1

Row

Num.

CR # Filed Against Summary Description / How to Reproduce

This report contains CRs for GeoMedia Desktop 15.01. GeoMedia Desktop contains CRs filed against assorted product releases of GeoMedia

Professional, GeoMedia, GeoMedia Fusion, GeoMedia Grid, GeoMedia Parcel Manager, GeoMedia Public Works Manager, and GeoMedia Transaction

Manager. These products were merged into GeoMedia Desktop 14.00. The Filed Against column indicates the previous product that the CR was filed

against.

GeoMedia Desktop 15.01

1. 1-9AUQSV GeoMedia

Desktop

The width of dialog

(control) is too

narrow to display

the entire strings

(English) and is hard

coded.

Internationalization: The width of "Conflict Resolution" dialog (control) is too narrow to

display the entire strings. For example, Connection filed cannot display the whole

connection name (original English name).

2. 1-9AUQV5 GeoMedia

Desktop

The properties

dialog does not have

the title

(GMTransaction

Administrator) in

German version.

The Properties dialog does not have the title (GMTransaction Administrator) in German

version.

The English dialog has the correct title but not the German version. This title is

concatenated and displayed at runtime.

Also, this dialog is too narrow for the longer localized strings. It would be better to make

this dialog wider to accommodate the localized longer strings.


2

Row

Num.


3. GM-22889 GeoMedia

Desktop

We need to

manually add 5

entries to both

Access and Oracle

GDO GALIASTABLE

metadata table for

mini-AFM to work.

Mini-AFM working in an EGIS configuration:

We need to manually add the following 5 entries to both Access and Oracle GDO GALIASTABLE metadata table for mini AFM to work:

INSERT INTO "GDOSYS"."GALIASTABLE"("TABLETYPE", "TABLENAME") VALUES('AFMAssocClasses', 'GDOSYS.AFMASSOCCLASSES');

INSERT INTO "GDOSYS"."GALIASTABLE"("TABLETYPE", "TABLENAME") VALUES('AFMEventHandlers, 'GDOSYS.AFMEVENTHANDLERS');

INSERT INTO "GDOSYS"."GALIASTABLE"("TABLETYPE", "TABLENAME") VALUES('AFMOperClasses, 'GDOSYS.AFMOPERCLASSES');

INSERT INTO "GDOSYS"."GALIASTABLE"("TABLETYPE", "TABLENAME") VALUES('AFMPickLists, 'GDOSYS.AFMPICKLISTS');

INSERT INTO "GDOSYS"."GALIASTABLE"("TABLETYPE", "TABLENAME") VALUES('AFMRuleClasses, 'GDOSYS.AFMRULECLASSES');

4. 1-9CG2Y8 GeoMedia

Objects

The

LoadCustomizedSett

ings method and

SaveCustomizedSett

ings methods -

documented but not

available.

The customers are moving from v. 6.1 to v. 14. They wanted to be able to customize the

ribbon bar and load their custom ribbon bar from their custom command using the

LoadCustomizedSettings and SaveCustomizedSetttings methods. These two methods are

still incorrectly documented in the online API Object Reference. If you use them in a

program, nothing happens.

5. 1-9BHGCE GeoMedia

Desktop

GUI Issues

encountered with

several

components:

GUI Issues encountered with several components. Chinese OS and Chinese GM.

Issues are not seen with English GM with English OS


3

Row

Num.


Chinese OS and

Chinese GM.

6. GM-24922

(internal bug

file by

GeoMedia

Add-on)

GeoMedia

Desktop

IGMMetadataExtens

ion::GetMetadataEx

tension() method

crashes in C# code

but works in VB

code.

In Map Publisher C# standalone utility (Upgrade Cartographic Database), the

IMetaExtension.GetMetadataExtension( out MetadataExtensionsObj ); line crashes. On

investigation, we found that the problem is with Version 3 of following file:

//depot/GeoMedia/GMMain/Implementation/GMCONNECTION/include/GMConnection

.odi

Version2 of this file works fine.

7. 1-7GLVL4 GeoMedia

Desktop

Apollo Catalog

Connection dialog

displays English title

and buttons on the

localized version.

The title of the Apollo Catalog Connection dialog as well as the OK and Cancel buttons

are in English on the localized version. These strings need to be externalized for the

localization and to overwrite the English strings with the localized strings on these items.

8. 1-926RW0 GeoMedia

Desktop

Export to MapInfo

Interchange Format

fails.

Steps to reproduce:

1. Start GM. and then make an Access RW connection to ‘USSample Data.mdb’.

2. Export any ‘FeatureClass’ of this connection using ‘Export to’ MapInfo Interchange

Format from the ‘Manage Data’ tab.

3. Start ‘MapInfo Professional’, and then select the Import option from Table.

4. Browse to the *mif file saved in Step 2, click Open, and then click Save.

5. Observe that an error message is displayed.


4

Row

Num.


9. 1-926RZR GeoMedia

Desktop

Locate Features by

Attribute Search

command headers

are in English.

The Locate Features by Attribute Search command (Analysis > Utilities >Locate Features

by Attribute Search) column headers are English.

These entries are hard coded. They need to be externalized for the localization.

10. 1-99HFNM GeoMedia

Desktop

Error saving a plot

composition

Open Batch Plotting utility, and make a composition sheet. Then select File > Save.

The Save dialog box does not appear in French GeoMedia configuration, French regional

settings. If you set the configuration to English, it is OK.

11. 1-A35831 GeoMedia

Desktop

Define Symbol File

Utility fails to open

some V8 cell files for

conversion to FSM.

User is unable to open some .cel files having complex shape geometry.

12. 1-AFIKNZ GeoMedia

Desktop

Managing legends

with Library Storage

Service causes data

corruption.

The copy to library having a feature class and a group as a name legend is causing data

corruption with SQL Connection.

13. 1-AJM1YM GeoMedia

Desktop

Manage Data >

Export > PRJ file

missing from ESRI

Shapefile Export

In GeoMedia Desktop 15.0 when exporting data to ESRI Shape files, a .prj file is not

created with the exported files. This issue can be reproduced by exporting the US Sample

Data States feature class. The .prj files are not created.

14. 1-926RON GeoMedia

Desktop

WMS GetFeature

info message dialog

is shown in English

WMS GetFeature info message dialog is shown in English on Chinese.

Steps to reproduce :

1. Start GM Pro, and then make an Access connection to USSampledata.mdb.


5

Row

Num.


on Chinese GM Pro

SP2, Build 80.

2. Start WMS Get feature info, and click in the map window.

The following message dialog should be localized:

--------------------------- GeoMedia Desktop --------------------------- There are no queryable

WMS feature classes for the selected point in the Map Window. ---------------------------

OK ---------------------------

15. 1-926RZ9 GeoMedia

Desktop

The layout of

Measure Area

(Home >Measure)

dialog is not Correct

on Japanese and

Chinese.

The layout of Measure Area (Home > Measure) dialog is not correct in Japanese and

Chinese. This dialog is generated at runtime. The fields on the left side are almost cut-off.

Items for Japanese and Chinese (size 9) are bigger than the original English (size 8).

16. 1-9BHGAN GeoMedia

Desktop

Right-click option

menu for curve

mode in layout

window is not

localized on

Chinese.

Right-click menu for curve mode in layout window is not localized on Chinese.

Steps to reproduce:

1. Select Show Layout Window.

2. Select curve mode from the Drawing tab on layout window.

Right click options with (end cancel exit options) are not localized. The right click

options will change when the feature is in progress and the feature is drawn

completely.

17. 1-9BLON2 GeoMedia

Desktop

Display CAD Files

dialog: OK and

Cancel buttons are

almost truncated on

Display the CAD Files dialog: the OK and Cancel buttons are almost truncated on

Japanese and Chinese. This is caused by the resizing function. Size 9 dialog is bigger than

size 8 dialog. Therefore, these buttons are placed at the bottom line.


6

Row

Num.


Japanese and

Chinese.

18. 1-9CSOYK GeoMedia

Desktop

Crash without

opportunity to save

when using labeling

with common

GeoWorkspace

settings

User may get the message "Error activating the command" followed by an application

crash when using Dynamic Labeling. If the user has the map window set up to navigate

using selected records in the data window, then Dynamic Labeling may crash, especially

if the user attempts to use the data window Promote Rows command.

Note: Map window properties are defined such that: "For items in select set" "Center at

current scale".

Steps to reproduce:

1. Open a GeoWorkspace (references Madison County dataset).

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

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

geometries.

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

5. Select the Table > Promote Rows.

Observation: A message is displayed from GeoMedia Desktop, Error activating the

command followed by application crash.

19. 1-A3YGQH GeoMedia

Desktop

GeoMedia exe does

not honor the

framestamp file

from the command

line.

GeoMedia is not honoring the framestamp file passed in by the command line. It is

failing to create an xml document object in order to parse the xml file.


7

Row

Num.


20. 1-9AUR8J GeoMedia

Desktop

Hard-coded strings

for the title of

"Transaction

Manager Settings"

dockable control

There are hard-coded strings for the title of the "Transaction Manager Settings" dockable

control. The strings are in TransactionMGR.cls. This string needs to be externalized for

localization.

21. 1-9AVREF GeoMedia

Desktop

Save As is not

working for second

time on German OS.

On the English OS-GM2015, Burst B and GM2014 SP2 the issue is not reproducible. The

issue exists on German OS-GM2015, Burst B Bld233 and GM2014 SP2, Build102.

Steps to reproduce:

1. Start GM Pro.

2. Make an Access R/W connection to USSampelData.mdb.

3. Add all legend entries to the map window, and then name it legend1.

4. Using the Save As option, try to save it as Test.gws.

5. Open a data window with States feature class.

6. Use Save As again.

Observation: The Save As dialog is not opened and not working for the second time

onwards.

22. 1-A57SLT GeoMedia

Grid

Error message for

Object Space

connection is not

translated into

German.

Steps to reproduce:

1. Start GM.

2. Select Object Space in Warehouse Connection, type C:\Warehouses, and then click

OK.

3. Observe the error dialog is in English and not translated into German:

--------------------------- Object Space Data Server --------------------------- Object Space file

not valid. Please verify the correct file name was given. --------------------------- OK ---------

------------------


8

Row

Num.


23. 1-7PKIDX GeoMedia

Professional

REGRESSION >

Wrong language in

context (right-click)

menu > Layout >

Map Graphic.

Within GM Pro SP1, when both English and French are installed, and when French is the

selected language, the context menu of the Layout > Map Graphic is: - in French if the

regional settings are "Français (France)", and in English if the regional settings are

"Anglais (Etats-Unis)".

24. 1-96X7P6 GeoMedia

Desktop

LOCALIZATION:

English display--The

embedded List

entries need to be

externalized.

The list property of the HeklaDisplay.ctl file contains the localizable strings. These strings

need to be extracted to rc files and pulled in at runtime.

\GeoMediaGrid\Utilities\MFRasterView\HeklaDisplay.ctl and ctx.

There is a workaround at the localization level.

25. 1-96X7W3 GeoMedia

Desktop

LOCALIZATION:

Layer

frmGridViewer.frm

cboGeoType - The

entries of List

property should be

externalized.

Grid: Layer frmGridViewer.frm cboGeoType - The entries of List property should be

externalized for the localization: X, Y Row, and Column.

26. 1-97O8P7 GeoMedia

Desktop

Control text for New

VPF Connection is

not localized -

Chinese GM and

Chinese OS

The control text for New VPF Connection is not localized - Chinese GM and Chinese OS-

GM Pro 2014 SP2, Build 75.

Steps to reproduce:

1. Start GM Pro, and then open a blank GeoWorkspace.

2. Start New Warehouse Connection, and then select VPF from the connection list

Observation: The text of the controls like tab names and buttons are in English whereas

they are localized in the case of other connections.


9

Row

Num.


27. 1-9AUFBS GeoMedia

Desktop

Removing SP1 from

Setup Manager

causes English and

German shortcuts to

co-exist.

Removing SP1 from Setup Manager causes English and German Shortcuts to co-exist on a

machine configured in German as the GM runtime language.

Steps to reproduce: On an English machine,

1. Install GM 2014 RTD (build 244).

2. Install SP1 build 63;

3. Modify to install German language pack;

4. Run Configuration Wizard to select German as GM runtime language. Once

configuration is finished, observe that the GM Shortcut menu strings are swapped to

German;

5. Remove SP1 update from the Setup Manager.

Observe that both English and German start menus co-exist under GM Shortcut menus.

28. 1-9AUQR3 GeoMedia

Desktop

The Japanese

message in the

message box is

garbled

(unreadable).

Internationalization: The message displayed in the GMMsgBox is garbled on Japanese

(and probably Chinese). It seems the default font is "Arial". "Arial' font will not display 2-

byte characters (Japanese and Chinese as well as Russian) correctly (unreadable). The

use of GMMsgBox in GeoMedia does not have this problem.

29. 1-9AUMOL

GeoMedia

Desktop

Insert Dimension

(Vector > Text and

Label > Insert

Dimension) dialog

does not display.

Insert Dimension (Vector > Test and Label > Insert Dimension) dialog does not display the

correct language resource. Observations:

1. German -- English "Select Segment" is displayed. This translation has German special

characters in it.

2. Japanese - Japanese is displayed but the font size is not correct (currently size 8).

3. When switching from Japanese to German on a Japanese OS, German "Select

Segment" is displayed but loses the special characters. Also, the entry in the field is

still Japanese.


10

Row

Num.


4. French - The translation of "Select Segment" is much longer than English. The string

is wrapped to 2 lines. Therefore, there is not enough space to display the entire

strings.

5. Chinese - English is displayed (However, the OS is English).

31. 1-91KXAX

GeoMedia

Desktop

Localization issue:

Edge Match > Rules

tab

Edge Match dialog > Rules tab: A whole control is not displayed. The two options at the

bottom are truncated. Edge Match dialog > Rules tab: An entire control is not displayed.

The two options at the bottom are truncated and invisible in Japanese. This is caused by

the resizing function Size 9 control to be inserted. However, this does not happen on

Chinese (the same size 9 language). In a visual comparison between Japanese and

Chinese resource, there is no difference on layout (size and position). So I do not see any

Japanese resource level problem.

32. 1-91KXGM GeoMedia

Desktop

Localization issue:

Attribute Rules

Attribute Rules dialog: The buttons "Function Filter" and "Queue message" are

overlapped on Japanese. The size 9 dialog size is bigger than the size 8 dialog. The

resizing function will adjust the button position based on the size 8 dialog size; therefore,

these buttons are overlapped even though the buttons are nicely positioned in the VB

form.

Workaround: The user can expand this dialog to eliminate this problem.

33. 1-9BH3B5

GeoMedia

Desktop

Text Translation

issues for some

components-

ChineseGM +

Chinese OS

Issue 1:

1. Start GM Pro.

2. Select Home > Default Height.

Observe that the dialog title is still in English and not translated into Chinese.

Issue 2:

1. Start GM Pro, and then make an Access R/W connection to USSampleData.mdb

delivered with product.


11

Row

Num.


2. Select the Insert > Interactive Area by Face command.

Observe that the tooltip for the "Hole processing Option" is in English instead of Chinese

Note: Issues are specific to Chinese.

Issue 3:

Start Schema Remodeler for the 'Advantage' or 'Essential' tier, and then observe that the

error message is in English and not translated into Chinese

34. 1-9BHFYD GeoMedia

Desktop

Toolbox > Edge

Match Class > Add :

Buttons at the

bottom are

overlapped with the

table.

Toolbox > Edge Match Class > Add : Buttons at the bottom are overlapped with the table.

The table displayed when selecting the "Find Exact", "Delete", and "Add/Modify Rules"

buttons is overlapped in Japanese This may be caused by the font size 9 of Japanese text

table instead of size 8.

35. 1-AW680I GeoMedia

Professional

SinglePass

LegendEntry

LoadData seems to

leak memory.

Retrieving a Legend from a LibraryConnection and running LoadData on its LegendEntries

result in a growing memory usage for consecutive iterations when the SinglePass

property of any given LegendEntry is set to True. When SinglePass is set to False, the

memory usage remains more or less constant. Setting SinglePass to False results in a

drastic reduction in performance, however.

36. 1-AQDP3Q GeoMedia

GeoPDF

Publisher

No Coordinates in

GeoPDF if

GeoMedia Desktop

German is used

There are no Coordinates in GeoPDF output when running GeoMedia GeoPDF Publisher

with German GeoMedia Desktop. Layer and Attributes are correctly exported into

GeoPDF if GeoMedia Desktop German is used, but no coordinates. Support testing

shows this is only a problem on German OS - Win7.

37. 1-AYIPXV GeoMedia

Desktop

Unable to Display

Unique Value

Customer has noted that he/she cannot display Unique Value Thematics for attributes

that are of type MEMO.


12

Row

Num.


Thematics With

Memo Data Type

The thematic memo values can be classified without error but selecting OK to place on

the legend results in the following error:

---------------------------

GeoMedia Desktop

Invalid operation

---------------------------

The resulting classified thematic legend entries are in an unloaded state and if attempt

to Right-click > Load Data the following message is displayed:

---------------------------

GeoMedia Desktop

Unable to display data.

At least one selected legend entry is invalid.

---------------------------

If a previous version GeoWorkspace containing a unique value thematic is opened in

2015 the error states:

---------------------------

GeoMedia Desktop

An error was encountered loading data for [FEANAME] legend entry.

Invalid operation

---------------------------

If you select More.. option you get the message:


13

Row

Num.


---------------------------

Extension, ExtendedPropertySet, not found

---------------------------

38. 1-AQDT9Z GeoMedia

Desktop

CENTERPOINT

functional Attribute

does not support

orientation of

segment if style is

changed.

Changing the style property of a CENTREPOINT function on a linear feature will not

honor the original style orientation.

Use any dataset to reproduce:

1. Create a CENTREPOINT functional attribute on a linear feature.

2. In the legend on the CENTERPOINT query select style properties.

3. Change the style type to GeoMedia Feature symbol file and browse to select

BaseMap.fsm

4. Select the Flow Arrow symbol and click OK to display.

5. The arrow should be aligned with the underlaying segment orientation.

GeoMedia Desktop 15.01 Issues Resolved - Hexagon Geospatialcommunity.hexagongeospatial.com/.../GeoMedia_Issues_Resolved_15.01_SP1.… · GeoMedia Desktop 15.01 Issues Resolved 1 Row

Documents