<?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/"
		>
<channel>
	<title>Comments for Imaging Forensics</title>
	<atom:link href="http://www.imagingforensics.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.imagingforensics.com</link>
	<description>Forensic Image and Video Analysis, Training, Expert Witness</description>
	<lastBuildDate>Mon, 10 May 2010 15:11:21 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Open Letter to Advanced Imaging Magazine by Simon Lambert</title>
		<link>http://www.imagingforensics.com/2010/05/open-letter-to-advanced-imaging-magazine/comment-page-1/#comment-127</link>
		<dc:creator>Simon Lambert</dc:creator>
		<pubDate>Mon, 10 May 2010 15:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.imagingforensics.com/?p=182#comment-127</guid>
		<description>Thanks for bringing this article to our attention, George. It&#039;s vital that these people are put right.</description>
		<content:encoded><![CDATA[<p>Thanks for bringing this article to our attention, George. It&#8217;s vital that these people are put right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Open Letter to Advanced Imaging Magazine by Larry Compton</title>
		<link>http://www.imagingforensics.com/2010/05/open-letter-to-advanced-imaging-magazine/comment-page-1/#comment-126</link>
		<dc:creator>Larry Compton</dc:creator>
		<pubDate>Sat, 08 May 2010 06:04:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.imagingforensics.com/?p=182#comment-126</guid>
		<description>Very well said George.  Thanks for taking the time to respond...and for sharing it with us.</description>
		<content:encoded><![CDATA[<p>Very well said George.  Thanks for taking the time to respond&#8230;and for sharing it with us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Open Letter to Advanced Imaging Magazine by Grant Fredericks</title>
		<link>http://www.imagingforensics.com/2010/05/open-letter-to-advanced-imaging-magazine/comment-page-1/#comment-125</link>
		<dc:creator>Grant Fredericks</dc:creator>
		<pubDate>Thu, 06 May 2010 21:26:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.imagingforensics.com/?p=182#comment-125</guid>
		<description>Nice letter George ... please let us know if you get a response.</description>
		<content:encoded><![CDATA[<p>Nice letter George &#8230; please let us know if you get a response.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reflecting back on 2009 by pnolte</title>
		<link>http://www.imagingforensics.com/2010/01/reflecting-back-on-2009/comment-page-1/#comment-124</link>
		<dc:creator>pnolte</dc:creator>
		<pubDate>Wed, 10 Feb 2010 18:09:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.imagingforensics.com/?p=173#comment-124</guid>
		<description>George One thing I spent time on last year was HDR and latent print imaging for AFIS searching. So far, I am getting great results in displaying faint ridges without clipping the darker ridges. It makes AFIS searching much easier. I can make some images available if you like. Pat</description>
		<content:encoded><![CDATA[<p>George One thing I spent time on last year was HDR and latent print imaging for AFIS searching. So far, I am getting great results in displaying faint ridges without clipping the darker ridges. It makes AFIS searching much easier. I can make some images available if you like. Pat</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Photoshop and Bridge for On-Screen Comparisons by Erik Berg</title>
		<link>http://www.imagingforensics.com/2009/11/using-photoshop-and-bridge-for-on-screen-comparisons/comment-page-1/#comment-123</link>
		<dc:creator>Erik Berg</dc:creator>
		<pubDate>Fri, 29 Jan 2010 14:40:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.imagingforensics.com/?p=135#comment-123</guid>
		<description>Very cool George.  We&#039;ll look at using this for doing facial examinations.

Erik</description>
		<content:encoded><![CDATA[<p>Very cool George.  We&#8217;ll look at using this for doing facial examinations.</p>
<p>Erik</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Synchronizing Video in Forensic Video Analysis by Erik Berg</title>
		<link>http://www.imagingforensics.com/2009/10/synchronizing-video-in-forensic-video-analysis/comment-page-1/#comment-122</link>
		<dc:creator>Erik Berg</dc:creator>
		<pubDate>Fri, 29 Jan 2010 14:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.imagingforensics.com/?p=91#comment-122</guid>
		<description>Steve,

To answer your question, the &quot;standard&quot; came from Steve Meager at the FBI via the NIST conference in 1999 I believe.  The FBI and SWGFAST wanted 1200 ppi as a minimum.  I pointed out that the resolution of several images in Hayden were only 289 ppi.  The UK presented test results from 34 Latent Examiners that showed a resolution of 600 ppi actually produced one additional identification over the same set of images captured at 1200 ppi.  NIST compromised by establishing a standard of 1000 ppi for the purpose of searching automated fingerprint systems.  The UK established a standard of 600 ppi because they weren&#039;t willing to pay for the additional storage and bandwidth 1000 ppi would require.

So, that&#039;s where the 1000 ppi standard came from.

Erik</description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>To answer your question, the &#8220;standard&#8221; came from Steve Meager at the FBI via the NIST conference in 1999 I believe.  The FBI and SWGFAST wanted 1200 ppi as a minimum.  I pointed out that the resolution of several images in Hayden were only 289 ppi.  The UK presented test results from 34 Latent Examiners that showed a resolution of 600 ppi actually produced one additional identification over the same set of images captured at 1200 ppi.  NIST compromised by establishing a standard of 1000 ppi for the purpose of searching automated fingerprint systems.  The UK established a standard of 600 ppi because they weren&#8217;t willing to pay for the additional storage and bandwidth 1000 ppi would require.</p>
<p>So, that&#8217;s where the 1000 ppi standard came from.</p>
<p>Erik</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reverse Projection Photogrammetry by Robert Wyman</title>
		<link>http://www.imagingforensics.com/2009/11/reverse-projection-photogrammetry/comment-page-1/#comment-120</link>
		<dc:creator>Robert Wyman</dc:creator>
		<pubDate>Sat, 19 Dec 2009 22:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.imagingforensics.com/?p=152#comment-120</guid>
		<description>George, I&#039;m continuing to enjoy outstanding results with the iWitness photogrammetry program. I&#039;m trying to employ it on every case, whether for actual documentation use or for my own continued training... and each case presents it&#039;s own unique challenges!

I&#039;m going to &quot;sanitize&quot; some of the names and locations, then put a gallery of scaled CAD diagram files on my website, with each diagram derived from photogrammetry-based documentation. Recent cases include a freeway crash site that could not be measured with traditional tools, a pedestrian fall site in which a sidewalk was found to have a subtle ... but significant... change in grade, and a vehicular damage case in which the impact angle became a critical element. 

I&#039;m finding this &quot;live&quot; use of photogrammetry to be a unique tool in my crash-reconstruction arsenal.</description>
		<content:encoded><![CDATA[<p>George, I&#8217;m continuing to enjoy outstanding results with the iWitness photogrammetry program. I&#8217;m trying to employ it on every case, whether for actual documentation use or for my own continued training&#8230; and each case presents it&#8217;s own unique challenges!</p>
<p>I&#8217;m going to &#8220;sanitize&#8221; some of the names and locations, then put a gallery of scaled CAD diagram files on my website, with each diagram derived from photogrammetry-based documentation. Recent cases include a freeway crash site that could not be measured with traditional tools, a pedestrian fall site in which a sidewalk was found to have a subtle &#8230; but significant&#8230; change in grade, and a vehicular damage case in which the impact angle became a critical element. </p>
<p>I&#8217;m finding this &#8220;live&#8221; use of photogrammetry to be a unique tool in my crash-reconstruction arsenal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reverse Projection Photogrammetry by Nicholas Guanti</title>
		<link>http://www.imagingforensics.com/2009/11/reverse-projection-photogrammetry/comment-page-1/#comment-119</link>
		<dc:creator>Nicholas Guanti</dc:creator>
		<pubDate>Tue, 15 Dec 2009 15:50:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.imagingforensics.com/?p=152#comment-119</guid>
		<description>I have been fortunate to have exchanged dialogue with both Mr. Bruegge and Mr. Bruehs regarding several areas of expertise and can support the benefit of understanding reverse projection by way of their highly technical knowledgebase. Mr. Bruegge also offers a wealth of knowledge in other areas of forensic image examination and analysis.

Nicholas Guanti</description>
		<content:encoded><![CDATA[<p>I have been fortunate to have exchanged dialogue with both Mr. Bruegge and Mr. Bruehs regarding several areas of expertise and can support the benefit of understanding reverse projection by way of their highly technical knowledgebase. Mr. Bruegge also offers a wealth of knowledge in other areas of forensic image examination and analysis.</p>
<p>Nicholas Guanti</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An Introduction to the Blog by admin</title>
		<link>http://www.imagingforensics.com/2009/10/imaging-forensics-blog-intro/comment-page-1/#comment-77</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 10 Nov 2009 18:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://66.147.244.157/~imagingf/?p=1#comment-77</guid>
		<description>Yes, the OpenGL features in PS-CS4 are wonderful. The rotate tool is key for temporarily rotating your images during comparisons. The improvement in viewing images at odd magnifications is great. You need to be sure that you have a graphics card that supports these features, and the feature must be turned on in the Performance Preference. There&#039;s more information on the Adobe website here: http://kb2.adobe.com/cps/404/kb404898.html</description>
		<content:encoded><![CDATA[<p>Yes, the OpenGL features in PS-CS4 are wonderful. The rotate tool is key for temporarily rotating your images during comparisons. The improvement in viewing images at odd magnifications is great. You need to be sure that you have a graphics card that supports these features, and the feature must be turned on in the Performance Preference. There&#8217;s more information on the Adobe website here: <a href="http://kb2.adobe.com/cps/404/kb404898.html" rel="nofollow">http://kb2.adobe.com/cps/404/kb404898.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An Introduction to the Blog by Wayne</title>
		<link>http://www.imagingforensics.com/2009/10/imaging-forensics-blog-intro/comment-page-1/#comment-76</link>
		<dc:creator>Wayne</dc:creator>
		<pubDate>Tue, 10 Nov 2009 17:45:09 +0000</pubDate>
		<guid isPermaLink="false">http://66.147.244.157/~imagingf/?p=1#comment-76</guid>
		<description>Is anyone using the OpenGL feature (rotate hand tool)in PS-CS4 (for forensic work?) I get a wndow that says: &quot;could not complete request-only works with OpenGL enabled windows.&quot;</description>
		<content:encoded><![CDATA[<p>Is anyone using the OpenGL feature (rotate hand tool)in PS-CS4 (for forensic work?) I get a wndow that says: &#8220;could not complete request-only works with OpenGL enabled windows.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
