Senior GIS Developer Position Requesting Experience with Intergraph Products

The folks from GeoSearch Inc. sent me a job posting for a GIS Developer that I thought I’d pass along to the readers.

Direct inquiries/resumes may be sent to: Jessica@geosearch.com

Intergraph Releases PostGIS GeoMedia Data Server at Hexagon 2011

At the Intergraph Hexagon, 2011 conference, Intergraph released a GeoMedia data server for PostGIS. For those that haven’t heard of PostGIS, it’s a FANTASTIC open source and free spatial database. Behind, Oracle Spatial, it’s probably the most powerful spatial database in the market.

From the PostGIS web site:

PostGIS adds support for geographic objects to the PostgreSQL object-relational database. In effect, PostGIS “spatially enables” the PostgreSQL server, allowing it to be used as a backend spatial database for geographic information systems (GIS), much like ESRI’s SDE or Oracle’s Spatial extension.

The data server can be downloaded from CodePlex. The data server is very easy to install. If you already have an existing PostGIS database, you only need to run the “Register.bat” batch script and the data server will be installed in GeoMedia. Like GeoMedia/Oracle, for read-only connections, you don’t even need to create a metadata schema! If you’d like to be able to PostGIS data, you’ll need to use the database utilities that come with the data server and setup the application metadata.

For those that are new to PostGIS, Intergraph provides a very nice PostGISGDOUserInfo.txt file that will guide you through the process of first installing PostGIS and then installing the data server. For those that would like to learn a lot more about PostGIS, there’s a recently released book named “PostGIS in Action“. Although I haven’t seen it myself, I’ve read many good things about it online.

One last note. If you’re a Windows Vista+ user, the data sever will NOT install unless you escalate a DOS window to “Administrator”. To do this, do the following:

1) In the start menu, type “CMD”

2) Right click on the result at the top and select “Run as administrator”

You’ll know that it worked as you’ll get back a “success” message box as opposed to a “error” message box.

Advertisement

Intergraph Launches Security, Government & Infrastructure User Forum

From an email I received yesterday

Intergraph is pleased to announce the availability of the new Security, Government & Infrastructure User Forum website.  We encourage you to utilize the forum website as a means of exchanging information with your peers.

Access to the Security, Government & Infrastructure User Forum website is available from any of the product support web pages or via the direct link below:

URL: http://userforums.intergraph.com/support/
Login: Same as your Siebel username and password.

Instructions for using the forum are available from the “Help & Guidelines” link on the User Forum page. Likewise, if you have any questions or feedback regarding the forums please send an email via the “Contact Us” tab.

Thank you,
The Intergraph® Customer Support Team

I’ve checked this out a few times, but haven’t had a chance to dig in much. Looks promising and it’s definitely a good sign from Intergraph.

HUGE Enhancements to GeoMedia Help Files

For a change of pace, I was working with GeoMedia Pro a little today. I was looking to use the REPLACE functional attribute that was introduced in 6.1.6 and had a few questions. So I went into the trusty help looking for the usage, and WOW, things have changed! The initial help appears to be much more organized and logically laid out. For instance, I receive a full description of the functional attribute. Below that each element of the functional attribute is VERY well explained. No more having to hunt and peck through the help just to understand the different elements of the functional attribute…very cool! But now for the best part – the examples. The examples actually push you off to the Intergraph Knowledge Base. Although the information appears to be a part of the Intergraph Knowledge Base that I’ve known about for a long time (and incidentally, that you need to login to access), the link in the help doesn’t require you to login.

When I clicked on the “REPLACE Example” link in the help, I was brought to a page with a whole host of examples. Here’s a copy and paste from the EXAMPLES sections:

Abstract

The following example shows how to use the REPLACE functional attribute.  This applies to GeoMedia products version 6.1.6 and later.

Code Example

REPLACE(“THIS-IS-EXAMPLE-TEXT”, “-”, “ ”) equals THIS IS EXAMPLE TEXT

REPLACE(“THIS-IS-EXAMPLE-TEXT”, “-”, “ ”, 6) equals THIS-IS EXAMPLE TEXT

REPLACE(“THIS-IS-EXAMPLE-TEXT”, “-”, “ ”, 1, 2) equals THIS-IS EXAMPLE-TEXT

REPLACE(“THIS-IS-EXAMPLE-TEXT”, “I%-”, “ ”, 1, 0, TRUE()) equals THIS IS EXAMPLE-TEXT

REPLACE(“THIS-IS-EXAMPLE-TEXT”, “i%-”, “ ”, 1, 0, TRUE()) equals THIS-IS-EXAMPLE-TEXT

Very cool!

A couple of notes:

1. Since the examples are written on a web page, it’s likely you won’t be able to just copy the example and paste it into the Functional Attributes dialog. You’ll instead need to first paste it into Notepad or some other text editor and clean-up the example. So, if you find your example not working correctly in GeoMedia, make sure to clean it up first.
2. When I logged into the Intergraph knowledge base directly (as opposed to accessing it through the help), initially I wasn’t able to find the same knowledge base entry. If you’re going to search the knowledge base directly, make sure to choose “(All GeoMedia Products)” under the “Product” section. I chose “GeoMedia and GeoMedia Professional” and didn’t get any records returned. As soon as I chose “(All GeoMedia Products)”, the same knowledge base entry I found in the help was also available in the Knowledge Base result set.

