image scout 2014 issues resolved - hexagon...
TRANSCRIPT
CR# Filed Against Summary Description / How to Reproduce
1 74005_GM GeoMedia Professional Symbols are not displayed at smaller
sizes, for example 0.001.
When the size of the symbol is small, for example, 0.001, the symbol is not displayed, either on
the map window or on the legend.
2 74014_GM GeoMedia Professional Windows bitmap with lower left
origin, row major displays upside
down
The user’s dataset contained .bmp, .csf, and .bpw files.
How to Reproduce:
1. Open a new .gws, and create a new warehouse.
2. Insert Georeferenced Images - World file.
3. Insert provided image.
4. Note: Image displays flipped about a horizontal axis. If you edit the file to change the
orientation to top left, row major, the image displays correctly.
3 74221_GM GeoMedia Professional Feature count does not match some
feature classes with MGE's count.
Features count does not match some feature classes with MGE's count. In a dataset the feature
class count does not match for following feature classes with MGE: GeoGraphics data server
MGE:
1. Survey_Notes_3041 - 2891 1941
2. Adderess_Text_3034 - 476 258
3. Street_Names_3022 - 2 38
4. The user found this while are doing manual testing with a GeoGraphics data server after
upgrading of dgn direct libraries of 0.995.
4 79324_GM GeoMedia Professional Rendering problems with Point string
data (type 22) in a symbol.
How to Reproduce: 1. Start GeoMedia Pro,
create a new GWS. 2. With the Legend - Styles command, create a new
point style. 3. Using the Properties command / Style Properties dialog box, set the following
properties for the newly created style:
Type = MicroStation V8 Design Files
Source = V8CellsPointStringData.dgn
Name = PointStringType22
Size = 75
Override color = none The dgn file has one
"point string continuous" element that resembles an arrow head and one "point string disjoint"
element that is a set of 5 points starting from the arrow head leftwards. The preview window
shows the symbol totally different from what is in the dgn file. The arrow head is rendered as an
ellipse, and the disjoint 5 points are drawn as a straight line.
Image Scout 2014 Issues Resolved
GeoMedia Professional
This report contains three sections: GeoMedia Professional, GeoMedia Image Professional, GeoMedia 3D, GeoMedia VPF Dataserver, GeoDEX. The GeoMedia Desktop section contains CRs
filed against assorted product releases of GeoMedia Professional, GeoMedia Grid. The Filed Against column indicates previous product that the CR
was filed against.
5 82357_GM GeoMedia Professional Data server needs to verify spatial
filter parameters to prevent
exception.
When the client s/w calls OpenRecordset specifying a SpatialOperator and
SpatialFilterGeometry but no GeometryFieldName, an unhandled exception results. The data
server needs to verify that all three parameters are specified before attempting to process a
spatial filter.
6 84641_GM GeoMedia Professional Point features are not displayed in
map window with an Auto CAD 2000
dwg file.
The same problem is observed in GM Pro 06.00.35.10 setup. Point features are not displayed in
the map window with an Auto CAD 2000 dwg file. How to Reproduce: 1.
Start GM Pro, and make an Access r/w connection to 'USSampledata.mdb'.
2. Add 'Cities' FC to the map window; then click on the style of
cities legend, and observe the Legend Properties dialog box is displayed.
3. Click Properties in the Legend Properties dialog box.
4. Observe the Style Properties dialog box is displayed. 5. In the Symbol Style
tab, select 'Auto CAD Drawing Files’. 6. Click the browse button to browse drawing files.
7. Select dwg file. 8. Click
OK in the Style Properties dialog box. 9. Click OK to dismiss the Legend Properties dialog box,
and observer that features are not displayed in the map window.
7 85739_GM GeoMedia Professional Display CAD Files AutoCAD .dwg
displays incorrectly.
The user is trying to display an AutoCAD release 10 .dwg file using the Display CAD Files
command. The problem is if one specific layer is added to the Display CAD Files criteria, the
display of the geometry is incorrect. There is a Word document in the TR data zip file that shows
the display problem with descriptions using GM Pro 6.0. The .dwg displays the layer in question
correctly in AutoCAD's .dwg viewer. How to Reproduce:
Open the DisplayDWG.gws file, and correct the paths to the .csd files.
This .gws was created with GM Pro 6.1.3.6. There are 2 CAD connections in this .gws. CAD
Connection 1 uses the CSD4.csd file, which points to the Data_original.dwg file, and CAD
Connection 2 uses the CSD6.csd file, which points to the Data_withoutLayer01364.dwg. The
CSD4.csd with the Data_original.dwg, which contains the Layer 01364, causes the display
problem. Without layer 01364 in the .dwg, the display of layer 01221 is correct.
8 86694_GM GeoMedia Professional Associate Catalog Records fails with
Oracle connection using windows
authentication.
The Associate Catalog Records command crashes GM Pro using a feature class from an Oracle
warehouse connection using Windows Authentication. User reproduced this crash on both GM
Pro 6.0 and 6.1.4.4. How to Reproduce: 1. Open
blank GeoWorkspace.
2. Connect to a GeoMedia Oracle read-write warehouse using Windows Authentication
(domain).
3. Add several feature classes to the legend.
4. Make a new ODBC catalog connection using an existing Oracle schema created with the
ora.sql script.
5. Run the Associate Catalog Records command.
6. If needed, create a new catalog record for one of the feature classes.
7. Select the feature class from Step 6, and click Associate Feature Class.
8. Select the appropriate feature class from the Oracle ODBC connection, and click OK. GM
crashes displaying the standard error "GM has encountered a problem, email error to
Microsoft".
9 64362_GM GeoMedia Professional Documentation needs elaboration on
distinction between file extension vs.
format.
The user was unable to open .jpg files in GMI or GMILT. Examination of the files shows that it is
really an INGR format 24-bit JPEG compressed raster from PhotoScan. Intergraph formats are
specifically excluded from the supported file formats list (just as a re-named Excel spreadsheet
with a .doc extension cannot be opened in Word). The user wants the documentation to explain
that file format is not determined by the file extension.
10 1-4MSZBH GeoMedia Professional XY Construction Aid Not Operating
Correctly (regression from 6.0)
The user was attempting to use the XY construction aid, and in certain data cases it resulted in
the following error:
GeoMedia Professional --- Coordinate Systems Services Invalid character string. Characters must
be numeric and express a value in the indicated unit. Please correct your input. --- OK --.
This problem also occurred in version 06.01.04.13.
11 1-4RT633 GeoMedia Professional Display CAD Files crashes when
serving V8 design file from customer
(regression from 6.0)
GeoMedia Pro crashes when using Display CAD Files to serve a specific MicroStation V8 XM
version 8.9.4.51 file. The same file can be served successfully with GeoMedia Pro version
06.00.35.16, so this is a regression from that version. The crash also occurs with 06.01.04.13.
How to Reproduce:
1. Create a new blank GeoWorkspace.
2. Select the Display Cad Files command.
3. Choose 'MicroStation V8' from the 'CAD Type' list.
4. Browse to the folder containing the design file; then select the check box in the 'Available
files' list.
5. Click OK to execute the command.
This results in an error message with a 'GeoMedia Professional' title that states "Automation
error The object invoked has disconnected from its clients."
6. After dismissing this error message with OK, a second 'GeoMedia Professional' message is
displayed that states "Unable to establish the connection. None of the selected files are of the
specified file format."
7. Dismiss this message with OK; then click Cancel on the Display CAD Files dialog box. This
results in a 'Microsoft Visual C++ Runtime Library' error that states "Runtime Error! Program:
C:\Program Files\GeoMedia Professional\Program\GeoMedia.exe R6025 - pure virtual function
call".
8. After dismissing this message a GeoMedia.exe crash dialog box is displayed, and the error
report indicates the crash was in module 'update~1.dll'.
9. After dismissing this message there are additional automation error messages displayed
before GeoMedia exits.
When this same workflow is performed with GeoMedia Professional version 06.00.35.16, the
connection to the 'oslas-bd-toc-20-0001.dgn' is successful, as is the display of the features in the
legend/map window. However, when exiting the 6.0 GeoWorkspace there is a 'Pmisc’ message.
12 1-4TF4BR GeoMedia Professional TEXT ORIGIN BY RANGE:TRUE is not
working (Regression)
A user noted a regression behavior in which MicroStation text that displayed correctly in
GeoMedia version 06.01.05.19 with the TEXT ORIGIN BY RANGE .ini setting is no longer correctly
displayed in version 06.01.06.19. The Ustn Geometry shifts downward in Y direction using CAD
Server with Text Origin by Range:TRUE in .ini MicroStation version 8 .dgn geometry shifts in Y
direction using CAD Server with Text Origin by Range:TRUE set in the .ini.
How to Reproduce:
1. Open a blank GeoWorkspace.
2. Select Warehouse > New connection, and then select CAD data server.
3. Browse and select the 000000.CSD, and then click OK.
4. Select Legend > Add Legend Entries, and then select all the features from the CAD connection.
Notice the display that is also available in "TEXT ORIGIN BY RANGE:FALSE.bmp".
5. Edit the 000000.ini file to change "TEXT ORIGIN BY RANGE" to TRUE or "TEXT ORIGIN BY
RANGE:TRUE", and then save the change in the 000000.ini file.
6. Select Warehouse > Connections, select the CAD connection, and then click the Reopen
Connection. Notice the display now shifted in the y direction, which is also available in "TEXT
ORIGIN BY RANGE:TRUE.bmp". The text ranges in the MicroStation version 8 000000.dgn file
were checked, and appeared to be OK.
13 1-4VOXZL GeoMedia Professional Insert Leader Line is crossing same
label pickups that label to display
instead of original label chose.
Insert Leader Line is crossing the same label feature pickups that label to display instead of the
original label chosen in the select set.
How to Reproduce:
1. Select a label that has leader lines enabled.
2. Select the Insert Leader Line command.
3. Place the termination point of the leader line.
4. Cross the leader line over other the label from the same label of Step 1.
5. After crossing over the other label, place one more point, and double click to end the leader
line. The value displayed is the value of the label crossed over, not the original label value
selected in Step 1.
14 1-5QX9LH GeoMedia Professional ISRU's dialog-based (non-command
line) utilities will not run on 64-bit OS
with GeoMedia Zip-files.
If you run Display Header and other utilities, they display a message box titled "ERROR from
Display Header" saying "ERROR finding the resources directory in the registry." The graphical
utilities do not run, but the command-line utilities seem to.
15 1-5QLZD1 GeoMedia Professional Synchronization between Bing, Picto -
Map window lost while working with
saved GeoWorkspace.
How to Reproduce:
1. Invoke GM Pro and create a blank GeoWorkspace.
2. Make Access R/W connection to MadisonCountyAL.mdb delivered with the product.
3. Create an ttribute query for Streets FC with expression ID=15224, and display it in map
window and data window; then Focus on the map window.
4. Add Streets LE to the map window.
5. Select View >External Maps > Bing Maps command, and provide reqd license file.
6. 5.Invoke View>External Maps>Pictomety command and provide license file and image
warehouse file.
7. Keep track options on both Bing and Picto in ON state.
8. Make changes in the map window and observe that they are reflected in Bing and Picto and
vice versa.
9. Focus on the Datawindow such that Bing an Picto controls are displayed, and save the
GeoWorkspace.
10. Exit the application and reopen the GeoWorkspace.
Observation:
Observe that bing control is not maintaining the state correctly. By moving the control slightly it
comes to correct state.
11. Now make changes in the map window
Observation:
Observe that changes were not reflected in either Bing or Picto controls.
Make changes in the Picto control and observe that changes are not reflected in either the map
window or Bing control. Make changes to the Bing control and observe that changes are
reflected in the map window but do not result in a change of Picto control.
Note: The same behavior is observed with a GeoWorkspace saved with the layout window in
focus.
16 1-52OP5O GeoMedia Professional Workflow using spatial filter
commands causes a crash in
GeoMedia Pro.
How to Reproduce:
1. Open a blank GeoWorkspace.
2. Select the Rectangular Fence Spatial Filter command.
3. Place a fence but do not accept it with a data point.
4. Select the Pan command, and slightly adjust the AOI.
5. Select the Polygonal Fence Spatial Filter command. Do not place any points.
6. Select the Rectangular Fence Spatial Filter command; then attempt to place a fence, but data
points are not recognized.
7. Click the Select (NW arrow) command. You will typically see a "GeoMedia has encountered a
problem and needs to close" message at this point. If not, attempt to close the GeoWorkspace
and a comparable message will display.
17 1-5S5WZV GeoMedia Professional Incorrect resource management in
Bing macro causes other code to fail.
Incorrect resource management in Bing macro causes other code to fail.
18 1-5T8LFB GeoMedia Professional Thematic Feature missing from BPU
plot when submitted with command
line.
How to Reproduce:
1. Open provided .gws, restore connection to provided .mdb.
2. Select Layout > File > Plot; plot Adobe PDF. Note the presence of colored thematics over
some Florida counties.
3. Exit and save the .gws
4. Open the .gws in BPU-Select, plot the single layout to Adobe PDF. Output should match that
from framework.
5. Close BPU.
6. Edit the provided .bat file to reference the files on your system properly. Exit and save; then
submit the plot. It will produce a .prn which you can open as a PDF.
You should note that the colored thematic is absent from the command line plot, but is present
in the Interactive GeoMedia plot and the BPU submitted plot. The thematic is missing regardless
of the PDF driver tested (Adobe PDF, Amyuni PDF Suite, PDF995), and also missing if the
command line output is 'exported' to .jpg raster.
19 1-5VA483 GeoMedia Professional Polygon Selection command raises
error on the startup of GeoMedia
through the custom code.
Polygon Selection command raises error on the startup of GeoMedia through the custom code.
20 1-5WLKX1 GeoMedia Professional Plots to PDF cause undesirable
reduction of resolution in raster
image.
User has 1:250000 scale charts they plot to PDF. They use Adobe Acrobat Pro v8. During the
course of their upgrade to GMPro 6.1 they find that the resolution of their shaded relief maps is
much courser - unacceptably so.
How to Reproduce:
1. To reproduce the error, open the provided .gws and restore connection to the provided .mdb
file. You will also have to restore the connection to the provided shaded relief image (.cot file).
2. You should have Adobe Acrobat Pro 8 on the system (plotting to hard-copy A0 sheet is also
possible, but it becomes more difficult to evaluate the problem w/ paper map).
3. Go to the Layout Window, select File > Print.
4. Select Adobe PDF driver, select either an E, A0, or custom sheet size to match or exceed the
layout sheet size. Select OK.
5. Output .pdf file contains blocky pixels that are about 6 times larger on a side, relative to
actual .cot file input. Customer wants those pixels to be full resolution (0.1mm).
21 1-5Y3VCL GeoMedia Professional Analytical Merge command does not
work on the localized version.
Analytical Merge command could not generate the attribute list.
How to Reproduce:
1. Start the Analytical Merge command from the menu.
2. Select a feature class, such as State from "Merge feature in" field; then "By attribute" is set as
default on "Merge criteria". However, the "Attributes" field is empty. No list of attribute is
displayed.
3. When selecting "All" or "Touching" on "Merge criteria", a "GeoMedia" error message is
displayed -- Stated as "Unable to retrieve output Query from merge operation. No current
record (GeoMedia)".
4. Click OK on this error message. Nothing happens.
5. Select the "By attribute" or "By attribute and touching" option in "Merge criteria"; nothing
happens (no error message is displayed and "Attributes" list is still empty).
22 1-58HWVX GeoMedia Professional Editing and continuing a geometry
causes an error with an infinite loop.
The following specific workflow in GeoMedia causes the error message "GeoMediaCommand:
Object variable or with block variable not set" to display.
How to Reproduce:
1. Open US Sample Data (One map window is open by default).
2. Open a second map window; then go back to the first map window .
3. Edit an existing linear geometry by selecting Edit > Geometry >Edit, performing any geometry
edit (for example, moving a keypoint of the line).
4. Do not quit the "Edit Geometry" command; immediately click the menu item of Edit >
Geometry> Continue. The error message of "GeoMediaCommand: Object variable or with block
variable not set" now displays . Clicking OK on the error message repeats the same error over
again for each click.
23 1-5HKMD3 GeoMedia Professional Define Symbol File fails to display/list
some cells from a MicroStation V8
cell file.
The user provided a MicroStation V8 cell library file that contains cells the user is attempting to
convert to .fsm symbols using the Define Symbol File utility. However, when they open the cell
library in the Define Symbol File utility, some cells from the cell library are not present in the
Library list (where the Symbol Name and Description names are shown). The cells that are
missing from Define Symbol File appear to have the same definition as the other cells in the
library that are displayed correctly. For instance, they share the same Cell Properties as shown
in the Model Properties dialog box in MicroStation V8. Specifically the cells all have the ‘Can be
placed as cell’ option checked and the ‘Cell Type’ set to ‘Graphic’. It was also verified that it is
possible to insert and display each of the missing cells in MicroStation V8 successfully, so they
appear to be valid cells.
How to Reproduce:
1. Open the provided .cel cell library in MicroStation V8; then use the File > Models command
see the list of Models defined as cells. Note the presence of models named 52 and 103.
2. Open the Model Properties dialog box for each of these models, and note that they are both
designated as cells by the ‘Can be placed as cells’ option, and they are both set to Graphic for
the Cell Type.
3. After reviewing the Models list, exit MicroStation V8.
4. Start the Define Symbol File Utility, and click Add to display the Add From File dialog box.
5. Change the ‘Files of Type’ filter option to ‘MicroStation V8 Cell File (*.cel/*.dgn)’; then
browse to the folder location containing the ‘survey_gm61.cel’ file, and open that file.
6. The ‘Add Symbols’ dialog box is now displayed with a list of symbols from the cell library.
Scroll through the Symbol Names and note that there is no symbol named 52 or 103 present in
the list despite the presence of cells with those names in the cell.
24 1-5M6ZEZ GeoMedia Professional Custom default printer properties are
not read by Batch Plotting Utility. Also
ignored by command line.
When you run the Batch Plotting Utility, the utility is not inheriting the default printer settings.
As a result, when you run the Batch Plotting Utility from a command line, all output is 8.5 x 11.
Regardless of your default settings in the printer, you can only get 8.5 x 11 output. This has been
duplicated by product planning and by Certification in HSV. The user set the custom default
printer sheet size and orientation in Start > Printers and Faxes > <printer> Properties. These are
read when printing to this printer from the framework graphic interface, but are ignored when
in the Batch Plotting Utility or using command line batch plotting.
25 1-5MWRUT GeoMedia Professional Search fails to return results if search
for numeric value stored in TEXT field.
The user pointed out that the Search command fails to return results when attempting to search
for a numeric values. The problem may be related to GeoMedia parser interpretation of the SQL
filter, but regardless, the user must have the ability to perform wild card searches for numbers
that are stored in a text string field. For example, the user needs to find all streets that have any
occurrence of "431" in the street name field (type text). If the user builds an attribute query
such as: NAME LIKE "*431*"; then records are returned as expected. If the user uses the View >
Searches command to build a parameterized search using same syntax such as: NAME LIKE
"*[Enter Name]*", then records are correctly returned until a spatial filter is applied. Once the
filter is applied, Search returns zero results while the Attribute Query continues to return 395
records. How to Reproduce (workflow 1):
1. Using Customer-supplied data, save and unzip data to a local disk; then open the .gws,
correcting the connection path as needed.
2. Notice the Attribute Query legend entry that defines an attribute filter: Aanduiding LIKE
‘*37*’.
3. Select View > Search; then in the Search dockable control, use the drop-down list to expand
Searches, and select the named search: “Search with EntityField”
4. Again on the Search dockable control, enter the value of: 37, and click Search.
5. Notice that no records are found.
6. If you instead use the search “Search without EntityField”, the three expected records are
found.
How to Reproduce (workflow2):
1. Using Madison County Sample Data 1, save Madison_Co.gws to local disk, and open the file.
2. Notice the Legend Entry "Hwy 431" that is an attribute query using the filter: NAME LIKE
"*431*"
3. Select View > Search; then in the Search dockable control, use the drop-down list to expand
Searches, and select the named search: "Search of Streets by Name".
4. Again on the Search dockable control, enter the value of: 431 and click Search.
5. Notice that no records are found.26 1-5OFSUN GeoMedia Professional Features are missing after spatial
filter is applied.
How to Reproduce:
1. Make a connection to a SmartStore data server.
2. Apply spatial filter to the map extents.
3. Observe that some features are not displayed (filtered out).
27 1-5QGVYL GeoMedia Professional GeoMedia Pro crashes while opening
a GWS file in which the layout
window was minimized at the Save
File step.
GeoMedia Pro crashes while opening a GWS file in which the layout window was minimized at
the Save File step. The crash happens when Terrago Publisher for GeoMedia Pro is installed, and
the layout window was minimized when the GWS file was saved. The crash does not happen if
Terrago Publisher for GeoMedia Pro is installed, and the layout window is either maximized or
restored to previous size when the GWS file was saved. The crash does not happen if Terrago
Publisher for GeoMedia Pro has not been installed. The user thinks this happens as GeoMedia
Pro reads the toolbar customization from the registry. Other 3rd-party add-ins that customize
the toolbar might also experience this problem.
How to Reproduce:
1. Create a blank GeoMedia workspace.
2. Connect to the US sample data Access warehouse.
3. On the Menu bar under Window, select Show Layout Window.
4. Once the blank window displays, minimize the layout window.
5. Save the GeoWorkspace; then exit GeoMedia.
6. Start GeoMedia Pro; then open the previously saved file. The GeoWorkspace will NOT open.
GeoMedia tries to start but will crash.
28 1-5QWF9P GeoMedia Professional GeoMedia installs duplicate
ZIRFL01.dll in Program folder and in
..\common files\Intergraph.
GeoMedia installs duplicate ZIRFL01.dll in Program folder and in ..\common files\Intergraph.
Only one copy should be installed.
29 1-5RXR31 GeoMedia Professional Setup.exe needs to be signed, so
when running setup.exe the dialog
box will not display Security Warning.
Setup.exe needs to be signed, so when running setup.exe the dialog box will not display Security
Warning.
30 1-5SBC5Z GeoMedia Professional Customized data servers not correctly
supported anymore.
Customized data servers are not supported anymore for most of the GeoMedia functions. The
problem occurs in the following commands: Attribute Selection Attribute Query, Validate
Geometry, and Spatial Query.
31 1-5SCXO6 GeoMedia Professional Key-in of a path that ends in '\' into
the 'filename' field causes GM Pro to
exit to desktop.
How to Reproduce:
1. Use Ctrl-C to copy a path (C:\Warehouses\) into the windows buffer; then open GeoMedia
with a new .gws and a new .mdb file.
2. Select Insert > Interactive Image; then paste (Ctrl-V) the path into the ‘filename’ field.
3. Select the Browse button without pasting in a path. GeoMedia crashes. The same behavior is
observed if you type a full path with a terminal '\'. If the path does not have the terminal '\', the
command works as expected. Selecting the Browse button without anything in the filename
field also works as expected.
32 1-5U13JD GeoMedia Professional Insert feature with “Place by
Rectangle” option, and segment
length constraint does not work.
How to Reproduce:
1. Select Insert Feature from the main menu.
2. Select an aerial feature class to place.
3. Select Place by Rectangle.
4. Select Segment Length Constraint from the right-click menu.
5. Check the Lock check box.
6. Type a length value in the Length field.
7. Move the cursor around, and notice that the dynamic segment is NOT displayed with the
locked length; it’s attached to the cursor instead.
33 1-5VNETX GeoMedia Professional GeoWorkspace display scale changes
From one system to another
(Regression).
The problem began as regression in 06.01.05. GeoWorkspace map view display scale is NOT
preserved/saved from one system to another. As the display scale changes, one can see that
map view graphic text and point symbols correspondingly change size, but it is expected that
map view display scale property should be saved even if the .gws is opened on a different
system. For example, a user creates new a GeoWorkspace connected to USSampledata.mdb,
displays States in map view, and sets the display scale to 1:25,000,000, and then exits and saves
the .gws. The user then opens the same GeoWorkspace on another system, and the display
scale is rarely the same and can vary greatly. In the case tested the .gws was saved at
1:25,000,000 but opens at 1:17,706,577 on a different system. It is expected that the display
scale of 1:25,000,000 should be preserved for the map view and that the .gws should appear
generally the same from system to system despite resolution settings.
34 1-5W838V GeoMedia Professional Undoing the deleting object
operations has some problems for
ERDAS IMAGINE.
After investigating this, we found that the ERDAS LabApp problem seems to result from
UndoRedoService implementation limitations. Basically, autonumber fields will not work
reliably with UndoRedoService outside of GeoMedia because UndoRedoService cannot
determine the database type and apply database-specific logic to autonumber fields. Customers
report that they ran into this Undo delete problem while working on GeoMedia integration in
IMAGINE. They can do delete, insert, and edit operations and Undo using GeoMedia’s
UndoRedoService on insert, and edit works fine also. The only problem is that if they delete one
object, which is not the last one in the table, and do Undo to it, they cannot insert a new object
due to an ID conflicting error. They created this simple VB code only to make sure the problem
is not caused by the C++ wrapper classes that Intergraph implemented.
How to Reproduce:
1. Make sure that the Access database and the States table are in good shape.
2. Run the VB application to delete the first record and undo the deletion (Note, GeoMedia
Profession is not running at this moment).
3. Exit the VB application.
4. Start GeoMedia Professional, and try to insert a new record to the States table.
35 1-5WHX6B GeoMedia Professional Spatial Query notification failure
(Spatial Query does not update after
insert).
The user pointed out a notification issue where the spatial query does not correctly update after
insert. For example, a user has a simple spatial query to find all parcels that do NOT Contain
Buildings. The query correctly displays after it is created, showing the parcels that do not
contain building features. The user then inserts a building into a parcel, and spatial query is not
correctly updated. The parcel that now clearly contains a building still participates in the spatial
query of parcels that do NOT contain buildings. If the connection is reopened, the query will
update. Interestingly enough, the spatial query does update if the building is deleted.
36 1-5Z0SK0 GeoMedia Professional Unable to use XY Construction aid for
insert and edit operations
Placing point feature using construction aid X, Y with the Geographic option results in error. This
is a regression from behavior observed in version 6.0.
-- GeoMedia Professional -- Coordinate Systems Services Invalid character string. Characters
must be numeric and express a value in the indicated unit. Please correct your input. -- OK --
How to Reproduce:
1. Open .gws file and correct path to .mdb.
2. Select Insert Feature; then select Study_Point to insert.
3. Right click in the map view; then select the X, Y Construction aid.
4. On the X and Y dialog box, set the mode of placement to "Geographic".
5. Type values for: Longitude: 34:47:00 Latitude: 32:05:00.
6. Click in map view to accept the values. Observation - Error displayed: -----------GeoMedia
Professional -- Coordinate Systems ServicesInvalid character string. Characters must be numeric
and express a value in the indicated unit. Please correct your input. --OK
37 1-60JV1J GeoMedia Professional Changing units for extrusion for one
legend entry changes units for other
legend entries.
If the unit of measure for extrusion of an area feature of a single legend entry is changed, the
unit of measure for other extruded area features will also change. The unit of the legend entry
changed is the only one that should have been altered.
How to Reproduce:
1. Open the GeoWorkspace; then toggle to the 3D window.
2. Review the units for extrusion for Fire_Stations legend entry. It should be 'm' - open style
properties for Hospitals.
3. Note that units for extrusion are 'm'; then change to 'ft', and save changes.
4. Review units for extrusion for Fire_Stations legend entry. It is now 'ft' although the operator
did not change them.
5. NOTE: Altitude options Use offset of unit field has the same bug.
38 1-6X6WQT GeoMedia Professional Files in STILE.MSM are not shared. Files in STILE.MSM are not shared. As a consequence, when IMAGINE and GeoMedia (Pro) are
both installed on a machine, and one of them is uninstalled, it removes the only copy of these
files, corrupting the other product and forcing a repair. This will also happen if GeoMedia (Pro)
and Viewer are installed on the same system.
39 1-62T0AM GeoMedia Professional GMPro is kicking off Bing and
Pictometry commands when a startup
command opens a GeoWorkspace.
Code was added to the framework in 6.1.11 to start the Bing and Pictometry commands as
GeoMedia is coming up. The commands are executing after the startup commands are running.
The problem is because GSM has a startup command that opens the GeoWorkspace. The Bing
and Pict commands do not do anything unless a GeoWorkspace is open. This is why you did not
see a problem when Pro was running normally. However, you would see it anywhere that
someone opens a GeoWorkspace from their startup command.
40 1-66X88X GeoMedia Professional WMS Get Feature Info command fails
with message that default style is
missing.
A user has a WMS that is behind a firewall (not publicly accessible) that they can successfully
serve layers from using the GeoMedia WMS data server. However, when using the WMS
GetFeatureInfo command for the same layer an error is returned stating that the Default style is
missing. The customer provided a GDOWMS.log file and GetCapabilities document for the and it
appears that there are styles associated with the layers. However, the GetMap request as
shown in the GDOWMS.log file does not include a style value (that is, the Style parameter is
blank/null).
Based on the WMS specification (version 1.1.1 and 1.3.0) the STYLES parameter is required in a
GetFeatureInfo request because the GetFeatureInfo request includes a required parameter of
<map_request_copy>, which is a copy of the GetMap request parameters (except for VERSION
and REQUEST). Here is the relevant information from the WMS 1.1.1 specification...
7.3.3.4 map_request_copy
<map request copy> is not a name/value pair like the other parameters. Instead, most of the
GetMap request parameters that generated the original map are repeated. Two are omitted
because GetFeatureInfo provides its own values: VERSION and REQUEST.
41 1-6AGXOV GeoMedia Professional WCS Data Server does not display the
coverage geometry.
The WCS data server can connect to some WCS sites but it fails to properly display the coverage
geometry. It only displays a GDO Area geometry using the Legend > Add Legend Entries
command. It is normal for the Legend > Add Legend Entries command to add all geometry fields
to the map legend. The coverage geometry is present but is not added. As an application level
example you can see the coverage geometry exposed in Functional Attributes.
How to Reproduce:
1. Open the supplied GeoWorkspace.
2. If the WCS connection is established properly, use the Legend > Add Legend Entries command
to add a legend entry.
3. Observation: Notice how no coverage (raster) legend entry is added. Only the footprint is
displayed.
4. If, however, you go into Analysis > Functional Attributes, the Expression dialog box for the
same feature, you can see there is a raster-based coverage geometry available. Double-clicking
this Coverage geometry to create a new expression does allow for the raster to be displayed.
42 1-6QXR7B GeoMedia Professional Invalid conversion of E/N to lon/lats
when max coordinate values are limit:
-180 or +180.
The customer is using the WMS Data Server through WebMap through Smart Client.
43 1-6W7M48 GeoMedia Professional Series of asserts in Debug mode when
dockable control is dismissed.
When a dockable control is deleted, there is a series of debug asserts in the afxwin2.ini and
winocc.cpp files. Once this occurs, it happens for every dockable control when you X off the
control and when you display them. You have to exit GM Pro to start over. Debug asserts seems
to indicate that the window handle has been lost.
44 1-61I129 GeoMedia Professional GeoMedia fails to display features
from WFS that all other tested clients
can display successfully.
GeoMedia Professional is unable to display any features from the World Health Organization
WFS. All of the other WFS clients available for testing (Gaia 3.4.2, Cadcorp SIS Map Browser 7.0,
uDig 1.2.2, and Quatum GIS 1.6.0.) are able to serve features from the same WFS successfully.
How to Reproduce:
1. Create a new GeoWorkspace.
2. Use the New Connection command to make a WFS Read-Only Connection.
3. Use the ‘Add Legend Entries’ command to add the ‘africa_airports_Type’ feature class to the
legend. Note that the legend entry is created, but there are 0 geometries shown. The
‘africa_airports_Type’ feature class contains 1,224 point features, and as noted earlier, all other
WFS clients that were tested can display this feature class successfully.
4. The GDOWFS.log file seems to indicate that there was a response error with the GetFeature
request, and when the GetFeature URL is submitted from Internet Explorer, the following
messages are displayed “The XML page cannot be displayed Cannot view XML input using XSL
style sheet. Please correct the error and then click the Refresh button, or try again later. _____
The namespace prefix is not allowed to start with the reserved string "xml". Error processing
resource 'http://apps.who.int... <wfs:FeatureCollection numberOfFeatures="1224"
timeStamp="2011-12-20T22:38:25.143+01:00" xsi:schemaLocation=http://www.w.... However,
if the same URL is submitted with Mozilla FireFox, the only message returned is “This XML file
does not appear to have any style information associated with it. The document tree is shown
below.” Because other clients are able to successfully complete the GetFeature Request, there
does not seem to be a fatal error with the WFS. This problem is not limited to the
‘africa_airports_Type’ feature class as the same behavior is observed with other features.
45 1-61PG4L GeoMedia Professional Unable to connect to WFS that other
clients can connect to successfully.
GeoMedia Professional is unable to establish a WFS Read-Only data server connection to the
WFS. When attempting to make a new connection with the WFS data server, the following error
occurs: {http://www.opengis.net/gml}Stations-World is not found in the collection. Other WFS
clients including Gaia 3.4.2, CadCorp SIS Map Browser 7.0, and Quantum GIS 1.6.0 are able to
connect and display features from the same WFS successfully. However, the uDig 1.2.2 client
does report an error stating “Expected {http://www.opengis.net/wfs}WFS_Capabilities but was
null#HTML”. The user suspects that this may be because that client is unable to parse the
GetCapabilites request.
How to Reproduce:
1. Create a new GeoWorkspace.
2. Use the New Connection command to make a WFS Read-Only Connection. The ‘Unable to
connect to the database.’ message is displayed, and clicking the More displays the additional
message: {http://www.opengis.net/gml}Stations-World is not found in the collection. The
GDOWFS.log file does not appear to indicate any errors as both the GetCapabilities and
DescribeFeatureType requests seemed to have been successful.
46 1-62FE0J GeoMedia Professional [GM-772] Update Attributes Using
Text command does not work
properly with Polish regional settings.
The Update Attributes Using Text command does not work properly with Polish regional
settings and English GeoMedia Professional 06.01.11.13. Running English GM Pro 06.01.11.13
with Polish regional settings, Update Attributes Using Text only works properly with integer
values but does not work using fractional values. For example, for value 1,3 meters it does not
update the attribute value, but for value 1 meter it updates values correctly.
How to Reproduce:
1. Using an English operating system and English GeoMedia Professional 06.01.11.13, set
regional settings on English machine to Polish regional settings.
2. Open a blank GeoWorkspace and create a new Access connection to ussample.mdb.
3. Use the attached "Service Request Number 1-363682971.docx" document to go through the
workflow to see problem.
47 1-62MXGL GeoMedia Professional Legend Entry from category unloaded
in Insert Feature and Change Feature
Class workflows
Legend Entry from category unloaded in Insert Feature and Change Feature Class workflows
48 1-630TN5 GeoMedia Professional Transaction POST requests missing
Content-Type header.
When trying to manipulate a feature from a feature class served by a WFS-T service, the
GeoMedia WFS RW Data Server issues WFS Transaction XML requests by HTTP POST which are
missing the Content-Type header.
-----------
This does not work with WCF based services that expect the Content-Type header and cannot
identify the format of the HTTP request body. The result is a 'HTTP 415 Missing Content Type'
response.
Furthermore, the HTTP 1.1 protocol specification says, that the Content-Type header SHOULD
be sent with the request and when missing, the recipient MAY try to guess the content type, but
SHOULD default to application/octet-stream (http://www.w3.org/Protocols/rfc2616/rfc2616-
sec7.html).
This issue makes it impossible to manipulate features served by SDI Pro's WFS services in
version 1.1.0
49 1-63UVE1 GeoMedia Professional Inconsistency in LENGTH functional
attribute documentation.
Inside the Functional Attribute dialog box there are four parameters for the LENGTH function
(geometry, RefSpace, UnitofMeasure, TwoD). In the same version of GM Pro the Help topics
search on LENGTH shows the following parameters (Geometry, MeasType, UnitofMeasure,
TwoD). One identifies RefSpace while the other MeasType as a parameter in the LENGTH
functional expression. This creates some confusion for users and is an inconsistency in the
documentation.
50 1-646LZK GeoMedia Professional AutoCAD Scanner serves ScaleX as a
null value if AutoCAD block has been
mirrored.
AutoCAD Scanner Serves ScaleX as a NULL value if AutoCAD block has been mirrored. When an
AutoCAD block has been mirrored, AutoCAD sets its own ScaleX property to –1. When this
property is exposed in GeoMedia; however, the value is served as a null value.
51 1-65P7NI GeoMedia Professional The font set on Text style buttons
needs to be set as MS Sans Serif.
The font set on those test style buttons are Times Romans now. This font needs to be changed
to MS San Serif. Otherwise, Russian characters will be garbled. For the localization, no specific
Western font, such as Arial or Times Romans, should be used on VB. Those fonts will cause the
garbled character on Russian or Chinese. MS San Serif must be used.
52 1-6KMDGI GeoMedia Professional The WMS Data Server is not
honoring/using the Parent/Root CRS
system.
The WMS Data Server is not honoring/using the Parent/Root CRS system. This is true even if the
CRS from the Root layer is defined in a .ini. In this particular case, the user has defined the
Default CRS in the .ini file to be EPSG:900913. However, the resulting coordinate system of the
geoworkspace is always CRS84.
Here is the URL of the WMS service: http://dpc.geosdi.org/geoserver/ows
Here is the URL used for the GetCapabilities document:
http://dpc.geosdi.org/geoserver/ows?SERVICE=WMS&CRS=EPSG:900913&VERSION=1.3.0&REQ
UEST=GetCapabilities
According to the 1.3.0 WMS spec:
7.2.4.6.7 CRS
Every Layer is available in one or more layer coordinate reference systems. 6.7.3 discusses the
Layer CRS. In
order to indicate which Layer CRSs are available, every named Layer shall have at least one
<CRS> element that
is either stated explicitly or inherited from a parent Layer. The root <Layer> element shall
include a sequence of
zero or more CRS elements listing all CRSs that are common to all subsidiary layers. A child layer
may optionally
add to the list inherited from a parent layer. Any duplication shall be ignored by clients.
When a Layer is available in several coordinate reference systems, the list of available CRS
values shall be
represented as a sequence of <CRS> elements, each of which contains only a single CRS name.
EXAMPLE <CRS>CRS:84</CRS> <CRS>EPSG:26718</CRS>.
The critical statement from the section above is the statement that: “The root Layer element
shall include a sequence of zero or more CRS elements listing all CRSs that are common to ALL
subsidiary layers. A Child layer may optionally add to the list inherited from a parent layer”.
So, if the user defines a .ini file for the WMS Data Server that defines the Default CRS to be one
of the CRSs listed in the Root/Parent CRSs, it should display the map layers in that CRS, and the 53 1-6NSFX1 GeoMedia Professional CompositePolygonGeometry
consisting of two Arcs is output as
stroked linestring. – It should be
polygon.
The customer is using GeoMediaWebMap to build a GeoRSS feed that is consumed by an
internal application.
The original Geometry is an Oracle Circle type that when viewed by GM is a
CompositePolygonGeometry consisting of two arc geometries. The output type in the
ExportToGeoRSSService xml file is a linestring, but the output type should remain a polygon.
User understands why the stroking is required, but after the stroking of the arcs is complete, the
output type should be a polygon.
For comparison purposes, the Export to Shape File command strokes the Arc Geometry
components to a linestring and outputs a polygon.
54 1-6NY2MY GeoMedia Professional Convert layout legend to graphics -
icons disappear completely, text
changed.
Environment: Any Windows 7 Environment, GM Pro 6.1.10.14.
How to Reproduce:
1. Open the USSampleData GeoWorkspace.
2. Select Window > Layout Window.
3. Select Sheets > Import Layout and select A4wide.glt.
4. Select the Layout frame and Insert > Graphics into Layout Frames.
5. Keep the defaults as it is and click OK.
6. Select the Legend frame and click Properties.
7. Select any of the legend entries, say Rivers, and click Properties.
8. Select Legend Frame and select Convert to Graphic from right-click menu.
9. Problem : Observe that Icons disappear from the legend area.
55 1-66QK1H GeoMedia Professional Internationalization: Hard-coded
English message. Needs to be
extracted for localization.
The English message is displayed when you:
1. Place Map with Static Mode on the Layout sheet.
2. Select the map placed.
3. Select the Map Window Legend Properties command.
4. The displayed message is English.
56 1-66522U GeoMedia Professional Data window does not display a non-
spatial query imported from a library
with active spatial filter.
The data window does not display a non-spatial query imported from a library when a spatial
filter is present in the GeoWorkspace. In our workflow, we have an Oracle connection, library
connection, and active spatial filter. We copy the non-spatial query from the library to the
GeoWorkspace using Tools > Library Organizer. We then open a new data window, expand
Queries, and select the non-spatial query. The data window does not display the data, but
generates the following message: "The selected feature class or query cannot be displayed. The
feature class or query is invalid or the connection is closed." If a spatial filter is not present
when the query is copied over from the library, the query can be displayed in the data window.
Any non-spatial table within an Oracle warehouse can be used to replicate the issue.
57 1-66OBHA GeoMedia Professional Problem using scale range on large
Oracle tables.
We are experiencing poor performance when we work with large Oracle tables in GeoMedia
and GeoMedia Professional. We are building GWS files that will be used for creating WMS
services. Those GWS files are based on Oracle spatial data. Some tables contain data that is
planned to be used at small scale (1:5 000 000@1:10 000 000) and other contains data to be
used at bigger scale (1:1@1:50000). Our problem is that even if we have defined all
appropriated scale ranges, it seems that GeoMedia is querying all tables, including tables that
are not supposed to display at the window scale. It looks like GeoMedia is getting all the data
from the database then applying the scale filtering. This behavior is causing GeoMedia to crash.
To operate without crashing, we apply a spatial filter. That way, GeoMedia consumes a lot less
memory and is able to operate. But again, GeoMedia is querying all the tables even those that
are not displayable. GeoMedia should be checking which layers to display before going to the
database.
How to Reproduce:
1. Import Oracle data from the data location.
2. Open displaybyscale.gws; then alter properties of the Oracle connection to match system
location/display. Note that display scale is 1:19342982, and all legend items are display by scale.
3. Zoom in once on the state of Ohio to come to a display scale of 1:9671491, and note that
only OHIO_LRS features are set to display at this level. All others are display off. However,
GeoMedia is querying all feature classes in the legend when at any scale instead of only those
that pertain to the current scale. This is causing lag and performance issues as the datasets
increase in number of records.
58 1-66QINB GeoMedia Professional Split Feature By Point does not honor
Vector Snap settings (shows disabled
snap types).
The Split Feature command does not honor the Vector Snap settings made by the user when the
‘Split Feature By Point’ option is selected. More specifically, the ‘Vertex Snap’ and ‘End Point
Snap’ glyphs are always shown even if the user has disabled those snap types on the SmartSnap
toolbar. For instance if the user has enabled only the ‘On Element Snap’(with all other vector
snaps disabled) when using ‘Split Feature By Point’, the ‘Vertex Snap’ and ‘End Point Snap’
glyphs will continue to be shown even though the user has disabled those snaps.
How to Reproduce:
1. Open a new blank GeoWorkspace , and then make an Access warehouse connection to
USSampleData.mdb.
2. Add the Interstates feature class to the legend.
3. Use the SmartSnap toolbar to disable all of the vector snap options except the ‘On Element
Snap’ by clicking on the appropriate toolbar buttons to disable all of the snaps other than ‘On
Element Snap’.
4. Select one of the Interstate features in the map window.
5. Select Edit > Split Feature.
6. On the Split Feature dockable control select the ‘Split by Point’ option by pressing the left-
most button. The prompt should now state “Move cursor to point on feature to split.”
7. Move the cursor along the selected Interstate feature.
8. Note that there are vector snap glyphs shown for both the enabled ‘On Element Snap’ as
expected, but there are also snap glyphs shown for ‘Vertex Snap’ and ‘End Point Snap’ even
though those snap types are disabled on the SmartSnap toolbar. Only the ‘On Element Snap’
glyph should be shown in this case because it is the only snap type that is enabled on the
SmartSnap toolbar. The 'Split By Polyline' and 'Split By Polygon' options do not exhibit this
problem.
59 1-6C8ODS GeoMedia Professional Equidistant Conic transformation fails
if geometry contains a large number
of vertices.
The transformation from a Geographic coordinate system to an Equidistant Conic (Simple Conic)
projection fails if the source geometry has a very large number of vertices resulting in the
transformed feature class failing to display in the map window. The test case is an area feature
representing Australia with a geometry type of PolygonGeometry with 34,965 vertices. If the
geometry of the feature is simplified using the Simplify Geometry command so that it contains
32,424 vertices, it will then be transformed successfully. The transformation of the original
source geometry with 34,965 vertices was tested with a large number of other projections
appropriate for continent level mapping and they all succeeded, so this seems to be a problem
specific to the Equidistant Conic (Simple Conic) projection. The list of other tested projections is
included below the workflow.
How to Reproduce:
1. Create a new blank GeoWorkspace.
2. Use the New Connection command to create an Access warehouse connection.
3. Use the Add Legend Entries command to add the feature class to the legend. This will display
a single area feature that represents Australia in the map window.
4. Select the View > GeoWorkspace Coordinate System command, and note that the current
coordinate system is Geographic with a WGS84 datum.
5. Click Load on the GeoWorkspace Coordinate System dialog box.
6. From the Load GeoWorkspace Coordinate System dialog box, browse for the ‘SimplConic.csf’
file, select it, then click Open. The coordinate system defined in the SimpleConic.csf file uses the
Projection algorithm of ‘Equidistant Conic (Simple Conic)’ with Projection Parameters as
follows… Longitude of origin: 140:00:00.000 dms Latitude of origin: 0:00:00.000 dms Standard
parallel 1: -20:00:00.000 dms Standard parallel 2: -30:00:00.000 dms False X: 0.00 m False Y:
0.00 m The datum is WGS 84.
7. Click the OK button on the GeoWorkspace Coordinate System dialog box.
60 1-6D5ZY7 GeoMedia Professional Registry keys under
HKEY_LOCAL_MACHINE\SOFTWARE\I
ntergraph are created with no
permissions set.
A user reports that when GeoMedia Professional is installed on a Vista or Windows 7 system, all
registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph are created with no
permissions set. This causes a problem when we install our custom commands with a Visual
Studio deployment project installer because that creates sub-keys with no access allowed. The
GeoMedia installer should copy the permissions of parent keys to their permissions unless it
sets explicit permissions for a key. The same applies to the Transportation Manager installer,
which creates HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\GeoMedia
Professional\06.01\ApplicationCommands with no permissions set, causing the same problem.
We can work around this for ourselves with regedit, but would not wish to ask our users to do
that." This has been verified that on a Windows 7 64-bit machine. The
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intergraph\GeoMedia Professional key
does not have any permissions defined. It has also been confirmed with Configuration
Management that this is not by design and should be considered a defect.
61 1-6DRHS7 GeoMedia Professional Deslection of select set features
through a fence (option 2 in GM
Users Guide page 206) doesn't work.
Discrepancy between documentation and functionality: GM Pro Users Guide page 206 says: “To
remove features from a select set: You can remove a feature from a select set in the following
two ways: Hold down CTRL or SHIFT while left clicking the feature you want to remove from the
select set. Hold CTRL or SHIFT while clicking and dragging to place a fence around the features
you want to remove from the select set. You must hold down CTRL or SHIFT, or the select set
will be replaced. Actually deslection by fence (option 2) does not work.
62 1-6FMHGF GeoMedia Professional Incorrect Screenshot for Attribute
Update of Text Attributes in GM Pro
User Guide
It would be very helpful to have a correct screenshot for Attribute Update updating Text values.
The screenshot on page 324 of the User Guide shows up Text entry. But the text should be set in
single quotes: 'Madison'.
63 1-6G6JG9 GeoMedia Professional BigTIFF Display > Display is blank at
'fit all' scale for a large .btf file.
Intermittent crash.
The environment is : Windows 7 64 bit and GM Pro 06.01.11.13 (English).
How to Reproduce:
1. Create a new warehouse.
2. Use Insert Georeferenced Images to create a new feature class, and then insert a BigTiff file
(6.8 GB).
3. Use the Add Legend Entries command to display the new feature class. Only the footprint of
the image is displayed (Insert_GeoreferencedImage.png).
4. After some Zooming In, the image is visible, but the scale of apparition is variable.
5. After some Zooming In/Zooming Out/Panning, GM Pro crashes. An error appears in the
EventViewer. The process takes more than 3 GB. The BigTIFF file is available from the filer.
64 1-6HV0K3 GeoMedia Professional AutoCAD polygon with SOLID hatch
served incorrectly, with non-uniform
lines.
The CAD data server does not properly serve polygons that contain a Solid hatch fill from an
AutoCAD dwg file. Instead of a fill color (or no hatch at all), the polygon is served with a series of
somewhat random lines within the polygon boundary and typically those lines are not uniform
in direction or spacing. By contrast other patterned hatch fills (such as Angle and Brick) are
served correctly, so the issue seems to be unique to the Solid hatch fill.
How to Reproduce (example based on user data):
1. Open the ‘CadServer AutoCAD.csd’ with the ‘Define CAD Server Schema File’ utility.
2. Use the Feature Class > Select Maps and Feature Class > Select Coordinate System Files
commands to modify the folder path to point to the location of the ‘SolidHatchError.dwg’ file
and the ‘Coordenadas AutoCAD.csf’ on your machine.
3. Use the Options > Connection command to edit the Warehouse Configuration File location to
point to the location of the ‘Configuración AutoCAD.ini’.
4. Start GeoMedia Professional and create a new blank GeoWorkspace.
5. Use the New Connection command to establish a CAD Server connection to the ‘CadServer
AutoCAD.csd’ file.
6. Use Add Legend entries to add the feature class’ to the legend.
Observation: There are five area features displayed. Note that the three features on the left side
of the map window have a series of non-uniform lines (some vertical, some horizontal, and
some at an angle) within their outer boundaries. These are the features that are assigned a Solid
hatch fill in AutoCAD. *SEE NOTES FOR COMPLETE DESCRIPTION*
65 1-6MAMX3 GeoMedia Professional Blank context menu opens on placing
any feature and right clicking in layout
window.
How to Reproduce:
1. Start GM Pro, and then select a new gws.
2. Switch window from map window to layout window.
3. Click on 'Drawing' tab, and then select 'Line' from 'Insert Geometry' frame.
4. Digitize the first point on the layout window, and then right click on the feature. Observation:
Blank context menu pops up .
66 1-6MAN1J GeoMedia Professional A blank menu pops up on right-
clicking Create Symbol in layout
window.
How to Reproduce:
1. Start GM Pro classic mode, and then select a new gws.
2. Switch from the map window to the layout window.
3. Select View > Toolbars.
4. In the ‘Toolbars' dialog box, check 'placing' option; then click OK.
5. In placing the toolbar, click the 'symbol' icon.
6. Digitize on the layout window, and then right click on the feature.
Observation: A blank menu pops up. The expected outcome is to show a menu that contains an
"Exit " menu item.
67 1-6QYFFP GeoMedia Professional "Insert Cartographic Grid" should be
disabled on the ribbon bar, but it is
not.
In the layout window, when nothing is selected, the "Grids and Index > Insert Cartographic Grid"
ribbon bar entry should be disabled, but it is not. This functionality works fine in classic mode
GeoMedia Professional. In ribbon mode with the layout window active, the Layout > Map
Graphics > Update Map Graphics command should be disabled when a map is not selected in
the layout window. It is always selected. In the Layout Window Ribbon bar, nothing is ever
really disabled under the Layout tab.
68 1-6SRZ3T GeoMedia Professional Need to document workflow to
display image data from WCS
connection.
The WCS data server serves image footprints that can be selected and used with the View >
Display Selected Images command to display the associated image data. This is not
documented. There should be a change to the User Guide and possibly appropriate areas of
Help to note the use of the Display Selected Images command to display WCS raster data.
69 1-6UIXJU GeoMedia Professional SI-1171: pservice error message after
adding MapInfo connection Legend
Entries.
How to Reproduce:
1. Open a new GeoWorkspace, and then make a connection to USSampleData.mdb.
2. Add States to the legend and apply a rectangular spatial filter. The spatial filter did not
happen correctly as features outside of the filter were being displayed.
3. Make a MapInfo connection to USA data.
4. After a while, on clicking somewhere on map window this pservice error is seen: The
InputRecordset cannot be modified after retrieving the OutputRecordset.
70 1-6W8RUN GeoMedia Professional Error displayed while working with
Search command.
How to Reproduce:
1. Start GM Pro, and then make an Access R-W connection to USSampleData.mdb delivered
with product.
2. Add States LE to the map window.
3. Select Tools > Queued Edit, and then select States.
4. Select the Search command.
5. Choose States, enter Alabama, and click OK.
6. Using Queued Edit, move to the next record.
7. Focus on the Search command; enter Texas and click OK.
Observation: The error displays ‘Key in not unique in Collection”.
8. After clicking OK, the map Texas gets highlighted as expected.
71 1-62FHDQ GeoMedia Professional Display of pre-defined symbols in 6.1
is degraded from 6.0.
Customer reported that after upgrading from 6.0 to 6.1 (06.01.11.13), the pre-defined ‘Circle’
symbol was no longer displayed at the origin of the placement point. After researching the
issue, it appears that the display in 6.1 of these symbols is degraded so that they appear offset
from the origin and irregular in shape.
72 1-648WWP GeoMedia Professional AutoCAD scanner serves certain
AutoCAD arcs incorrectly.
User has noted that certain (but not all) arcs curve in the wrong direction. Problem has been
noted with arcs that participate as members of an AutoCAD block. The block graphic does not
appear as it does in GeoMedia when the server has been set to: SERVE BLOCK GEOMETRY:TRUE.
73 1-63WQ9Z GeoMedia Professional Problem with the Attribute Selection
command using French GM on French
WIN7 OR XP.
Attribute selection query property does not handle adding a new attribute column to the
feature class table. New attribute column disappears in the Select Set Properties after bringing
the Attribute Selection query up in Queries > Properties and checking and unchecking the added
attribute column.
74 1-568KO3 GeoMedia Professional Problem with the usage of wildcard
characters in Attribute Query.
How to Reproduce:
1. Run the Attribute Query command. A textbox will appear. Enter the following text "%场"
(Chinese character) in to the text field.
2. GeoMedia crashes.
75 1-4XQ87H GeoMedia Professional GeoMedia crashes when a text file
connection is open in Excel.
GeoMedia crashes when adding a text file connection feature to the legend and the text file is
open in Excel. The crash also happens when selecting the text file on the
Output_To_Feature_Classess dialog box while the text file is open in Excel. GeoMedia should
either display a message, for example, "Text file in use" or "Text file open in another
application", or allow the text file to be used. User determined the crash occurs on GeoMedia
Professional versions 6.1.6.19 and 6.1.4.13.
76 1-57PTZZ GeoMedia Professional Default value is not correctly assigned
on text fields when feature is placed.
The following problem has been reported regarding setting a default value with a leading 0
character in a Text Data Type field. Observed this problem when reviewing a placed feature in
the data window and with Properties:
How to Reproduce:
1. Open a blank GeoWorkspace.
2. Create a new warehouse (normal.mdt).
3. Create a new feature class with the following fields: ID (Autonumber, PrimaryKey), and
Attribute2 (Text, 50).
4. Assign a default value on the Attribute2 field: "00012345"(only numbers, and begining with at
least a zero).
5. Create some objects in this feature class (without changing any value).
6. Open a data window on this feature class. All features have a value in the Attribute 2 field,
but this value is "12345", without the zeros.
If you open the Warehouse > Feature Class Definition command, you can see that the default
value is correct ("00012345"). If you open the .mdb file with MSAccess and look on the "Design
View" of the table, the default value is incorrect ("12345").
77 1-57RTO9 GeoMedia Professional Raster from WCS Web service not
honoring transparency style setting.
The user connected to the WCS Web service using the WCS data server. The user displayed
several image footprints and the corresponding images using View > Display Selected Images. In
previous releases, the user was able to set transparency for 0-value pixels within the minimum
bounding rectangle of the image.
78 1-61PG4L GeoMedia Professional Unable to connect to WFS that other
clients can connect to successfully.
GeoMedia Professional is unable to establish a WFS Read-Only data server connection to the
WFS.
How to Reproduce:
1. Create a new GeoWorkspace.
2. Use the New Connection command to make a WFS Read-Only connection to the supplied
service.
The GDOWFS.log file does not appear to indicate any errors as both the GetCapabilities and
DescribeFeatureType requests seemed to have been successful.
79 78707_GM GeoMedia Professional Some elements are missing in the
rendered symbol. Some are awry due
to line style.
How to Reproduce:
1. Start GM, Create a new GeoWorkspace. Select > Legend > Styles, and
then select New Point Style.
2. Click Properties to display the Style Properties dialog box for the newly
created style.
3. Select MicroStation V8 Design Files and Browse for the dgn in the data
path.
4. Select Default in the Name drop-down list, set the Input size to 75, and
then click OK.
5. See the preview on the Styles dialog box.
Use the magnify command to see clearly. The cell in the dgn contains:
resembles the letter S. This is missing in the rendered symbol.
line style. This looks fine.
the line style. This looks fine.
4 as the line style. This looks a little awry, especially when not
magnified much.
and weights resembling the letter I. This is missing.
T. This is missing.
weight. This is shown incorrectly filled though the element is not
marked filled and the line styles and weights do not look correct.
80 1-4P57KQ GeoMedia Professional Map graphic display order incorrect
relative to existing graphics after
insert graphic into existing.
User noted after inserting map graphics into Layout Frames, the display
order of the map frame (relative to other layout graphic items) is not
preserved. The map frame is displayed on top of existing graphics such
that other graphic items are obscured.
How to Reproduce:
1. Extract appropriate data to the \Warehouses folder.
2. Open an appropriate GeoWorkspace.
3. In layout view, notice there are graphics in the lower left of the map
frame. Notice how the layout map frame is behind these graphics.
4. Select Map Frame (map frame group is selected).
5. Use Insert > Graphics into Layout Frames command to populate.
6. Observe the display order of the map frame is now on top the existing
graphics (lower left). The layout display order is not preserved.
The problem occurs in Batch Plotting workflows. When you print from
GeoMedia, the legend is above the map frame. When you use that
same template in Batch Plotting, the legend always appears below the
map frame.
81 1-4ZZGB8 GeoMedia Professional French GM Pro - Attribute Queries on
Date Fields return no results when
using French SQL Server.
French GeoMedia Pro and French SQL Server:
Attribute queries on date fields return no results on French systems. The
query is sent to the database but never matches dates as stored. This
occurs even if the date is selected using the Show Values command. The
example case has the date set using GeoMedia's Update Attribute
command with the Date Field is set to a constant. A simple query on the
date in that field returns zero results.
82 1-4S7O62 GeoMedia Professional Export to MIF creates .mif file with
comma decimal separator for Angle -
causes error when importing.
When the regional settings for the operating system is set to Dutch
(Netherlands) or some other region using a comma for the decimal
separator, the Export to MapInfo Interchange Format command exports
the Angle value in the .mif file with a comma as the decimal separator.
This is incorrect and causes an error when importing the .mif file with the
MapInfo application. MapInfo expects the decimal separator in the .mif
file to always be a point, so Export to MapInfo Interchange Format needs
to export decimal separators as points in the .mif regardless of the
regional options. This will ensure that the GM Pro Export command
matches the behavior of the Export Table to File command used to export
.mif files in the MapInfo application itself.
How to Reproduce:
1. Open the Regional and Language Options dialog box from Settings >
Control Panel, and on the Regional Options tab select Dutch
(Netherlands) from the drop-down list in the Standards and Formats
frame.
2. Start GeoMedia Pro, open the TextAngle.gws, and correct the
connection path to the TextAngle.mdb Access warehouse when
prompted.
3. Select Warehouse > Export to > MapInfo Interchange Format.
4. Select TextClass1 from the 'Features to export' drop-down list.
5. Enter a .mif name of your choice in the Export to field, or accept the
default, and click Apply to perform the export.
6. Use NotePad to open the .mif file and notice the last line of the file
contains the line “Angle 50,90000000000000" where the 50.9 angle of
the rotated text feature was output with a comma for the decimal
separator. Notice that the decimal separator for the X, Y coordinates
in the preceding lines is a point rather than a comma.
83 1-51S8U6 GeoMedia Professional Insert > By Paper Size: Display of map
graphic properties and OK causes
scale change.
How to Reproduce:
1. Open USSampleData.gws, and restore the connection to
USSampleData.mdb.
2. In the layout window, Sheet1 should be A size landscape. Select Insert
> Map, using Paper Size method to define geographic extent: Height =
8in, Width = 10in, and Scale=10,000,000.
3. Click OK, define map in the map view, and place it in layout Sheet1.
4. Double click on the map graphic to display the Map Properties dialog
box. The checkbox Modify width, height, and map scale
independently should not be checked (default condition).
5. Review values - Height, Width, and Scale are all as previously defined.
6. Click OK without changing any values.
7. Double click on the map graphic again. The Map Properties dialog box
appears, but the Scale value is no longer 1:10,000,000.
In a test, the new value was 9,999,542. This error causes problems if
the user adds a cartographic grid.
Also reported was a problem with carto grid that has its cause in the
change to the map graphic scale. Workaround is to check the Modify
width, height, and map scale independently checkbox, verify the scale
does not change after exiting the dialog box, and then place the carto
grid as usual.
84 1-5A7UFA GeoMedia Professional GeoWorkspace will not save after
changing KML publishing
configuration.
User has a GeoWorkspace that periodically refuses to save, giving the
message: Failed to save document. When the user clicks OK, it gives the
message: Unable to save the GeoWorkspace. Failure may be due to
insufficient disk space.
This is not an overly large GeoWorkspace; there is plenty of disk space,
and the other GeoWorkspaces are saved without any problems. User has
had this sort of problem with other GeoWorkspaces in the past, but
usually only when they are old and cumbersome, or have become
corrupted in some manner. This GeoWorkspace is fairly new and not
overly burdened down by queries. After the user reboots, it sometimes
save for a few times, then it just refuses to save at some point.
How to Reproduce:
1. Unzip data files, open the GeoWorkspace, and re-create connections
as needed.
2. Select File > Publish > Configure KML Publishing.
3. For each of various feature classes, select 'Get Placemark names from:'
Name, and choose to publish attributes.
4. Click OK, and then select File >Save GeoWorkspace. Observe that Save
occurs as designed in the legend.
5. Right click 'Roads' thematic, and choose 'display on'.
6. Select File > Publish > Configure KML Publishing.
7. For each of the feature classes, select 'Get Placemark names from: Full
Name'.
8. Click OK, and then select File > Save GeoWorkspace. Error is returned:
"Failed to Save Document".
9. Click OK. Error is returned: "Unable to save the GeoWorkspace. Failure
may be due to insufficient disk space." All other GeoWorkspaces can
be saved without this error. These other GeoWorkspaces do not85 1-5RNZQA GeoMedia Professional [GM-4999] Change Feature class
command is not working by selecting
the feature from data window.
Issue exists in 06.01.10.14 and 06.01.04.13, but is a regression from
06.01.02.04. In 06.01.02.04 the behavior is fine. Highlight any single entry
on data window and start the Change Feature Class command. Select the
target feature class, and click OK. An error is displayed instead of changing
the feature class.
How to Reproduce:
1. Start GeoMedia Pro, and then create a blank GeoWorkspace.
2. Make an Access R/W connection to USSampleData.
3. Open a new data window, and add the Rivers feature class to it.
4. Select the first entry in the data window, and then select the Change
Feature Class command
5. Select Interstates as the target feature class, check on both the
options available, and then click OK.
6. Observe that error displayed as “GeomediaCommand Object doesn't
support this property or method”. Click More and observe that
message is “This method/property is not yet implemented.”
86 1-5ROA19 GeoMedia Professional Properties of layout window do not
show correctly when GM Pro
installed on G/Tech installation.
A customer installed GeoMedia Pro 6.1.7 on a system with an existing
G/Technology Designer and Netviewer 9.4.3.1601. He then opened a
layout window and performed a right click in a sheet and selected
Properties. The dialog box opens, but the forms with the information
about different sheets are very small tiles (less than 0.5 cm ).
The customer also tried to run RegGM, Repair GeoMedia Pro, and reinstall
GeoMedia Pro, but the problem remained. This occurs on several
computers (all with G/Technology also installed). Installing on computers
without G/Technology displays the right properties screen.
87 1-5TE255 GeoMedia Professional Missing precision option in Insert >
Carto Grid > Advanced causes
incorrect neat line labels.
How to Reproduce:
1. Open the GeoWorkspace, and restore the connection to the .mdb file.
2. Go to the layout window, and insert a new sheet.
3. Copy a map graphic from one of the existing sheets to the new sheet.
4. Select the map graphic, and select Insert > Cartographic Grid.
5. Click Advanced..., and notice the options on the drop-down list under
Format > Precision are: 1 .1 .12 .123 .12345 .123456 .1234567. Notice
there is no option for 4 digits of precision ('.1234'). Selection of 5 digits
yields 4 digits of precision on output, selection of 6 yields 5, selection
of 7 yields 6, and the user is unable to produce 7 digits of precision.
88 1-5Y72JT GeoMedia Professional Batch Plotting Utility is displaying
"Object variable or With block
variable not set" error.
The Batch Plotting Utility displays an error stating "Object variable or With
block variable not set". If you click OK on the dialog box, the same error
message keeps getting displayed. The only way to get rid of it is to stop the
GeoMedia.exe and BatchPlot.exe in Task Manager.
How to Reproduce:
1. Unzip the attached ‘BP_Issue.rar’ into (C:\BP_Issue) folder.
2. Double click "C:\BP_Issue\BPIssue_Local_Machine.gbp" to open the
Batch Plotting Utility.
3. Select File > Export.
4. Select a folder, and click OK 5.
5. Select *.jpg as the Export type.
6. Select Resolution as 300dpi 7, and click OK. An error displays stating
"Object variable or With block variable not set". User machine
configuration is: GeoMedia Pro: 06.01.06.19, Batch Plotting Utility:
06.01.09.10. (Note: User ‘sproject uses binaries of BP Utility
06.01.09.10 installed on GM Pro 06.01.06.19) User reproduced
problem running GeoMedia Pro 6.1.11.13.
89 1-63WQBD GeoMedia Professional TextFile data server issue When using a textfile connection, any record with an ordinate value of 0 in
the geometry definition returns a null geometry object.
90 1-63Y220 GeoMedia Professional Carriage returns not exported to .dgn
file in GeoMedia Pro 6.1.11.
A user has a GeoWorkspace containing labels with carriage returns. When
this query is exported, as a MicroStation .dgn file, the carriage returns are
not carried over and the text is bunched up. Export to Design file in GM
Pro 6.1.10 handles carriage returns, and results are as expected inside of
MicroStation.
How to Reproduce:
1. Open USSampleData.gws.
2. Select Insert > Label features in: States.
3. Create a three-line layout for label using Ctrl + Enter for a new line,
State_name STAABBRV POP.
4. Output as Query and accept defaults.
5. Observe labels in map window hold three lines of text.
6. Perform a warehouse Export to Design File export format as
MicroStation V8.
7. Choose the label query previously created, and add it to the features
to export.
8. Open the created .dgn, and observe that three-line labels are now
bunched into one line inside of MicroStation.
9. Repeat workflow using GM Pro 6.1.10, and observe that the three-line
label is honored in MicroStation.
91 1-647STH GeoMedia Professional Issue with Insert Area By Face or
Insert Interactive Area by Face
GeoMedia Pro 06.01.10.14 used to keep a history of the previously chose
Insert by Face feature. Now when the customer wants to do another
Insert By Face, the previously chosen feature no longer appears in the
drop-down list. The list is blank, and that feature has to be chosen again.
This is tedious when there are numerous area features. This issue did not
occur in the previous version; it only occurs in GeoMedia Pro 06.01.11.13.
92 1-64QJ05 GeoMedia Professional Layout ‘Insert Legend’ command
crashes if map legend includes an
entry from a closed WMS connection.
If you try to use the Insert Legend command in the layout window for a map that has a legend
entry from a WMS connection, where that WMS connection is closed thus disabling the legend
entry, a crash occurs. This problem has been reproduced using the customer-provided
‘wms_conn_layout_legend.gws’ and a new ‘WMSLayoutLegend2.gws’
created by Huntsville Support using a different WMS connection.
How to Reproduce:
1. Open the ‘WMSLayoutLegend2.gws’. Note that the map window legend contains two legend
entries (Rivers, an active/displayed legend entry from the USSampleData Access connection,
and a user feature, an inactive/disabled legend entry from a WMS connection that has been
closed using the Connections dialog box).
2. In the layout window select the map frame (which contains a map created from the displayed
Map Window display using Insert Map.).
3. From the Insert menu in the Layout Window, select the Insert Legend command. This will
result in the immediate display of a ‘PLayCmdCmd’ error message: “Num: -2147417848 Source:
GeoMediaCommand Desc: Automation error The object invoked has disconnected from its
clients. Procedure: igCommand1_Initialize”.
4. Dismiss the error message with OK, and then click Exit to exit the GeoMedia application. After
selecting Exit an additional ‘PMiscCmd’ error message is displayed: “Error exiting application.
Source:Intergraph Description:Internal application error.”
5. Dismiss this error message with OK, and a ‘Microsoft Visual C++ Runtime Library’ error is
displayed: “Runtime Error! Program: c:\progra~2\geomed~1\Program\GEOMEDIA.EXE This
application has requested the Runtime to terminate it in an unusual way. Please contact the
application's support team for more information.”
93 1-65P7NO GeoMedia Professional Hard-coded string needs to be
extracted for the localization
"Publishing" string displayed on the status bar is hard coded. This string
needs to be localizable.
94 1-6DA5AC GeoMedia Professional Insert Interactive Area By Face fails to
preserve target feature last session
preference (Regression)
GeoMedia Pro 6.1 creates duplicate identical entries in GCoordSystem
table. A new entry is created each time a given image is inserted using
Insert > Georeferenced Images command. This is a regression from GM
Professional 6.0
How to Reproduce:
1. Open USSampleData.gws, select Warehouse > Feature Class
Definition. Export a .csf from the USSampleImage feature class. Exit
GeoMedia.
2. Open a blank .gws. View > GeoWorkspace Coordinate System. Load
the previously saved .csf. Now Warehouse > New Warehouse (name it
test.mdb?). Create an Access connection. If you would like, exit and
save, then inspect the warehouse to ensure that there is a single entry
in the GCoordSystem table. Restart with previously saved .gws.
3. Select Insert > Georeferenced Images. Insert USSampleImage.tif into a
new feature class (test1). Re-select Insert > Georeferenced Images
and insert the image again. Repeat a couple more times, using a new
feature class name each time. Exit and save.
4. Open the test.mdb file in Access, review the GCoordSystem table. You
will see a record for each time you inserted the USSampleImage, each
with a different CSGUID, but with identical coordinate system
properties. Multiple insertions of a single image should not result in
duplicate records.
Customer states:
Reviewing the Access database it was found there were 119 rows in the
coordinate system table. There was one default row and multiple rows of
the exact same CS information. We created a new Access database and
inserted one image with the Georeference image command. Checking the
coordinate system table there are two rows. A default row and a second
95 1-6DRDB9 GeoMedia Professional Using Measure Tool and View
Commands Can Result In Application
Termination. (Regression)
Users working with the Tools Measure Command in conjunction with view
control commands such as Zoom In/Out or Pan can easily get into a
situation where the both the View and Measure commands are nonfunctional.
Use of the commands can only be recovered by exiting and
restarting GeoMedia where the user sees the application crash. The
problem is a regression from 06.00.35.16.
How to Reproduce:
1. Open a GeoWorkspace, and then select Tools > Measure
Distance/Area.
2. Begin measuring a distance (place two or more points in the map
view).
3. Select the View command, then Pan, and pan the view (do not stop
the measure).
4. Click X to close the Measure dialog box.
5. Again start the measure command by selecting Tools > Measure
Distance/Area, and then attempt to measure in the map view.
6. Observe the following error message is posted: “GeoMedia
Professional Error, there are no Mapviews connected to the
EventControl.” The Measure and Pan commands are both nonfunctional
at this point. The only means to recover is to exit the
GeoWorkspace and restart the session.
As you exit you may also see the errors: PMiscCmd Error exiting
application Source:Intergraph Description:Internal application error.
PMiscCmd Error exiting
application.Source:GMCmdSuptDescription:Method '~' of object '~'
failed Microsoft Visual C++ Runtime Library Runtime Error!
Program:..m Files (x86)\GeoMedia
Professional\Program\GeoMedia.exe abnormal program termination.
96 1-6GT3CU GeoMedia Professional Some circles from AutoCAD DWG are
served incorrectly (as half-circles).
Customer has provided an AutoCAD 2000 version DWG containing areas
representing circles (that is, Closed POLYLINE elements consisting of two
arcs that form a circle) where there are three concentric circles
representing a feature. Each circle is a separate element on the same
layer, and the inner circle and the middle circle are served by the AutoCAD
Scanner correctly (so they appear as circles in GeoMedia Pro.). But, the
outer circle is served incorrectly, so it appears as a half circle in GeoMedia
Pro. In addition to the geometry issue, there also appears to be an issue
with the associated coordinate system because when you select the Select
Set Properties command for the feature, an error message is displayed
stating “Unable to display the measurement in General tab. The
measurement cannot be calculated with the given coordinate system
configuration.”
How to Reproduce:
1. Open the .dwg file using AutoCAD or MicroStation V8 so you can see
the original display for the circles. If the file is opened with AutoCAD,
you can use the ‘LIST’ command to identify and display the element
parameters, and if the file is opened in MicroStation, you can use the
‘Element Information’ command to display the element parameters.
2. Open the .csd file in the Define CAD Server Schema File utility, and
correct the paths to the referenced .dwg, .csf, and .ini files as
necessary.
3. Save the .csd file with these changes.
4. Open the .gws with the half circle error and correct the path to the
.csd for the CAD Warehouse Connection if necessary.
Note that the outermost concentric circles in the GeoMedia Pro are
displayed in the map window as half-circles
5. Double click on one of the half-circles to open Select Set Properties.
97 1-6I9H07 GeoMedia Professional Crash occurs with CAD data server
when serving the ‘Default’ level from
V8 design file.
A customer has a V8 design file that is of type 2D ‘taken’ from a 3D design
file, which presumably means he used the File > Export > 2D command in
MicroStation to save the 3D file as 2D. When attempting to serve the 2D
file in GeoMedia Pro using the CAD data server for MicroStation V8, a
crash occurs when attempting to load the Default level. If the Default level
is excluded the design file can be served without error. The Default level
originally contained tag elements, but even if all of the tag elements are
deleted from the design file, the crash still occurs.
How to Reproduce:
1. Create a new blank GeoWorkspace.
2. Select the Display CAD Files command.
3. On the Display CAD Files dialog box, for CAD Type choose
‘MicroStation V8’.
4. In the CAD Files frame Browse to the folder containing the 2D .dgn file;
then in the Available Files list check the 2D .dgn file.
5. Click on the Advanced tab to make it active.
6. Select the option to ‘Create a separate legend entry for each selected
level’, and click OK.
7. When the dialog box appears with the message “Coordinate system
file not specified. Do you want to continue?” appears, click Yes.
8. After creating the legend entries, during the load of the ‘Default’
legend entry, this message is displayed: “An error was encountered
loading data for Default legend entry. Error String - Load Resource
Error Do you want to continue loading remaining legend entries?”.
9. Click Yes. This displays a message box with the title ‘Microsoft Visual
C++ Runtime Library’ title stating “Runtime Error! Program:
C:\Program Files\GeoMedia Professional\Program\GeoMedia.exe.
98 1-6J3YE8 GeoMedia Professional Crash occurs with CAD data server
when serving the ‘Default’ level from
V8 design file.
A customer has a V8 design file that is of type 2D ‘taken’ from a 3D design
file, which presumably means he used the File > Export > 2D command in
MicroStation to save the 3D file as 2D. When attempting to serve the 2D
file in GeoMedia Pro using the CAD data server for MicroStation V8, a
crash occurs when attempting to load the Default level. If the Default level
is excluded the design file can be served without error. The Default level
originally contained tag elements, but even if all of the tag elements are
deleted from the design file, the crash still occurs.
How to Reproduce:
1. Create a new blank GeoWorkspace.
2. Select the Display CAD Files command.
3. On the Display CAD Files dialog box, for CAD Type choose
‘MicroStation V8’.
4. In the CAD Files frame Browse to the folder containing the 2D .dgn file;
then in the Available Files list check the 2D .dgn file.
5. Click on the Advanced tab to make it active.
6. Select the option to ‘Create a separate legend entry for each selected
level’, and click OK.
7. When the dialog box appears with the message “Coordinate system
file not specified. Do you want to continue?” appears, click Yes.
8. After creating the legend entries, during the load of the ‘Default’
legend entry, this message is displayed: “An error was encountered
loading data for Default legend entry. Error String - Load Resource
Error Do you want to continue loading remaining legend entries?”.
9. Click Yes. This displays a message box with the title ‘Microsoft Visual
C++ Runtime Library’ title stating “Runtime Error! Program:
C:\Program Files\GeoMedia Professional\Program\GeoMedia.exe.
99 1-6C8K6J GeoMedia Professional Insert Georeferenced Images
creates duplicate entries in
GCoordSystem table.
GeoMedia Pro 6.1 creates duplicate identical entries in GCoordSystem table. A new entry is
created each time a given image is inserted using Insert > Georeferenced Images command. This
is a regression from GM Professional 6.0
How to Reproduce:
1. Open USSampleData.gws, select Warehouse > Feature Class Definition. Export a .csf from the
USSampleImage feature class. Exit GeoMedia.
2. Open a blank .gws. View > GeoWorkspace Coordinate System. Load the previously saved .csf.
Now Warehouse > New Warehouse (name it test.mdb?). Create an Access connection. If you
would like, exit and save, then inspect the warehouse to ensure that there is a single entry
in the GCoordSystem table. Restart with previously saved .gws.
3. Select Insert > Georeferenced Images. Insert USSampleImage.tif into a new feature class
(test1). Re-select Insert > Georeferenced Images and insert the image again. Repeat a couple
more times, using a new feature class name each time. Exit and save.
4. Open the test.mdb file in Access, review the GCoordSystem table. You will see a record for
each time you inserted the USSampleImage, each with a different CSGUID, but with identical
coordinate system properties. Multiple insertions of a single image should not result in
duplicate records.
Customer states:
Reviewing the Access database it was found there were 119 rows in the coordinate system
table. There was one default row and multiple rows of the exact same CS information. We
created a new Access database and inserted one image with the Georeference image command.
Checking the coordinate system table there are two rows. A default row and a second row
assigned to the image that duplicated the default coordinate system information. We removed
the extra coordinate system rows leaving the default row and the 10 rows assigned to the
images. At this point, the Access database could be opened in the workspace and there were no
issues with the GM custom commands.
100 1-6QRWL9 GeoMedia Professional Incorrect field values retrieved from
the recordset of a
MapViewSelectedObject of a
Thematic LE.
A customer is having issues with a custom command. The custom
command retrieves the user's selected text point geometry by getting it's
associated GeometryObject instance. From this instance, its recordset and
bookmark are obtained. The bookmark is set on the recordset and a value
of one of the record's fields is retrieved. Intermittently, this value is
incorrect - the value is from a different record, not the bookmarked
record. This behavior only happens when the corresponding LegendEntry
has a unique value thematic. If the thematic is removed, the problem goes
away.
101 1-6RZH4O GeoMedia Professional AutoCAD DXF stored area polygons
containing arcs do not display
correctly (invalid geometry).
Customer has supplied an AutoCAD DXF file where the area polygons
containing arcs are not displayed correctly. It appears that the AutoCAD
data server is drawing a zinger from the last point of the polygon to the
last arc (bulge) point. This zinger line does not exist in the source data. If
your run Tools > Validate Geometry, you can see that each of the problem
shapes is returned as "Unclosed area" anomalies. It is believed that the
source .dxf file is valid and should not return invalid geometries. If you
review the various items, you can see a line connects the last point of the
geometry to the last point of the last arc. The same problem is observed if
you use the other .dxf files also. This extra line is not present if reviewing
the .dxf in AutoCAD or in MicroStation.
102 1-6TOYV2 GeoMedia Professional GeoMedia Pro Help F1 - Mistake in
Help Topic Spatial Operators for
Queries.
There is a mistake in the Help F1-Text in GeoMedia‚ Spatial Operators for
Queries topic in English as in German. In the subsection "Entirely Contains/
Entirely Contained by" in the second row on the left, it says "Point 3 is not
entirely contained by area.". It should be "Point 2 is not entirely contained
by area." instead because there is no Point 3 in this example.
103 1-6U59PD GeoMedia Professional GeoMedia Installation Guide States
that If .NET 4.0 is not I\installed, it
will be installed automatically.
The GeoMedia Installation Guide, Overview of GeoMedia Installation
section Before You Install GeoMedia subsection states: Verify that you
have Microsoft .NET Framework Version 4.0 Full Package or higher
installed on your system. When you start setup, if you do not have
Version 4.0, it will be automatically installed before you can start
installation. See Microsoft documentation for more information on
installing and using .NET. This paragraph does not make sense because a)
Although it may be logical that .NET Framework redistributable package
(for server and development), Version 4.0 would be automatically
installed, this is not currently the case, and b) If .NET is automatically
installed, then why see Microsoft for more information on its installation?
104 1-6UIXWF GeoMedia Professional GM Pro crashes creating a select set
with more than 400,00 geometries.
GM Pro crashes creating a select set with approximately 366,000
geometries. Connecting to an Oracle database and displaying 2 features
with 366,642 geometries results in GM crashing. GM is running on a WIN7
machine with 4 quad processors and 12 GB of memory. User can create a
union query of the same feature geometries with no problem.
Oracle connection information:
User/pwd: usstreets/usstreets
Host: gmdb
#
GMDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 129.135.185.38)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = GMDB)
)
)
#
105 1-6Y5853 GeoMedia Professional Use of uniqueidentifier as key column
fails on inserts.
The SQL Server data server should support uniqueidentifers as the primary
key. According to discussion on this issue, the SQL Server data server is
modified so it can now support mapping uniqueidentifier data type to
either gdbGuid (default behavior) or gdbText(38) if the user could
manually modify metadata and modify the mapping (GFieldMapping table)
uniqueidentifier to the gdbText. If so, the user can use this field as
primary key field and can use the default value, for example newid(),
which is a standard function of the MSSQL.
Note that if the metadata is changed so uniqueidentifier is mapped to
gdbText and newid() is used as the default for the field, you can insert new
features in the map view, but cannot insert a new row in the data view.
This is a separate problem. The reason is the properties control calls
AddNew and then asks get_Value for the default values, but the data view
is asking for DefaultValue property and then uses it (it does not work for
server side expressions/functions like newid()). A separate TR/CR could be
filed on the data view on this issue.
Also note the uniqueidentifier field is created externally; such a field
cannot be created through our clients (like the FCD command). In 6.1,
updates and deletes work but inserts fail. So, a change was made since 5.2
that disallows the inserts. In the way notification works, GeoMedia would
need to know the key value at the time of insert. To do that, it would need
to pull a value from NEWID() before inserting a record. The use of this type
of function is critical to SQL Server's implementation in Europe as the use
of uniqueidentifier for key columns is not a requirement for all municipal
GIS data.106 1-6ZM8S8 GeoMedia Professional Subscript out of range when valid
feature class is selected after
selecting an empty feature class.
Subscript is out of range when a valid feature class is selected after
selecting an empty feature class. This issue is reproducible with both IFC
On/Off.
How to Reproduce:
1. Start GeoMedia Pro and make an Access connection to
USSampledata.mdb.
2. Create a new point Feature class, say FC1.
3. Go to the Manage Data tab and select the Apollo Catalog Connection
command.
4. Make an Apollo connection.
5. Click OK on the ERDAS Apollo Catalog Connection dialog box.
6. Start the Explore Apollo Catalog command, and on the ERDAS APOLLO
Catalog Explorer dialog box, select the Base map-drop down list.
7. Select the Cities feature class under the Access connection.
8. Select FC1, and then select Cities again.
9. Observe that the subscript out of range is displayed in the Explorer
view.
107 1-70K8ID GeoMedia Professional Exception seen while showing
metadata of a catalog record.
Observed this while testing with APOLLO 2013 instance.
How to Reproduce:
1. Make an Apollo connection In the Explore APOLLO Catalog command,
click Search for a pass through the query.
2. Observe that 19 results are populated.
3. Select the record with title atl_tiles_1_1.ecw.
4. Right click and select View Index Metadata.
5. Observe the exception below. See the end of this message for details
on using just-in-time (JIT) debugging instead of this dialog box.
6. ************** Exception Text **************
System.NullReferenceException: Object reference not set to an
instance of an object. at
Intergraph.GeoMedia.Apollo.FrmExploreApolloCommand.populateval
ueinIndexMetadata(CatalogItem item) at
Intergraph.GeoMedia.Apollo.FrmExploreApolloCommand.contextMen
uStrip1_ItemClicked(Object sender, ToolStripItemClickedEventArgs e)
at
System.Windows.Forms.ToolStrip.OnItemClicked(ToolStripItemClicked
EventArgs e)
108 1-710O45 GeoMedia Professional Change Label Properties is not
recognizing fence select set of
warehouse appended labels.
The failure of this command appears to be limited to labels in the fence
select set that have been appended to the feature class in the previous
PVT script Under normal conditions, all labels in the select set are
modified, but in this case those labels that have been bulk loaded after the
initial writing of the feature class to the warehouse are not being
recognized for the edit by this command. When the labels are selected
individually for modification by this command, the command works.
109 1-72DDKV GeoMedia Professional Spatial filter not honored by Label
Manager
How to Reproduce:
1. Open a new GeoWorkspace and create a warehouse connection to
USSampleData.mdb
2. Add Interstates to the legend.
3. Enable labeling through Label Manager, and choose any attribute, like
ROUTE_NUMBER in label properties.
4. Click 'Toggle Dynamic' so that labels are displayed.
5. Apply a rectangular spatial filter, and observe that Interstates features
outside the boundary will disappear but labels for them are still
displayed.
Display of labels falling outside the area of interest would be totally
undesirable for anyone deciding to print the map with spatial filter in
place.
110 1-72R343 GeoMedia Professional Named Legend entry does not show
feature or geometry count when
added to legend.
Named Legend entry does not show feature or geometry count when
added to legend. This is a regression from 06.01.11.13.
How to Reproduce:
1. Start GeoMedia Pro and make an Access R/W connection to
USSampledata.mdb.
2. Add the Cities feature class to map window, and name the legend
"Legend1".
3. Delete the Cities legend entry from the legend.
4. Select the Home tab, and then select Legends command.
5. On the Legends dialog box select "Legend1", and the click Replace.
6. Click Yes on the message box displayed, and close the Legends dialog
box.
7. Observe that the legend entry and features are added but no feature
or geometry count is displayed.
8. Right click and select Properties
9. On the Properties dialog box, check the three check boxes available,
and click OK. Observation: Still no count is displayed.
111 1-72R361 GeoMedia Professional Wrong named legend entry icon is
shown for a closed connection.
The wrong named legend entry icon is shown for a closed connection. This
is a regression from 06.01.11.13.
How to Reproduce:
1. Start GeoMedia Pro, and make an Access R/W connection to
USSampledata.mdb.
2. Add the Cities feature class to the map window.
3. Name the legend as "Legend1", delete the Cities legend entry from
legend, and then close the connection.
4. Select the Home tab, and select the Legends command.
5. On the Legends dialog box, select "Legend1", and click Replace.
6. Click Yes on the message box displayed, and close the Legends dialog
box. Observation 1: The Legend entry icon should indeed signify that
the connection is closed, but the wrong icon is displayed here.
112 1-72RI0H GeoMedia Professional A few right mouse menu entries
missing in Legend right mouse menu
after adding named legend
A few right-click menu entries are missing in the Legend right-click menu
after adding a named legend. This is a regression from 06.01.11.13.
How to Reproduce:
1. Start GeoMedia Pro, and make an Access R/W connection to
USSampledata.mdb.
2. Add the Cities feature class to the map window.
3. Name the legend as "Legend1".
4. Delete the Cities legend entry from the legend.
5. Select the Home tab, and select the Legends command.
6. On the Legends dialog box select "Legend1", and click Replace.
7. Click Yes on the message box displayed, and close the Legends dialog
box.
8. Right click in the legend to open the Legend right-click menu.
Observation : A few right-click menu entries like "Fit Legend", "Map
window tooltip", and so forth. are missing in the Legend right-click
menu.
113 1-76IMET GeoMedia Professional ViewDetails.xsl (Stylesheet) installed
as part of GMPro2013 calls a GIF that
is not installed.
The stylesheet C:\Program Files (x86)\Common
Files\Intergraph\GeoMedia\StyleSheets\Catalogs\ViewDetails.xsl is
installed as part of GeoMedia Pro. It contains the following at line 14:
<img src="c:\Program Files\GeoMedia
Professional\StyleSheets\tech_geomedia.gif" height="52" width="234"
alt="To display an image here, please edit your stylesheet to include a
valid path and graphic file name"/>, This graphic file is not installed with
the software; thus when the stylesheet is called by the “View Details”
button of the GM Catalog Explorer, the selected XML file is displayed with
an error at top left saying the file is missing.
114 1-77Q4DT GeoMedia Professional F1 Help on Customize Keyboard
dialog box displays wrong topic.
The F1 Help on the Customize Keyboard dialog box displays the wrong
topic. It should display the topic "Customizing Keyboard Shortcuts" with
Context ID 131429
115 1-7B04D0 GeoMedia Professional Hard-coded strings on Quick Access
Toolbar menu. Need to be
externalized for the localization.
By using the localized GeoMedia.drx, the Quick Access Toolbar menu
shows the English strings. These strings are related to "My Workflow".
116 1-7DDNHX GeoMedia Professional Export to SQL Server incorrectly
creating metadata.sql
The Export to SQL Server command is not creating the metadata.sql file
correctly. The definition for the ModificationLog table is missing the
ModifiedDate field. CREATE TABLE ModificationLog( ModificationNumber
INT PRIMARY KEY IDENTITY, Type TINYINT, ModifiedTableID INT,
KeyValue1 NVARCHAR(255), KeyValue2 NVARCHAR(255), KeyValue3
NVARCHAR(255), KeyValue4 NVARCHAR(255), KeyValue5 NVARCHAR(255),
KeyValue6 NVARCHAR(255) , KeyValue7 NVARCHAR(255), KeyValue8
NVARCHAR(255), KeyValue9 NVARCHAR(255), KeyValue10
NVARCHAR(255), SESSIONID INT DEFAULT @@spid NOT NULL) It should
be: CREATE TABLE ModificationLog( ModificationNumber INT PRIMARY
KEY IDENTITY, Type TINYINT, ModifiedTableID INT, KeyValue1
NVARCHAR(255), KeyValue2 NVARCHAR(255), KeyValue3 NVARCHAR(255),
KeyValue4 NVARCHAR(255), KeyValue5 NVARCHAR(255), KeyValue6
NVARCHAR(255) , KeyValue7 NVARCHAR(255), KeyValue8
NVARCHAR(255), KeyValue9 NVARCHAR(255), KeyValue10
NVARCHAR(255), SESSIONID INT DEFAULT @@spid NOT NULL,
ModifiedDate datetime DEFAULT GETDATE() NOT NULL) ll. This affects 6.1
as well as 2013.
117 1-7EA9EJ GeoMedia Professional KML data server fails to display
features from KML file that works
properly in Google Earth.
A customer has a KML file containing extended data (user data that is
described by a Schema element in the KML file) that displays successfully
in Google Earth and ESRI ArcGIS Explorer, but fails to display in GeoMedia
Pro using the KML data server. The GeoMedia KML data server can
connect to the customer-provided KML file, but when attempting to add
the feature class from the KML file to the legend, an error occurs and the
feature fails to display. The failure appears to be related to the Schema
element that describes the user data because if the Schema element is
deleted from the KML file, the feature class can then be added to the
legend successfully in GeoMedia Pro.
How to Reproduce:
1. Create a new blank GeoWorkspace.
2. Use the New Connection command to create a KML connection to the
‘water_control_valves.kml’ file.
3. Use the Add Legend Entries command to add the ‘Control_Valves’
feature class to the legend. This results in an error message stating:
Error creating a legend entry for Control_Valves Source: GMCmdSupt
Description: Method '~' of object '~' failed Continue with operation?,
and the feature class fails to load to the legend.
118 1-7FH1K2 GeoMedia Professional User Guide contains what appears to
be old fashion strikethroughs.
The Exporting to Shapefile section has many characters that appear to
have strikethroughs and over-types. The characters seem to copy/past
correctly into Notepad, so possibly the odd characters are a font issue.
Possibly the font was not embedded into the .pdf when the file was
created. Problem was noted using Adobe Reader X, version 10.1.5.
119 1-7FGIYY GeoMedia Professional Label Manager not working when
FME 2013 is installed
There is a conflict with FME and GeoMedia 2013 concerning the shared
use of MapText's geolabel technology. Both FME 2013 and GM 2013
embed MapText components. With FME 2013 loaded the Geolabel Label
Manager in GeoMedia 2013 is unable to open. Uninstalling FME 2013 and
repairing the GeoMedia 2013 installation, the Label Manager is able to
open normally
It has been found that this conflict does not affect all machines with
installs of GM 2013 and FME 2013. The conflict and thus the defect is
predicated on the order in which the assemblies are searched by .NET.
MapText support under case number MT4755 has determined the issue is
that the MapText.LabelingSetupGui.dll from the c:\windows\assembly
folder is tried first instead of the local one in the GeoMedia install folder
and this leads to the failure.
MapText has provided a patch resolution to this defect.
120 1-7FL5LI GeoMedia Professional DGNGT2D.ini and DGNGT3D.ini have
incorrect MS resource file
references.(Regression)
The variable for MS resource files defined in DGNGT2D.ini and
DGNGT3d.ini is no longer correct in GeoMedia 2013. The MS resource
riles are defined as: C:\Program Files (x86)\GeoMedia
Professional\Program\Symtrans\FONT.rsc. The path is incorrect and
should be: C:\Program Files (x86)\Intergraph\GeoMedia
Professional\Program\Symtrans\Font.rsc It is believed that this could
affect Export to CAD, Layout Insert Object (for .dgn), and possibly other
areas.
121 1-7FPJQQ GeoMedia Professional Catalog components delivery table
needs correction for location of
scripts
If you look at the section detailing "Software Delivery", in "Working with
Catalogs" and look at the Catalog Components Delivery Table, you can see
that the location for scripts is not correct. References to Oracle Scripts and
SQL Server Scripts should point to their new 2013 location: Oracle Scripts
can now be found at: C:\Program Files (x86)\Common
Files\Intergraph\GeoMedia\Scripts\OracleCatalogScripts MS SQL Scripts
can now be found at: C:\Program Files (x86)\Common
Files\Intergraph\GeoMedia\Scripts\SqlServerCatalogScripts. This may also
bring into question the location of what the section calls the
HOME\Program folder for catalog as 2013 has two program folder
locations: C:\Program Files (x86)\Common
Files\Intergraph\GeoMedia\Program C:\Program Files
(x86)\Intergraph\GeoMedia Professional\Program. For example we also
see that references to style sheets should be changed to: C:\Program Files
(x86)\Common Files\Intergraph\GeoMedia\StyleSheets\Catalogs. It is now
believed by the filer that all file path references in this section are
incorrect for 2013.
122 1-7FPJU4 GeoMedia Professional User Guide corrections needed to
reflect structure/folder changes
introduced by 2013. (Regression)
The following are some of the changes (mostly paths) needed to update the User Guide to
better reflect how 2013 is delivered. This list is not considered to complete.
*** Change to: "The default location for GeoWorkspace templates is ...\Program Files
(x86)\Intergraph\GeoMedia Professional\Templates\GeoWorkspaces.". Existing Statement:
"Then if you want to store the new template in the main templates folder, click the drop-down
arrow and browse to the \Intergraph\Program Files
x86)\<product>\Templates\GeoWorkspaces folder." Change to: "Then if you want to store the
new template in the main templates folder, click the drop-down arrow and browse to the
...\Program Files (x86)\Intergraph\GeoMedia Professional\Templates\GeoWorkspaces." Catalog
(Metadata) Existing Statement: "See the “GeoSpatial Metadata Profile: FGDC Dataset”
document GDCDatasetMetadataProfile.pdf in <HOME>\Program Files
(x86\Intergraph\GeoMedia Professional or \GeoMedia)." Change to: "See the “GeoSpatial
Metadata Profile: FGDC Dataset” document (FGDCDatasetMetadataProfile.pdf in C:\Program
Files
(x86)\Common Files\Intergraph\GeoMedia\Program\resdlls\0009 folder." General Doc Issue
with x86 specifications Need to search entire document and look at "(x86\" and replace with
"(x86)\" Example: Existing: "The default location is <drive:>\Program Files
(x86\Intergraph\GeoMedia\Templates\Layouts." Change to: "The default location is
<drive:>\Program Files (x86)\Intergraph\GeoMedia\Templates\Layouts." Exporting Data to
Other Systems Existing: "This can be done by using the Create Metadata
command in Database Utilities, or by using the CreateGDOSYS.sql script that is delivered in the
\Intergraph\GeoMedia\Program folder." Change to: "This can be done by using the Create
Metadata command in Database Utilities, or by using the CreateGDOSYS.sql script that is
delivered in...”.
123 1-7FYZZ1 GeoMedia Professional Folder name GML3.1.1 is incorrectly
named with double dot GML3..1.1.
(Regression)
C:\Program Files (x86)\Common
Files\Intergraph\GeoMedia\Schemas\GML3..1.1, has a double dot. This is
a regression from the previous version.
124 1-7GA9RM GeoMedia Professional Style Properties, Advanced tab,
Application hang if press <F1> Key for
Help. (Regression)
Apparently, if Help cannot find the Help (.chm) file, the error dialog box
can "fall behind" the style dialog boxes and cannot be accessed. The only
recovery is to use Task Manager to terminate the application. Note there
will also be two GeoMedia.exe processes to terminate. Problem is a
regression from Version 6.1.
How to Reproduce:
1. Open the supplied GeoWorkspace, which references
USSampleData.mdb.
2. Double click on the legend style (point) icon. The Legend Entry
Properties dialog box is displayed.
3. Click Properties on the dialog box. The Style Properties dialog box is
displayed.
4. Click on the Advanced tab, and then press the F1 key.
5. Note the GeoMedia application is now hung. The error dialog box(s)
are present but have "fallen behind" the application and cannot be
accessed. The recovery is to terminate the application using Task
Manager. Afterwards, an extra GeoMedia.exe will be in the Task
Manager also.
125 1-7GA9RW GeoMedia Professional Style Properties, Advanced tab, <F1>
for Help looking for 6.1 Help files
(Regression)
If the user presses the <F1> key to look at Help for the Style Properties,
Advanced grid, Help is not displayed. This is a regression from Version 6.1
behavior. Apparently it is looking for the file "GeoMedia
Professional61.chm" .
How to Reproduce:
1. Open the supplied GeoWorkspace, which references
USSampleData.mdb.
2. Double click on the legend style (point) icon. The Legend Entry
Properties dialog box is displayed.
3. Click Properties on the dialog box. The Style Properties dialog is
displayed.
4. Click on the Advanced tab, and then press the F1 key.
5. Observe that a dialog box is displayed stating: Cannot find file
GeoMedia Professional61.chm. Do you want to try to find this file
yourself?.
Note: If GeoMedia hangs, see the Related CRs section for the related
defect 1-7GA9RM.
126 1-7HK1AB GeoMedia Professional DefParsingRules.exe does not run in
Version 2013. (Regression)
If the user attempts to run C:\Program Files (x86)\Common
Files\Intergraph\GeoMedia\Program\DefParsingRules.exe, the following
error occurs:
--------------------------- DefParsingRules.exe - System Error ------------------------
--- The program can't start because JUTIL.dll is missing from your
computer. Try reinstalling the program to fix this problem. --------------------
------- OK ---------------------------.
This is a regression from the previous version (06.01.11.13) where you can
see that the Define Parsing Rules Utility works.
127 1-7IFDC2 GeoMedia Professional Error when attempt to run Setup.bat
from folder Containing space in name
User downloaded .zip of GeoMedia Essentials from Intergraph's
GeoSpatial Downloads site, and saved the .zip file to C:\GM Essentials.
User extracted/expanded the files to the C:\GM Essentials folder, right
clicked on Setup.bat, and then used the “Run as administrator" option.
The DOS command window appeared with the message:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework
Setup\NDP\v4\Full Install REG_DWORD 0x1. The user also got an error
message titled: C:\GM Windows cannot find 'C:\GM'.
Make sure you type the name correctly, and then try again. If you rename
the folder to not contain the space(s), then Setup.bat works.
128 1-7JE85L GeoMedia Professional Get errors and unable to load label
query from library (Regression)
The supplied Access Library created using Version 2013 references a connection. If you *copy
the objects of this library into a new GeoWorkspace, the objects copy successfully. The Label
query, however, fails to load to the map view. This is a regression from Version 6.1 when
performing the same workflow using the same 2013-created library. *Note: User selects
(checks) all objects available. This seems to be the key to the problem. If the user only selects
the Named Legend, the issue does not occur. When attempting to use the Legend > Legends >
Replace Legend command, you get this error message: An error was encountered loading data
for Labels of SCHEMAA.COUNTIES legend entry. Error getting the GFields object Do you want to
continue loading remaining legend entries? The county labels are not displayed in 2013 but they
are displayed in Version 6.1.11.13.
How to Reproduce:
Note: you may need to configure your TNSNames.ora to see the database.
1. Save Access library attachments to local machine.
2. Create a blank GeoWorkspace.
3. Select Manage Data > Library > New Library Connection.
4. Use Library Organizer to copy the named legend into the blank .gws file.
5. Use the Home tab > Legends > Legends command to replace the current legend, and then
observe the error.
6. Perform the same workflow using Version 6.1, and there are no errors, and the text/labels for
counties display fine. The legend has: a) Label query of County_Names, b) Attribute query for
Interstate 40, c) Buffer Zone of Interstate 40, d) Cities (US Sample based), e) Counties (Us
Sample based), and f) Thematic Legend Entry of Merge of Counties by StateName.
129 1-7JE7WA GeoMedia Professional In RTFText mode, nominal map scale
is changed to match display scale.
When the registry entry is set to RTFText mode and labels are generated
with Generate Static Labels command, the nominal map scale of the map
view that was different from the display scale before running the
command will be matched to display scale. I/Map Editor customers use a
workflow to create different label queries at different display scales by
keeping the nominal map scale constant. This is not possible with the
advanced labeling system in RTFText mode. This restricts them to only use
NativeText mode. When the nominal scale is different between label
queries, a label generated at 2000 nominal map scale will not look right
(displaced) at a nominal map scale of 6000 (set when generating the labels
at display scale of 6000).
The labels are generated at different display scales and their size is
adjusted for those legend entries, such that user can have appropriate size
labels without conflicts at different display scales as the user zooms
in/out. The legend entries are turned on/off by setting them to display by
scale.
130 1-7JRHEQ GeoMedia Professional Legend, right-click menu options
missing if legend created using
Replace Legen
If the user uses the Replace Legend command to replace the map legend,
the following legend commands are missing: Load Data Map Window,
Tooltip Fit by Legend Entry, and Fit Legend. This is a regression from
behavior observed in Version 6.1. These commands are very commonly
used mainstream commands.
How to Reproduce:
1. Open a GeoWorkspace, and make MapWindow1 active.
2. Use Legend group > Legends > Add Legend Entries to add States to the
map view.
3. Use Legend group > Legends > Name Legend to name the legend to
some name.
4. Make MapWindow2 active, and use Legend group > Legends >
Legends command to Replace the current legend.
5. Right click on the MapWindow2 legend, and review the menu options
available. Compare to the legend Right-click menu options available
for MapWindow1. Observations: The legend created using the Named
Legend does not have the options available. The missing right-click
menu options include: Load Data Map Window, Tooltip Fit by Legend
Entry, and Fit Legend. *Note: These options are missing even if the
user right clicks on top of an existing legend entry vs. right clicking in a
"blank space" of the legend. This issue was noted while migrating map
legends from one GeoWorkspace to another using the Library System
and then using the Replace Legend command to review the results.
131 1-7JRHRU GeoMedia Professional GeoMedia Installation Guide needs
more information in Configure
License section.
The GeoMedia Installation Guide.pdf needs additional information and
associated graphics to better show users how to configure their license. In
fact the current statements are incorrect. Currently the steps in the guide
state: 1. Click Next on the Configuration Wizard Welcome screen. 2. Click
Configure License on the next Wizard dialog box. 3. Select the Concurrent
licensing method, click Specify License Servers, and type your license
server information. Then click Close. OR Select the Nodelocked licensing
method option, type or select your Host ID and, type the License folder,
and then click Close.
Step 3 needs more explanations and graphic examples for both methods.
Something similar to: To configure your license using the Concurrent
method, an existing license server can be specified. This can be done by a)
Selecting the Concurrent Licensing Method option, b) Clicking on the
Specify License Server option., or c) On the Specify License Servers dialog,
specify the license server either by address or DNS name (@server name).
Syntax: PORT@LICENSE_SERVER_NAME [Show example graphic here]
where the port number is optional, depending on the configuration of the
license server. For more information on configuration of the license server
can be found at: http://support.intergraph.com/Licensing.asp To
configure using the Nodelocked option: a) Select the Nodelocked Licensing
Method option., b) Use the composite Host ID displayed, with your License
Authentication Code (LAC) to generate your license at
http://www.intergraph.com/sgi/license, or c) Copy your license file to the
path specified in the License folders field.132 1-7J7VUK GeoMedia Professional Turn Dynamic Labeling state to off
when user deletes the
'DynamicLabels' legend entry.
Currently the Toggle Dynamic Label command works in an On/Off toggle
state where a single legend entry (DynamicLabels) is produced in the
active map window when the command state is set to 'On'. When the
command is set to 'Off', the legend entry is removed. The user can turn off
dynamic labels by navigating to the Labels tab and depressing the Toggle
Dynamic command button. This may not be the most intuitive approach
that users will take.
133 1-7J8MAB GeoMedia Professional Quick Access Toolbar location is
always on the top of ribbon bar for
new session.
How to Reproduce:
1. Start GM Pro and create a new GeoWorkspace.
2. Right click in ribbon bar area and select Show Quick Access
Toolbar(QAT) below the Ribbon. Quick Access Toolbar is moved below
the ribbon bar.
3. Exit the GeoWorkspace with/without saving
4. Start GM Pro again and notice the Quick Access Toolbar is below the
toolbar as GM starts and moves to the top of the ribbon bar as soon as
the new Quick Access Toolbar /select Quick Access Toolbar dialog box
is displayed.
5. Create a GeoWorkspace and notice that the Quick Access Toolbar is on
the top of the ribbon bar. The user has to again right click and select
the entry to move it below the ribbon bar. The user does not have to
do this every time a new GM window is opened
134 1-7KLBKH GeoMedia Professional Browse button for .lsf file goes to
Documents folder instead of path
already in there
How to Reproduce:
1. From Label Manager, bring up label properties for any point feature
layer.
2. Check 'Label with symbol' check box.
3. By default 'Fixed' is selected and path for symbol file has - "C:\Program
Files (x86)\Common
Files\Intergraph\GeoMedia\Program\Symbols\shields.lsf".
4. Click on Browse button.
Notice that it will go to Documents folder with the 'File Name' set to
"C:\Program Files (x86)\Common
Files\Intergraph\GeoMedia\Program\Symbols\shields.lsf". You might only
see the last section ("mbols\shields.lsf") of the path. Should it browse to
the folder where the shields.lsf file was so users can select another lsf file?
135 1-7MITKL GeoMedia Professional Only showing connections in the
Display Labels dialog that contain
labeling outputs
The current dialog box displays all connections in the GeoWorkspace. It
should only display connections that are relevant for this command.
136 1-7NB5QJ GeoMedia Professional GWM MapSvr.exe instance crashes
with no error and creates black maps
until service restart.
The customer is experiencing problems with their custom GWM based Tile
map server, where strange things happen to MapSvr.exe, no log, no error
message:
The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
This is msg we've got during debuG session.
We have 12 license GWMs and whenever this error happened to any of 12 running instances,
this instance starts to create pure black maps from this moment until GWM restart, and it
seems that there is no way to reset only this instance back to any useful state.
As this problem occurs under tile server, it creates a lot of black tiles on screen, because this
MapSvr.exe instance is captured again and again (as valid) by tile server.
Changing output type, load another mss, call Clear, reload library connections will not help.
Restart of whole GWM is very time consuming and TMS creates a heavy load....so best the
option is to solve this problem or kill/reset this instance only. We suspected the problem might
be related to either data or map symbolic (very complex) in legend, because this error occurs
again and again when user ask the same map tile (same spatial filter). We have approx. 20 :
30,000 ratio bad to good tiles. Error repeats on same places, but when we display a critical
location with same spatial filter and same legend in GM Pro, everything works OK, so data and
map symbolic is probably OK.
Our production tms server starts under a heavy load as our users start to use our application
that load maps from it.. The problem has been determined to be in the RL
OffsetGeometryFactory.
137 1-7NF2I3 GeoMedia Professional Different results when extracting
coordinate systems from raster files
using RGR (6.1.x vs. 2013).
If you export an MFM File as a GeoTIFF on 6.1.3, the coordinate system in
the GeoTIFF file passes a “IsEssentiallyIdentical” check when comparing to
the coordinate system of the study area on which it originated.
“IsEssentiallyIdentical” now returns false in this case on GM 2013.
138 1-7NV11X GeoMedia Professional Invocation of GM Pro Application
takes nearly one minute.
GM Pro Application invocation takes almost 50 seconds to 1 minute. This
is the time for the Welcome dialog to appear on the screen.
139 1-7OGUGA GeoMedia Professional License not found message always
appears when starting custom app
with map view control.
The customer has a VB6 custom application built on Version 13. He has the
GeoMedia product. Whenever the custom application is started, he always
receives a message stating that the license was not found and to select
concurrent or nodelocked license. The customer has a Nodelocked license
-- not a concurrent license.
Once the Nodelocked license is selected, the program runs. All license
files and paths, etc. are properly defined.
The problem seems to be that the map view control is expecting a
GeoMedia_Objects license in addition to the GeoMedia license, and this
should not be required. This is a regression.
If the user runs the GM GUI with only the GeoMedia license, it runs fine.
140 1-7P0MKU GeoMedia Professional German GeoMedia Pro 2013 - range
thematic and unique value thematic
are mixed up.
The region reports that legend entry properties of German GeoMedia Pro
2013 range thematic (Thematische Bereiche) and unique value thematic
(Eindeutige Werte) are mixed up. Selecting "Eindeutige Werte" starts
"Thematische Bereiche" and vice versa.
141 1-6XJ1X7 GeoMedia Professional Delivered catalog SQL Server script is
not working with SQL Server 2012.
Delivered catalog SQL Server script is not working with SQL Server 2012.
How to Reproduce:
1. Create catalog users.
2. Execute delivered SQL Server catalog script for above user.
Observation: Script failed with errors.
SQL Server catalog scripts (which are delivered with Setup) need to be
modified to support SQL Server 2012.
142 1-6YFFK1 GeoMedia Professional "Object variable " error with Insert
Interactive Area by Face command
There is an "Object variable " error with Insert Interactive Area by Face
command. How to Reproduce:
1. Start GeoMedia, and make an Access connection to USSampledata.
2. Add the States features to the map window.
3. Select any States feature, and start Insert Interactive Area by Face.
4. Select the States feature from the dockable control.
5. Press the Esc key. The command is exited.
6. Again start Insert Interactive Area by Face, and click in map window.
Observations : Following error is displayed:
---------------------------
GeoMedia Professional
---------------------------
91
GeoMediaCommand
Object variable or With block variable not set
---------------------------
OK
143 1-736MKD GeoMedia Professional Fields are disappearing on “Labeling
Option” dialog box after pressing the
“Enter” button.
Fields are disappearing on “Labeling Option” dialog box after pressing the
“Enter” button.
How to Reproduce:
1. Start GeoMedia Pro and open a GeoWorkspace.
2. Go to Labeling tab and start the “Labeling Options” command.
3. Make changes on any field on “Leader Styles” or “Stacking” tabs from
“Labeling Options” dialog box, and press Enter.
Observation: Fields on “Leader Styles”/“Stacking” tabs are disappearing
from the dialog box.
144 1-73OP6B GeoMedia Professional DefSymFile, Warehouse Config File,
and DefTFD utilities do not work after
install/uninstall of GMO.
How to Reproduce:
1. Install the following GM products in the following order: GeoMedia
Pro, GeoMedia, GeoMedia Viewer, and GeoMedia Objects.
2. After installation, try starting the following utilities from the Start
menu: Define Symbol File, Define Text File Definition, and Define
Warehouse Configuration File.
Observation: Starting Define Text File Definition displays the error:
---------------------------
DefTFD1.exe - System Error
---------------------------
The program cannot start because CFCacheName.dll is missing from the
computer.
145 1-77I3RR GeoMedia Professional SI-1605: Problem with display if issue
zoom during draw (Regression)
When working with large datasets (several large feature class tables
displayed), if you zoom in or zoom out during a draw (the map view is
being updated), then the resulting display is garbled with features
displayed at different scales.
The user can recover the view by maximizing then restoring of the map
view.
How to Reproduce:
1. Open the GeoWorkspace that references data on the server.
2. Allow the data to display and complete the draw.
3. Select Zoom In, but do not zoom in yet.
4. Select FIT.
5. As the data begins to draw, issue 2 or 3 clicks in the map view, and
allow the data to continue drawing.
Observation: The data will be displayed incorrectly with features displayed
at two different scales at least.
146 1-7EUGXF GeoMedia Professional Scripts folder not delivered As referenced by the GeoMedia's User Guide, p. 789, "Oracle DBA‘s can
use the CreateGDOSYS.sql script in the ..GeoMedia Professional/Scripts
folder to manually create the GDOSYS schema."
This folder is not delivered in the GeoMedia 2013 release.
Scripts are now in the C:\program files\common
files\intergraph\geomedia\scripts folder
147 1-7EWWT5 GeoMedia Professional Command tooltips have disappeared
(machine-specific regression).
After loading GeoMedia Pro 2013, command tooltips for both the map and
layout window commands do not display. The issue is machine specific
and has been reported by two separate Service Requests, both internal.
The troubling point is that so far no resolution has been found to correct
the issue, including the complete removal of the application, cleaning of
registry, and subsequent reload; the problem persists. Reproducing the
problem probably requires remote desktop access to one or both of the
machines reporting the issue.
148 1-7HIKJT GeoMedia Professional Generate Static Labels creates a
feature class with FSM extension that
has no known purpose.
A customer filed an SR asking the following question regarding the new
Labeling commands in GeoMedia Pro 2013:
“When I create Static Label using Generate Static Command in Labeling
Tab, 3 things are created (TXT, FSM, and LDR). I understood TXT means
text, LDR means Leaderline, but what does FSM mean? Does it mean
GeoMedia Feature Symbol file?”
None of these feature class extensions are mentioned in the GeoMedia
Labeling User Guide delivered with GeoMedia Pro and there is no Help
topic for the Generate Static Labels command. Note that in all of
Generate Static Label results that were observed, the feature class with
the FSM extension has had 0 geometries, so it is not clear whether this
feature class is actually used for any purpose (at least in the context of
GeoMedia).
149 1-7HIKQZ GeoMedia Professional Customer asks how to create .lsf
symbol files in GeoMedia for use with
Labeling.
A customer asked the following question regarding the new Labeling
commands in GeoMedia Pro 2013:
“When creating label with a symbol, the extension of the symbol file is lsf.
Can I create lsf files like a .fsm file created by layout window? Or how can I
create a symbol?”
The only mention of this symbol format/extension in the delivered
documentation is an entry in the GeoMedia Labeling User Guide for the
Label Properties dialog box that states "GeoMedia Labeling comes with a
default symbol repository (install_folder\Common
Files\Intergraph\GeoMedia\Program\Symbols\shields.lsf), but you can
select any compatible symbol file with the .lsf extension."
There is no further discussion about what constitutes a compatible symbol
file with a .lsf extension or where such a symbol is created/obtained.
I posed this question to product planning who provided the following
additional information:
“The .lsf file - label symbol file, is a text file that is delivered with the
product that instructs the software how to prioritize and color the symbol
fonts that are used for symbols. In the original GeoLabel Pro
documentation, there was a statement that read 'If you want more info
on the .lsf format, contact MapText'. Because we are delivering at least
one or more .lsf files, this indicates that it is a supported symbol format. If
that is the case, some explanation of the purpose of a .lsf file, its format,
and the means required to create or obtain additional .lsf symbols is
necessary in the documentation.
150 1-7HK1AJ GeoMedia Professional Find Address dialog box problems in
2013 (Regression)
The Find Address dialog box has some very odd behaviors and difficulty in
use in version 2013.
a) It cannot be resized, which makes fields cut off or difficult to read.
b) It is not properly designed/formed (looks bad) with text cut to the edge
of the dialog box.
c) It can "fall behind" / disappear by clicking on some other application
such as Notepad.
All of these issues are regressions from the previous version (06.01.11.13).
The problems observed are in the new standard ribbon interface.
151 1-7OF3WF GeoMedia Professional Loading the Software on a 64-bit
Operating System - section is
incorrect.
The Loading the Software on a 64-bit Operating System Installation Guide
section is incorrect for the 2013 release as it references locations and
registry entries that are no longer used.
152 1-7PAPNX GeoMedia Professional REGRESSION > Wrong language in the
legend context menu when regional
settings = English(US)
With GeoMedia Pro, when both English and French are installed, and
when French is the selected language, the context menu of the legend is:
- in French if the regional settings are "Français (France)"
- in English if the regional settings are "Anglais (Etats-Unis))"
There is no problem with the map context menu. Localization has verified
this error.
153 1-7PQTUJ GeoMedia Professional Hurricane model in IMAGINE 2013
crashes after GeoMedia MR1 is
installed.
How to Reproduce:
1. Install IMAGINE 2013, GeoMedia Pro, and GeoMedia Objects.
2. Select IMAGINE-> File-> New-> Spatial Model Editor.
3. Select File-> Open->Open Spatial Model->.
4. Open Hurricane model.
5. Alternative for step 3: Add and connect Vector Input operator and
Preview into the Spatial Modeler; in Vector Input add a point data
from USSampleData.mdb.
6. Click Preview on Spatial modeler tab: "Observe that IMAGINE stops
working (Crashes)" Note: 1) After Uninstalling GeoMedia Pro the issue
is also found. 2) After repairing IMAGINE the issue can also be found
154 1-6JLFBB GeoMedia Professional Selection of MicroStation V8 cells for
use as Symbol Style crashes
GeoMedia Pro.
Attempting to specify certain MicroStation V8 as a Symbol Style on the
Style Properties dialog box causes a crash of GeoMedia Pro. These same
cells can be served successfully using the CAD Data Server. Likewise the
customer reports that Bentley has reviewed the cells and states that they
are correct. Support has also confirmed that the ‘VerifyDGN’ MDL
command in MicroStation reports no errors for the customer’s .cel file, so
presumably the cells are valid.
How to Reproduce:
2. Open USSampleData.gws or another GeoWorkspace with a point
feature class displayed on the legend.
3. Right click on Cities (or another point feature) in the legend, and select
the Style Properties command.
4. On the Style Properties dialog, select ‘MicroStation V8 Cell Files’ from
the Type drop-down list.
5. For the Source, browse to the location of the .cel file and select it.
6. From the Name drop-down list, select the cell entry. This will
immediately result in an error message titled ‘GeoMedia’ that includes
the message “GeoMedia has stopped working A problem caused the
program to stop working correctly. Windows will close the program
and notify you if a solution is available.”, with buttons named ‘Debug’
and ‘Close Program’.
155 1-75D1EL GeoMedia Professional Resizable dockable controls
dynamically grown when other
dockable controls are displayed
This is only a problem in ribbon mode. If a resizable dockable control is
visible and another dockable control is displayed or resized
programmatically, it causes the resizable dockable control to grow a small
amount horizontally and vertically. This is evident when the GeoMedia
Grid Study Area list is displayed and another dockable control is displayed
(say, Insert Feature command dockable control). This CR also affects
GeoMedia Grid.
This problem does not seem to affect the Bing and Pictometry command
dockable controls. They are implemented in CSharp. User suggests
checking the Queued Edit control, but it has been temporarily disabled
from growing because it will crash GeoMedia if resized or undocked. User
is not aware of any other GeoMedia dockable controls that are resizable.
156 1-7JA3F3 GeoMedia Professional Label Manager workflow for defining
feature class to be labeled and
expression is very inefficient.
To generate labels using the new GeoMedia Pro 2013 Labeling commands, the user must first
use the 'Label Manager' command to identify which feature classes will have labels and define
an expression for the labels for those feature classes. To accomplish this task the 'Label
Manager' dialog box presents a list of feature classes (labeled Layer Name' in the dialog
box) with a corresponding column named 'Label' with a checkbox. To identify which feature
classes will have labels created the user must place a check in the checkbox of the Label column
for the feature class. However an expression for the label placement for each feature class must
also be defined which requires use of the Label Properties dialog box.
Currently the workflow for performing these two required steps (defining the expression and
identifying the feature class to be labeled) is very inefficient and frustrating. The current
workflow is described below.
Current inefficient workflow (using USSampleData):
1. Select the 'Label Manager' command.
2. On the 'Label Manager' dialog box, click on the checkbox in the Label column for the States
feature class (a.k.a. Layer Name). A checkmark was expected to have been placed, but instead a
message box is displayed stating "The text expression needs to be specified before a layer can
be labeled. Please specify the expression by clicking the "Properties…" button."
3. Dismiss the message box with the OK button
4. Click the 'Properties...' button to open the 'Label Properties' dialog box, then use the Text
field drop-down to choose an attribute name for the label such as 'STATE_NAME'. Then click the
OK button to exit the dialog box and save the changes to the dialog box.
5. The Label checkbox for States is still unchecked, so click on it again to
check it (failure to do so means that no label will be placed for States).
6. Click OK to exit the Label Manager dialog box.
157 1-7FQRQ9 GeoMedia Professional ABS Symbology is rendered
incorrectly in GeoMedia
2013.
Attribute-based styles created in GeoMedia 6.1 are rendered incorrectly in
GeoMedia 2013. How to Reproduce:
1. Launch GeoMedia/GeoMedia Pro and establish an Access warehouse connection to
SampleABSUKData.mdb.
2. Establish a Library connection to SampleABSUKLibrary.mdb.
3. Using Library Organizer, transfer all styles from SampleABSUKLibrary.mdb to the
GeoWorkspace.
4. Add all feature classes from SampleABSUKData.mdb to a map window.
5. Fit Map Window by any legend entry.
6. Zoom to a display scale of 1:2500 as ABS style is not displayed until < 1:5000.
7. Observe the difference of the ABS between GeoMedia 06.01.11 and 13.0.
Also, compare .png files.
158 1-5A2HUH GeoMedia Professional Hot fix installation
overwrites AppPath entries in registry
If the user installs GM hot fix 6.1.7.16 or later (probably earlier as well), the setup
will erase all entries at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Paths\GeoMedia.exe, and the setup will simply insert the GeoMedia entry. This causes any
other GM-dependent applications to become broken.
159 1-7OUK5Z GeoMedia Professional Insert Georeferenced Image
command shifts GeoTIFFs referenced
with US Survey Feet.
How to Reproduce:
1. Start GeoMedia and open a blank GeoWorkspace.
2. Use View > GeoWorkspace Coordinate System to load "project.csf" from the data set.
3. Create New Warehouse from normal.mdt.
4. Use Insert >Georeferenced Images to insert "1.tif" using Automatic
(GeoTIFF) mode.
5. Use the dialog box to create a new feature and add it to the legend.
6. Zoom way in on upper-left corner and note the upper left corner of
the image is misplaced by about 1.5' in X and 2.75' in Y.
Problem appears to happen with images georeferenced with US Survey
Feet, not metrics.
Problem does not occur in 6.1.11.13 release.
Problem does not occur if the user inserts the image using the accompanying world file.
Problem does not occur if the user manually creates a new image feature between steps 3 and 4.
This change in behavior prevents OrthoPro customers from importing orthos properly for
processing. There is no workaround as OrthoPro always reads the GeoTIFF tag first and does not
let the user force the use of the world files.
160 85674_GM GeoMedia Professional Sorting Data View columns breaks
queue navigation.
When Queued Edit displays the queue in a data window, and you select a data window column
header then right click the header to sort, queue navigation becomes unreliable. Selecting a row
in the data window will initially select the row, and then navigate to a new row. Clicking the
Previous and Next buttons on the Queued Edit control does not work reliably either. It seems
Queued Edit is using the key-value of the newly selected row to select the data window row
that would have had the selected row before the sort.
You can see this problem by opening USSampleData, queuing States, and sorting a column
Descending (anything that changes the order the keys are displayed in).
User thinks Queued Edit keeps track of the keys in the order they are displayed and does not
know that the data window has changed them. If you use Queued Edit to sort the records, this
problem does not happen, which implies this is a Framework notification limitation.
Unfortunately, more GeoMedia users know about data window's sort than Queued Edit's sort,
which is hidden on a drop-down menu under a button on the dockable control.
Now that Queued Edit is part of the Core products, this may be more of an issue because
GeoMedia users will not be trained on Queued Edit as much as GM Fusion users.
161 87322_GM GeoMedia Professional When a Halo style is applied to Arabic
text the characters are split apart.
When a Text Style that includes a Halo is applied to Arabic text, the text string is broken apart so
that each character is separate with a halo around each individual character. This results in
incorrect Arabic text strings because some characters are formed by combining characters, so
breaking them apart changes the meaning. To see the problem, open the
Arabic_Halo61_CharacterSplit.gws that has an Access connection to Arabic.mdb, and note the
difference in appearance for the text without a halo and the same text below it with a halo. The
font applied to the Text Style is Arial Unicode, but the problem occurs with all Arabic fonts the
user tried.
This is a companion TR to 86408 as the customer mentioned both the left-to-right issue when
using a halo as mentioned in that TR, and the splitting of the characters when the halo is applied
as reported in this TR.
162 87474_GM GeoMedia Professional Warehouse > Output to GeoTIFF -
incorrect .tfw file
How to Reproduce:
1. Open a new GeoWorkspace, connect to world.mdb, verify geographic WGS84, and place
'country' feature class on the legend.
2. Use Insert > Interactive Image to place an image without GeoTIFF tags interactively. The user
placed it in Mexico, but anywhere on the map works (fails).
3. Select Warehouse > Output to GeoTIFF.
4. Create a file in a known location on disk.
5. Turn display off on the inserted interactive image, and Insert > Georeferenced Image with the
newly created GeoTIFF (use world file georeferencing).
The new image will display with its origin at the correct location, but will be flipped about a
horizontal line.
If you examine the world file, you should see something like this:
0.000512580387270
0.000000000000000
0.000000000000000
0.000512580387270
-105.975372649008210
27.264821322449013
Obviously, GeoMedia is forgetting to write the Y scale value with a negative sign, which is
required in this case.
163 1-4MSZ6P GeoMedia Professional Incorrect results with Edit Geometry if
editing locatable join features
(Regression from 6.0)
If you edit a feature class with a Join of the same feature class displayed, you get a "double
edit". The problem does not occur in Version 6.0. For example, when you edit a locatable
feature and a join to the same feature with maintain coincidence enabled, then move the
existing vertex, the distance of the resulting move is twice the distance issued by the user.
How to Reproduce:
1. Set up supplied data with a feature class and a join of the feature class displayed. Maintain
coincidence is enabled. Both the feature class and the Join are locatable.
2. Move a vertex using Edit Geometry, and observe the result is incorrect.
3. If you make the Join Unlocatable, or turn off Maintain coincidence, the problem does not
occur.
This problem does not occur in GMP 6.0.
164 1-4QTUP1 GeoMedia Professional Unique thematic problems with text
data containing commas
A German customer has found that if the text attribute data contains a comma, the results of a
Unique Thematic classification are incorrect. The problem occurs when the Regional and
Language Options are set to German (Germany).
How to Reproduce:
1. Use Control Panel, Regional and Language Options to set your Standards and formats
preference to German (Germany).
2. Open a blank GeoWorkspace.
3. Open a warehouse connection to thematic_with_komma.mdb.
4. Define a thematic legend entry for feature class “Biotop”.
5. Use “Unique Value Thematic”.
6. Select Attribute “Bezeichnung” in the “Classification” field.
7. Select the checkbox for “Other” entries.
8. In the “Count” field there are “0” objects for “Others”.
9. Click “OK” and load the legend entry into the map.
There is one element in "Other". This element includes a comma "," in the column.
This problem does not occur if the Regional and Language settings are set to English. The
problem occurs in both Versions 06.00 and 06.01.
165 1-4RXMB1 GeoMedia Professional Cannot use VPF data as served up by
the VPF Data Server
There is a problem with VPF Data Server serving certain VPF polygons within GeoMedia. The
faces should be served as one merged polygon geometry, but they are served as individual face
feature instances instead.
Further customer information:
The VPF Data Server serves up the VPF data unsuitable for use in production. The problem is
with features in VPF defined using join tables, particularly area features. A single area feature
can be composed of several faces. In GeoMedia, the area geometry is a Geometry Collection
made up of several polygons, one for each of the faces. When displayed in GeoMedia, the
boundaries of each face are displayed for the feature. The COMPASS program has indicated this
is a problem, and DCAFE will have the same problem, particularly when we want to symbolize
the feature for a hard-copy chart.
The ideal solution would be to convert the geometry collection into a single polygon. User has
been unable to find any existing GM functionality that will do this. The VPF Data Server gave a
fix to test and it worked exactly as wanted, but it broke further VPF Processing. The ideal route
would be to use the VPF Data Server's fix and get it to work correctly downstream with the VPF
export software. If not, perhaps Digital Cartographer could come up with a command that fixes
the area features.
166 1-4TMTNV GeoMedia Professional Queued Edit: Sort in data window not
honored
If you perform a Queued Edit and display a data window for the queue and then do a sort in the
data window and select a row in data window, the queued edit jumps to a different feature
from the selected feature.
How to Reproduce:
1. Open a queued edit for States in USSampleData.gws; the queued edit map window and a data
window are opened.
2. In data window select a second row (Arizona); Arizona is also selected in the map window
and the queued edit map window.
3. Do a sort ascending in the data window on POP: the second row is now Wyoming.
4. Click on the second row (Wyoming) in data window: all the windows (map window, Queued
Edit map window, and data window) jump to Arizona instead or some state other than
Wyoming.
167 1-4ULDBT GeoMedia Professional Style Renderer - Text Patterned Line -
spacing varies as map window is
rotated.
How to Reproduce:
1. Open the provided GeoWorkspace, and restore a connection to the provided .mdb file.
2. Note that the left map window has had a 90-degree rotation applied. The red dots maintain
their spacing regardless of rotation angle in the map window, but the text pattern undergoes
some rescaling - the actual characters are spaced farther apart at a 90-degreesrotation than
they are at 0 degrees.
3. The right window shows an unrotated line: change the Map View display properties so that
the view has a 90-degree rotation and see the same problem.
The font does not seem to be a factor, and predefined symbols used to pattern the line do not
exhibit the error. This was seen in 6.1.4 and 6.1.5.
168 1-4UOJUM GeoMedia Professional When reading VPF data, the geometry
for area features is including the
geometry for all edge features.
Using VPF DATA SERVER 06.01.00.01:
When reading VPF data, the geometry for area features is including the geometry for all edge
features contained within.
The edge primitives for the area and linear features are contained within the same EDG tables.
All edges with the same left or right face ID are being added to the geometry of the area;
however, edges that have the same containing face to the left and to the right should not be
included.
How to Reproduce:
1. Create a GeoWorkspace.
2. Connect to the new warehouse ..VPF then
..."293232584\projects\DNC\Backup\vpfout2\dnc23\gen23".
3. Add the hyd_hydline and also the hyd_hydarea features.
4. Turn the display off on the hyd_hydline feature, and click on the upper left Area feature (the
Polygon) and do a Geometry Information.
5. Look at the Geometry Information for the Line in the middle, which GM is calling a “HOLE”.
6. Note that the line in the middle is a “HOLE” but displays as a Polygon Geometry. How can this
be a hole based on the X and Y of the 4 points for the “hole” when in reality it is a line? If there
were any difference in the Z value, it could be a “hole”.
169 1-4UTKGB GeoMedia Professional Data window for Queued Edit issue
when sorting
Using the Queued Edit Data Window on the Queued Tool bar, the selected ID is not being
recognized; the software seems to jump to another ID.
Software used:
GM Pro 06.01.05.19
GM Fusion 06.01.00.08
How to Reproduce:
1. Create a blank GeoWorkspace .
2. Connect to a warehouse that has a feature class you know will generate anomalies when
running the Advanced Geometric Validation, Validate Geometry tool within GM Fusion.
3. Execute Advanced Geometric Validation, then Validate Geometry.
4. If the Queue Edit Tool bar is not displayed, make it active.
5. Select the proper queue based on the feature you ran on.
6. In the Queue Edit Data Window, select the AnomalyDescription column; then right click to
bring up the right-click menu, and choose Sort Descending or Ascending.
7. Select a line (a record/row) by using your down arrow on your key board, or choose it with
your mouse on the Queued Edit Data Window, and then click on the record/row below, and
note that the record clicked on is not the one that shows up (for example, selected 3607 and it
returned 1076).
Note: The user found that if you bring up a Window > New Data Window to view the Queued
Edit results, this problem appears.
170 1-4WCOBD GeoMedia Professional Problem selecting a specific record in
the Queued Edit Data Window
The following problem has been observed when sorting a column in a Queued Edit Data
Window other than ID (User selected the US Sample STATES feature class FIPS column and
sorted by ascending).
When the third row is selected, the active record jumps to ID= 3 instead of remaining on the 3rd
row. This does not occur in the data window when selected from Windows; it only happens with
the Queued Edit Data Window:
In the Queued edit Data Window, if you sort the grid in another column that is not ID, and select
the third line, GeoMedia selects the feature that has the value of ID=3. The user did the test on
the USSample data.
171 1-4ZS085 GeoMedia Professional Orient to geometry does not work for
points in a compound feature class.
This is a regression and occurs in GM Professional 6.1.2.4.
If a compound feature is placed as a point with rotation, then if Insert Label is run, and the label
is placed with the Orient to geometry option, the label will not be rotated. This works correctly
for a regular point type feature.
How to Reproduce:
1. Open the "301951981_TextJoinLabeling.gws", and correct the path to
"20100210_TextJoinLabeling.mdb".
2. Insert several "Textgeometrie" feature class instances using "Place at angle" or "Rotate
dynamically", populating the name attribute value with several characters.
3. Run Insert Label on the "Textgeometrie" feature class, making sure to select "Orient to
geometry" placement.
4. Click OK to create the query.
The labels are not oriented to the "Textgeometrie" feature class based on its rotation.
This workflow works using point geometry.
172 1-50PXI5 GeoMedia Professional GM Professional crashes on trying to
display image of a thematic legend
entry created on image footprint.
This CR is not a regression from GM Professional 06010619 setup.
How to Reproduce:
1. Start GM Professional 06.01.07.10, and open USSampleData.gws delivered with setup.
2. Using the Insert Georeferenced Image command, create an image feature class named ‘Test’,
and select USSampleImage.tif. Do not add a legend entry for the feature class. Run the
command.
3. Select Analysis > Image Footprints, create an image footprint on the georeferenced image
viz., USSampleData\Test, and then display the footprints in the map window.
4. Select Image footprints of Test in the map window, and select View > Display Selected
Images.
The image is displayed without any issues.
5. In the legend window, select ‘Image footprints of Test’, and create a Unique Value Thematic
on the ImageName attribute.
6. Select the Image footprints of Test in the legend window, and move it to the top.
7. Select the sub-thematic legend entry in the map window, and select View > Display Selected
Images.
Observation: The GeoMedia application crashes immediately.
173 1-51XX9M GeoMedia Professional Define Symbol File fails to open V8.cel
file (with crash or error message).
The Define Symbol File utility is unable to open the V8 cell file named 'ba13_v8.cel' that was
provided by the customer. The cell file appears to be valid as it can be opened successfully in
MicroStation V8 (either directly as a design file or as an attached cell library), and when the
'verifydgn verify' mdl command is run in MicroStation V8, no errors are reported for
'ba13_v8.cel'. Likewise the same .cel file can be used successfully to define a Symbol Style for a
point feature in GeoMedia Professional through the Style Properties dialog box.
The customer reports that when attempting to open the .cel file with the Define Symbol File
utility in the localized German version of GeoMedia Professional 06.01.6.19, the utility crashes,
while in English GeoMedia Professional 06.01.07.16 a 'Define Symbol File' error message is
displayed stating "Unable to open Symbol library %s".
In tests with GeoMedia Professional 06.01.07.16, the "Unable to open Symbol library %s" was
also seen, but on the first attempt to add the 'ba13_v8.cel' file, the following message was
displayed first:
Warning
---------------------------
Critical (): File C:\DataSets\1-305375687_Ulirch_Haugg\ba13_v8.cel is not a valid MicroStation
file and cannot be translated.
After dismissing this message with the OK button the "Unable to open Symbol library %s"
message is then displayed.
How to Reproduce:
1. Start the 'Define Symbol File' utility.
2. Click the Add button.
3. Browse to the folder containing the 'ba13_v8.cel' file, and change the Files of Type filter on
the 'Add From File' browse dialog box to 'MicroStation V8 Cell File (*.cel/*.dgn)' so that the
'ba13_v8.cel' file is visible; then select the file, and click Open.
4. If this is the first time you have attempted to add the 'ba13_v8.cel', you will see the Warning
message above, and after dismissing this message, you will see the "Unable to open Symbol
Library" error on subsequent attempts to add the .cel file.174 1-5JNJU2 GeoMedia Professional Scale bar length does not match on
initial map window display.
How to Reproduce:
1. Open the provided 619de_uha61_1280x1024_LOC.gws in GM Professional.
2. Measure the length of the scale bar. On the user’s machine, configured 1280 X 1024
resolution; the scale bar measures ~2800km long. It should measure 2000km.
3. Open the same GeoWorkspace through a remote desktop connection. The user’s remote
desktop connection had a resolution of 1024X768. The length of the scale bar measured
~1600km. It should have measured 2000km.
In both cases, if you zoom in then out (or out then in), the scale bar is redrawn at the correct
size.
The customer feels the scale bar should display initially at the correct scale for the device on
which it is displayed.
175 1-5LMAIZ GeoMedia Professional Citrix client - growing list of printers in
Layout Print command dialog box
Using GeoMedia through the XenApp client plugin, each time a new user connects to the server
and runs a workflow involving the layout window Print command, the list of available printers
grows. For example, if you have 4 users accessing GeoMedia through the Citrix server, user 4
will have more printers listed in the Layout/Print dialog box than users 1-3. User 3 would have
more printers listed in the Layout/Print dialog box than users 1 and 2, and so forth. The more
users accessing the Citrix server simultaneously, the more apparent the problem becomes.
Selection of a printer from another client usually leads to a series of PLayCmdCmd errors,
resulting in a nonfunctioning Print Layout Window command.
176 1-5TIZK6 GeoMedia Professional [GM-5044] Problem Inserting ECW
Images on Win7 x64 Systems
A user supplied .image files that show ECW images do not consistently insert into the image
warehouse on a Win7 x64 systems. After selecting Insert on the Insert Georeferenced Image
dialog box, the process hangs and the GeoWorkspace session must be terminated. The image
feature class is not created. Occasionally (and for no apparent reason so far), the Insert on the
Win7, 64-bit system will work. The process seems to work on 32-bit systems even if they are
Windows7.
How to Reproduce:
1. On Win7 x64 system, open \\fileserver\TRdata\GeoMedia\pgsmith\1-
5TIZK6\GeoWorkspaces\Example1.gws file.
2. Select Insert > Georeferenced Images.
3. Set the Folder option to: \\fileserver\TRdata\GeoMedia\pgsmith\1-5TIZK6\Images.
4. Set the Coordinate system to the supplied EPSG25832.csf.
5. Change the extension to *.ecw.
6. Select >>.
The .ecw Images are added to Selected files column on the right side of the dialog box.
7. Key in an output feature class name.
8. Click OK.
Observation: 9 times out of 10, the Insert dialog box hangs, and the GeoMedia application must
be terminated by Task Manager to recover.
177 1-5WHZN1 GeoMedia Professional Press Enter does not save values
modified in 3D Settings Tab of Style
Properties dialog box.
How to Reproduce:
1. Select any Legend Entry of Area feature type for which 'Boundary Options'' Style Property in
not applied.
2. Right click and select Style Properties.
3. Go to the 3D Settings tab.
4. Check the 'Boundary options' check box,
5. Select the ‘Extrude' and 'Use extrusion of' option buttons.
6. Change 'Use Extrusion of' drop-down field by selecting some parameter, or type some
constant value.
7. Press Enter on the keyboard.
8. Open the 'Style Properties' '3D Settings' tab again, and check that changes like selecting
'Boundary options' check box, 'Extrude' and 'Use extrusion of' option button are saved, but the
changes in 'Use extrusion of' field value is not saved.
Note: This can also be seen in 'case of Use offset of:' field
178 1-5Y7217 GeoMedia Professional GeoMedia crashes using raster data
in the 3D map window after using the
navigation tools.
This CR was a result of verifying CR 1-5NODB9, which stated GM crashes when converting from
a 2D to a 3D map window. GM does not crash now when converting from a 2D to a 3D map
window but does crash once in the 3D map window, and using the navigation tools several
times like zoom in/out , tilt, and pan for anywhere from a minute to five minutes.
Using the customer's data set, GM crashes when using the navigation tools several times, like
zoom in/out , tilt, and pan the3D map window when raster data is displayed in the 3D window.
If the display of the raster data is turned off in the 3D map window, the crash does not occur.
This can be reproduced on WINXP 32-bit and WIN7 64-bit machines.
How to Reproduce:
1. Edit the "Bodenflächendaten.ini" file .csf path.
2. Edit the image files path under the Warehouse drop-down menu.
3. Open hydro.gws, and correct the warehouse connection paths.
4. Convert the 2D map window to a 3D map window.
5. Use the navigation tools several times, like zoom in/out , tilt, and pan for anywhere from a
minute to five minutes, and GM will crash.
6. Open hydro.gws again, turn the display off for the raster data, and convert the 2D map
window to a 3D map window. GM does not crash.
179 1-5YHWQH GeoMedia Professional Measure Angle dynamic text
disappears when used in a 3D map
window.
If the Measure Angle command is run while in a tilted view of a 3D map window, the text for the
angle measurement will disappear as the arc is moved away from the operator.
180 1-5Z9T7A GeoMedia Professional Help topics need to updated for SQL
Server Spatial Data Server,
The following are help topic contents needing update to support SQL Server Spatial DS:
• Help topic needs update for the Database Utilities to cover SQL Server Spatial Data Server.
• Help topic needs update for the Export to SQL Server command according to modifications in
the command.
181 1-6079IV GeoMedia Professional Tooltips for numeric default values
show as a negative value.
In Attribute Properties, if you hover over a Value field that has a default assigned, a tooltip pops
up showing you the data type and the default value. For numeric types like int, longint, single, or
double, the default number is shown as a negative number even though it is really a positive
number.
182 1-62SW1Y GeoMedia Professional [GM-756] Sorting in the Queued Edit
Data Window itself does not update
queue.
When a queue result is open in the Queued Edit Data Window using Data > Sort Ascending or
Descending, it does not update the Queued Edit Window with the record. When the additional
commands are used from the Queued Edit dialog box and Sort Ascending or Descending on a
particular field is used, the Queued Edit Map Window is updated with the proper record.
How to Reproduce:
1. Open USSampleData.gws.
2. Select Tools > Queued Edit to open any queue.
3. With the field selected (ID), select Data > Sort Descending, and observe that Queued Edit Map
Window is not updated with record.
4. Use Queued Edit Window Additional Commands > Sort descending (ID), and observe that the
Queued Edit Map Window is updated with the record.
183 1-630TNE GeoMedia Professional Seemingly valid WFS-T 2.0.0 service is
seen as read-only.
All feature classes from a WFS-T 2.0.0 are treated as read-only, even though the Capabilities
document returned seems to have everything in order. The Transaction operation is present and
the ImplementsTransactionalWFS constraint is set to true. Because in Version 2.0.0 of the OGC
WFS specification, there is no mention on how to declare aparticular feature types editable (as
in Version 1.1.0, which supplied the FeatureTypeList/Operations and FeatureType/Operations
elements).
This issue prevents GeoMedia Professional from manipulating features served by SDI Pro WFS in
Version 2.0.0.
184 1-65P7MI GeoMedia Professional Need to extract the hard-coded string
for localization.
The string "Exporting" displayed in the Status bar is hard coded. This string needs to be
extracted in the res file for localization.
185 1-6AZMPP GeoMedia Professional GML data server returns incorrectly
and gives misleading error messages
regarding coordinate system failure.
A customer provided a set of four version 3.2. GML files that have the SRSName defined as
‘urn:ogc:def:crs:EPSG:2065’.
When connecting to any of these GML files with the GML data server in GeoMedia Professional,
an error message is displayed stating “Coordinate System File urnogcdefcrsEPSG2065.csf not
found in <host product>/EPSG or current folder for feature class : VymennyFormat”, and the
connection will fail.
The message indicates that the failure occurs because the GML data server expects to find a
coordinate system file named urnogcdefcrsEPSG2065.csf in the EPSG folder.
However, this is not the case as the data server is actually looking for a coordinate system file
named EPSG2065.csf.
How to Reproduce:
1. Unzip the contents of the customer-provided ‘CUZK.ZIP’, ensuring that the folder structure is
maintained when the files are extracted. This file includes the four GML files (with a .xml suffix)
in the data subfolder along with coordinate systems file named urnogcdefcrsEPSG2065.csf and
EPSG2065.csf.
2. Start GeoMedia Professional, and create a blank GeoWorkspace.
3. Choose the New Connection command, and for the GML files, select one of the .xml files in
the CUZK\vzorky-dat-vfr-20120309\data subfolder of the location where the zip file was
extracted; then click the OK on the Connection dialog box.
This will result in a connection failure with the error message: “Coordinate System File
urnogcdefcrsEPSG2065.csf not found in <host product>/EPSG or current folder for feature class
: VymennyFormat”.
4. Based on this error message, copy the urnogcdefcrsEPSG2065.csf from the zip file to the
C:\Program Files\GeoMedia Professional\Program\EPSG folder.
5. Use the Connections command to try to open the GML Connection again. Note that the same
error message is displayed.
186 1-6B1DI7 GeoMedia Professional Minor change to wording concerning
Bing Maps Key
In the sections "Before Using this Command" (in reference to use of Bing Maps) the following
are suggested changes:
From:
"To obtain Bing Maps keys, you have to create a Bing Maps Developer Account at the Bing Maps
Accounts Center. https://www.bingmapsportal.com."
To:
"To obtain a Bing Maps key, you must first create a Bing Maps Account at the Bing Maps
Accounts Center https://www.bingmapsportal.com."
The use of the word "developer" is not accurate for our customer base.
Post Note: Intergraph has recently added to its price book the ability to sell Bing Maps Keys in
blocks of 5 keys that are device specific. Considering this price book entry, maybe the text in
the User’s Guide should be changed to something such as:
Bing Maps keys can be purchased from Intergraph or from Microsoft at the Bing Maps Accounts
Center https://www.bingmapsportal.com. For further details, contact your Intergraph sales
representative, or visit this Microsoft Web site for Getting a Bing Maps Key
http://msdn.microsoft.com/en-us/library/ff428642.aspx.
187 1-6B1DIG GeoMedia Professional Question concerning Bird's Eye View
statement
In the User Guide, there is a note statement in the Bing Maps section concerning Birds Eye View
(Oblique Aerial Photos). The statement says:
"NOTE Bird‘s Eye View is not available to Public Sector customers within the U.S. and Canada."
This statement seems to be incorrect. According to http://en.wikipedia.org/wiki/Bing_Maps,
Bird’s Eye View is "..available in selected locations across the globe, including major cities in the
United States, Canada, and Japan and in over 80 European locations."
It is suggested that we modify the statement to some generic statement or some statement
similar to that given above by Wikipedia.
188 1-6EL5CQ GeoMedia Professional WMS Legend entry does not load. Saved WMS legend entries may not load upon reopening of the GeoWorkspace document. The
following message will appear:
GeoMedia Professional
An error was encountered loading data for
[WMS Feature Name Here] legend entry.
Do you want to continue loading remaining legend entries?
If you right click on the WMS legend entry, and select Load Data, you get the following message:
GeoMedia Professional
Unable to display data.
At least one selected legend entry is invalid.
Oddly, the user must delete the legend entry(s) and add to the legend again to see the entries.
Creating a GDOWMS.log file in the users $TEMP$ folder shows the following when the failure
occurs:
GRecordsetSourceInterfaceGDOXML::OpenSourcecstrSrcStrNOCSFFOUND=FAIL;
How to Reproduce:
1. Open .gws file and observe this error:
An error was encountered loading data for
[WMS Feature Name Here] legend entry.
Do you want to continue loading remaining legend entries?
2. Delete the WMS Legend entry and use Legend > Add Legend Entries to add it again, and
notice how the same feature is valid. If you now exit and reopen the GeoWorkspace, the same
error may or may not occur.
189 1-6EVADB GeoMedia Professional Regression: Unique thematic legend
differentiates capital and lower case
at first classification.
When a user creates a unique thematic legend based on an text attribute that has initial
characters both capital and lower case (for example, Grass, and grass), the user sees two
separate classes on the 'Add Thematic Legend Entry' (Legend Entry Properties) dialog box, each
of which contains only those instances of the case-specific type. The dialog box is case sensitive.
This was not the case in Version 6.0 - all instances went to a single class.
The thematic legend entry produced contains two classes, but they both contain all the same
instances.
In GM Professional Version 6.0, the Add Thematic Legend Entry dialog box only finds one
separate class - it is not case sensitive.
190 1-6HFPU2 GeoMedia Professional WebMap crashes when responding to
intensive usage of a WFS Service.
Intensive usage of a WebMap Publisher application that contains a WFS Service crashes
WebMap. The errors are written to the Event Log, very large mapsvr.exe memory usage, and
the last line of the WebMap log files are:
Fri Jun 29 08:28:50 2012(12.430532) - Publisher: WebServicesUtilities: GetLegendEntry : EXIT
Fri Jun 29 08:28:50 2012(12.430609) - WFSUtil: OpenRS : Opening Recordset
191 1-6SSRU0 GeoMedia Professional Need a statement of version of WCS
Service supported for WCS data server
Connecting to a WCS Warehouse section of the User Guide needs to be clear that GeoMedia
supports the display of data from OGC WCS Version 1.0 sites. The current wording seems to
imply that you try to specify some other version.
Current wording:
If you do not specify a version parameter, the data server issues the request with version 1.0.0.
If the WCS does not support this version, the connection fails and an error is presented as:
"Version negotiation failed. The WCS does not support the versions supported by the data
server (1.0.0)."
This is a very wordy way to say:
"GeoMedia only supports the display of data from OGC WCS Version 1.0.0 sites."
192 1-6UZDXE GeoMedia Professional Error when editing point style
property
The user has a GeoWorkspace containing a legend and when attempting to access the style
properties for some of the point symbols, this error is displayed: Initialization of style
properties control GMStylCtl.GMSymbolStyle failed. Invalid use of Null
GWS attached to SR 1-413435511
Enter the Legend|Styles, and then select the AuxEquip properties. You will then get the error
message. The style does display but you cannot get into the properties.
193 1-6WCJ97 GeoMedia Professional Unable to differentiate Toggle
Dynamic ON or OFF state.
Unable to differentiate Toggle Dynamic ON or OFF state. This is ribbon specific.
How to Reproduce:
1. Start GeoMedia Professional.
2. Select the Labeling tab.
3. Do some Label Manager operations, and then click Toggle Dynamic.
Observations: Cannot differentiate if the button is ON or OFF.
194 1-6XX5WH GeoMedia Professional LWArchive.exe (utility delivered with
GM) does not create toolbars when
layout window is active.
After running LWArchived.exe, the Archived Commands toolbar is not accessible when the
layout window is active. The toolbars for layout window (Place, Edit, Nudge, Align, etc.) have
been disabled, so looking for the Archived Commands toolbar in ribbon mode will never work.
In classic mode this toolbar is not present. It appears that the LWArchived.exe utility is not
preforming as expected.
195 1-70TKFZ GeoMedia Professional Define Coordinate System File utility
crashes after clicking OK.
The Define Coordinate System File utility crashes after clicking OK. This is regression from
06.01.11.13
How to Reproduce:
1. Start the Define Coordinate System File utility.
2. Click OK on the Define Coordinate System File dialog box.
3. Click Cancel on the Save as dialog box.
4. Again click OK on the Define Coordinate System File dialog box.
Observations: Define Coordinate System File utility crashes.
196 1-722721 GeoMedia Professional Connections pertinent to GM Pro are
available in GM and GMV too if all are
installed on the same machine.
This is a regression from GM Professional 6.1.11.
How to Reproduce:
1. Install these products in the following order:
a) GeoMedia Viewer
b) GeoMedia
c) GeoMedia Professional
2. Start GM Professional, GM, and GM Viewer with blank GeoWorkspaces.
3. Open the New Connection dialog box in all the three products.
Observations: All the Connection types listed in GeoMedia Professional are available and in
GeoMedia and GeoMedia Viewer too.
GeoMedia should have a subset of connection types of GeoMedia Professional, and GeoMedia
Viewer will have more, lesser connection types available.
197 1-7379Q9 GeoMedia Professional GM Viewer Start menu lists GM
Viewer Installation Guide instead of
composite GM Installation Guide.
The GM Viewer Start menu User Documentation lists the legacy "GM Viewer Installation Guide",
not the new composite "GM Installation Guide". When selected for display, an error message is
displayed.
198 1-74CHL5 GeoMedia Professional The Supported Environments doc is
incorrect.
• Oracle 10G express is based on 10.2.0.1 and is not supported. Oracle 11G Express is current
and supported.
• SQL Server Express 12 is not mentioned.
• CITRIX XenApp is Version 6.0 not 5.0, but there has been no testing on QA's XenApp Server.
199 1-76FMO0 GeoMedia Professional Regression: Insert > Georeferenced
Images fails to select proper
georeferencing mode, and produces
error
A customer's ECW file contains tie point information and an invalid EPSG code (32767). The new
functionality (in GM Professional 2013) 'automatically' attempts to use "Other with internal
coordinate system" georeferencing, then fails with the error:
++++++++++
GeoMedia Professional
! Error using raster properties service
GeoMedia
Position information cannot be automatically determined for the specified file.
+++++++++++++
GM Professional framework needs to validate that the EPSG CS information is valid before
switching the georeferencing mode from 'internal' (6.1 default behavior) to 'external'.
A workaround is to manually select the "Other with external coordinate system" georeferencing
mode and provide the correct .csf file.
200 1-79XETT GeoMedia Professional References to EPSOM codes should
be changed to EPSG code.
In the section titled "Exploring ERDAS APOLLO Catalogs", the text needs to change from:
… “In addition, it displays spatial search parameters (the bounding box extent and the EPSOM
code)…
To:
… “In addition, it displays spatial search parameters (the bounding box extent and the EPSG
code)…
201 1-79XRHK GeoMedia Professional Custom Keyboard shortcuts do not
work.
Custom Keyboard shortcuts do not work. Default shortcuts work and custom keyboard
shortcuts work in the classic mode but not in the ribbon mode.
202 1-7FYC0D GeoMedia Professional GeoMedia application hangs when
creating WMS connection to DEMIS
site.
Delivery and Connection
Prerequisites Section is incorrect and needs to be changed to reflect the 2013 release.
203 1-7HCEYU GeoMedia Professional GeoMedia application hangs when
creating WMS connection to DEMIS
site
If you attempt a WMS connection to the following WMS site, GeoMedia will hang. The only
recovery is to use Task Manager to terminate the application. Problem occurs in GeoMedia
06.01.11.13 and 2013.
URL: http://www2.demis.nl/worldmap/wms.asp?request=GetCapabilities&version=1.0.0
The same URL does return capabilities when issued in Internet Explorer.
How to Reproduce:
1. Create a blank GeoWorkspace file.
2. Use Warehouse > New Connection to create a WMS connection using URL:
http://www2.demis.nl/worldmap/wms.asp?request=GetCapabilities&version=1.0.0
Observation: The application hangs. The GDOWMS.log file states:
4:09:28 PM 2/15/2013 -
GRecordsetSourceInterfaceGDOXML::OpenSourcecstrSrcStrNOCSFFOUND=FAIL;URI=http://www
2.demis.nl/worldmap/wms.asp?request=GetCapabilities&version=1.0.0;FORMAT=image/png;
4:09:28 PM 2/15/2013 - GRecordsetSourceInterfaceGDOXML::LoadDataFromURL
[GET][OPERATION-GETCAPABILITIES]
4:09:28 PM 2/15/2013 - GRecordsetSourceInterfaceGDOXML::LoadDataFromURL [GET QUERY
POSTED] =
http://www2.demis.nl/worldmap/wms.asp?request=GetCapabilities&version=1.0.0&SERVICE=W
MS
4:09:31 PM 2/15/2013 - GRecordsetSourceInterfaceGDOXML::LoadDataFromURL [STATUS] -
SUCCESS
Regardless, the application should not hang.
204 1-7JK74N GeoMedia Professional Attribute query date field comparison
returns incorrect results when
GeoMedia Parser is used.
Customer has an attribute query, DATE_Field1 > DATE_Field2, that works fine (returns results) if
applied/queried directly on the originating feature class (Access or Oracle).
If the same query is applied to a Spatial Reference Feature of the same feature class, the query
fails to return any results. The query also fails to return any results if applied to any query of the
originating feature class.
It is presumed that the problem here may be that the GeoMedia Parser is failing to parse the
syntax correctly, or the given syntax for the DATE field comparison is incorrect. It should be
pointed out that all queries work when performing similar comparisons using data types of
LONG and DOUBLE. For example LONG_Field1 < LONG_Field2 query returns records whereas
DATE_Field1 < DATE_Field2 fails to return records (when query on Spatial Reference or Query
on Query).
Development Questions:
1. Is it true that GeoMedia Parser is being employed when attribute query is applied to:
- Spatial Reference Features?
- Other queries?
2. Does the GeoMedia Parser support date field comparisons using <greater than> or <less
than> operators? If yes, what is the proper syntax?
How to Reproduce:
1. Save .zip to C:\Warehouses folder and use WinZip's Extract to here.
2. Open C:\Warehouses\1-7JK74N\Example.gws
3. Notice the query "Inbetrieb_kl_Schadensdatum" has some 776 records returned. This query
comparing two date fields is applied to the originating feature class.
4. Notice how the query "Ref_Inbetrieb_kl_Schadensdatum" has 0 records returned. This is
same query applied on a Spatial Reference Feature of the same feature class. The user expected
the query to work, especially because it does work if the field types for comparison are of some
numeric type such as LONG or DOUBLE.
205 1-7JQV2D GeoMedia Professional Quick Access Toolbar (QAT) does not
preserve I/Map Editor commands
between sessions.
How to Reproduce:
1. Open a new GeoWorkspace, and add I/Map Editor commands to the Quick Access Toolbar
(QAT).
2. Exit the GeoWorkspace with or without saving it.
3. Bring up a new GeoWorkspace again, and notice that QAT does not have the I/Map Editor
commands that were added in the last session.
User tried adding the commands to QAT using the Customize QAT dialog box and also by right
clicking on a command and selecting 'Add to QAT'.
For GM Professional commands, it works fine. The problem is only with I/Map Editor
commands. I/Map Editor commands in My Workflow are preserved but not in QAT.
206 1-7K1Y0K GeoMedia Professional Edit Geometry can hang GeoMedia
application with Updating Display
flashing in prompt field.
Customers have reported an issue where the Edit Geometry command can hang while editing.
For example, the user clicks to move a vertex and the application hangs with a flashing status
prompt that says: "Updating Display". Recovery is to use Task Manager to terminate the
GeoMedia application.
How to Reproduce:
1. Open a GeoWorkspace correcting path to the data.
2. Ensure that the Maintain Coincidence digitizing option is enabled.
3. Select a geometry.
4. Select Edit Geometry.
5. Move a vertex.
6. Undo the move vertex.
7. Select another geometry.
8. Move a vertex.
9. Right click Undo.
10. Select a specific geometry, select Edit > Identify Vertex.
207 1-7L7PSN GeoMedia Professional Labeling dialog boxes need to honor
Windows regional settings.
The labeling dialog box font size field is hard coded to use '.' as the decimal separator (for
example, "9.0"). The default decimal separator for some languages, such as Spanish, German,
and French, is a comma ','. This causes the font size to be broken for European languages. If you
change the period to a decimal, the labeling dialog box interprets the number as multiplied by
1000, that is, if you type "9,0", the dialog box appears to interpret it as “9,000”. The dialog box
needs to be changed to interpret the separator based on Windows regional settings.
208 1-7M09UH GeoMedia Professional VMAP2i - Lost features in GeoMedia
when displaying VMAP2i data using
VPF data server
When displaying VMAP2i data in GeoMedia using a VPF data server, some features of
iwa_watrcrsl feature disappear. The same feature can be displayed in ArcMap and VPF View.
The problem is related to the VPF Data Server.
GI Toolkit 6.1.4.34
GMDC 6.1.3.20
VPF Data Server 06.01.00.04 + EP
209 1-7MN6W4 GeoMedia Professional Supported Environments document
Says .NET 4.0 is auto-installed by
Setup.
The GeoMedia Supported Environments document lists .Net 4.0 as "R-A". If we look at the key
for R-A, we see it indicates that:
R = Required and A = Automatically Installed by Setup.
It has been observed that running Setup.exe does not install .Net 4.0, so the listing of
"automatically installed" is incorrect for the document.
210 1-7N7A3B GeoMedia Professional Requesting support for anti-aliasing in
map to improve rendering of linear
and areal geometries
In an oversize overweight solution, a custom command uses GeoMedia Professional to generate
Google-like map tiles by capturing multiple snapshots of what is rendered in the map window.
The linear and areal features currently being rendered in the map window look jagged. The
customers have requested we have support for anti-aliasing or other means to improve
rendering of these geometry features.
211 1-7OMOOF GeoMedia Professional Ribbon-based GeoMedia places Close
button on dockable controls,
Ribbon mode GeoMedia keeps putting an X in the dockable control title bar. Note that the
UserControl property is set to False, which according to the documentation states that the X
should be missing from the title bar.
212 1-7OZ2RL GeoMedia Professional Map window (and data window)
clients cannot set position of the
window to an appropriate location.
Works fine in cassic mode, but is broken in the ribbon mode.
GeoMedia ribbon framework code is interpreting the values passed in to the map window
put_Top and put_Left functions as coordinates relative to the origin of the application main
frame client space. However, the map window is actually owned by the application main frame
window’s MDIClient window; GM should be interpreting the values passed in to the put_Top
and put_Left functions as coordinates relative to the origin of the MDIClient window’s client
space.
To illustrate the problem easily, you (as a map window client) can simply get the Top property,
set the returned value back to the Top property, then get the Top property again. Observe that
the Top property now returns a different value. In fact, even setting any of the position or size
properties also changes the others.
This has broken ImageStation PixelQue and is expected to break ImageStation Stereo for
GeoMedia as well. Any application that needs to position map windows or data windows will be
broken by this.
Workaround: None
Note this is a regression. The previous version of GM (based on the non-ribbon framework) did
not exhibit this problem. The exact same functionality was present and it is now broken.
Therefore, this is a regression and not a bug in new functionality.
213 1-7P06D5 GeoMedia Professional The Oracle LTT data server appears in
Connection dialog box when Oracle is
not installed on the machine.
The changes to handle the COM extraction issue using Common Setup on a 64-bit build machine
caused this regression.
214 1-7PS7E5 GeoMedia Professional Label Manager fails to produce labels.
Error message not useful in recovery.
How to Reproduce:
1. Start a new GeoWorkspace.
2. Make a new connection to Tiles.MDB in the attachments.
3. Display the legend entry by type: unique value thematic.
a) Classify by attribute: size.
b) Do not assign colors.
c) Assign widths 0.709 to 3.500.
d) Add a " to the end of all labels.
4. Click Classify and then OK.
5. Open Label Manager, select the first item, and then click Properties.
6. Use the expression: Size +"\" " + Type + "(" + Year +")".
7. Click OK.
8. Click the "Label" checkbox for TileNetwork (should select all sub-items); then click OK.
Observe error: Failed to perform label placement: CFG_PARSE_ERROR. Failed to dynamically
label the map.
215 1-7PXHAT GeoMedia Professional Fit All does not update label
placement.
How to Reproduce:
1. Start a new GeoWorkspace.
2. Connect to Tiles.mdb (attached).
3. Display all the features classes in the map window.
4. Run Label Manager.
5. Click Properties, and then set text to: Type.
6. Click OK.
7. Click the label checkbox, and then click OK.
8. Zoom in on the lower-right features.
9. Click Fit All.
10. Observe that labels are only drawn in the lower right with a strange font size/spacing.
216 1-7R09VS GeoMedia Professional PAFMSvc_dll.dll is not being removed, The PAFMSvc_dll.dll is not being removed after uninstalling GeoMedia Professional with
GeoMedia PublicWorks.
How to Reproduce:
1. Run GeoMedia Common Setup.
2. Select GeoMedia Desktop Products and expand the tree.
3. Select GeoMedia/GeoMedia Professional.
4. Click Install.
5. From the 'Custom Setup' - Select the Program features you want to install.
6. Expand the GeoMedia Professional sub-tree, and select 'GeoMedia Parcel Manager' for
installing.
7. Install the products.
8. After the products are installed, uninstall through the Common Setup
9. Observe: The following file is left behind: C:\Program Files (x86)\Common
Files\Intergraph\GeoMedia\Program\PAFMSvc_dll.dll.
217 1-7RKNUQ GeoMedia Professional Error displayed when trying to
compose text
GM 13.00.01 Release Phase testing Failure "Adhoc Testing"
This is regression from Bld242-GM2013. Issue is reproducible with both IFC OFF and ON.
Decompose a text and try to compose it and error is displayed.
How to Reproduce:
1. Start GM Professional, and create a blank GeoWorkspace.
2. Make an Access R-W connection to USSampleData delivered with the product.
3. Add States LE to the map window.
4. Select Labeling > Label Manager; then click Properties.
5. Click Expression, select State Name, and then click OK.
6. Select the Label checkbox, and then click OK.
7. Select Generate Static from Labeling tab, then select the Warehouse option.
8. Type the output name as TESTLABEL, and then click OK.
9. Select West Virginia text, and then click Decompose.
10. Verify that text is decomposed.
11. Select West and Virginia, which are in decomposed state, and then click Compose.
Observation: Error displayed as:
“GeoMedia
---------------------------
Failed to finish execution of this tool because of an unexpected error.
The given bookmark is either bad or not created by this server (or this version of the server).
---------------------------
OK“
218 1-7RKO4R GeoMedia Professional Crash to desktop when printing large
paper size (A1) with WMS data source
failure
How to Reproduce.
1. Open a GeoWorkspace with only a WMS data source. (https://secure.geowms.my.bl.ch ; user:
BL00000066 ; pswd: Andrea!)
2. Switch to the layout window.
3. Print a layout sheet A1 (size A1).
Error message appears; GeoMedia exits to desktop.
Testing indicates that this plot can succeed if the resolution of the device is lowered to 300 dpi
or lower.
Following the workflow above, the user plotted the A1 sheet to PrimoPDF, CutePDF, and
AdobePDF drivers at 300 dpi without error. Smaller sheets plot successfully at 600 dpi.
It appears that the 'Print Quality' slider is having no effect on the output plots - the output PDF
files are the same size regardless of the Print Quality setting. This should not be the case, but
that may be a different CR-Defect.
Customer was informed of this workaround (lowering dpi of the device). They suggest the
software should not crash to desktop at 600 dpi.
Testing on v.13 replicated the error. Plots at 300 dpi are fine; 600 dpi crashes without an error
message.
219 1-7RPK11 GeoMedia Professional Cannot copy feature or split feature
when it has dynamic label and
Attribute Properties enabled
When a feature such as a point feature (USSample Cities) has a Dynamic Label displayed, the
user will be unable to use the Copy Feature command to copy a feature. Attempting to copy will
result in the error: Update or CancelUpdate without AddNew or Edit.
The problem seems to occur when the digitizing option (Display Properties) is enabled. The
problem also occurs for the Split Feature command.
How to Reproduce:
1. Open a GeoWorkspace and correct path to data (USSampleData as needed).
2. Cites and Labels for Cities should be displayed.
3. Ensure the Display Attribute Properties digitizing option is enabled.
4. Use the Vector > Copy command to copy a city.
Observation: Error dialog box appears: Update or CancelUpdate without AddNew or Edit.
220 1-7RU6OB GeoMedia Professional Working with Label Manager Results
in warning sound.
While working with Label Manager and some of its sub-dialog boxes, the user is continually
"beeped" by a warning or attention sound when the user takes action on dialog boxes by
selecting OK or Cancel. Normally sounds are not used unless there is some dialog box or field in
error.
How to Reproduce:
1. Open any GeoWorkspace (even a blank one).
2. Select Labeling > Label Manager.
3. Turn up your speaker volume.
4. Select Cancel.
Observation: Notice the warning sound issued by selection of Cancel. While it seems to be only
an annoyance, it leads the user to feel there is something definitely wrong.
221 1-7RVQ0K GeoMedia Professional Problems with Label Manager settings
for large road shield symbols and text
Users need to use Label Manager in GeoMedia 2013 to place large road shields and text. It
seems that it is not possible to place symbols larger than 72 pts. If they set it to larger than 72,
it reverts to 72 points (it does display but back at 72 points). Users need a 150 pt. size.
The labeling system performs label placement calculations based on the size of the label and/or
symbol in "View Style Scaling". This means that the user may often need to create/use large size
values. It is unreasonable to restrict the user to a maximum size of 72 pts.
222 1-7S212R GeoMedia Professional Copy Parallel fails to work if any
dynamic label is displayed.
If Dynamic Labeling is displayed on a map, the Copy Parallel command fails to work. You are
prompted to select a feature but cannot select the feature. There is no error, simply a message
to "Click to select a feature to copy parallel".
If you Toggle Off the dynamic labeling (Labeling > Toggle Dynamic), Copy Parallel works.
How to Reproduce:
1. Open a GeoWorkspace correcting the path to data as needed.
2. Notice the display of Dynamic Label for States, StateName.
3. Select Vector > Copy Parallel, and attempt to copy an Interstate line.
Observation: You are prompted to select a feature but cannot select the feature. There is no
error, simply a message to "Click to select a feature to copy parallel". If you Toggle Off the
dynamic labeling (Labeling > Toggle Dynamic), Copy Parallel works.
223 1-7SQ4ZB GeoMedia Professional WFS Service does not handle layer
names with accents
Users have a façade service of a WFS service that contains layers with accents, when connecting
from GeoMedia 2013, the Add Feature Class to Legend fails. Also the users have isolated the
problem creating simple WFS features with layers that have accents, and then it fails when
connecting to it from a GeoMedia 2013 session. The problem is urgent for the users’ project
evolution because the façade is used for a WFS where the provider does not want to change
layer names.
224 1-7T6TT1 GeoMedia Professional GeoMedia Grid's Elevation
Workbench command returns invalid
results with IFC enabled.
GM 13.00.01 Release Phase testing Failure
Grid's Elevation Workbench command yields different results if IFC is enabled or not. The
problem seems to revolve around obtaining the Coordinate System of the gird data from the
underlying warehouse. The following is a very high level perspective of what looks like is
happening:
In the traditional workflow, IFC disabled, the Elevation Workbench (EWB) obtains a record from
the select set. It then traverses this record to its Originating Pipe (OP). From there, it gets the
Geometry Field of the data and thus the CoordSystem Extension. Next, a Server Trans Server
object is created that will return the CS of the warehouse.
In the IFC workflow, the same workflow is employed. However, when what we believe is the OP
is queried for the CoordSystem Extension of the Geometry Field and then the Server Trans
Server object is created, we are returned the CS of the Workspace.
The workflow for obtaining the Warehouse CS should be modified.
225 1-7T9Y07 GeoMedia Professional Labeling Options - OK and Cancel
buttons do not respond when
pressing the Enter key.
This problem persists on the Options dialog box after fixes were implemented for CR 1-736MKD.
The OK and Cancel buttons respond to mouse click events to dismiss the dialog box, and the
buttons also respond when pressing the tab key to navigate on the dialog box.
How to Reproduce:
1. Start GeoMedia Professional and open a GeoWorkspace.
2. Go to Labeling tab and select the “Labeling Options” command.
3. Press the tab key to navigate around on the dialog box. When the focus is on either the OK or
Cancel button, press the Enter key.
Observation: There is no response. The user must use a mouse click to dismiss the dialog box.
226 1-7TKE8N GeoMedia Professional AfterDockableControlHide event is
not fired when a floating dockable
control is closed.
In classic mode, when the Close button on a floating dockable control is clicked, the
AfterDockableControlHide event is fired from the Core (GeoMedia Application). In ribbon mode,
the AfterDockableControlHide event is not fired. Applications need to be notified when a
floating dockable control is closed so that any necessary cleanup can be done.
227 1-7TKQAL GeoMedia Professional Application commands need to be
able to control the Checked state of
their ribbon bar button.
The software needs the ability for application commands that implement a toggling capability
(like turning a dockable control on/off) to have their associated ribbon bar button's 'Checked'
state set accordingly. For example, when the application command's state is ON, its associated
ribbon bar button would be in a pushed-in state visually or in a pushed-out state otherwise. The
Precision Coordinates command and the Midpoint Snap option are examples of internal
GeoMedia commands that have this capability. Perhaps a new command evemethod (similar to
CanEnable) is needed where the command manager can determine the state of the toggle
command and update the ribbon bar GUI accordingly.
228 1-7UY066 GeoMedia Professional Labels with Korean characters and
parenthesis are displayed with
parenthesis in wrong location.
When the Insert Label command is used to place labels for attributes that contain Korean
characters (or characters from other Asian languages such as Japanese or Chinese), and those
attributes also contain parenthesis, the parenthesis are often displayed in the wrong location
within the label. In other words the label output from the Insert Label command does not match
the attribute value from which the label was derived. This appears to be a display issue because
the Geometry Information command shows the correct string for the TextPointGeometry that
makes up the label, but the display in the map window for the label does not match the
TextPointGeometry string as shown using Geometry Information.
The mismatch between the label text in the map window and the attribute appears to occur
only when the parenthesis (either open or closed) is at the beginning or at the end of Korean
labels, or there is no corresponding open or close parenthesis. For instance, an open
parenthesis at the beginning of the label text is displayed as a closed parenthesis at the end of
the label text and vice versa. Additionally a closed parenthesis at the beginning of the label text
is being displayed as open parentheses at the end.
This problem has been reproduced with both GM Professional 13.00 and 06.01.11.13. It cannot
be reproduced in GM Professional version 06.01.02.04, so it appears to be a regression from
that version. Furthermore the customer reports that this problem occurs with Windows 7, but
not Windows XP.
229 1-7V4X85 GeoMedia Professional Mismatching naming conventions for
application versus Help and Help
tooltip
Workflow: Install GeoMedia Professional (the desktop application) and observe the following:
A. Users are accustomed to finding Help as “?” in the upper right.
B. The application for Help is listed as “GeoMedia Pro”
Note: Users may actually miss the options for Help About because if you click on “GeoMedia
Pro”, the pull out is missed completely. User must hoover over “GeoMedia Pro” for Help About.
If you click on GeoMedia Pro option (usually a natural tendency), you get “GeoMedia Help”
topic “Overview of GeoMedia”. User agrees with filer of CR 1-7OHKVH “; Help About needs to
be more readily locatable “.
C. The application titled (title bar) is listed as “GeoMedia Professional”.
D. The about option is “About GeoMedia”.
E. The tooltip is “About GeoMedia Professional”.
F. The Help About dialog box is displayed and titled “About GeoMedia”. Notice that the text for
buttons is fuzzy.
G. Notice how I/Map Editor placed Help buttons.
230 1-7W4102 GeoMedia Professional Export to V8 dgn: Errors in output Output V8 .dgn files are incorrect - holes are not interpreted correctly, and polygons with large
number of vertices are lost.
In the user data, two large polygons are lost, and the 'holes' in the original data are now simply
polygons.
Customer says exporting to V7 works fine, but testing shows errors there as well.
The error is reproducible on GeoMedia v13.00.01.
Customer Service Request:
-----------------------------------
Problem exporting to V8 when there are holes and features with more than 5000 vertices. It
works when exporting to V7.
-----------------------------------
231 1-7WRNIX GeoMedia Professional Labeling does not honor Obstacles. Labeling does not honor the Obstacle option for area features within an area feature.
How to Reproduce:
1. Open 1-478041488.gws and correct path to NZSampleData.mdb.
2. Notice the two parcel labels blue and yellow are placed within a building area feature even
though buildings are set as an obstacle. These were placed as static labels. The result is using
dynamic labels.
Customer description: We have two area feature classes (parcels and buildings) that we want to
be labeled, where the labels of the parcels should not be placed on top of a building. In Label
Manager we have checked Obstacle for Buildings to get this result. But the labels of the parcels
are placed on the buildings anyway.
232 1-7YKR8I GeoMedia Professional Labeling rules: lack of documentation
for text positioning for area features
Labeling does not honor the Obstacle option for area features within an area feature.
How to Reproduce:
1. Open 1-478041488.gws and correct path to NZSampleData.mdb.
2. Notice the two parcel labels blue and yellow are placed within a building area feature even
though buildings are set as an obstacle. These were placed as static labels. The result is using
dynamic labels.
Customer description: We have two area feature classes (parcels and buildings) that we want to
be labeled, where the labels of the parcels should not be placed on top of a building. In Label
Manager we have checked Obstacle for Buildings to get this result. But the labels of the parcels
are placed on the buildings anyway.
233 1-7YKR9L GeoMedia Professional Place at Dominant Angle option yields
odd results.
The user has noted that the orientation of dynamic labeling of area features is not as wanted
when using the "Place at Dominant Angle" rule. The label orientation is not predictable and is
not as expected.
234 1-7YKRB2 GeoMedia Professional Dynamic Label orientation changes
when pan only small distance.
The user has noticed that after labeling area features using the Use Dominant Angle option a
very small pan can result changes to the label orientation. We would expect that the angle
would be consistent if:
a) the Zoom scale has not changed.
b) the area feature labeled remains fully in view (not clipped by the edge of the map window).
Instead we see that the label orientation can vary dramatically even by panning only a few mm.
in the view.
The user is not satisfied with the selected angle/orientation when using the Dominant Angle
option but recalculating by minor shifts and coming up with drastically different orientations
seems incorrect.
235 1-80GV0L GeoMedia Professional Error message with configuration
after installing GeoMedia to D: drive.
An error message is displayed with configuration after installing GeoMedia to D: drive instead of
default C: drive.
After installing GeoMedia Professional to the D: drive, while configuring it, the following error is
displayed:
---------------------------
Intergraph Setup Manager
---------------------------
Unable to load a required file <D:\Program Files (x86)\Intergraph\GeoMedia
Professional\Program\Intergraph.GeoMedia.ConfigurationWizard.exe>.
---------------------------
OK
---------------------------
236 1-80JDUB GeoMedia Professional WFS update to honor changes in
service
WFS Data Server needs to honor changes where the coordinate order must be (y,x), which is the
case with the WFS Service.
How to Reproduce:
1. Connect to a WFS Read-Write Data Server with the service source configured with SQL Server
Read-Write data.
2. Select any Legend entry and add.
3. Try moving a Feature from its original position to some other position in the map window.
4. An Error Message is displayed stating: "Unable to translate Geometry. Please review
Coordinate Systems and Geometry Definitions and retry."
237 1-80L32D GeoMedia Professional Objects with Cyrillic characters in
their names fail to copy from library.
Objects containing Cyrillic characters in the name can be successfully copied from a
GeoWorkspace to a library. But when attempting to copy these same objects from the library to
a new GeoWorkspace, the copy will fail with the error message "Cannot copy. An unknown or
invalid object was encountered during copy.".
How to Reproduce:
1. Set your machine to recognize Cyrillic characters by selecting Control Panel > ‘Region and
Language’. On the ‘Region and Language’ dialog box, select the Administrative tab. In the
‘Language for non-Unicode programs’ frame, click the ‘Change system locale’ button. Then from
the ‘Current system locale’ drop-down, select ‘Bulgarian (Bulgaria)’. Restart your system as
prompted.
2. Use GeoMedia Professional to open the provided ‘cyrillic.gws’ that has an Access warehouse
connection to cyrillic.mdb.
3. Select the ‘New Library’ command and create a new Access library from the
LibraryTemplate.mdb. Provide a name for the new library (such as ‘cyrillic_library.mdb’).
4. Select the Library Organizer command, and from the ‘GeoWorkspace contents’ list on the
right side of the dialog box. check each node in the treeview that contains objects (that is,
Categories, Legends, Queries, Searches, Spatial Filters, and Warehouse Connections), and then
click the ‘Arrow’ button to copy these objects to the library. When the ‘Copy complete.’
message is displayed, dismiss it with OK ; then click Close on the ‘Library Organizer’ dialog box.
5. Select the ‘New GeoWorkspace’ command, and create a blank GeoWorkspace’ .
6. Select the ‘New Library Connection’ command, and select the library created in Step 3 (for
example, ‘cyrillic_library.mdb’).
7. Select the ‘Library Organizer’ command, and attempt to copy each of the objects from the
‘Library contents’ list that contains Cyrillic characters in the name. In each case the copy will fail
with the message "Cannot copy. An unknown or invalid object was encountered during copy."
238 1-811OVZ GeoMedia Professional Custom Keyboard hotkeys no longer
work with the new ribbon style GM
Pro.
Custom keyboard hotkeys do not work with the new ribbon style menus in GM Professional
13.00.
In GM Professional 6.1 or classic menus 13, a customer can assign the F4 key, for example, to
the 'Fit All' command. With v13, they set it, but there is no effect. This works fine with the
Classic style.
You must recommend that the customers use Classic menus if they want to use their keyboard
shortcuts.
239 1-81B1KM GeoMedia Professional Caching coes not work for AFM
connection(s).
Caching of GM 2013 is not applied to AFM Models such as those used by PublicWorks, Parcel
Manager, and I/Map Editor. The user selects the Create Cache option but no cache files are
created. There is no error or indication of any issue or problem.
The User Guide and Help, or "Caching Explained" (Tools > Options dialog box button) does not
mention any restriction on AFM enabled connections.
240 1-81CJ1F GeoMedia Professional Displaying Layout Properties dialog
box using mnemonics pops up a
message dialog box.
This issue was observed while executing VT _ATPs on build 53.
How to Reproduce:
1. Start GM Professional, and open a new GeoWorkspace.
2. Open a layout window.
3. Select Layout Properties through mnemonics : ALT > Y > LP.
A warning message displays saying 'Please select a valid map frame'.
The Layout Window Properties dialog box is displayed successfully on clicking the 'Properties'
button on the ribbon bar.
241 1-88AURD GeoMedia Professional INI file options are not honored with
WMS service, in some cases.
This issue is specific to one WMS service.
How to Reproduce:
1. Make a WMS connection using url:
http://arcims.mim.dk/wmsconnector/com.esri.wms.Esrimap?SERVICENAME=GEUS_DK_DRIKKEV
AND_WMS&service=WMS&VERSION=1.1.0&REQUEST=GetCapabilities
2. Create an ini file and add the following content:
[SRS for Feature Classes]
Default=EPSG:25832
3. After connecting to the service, go to the features and see the coordinate system of the
Analaegs type layer.
The coordinate system is EPSG:4326 instead of EPSG:25832 as per ini file.
242 1-8BRU5Z GeoMedia Professional GeoMedia crashes when map window
is closed after back-to-back
invocations of Toggle Dynamic
command.
This problems was first noticed during the 14.00 construction phase during testing on the
Toggle Dynamic command due to changes made with event handlers. The same workflow was
applied to the 13.00.0100.00167 release and produced the same crash. This appears to be a
latent issue that is independent of the current enhancements being worked on this command.
It should be noted that part of the enhancements to this command for the 14.00 release is to
provide independent dynamic labeling per map window. It was initially thought that this was
contributing to this problem, but the fact that this is reproducible on the previous release led to
the filing of this latent CR.
How to Reproduce:
1. Create a GeoWorkspace and connect to USSampleData warehouse.
2. With a single map window open, add States, and zoom to display 50% of the country.
3. Save and exit; then reopen the saved GeoWorkspace.
4. Configure labeling for States in the window and toggle Dynamic Labels.
5. Open a new map window, add Counties and Rivers, and then zoom in to 25% of the country.
6. Configure labeling for Counties and Rivers in the new window.
7. Toggle Dynamic Labels off and then toggle Dynamic labels back on.
8. Close the second map window that contained Counties and Rivers by clicking the 'x' in the
upper-right corner of the window, and notice GeoMedia will crash.
243 1-8H92WQ GeoMedia Professional 'Update All' does not update dynamic
labels.
How to Reproduce:
1. Set up dynamic labels.
2. Zoom out using the mouse scroll wheel.
3. Click Update: - the labels are not refreshed.
4. After zooming by the mouse scroll wheel, a left click causes a refresh of the dynamic labels.
244 1-8EYFVT GeoMedia Professional Missing example data There is an exercise in the Help document "GeoMedia PublicWorks Manager Sample Event-
Handler Procedures" that references a 'GPWSampleEventHandler.zip' file, which is supposed to
be in the \SampleData folder. It is not. So we should add the file1-811OVZ1-80L32D1-80K9DFor
remove the exercise from Help.
245 1-80K9DF GeoMedia Professional Installation of Intergraph License
Manager shows incorrect product
name.
When installing the Intergraph License Manager to a system where the regional settings is not
English, the Setup dialog box lists the product as:
"SGI MSI Template Feature"and the description reads:
"SGI MSI Template Feature Description"
How to Reproduce:
1. Set Regional Settings Units and Formats to Japanese.
2. Run Setup.exe, run install, and then click Next until you get to the "Custom Setup" dialog box.
Observation: Notice the name of the feature to be installed is listed as "SGI MSI Template
Feature".
The correct name (as listed for English systems) is: Intergraph Licensing 11.10.02.1-7YKRB21-
7TKQALpan.
246 1-7TA6ZJ GeoMedia Professional Additional event packages needed for
.NET commands (DocSelectedObjects,
etc.).
GeoMedia currently contains an event package (wrapper) for the Application events to support
.NET commands. Such packages are needed due to limitations with COM interops. Additionally,
the DocSelectedObjects events also need an event package to properly fire events in .NET. This
is a requirement for the GeoMedia 3D flight path commands. Therefore, event notifications
directly connected from the DocSelectedObjects object will not properly raise the events for
.NET (C#) commands and require the use of an event package.
Furthermore, any other events implemented at the GeoMedia core level (Legend, LegendEntry,
etc.) should also each have an event package created and exposed in GeoMedia core to support
.NET commands.
247 1-7SQO6Q GeoMedia Professional Grayed out read-only attribute value
editable in Oracle connection
Using an Oracle DB, it has been discovered that it is possible to edit a grayed-out attribute (for
example, ID column, datatype AUTONUMBER). This behavior can be repeated. A grayed out
attribute is meant to indicate a read-only value and should not be editable. Note: In Access, the
data can be edited, but it is not saved to the database. Is this normal behavior?
How to Reproduce:
1. Open USSampleData.gws.
2. Make a warehouse connection to any Oracle read-write database available.
3. Use Warehouse > Output to Feature Classes to output the 'States' feature class from Access
to Oracle.
4. Display the Oracle 'States' feature class in the map window, and double click the state of
Alabama to display attribute properties.
5. Note that ID is grayed out and contains a value of '1'; then place focus on this value, and
change it to '1000'.
This value is edited to take the '1000' value and is seen in subsequent map window, data
window, and database review. Indicating that this is not read-only as the grayed out value
should indicate. Datatype is 'Autonumber'.
6. Repeat the review with an Access 'State' feature class and note that while a new value can be
input, it does not get committed to the database. The original value is retained and shows up in
subsequent map and data windows as such.
248 1-7SLV45 GeoMedia Professional GeoMedia crashes when attempting
to open a GeoWorkspace that has an
open layout window.
This problem also occurs in build 242. It does not occur when IFC is turned OFF. The data set
used is the Connecticut ArcView data set. When IFC is turned on and an attempt is made to
open one of the GeoWorkspace files delivered with GeoMedia, 2 of the 6 files will crash when
attempting to open them.
IFC ON
batchplotting.gws - crash
learn_afterplot.gws - error message (learn_afterplot_error.png) and then crash
learn_beforeplot.gws - no problem, standard configuration issues encountered
learn_data.gws - no problem, standard configuration issues encountered
learn_orig.gws - no problem.
skiresort_orig.gws - no problem.
USSampleData.gws - error message (USSampleData_error.png), error message
(USSampleData_error_2.png), and then crash.
IFC OFF
batchplotting.gws - no problem.
learn_afterplot.gws - no problem.
learn_beforeplot.gws - no problem.
learn_data.gws - no problem.
learn_orig.gws - no problem.
skiresort_orig.gws - no problem.
USSampleData.gws - no problem.
How to Reproduce:
1. Open C:\Connecticut\GeoWorkspaces\Connecticut_AV.gws.
2. Select File > Options and ensure that Warehouse caching has been enabled.
3. Save the GeoWorkspace.
4. Select the File/Application tab, and select the Open GeoWorkspace command.
5. On the Open GeoWorkspace dialog box, select batchplotting.gws.gws, and click Open.
6. On the 'File has changed' message dialog box, click No.249 1-7RW7IR GeoMedia Professional The spatial operator
“GConstants.gdbNotTouches” used in
OriginatingPipe does not work for
Oracle.
Code fragment:
conn.CreateOriginatingPipe(out op);
op.Table = featureName;
op.SpatialFilter = spatialFilter;
op.SpatialOperator = GConstants.gdbNotTouches;
op.GeometryFieldName = geometryFieldName;
Returns no records for Oracle database - incorrect.
Returns filtered records for Access database - correct.
250 1-7RRH6H GeoMedia Professional Performance degradation is observed
while Adding feature class to map
window with IFC ON-Rerun.
Performance degradation is observed while Adding feature classes to the map window with IFC
ON-Rerun. Similarly performance degradation is observed with Attribute Query to display
features.
• Refer this Wiki page: http://swengwiki:8080/display/GM/Using+Rational+Visual+Test to install
software and necessary configurations.
• Dataset is located at: \\in-gmtest9\Datasets\Access share.
• Workflows were written in the 'TestCaseDetails" sheet.
How to Reproduce:
Note: Before running this workflow, clean 'Caches' folder.
Add Legend Entry for IFC OFF:
1. Start the GM Professional ribbon application with a blank GeoWorkspace; make sure that IFC
option is set to OFF.
2. Make an Access connection to 'Orlando2000.mdb'. Data is available at \\in-
gmtest9\Datasets\Access share.
3. Select 'Add Legend Entry', add the 'PRCLLN' feature class to the map window, and then start
'timer', before clicking OK.
4. Once the feature class is loaded completely on the map window, stop the 'timer'. Time taken
to load the feature class on map window is "6.380 secs".
5. Exit GM Pro without saving the GeoWorkspace.
Add Legend Entry for IFC ON-Initial:
6. Start GM Pro ribbon application with a blank GeoWorkspace; make sure the IFC option is set
to ON to create the cache.
7. Make an Access connection to 'Orlando2000.mdb'. Data is available at \\in-
gmtest9\Datasets\Access share.
8. Select 'Add Legend Entry', add the 'PRCLLN' feature class to the map window, and then start
'timer' before clicking OK.
9. Once feature class is loaded completely on map window, stop the 'timer'.
Time taken to load feature class to map window is "18.112 secs".
251 1-7KQR3Y GeoMedia Professional Very large memory leak and
performance degradation when
editing attribute value of a query
The region discovered a problem whereby a significant performance degradation and memory
leak occurs when editing an attribute value. The problem occurs only when a spatial query (that
is itself built on join queries) is displayed in the legend and a change is made to an attribute
value from an attribute query (which is performed from a data window in the customer
workflow). Each time the attribute value is edited, the time to complete the operation and the
memory usage of the GeoMedia process increase significantly. The memory used is
approximately 500 MB per edit, and this memory is never released, so after a number of edits
the memory available for the machine can be quickly exhausted. Likewise the time to complete
the attribute change increases greatly each time another attribute edit is performed, so after
several edits the GeoMedia application is no longer responsive. For instance, it takes about 2
minutes to perform the attribute edit the first time (when the spatial query display is turned on
in the legend), and this increases the memory usage approximately 500 MB. Making a second
edit to the same attribute value takes 4 minutes and uses another 500 MB of memory. Each
subsequent edit takes an additional 2 minutes and 500 MB of memory, so after 5 edits, it takes
more than 10 minutes to complete the edit, and 2.5 GB of memory is used.
The initial workflow provided by the region required the use of their custom GEOSPro
application and this issue affects that application. However, the region provided a workflow and
dataset to be used to reproduce the problem using only the standard GeoMedia Pro application
and commands . A Windows 7 machine was used to reproduce the problem. You will also want
to display the ‘Windows Task Manager’ dialog box and use the Performance tab option so that
you can see the memory usage.
252 1-7J2WB7 GeoMedia Professional A customer has a number of rich text
(RTF) strings that contain diacritics
that do not display properly in
GeoMedia.
A customer has a number of rich text (RTF) strings that contain diacritics that do not display
properly in GeoMedia. The example provided by the customer consists of a string of four
characters where the second character in the string is an uppercase P with a combined
circumflex (). The string should appear as lP̂yd, but it is shown in the GeoMedia map window
with the circumflex character displayed to the right of the uppercase P so that the string
appears as IPˆyd. The issue seems to be a display problem because if you use the Geometry
Information command to examine the text geometry, you can see the value in the ‘Text’ field of
the Geometry Information dialog box shows the string as lP̂yd (with the circumflex character
combined with the uppercase P as expected based on the RTF string).
The actual RTF string as provided by the customer in the SR appears as:
{\i0\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset0 1;}}{\colortbl
;\red0\green0\blue0;}\viewkind4\uc1\pard\cf1\lang1033\fs18 lP\u770Pyd} with the relevant
portion of the string being the last characters of “lP\u770Pyd” where the \u770 represents the
Unicode Character 'COMBINING CIRCUMFLEX ACCENT' (U+0302) specified using the decimal
encoding of 770.
It has also been verified that the relevant part of this string (lP\u770Pyd) will generate the
correct RTF display in Microsoft Word, so this is further evidence that the RTF string itself is
correct.
In addition to the one example text geometry provided by the customer, they also provided a
Word document containing a list of additional characters with diacritics that they indicate are
not displayed correctly in GeoMedia.
253 1-7G039M GeoMedia Professional EG-1937: Orthophoto images and
panning
While panning around in the map window, orthophoto images will "break" into pieces and not
appear in a cohesive whole again until you either zoom in or out and then back to the scale at
which you were previously viewing the orthophotos. This happens for all of the customer seats
of GeoMedia 2013, whether or not they have enabled caching. The users are currently
reviewing a new series of orthophotography, and it is extremely frustrating and tedious to have
to zoom in and out, rather than simply pan across, to be able to examine these images. The
users had to go back to an older computer with the previous version of GeoMedia to efficiently
review these images.
Data in Attachments of SR 1-450078851
Create a GWS and attach ECW files to a warehouse. Zoom in to 1:1000 and pan. Redraw fails.
254 1-6YWDHJ GeoMedia Professional Sample files/databases not delivered
with setup
GM Pro 2013 setups are not delivered with certain files that were delivered earlier.
For example, the Warehouses folder used to contain: GMAGNCStreets.agi, GMAGTNStreets.agi,
GMAGTrainingCenterlineStreetData.mdb, GMAGTrainingCenterlineStreetData.xml,
GMAGExerciseAddresses.mdb, learn_afterplot.mdb, learn_beforeplot.mdb, learn_data.mdb,
SkiResort_orig.mdb, and world.mdb to name a few.
255 1-6WSBGZ GeoMedia Professional Display CAD Files crashes when
serving customers’ V8 DGN with
default dialog box settings.
When using the Display CAD Files command to serve the attached MicroStation V8 design file
(paw_2075_leitplanken.dgn) using the default settings of ‘Display all levels’ and ‘Create a single
legend entry for all selected levels’, an error message is displayed stating "An error encountered
loading date for TextGeometry of AllLevels legend entry. Method '~' of object '~' failed. Do you
want to continue loading remaining legend entries?". When the error message is dismissed with
either the Yes or No button, a crash will occur with the message “GeoMedia has stopped
working. A problem caused the program to stop working correctly. Windows will close the
program and notify you if a solution is available.”
The ‘paw_2075_leitplanken.dgn’ V8 design file was upgraded from a V7 design file
(paw_2075_leitplanken_v7.dgn), and the Display CAD Files command is able to successfully
serve the original paw_2075_leitplanken_v7.dgn file using the same default settings successfully
without any error. Likewise if the option is selected on the ‘Advanced’ tab to ‘Create a separate
legend entry for each selected level’, the V8 design file can be served successfully without any
errors as well.
How to Reproduce:
1. Open the provided LV03.gwt or create a GeoWorkspace, and load the ‘Schweiz_LV03.csf’ as
the GeoWorkspace Coordinate System file.
2. Select the Display CAD Files command.
3. Choose ‘MicroStation V8’ from the ‘CAD type’ drop-down list.
4. Browse for the folder containing the ‘paw_2075_leitplanken.dgn’ file, and once the Available
file list is populated, select the checkbox for ‘paw_2075_leitplanken.dgn’.
5. Browse for the ‘Coordinate system file’ named ‘Schweiz_LV03_DGNV8.csf’, and select it.
6. Now that the design file and coordinate system file are specified, click OK. This will result in
the error message: “An error was encountered loading data for TextGeometry of AllLevels
legend entry. Method '~' of object '~' failed...
256 87623_GM GeoMedia Professional Closing document object on
USSampleData.gws file causes crash
on 2nd open attempt.
The customer has written a custom application that opens a GeoMedia GeoWorkspace without
the database connections. It also will close the document object on a currently open
GeoWorkspace to close it and open another GeoWorkspace. All works fine in the code if the
USSampleData.gws GeoWorkspace is never opened. However, if this GeoWorkspace is opened,
and then the document object is closed on it, when you try to reopen this GeoWorkspace in
code with the Open method on the application object, GM crashes and the Microsoft
Send/Don't Send dialog box is displayed.
The error message in the Event Viewer for the Application is:
Faulting application geomedia.exe, version 6.1.5.1, faulting module mfc80.dll, version
8.0.50727.762, fault address 0x0008d10c.
The problem was reproduced on Version 06.01.05.01. The customer is running version
06.01.04.13.87322_GM.
257 83161_GM GeoMedia Professional Map scale not getting updated with
enter key
This is not a regression from GM Pro 6.0. The map scale is not getting updated with the Enter
key.
How to Reproduce:
1. Start GeoMedia Professional.
2. Create a GeoWorkspace.
3. Make an Access connection to USSampleData.mdb.
4. Add Legend Entry States.
5. Select Window > Show Layout Window, maximize the layout window, and then Select View >
Fit All.
6. Select Insert > Map.
7. Click OK, and place the map frame at a point with the layout frame.
8. Select the Map Properties of the placed map frame by double clicking on the placed map
frame.
9. Change the value of Scale field under Geometry and Content tab, and press the Enter key.
10. Observe that the map scale will not get updated.
258 1-7JQMKB GeoMedia Professional Appears no spatial filtering on
WebMap Publisher site using Native
Spatial DS with area features
The customer is in the process of migrating the GIS database from an Oracle to an SQL Server
2008 using spatial. They have used the Export to SQL Server command to export from Oracle
(using SQL Server native spatial format).
They have a WebMap Publisher test site based on the SQL Server spatial connection and are
finding that WebMap is not applying any spatial filter on the data. Thus the site will time out
when the parcel feature is loaded as it attempts to load over 200,000 records at 1:50,000 scale.
Spatial indexes have been defined as per the GeoMedia SQL Server Spatial User Guide. The
current Oracle-based site is not showing this behavior and is spatially filtering correctly.
259 1-6GAR8A GeoMedia Professional MapSvr.GetFromLibrary method
cannot open WFS
Legend/LegendEntry stored in library
warehouse.
Users have an installation with GWM Publisher applications created with WebMap Professional
6.1.6 that they migrated through different minor releases until 6.1.11.
The metadata of Publisher application is in Oracle. Everything works fine, but after intensive
working during 3 or 4 hours, they begin to get errors on Event Viewer and after these normally
the system is not working fine, and they have to restart services.
The error on Event Viewer says: “Error Description: Error in Initiating Display Path - Extension,
AFMAttributeFilterPipe, not found
The error in WebMap Log says: “UpdateLegend->Canvas 1871f694
- Error in initiating display path 8004045c - Exit CGWMMapServer::CreateMapByRange.
Checking the metadata of the Publisher application they appreciate that there is a table
AFMATTRFILTERPIPES that on the new publisher application is not present and also has data
populated. They do not know if this is the cause of the problem and if it is, how to update their
projects for not having this table. They have never had PublicWorks installed, so they do not
understand why this table is created.
Event viewer:
Time: Wed Mar 21 11:12:44 2012
Source: Map Server
Version: 06.01.11.19
Function CreateMapByRange
Error: 0x8004045c
Error Description: Error in Initiating Display Path - Extension, AFMAttributeFilterPipe, not found
WebMap:
Mon Mar 19 11:43:50 2012(1.130310) - LE Loaded
Mon Mar 19 11:43:50 2012(1.130332) - Logo Font Size in get 0.000000
Mon Mar 19 11:43:50 2012(1.130353) - UpdateLegend->Canvas 1871f694
Mon Mar 19 11:43:50 2012(1.139315) - Error in initiating display path 8004045c
Mon Mar 19 11:43:50 2012(1.145288) - Exit CGWMMapServer::CreateMapByRange - -
2147220388260 1-6B3GPE GeoMedia Professional Update documentation to reflect Bing
Maps licenses for sale through SG&I
Price book.
Current GeoMedia Pro documentation directs users to Microsoft's Bing Maps website for
purchase of their licenses. This should be changed to reflect that SG&I can now offer Bing Maps
license keys through the SG&I price book.
261 1-7P8ORO GeoMedia Professional Ability to import ESRI File
GeoDatabase data format.
Software needs the ability to import the ESRI File GeoDatabase data format.
262 1-6FIAW9 GeoMedia Professional Need data server for ESRI File
GeoDatabase data
More and more users are using ESRI File GeoDatabase format of data. File GeoDatabase does
not suffer the limitations of the ArcView shapefile format, such as attribute field names length
limits and limits on numeric data type support. GeoMedia needs the ability to serve this more
modern format of data.
263 1-4ZFE17 GeoMedia Professional GM Pro crashes on Fix Connectivity
and corrupts data containing arcs.
GM Pro crashes to desktop when running Fix Connectivity on customer-supplied dataset. Data
passes Oracle Validation. For the customer, the process does not crash, instead, it corrupts their
data and forces them to reload from backup. In-house testing has not seen the data corruption,
only the crash.
264 54671_GM GeoMedia Professional Adding Conflation functionality A good enhancement to GeoMedia Professional would be to incorporate conflation
functionality into the product. Perhaps the Spatial Tools conflation could be adapted for Line to
Line conflation and something similar to the Parcel Manager Fix Areas could be adapted for
Area to Area conflation.
265 1-80L33R GeoMedia Professional Appears no spatial filtering on
WebMap Publisher site using Native
Spatial DS w/area features
A customer is in the process of migrating the GIS database from an Oracle to an SQL Server
2008 using spatial. They have used the Export to SQL Server command to export from Oracle
(using SQL Server native spatial format). They have a WebMap Publisher test site based on the
SQL Server spatial connection and are finding that WebMap is not applying any spatial filter on
the data. Thus, the site will time out when the parcel feature is loaded as it attempts to load
over 200,000 records at 1:50,000 scale. Spatial indexes have been defined as per the GeoMedia
SQL Server Spatial User Guide. The current Oracle-based site is not showing this behavior and is
spatially filtering correctly
266 86572_GM GeoMedia Grid Update Geometry Z Values
command fails to update
features in Oracle warehouse.
If the Update Geometry Z Values command is run and feature classes from an Oracle warehouse
are selected for update, none of the vertices are updated.
267 85099_GM GeoMedia Grid GM Grid cell offset from GM
Pro positioning.
GMG - Cell origin incorrect. When importing the attached text XYZ file, chose cell
center as the position of the points. The point is not within the cell at all. User
thought this may be due to the data being irregular, so they added two false points at
top right and bottom left. The same positional error occurred. From where does GMG
take the file origin? User just created a subset of a grid dataset (part.xyz) and
imported that. It also gave a half cell offset.
268 84000_GM GeoMedia Grid Subscene command returns errors,
fails to run, errors not useful in
recovery
Using the workflow below, when the subscene command is run, error messages are returned
that do not assist the user in recovery. - open new workspace, connect to madisoncountyal.mdb
as delivered with GMCore - change workspace to UTM 16N projectionc:\trs- import Madison
and HSV grid files - run import a second time, import pondvolumearea.mfm to another study
area - set the first study area to active - run reporject/copy, select HSV layer, and reproject to
second study area using defaults - run subscene, select pondvolumearea layer to be subscened. -
select hsv layer for subscene extent - press OK, Errors display: --------------------------- SubScene
Error --------------------------- The row and/or column value specified is invalid. ---------------------------
OK ------------------------------------------------------ SubScene Error --------------------------- Access
Denied --------------------------- OK ---------------------------
269 82281_GM GeoMedia Grid Request More Flexible ASCII
Import of GRIDS.
User is preparing some presales work and received an ArcInfo ASCII GRID file from
the client. He gets an 'x coordinate value in the input field is invalid' error. He then
edited the file, replaced all spaces by tabs, and tried to import it as an ASCII tab
delimited grid; that didn't work either. He discovered the endline character(s) was not
correct. After updating this, it worked. User believes it would be much more efficient
if this import filter should be more flexible: space, tab, multispaces, multitabs, endline
CR of LF or a combination. A little wizard would come in handy.
270 81010_GM GeoMedia Grid Cancel from warning dialog results in
inability to run command
If a non linear feature class is selected, then if the layer profile command is run, an
error/continue dialog displays which notes "You can only select a LINE feature before
performing a Profile. Click OK to begin drawing profile line(s), or Cancel to abort this operation.
If Cancel is selected, and the select set is cleared, the command cannot be run again until a
workaround is completed. Selection of the command does nothing. While in this state, if a non-
linear feature is selected, and the OK button is selected from the error/warning dialog, the
operator is supposed to be able to place a line manually for the profile. This will not work until
the workaround is completed The workaround is to select a linear feature. The command will
then run again.
271 78909_GM GeoMedia Grid Unable to click on GeoMedia to
bring the application forward
when switching windows.
If other applications are running in addition to GeoMedia, then if the user runs the Study Area
Information command, leaves the dialog displayed, and covers part of the GeoMedia application
with another application (email, IE, etc.) such that it covers the study area information dialog,
clicking on GeoMedia will not bring the application forward to the front of the windows stack.
272 77090_GM GeoMedia Grid Profile command fails to run
using mid or high latitude
DTED.
If a middle or high latitude DTED file is imported and displayed and if vector lines are digitized
over the study area, then if one of the lines is selected and Layer Profile is run, the command
fails and an error is displayed. The error is not user friendly. The error notes "Unable to
successfully query the server's coordinate system table. Please review the server's current
configuration and retry."
273 65315_GM GeoMedia Grid GMTerrain data will not import
using svy_ft in .csf file.
If the noted set of data is selected for import to GMGrid, the process fails and returns the error
"Error processing file: .” The cause of the error was: “The given unit specified by the short unit
string: sf could not be found."
274 64245_GM GeoMedia Grid Cancel button may not
complete exit command, or
free memory.
If the cancel button is selected during the feature record creation step of Vectorize to feature
class (when large numbers of feature class records need to be created), the computer system
will become unstable and slow. Upon exit from GeoMedia, a large amount of system memory
continues to be used, and GeoMedia.exe remains running and processes (something, not sure
what). This is only one example. Other commands potentially have the same result if cancel is
pressed, especially when processing large amounts of data. This CR is intended to cover a
review of command clean-up for all GMGrid commands after the cancel button is selected.
275 64147_GM GeoMedia Grid Date display does not match
system short date definition.
If the isolation dialog or the Date/Time tab in the shaded relief dialog is viewed, the date format
displayed may not match the date format defined under the regional and language setting for
short date. For example, if English (United States) is the selected regional selection, the format
is not honored in these two dialogs.
276 59591_GM GeoMedia Grid Problems when comma is used as
decimal delimiter rather than period
The following problems were noted when a comma (,) is used as the decimal delimiter rather
than a period (.). [Set using Control Panel > Regional Options, Numbers tab, Decimal Symbol] 1)
Some fields did not accept a comma delimiter, but forced the use of a period 2) When a period
appears in a field it is actually dropped in processing (so that 30.0 becomes 300 when a Study
Area is defined, for example)
277 1-6W709Q GeoMedia Grid Several commands have problems
with European decimal separators
Czech customer has problem with grid when windows system decimal separator is set to "," .
They found this situation occurs with these commands: * create isolines * creating new study
areas * grade - precision They found two type of workarounds. * when there is number typed
from keypad and you cannot use double (integer is enough), the decimal symbol must be
manually removed from textbox * Or reset the windows regional settings such that '.' is the
decimal separator.
278 1-6MD35R GeoMedia Grid Viewing Documentation When going though the 'Viewshed' tutorial, page 11 covers how to view your results in 3D. This
assumes that you installed the Skiline Viewer that was distributed with the product in past
verstion. Also, documentation should state that with GM 3D installed you do not need to go
through these steps and with 3D installed the 'Construct 3D Model' command (page 12) is not
available. I am also under the impression that with the next version of Grid this whole section
should be removed since Grid will not come with the Skyline product anymore.
279 1-6DNJ7T GeoMedia Grid Some .asc will not import into GM
Grid
Having some trouble importing certain .asc 0.5m dem files in to Grid. Coordinates are in meters
and headers for each .asc appear valid. Study area row x column limits are acceptable. Data
location:\\fileserver\TRdata\GeoMedia\stclow\1-6DNJ7T Workflow to reproduce:Unzip .zip
from data location Open blank geoworkspace Grid>Study Area>Import File(s) choose single file
and point to 'rr_n2.asc' Choose ArcGrid ASCII Point .csf to the .csf provided at data location Next
change tie point untis to be meters and cell resolution to equal 0.5m file will get translated and
added to study area Finish Repeat workflow with ar_east.asc and observe after attempting to
translate the raster layer the following error message is received and no layer is created: Error
processing file: ar_east.asc the cause of the error was: Error, an error occurred while reading
from the input file.
280 1-6BX70J GeoMedia Grid Buffer overflow found in the
KGIncrementalVolume operation.
Buffer overflows will intermittantly crash the software. The problem is with a variable named
"Z" with an element count of 9. This element array is 0 based but the 9th index is written to and
read from.
281 1-6ADB8D GeoMedia Grid The Density Output Area Units combo
box is no longer working
The mapping between what the user sees on screen and what parameter is actually used for the
normalization process differ. Problem is caused by localization work.
282 1-6AAG09 GeoMedia Grid While executing the GeoMedia Grid
customer based workflow - Natural
Heritage Study - GeoMedia crashe
Execute the Customer based workflow - Natural Heritage Study that is delivered with the
GMGRID installation. Observer that GeoMedia crashes on exit with the follwoing error This
crash occurred both manually and through an ATP. GeoMedia.exe - Application Error The
instruction at "0x781ff27c" referenced memory at "0x0000009c". The memory could not be
"read". Clcik on OK to terminate te program. (See atttached snapshot of the error)
283 1-695349 GeoMedia Grid Incremental Frontage algorithm
doesn't correcly deal with fixed data
when an elevation layer is used
Algorithm problem is in the GetMeCotesPerimeters. Void should be intepreted as 0. Right now,
it's not and its value is being used.
284 1-65OPF1 GeoMedia Grid Daylight savings time on control is
always disabled
If the insolation command is run, the 'Daylight savings time on' check box is always disabled.
This is regression from 6.1.2 GMGrid.
285 1-63D7SN GeoMedia Grid GM Grid commands error out with an
"ActiveX component can't create
object"
GM Grid commands error out with an "ActiveX component can't create object". The problem is
a result of GM Grid installation not handling Microsoft updates correctly on the machine. The
workaround is to uninstall GM Grid and run Windows update on the machine and install all
critical updates. Then reinstall GM Grid and the error is eliminated. Development(David O.) is
aware of the problem and provided the workaround.
286 1-60XVOB GeoMedia Grid ESRI ASCII (.asc) fail to import Using the Import File(s) tool within Grid, an error is reported when the user imports an ESRI
ASCII file. The error report reads: "The cause of the error was: Failed to activate control
'VB.UserControl'. This control may be incompatible with your application. Make sure you are
using the version of the control that was provided with your application." The .asc data used
was attached in CR# 1-5M2XL0. This error report does not get called using 06.01.02
287 1-5VBHX9 GeoMedia Grid MFMathematics.MFEval(MFMap1,
mfSubtract, MFMap2) doesn’t work.
I have problem with GeoMedia Grid 6.1 (6.01.00.18 and 6.01.01.28).
MFMathematics.MFEval(MFMap1, mfSubtract, MFMap2) doesn’t work. It give a error: -
2147211487: Method '~' of object '~' failed But when I try run the same code with the same
attributes in GeoMediaGrid 6.0 (6.00.01.14) everything is all right. What is going wrong? For
further details please contact with Piotr Chomiankiewicz: [email protected]
288 1-5V2VT2 GeoMedia Grid Data Units from LiDAR Source Data
Properties dialog not carrying through
to end result.
How to Reproduce:
1. Select LiDAR footprints.
2. Select Tools > Source Data > Load From Selected Footprints.
3. Leave the Default properties.
4. Note: Default Data units is equal to “Feet”.
5. Click OK button.
6. Select Tools > Surface > Smooth.
7. Leave the Default properties.
8. Click OK button.
9. Click Refresh button.
10.Get the information for the resulting layer and notice that it is “Feet”.
11. Reopen the Load From Selected Footprints dialog box.
12. Change the Data Unit to “Meters”.
13. Click Refresh button.
14.Get the information for the resulting layer and notice that it is still “Feet”.
Should be Meters. This will throw off all DEM by a large value.
289 1-5QLVBV GeoMedia Grid Define New Layer needs to
support SQL Server.
GeoMedia Feature Cartographer has a command which calls GeoMedia Grid's Define New
Layer. We get a failure when making that call if the output is an SQL Server or SQL Server
Express connection. GeoMedia Feature Cartographer has requirements to support SQL Server
Express. We need GeoMedia Grid to also support SQL Server.
290 1-5N3KDB GeoMedia Grid Study area and imported file row/col
numbers not matching
Import single .xyz file to define Study area and the study area created and the imported .xyz
layer have different row/col numbers This causes an issue in later workflows since created
layers and rasterized legend entries take on the resolution and extents of the study area. When
using the imported .xyz layer and created layers in the study area the row/col numbers do not
match and can not be used in the workflow together because of this. As per help topics the
coord system, cell resolution and extents should match the study area: The Rasterize Feature
Classes command is similar to the Rasterize Legend Entry(s) command (i.e. the Rasterize Feature
Classes command creates a new GeoMedia Grid layer for each input feature class). However,
unlike the Rasterize Legend Entry(s) command, the Rasterize Feature Classes command allows
you to convert feature classes to GeoMedia Grid layers without having to first load them into a
GeoMedia map window. The resulting GeoMedia Grid layers will have the same coordinate
system, cell resolution, and extents as the current Study Area. This is causing the " the number
Row/Col is different" message when running a supervised classification. See data location
\\fileserver\TRdata\GeoMedia\stclow\1-5n3kdb for data files and grid.wmv located here for
workflow. support has not tested against version 6.0 of grid, but 6.1.1. shows this same defect.
291 1-5M2XL0 GeoMedia Grid Importing Arc ASCII grid files into GM
Grid - file is placed in wrong location
Customer has been given some LIDAR differencing data in ESRI ASCII grid format which they
need to bring in to GeoMedia Grid. This data contains difference information between pre- and
post- earthquake LIDAR data. Files are attached. An example header would be the following:
ncols 480 nrows 720 xllcenter 1560160.500 yllcenter 5179200.500 cellsize 1.0000 nodata_value
-99 On the import dialog, the above values for X and Y appear. The default location for this
point within the cell is the upper left corner, but it should be the center. I changed this so that
the pixel center was specified by the values above. The file imports fine, with no error, but the
upper left corner of the grid (measured using the footprint and coordinate readout in GMPro) is
at E/N 1560160.5/5179921.0, which is incorrect. The correct location should be
1560160.0/5179920.0. The upper left corner is 1 pixel too far east, and 1/2 pixel north of where
it should be. I've tried several other coordinate locations on the gadget and have yet to find one
which puts the grid into the correct location. I created a .tif file of this data using a third party
tool - it displays in the correct location. It is attached as a separate .zip. You can use the Insert
> Georeferenced Images command in GeoMedia Pro to get an idea where the image should be.
292 1-5JXDON GeoMedia Grid File Name Attribute Selection dialog
displays once for each feature record
input
The file name attribute selection dialog will display once for each footprint record that is
selected. The user may select 100 LAS file footprints to build a layer, and there is no way to tell
what feature record the user is being prompted for input from.
293 1-5JVDBD GeoMedia Grid Cell Magnifier/layer drill down
commands stop 3D map window
from displaying content
If the cell magnifier or the layer drill down commands in GMGrid are running and the user
selects to start the GeoMedia 3D 3d Window, no data will display in the 3D map window, and
navigation will not work.
294 1-5JCW21 GeoMedia Grid The MFEngine is not thread
safe.
The MFEngine is not thread safe, and this is causing crashes when running certain GM
Grid commands in a GM 3D map window.
295 1-5I66C9 GeoMedia Grid Calculator do not list all the layers of
Study Area selected, inconsistently.
This was observed during the execution of Points to At-Risk Areas Grid tutorial. At page 22,
Invoke 'Calculator' to create Mercury Severity layer. Observe that, it is not listed all the layers
available in the Study Area, it lists only the layers created during the workflow run, do not list
the layers already exists in saved GWS. Note: Reinvoke 'Study Area>List' and 'Calculator' 2 to 3
times, it lists all the layers in Calculator dialog.
296 1-58GE21 GeoMedia Grid Attempt to run Update geometry z
value command returns error
Create a study area with the Huntsville AL SDTS terrain file. Then run update
geometry Z values command, and select the feature class in the warehouse. The
command fails, and returns the error: Grid Command Error: Type mismatch –OK–.
297 1-57G9E5 GeoMedia Grid X-coordinate transformations fail for
derived data.
USGS NED Data was downloaded from http://seamless.usgs.gov web site. Data
originated as GeoTIFF, and imports as Unprojected - Lat-Lon in Grid. Data was
Reproject/Copy'd to a new study area which is projected in our standard coordinate
system (4602-NAD83-HARN-NoVert-sf,) which translates to Washington State Plane
South projection, NAD83-HARN geographic space, user-defined vertical, survey foot
units. The imported data projects correctly, and all grid layers derived from it is also
correctly represented. When a resultant layer, in this case generalized slope, is
vectorized using any method offered, the X-axis result is incorrect. An image will be
provided to demonstrate, but it appears that the x-value is storing as feet, but
calculated in meters, thus arriving too far west, and highly compressed.
298 1-515SW1 GeoMedia Grid Numerous Kinks (11,250) found
in created isolines.
Numerous kinks were found in created isolines by running the Fusion Validate Geometry using
the Specialized anomalies option. Most were flat zigzags in lines, each of which were logged as
two kinks. 30 queue items were extremely small closed contours with only one vertex location
at one end. Another six were relatively large spike shapes where the line crossed itself. Re-
running the same Specialized Geometric Validation on kinks only and with auto fix turned on at
the default tolerance of 10 resulted in a 36 item queue containing the 30 small closed contours
and the 6 self crossing spikes mentioned above. Grid should determine why these kinks are
created and determine if they can be avoided when creating isolines.
299 1-4ZXABN GeoMedia Grid 'Place subscene(s) in new study area'
text field blacks upon toggling the
options
Invoke Grid>Study Area>Subscene In the 'Options' section, toggle the radio-buttons between
the options and observe that the Text Field turns black making it difficult for the user to enter
the text
300 1-4YWAFP GeoMedia Grid .flt and .asc files not listed when
importing multiple files
when using Grid>Study Area>Import File(s) Under All supported files for the Import Single File
ArcGird binary (.flt) and ArcGrid ascii (.asc) are present and available to be imported. However
when importing multiple files, neither the .flt or .asc file is present in the format drop down.
301 1-4Y62IM GeoMedia Grid GeoTIF output from GMGrid
contains extraneous header
coordinate system information
If a geographic WGS 84 coordinate system is defined in a study area, and then if a
geoTIF file is created using the layer export command in GMGrid, the coordinate
system information section of the geoTIF header contains extraneous information,
seen below. This occurs for any such export. GeogCitationGeoKey (Ascii,72):
"Projection: Cylindrical equirectangular; Datum: WGS84;
302 1-4Y37DI GeoMedia Grid Request to support MG4 data
type (Mr SID 4th Generation
file).
The request is to enhance GMGrid and/or Terrain to support fourth generation Mr
SID files (MG4). General information is that MG4 is a compressed version of .LAS and
.XYZ LiDAR data sets that allows for increased performance when processing and
accessing LiDAR data sets. Customer is requesting that GM Grid support this data
type.
303 1-4X67OD GeoMedia Grid Layer calculator command create
corrupt layer which can crash
GeoMedia
Using the equation noted below, a layer is created. If viewed in layer information, the statistics
display invalid values. If the layer is opened in the Edit Window and an entry on the legend is
right clicked, GMCore will crash. Import the two layers in attachments, and apply the equation:
DownhilAccumulation/TAN(GradeDegrees/0.174532925)
304 1-4X3E83 GeoMedia Grid GMG -import ARCGRID fails when X-
coordiante of origin is 0.0
ARCGRID data failed to import into GMG06.01.01.28. Error stated that x coordinate
was invalid. The user checked header of file and it is NCOLS 1200 NROWS 1200
XLLCORNER -0.0000000000 YLLCORNER 52.0000000000 CELLSIZE 0.0016666667
NODATA_VALUE 25.000 -20.967 -21.105 -21.243, which seemed ok. They removed
the minus (-) sign, but got the same error. So they edited the header to NCOLS 1200
NROWS 1200 XLLCORNER 0.0000000001 YLLCORNER 52.0000000000 CELLSIZE
0.0016666667 NODATA_VALUE 25.000 -20.967 -21.105 -21.243, and now the data
imports ok. Thus GMG seems to have a restriction on data with an origin exactly on the
meridian. Testing shows X origin of 0.0 causes identical error for projected CS as well.
305 1-4USI0B GeoMedia Grid Cancel on Import does not
really cancel the process.
How to Reproduce:
1. On clicking the cancel button while the status bar says "Getting geo-referencing
infor....", the dialog dismisses instantaneously but the process keeps running in the
background. Even if GeoMedia is exited, the process keeps running until the import is
complete.
2. After Cancel button is clicked, trying to invoke the Study Area > Import File
command again does not display the command dialog. User has to select it for the
second time for the command dialog to display.
3. Sometimes an Object Variable error occurs after clicking the Cancel button.
306 1-4UQ3XF GeoMedia Grid Import files command fails to list
layer types in drop down list and
open file for normal user
If a new normal system type user is created on a system, then if that user is used to open a new
workspace, create a new warehouse and then attempt to import external grid data, the list for
multi file import is empty. If single file import is run, there are not files of type available. This is
regression from 6.1.0 and earlier releases of 6.1.1 GMGrid.
307 1-4UL1EG GeoMedia Grid View legend group entries Int/Inc
field does not accept decimal values
If the user runs view legend and selects a floating point layer, then selects a set of
values, right clicks, selects the group by item, selects value increment, and enters 0.1,
an error is displayed if the range of values supports the group definition: MFLEGV~1
Error, Interval/Increment value must be greater than zero. –OK–
The error is in error because 0.1 is greater than zero. Also, this command needs to
support decimal grouping.
308 1-4UBEC5 GeoMedia Grid Export layer to geotiff fails to run,
returns system error.
Export to geotiff fails on system using GeoMedia regular, with error below. Export to
tiff error: Unable to georeference the file. The error returned was: Unable to cast
COM object of type 'RasterGeoRef.ZIGeoCodeClass' to interface type
'RasterGeoRef.IZIGeoCode6'. This operation failed because the QueryInterface call on
the COM component for the interface with IID '{806A0A53-51B8-4E6B-9D7D-
744969FEBA81}' failed due to the following error: No such interface supported
(Exception from HRESULT: 0x80004002 (E_NOINTERFACE)). – OK–
309 1-4U4WLZ GeoMedia Grid GM crashes if obscure areas entirely
contain point features
Add two sources such that one contains point features with geomorphic type as
regular and the other contains area features (that spatially contain these point
features) with geomorphic type as obscure areas. Running Triangulation for the above
two sources crashes GM.
How to Reproduce:
1. In a blank new gws, connect r/w to USSampleData.mdb.
2. Add States and define Study Area encompassing all States with a resolution of 1
mile.
3. Invoke Triangulation command and select the following sources. Source1: Select
Routeshield with elevation source as RouteNumber with units as KM's. Source2:
Select States with elevation source as Geometry and geomorphic type as Obscure
Areas.
4. With rest all defaults run the command. Observe that GM crashes.
310 1-4U4H0W GeoMedia Grid Study area list commands return if
selected when layout window is
active.
If the study area list is displayed and contains Study Areas and layers, then if the
layout window is displayed and if any study area right click menu command is run, an
error is returned in almost every case. The errors are similar to: Cannot get layer
history Error: Invalid argument. –OK–
311 1-4U147O GeoMedia Grid Value field allows entry of
alphabetic characters and will
still run.
The value field for the explicit cross tabulation dialog allows the entry of alphabetic
characters other than VOID or void. The command will run even though the text is not
a numeric value and will output a numeric value of 0 in the result layer.
312 1-4TY7XZ GeoMedia Grid Two commands share identical
dialog title
Both the Ordinary Kriging Suite and the Ordinary Kriging command dialogs have the
same title, "Ordinary Kriging". The Ordinary Kriging Suite command dialog title
should be updated to reflect the actual command name.
313 1-4TW8GE GeoMedia Grid Kriging suite command fails on
German operating system.
Using the noted data and the following workflow, the Ordinary Kriging Suite
command fails to create results. Same workflow on English US system runs fine.
How to Reproduce:
1. Open new workspace.
2. Create new access warehouse.
3. Import .mfm layer.
4. Set workspace distance units to svy_ft.
5. Run ordinary Kriging suite.
6. Set distance units to svy_ft.
7. Set lag separation to 10,000001.
8. Set number of pairs to 10.
9. Press next.
10. Turn on covariance and correlogram options.
11. Press variogram.
12. Tab dialog returns with message: "Sorry, there was a problem reading the target
file."
13. Processing cursor continues to display; it takes two clicks on the OK button to
return to the command dialog.
314 1-4TUBZJ GeoMedia Grid Import File > XYZ > creates
incorrectly sized study area
How to Reproduce:
1. Open a blank .gws, connect to world.mdb.
2. Load provided 'Krovak.csf' as GeoWorkspace Coordinate System.
3. Grid > Study Area > Import > XYZ. Import provided .xyz file using Krovak.csf. Grid is
metric, with 10m grid cell. Grid is 10rowx X 10 columns (100m X 100m).
4. Display layer in map window.
5. GeoMedia > Tools > Measure Distance - grid cells are 10mX10m, and there are 10
rows of 10 columns.
6. Grid > Study Area > Select: On this dialog note that the grid file has 10 rows by 10
columns, but the study area is 90m X 90m. This is incorrect.
7. Grid > Layer > Export to .xyz file, create new output file 'output.xyz' (UTM).
8. Grid > Study Area > Import - import 'output.xyz' (meters, krovak).
9. Grid > Study Area > Select: Newly imported grid is 81m X 81m. The size of the grid
and the dimension of a grid cell, should not change simply by exporting/importing the
data.
315 1-4TEHRV GeoMedia Grid Group details how 'into x
groups' field error message is
incorrect, field always decimal
If a decimal value less than one is entered into the 'into X groups' field, such as .001,
an error is returned, but the message is not accurate. Error states: GeoMedia Grid
Error; Error, Groups or Group Size must not be zero. –OK–
Instead, the message should state that decimal values less than one are not valid. Or
better yet, the field should only allow integer numeric entry.
316 1-5M2XKK GeoMedia Grid The user requests
enhancement - Batch import of
ESRI ASCII (.ASC) files
The user is currently receiving post-earthquake LIDAR derived DEM data in .ASC
format would like a CR that allows batch importing of ESRII ASCII Grid files.
317 1-5B23BC GeoMedia Grid RasterizeVector method fails
with RPC_E_Server error
message: 0x80010105
The user wants to encode an attribute by using a map generated by RasterizeVector.
The attached program does not get past the RasterizeVector method. It always fails
with an error of Server Threw Exception: RPC_SERVER_FAULT.
318 1-4SGFQ6 GeoMedia Grid Number in search radius field
returns error that value must be
numeric.
If 11 or more numbers are entered in the search radius field for the variogram tab
of the kriging suite command, an error displays noting that the entry must be
numeric even though it was -Ordinary Krige Suite The value entered must be
numeric. – OK.
319 1-4XULDL GeoMedia Grid Export of 32-bit signed layer to
GeoTIFF does not create a
signed file
Using any signed data set (mosaic this set of files, then export), when export is run
as a GeoTIFF, then if the GeoTIFF is reimported to GM Grid, the data has been
changed to two values only, unsigned.
320 1-7U246R GeoMedia Grid Help Dialog title is labeled
"GeoMediaGrid_Help". Should
be labeled "GeoMedia Grid
Help".
Help Dialog title is labeled "GeoMediaGrid_Help". It should be labeled "GeoMedia
Grid Help".
321 1-7T8U6I GeoMedia Grid GeoMedia Grid's Elevation
Workbench command returns
invalid results with IFC enabled.
GeoMedia Grid's Elevation Workbench command yields different results when IFC
is enabled and when it is not. The problem seems to revolve around obtaining the
Coordinate System of the grid data from the underlying warehouse.
322 1-7N0CLI GeoMedia Image
Professional
Image Pro checks out 2 ILT licenses
when Image Pro ILT window is
invoked.
When opening GMPro w/ GMImagePro installed, a GeoMedia_Professional license is checked
out. If you then select a GeoMedia Image (not GMIP) command (e.g. Show Enhancement
Toolbar), a GeoMedia_Image license is checked out.
If you select a GeoMedia Image Professional command which would open the ILT Image
Window (Load Image from Footprint, etc.) two copies of the GeoMedia_ILT_Plus license are
checked out.
If you select a GM Image Pro command that does not open the ILT Image Window (e.g. Tracking 323 1-5IX6V7 GeoMedia Image
Professional
GeoTIFF information for Mercator
written incorrectly
When a non-0 latitude of origin is used in the Mercator projection definition, the Y origin is
written incorrectly in the GeoTIFF information when the image is saved in ILT+. The Y origin is
referenced to 0 latitude rather than the latitude of origin defined in the projection.To
reproduce: 1. Open the attached image moon.tif in ILT+. 2. Register the image by adding control
points at the quad frame corners and keying in the corresponding lat/lon values. 3. Image >
Rectify. Select Projection, Mercator, Lon. of Origin = -86.5, Lat. of Origin = 34.625, WGS84. 4.
Save the image as TIFF format. 5. View the GeoTIFF information using ISRU > Display Header.
Note the Y origin value is approximately 4 million meters. That is the distance from 0 lat. Given
the ProjNatOriginLatGeoKey value of 34.625, the Y origin should be approximately 14825
GeoMedia Image Professional
324 1-6PT0MO GeoMedia Image
Professional
GeoMedia Image Professional
Advanced Image Registration affine
transform fails
Registering a scanned paper map to a Mercator projection. An affine transformation should
work well, but gives very inaccurate results (average error is approximately 1km in Y). It's
necessary to measure 16 points and use a 3rd-order polynomial to get acceptable results for
registering to the map gradicule.Workflow: 1. Open provided .gws, restore connection to
provided .mdb. 2. Note 6 points at specific lon/lat locations. 3. Use Insert > Interactive Image to
place provided .tif file in the warehouse. Place the image to the left or right of the 6 points. 4.
Select the image. 5. Select GeoMedia Image Pro > Utilities > Advanced Image Registration. 6.
Verify the model is set to Affine. Create a new registration. You should be able to place point
pairs, using 6 vector points and readily identifiable points in the scanned map. 7. After 6 point 325 1-89Y45Z GeoMedia Image
Professional
Generate Registration Grid Creates a
Distorted Grid When it Spans 180
Degrees Longitude
The Generate Registration Grid in GMIP creates a distorted elongated grid when it crosses the
180 degree longitude line. The DCAFE and Compass programs regularly encounter charts that
cross the 180 degree longitude line which necessitates generating registration grids across the
180 degree longitude line to guide registration of these charts. Grid is placed in Geographic
Lon/Lat coordinate system.
326 1-89NNWS GeoMedia Image
Professional
Raster Maps Crossing the 180 Degree
Longitude Line cannot be Registered
Raster maps that are in a Mercator projection cannot be registered using GMIP if they cross the
180 degree longitude line. They register fine on either side of the 180 degree line. If control
points are used on both sides of the line however, the map gets stretched and distorted badly.
The DCAFE and Compass programs regularly encounter maps crossing the 180 degree
longitudinal line therefore this is a critical SR for these programs.
This product is new in Image Scout bundle hence there are no CRs listed.
There are no CRs resolved as this version is a compatibility release with GM Pro 2014
There are no CRs resolved as this version is a compatibility release with GM Pro 2014
GeoMedia 3D
GeoDEX
GeoMedia VPF Dataserver