<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Bugs We&#8217;ve Found</title>
	<atom:link href="http://jeffhobbs.net/bugs-weve-found/feed/" rel="self" type="application/rss+xml" />
	<link>http://jeffhobbs.net</link>
	<description>"A picture is only worth a thousand words. A map may be worth a thousand numbers. But a GIS is worth a thousand tables."</description>
	<lastBuildDate>Mon, 26 Jul 2010 03:43:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Bob Akers</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-3103</link>
		<dc:creator>Bob Akers</dc:creator>
		<pubDate>Thu, 24 Jun 2010 15:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-3103</guid>
		<description>Jeff,
We are using Geomedia and Orthopro.  We get error messages (cannot open anymore tables DAO error 3014) when trying to run large projects (1200 photos).  Geomedia will load a portion of the images say 300.  Any idea how to get around this.  Intergraph says to open another ortho project and import the orthos into that project.</description>
		<content:encoded><![CDATA[<p>Jeff,<br />
We are using Geomedia and Orthopro.  We get error messages (cannot open anymore tables DAO error 3014) when trying to run large projects (1200 photos).  Geomedia will load a portion of the images say 300.  Any idea how to get around this.  Intergraph says to open another ortho project and import the orthos into that project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: manoj</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-3102</link>
		<dc:creator>manoj</dc:creator>
		<pubDate>Sun, 20 Jun 2010 07:20:35 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-3102</guid>
		<description>is there any printing facility is available in new versions of geomedia viewer.

Thanks,
Manoj T</description>
		<content:encoded><![CDATA[<p>is there any printing facility is available in new versions of geomedia viewer.</p>
<p>Thanks,<br />
Manoj T</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: manoj</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-3101</link>
		<dc:creator>manoj</dc:creator>
		<pubDate>Sun, 20 Jun 2010 07:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-3101</guid>
		<description>i am using geomedia viewer 6.0 and not able to take print out of scale 1:500 on a3 paper.so much blank space is on the Paper and  is wasted.please suggest how to resolve this issue.

Thanks,
Manoj t.</description>
		<content:encoded><![CDATA[<p>i am using geomedia viewer 6.0 and not able to take print out of scale 1:500 on a3 paper.so much blank space is on the Paper and  is wasted.please suggest how to resolve this issue.</p>
<p>Thanks,<br />
Manoj t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeffhobbs</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-3067</link>
		<dc:creator>jeffhobbs</dc:creator>
		<pubDate>Thu, 13 May 2010 06:45:32 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-3067</guid>
		<description>Silvio - that would be my approach as well. Highly inefficient, I agree. But I don&#039;t know of any better way. </description>
		<content:encoded><![CDATA[<p>Silvio &#8211; that would be my approach as well. Highly inefficient, I agree. But I don&#8217;t know of any better way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silvio Causetti</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-3018</link>
		<dc:creator>Silvio Causetti</dc:creator>
		<pubDate>Mon, 08 Mar 2010 15:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-3018</guid>
		<description>Hi Jeff,
our main warehouse for Gomedia is an Oracle database containing data for printed World Atlas products. Our maps are mainly obtained making use of Oracle views based on the feature classes of the unique master database in a way that updates on the master are automatically propagated to the products.
We are making use of several Oracle schema and  it would be useful, in a .gws,  having the capability to change just the Oracle Connection, switcing from a user (schema) name to another one. This will allow us to avoid all the redefinition for the legend entries, queries and styles.
I have never found a tool doing this. The workaround is: save the all legends, queries and connection into a library, close it; open it with MS Access, changing in the table CONNECTION the column LOCATION (with the new schema); Create a new geoworkspace, attach the library and copy the elements to the new gws, replace the legend.
Obviously this workaround is highly intercative and time consuming.
Do you have any other idea?

Thanks, Silvio.</description>
		<content:encoded><![CDATA[<p>Hi Jeff,<br />
our main warehouse for Gomedia is an Oracle database containing data for printed World Atlas products. Our maps are mainly obtained making use of Oracle views based on the feature classes of the unique master database in a way that updates on the master are automatically propagated to the products.<br />
We are making use of several Oracle schema and  it would be useful, in a .gws,  having the capability to change just the Oracle Connection, switcing from a user (schema) name to another one. This will allow us to avoid all the redefinition for the legend entries, queries and styles.<br />
I have never found a tool doing this. The workaround is: save the all legends, queries and connection into a library, close it; open it with MS Access, changing in the table CONNECTION the column LOCATION (with the new schema); Create a new geoworkspace, attach the library and copy the elements to the new gws, replace the legend.<br />
Obviously this workaround is highly intercative and time consuming.<br />
Do you have any other idea?</p>
<p>Thanks, Silvio.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Natalie Lyons</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-2929</link>
		<dc:creator>Natalie Lyons</dc:creator>
		<pubDate>Tue, 26 Jan 2010 22:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-2929</guid>
		<description>Hi Jeff,

Thanks for the reply. I have managed to figure out a few things since my post. 

In regards to the issue with the general slowness and layout problems, this seems to not have replicated in 6.1 and I have been using it mostly with ease. 

The legend and scale bar issues still continue, however I have identified a work around. The problem lies in printing from the layout to .pdf therefore I have been exporting the layout to .jpeg first then print to .pdf. This eliminates the problem with the scale bar font and legend issues. 

After some investigation, I found that the legend/scale bar issue is known to Intergraph and they were going to release a hotfix though i&#039;m not sure when. Also I found that we downloaded the wrong hotfix (not the latest one) for 6.1 on my machine, therefore am waiting for the latest to be downloaded today. Hopefully this will fix the problem, but if not I still have the work around. 

Thanks for your help.

Natalie.</description>
		<content:encoded><![CDATA[<p>Hi Jeff,</p>
<p>Thanks for the reply. I have managed to figure out a few things since my post. </p>
<p>In regards to the issue with the general slowness and layout problems, this seems to not have replicated in 6.1 and I have been using it mostly with ease. </p>
<p>The legend and scale bar issues still continue, however I have identified a work around. The problem lies in printing from the layout to .pdf therefore I have been exporting the layout to .jpeg first then print to .pdf. This eliminates the problem with the scale bar font and legend issues. </p>
<p>After some investigation, I found that the legend/scale bar issue is known to Intergraph and they were going to release a hotfix though i&#8217;m not sure when. Also I found that we downloaded the wrong hotfix (not the latest one) for 6.1 on my machine, therefore am waiting for the latest to be downloaded today. Hopefully this will fix the problem, but if not I still have the work around. </p>
<p>Thanks for your help.</p>
<p>Natalie.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Hobbs</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-2925</link>
		<dc:creator>Jeff Hobbs</dc:creator>
		<pubDate>Thu, 21 Jan 2010 05:26:36 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-2925</guid>
		<description>Natlie,

I haven&#039;t noticed either issue. It sounds like something may have gone awry in your upgrade from 6.0 to 6.1.

Are you able to replicate these issues on a new GWS created with 6.1?

You might want to try to do a File &gt; Save As and see if that by chance fixes your issue.

On a side note, I often times run into problems where my legend in the layout window gets screwed up. When this happens (and it&#039;s fairly often) I have to recreate the legend. I&#039;m guessing it&#039;s tied to the fact that I often times rename the legend entries in the legend. However this is just a guess. But I haven&#039;t noticed other issues with the legend.</description>
		<content:encoded><![CDATA[<p>Natlie,</p>
<p>I haven&#8217;t noticed either issue. It sounds like something may have gone awry in your upgrade from 6.0 to 6.1.</p>
<p>Are you able to replicate these issues on a new GWS created with 6.1?</p>
<p>You might want to try to do a File &gt; Save As and see if that by chance fixes your issue.</p>
<p>On a side note, I often times run into problems where my legend in the layout window gets screwed up. When this happens (and it&#8217;s fairly often) I have to recreate the legend. I&#8217;m guessing it&#8217;s tied to the fact that I often times rename the legend entries in the legend. However this is just a guess. But I haven&#8217;t noticed other issues with the legend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Natalie Lyons</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-2923</link>
		<dc:creator>Natalie Lyons</dc:creator>
		<pubDate>Mon, 18 Jan 2010 23:35:54 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-2923</guid>
		<description>Hi Jeff,

I have been having problems with Geomedia for some time now, and after having my computer reimaged as a last result, have just found your forum. I now suspect it is not a problem with the computer at all!

The problems I have experienced are in line with posts from July 13 2007 to December 20 2007. 
Such problems include Geomedia shutting down unexpectedly and layout window issues as discribed by Patrick (20/12/2007).

After reimaging the computer they decided to put Geomedia 6.1 on my computer instead of 6.0 (which is what I was using when having all these problems). I have not used Geomedia 6.1 enough to know yet whether I am still having the same problems as before (though it has unexpectedly shut down on me again), however am now experiencing a couple of different problems (not sure if they&#039;re related) and hoping you can assist.

* I have opened a geoworkspace that I had been working on in 6.0 and the legend in the layout window is acting very odd. The text and legend keys are not actually contained within the legend box. Where ever I place the legend, the way it is placed and how it looks on screen is not how it looks when writing to pdf. I think the legend keys ARE actually contained with the box (as this seems to be how it looks when writing to pdf) but because it is showing the keys outside of the box, it is very difficult to accurately place the legend on the map layout. It&#039;s difficult to explain so if you need further explanation or screen shots let me know.

* When writing the file to pdf, I have the same problem as posted by Giulio on June 8 2009. For example, when creating my map layout, the scale bar is placed nicely over a white box on the map, and the text and scale bar is viewable. However once I print it to pdf, the scale bar moves around(still within the white box that i have inserted) but the text is so small it&#039;s almost not even there! I have tried playing with scale properties (paper &amp; view) but it makes no difference.

So I guess my questions for you are -

1) Have you heard of any fixes or reasons for the layout window issues described by Patrick in Dec 07?
2) Are you able to assist me with the new issues at the asterixes above? 

Please help! I&#039;m getting very frustrated!

Many thanks

Natalie</description>
		<content:encoded><![CDATA[<p>Hi Jeff,</p>
<p>I have been having problems with Geomedia for some time now, and after having my computer reimaged as a last result, have just found your forum. I now suspect it is not a problem with the computer at all!</p>
<p>The problems I have experienced are in line with posts from July 13 2007 to December 20 2007.<br />
Such problems include Geomedia shutting down unexpectedly and layout window issues as discribed by Patrick (20/12/2007).</p>
<p>After reimaging the computer they decided to put Geomedia 6.1 on my computer instead of 6.0 (which is what I was using when having all these problems). I have not used Geomedia 6.1 enough to know yet whether I am still having the same problems as before (though it has unexpectedly shut down on me again), however am now experiencing a couple of different problems (not sure if they&#8217;re related) and hoping you can assist.</p>
<p>* I have opened a geoworkspace that I had been working on in 6.0 and the legend in the layout window is acting very odd. The text and legend keys are not actually contained within the legend box. Where ever I place the legend, the way it is placed and how it looks on screen is not how it looks when writing to pdf. I think the legend keys ARE actually contained with the box (as this seems to be how it looks when writing to pdf) but because it is showing the keys outside of the box, it is very difficult to accurately place the legend on the map layout. It&#8217;s difficult to explain so if you need further explanation or screen shots let me know.</p>
<p>* When writing the file to pdf, I have the same problem as posted by Giulio on June 8 2009. For example, when creating my map layout, the scale bar is placed nicely over a white box on the map, and the text and scale bar is viewable. However once I print it to pdf, the scale bar moves around(still within the white box that i have inserted) but the text is so small it&#8217;s almost not even there! I have tried playing with scale properties (paper &amp; view) but it makes no difference.</p>
<p>So I guess my questions for you are -</p>
<p>1) Have you heard of any fixes or reasons for the layout window issues described by Patrick in Dec 07?<br />
2) Are you able to assist me with the new issues at the asterixes above? </p>
<p>Please help! I&#8217;m getting very frustrated!</p>
<p>Many thanks</p>
<p>Natalie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeffhobbs</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-2917</link>
		<dc:creator>jeffhobbs</dc:creator>
		<pubDate>Wed, 06 Jan 2010 19:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-2917</guid>
		<description>You have the ability to reference database columns when defining export symbology. I&#039;ve never tried to do this, but it seems logical that you could write at least some of the symbology out to attributes and then use the attributes to symbolize the DGN/CAD file. However I&#039;m not sure that would work for hatching unless you could somehow reference the hatching with a number e.g. 23 and that number were understood by the CAD.

Does this help at all?</description>
		<content:encoded><![CDATA[<p>You have the ability to reference database columns when defining export symbology. I&#8217;ve never tried to do this, but it seems logical that you could write at least some of the symbology out to attributes and then use the attributes to symbolize the DGN/CAD file. However I&#8217;m not sure that would work for hatching unless you could somehow reference the hatching with a number e.g. 23 and that number were understood by the CAD.</p>
<p>Does this help at all?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeffhobbs</title>
		<link>http://jeffhobbs.net/bugs-weve-found/#comment-2915</link>
		<dc:creator>jeffhobbs</dc:creator>
		<pubDate>Wed, 06 Jan 2010 18:59:37 +0000</pubDate>
		<guid isPermaLink="false">http://jeffhobbs.net/bugs-weve-found/#comment-2915</guid>
		<description>Have you filed a worksheet on this with Intergraph? I have even looked at the lastest updates for WebMap, but make sure all are as current as possible. Mixing version can cause problems.

I&#039;ve run into a similar problems just working with tooltips in the desktop products. I&#039;ll create tooltips in GM Pro and save the GWS. I&#039;ll then open in GM Viewer and the tooltips don&#039;t work. I&#039;ve filed this as a bug with INGR. I&#039;m not sure if it has been corrected to date.</description>
		<content:encoded><![CDATA[<p>Have you filed a worksheet on this with Intergraph? I have even looked at the lastest updates for WebMap, but make sure all are as current as possible. Mixing version can cause problems.</p>
<p>I&#8217;ve run into a similar problems just working with tooltips in the desktop products. I&#8217;ll create tooltips in GM Pro and save the GWS. I&#8217;ll then open in GM Viewer and the tooltips don&#8217;t work. I&#8217;ve filed this as a bug with INGR. I&#8217;m not sure if it has been corrected to date.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