Next GeoMedia Minor Release 6.1.6 Available for Download

Sorry, a bit late on the update. Intergraph released GeoMedia Minor Release 6.1.6 in the middle of last month. I posted it on the GeoMedia Wiki, but didn’t get a chance to post it on the blog. On a side note, if you subscribe to the GeoMedia Wiki “Product Announcements and Software Updates” page on the wiki, you’ll receive an email whenever that page is updated. So when a product announcement is posted e.g. the release of a minor release, you should receive notification via email.

GeoMedia’s New Search Tool

Fast Note by Jeff Hobbs: The functionality that Adam describes below was has been in the product for some time. Maybe as far back as 6.0. I just wanted to make sure the readers all understand that you do NOT need to upgrade to 6.1.6 to use this functionality.

The folks at Intergraph recently introduced a new search tool in GeoMedia that brings my ability to develop data maintenance workflows of this sort to a new level.  It is often the case that the most difficult part of a data maintenance or integration workflow is not in linking the records after you find the right place on the map, or in digitizing the geometry, but in actually searching and/or panning and zooming the map to where it needs to be to allow entry of the new spatial data record.

Here is an example… I have a spreadsheet that I acquired from the local power company that specifies locations (in non-standard English descriptions) for every light pole in my client’s city.  All that my client wants to do is create a GIS point feature that is attributed with the unique ID for each light pole from the spreadsheet and inherit the other attributes from the spreadsheet.  It is easy to digitize a point for each pole once you know where to put it.  The difficult part of the workflow is to turn this English descriptive location into a meaningful location on the map  for each record.

In the old paradigm, I would use the attribute query tool to predefine a SQL statement in which someone can search for a parcel or a street to help the person doing the data entry find the location of interest.  This was difficult for the user because in order to find anything at all, the user cannot do anything to the SQL that would mess it up – like forget to put the closing apostrophe at the end of the statement if it is a text field.  However, with the new search tool, (available in version 6.01.06.19), I can predefine a search, pin wildcards to each side of the user-input search term, and GeoMedia will provide an input box for the user to enter the search string.  The result is that it is easy for a person completely unversed in SQL to reliably execute a search query in GeoMedia against an available table or feature class.

This may seem pedestrian to GIS veterans, but I really think that this is a huge leap forward in the usability of GeoMedia workflows for folks less versed in database.  And let’s face it – it means that us GIS veterans have to do less of the drudgery of data creation.  So… create those workflows, pass them off to the interns, and go have yourself some shrimp cocktail.

For more details on exactly how to use the search tool, open up GeoMedia , go to Help –> GeoMedia Help Topics, and type ‘search’ on the index tab.

Bulk, Automated Geomedia Editting: split a lot of polys based on a line layer

A little more than a year ago, I did a project for a left leaning political organization that had an interest in developing an automated means to create (and recreate) a national layer of election precincts to support activities like political canvasing.  Click here for a more complete case study on my company’s website.

One of the basic challenges in this project was to find an efficient way to split hundreds of thousands of polygons (census blocks) using a separate, and rather large layer of line geometry – in this case, statewide commercial street data.  Although I had the option to do this work with custom code in Oracle Spatial, I wanted to use Geomedia in order to avoid the Oracle customization time sink.  How to do it in Geomedia?  The solution is easy, but not at all obvious (at least to me).  Here is the recipe I came up with:

1. Load the feature class that you want to split (in my case, census blocks), and the features that you want to split by (in my case, streets). Also, and this is important, make sure that the “Display Properties Dialog for New Features” button is unpressed.

2. Select the census blocks and initiate the split tool in Geomedia.  Notice that a new toolbar appears with four buttons on it… split by point, split by line, split by polygon, and split by selected features.  Click on “split by selected features”.

3. Turn OFF locatability on the census blocks layer (the layer to be split).  Be sure to do this without unselecting those features.

4. Turn on locatability for the streets layer, and select the features that you want to use as a basis for splitting census blocks.

5. Double-click somewhere – anywhere – on the map window and let Geomedia do its thing.  Depending on the complexity of the features that it is analyzing and the sheer number of records, it may take a little time to complete.  If you didnt take my advice from step one and ignored the “Display Properties Dialog for New Features” button, then it might force you to click OK for every newly split feature.

The result in my case is census blocks seemlessly split based on a seperate layer of line work.  Perfect geometry, perfect topology between features, with no slivers or gaps… a thing of beauty.

Welcome to the Blog: Adam Lodge

I’m pleased to announce that Adam Lodge of Farallon Geographics has asked to be an author on the blog. Needless to say, I accepted his offer!

I first met Adam when he was with San Mateo County, CA and I was working with the City of San Jose. While I was with Intergraph, Adam served as the president of the Northern California Intergraph Geospatial User’s Community. Adam has been working with GeoMedia for many years (maybe even longer than me) and has a ton of knowledge about both Intergraph products like GeoMedia, GeoMedia Parcel Manager, GeoMedia Grid, and GeoMedia/Hansen interface. Additionally, he has a lot of experience with open source products like Geoserver, OpenLayers, and PostGIS. Finally, he’s been working with Oracle Locator/Spatial for a number of years.

