GeoMedia 15.00.0000 Issues Resolved This report contains CRs for GeoMedia 15.00.0000. GeoMedia contains CRs filed against assorted product releases of GeoMedia, GeoMedia, GeoMedia Fusion, GeoMedia Grid, GeoMedia Parcel Manager, GeoMedia Public Works Manager, and GeoMedia Transaction Manager. These products were merged into GeoMedia 14.00.00. The Filed Against column indicates the previous product that the CR was filed against. GeoMedia 2015 1 1-72AO7R GeoMedia Improper help displayed for Edit/Open Hyper text commands on Data window in GeoMedia only. 2 1-72M8CZ GeoMedia Legend group is in disable state after invoking GeoMedia Application Improper help displayed for Edit/Open Hyper text commands on Data window in GeoMedia only. After selecting Data cell with Hypertext in Data Window, focus to Table tab. Select the hyper text command and press F1. Improper help is displayed. Legend group is in disable state after invoking GeoMedia Application without any warehouse connection made. (See the attachment) 1
GeoMedia 15.00.0000 Issues Resolved 3 1-8XQMZ9 GeoMedia GeoMedia fails to connect to file geodatabase that ESRI can connect to successfully GeoMedia is unable to connect to an ESRI File Geodatabase folder that ESRI ArcGIS Explorer (version 2.0.0.1750) can open and display features from successfully. As per the related SR the geodatabase file was created by the customer by exporting from an ArcSDE database using a post ArcGIS 10.0 version of software. Here are the steps to reproduce the problem along with additional details regarding the error: 1. Extract the LH.gdb folder structure from the LH.gdb.zip file to a folder on your local machine. 2. Start GeoMedia 2014 and open a new blank geoworkspace. 3. Select the New Warehouse Connection command and select the File Geodatabase Read-Only connection type. 4. For the File Geodatabase workflow folder browse to the location of the LH.gdb folder on your machine and select it. Then click OK to make the connection. This will result in the standard Unable to connect to the database. Please verify that your warehouse-connection parameters are correct and try again. message, but if you select the More button on the message dialog you will see the additional message Coordinate System Translation Failure. 5. By checking the Properties of the LH.gdb features in ArcGIS Explorer I was able to determine that the coordinate system used for at least some of the tables is S-JTSK_Krovak_East_North (102067) which I believe is an ESRI specific code as per http://spatialreference.org/ref/esri/102067/. However even if you specify a.ini file for the connection that assigns a coordinate system that matches the code the same error occurs during the connection. The coordinate system and.ini file I used for this test are included in the ESRI102067.zip file. The customer notes that the LH.gdb file geodatabase folder contains no tables at the root level and they surmise that this may why GeoMedia fails to connect. 2
GeoMedia 15.00.0000 Issues Resolved 4 1-97G36Q GeoMedia 5 1-9A36JR GeoMedia Display Properties Dialog fails to display inserting new feature Text Print queues not available in Layout Window Display Properties Dialog fails to display inserting Text even though the "Display Properties dialog for new features" is enabled. This happens with all R/W warehouses. 1. Open.gws and connect to a R/W warehouse with Text features. 2. Enable the "Display Properties dialog for new features" option. 3. Insert Text to see problem. The "Display Properties dialog for new features" dialog does not dispaly after inserting text. Print queues not available in Layout Window. Error: unable to connect. In Map window all queues are available and are displayed in the form. 6 78601_GM GeoMedia MapInfo server unable to connect to a customer s seamless MapInfo table When attempting to make a MapInfo warehouse connection to the 'Carto_Area_Seamless.tab' file provided by the customer an "Unable to connect to the database." error occurs and the information from the More button is "No MapInfo Tables are available in the workspace directory". As the name implies, the 'Carto_Area_Seamless.tab' file a seamless MapInfo table that references base 'Carto_Area.tab' tables in the various subfolders. This same 'Carto_Area_Seamless.tab' file can be displayed successfully in MapInfo 6.0 so it appears to be a valid file. Likewise GeoMedia Pro can successfully read other MapInfo seamless tables such as the 'DC_AREAS.TAB' sample seamless table delivered on the MapInfo product CD. To reproduce the problem: 1. Extract all the files from the 'SR1-233357291_sdabell.zip' file with the 'Use folder names' option enabled to insure that the folder structure is maintained for the base tables referenced by the seamless table. 2. Open GMPRO and attempt to make a MapInfo warehouse connection to the 3
GeoMedia 15.00.0000 Issues Resolved 'Carto_Area_Seamless.tab' file. This will result in the connection failure with the "No MapInfo Tables are available in the workspace directory" message. 3. Open the same file in MapInfo or the MapInfo viewer and note that the table is opened successfully. 7 1-4Y79SX GeoMedia 8 1-8ZMS8G GeoMedia Unwanted columns are copied to Excel. A command added to the Quick Access toolbar is added again each time GeoMedia is started When you are in the data window and select noncontiguous columns and copy these into Excel- if you have the Tools > Options Copy data window column headers to clipboard, all the column headers are pasted into Excel; not just the columns you copy. If you add the command 'Tile Horizontally' to the Quick Access Toolbar so that it is the last command on the toolbar (i.e. it is the right-most command icon), each time you start the GeoMedia application another copy of the command icon is added to the Quick Access Toolbar. Thus if you start GeoMedia ten times after initially adding the command you will see eleven 'Tile Horizontally' icons in a row on the toolbar. The commands appear to be added in perpetuity each time GeoMedia is started. 4
GeoMedia 15.00.0000 Issues Resolved 9 1-91LGU9 GeoMedia Size Property Not Stored When Size Less Than 2 pt User has noted that the size property for labeling does not store values which are less than 2 points. For example, if specify a size value such as 1.0 and select OK to accept, the value is accepted and the text is placed BUT the value (1.0) is NOT stored in the dialog upon return to review the label properties. The value is changed to 2.0 and a tooltip error is displayed with flashing exclamation symbol. There may be error checking logic that does NOT match the accepted value ranges for size property; this however is a major usability issue since the size value is reset (not stored) upon return to review the label properties. Workflow: 1. Label Manager > Enable (check) feature to Label > Properties > Set the Size property to 0.5 2. Select OK 3. Select Properties button again Observation: The Size has reverted to 2.00 with flashing exclamation symbol which reads on tooltip: The specified value was out of the allowed limits. It has been set to the closest allowed value. The error however seems incorrect in that labels can be produced at sizes such as 1.0 and 0.5 Additional Notes: I/Map Editor user workflows often require that users be able to specific sizes such as 1 pt. Some sources seem to indicate that the native GeoLabel command from MapText can accept values as low as 0.5 pt. Standard GeoMedia Text and Symbols can be sized quite small. The numeric range as noted by the older label error message system is "...numeric value between 0.000028346 and 2834.646." This error and range is NOT used by the newer label commands. 5
GeoMedia 15.00.0000 Issues Resolved 10 1-93ZBTV GeoMedia 11 1-979X1V GeoMedia Application Crash With Find Address and GeoCode Addresses Commands Label > Toggle Dynamic > Rotate View: Crash to desktop, loss of work GeoMedia stops working without the chance to save with the following error when using the Find Address or GeoCode Addresses commands: PGeocCmd Run-time error '7' Out of memory The problem has been observed on Win7 systems where the Display settings for the system has been set to a value other than 100%. For example, the user sets his display to "Medium - 125%" then the Crash is observed when attempting to use Find Address or GeoCode Addresses commands (normal use). Workflow: 1. Win7 system, use Control Panel > Display to set display to 125% 2. Create GeoWorkSpace and select Analysis tab > Find Address 3. Setup the Geocode Address Settings, (for example use/select C:\WarehousesGMAGTrainingCenterlineStreetData.xml as the Geocoding directory). 4. Select OK after setting up addressing parameters. Observation: GeoMedia application stops working. No opportunity to save. Same problem occurs with GeoCode Addresses command. GeoMedia crashes to desktop if, after toggling on dynamic labels, the user rotates the mapview and then causes a refresh. Open USSampleData, zoom to 1:250,000 in an area with cities. Select Label > Label Manager, turn on labels for 'Cities' (City_Name), turn off 'Obstacle' for other feature classes. OK. Label > Toggle Dynamic Now right click in Map View, Display Properties, set rotation <>0.0. Apply, then Close. Use the Pan command to force an update. GMPro crashes to desktop without opportunity to save. Reported by customer on 14.00.0000. 6
GeoMedia 15.00.0000 Issues Resolved 12 1-981O9J GeoMedia "Error loading list of printers" when XPS Document Writer or Send to One Note 2010 printer exists Using File>Print from a layout window in a Citrix session will result in the error message 'Error Loading List of Printers' when the Microsoft XPS Document Writer or Send to One Note 2010 printers are present on any client machine that has an active Citrix session. It should be noted that File>Print from a Map window does not exhibit this same issue, but the Batch Plotting utility does. 13 1-9BGIC4 GeoMedia Batch SmartStore Publishing fails in 2013/2014 and corrupts specified profile A SR was filed reporting that the batch publish of Smartstore files fails and corrupts the profile specified in the command line. I have tested with the latest GeoMedia 2014 version and confirmed the behavior described in the SR. For instance if you specify a command line path like the following SmartPub.exe -p C:\Warehouses\Rivers.ssp -l C:\Warehouses\RiversSSP.log the output will include only a single file in the C:\Warehouses folder with the name Rivers.ssp and if you open Rivers.ssp with Notepad.exe or another text editor you will see that it includes the text that should have been written to the log file (i.e. RiversSSP.log) appended to the original profile information. In other words the profile file specified (Rivers.ssp) was appended with log file information thus corrupting the profile and no SmartStore files were published. By contrast if you use the same command line with GeoMedia 6.1 (06.01.11.13), the expected Rivers.ddc, Rivers.cdt, and Rivers.csf file are output along with the RiversSSP.log file 14 1-9SDU7I GeoMedia Layout Out Window Drawing tab Commands Cut, Copy and Paste Do Not Work The buttons for Cut, Copy and Paste found under the Drawing tab in Layout do not work. Using <CTRL> keys such as <Ctrl> c and <Ctrl> v do not seem to work; the only workaround seems to be right-click mouse actions. 7
GeoMedia 15.00.0000 Issues Resolved 15 1-5W6U75 GeoMedia MicroStation v8 Connection: Display CAD Files Does Not Display Grouped Text Elements Summary: The Display CAD Files command fails to display grouped text. User has noted that after using Tools > Display Design Files that certain graphic items are not served into the GeoWorkspace. In the data case given the user has Microstation v8 text elements which have been grouped using Microstation Edit > Group command. Apparently this group command ties the selected elements together as group by simply placing a cell header (Type=2). Notes: The grouping of the graphic elements using Edit > Group in Micostation creates a cell header where the Name (cell name) is NULL, making the grouping difficult to set the scanning criteria. In the case given the users text cell groupings have multiple Microstation Layernames. Apparently GeoMedia exposed the GField LayerName from the first element. It is assumed that the first layer name in the grouping can vary making the scan criteria difficult. Example data given. First try creating a new.gws file and use Tools > Display design files to display the contents of Extract.dgn. Notice how the text does NOT display. If we instead display the graphics from Extract_Ungrouped.dgn then the text items display. 16 1-67AVM0 GeoMedia Définir le fichier de configuration du Warehouse Problème for CAD Serveur When using the Définir le fichier de configuration du Warehouse for CAD data the dialog is missing information that allows the user to select the version of the CAD data to use. This in turn allows the user to progress to the next dialog where the Mots-cles disponibles (keywords) are not displayed. Problem is specific to version 06.01.11 French and is a regression from 06.01.09 French. Problem does not seem to occur on English or German versions. Workflow: 1. Start > All Programs > GeoMedia > Utilitaires > 2. Definir le fichier de configuration du Warehouse 3. On the dialog, Set the Serveur de donnees to : *CAO Observation: The Informations su le warehouse section is not populated. It should list options for AutoCAD, Microstation8 and Microstation7 * Should CAO be 8
GeoMedia 15.00.0000 Issues Resolved spelled CAD? 17 1-6J297C GeoMedia 18 1-7TYEPI GeoMedia WFS Service with holes does not display with WFS Data Server. Publish to Smartstore fails if dot. appears in UNC share server name Using the customer data, there are many polygons with holes. This data is published to a WFS Service and then displayed using the WFS Data Server. it appears the almost all of the polygons with holes do not display. See the Notes and Attachments tab for further information and test data and comparison testing after modifying customer's data. Setup an UNC path such as \\ccity.biz\fileserver\transfer\falconers\test; i.e. server name has a dot. in it - Publish Smartstore Setup output Smartstore warehouse to use UNC path with dot. in server name. Our source was from SQL Server (old GDO dataserver) Smartstore claims to finish. Note: tested with and without Coordinate system transform, including to csf held on UNC path with dot. in server name - Check output csf file is not created error in log file vwbuildingfootprint: An error encountered while reading the feature class information. Failed to publish csf, ddc, log all published. csf failed to publish. - Change output path to unc path where server name does not have a dot. in it such as \\test\mytest\test - Publish Smartstore Works. 9
GeoMedia 15.00.0000 Issues Resolved 19 1-8KK7HG GeoMedia 20 1-8NK8G5 GeoMedia French or German Regional Settings, attempting to access properties for locations hangs GeoMedia Select Set Properties on feature served from Microstation V8 design file crashes GeoMedia Reviewing the Properties of named locations hangs GeoMedia application when using French or German regional settings format. The only recovery found is to terminate the application forcefully using Task Manager to Close the GeoMedia application. Oddly, the Locations does seem to operate correctly for Spanish (Spain) regional setting so the issue may be more than just the decimal separator used. Overview: a) Regional Settings using French b) If you save a location using Location tab, > Name Location command, the named location will be written to locations.xml file with center coordinates such as the following which despite the very high percision seems valid: <Location Name="New York City" CenterX="-73.8857162570115" CenterY="40.6781489490614" c) If you now select this named location using the Locations command and select OK (even without making any properties changes), the center coordinates are re-written to the.xml as: <Location Name="New York City" CenterY="40,6781489490614" CenterX="- 73,8857162570115" Notice how decimal separator is now a comma. Additionally the X and Y values are swapped! As a side note the 13 significant digits is rather high for application that only show 7. If the user attempts to display this named location (from step c), GeoMedia will hang and force the user to terminate without the opportunity to save. After using the Display CAD Files command to serve the customer provided Microstation V8 design file, if you invoke Select Set Properties for any feature in the file GeoMedia will crash. The workflow to reproduce the problem and details of the crash are provided below. 1. Create a new blank geoworkspace. 2. Select the Display CAD Files command. 3. Choose Microstation V8 from the CAD type drop down list. 10
GeoMedia 15.00.0000 Issues Resolved 4. In the CAD files frame, use the Browse button to navigate to the folder containing the Rogan_DataCut_Assets.dgn file. 5. In the Available files list place a checkmark next to the dgn filename to select it. 6. Select the OK button on the dialog. 7. When the message box is displayed stating Coordinate system file not specified. Do you want to continue? select the Yes button. 8. After the features are displayed in the Map window, double-click on any of the displayed features to display the Select Set Properties dialog (or alternately select a feature then choose the Select Set Properties command from the menu/toolbar.) This will result in a Microsoft Visual C++ Runtime Library error message if you are running GeoMedia Classic that states Runtime Error! Program:...rgraph\GeoMedia \Program\GeoMediaClassic.exe abnormal program termination When you click OK to dismiss the message a second message with a GeoMedia Classic application title will be displayed stating GeoMedia Classic application has stopped working. If running the GeoMedia.exe version (ribbon bar) only the second message is displayed with text GeoMedia Classic replaced with GeoMedia in the message. When researching this issue I found that a crash will occur (with the same error messages) when serving the design file if you select the option to Display with native symbology on the Advanced tab of the Display CAD Files dialog 11
GeoMedia 15.00.0000 Issues Resolved 21 1-8PWEC9 GeoMedia Poorly Formed WMS GetMap Request For Certain WMS Services Data from the following 2 example WMS connections fails to display in GeoMedia 2013. http://mymachine/?servicename=print_topo25&client=geomedia&request=getcapabili ties&service=wms&version=1.1.1&login=my&password=mine http://mymachine/?servicename=orto_sommer_2012&client=geomedia&request=getc apabilities&service=wms&version=1.1.1&login=my&password=mine Version 6.1 GETMAP: 6:56:46 PM 12/5/2013 - CGMWMSRasterEngine::WMS_Display [Get Map]: http://mymachine/print_topo25?ignoreillegallayers=true&transparent=true&login=m y&password=mine&servicename=print_topo25&client=geomedia&version=1.1.1&req UEST=GetMap&SERVICE=WMS&LAYERS=dtk_kort25_graa_254dpi&STYLES=&FORMAT=i mage/png&transparent=true&bgcolor=0xffffff&exceptions=application/vnd.og c.se_blank&srs=epsg:4326&width=784&height=284&bbox=2.47833,53.0109326086 957,17.5575,58.4744 The Get Map 2013 looks like: 6:57:02 PM 12/5/2013 - CGMWMSRasterEngine::WMS_Display [Get Map]: http://mymachine/print_topo25?ignoreillegallayers=true&transparent=true&login=\m y&password=my&client=geomedia&servicename=print_topo25&version=1.1.1&requ EST=GetMap&SERVICE=WMS&LAYERS=dtk_kort25_graa_254dpi&STYLES=&FORMAT=im age/png&transparent=true&bgcolor=0xffffff&exceptions=application/vnd.ogc. se_blank&srs=epsg:4326&width=642&height=233&bbox=2.22632171809193e- 05,4.76205309854627E-04,1.57721706009285E-04,5.25284472476839E-04 Notice what is assumed to be an incorrect BBox specification in the 2013 GetMap Request which prevents the data from correct spatial display/transformation. The problem does not occur for all WMS services, for example the following WMS service works for both GeoMedia version 6.1 AND GeoMedia 2013 connections. http://mymachine/?servicename=my_temp&client=geomedia&request=getcapabilities &service=wms&version=1.1.1&login=my&password=mine 12
GeoMedia 15.00.0000 Issues Resolved 22 1-8RV24N GeoMedia Label Manager > Dialog accepts font sizes which are outside of the valid range When defining the font size for labels in label manager, the range of valid values is from 2pt to 72pt, in 0.5pt intervals. The user is able to key in values outside this range (1pt, 72.5pt) and the dialog accepts the value, allowing the user to 'OK' the dialog. When the user returns to the dialog, the value is changed (1 is changed to 2, 72.5 is changed to 72) and a flashing yellow triangle with a '!' appears over the 'pt' units field. Throughout GeoMedia, we consistently disallow invalid input by inactivating the 'OK' button on the dialog. The behavior of this form is non-standard and should probably be change to check for valid input before activating the 'OK' button. Testing shows that the form still accepts values less than 2, but changes them to 2 when the OK button is selected. It also shows that it now accepts values greater than 72 (up to 2834.646) which is a great improvement. Values greater than this are not accepted, but the error states Font size must be a numeric value between 0.000028346 and 2834.646. This error is wrong, or the software has a bug, since values less than 2 are still not accepted. 13
GeoMedia 15.00.0000 Issues Resolved 23 1-8W2ZL9 GeoMedia Geometry Information crashes GeoMedia when labels from Label Segments query are selected for review When the Label Segments query command is used to generate labels for a feature with many segments, if the Geometry Information command is then used to review the geometry for those labels the GeoMedia application will crash. The workflow to reproduce the problem is as follows: 1. Open a new blank GeoWorkspace. 2. Make a new warehouse connection to the USSampleData.mdb Access warehouse. 3. Use Add Legend Entries to display the States feature class in the Map window. 4. Run the Vector > Text and Labels > Label Segments command. 5. Choose the States feature class in the dropdown list and execute the query with the default parameters by clicking the OK button. 6. After the query completes, use the cursor to select a set of labels from one of the States, then choose the Geometry Information command (Home > Geometry Information). This will result in a crash of the GeoMedia application. If you run Label Segments on a feature that has a relatively small number of segments (such as some of the short Interstates in USSampledata), the Geometry Information command will sometimes display the dialog successfully without crashing, but upon selecting the Close button on the dialog to dismiss it the crash will occur. Likewise it is possible to both display the geometry and close the Geometry Information dialog successfully if the number of segments that were labeled is very small. The 'LabelSegmentsStates.gws' in the Attachments tab can be used to see the problem by performing step 6 only in the workflow. 14
GeoMedia 15.00.0000 Issues Resolved 24 1-8WRNV3 GeoMedia 25 1-8X6H2L GeoMedia GM 2014 crashes when executing 'Display CAD Files' command using.dwg file Toolbox/Conflation/ Linear Link Zoom creates Type Mismatch error messages even if queue is active GM 2014 crashes when executing 'Display CAD Files' command using.dwg file. Data attached to CR. Reproduce: 1. Open blank.gws 2. Select 'Dsplay CAD Files' command and choose the File_DWG.dwg 3. GM crashes I am able to display successfully the File_DWG.dwg file using the DWGViewer(DWGSeePro2013.exe). Customer's description: One customer has requested us to integrate a CAD file (.dwg) and to provide them a Shapefile export after some queries in GeoMedia. You will find the CAD file in the attachment. The DWG file is in DWG2010 format (supported by GM). When I execute the 'Display CAD File' command, GM crashes. Toolbox/Conflation/Linear Link Zoom command creates "Type Mismatch" error messages even if queue is active. Reproduced on English and German GeoMedia 2014 SP1. 15
GeoMedia 15.00.0000 Issues Resolved 26 1-8XRIQH GeoMedia GeoMedia is unable to display features from a File Geodatabase that ESRI can display successfully GeoMedia is unable to display features from an ESRI File Geodatabase folder that ESRI ArcGIS Explorer (version 2.0.0.1750) can display successfully. As per the related SR the geodatabase file was created by the customer by exporting from an ArcSDE database using a post ArcGIS 10.0 version of software. Here are the steps to reproduce the problem along with additional details regarding the error: 1. Extract the.gdb folder structure from the.gdb.zip file to a folder on your local machine. 2. Start GeoMedia 2014 and open a new blank geoworkspace. 3. Select the New Warehouse Connection command and select the File Geodatabase Read-Write connection type. 4. For the File Geodatabase workflow folder browse to the location of the.gdb folder on your machine and select it. Then click OK to make the connection. 5. After the connection completes select the Add Legend Entries command. Note that there are only two feature classes listed (jaskyna and obec). By contrast if you connect to this same.gdb file geodatabase with ESRI ArcGIS Explorer you will see that in addition to the two tables shown in GeoMedia at the root level, there are three additional nodes/folders that contain many more tables that are not listed by Add Legend Entries in GeoMedia, but can be selected and added to the legend in ArcGIS Explorer successfully. 6. In addition if you attempt to Insert a new instance of one of the two available features classes in GeoMedia an error message is displayed stating GDO ServerKit Recordset Source The user does not have permission to execute the operation. Choose the Insert Feature command and try to insert a new obec area feature to see this error message. The customer reports that the Edit Geometry command produces the same error. 16
GeoMedia 15.00.0000 Issues Resolved 27 1-8Y86ST GeoMedia Regression - Cannot insert ECW file in 2013 or 2014, inserts fine in 6.1 Customer reports failure inserting ECW file using Raster > Insert Georeferenced Images. This has be reproduced here. ECW file, ancillary data attached. Open a blank.gws, connect to world.mdb. Load provided.csf file as the.gws CS. Select Raster > Insert Georeferenced Images, browse to location with provided ECW image. GeoMedia will be unable to insert this file, regardless of whether the georeferencing method is 'Automatic', 'Other with internal CS', 'World file' or 'Other with external CS'. Examination of file header reveals an EPSG code of 31287, which is probably the source of the problem. 17
GeoMedia 15.00.0000 Issues Resolved 28 1-8YLZQR GeoMedia Schema Manager Does Not Create GPickList Table User has noted that Schema Manager, Construct Feature Class option does NOT create a properly populate GPickList table when the target warehouse does not already contain a proper GPickListTable. This behavior is a regression from GeoMedia Fusion version 6.1 Workflow using supplied data. 1. Manage Data > Schema Manager The schema here has a feature defined called "Poles" which has an attribute called "Pole_Type" associated to the picklist called "Pole_Type_Code_List". 2. Click on the Construct Feature Classes... button and select OK on the next dialog to create the feature class. Obsevation: The following message is posted: Cannot find "INGRPickLists" in the "GAliasTable" table. Do you want to create the "GPickListTable" table? Side Note: This dialog is asking a Yes / No question but the dialog has only "OK" as an option. 3. Select OK to create the "GPickTable" table. Observation: The following message is posted: GeoMedia The Microsoft Jet database engine cannot find the input table or query 'GPickListTable'. Make sure it exists and that its name is spelled correctly. Observation: The feature(s) are created without their associated picklist. If the user manually creates GPickListTable, then the Construct Feature Classes option will correctly associate picklist values to the feature class created. GPickListTable columns are all TEXT (255), columns listed below: FeatureName FieldName PickListTableName ValueFieldName DescriptionFieldName FilterClause 18
GeoMedia 15.00.0000 Issues Resolved 29 1-904KNA GeoMedia GM Grid in GeoMedia 2014 does not process.grd/.dgn files. Regression from 2013 In attempts to using the GM Grid Import Wizard for importing.grd with.dgn coordinate file previously successful imported by GM Terrain, you get an error message: Cell resolution must be greater than zero encountered. When attempts are made to use the GM Grid Create Elevation Footprints command, the Log Summary reads: Information (3/11/2014 9:03:27 AM): Footprint creation process started. Warning (3/11/2014 9:03:27 AM): Error processing file: D:\Projects\TOD217a\Data\MTA_files from NAVO\TEST_DATASET_COV_M_U100.GRD: Could not load the file, D:\Projects\TOD217a\Data\MTA_files from NAVO\TEST_DATASET_COV_M_U100.GRD. Information (3/11/2014 9:03:27 AM): Process completed with warnings. The input data files and GM Terrain workflow are attached. 30 1-90WTTX GeoMedia Labels Fail To Display With Errors When Using Certain Regional Language Settings When the user is using a custom decimal and grouping separator then Labeling > Toggle Dynamic fails to display labels. Example 1: If using English(USA) Regional Settings with Advanced tab settings of: Decimal Separator: "," Grouping separator: "." Results in the following Error when use Toggle Dynamic --------------------------- GeoMedia Failed to perform label placement: CFG_PARSE_ERROR Failed to dynamically label the map. --------------------------- Example2: Spanish (Spain) Regional Settings with Advanced tab settings of: Decimal Separator: "." Grouping Separator: "," Results in the following Error when use Toggle Dynamic --------------------------- GeoMedia An error was encountered loading data for Dynamic Labels legend entry. Do you want to continue loading remaining legend entries? --------------------------- followed by: --------------------------- GeoMedia Error creating unique value thematic classes. Failed to dynamically label the map. ----------------- ---------- 19
GeoMedia 15.00.0000 Issues Resolved 31 1-90WU3J GeoMedia 32 1-91302Y GeoMedia GRID-Vectorize results in partial overlaying area features ESRI File GeoDatabase Date Fields Not Served Correctly Vectorize to feature class with Output type: Complex Polygon Non-Partitioned Boundary results in area features which are overlaying each other. Please see attached doc file with workflow and data set for testing. Date fields in ESRI File GeoDataBase are not read properly. In the given customer data set, all values are returned as: 12/30/1899 12:00:00 AM. In ArcGIS the Date attributes work as expected. As well we imported the Data to PostGIS via FME. As a comparison, the date values are seen/served correctly by GeoMedia PostGIS data server. See also Attachment for screen shots and example FGDB data. 33 1-914800 GeoMedia 2014 VPF dataserver to valid VPF formatted data corrupts the attributes 2014 VPF Dataserver connection to valid VPF formatted data corrupts the attributes for multiple feature classes. The attached zip file provides lists of feature classes with corrupted attributes and two VPF libraries used in the test. 1. Open the CR 1-914800.gws and correct path to VPF libraries. 2. Double click on any of the displayed features to see attributes zeroed out from attached 2014 VPF dataserver test results.doc document. 20
GeoMedia 15.00.0000 Issues Resolved 34 1-93A9X4 GeoMedia Certain ESRI FGDB Text Fields May Be Incorrectly Mapped to GDO Data Type Data supplied by Intergraph Services organization shows that ESRI FGDB text fields may be mapped to LENGTHS which exceed 255 characters. This issue prevents users from directly outputting such features using Output to Feature Classes command. For example attempting to write to Access will result in the error: Error: Failed to create table in the underlying database. Please verify the table name and attribute names. (More Info: The size of a field is too long.) This error does not occur with all FGDB data sets; other similar FGDB text fields seemly map to GDO text correctly. The Native to GDO field mapping of the ESRI FGDB design specification suggest that the Native "String" is a text field represents a series of alphanumeric symbols. This can include street names, attribute properties or other textual descriptions. If length <= 256, gdbtext If length > 256, gdbmemo According to http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/file_geodatabase_size_ and_name_limits/003n0000007q000000/ The max length (width) for text values in native ESRI FGDB data is 2,147,483,647 characters. User expectation is that if a text field in ESRI FGDB data exceeds 255 characters, the data should be mapped as MEMO. In the case of the given example data where the text field maps as text length of 2147483647, the max length "value" is only 40 characters. Example Workflow Using Supplied Data (see also Attachments) 1. Create blank GeoWorkSpace and use Manage Data tab, Warehouse > New Warehouse Connection to create a File Geodatabase Read-Only Connection to the supplied data. 2. Select the Manage Data tab, Features tab 3. Review the Attributes for the AADT_20 feature class. Observation: Notice the data type and length assigned to the ROUTE_ALIAS field. TEXT (21474836..) Notice how this overly large value seems to match the max text size supported by FGDB native text. 21
GeoMedia 15.00.0000 Issues Resolved 35 1-93I7AA GeoMedia Static Label generation not working with SQL Server Native When attempting to create static labels using the label manager. The following error occurs, "Failed to generate static labels". The feature is coming from a SQL Server Native database however when export to feature class is used to export it to an access warehouse the labels work correctly. This error was reproduced by CEWoodbury using the GMan SQL database on tsdb64. He "ran a trace, but nothing is happening at the database level prior to failure. I think you will need to get development to tell you why the error is occurring." 22
GeoMedia 15.00.0000 Issues Resolved 36 1-93Z3H9 GeoMedia Cannot Create Union of Certain FGDB Data User provided ESRI FGDB data shows the following error when attempting to Union the data: --------------------------- GeoMedia Unable to retrieve output query from union operation. The coordinate systems do not match for field Shape. ----------------------- ---- Suspect that FGDB data server is failing to correctly set/define coordinate system of features in certain data cases. The coordinate system of the the 2 feature classes match when observed in the Manage Data tab, Features command (Feature Class Definition). In this data case, the user has defined a single.ini file where the coordinate system keyword references the same coordinate system (.csf) file for each file.gsb folder. Workflow Using Supplied Data: 1. Copy.zip to C:\Warehouses and extract all to the C:\Warehouses folder. C:\Warehouses\1-550831295 should be created. 2. Open FGDB_Union_Issue.gws 3. Select Analysis > Union 4. On the Union dialog select STREETCENTERLINES from each connection. Observe the error "Unable to retrieve output query from union operation. The coordinate systems do not match for field Shape" Despite the.ini definition referencing the same coordinate system (.csf) file for both.gsdb features, there are some odd behaviors: Oddity 1: a) GeoWorkSpace Coordinate System name = "EPSG: 2915" b) Feature Class Definition Coordinate System for the feature = "EPSG: 2915 1" Oddity 2: If export the features to Shape File, one shape file feature will be set to "EPSG: 2915" while the other shape file will be set to "EPSG: 2915 1". It is expected that Shape Files should be output/transformed to the Coordinate System of the GeoWorkSpace. The exported shape files also have the same issue with Union in both 2014 and version 6.1. An important footnote to this data is that if the user does not define the.ini file with the coordinate system keyword, the Knox.gsdb data cannot be displayed. It throws an coordinate system error as noted in related CR 1-8XQMZ9. 23
GeoMedia 15.00.0000 Issues Resolved 37 1-9412AO GeoMedia 38 1-947MGT GeoMedia Function "Void- Flächen erkennen" creates error message on German GMPro 2014 geoworkspace throws error when closing the application: "Error Exiting Application. Source:GMCmdSup Function "Void-Flächen erkennen" creates error message on German GMPro 2014 Using function "Void-Flächen erkennen" (Detecting Void Areas) brings up error message "Ressource mit dem Bezeichner '10' nicht gefunden" in German GeoMedia Pro.. Please see attached screenshot. This does not occur on English GMPro 2014 This problem exists on German GM Pro. I have a customer that has newly installed GeoMedia Essentials Version 14.00.0001.00064 in Windows 7 Service Pack 1, 64bit. She creates a GeoWorkspace with different types of data connections usually Access, CAD Files and GeoMediaSmartStore. She works with for a while and creates a layout window. She is able to put in the Map into a Layout Window. She closes the application. But when she opens the same geoworkspace again and makes changes to the Map window and opens the layout window and then closes the Application, The Application gives her this Error: "Error Exiting Application. Source:GMCmdSupt Description:Method '~' of object '~' Failed" And In the Application Log it points to this DLL as the ntdll.dll. Please look into the Attachment for more detail of SR 1-551214121l. Dataset is in attachments of that SR also. Open the GWS and restore some of the connections and then go into the layout window and hit zoom and you will get the crash. 24
GeoMedia 15.00.0000 Issues Resolved 39 1-95SVN2 GeoMedia KML/KMZ file is not properly displayed on GeoMedia 2013 KML/KMZ file is not properly displayed on GeoMedia 2013. I will include the KMZ file and an image showing how It is seen in Google Earth. -------------- Above is SR description. Looking at the Style Properties for the 'maps_combined_probability' legend entry, we see that the 'Source = Icon'. If we look at individual features in this FC, we see 'Icon' attribute is undefined. Appears that the issue is they have 8 separate.png raster files, one for each feature in the 'maps_combined_probability' FC, and we have no way of mapping individual features to the correct.png file? Also there seems to be an issue with the 'Access_Points' feature (maybe maps_combined_probability as well?) where the OverrideColor is defined, but perhaps should not be. The customer's.kmz and a screen cap of the appearance in Google Earth is provided as attachment 40 1-95TCEG GeoMedia Problems viewing files from a Gdatabase Problems viewing files from a Gdatabase. Problem: two features have a field defined as text for the key instead of autonumber. Data in \\mymachine \Customer Files\1-553937239. Rest of features work fine. Data fine in Arc. Features with issues are CommonPlace and CommonPlaceXY 25
GeoMedia 15.00.0000 Issues Resolved 41 1-96ORR9 GeoMedia Only top (root) level FGDB features can be edited/inserted. Edits to non-root features fail. Non-root feature class from an ESRI File Geodatabase connection cannot be edited. Specifically an error message is displayed stating The user does not have permission to execute the operation. when attempting to make any type of edit, including inserting a new feature, editing the geometry of an existing feature, or changing an attribute value for an existing feature. By contrast it is possible to successfully edit features from rootlevel feature classes from the same File Geodabase connection without any error. To reproduce the problem, use the workflow below. 1. Insure that you have GeoMedia MR version 14.00.0002.00095 installed. 2. Extract the ZBGIS_Modra_v_10_2.gdb file geodatabase from the attached ZBGIS_Modra_v_10_2.zip file to a folder on your machine. 3. Start GeoMedia version 14.00.0002.00095 and make a new File GeoDatabase Read-Write connection to the ZBGIS_Modra_v_10_2.gdb file. 4. Use Add Legend Entries to add the jaskyna and cesta feature classes to the legend. The jaskyna feature class is at the root level of the file geodatabase, while the cesta feature class is in a subcategory under TopoDataset. 5. Double-click on one of the cesta linear features in the Map window to open the Select Set Properties dialog. Change one of the attribute values. For instance if the AUT value is 1 change it to a value of 2 (or if the AUT value is 2 change it to 1) then click OK to save and exit the dialog. This will result in an error message stating The user does not have permission to execute the operation. 6. Now select the Insert Feature command and choose cesta as the feature to insert. Place several points to digitize a line. Then double-click to end the feature. If the Select Set Properties dialog appears, click OK to accept the defaults. This will result in a message stating GDO ServerKit Recordset Source The user does not have permission to execute the operation. 26
GeoMedia 15.00.0000 Issues Resolved 42 1-96PXBK GeoMedia WFS data server malformed WFS transaction requests It seems that the update and delete transaction requests for WFS-T generated by WFS data server don t pass validation against relevant schemas. In case of the update operation, the order of the <Filter> and <Property> elements in the generated requests is swapped. According to the schema, the <Property> element should precede the <Filter> element. In case of the delete operation, the <Filter> element in the generated request is in the http://www.opengis.net/ogc namespace. According to the schema, it should be in the http://www.opengis.net/fes/2.0 namespace. The requests generated by WFS data server and corresponding error messages are attached for reference. The bugs have been found using the following WFS-T instance: http://mywfs/wfst/service.svc/get 43 1-96ZWKY GeoMedia Update Attributes Inoperable in Session Workflow - ActiveX Component Steps provided by region show how it is very easy to cause the Update Attributes command to stop working in the GeoWorkSpace session. 1. Open any GeoWorkSpace with a read-write connection. 2. Select Vector > Update > Update Attributes 3. Expand (+) any connection and select / highlight any feature. 4. Collapse (-) the connection 5. Click on any of the attributes to update cells (right side) The following error is posted and now the Update Attributes command can no longer be used in the current session- PAttrCmd Run-time error '91': Object variable or With block variable not set If attempt to select Update Attributes again the following message is posted:--- GeoMedia ActiveX component can't create object Can also see the message above while exiting. A hung GeoMedia.exe will be running in Process list which must be ended manually. Problem seems to occur in all versions since and including 27
GeoMedia 15.00.0000 Issues Resolved 6.1.11 44 1-97WRAZ GeoMedia 45 1-980VSX GeoMedia Batch Plotting hangs on Printer > Properties Using XYZ translator to create footprints results in geometry being flipped by Elevation Workbench. GeoMedia Pro Batch Plotting on Windows 7 X64: When opening Printer Properties dialog Batch Plotting is locked and has to be killed via task manager. This is independent of the printer used. -Start Batch Plotting and select USSample.GWS in Sheet selection - Add Sheet1 - Go to File - Print - For example select "Microsoft XPS Document Writer" - Select printer "Properties" Observation: There is way to exit the properties dialog! Task manager must be used to kill both Batchplot.exe AND GeoMedia.exe When the XYZ translator is used to create footprints, the resulting geometries are causing the data to flip when processed by the Elevation Workbench. When the user attempts to create footprints a large collection of XYZ files, the resulting footprints look correct however when these are used as input into the Elevation Workbench the result DEM files are flipped. 28
GeoMedia 15.00.0000 Issues Resolved 46 1-983363 GeoMedia Customer has this error from GM via their custom command: " Encountered an improper argument." This is a custom application with various custom commands. I have looked at a couple of the files, and it does appear that the commands were created without using the command wizard. The product has about 6 or 7 custom commands. Two particular commands are being used: Display Center and Administration Console. If the Refresh Configuration button on the Administration Console is selected several times and also making the Map window active between those refresh configurations, the error of: GeoMedia : Encountered an improper argument occurs. When we click on OK button or the error message, it re-throws the same error message box several times upon which, it either finally crashes or needs to kill the GeoMedia instance from task manager. This error is not leaving any traces in EGIS custom command code and no call stack information is displayed 47 1-98EOOU GeoMedia Grid > Setup / Install > Creation of "C:\GeoMedia Grid Tutorials" Please see attachments for full report of the issue. Customer has an issue with the way GeoMedia 2014 installs files that is a potential show-stopper for their approval process. Apparently, if a product installs files on the root of C:, it is a major violation of the security guidelines they have to follow. Please read customer's email attachment, and development comments attachment. 48 1-98PFBN GeoMedia Russian characters not correctly displayed in FGDB data connections In Select Set Properties and Data Window attributes with Russian characters from a File Geodatabase connection (FGDB) data format is displayed as question marks ("???"). Able to display the Russian characters in ARC GIS Explorer with no problem. Machine Regional settings are set to Russian for the change system locale. Also, the GM UNICODE registry settings are set per the installation guide. Sample Russian characters available in attached word document as well as the file geodatabase file. 29
GeoMedia 15.00.0000 Issues Resolved 49 1-990NPB GeoMedia Problems with Russian character symbols There are several problems displaying Russian characters in GM 2014. In the Data Window title bar. Also, in file paths like The folder path: C:\Warehouses\ДЗЗ the customer and I reproduced. I set my WIN7 64BIT machine to Russian regional settings. To reproduce: 1. Set machine regional settings using the Regional Settings Dialog.png 2. Open the Dagestan_for_webmap.gws and correct path to the Dagestan_for_webmap.mdb. Notice the problems referencing HSV Reproduced problems.png. Customer's description: The problem is the import of raster image to GeoMedia from the folder which name contains the Russian symbols. I tried to open USSampleData.tif from such folder - I had an error (when I open it from the folder without Russian symbols - it works). I've already added the existing font to the register. It doesn't help. Moreover I has a strange symbols on the GUI instead of Russian letters. The full version of GM is 14.00.0002.00095. The customer's OS : Windows 7 64 bit RUSSIAN. The folder path: C:\Warehouses\ДЗЗ 30
GeoMedia 15.00.0000 Issues Resolved 50 1-99MNN0 GeoMedia Problem with Insert> Legend in Layout window When using Insert>Legend in the layout the error 'Invalid key 3' is given. The legend dialog eventually comes up but is not populated. When the user clicks 'Add' the error 'Invalid key 32' is given and application will crash. This occurs when Format and Location is set to English (south Africa) and South Africa respectively in the Regions and Languages controls. Workflow to reproduce: 1. Access Region and Language via Control Panel 2. change format to equal English (South Africa) 3. change Location to equal South Africa 4. Open USSampleData.gws 5. In layout window add map frame and map. Select map and Insert>Legend Observe that error 'Invalid key 3' appears. 6. Ok and then unpopulated legend dialog appears. 7. Choose 'Add' and observe that 'Invalid key 32' appears. user is unable to add legend to layout window 8. Repeat workflow after changing Format to be English (united states) and location to be United States. Application and layout window Work as Designed. 31
GeoMedia 15.00.0000 Issues Resolved 51 1-99APAU GeoMedia Installing GM 2014 on machine with G/Tech 10.1.0003.2800 breaks G/Tech Installing GM 2014 on machine with G/Tech 10.1.0003.2800 breaks G/Tech The critical problem is GeoMedia registering some dlls such as the "Praster1.dll" which replaces the Praster1.dll of GTech so when the customer uses a legend which includes OGC WMS services, the display for GTech WMS layer fails. Running repair on GTech doesn t repair/work on this problem. This is the dll GTech should use instead of using the one in the video. Video attached to the CR. Also, if G/Tech 10.1.0003.2800 or 10.02.0002.09001 is installed on a machine and GM 2013/2014 is installed on that machine GM installation removes/deletes in the registry the GFramme folder under HKLM\Software\Wow6432Node\Intergraph\Applications. Running a "Repair" rewrites the GFramme folder to the HKLM\Software\Wow6432Node\Intergraph\Applications folder and G/Tech can be used. Customer is upgrading from version 6.1 to GM 2013 or GM2014 where there are about 600 machines to upgrade which already have Gtech 10.1 installed on their machines, so it is not suitable for the customer to uninstall Gtech10.1 and then install GM2014 and the reinstall Gtech10.1. Have reproduced this in HSV. Customers comments below: I have experienced serious problem with my customer EPM, while updating machine that has already installed Gtech 10.1. It seems both products share some common DLLS and after installing GeoMedia 2013 or GeoMedia 2014 some Gtech DLLS are replaced and therefore Gtech doesn t work properly. So far the workaround for this has been to repair the Gtech installation, but the customer has been not complete satisfied with this option as this involves a lot of additional time for the IT resources responsible of making the update. Besides there is a conflict with Gtech utility OGC WMS Caching Server Configuration Utility, when installed on a server that has installed GeoMedia Web Map. 32