<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.communities.hp.com/online/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Security Printing and Imaging : authentication, GPS</title><link>http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/authentication/GPS/default.aspx</link><description>Tags: authentication, GPS</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP1 (Build: 31106.3070)</generator><item><title>Imaging Challenges</title><link>http://www.communities.hp.com/online/blogs/securityprinting/archive/2008/09/18/imaging-challenges.aspx</link><pubDate>Thu, 18 Sep 2008 11:57:00 GMT</pubDate><guid isPermaLink="false">964d1d0f-bea0-4201-a2aa-8aa369a35a46:84794</guid><dc:creator>StevenSimske</dc:creator><slash:comments>0</slash:comments><comments>http://www.communities.hp.com/online/blogs/securityprinting/archive/2008/09/18/imaging-challenges.aspx#comments</comments><description>&lt;p&gt;&amp;quot;Imaging&amp;quot; is a broad term meaning the ability to transform, interpret and/or associate an image. Sounds pretty easy, right? But when you consider what is actually involved, it&amp;#39;s&amp;nbsp;pretty hard. Most modern digital cameras (and other photo-capture devices) are packed with a host of &amp;quot;automatic&amp;quot; imaging, such as noise removal, contrast/exposure enhancement, etc., up to red-eye removal and photo album aggregation. All of which implies there are (hopefully reliable!) algorithms available to improve the quality of an image (and thus improve its value).&lt;/p&gt;
&lt;p&gt;However, the&amp;nbsp;way you will use an image (called its &amp;quot;workflow&amp;quot;)&amp;nbsp;impacts what algorithms you will use to clean it up, improve its quality, and otherwise transform it. Normal metrics for &amp;quot;image quality&amp;quot;, for example, are not as important in security printing and imaging as are the more arcane concepts of inspectability, authenticability and forensics-capability. Consider, as an exemplar, if I have added information--such as a 2D bar code or a digital watermark [hidden, or &amp;quot;steganographic&amp;quot; information]--to an image, then whatever I do with my imaging should be focused on helping me reliably extract that information rather than improving the aesthetics of the image.&lt;/p&gt;
&lt;p&gt;How hard can that be, you ask? Let&amp;#39;s look at four photos that each contain one set of identical information; namely, the GPS location that the image was taken from.&lt;/p&gt;
&lt;p&gt;Picture 1 is the new Sao Paulo bridge by day, from the 31st floor:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img height="144" alt="" src="http://images2.snapfish.com/232323232%7Ffp533%3B2%3Evq%3D3365%3E48%3B%3E837%3EWSNRCG%3D3238%3C3%3C%3B%3C895%3Bvq0mrj" width="192" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;Picture 2 is the same bridge, from the same floor, with a different aspect ratio:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;img height="192" alt="" src="http://images2b.snapfish.com/232323232%7Ffp53459%3Evq%3D3365%3E48%3B%3E837%3EWSNRCG%3D3238%3C3%3C%3B%3C895%3Avq0mrj" width="144" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;The third is taken from the same GPS location, 30 floors lower, and at dark:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;img height="144" alt="" src="http://images2.snapfish.com/232323232%7Ffp533%3A%3B%3Evq%3D3365%3E48%3B%3E837%3EWSNRCG%3D3238%3C3%3C%3B%3C8%3C24vq0mrj" width="192" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;And the last image is taken from the same GPS location, 6 stories up, in the opposite direction:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;img height="192" alt="" src="http://images2.snapfish.com/232323232%7Ffp533%3B4%3Evq%3D3365%3E48%3B%3E837%3EWSNRCG%3D3238%3C3%3C%3B%3C8%3C25vq0mrj" width="144" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;What information do these pictures have in common aside from the GPS location? Picture 1 and 2 are pretty similar to the human viewer, but to the imaging algorithm have a number of distinctions. Perspective, aspect ratio, contrast and exposure all differ considerably. Most image-clustering technologies, however, can aggregate (find similar) these two. But if the bridge were watermarked, would the photos equally represent those watermarks? Would the same bridge in Picture 3 also aggregate with Pictures 1 and 2?&amp;nbsp; Humans would say yes, but machine algorithms are not so sure. Picture 4, not a chance for the machine (or for any human who did not have the memory of both images), without the GPS information.&lt;/p&gt;
&lt;p&gt;This represents (somewhat figuratively)&amp;nbsp;some of the challenge involved in security imaging. In practice, we are not usually required to associate Picture #4 with Pictures 1-3 except through metadata (image header) search. In future blogs, I will discuss how the imaging is actually able to work (and work well!) on Pictures 1-3.&lt;/p&gt;
&lt;p&gt;-Steve&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://www.communities.hp.com/online/aggbug.aspx?PostID=84794" width="1" height="1"&gt;</description><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/security/default.aspx">security</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/authentication/default.aspx">authentication</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/forensics/default.aspx">forensics</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/inspection/default.aspx">inspection</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/imaging/default.aspx">imaging</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/Sao+Paulo/default.aspx">Sao Paulo</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/Morumbi+bridge/default.aspx">Morumbi bridge</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/GPS/default.aspx">GPS</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/image+transformation/default.aspx">image transformation</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/exposure/default.aspx">exposure</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/contrast/default.aspx">contrast</category></item></channel></rss>