I’ll let Adam tell you more in his own words. But needless to say, I’m very happy to have someone else post on the blog. If anybody else is interested in contributing to the blog, please email me and we’ll add you as well!

GeoMedia Viewer Now Available for Download!

In the way old news section of the blog, it was brought to my attention a while ago that you can now download the GeoMedia Viewer from the Intergraph web site. For a long time, you had to make a request from product support and then Intergraph would send you a CD with GeoMedia Viewer on it. As of late last year or early this year that changed. You can now download it from Intergraph Support site. https://support.intergraph.com/Product/GeoMediaViewer.asp Please note, although it’s on the Intergraph’s support site, I do NOT believe you need to login to download. So, if you’re looking for a tool that will do any of the following:

• Read a GeoMedia/GM Pro workspace
• Connect to Oracle Spatial and SQL Server
• Have the same look and feel as GeoMedia and GeoMedia Pro
• Free

You’re definitely in luck. I’d encourage you to download it and give it a try. Please note that if you’re going to install GeoMedia Viewer on a machine already running GeoMedia and/or GeoMedia Pro, I believe Intergraph recommends you install the least functional piece of software first. In other words, if you’re going to run (not sure why you would want to) GeoMedia, GeoMedia Viewer, and GeoMedia Pro all on the same machine, you’d want to first install GeoMedia Viewer, then install GeoMedia Std, and finally install GeoMedia Pro. If you don’t follow this pattern, you might find that some of your functionality is lost.

From the GeoMedia Viewer site:

GeoMedia Viewer is an easy to use, FREE GIS software application for desktop viewing and distribution of geospatial data. It allows an organization to maximize the value of its geospatial data by extending availability to novice users who wouldn’t otherwise have access because of the barriers of purchasing and learning how to use a full GIS software application.

Analyze Geometry

Sorry about the long time between posts. I’m not giving up on blogging, but, believe it or not, it does take a lot of time….

Anyhow, I’ve been playing a little with the Analysis > Analyze Geometry command. I can’t say I use it all the time, so I’m not sure when this changed. It may have been a long time ago. I’ve always found it hard to get lat/long coordinates from my state plane coordinates. Yes, I can do this one off by just clicking on the map and getting a coordinate readout from the “Precision Coordinates” dialog, but what if I wanted to have lat/long for 10,000 points. That was much harder.

You can do this with functional attributes. In fact, I posted an article on www.geomediawiki.org on how to do it. It was actually copied for the most part out of the GeoMedia online help. However you can also do this with the Analyze Geometry command.

1. Launch the command (Analysis > Analyze Geometry)
2. Choose a point feature class. If you have lines or polygons, use the CENTERPOINT functional attribute to create points from the line/area geometry.
3. When you select the point feature class, you will see the “Analysis Options” dialog populate. In the dialog you will see “Geographic Coordinate” and “Projection Coordinate”
   
4. If you check “Geographic” you will get lat/long. If you check “Projection” you’ll typically get easting/northing. NOTE: you can set the output coordinate format in the “Units and Formats…” dialog in the same Analyze Geometry dialog.
5. For points you have options for Azimuth, Bearing, Geographic Coordinates, Projection Coordinates, and Height. Height assumes you have the Z elevation populated in your geometry
6. If you work with lines, you’ll have options for Length, Azimuth, and Bearing
7. If you work with areas, you’ll have options for Area, Perimeter, and Area/Perimeter ^2

All in all, this is much easier than having to write a functional attribute.

Intergraph Schema Remodeler

With the last blog post on Safe Software’s FME suite, I would be remiss to not discuss Intergraph’s own Schema Remodeler utility. The Schema Remodeler utility comes as part of GeoMedia Fusion.

[RANT]On a complete side note…IF Intergraph would NOT hide their marketing information behind a login and password, then I’d have links to the products. The last I heard, David Holmes had said that he hoped to have at least the splash pages out from login/password shortly after the end of the conference. We’re going on almost a month now…anytime soon would certainly be nice. Actually, I found what I think is a hidden link to a bit of literature on the software.[/RANT]

Anyhow, GeoMedia Fusion is a great tool for doing data cleanup, attribute validation,  and conflation. The schema remodeler utility comes with GeoMedia Fusion and is a stand alone utility that provides you with the ability to migrate data from one source to another and to bulk export from the GeoMedia environment. For those that have heard of Intergraph’s Data Warehousing Tools, the schema remodeler utility is the re-branded (and enhanced) Data Warehousing Tools. Schema Remodeler is one of my favorite Intergraph tools and I almost always use it at least once a week.. As of late I’ve set it up to take my Trimble GPS text files and load them into my Oracle Locator database. In the schema remodeler utility, you can do a number of things including re-mapping and reordering columns from one source to another (think migrating a database from Access to Oracle or SQL Server); exporting a seamless Access feature class into a gridded Bentley Microstation V7 environment; and updating columns using functional attributes, creating a subset of the the data using temporal and attribute queries, and modifying the source geometry using an analytical merge so you can export the Oracle data to create a shapefile (all in one transaction).

