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.
114
Embed
Image Scout 2014 Issues Resolved - Hexagon Geospatialcommunity.hexagongeospatial.com/hmrkh95973/attachments...Adderess_Text_3034 - 476 258 3. Street_Names_3022 - 2 38 4. The user found
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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
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
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
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
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
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