When you look at the functionality of Schema Remodeler, it’s really pretty amazing at how much you can do with the utility. Now, how do I compare it to FME? It’s hard to say as I’ve used Schema Remodeler off and on for the last five years and I’ve only use FME a handful of times. In my eyes, they both attempt to do similar things. The biggest difference in my eyes has to do with the number of file formats supported (Schema Remodeler only supports the standard GM data server while FME supports at least 150 different GIS data types) and how detailed you need to get. Schema Remodeler is great for many things, however it’s only a utility. FME on the other hand is a complete software solution. Its so goal is “spatial ETL (Extract, Transform, and Load”. It should also be mentioned that since you can’t buy Schema Remodeler by itself (it only comes with GeoMedia Fusion), FME is actually quite a bit cheaper than Schema Remodeler. So, if you’re looking exclusively for “spatial ETL” functionality, I personally would go with FME. However if you need to do some pretty advanced conflation, a lot of automated data cleanup, and attribute validation, you really should be looking at GeoMedia Fusion. If you do that, it’s really nice to know that Schema Remodeler comes as part of Fusion and may answer many of your ETL needs.

Couple of Cool Utilities

A little while ago, I was passed a couple of utilities that I wanted to share with the community.

1) CSF2ASCII.exe – This tool will read any .csf file and write out the contents (projection information out to a a ASCII text file or an HTML file. This is also available in the download widget on the left hand side of the screen.

2) Database Inventory – This will analyze any warehouse connection and provide a complete list of the GeoMedia objects that are available in the connection. I found this one a bit hard to use…but it could definitely be useful if you needed to get a better feel for the contents of a new connection…especially a database. Great for documentation and learning. This too can be downloaded from the widget on the left hand side of the screen.

Heading to Intergraph 2008

Just found out my travel for Intergraph 2008 has been approved! So, I’ll be heading out to Las Vegas, NV probably on Monday, June 1. Who else is going? Maybe some folks want to get together for drinks one night?

Reply and let me know!

GeoMedia Wiki

Was reading a post made by Zym in reply to one of my entries. It mentions using Google as a reference for a good source of documentation. He also mentions the idea of developing a wiki. There has been talk of developing a wiki focused on GeoMedia suite. I envision it to be a centralized place where users can find examples, documentation, and pointers for more ideas. Additionally, I envision it being a collaborative effort with some content coming from Intergraph but also quite a bit of content coming from the users.

As I’m sure you all know, the real power of a wiki is the ability for many people to collaborate. So, with that said, I’d like your feedback.

1. Would you find it useful?
2. Would you help edit it?
3. Would you add your own content (e.g. examples, workflows, ideas, etc).
4. Would the requirement that you had to login turn you off from editing/adding content?

Please provide your feedback as I could really see this happening…if there’s enough interest.

Thoughts?

Intergraph Minor Releases

I will be posting different things that were covered at the GeoMedia 6.1 product launch soon… However one thing that was covered was the idea of “minor releases”. They are new with the 6.1 release and have replaced the “hotfix” nomenclature…with one big difference. With few exceptions, hotfixes were designed to just be a set of patches/fixes to GeoMedia. On the other hand, minor releases are designed to be both patches AND new functionality. As far as I understand it, Intergraph is trying to get the users functionality much faster (which is always very nice). So, to do this, they will be rolling the functionality in minor releases. Now, it sounds like Intergraph might also be rolling future expansion packs into a minor release. Not totally sure on this one (any comments from Intergraph??).

Anyhow, with that said, I’m a little late in posting. However Intergraph has released minor releases for GeoMedia 6.1, GeoMedia Pro 6.1, and GeoMedia Viewer 6.1. Here’s the complete this of fixes and enhancements for GeoMedia Pro 06.01.03.08. This was copied right from the web site. You can assume the enhancements will change depending on your version of GeoMedia.

The problems summarized below have been fixed in GeoMedia Professional Minor Release #1 version 06.01.03.08.

• Resolved a problem where a Double Click of the mouse would add extra points if coincident. JTS TR# 39108

• Resolved a problem where the results of a Spatial Query were incorrect after unloading and loading of the query. JTS TR# 64432

• Resolved a problem where new Mapwindow names were not being honored with a Spatial Intersection Query. JTS TR# 65490

• Resolved a problem where the Generate Base Geometry command was returning incorrect results when the source was a DynSeq query. JTS TR# 69778

• Improved memory usage in the Library system. JTS TR# 70495

• Resolved a problem where the Unload command would not release an application command from memory. JTS TR# 70650

• Resolved a problem where a Resolve Text Conflicts query was not handled by Geomedia WebMap Publisher. JTS TR# 76668

• Resolved a problem where Show Legend Entries returned an error for GeoMedia Grid raster objects. JTS TR# 76710

• Resolved a problem where the application would crash when attempting to load a SQL Server SLOPE feature. JTS TR# 80793

• Resolved a problem where the application would crash with a Dr. Watson error when re-projecting a WMS raster to the Layout sheet. JTS TR# 82250

• Resolved a problem where a PPInsOps dialog was being displayed when data was loaded. JTS TR# 82739

• Resolved a problem where a ‘remote server machine does not exist’ error message was displayed when invoking the Style Definition dialog within Batch composition. JTS TR# 82763

• Resolved a problem where importing a GLS where the map frame contains only thematics in the legend would fail with a ‘No geometries found’ error message. JTS TR# 82831

• Resolved a problem where an automation error would be observed when digitizing a feature using the Arc by start, Point on Edge, End placement mode. JTS TR# 82993

• Resolved a problem with HKLM R/W Access affecting the use of analytic merge and functional attributes. JTS TR# 83012

• Resolved a problem where a ‘PProServiceApplication-defined or object-defined’ error message repeatedly occurs when the Redigitize command is continued. JTS TR# 83026

• Resolved a problem where the Batch Plotting utility crashed when the Y value was deleted on the setting dialog. JTS TR# 83054

• Resolved a problem with the queuing options locator box width field on a machine running a German operating system. JTS TR# 83058

• Resolved a problem where the user could not place an area feature if the default height was changed during placement. JTS TR# 83091

• Resolved a problem where an ‘Object variable or Width block variable not set’ error would display when the user clicked in the Map window after a Continue geometry was invoked. JTS TR# 83160
  1. Create an Access Read-Write connection to USSampledata.mdb.
  2. Add RouteShield feature class to the map Window.
  3. Select Route Shield legend and from right click menu select Style Scaling as Paper.
  4. Zoom to a single feature in Map window .
  5. Select the single feature and invoke Edit > Geometry > Continue
  6.Click in Map window before Place Point at Angle dialog appears.

• Resolved a problem where the Text File Preview pane would display three dots at end of line that do not exist. JTS TR# 83172

• Resolved a problem where a spatial filter by select set was failing in some cases with a WFS connection. JTS TR# 83187

• Resolved a problem where no feature classes were displayed for a GML File that would display in other applications. JTS TR# 83189

• Modified the WMS dataserver to support WMS 1.3.0. JTS TR# 83201

• Resolved a problem where an automation error would occur when the backspace key was pressed during a continue geometry function. JTS TR# 83212

• Improved scalability of data loading (Add Legend Entry). JTS TR# 83216

• Resolved a problem where a Patterned Line with Offset could not always be located. JTS TR# 83338

• Resolved a problem where a blank error message would be displayed when performing a copy parallel on an edited Cartographic Geometry feature. JTS TR# 83349
  Steps To Reproduce:
  1. Invoke GMPro and connect to USSampelData.mdb.
  2. Add States to Map Window.
  3. Select a States feature and invoke ‘Create Cartographic Geometry’ command. Hit ESC.
  4. Perform Copy Parallel operation on any of the States feature displayed in Map Window with target set to ‘States’.

• Implemented support for ARCS image format. JTS TR# 83358

• Resolved a problem where using the Options command (via the File Locations tab) to change the default GeoWorkspace or Warehouse folder location to a folder named with the Japanese hyou character results in the error message “Error displaying the file location for GeoWorkspace Files” or “Error displaying the file location for Warehouse Files” respectively. JTS TR# 83396
  1. In the folder Warehouses create a folder with the name the Japanese character hyou, Unicode 0x8868, SJIS 0x955c
  2. Initialize GeoMedia Pro.
  3. Invoke the Tools > Options command and select the File Location tab.
  4. Select Warehouse Files from the File Types list and click the Modify button.
  5. Browse to the folder with the hyou character name as created in step 1. Click OK to save the change. This will result in the message “Error displaying the file location for Warehouse Files” will be displayed and the default warehouse location will not be changed.

• Resolved a problem where Arabic Unicode text would display backwards JTS TR# 83398

• Resolved a problem where the Precision Coordinate and Spatial Filter dockable controls displayed blank in gws. JTS TR# 83484

• Resolved a problem where non-existing lines display as the user zooms in and out. JTS TR# 83509

• Resolved a problem where Japanese characters were displayed incorrectly if the text file that contains them was saved as ANSII. JTS TR# 83510

• Resolved a problem where ‘Read-only features cannot be edited’ error message would display when the user attempted to Insert Text with the Place Along Existing Geometry orientation. JTS TR# 83518
  Steps to reproduce:
  1.Invoke GMPro blank GWS; make an access R/W connection to USSampleData.mdb
  2.Add States FC to the MW.
  3.Invoke Insert>Text command.
  4.Select StateNameLabels FC from dropdown, key in ‘Test’ named text to insert and select ‘Place along existing geometry’ as the orientation mode.
  5.Once click on the Texas state and move over the state to place the label.
  6.Now at some point the label comes very much closer (even the label may be disappeared), click on that particular point to place the label.

• Added OGC with GML 3.2 compliancy for the GML data server, WFS data server, and the ExportToGML commad. JTS TR# 83523

• Resolved a problem where the user could not move or delete Cartographic geometries with an Arcview connection. JTS TR# 83552

• Resolved a problem where Japanese text was rendered incorrectly in the map window. JTS TR# 83579

• Resolved a problem where GMPro cannot display 2525B fonts from GeoDex. If the user uses the font inside of a style for a point feature, the symbol display is blank. Also, the style dialog cannot display the characters in its character map. JTS TR# 83603

• Resolved a problem where inserting a feature would not permit the selection a feature class from a category. JTS TR# 83608

• Resolved a problem where a search would fail when a Spatial Filter was applied and then removed. JTS TR# 83613

• Resolved a problem where the application would crashes when copying a legend from a Resolve Text Conflict query in the GWS to the library JTS TR# 83615
  Steps to reproduce:
  1.Open a blank GWS; Make an Access r/w connection to USSampleData.mdb.
  2.Invoke Tools>Resolve Text Conflicts command.
  3.Select StateNameLabels from ‘Resolve Text Conflicts in’ field and click OK on the Resolve Text Conflicts dialog taking default inputs for others.
  4.Invoke Legend>Name Legend command and name the legend as ‘Legend1’.
  5.Create a new Access library named ‘Test’ and invoke library organizer dialog.
  6.Check the Legends check box in GWS contents pane and try to copy Legends to Library contents pane.

• Resolved a problem where creating a patterned line, the symbol placed along a line is rotated by twice the amount of the mapview JTS TR# 83627
  When
  Steps to reproduce the problem
  1. Invoke a blank geoworkspace and connect to USSampleData.
  2 Add the interstates feature class to the legend.
  3. Insert a new interstate feature that has a horizontal line and a veritcal line.
  4. Zoom in on this feature
  5. Edit the line style for the interstate feature by leaving the existing line style and adding a new line style.
  6. Move the new line style to the top and make it a pattern line style.
  7. Change the point style to a FSM symbol with the symbol file Transportation and select the symbol “Interstate Route Shield (color)” with a point size of 16.
  8. On the pattern style GUI select a spacing of 10 mm, and okay out of all the dialogs.
  9. Rotate the view by 45 degrees.

• Resolved a problem where the Cartographic grid was placed incorrectly in the batch plotting- compose workflow. JTS TR# 83646

• Resolved a problem where the display of characters with a Library grid was not correct JTS TR# 83647

• Resolved a problem where the WFS data server can’t connect to a public WFS site. JTS TR# 83697

• Copying a search query from a library and performing search operation throws a ‘Method of Object Failed’ error message when pressing the key for first time JTS TR# 83706.
  Steps to reproduce:
  1.Open a Blank GWS; make an access R/W connection to USSampleData.mdb.
  2.Invoke View>Searches cmd and create a new search ‘Search of Counties’ with filter value ‘ANNULRAIN >= [value] AND STATE_NAME = ‘[StateName]’;’
  3.Create a new Access Connection library named ‘Test’ and copy ‘Search of Counties’ from GWS to Test Library through Library Organizer dlg and dismiss the same by clicking Close button.
  4.Invoke a new GeoWorkspace through File>New GeoWorkspace command.
  5.Create a New Library Connection to the Test Library and copy search ‘Search of Counties’ from Test Library to GWS contents through Library Organizer dlg and dismiss the same by clicking Close button.
  6.Invoke View>Search command, Select ‘Search of Counties’ from the drop down tree view.
  7.Enter ’10’ in value field and press tab to enter into StateName field.
  8.Enter ‘Texas’ in StateName field and press key.
  9.Repeat steps from 4 to 8.

• Resolved a problem where the Symbol file editor would incorrectly display Japanese symbol names. JTS TR# 83721

• Resolved a problem where a Select Locatable Off on a Legend Thematic and GWS would terminates the session. JTS TR# 83756

• Resolved a problem where the user was unable to dismiss an error message when performing a Redigitize Text operation. JTS TR# 83769

• Resolved a problem where an ‘An error occurred during copy’ message on invoking Copy attributes for a newly created feature class. JTS TR# 83811
  Steps to reproduce:
  1.Open blank GWS; make an access R/W connection to USSampleData.mdb
  2.Create a new feature class named ‘Line’ of geometry type Line.
  3.Add Interstates FC to the MW. Select any of the features on the MW and invoke Edit>Feature>Change Feature Class.
  4.Select Target feature as ‘Line’ and dismiss Change Feature Class dialog by clicking OK button.
  5.Delete Interstates and add Rivers FC to the Legend.
  6.Invoke Edit>Attribute>Copy Attribute Definition dlg and set the below following, then dismiss the dlgs by clicking OK button
  Line: Target Features
  Rivers: Source Features
  Rivers Type, River Name: Attributes to copy
  7.Select the Line feature and any one of the Rivers feature on the MW using key.
  8.Invoke Edit>Attribute>Copy Attributes.

• Resolved a problem where the WMS Data Server was incorrectly serveing WMS 1.3.0 data. JTS TR# 83842

• Resolved a problem where hidden legend entries would remain selected. This caused the Fit by Legend Entry and Select by Legend Entry commands to return invalid results. JTS TR# 83847

• Resolved a problem where invoking LRS Precision and QE dockable controls would result in an ‘Object Variable’ error message. JTS TR# 83883
  Steps to reproduce:
  1.Invoke GMPro blank GWS; make an access R/W connection to LRSMorgan.mdb
  2.Invoke Tools>LRS Precision Location dlg and set ‘LRS’ feature from LRS features in drop down list.
  3.Click on Properties button and set the following
  Primary: nlfid
  Start measure: frommeasure
  End measure: tomeasure
  4.Dismiss both LRS Properties and LRS Precision dialogs by clicking OK button.
  5.Invoke Tools>Queued Edit.
  6.Select File>Exit and click ‘No’ on the confirmation message displayed.

• Resolved a problem where digitizing a feature(relatively big) in the map window using ‘Arc by Start, Point on Edge, End’ placement mode with the insert feature command active, the user would observe that the feature was not displayed properly. JTS TR# 83891
  Steps to Reproduce
  1)Invoke GMPro, make an access r/w connection to ‘USSampledata.mdb’
  2)Invoke Insert> Feature cmd, select ‘Interstates’ feature from insert feature dockable control and change placement mode to ‘Arc by Start, Point on Edge, End’.
  3)Digitize a contiguous arc feature in map window, double click to end feature and make sure that command is active.
  Observation:
  Digitized feature is not displayed properly in map Window. Here mainly problem with refresh. Use ‘Select Tool’ command to terminate insert feature command and perform Fit All operation. Observe that feature is displayed properly. Some times while performing an Undo operation using Edit > Undo command, observe some part of feature is still displayed in map window. Now perform ‘Fit All’ operation then feature disappears from Map window.

• Resolved a problem where the full syntax for DISTANCE was not shown at the bottom of the dialog. JTS TR# 83907

• Resolved a problem where the DISTANCE function would not accept a Boolean for a 2D parameter. JTS TR# 83908

• Resolved a problem where the user would get a ”One or more selected image files did not support the selected georeference mode’ error when using Insert Georeferenced Images with a standard TIFF with a world file. JTS TR# 83913

• Resolved a problem where the application would crash with an ‘Invalid procedure call or argument’ error while digitizing a feature in map window using the Insert Traverse command after previously digitizing a feature with default settings using Insert Traverse. JTS TR# 83942
  Steps to Reproduce
  1)Invoke blank GWS, Make an access r/w connection to ‘Sanfran.mdb’
  2)Invoke Insert>Traverse command, select ‘Alleys_NR’ FC from “Primary Feature class” and “Component Feature class” list box control
  3)Digitize feature using “Use Map” option, Click on ‘Close feature’ to close digitized feature and select ‘Apply’ button to apply insert traverse entries into feature. Observe that feature is displayed in map window.
  4)Click on ‘Save’ button in ‘Insert Traverse’ dialog then ‘Save as’ dialog is displayed. Give name of file as ‘Test’.
  5)Now again Invoke Insert> Traverse cmd, Make sure that keep values as default values and select ‘Load’ button then load ‘Test’ file which is saved in earlier.
  6)Click ‘Close feature’ button to close feature and Click ‘Apply’ button to apply insert traverse entries to feature.

• Resolved a problem where the EditBoxes on the Placement Mode dialog were not displayed properly. JTS TR# 83972

• Resolved a problem where the application would crash with an ‘Invalid procedure call or argument’ error message while digitizing feature using the Insert Traverse Command. JTS TR# 83988
  Steps to Reproduce
  1)Invoke blank GWS, Make an access r/w connection to ‘USSampledata.mdb’
  2)Invoke Insert>Traverse cmd, select ‘Inter States’ FC from “Component Feature class” list box control
  3))Digitize feature using “Use Map” option, Make a click on map window observes start point values are displayed. Make sure that change value of start point to “90,90” , keep focus on same start point row and press Right arrow button.
  4)Observe that two “Start points” are displayed in ‘Insert Traverse” dialog. Digitize feature on map window from second “start point”. Click on ‘Close feature’ button to close digitized feature and select ‘Apply’ button to apply insert traverse entries into feature.

• Resolved a problem where the application would crash while using Search. JTS TR# 83989 and JTS TR# 83990
  Steps to reproduce:
  1.Invoke GMPro blank GWS; make an access R/W connection to USSampleData.mdb
  2.Invoke View>Search command.
  3.select any one of the FC say States and enter value ‘3’ in value to search field. Click the Search button.
  4.Invoke the ‘Search Data Window'(if not displayed) and using the ‘X’ button dismiss the DW.
  5.Now enter value ‘4’ in value to search field and click the Search button

• Resolved a problem where the SmartStore data server does not read the TextPointGeometry blobs correctly. The data server has to strip-off the extra bytes used for G/Tech while reading the text point geometry blobs from the DDC files. JTS TR# 84041

• Resolved a problem where the Search button remains disabled after keying in values. JTS TR# 84089

• Resolved a problem where an ‘Invalid geometry field name for the given recordset’ error message displays while exporting reference features with a geographic corrdinate system. JTS TR# 84109
  Steps to Reproduce
  1)Invoke GMPro, Make an access r/w connection to ‘USSampledata.mdb’.
  2)Invoke warehouse Spatial filter > Spatial filter reference features, check all features and click on ‘ok’ button to dismiss spatial filter reference features dialog.
  3)Invoke View> Geoworkspace coordinate system, change co-ordinate system type to ‘Geographic’ and click on ‘ok’ button to dismiss ‘Geoworkspace coordinate system’ dialog.
  4)Invoke Export> Export Shape File command, Check all features from ‘Reference features> access connection” under ‘features to export’ frame.
  5)Click ‘Apply’ button to export records into mentioned paths.

• Resolved a problem where moving the search Properties dialog separates from the drop down list. JTS TR# 84110

• Resolved a problem where all the fields were not being listed in the predefined search. JTS TR# 84160

• Resolved a problem where Insert Georeferenced Images would crash with a ‘general protection’ error when attempting to load a NITF 2.1 image. JTS TR# 84258

• Resolved a problem where the Continue Geometry two point mode would not exit the command properly if endpoints were used. JTS TR# 84280
  1. Make connection to USSampleData.mdb
  2. Add Legend Entry for feature class “Rivers”
  3. Select a single river feature.
  4. Select the Continue Geometry command using the Two Point mode.
  5. Digitize two points that are discontiguous from selected river, command terminates normally after two points and discontiguous line is drawn.
  6. Select the same river feature again.
  7. Select the Continue Geometry command using the Two Point mode.
  8. Digitize two points this time making the first point coincident with the endpoint of the existing river, after the second point is captured, user is still in command even though 2 points have been captured, user still sees prompt which states “Click to place next point. Double Click to End”. If the user clicks an additional point in the map window, the following error occurs, “Geomedia Professional: PPro Service, Invalid procedure call or argument”. This seems to only happen when using the two point mode if the continued geometry is coincident with the existing geometry

• Resolved a problem where attempting to insert a georeferenced image would crash the application to the operating system. JTS TR# 84408

• Resolved a problem where tiling would cause an opaque image to be overridden by a white background when Export2GeoPDF was run. JTS TR# 84446

• Resolved a problem where WMS server would fail with German regional settings on specific URL. JTS TR# 84451

• Resolved a problem where attempting to use the Database Utilities ‘Create Metadata Tables’ command to create metadata for a SQL Server database with the Collation set to ‘Czech_CS_AS’. The command would fail with a ‘Database Utilities’ error for case sensitivity testing. JTS TR# 84593

• Resolved a problem where attempting to keyin the following expression, will crash the application: CREATEPOLYLINE(Input.Geometry,FIRST(Detail.Geometry))
  JTS TR# 84599

• Resolved a problem where a patterned line style symbols would shift when zooming in and out. JTS TR# 84647

• Resolved a problem where a static queue name with a special character [like $ or &] would not validate correctly. JTS TR# 84662

• Resolved a problem where Variable Text Strings were getting set to the Map Window Sizing Method. JTS TR# 84667

• Resolved a problem where the results of Text Properties dialog edits were different than Ribbon Bar edits. JTS TR# 84672

• Resolved a problem where an ‘Invalid geometry field name for the given recordset’ error message was returned while exporting spatial filter reference features using ‘Export to OOM model’ command with a geographic co-ordinate system. JTS TR# 84674
  Steps to Reproduce
  1)Invoke GMPro, Make an access r/w connection to ‘USSampledata.mdb’.
  2)Invoke warehouse > Spatial filter reference features, check all features and click on ‘ok’ button to dismiss spatial filter reference features dialog.
  3)Invoke View> Geoworkspace coordinate system, change co-ordinate system type to ‘Geographic’ and click on ‘ok’ button to dismiss ‘Geoworkspace coordinate system’ dialog.
  4)Invoke Export> OOM model command, Check all features from ‘Reference features> access connection” under ‘features to export’ frame.
  5)Click ‘Apply’ button to export records into mentioned paths.

• Resolved a problem where an ‘Invalid geometry field name for the given recordset’ error message was returned while exporting spatial filter reference features using ‘Export to SQL server’ command with geographic co-ordinate system. JTS TR# 84675
  Steps to Reproduce
  1)Invoke GMPro, Make an access r/w connection to ‘USSampledata.mdb’.
  2)Invoke warehouse > Spatial filter reference features, check all features and click on ‘ok’ button to dismiss spatial filter reference features dialog.
  3)Invoke View> Geoworkspace coordinate system, change co-ordinate system type to ‘Geographic’ and click on ‘ok’ button to dismiss ‘Geoworkspace coordinate system’ dialog.
  4)Invoke Export> Export SQL server command, Check all features from ‘Reference features> access connection” under ‘features to export’ frame.
  5)Click ‘Apply’ button to export records into mentioned paths.

• Resolved a problem where Legend entries with sub entries returned a ‘Unmatched # of items between the legend and the tree view’ error in the Show legend Entries command. JTS TR# 84693

• Resolved a problem where WFS would give a connect error with certain test data. JTS TR# 84786

• Resolved a problem where a busy cursor state continued when the Filter button was clicked. JTS TR# 84795

• Resolved a problem where publishing the GWS from metadata fails and did not copy the connection info. JTS TR# 84851

• Updated the Help documentation for the Library Organizer Select References Command. JTS TR# 84953

• Resolved a problem where the DefSymFile command line and GUI generated SVG files that did not match. JTS TR# 85688

• Resolved a problem where an admin error would display when trying to update Lengen Entry style for a second time. JTS TR# 85744

• Implemented the ability to allow the user the selection of a disk for storage of temporary setup files. JTS CR# 52828

• Implemented the use of an .MSP installation process to provide fixes. JTS CR# 60477

• Implemented the use of an .MSP installation process to provide silent install of fixes. JTS CR# 70697

• Implemented the use of an .MSP installation process to provide fixes. JTS CR# 73693

• Updated Appendix E in the user documentation to reflect support for multibyte B/W, RGB and 4band data. JTS CR# 83652

• Implemented support of the MapFile3D component to read both G/Tech 9.x and 10.x DDC files. JTS CR# 84042

• Implemented the ability to publish 3D DDC files for G/Tech 10.x. JTS CR# 84043

• Improved the caching of the GeoMedia Raster Engine. JTS CR# 84505