<?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 for the Air Vent</title>
	<atom:link href="http://noconsensus.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://noconsensus.wordpress.com</link>
	<description>Because the world needs another opinion</description>
	<lastBuildDate>Wed, 16 Dec 2009 06:59:33 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Swiss Homogenization by Espen</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/swiss-homogenization/#comment-15839</link>
		<dc:creator>Espen</dc:creator>
		<pubDate>Wed, 16 Dec 2009 06:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6980#comment-15839</guid>
		<description>#11: The &quot;Säntis 2000&quot; construction project (of the huge buildings seen in the image linked from my previous post) was finished in 1998.</description>
		<content:encoded><![CDATA[<p>#11: The &#8220;Säntis 2000&#8243; construction project (of the huge buildings seen in the image linked from my previous post) was finished in 1998.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Swiss Homogenization by Espen</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/swiss-homogenization/#comment-15838</link>
		<dc:creator>Espen</dc:creator>
		<pubDate>Wed, 16 Dec 2009 06:54:47 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6980#comment-15838</guid>
		<description>#10: No urban heat on Säntis? Are you sure?
http://www.appenzellerlandsport.ch/site/downloads/Image/mittel/saentis_von_oben.jpg</description>
		<content:encoded><![CDATA[<p>#10: No urban heat on Säntis? Are you sure?<br />
<a href="http://www.appenzellerlandsport.ch/site/downloads/Image/mittel/saentis_von_oben.jpg" rel="nofollow">http://www.appenzellerlandsport.ch/site/downloads/Image/mittel/saentis_von_oben.jpg</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Things that make you go HMM … by Pauski</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/3649/#comment-15837</link>
		<dc:creator>Pauski</dc:creator>
		<pubDate>Wed, 16 Dec 2009 06:47:31 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6984#comment-15837</guid>
		<description>It is nice to see people looking at the Nasa data which has been corrupted either way due do their own release statements in the last few years. However, one major problem these programs have is beyond obvious.  There is no account of global position of each temperature taken.  For instance, let say the wall in your room  was to be measured for a wall temperature. This wall temperature was to be the average temperature across the entire surface.  By all laws of sampling as taught in simple engineering school or grade school science fair projects, one needs to take a temperature reading in a uniform distance across the surface so as to have a uniform sampling density. Why? Because, if you take 100 samples on the left side at the floor and one sample in the middle, it would be invalid sampling. This is fairly obvious but climate people seem too not have a clue. Most of all temperature science is found under &quot;black body radiation and sampling&quot; chapters in most engineering books. In the real world of steel production, temperature sampling is extremely important and is well understood. Uniform or equally distant sample points are required unless a proven distance to temperature capacity formula is used to quantify errors in true distance sample.  This means you placed 100 points on a surface uniformly but a few are millimeters off.  Averaged cells are used to form a pyramid of cells with error values for each cell. Every sample has a sampled error and a corrected error.

Just being Captain Obvious here, but none of the sample data will allow a global temperature even for the USA. Period and end of story.  What can be said, you have historical data on several temperature reading sites. One can not use it for global or average temperature at all. Just not correct. 

Sadly, the temperature data can say maybe for a city that the temperature has changed over time but that is it.  All this was well known back in the 1950&#039;s and 1960&#039;s. That is why the thought was to have Satellites measure the overall surface. But, some snags there as well, one is the aging of Sat&#039;s sensors has not been sufficiently verified as recommended by the engineers. For instance, an uniform swath of land with temperature readings would need to be verified by the Sat data. This comparison would give a confidence number as to the correctness of the Sat equipment.  But once again, only done initially and dropped due to budget cuts. And, Sat sensing has its problems due to Ionosphere interference, radar curvature problems, atmospheric interference. Hence, the sampling was never corrected. This was deemed OK since they were just used as a general feel not tenths of a degree accuracy.  Maybe plus or minus 5 degrees C but then one could not say if the world was warming or cooling a degree.</description>
		<content:encoded><![CDATA[<p>It is nice to see people looking at the Nasa data which has been corrupted either way due do their own release statements in the last few years. However, one major problem these programs have is beyond obvious.  There is no account of global position of each temperature taken.  For instance, let say the wall in your room  was to be measured for a wall temperature. This wall temperature was to be the average temperature across the entire surface.  By all laws of sampling as taught in simple engineering school or grade school science fair projects, one needs to take a temperature reading in a uniform distance across the surface so as to have a uniform sampling density. Why? Because, if you take 100 samples on the left side at the floor and one sample in the middle, it would be invalid sampling. This is fairly obvious but climate people seem too not have a clue. Most of all temperature science is found under &#8220;black body radiation and sampling&#8221; chapters in most engineering books. In the real world of steel production, temperature sampling is extremely important and is well understood. Uniform or equally distant sample points are required unless a proven distance to temperature capacity formula is used to quantify errors in true distance sample.  This means you placed 100 points on a surface uniformly but a few are millimeters off.  Averaged cells are used to form a pyramid of cells with error values for each cell. Every sample has a sampled error and a corrected error.</p>
<p>Just being Captain Obvious here, but none of the sample data will allow a global temperature even for the USA. Period and end of story.  What can be said, you have historical data on several temperature reading sites. One can not use it for global or average temperature at all. Just not correct. </p>
<p>Sadly, the temperature data can say maybe for a city that the temperature has changed over time but that is it.  All this was well known back in the 1950&#8217;s and 1960&#8217;s. That is why the thought was to have Satellites measure the overall surface. But, some snags there as well, one is the aging of Sat&#8217;s sensors has not been sufficiently verified as recommended by the engineers. For instance, an uniform swath of land with temperature readings would need to be verified by the Sat data. This comparison would give a confidence number as to the correctness of the Sat equipment.  But once again, only done initially and dropped due to budget cuts. And, Sat sensing has its problems due to Ionosphere interference, radar curvature problems, atmospheric interference. Hence, the sampling was never corrected. This was deemed OK since they were just used as a general feel not tenths of a degree accuracy.  Maybe plus or minus 5 degrees C but then one could not say if the world was warming or cooling a degree.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Swiss Homogenization by cogito</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/swiss-homogenization/#comment-15836</link>
		<dc:creator>cogito</dc:creator>
		<pubDate>Wed, 16 Dec 2009 06:44:36 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6980#comment-15836</guid>
		<description>On comparing the station data for Saentis, Switzerland with GHCN, I noticed that the homogenized Swiss data
http://www.meteoswiss.admin.ch/web/de/klima/klima_heute/homogene_reihen.Par.0037.DownloadFile.ext.tmp/saentis.txt
is systematically &lt;strong&gt;lower&lt;/strong&gt; (colder) by 0.2 to 0.4 °C than GHCN from 1864 to 1998, thereafter the difference becomes 0 from 1998 to 2009.</description>
		<content:encoded><![CDATA[<p>On comparing the station data for Saentis, Switzerland with GHCN, I noticed that the homogenized Swiss data<br />
<a href="http://www.meteoswiss.admin.ch/web/de/klima/klima_heute/homogene_reihen.Par.0037.DownloadFile.ext.tmp/saentis.txt" rel="nofollow">http://www.meteoswiss.admin.ch/web/de/klima/klima_heute/homogene_reihen.Par.0037.DownloadFile.ext.tmp/saentis.txt</a><br />
is systematically <strong>lower</strong> (colder) by 0.2 to 0.4 °C than GHCN from 1864 to 1998, thereafter the difference becomes 0 from 1998 to 2009.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Swiss Homogenization by cogito</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/swiss-homogenization/#comment-15834</link>
		<dc:creator>cogito</dc:creator>
		<pubDate>Wed, 16 Dec 2009 06:10:57 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6980#comment-15834</guid>
		<description>Funny, I was starting to compare Swiss figures raw/homogenized yesterday and came to the same conclusions. In ther explnation they say that the main reasons for homogenization were change of instruments and/or displacement. In these cases, wouldn&#039;t you expect a step function? 
Look at the station SAE (Säntis), top row of last page in http://www.meteoschweiz.admin.ch/web/de/klima/klima_heute/homogene_reihen.Par.0054.DownloadFile.tmp/vergleichoriginalhomogen.pdf:

Säntis (Googel Earth: Saentis, Switzerland) is a peak at 2500 m altitude in a chain of mountains. The only building (which has been there for decades) is the top station of the cable car and a mountain restaurant. There is no way this station can be contaminated by urban heat, unless it sits on the roof of the restaurant. There is no way to move the station more than a few meters before it falls off. Yet, they have &quot;homogenized&quot; the temperatures.</description>
		<content:encoded><![CDATA[<p>Funny, I was starting to compare Swiss figures raw/homogenized yesterday and came to the same conclusions. In ther explnation they say that the main reasons for homogenization were change of instruments and/or displacement. In these cases, wouldn&#8217;t you expect a step function?<br />
Look at the station SAE (Säntis), top row of last page in <a href="http://www.meteoschweiz.admin.ch/web/de/klima/klima_heute/homogene_reihen.Par.0054.DownloadFile.tmp/vergleichoriginalhomogen.pdf" rel="nofollow">http://www.meteoschweiz.admin.ch/web/de/klima/klima_heute/homogene_reihen.Par.0054.DownloadFile.tmp/vergleichoriginalhomogen.pdf</a>:</p>
<p>Säntis (Googel Earth: Saentis, Switzerland) is a peak at 2500 m altitude in a chain of mountains. The only building (which has been there for decades) is the top station of the cable car and a mountain restaurant. There is no way this station can be contaminated by urban heat, unless it sits on the roof of the restaurant. There is no way to move the station more than a few meters before it falls off. Yet, they have &#8220;homogenized&#8221; the temperatures.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Things that make you go HMM … by Ryan O</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/3649/#comment-15833</link>
		<dc:creator>Ryan O</dc:creator>
		<pubDate>Wed, 16 Dec 2009 06:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6984#comment-15833</guid>
		<description>You can&#039;t just fit trends and then tack them all together; your final answer will be totally erroneous.

Take any noisy time series - be it the CRU index, an individual station, or a stock price.  Break it up into intervals (your choice).  Perform a linear regression for each interval and tack them end-on-end.  Then compare that result to the linear trend using all the data.

No worky.

The problem is that in the regression model y=mx+b, you have to keep track of all of the b&#039;s (the y-intercept).  In other words, even if you try just to use trends, you still have to keep track of the intercepts, which means you have to know what the offset is from one segment to the next.  Now how do you know if a &quot;shift&quot; is due to real no-shit temperature change?  Or a station move?  Or UHI?  Using trends gives you no additional information.

The other issue is with anomaly baselines.  When it comes to climate, we only care about the change.  That change has to be relative to a baseline.  If you have incomplete records, you cannot baseline the records to the same period without figuring out what the offset is from one station to the next.  With anomalies, the issue is intractable.  You can&#039;t go back and add more stations, so if you want to use information that only has partial coverage temporally, you must adjust.

In other words, the trend thing won&#039;t work.</description>
		<content:encoded><![CDATA[<p>You can&#8217;t just fit trends and then tack them all together; your final answer will be totally erroneous.</p>
<p>Take any noisy time series &#8211; be it the CRU index, an individual station, or a stock price.  Break it up into intervals (your choice).  Perform a linear regression for each interval and tack them end-on-end.  Then compare that result to the linear trend using all the data.</p>
<p>No worky.</p>
<p>The problem is that in the regression model y=mx+b, you have to keep track of all of the b&#8217;s (the y-intercept).  In other words, even if you try just to use trends, you still have to keep track of the intercepts, which means you have to know what the offset is from one segment to the next.  Now how do you know if a &#8220;shift&#8221; is due to real no-shit temperature change?  Or a station move?  Or UHI?  Using trends gives you no additional information.</p>
<p>The other issue is with anomaly baselines.  When it comes to climate, we only care about the change.  That change has to be relative to a baseline.  If you have incomplete records, you cannot baseline the records to the same period without figuring out what the offset is from one station to the next.  With anomalies, the issue is intractable.  You can&#8217;t go back and add more stations, so if you want to use information that only has partial coverage temporally, you must adjust.</p>
<p>In other words, the trend thing won&#8217;t work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on GHCN Antarctic, 8X Actual Trend &#8211; Uses Single Warmest Station by yonason</title>
		<link>http://noconsensus.wordpress.com/2009/12/13/ghcn-antarctic-warming-eight-times-actual/#comment-15832</link>
		<dc:creator>yonason</dc:creator>
		<pubDate>Wed, 16 Dec 2009 05:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6926#comment-15832</guid>
		<description>Another article on why we must be wary.
http://www.examiner.com/x-28973-Essex-County-Conservative-Examiner~y2009m12d11-Global-weather-dataset-being-systematically-corrupted</description>
		<content:encoded><![CDATA[<p>Another article on why we must be wary.<br />
<a href="http://www.examiner.com/x-28973-Essex-County-Conservative-Examiner~y2009m12d11-Global-weather-dataset-being-systematically-corrupted" rel="nofollow">http://www.examiner.com/x-28973-Essex-County-Conservative-Examiner~y2009m12d11-Global-weather-dataset-being-systematically-corrupted</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fascinating &#8211; No ice in 5 years by kevoka</title>
		<link>http://noconsensus.wordpress.com/2009/12/14/6567/#comment-15831</link>
		<dc:creator>kevoka</dc:creator>
		<pubDate>Wed, 16 Dec 2009 04:54:21 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6966#comment-15831</guid>
		<description>#11 - One thing NOBODY is discussing that we could do to save the world from total and utter collapse due to overheating in the next 5 years and, to my knowledge, is accepted by all to be a fact: 

Encourage ;), if you will, a volcano (or 2) to go off. They really don&#039;t do to much damage to the immediate surroundings, and would drop the old global T pretty quickly...</description>
		<content:encoded><![CDATA[<p>#11 &#8211; One thing NOBODY is discussing that we could do to save the world from total and utter collapse due to overheating in the next 5 years and, to my knowledge, is accepted by all to be a fact: </p>
<p>Encourage <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> , if you will, a volcano (or 2) to go off. They really don&#8217;t do to much damage to the immediate surroundings, and would drop the old global T pretty quickly&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Things that make you go HMM … by TurkeyLurkey</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/3649/#comment-15830</link>
		<dc:creator>TurkeyLurkey</dc:creator>
		<pubDate>Wed, 16 Dec 2009 04:51:55 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6984#comment-15830</guid>
		<description>Hey Jeff;
 Thanks for pointing out another blindingly obvious thing that I had not realized until you wrote it.

What would be the effect of  truncating short records at multiples of 365 days length,  and fitting the trend to each one as #37 was suggesting?  
Whenever a purported discontinuity (change of equipment, location, etc) just separately truncate that segment and then  mod365.25 days. Hmm, tricky to do that fractional day thing...

I like the idea of avoiding as many &#039;adjustments&#039; as possible.
I&#039;m not sure of the value of trying to adjust the segments to get rid of shifts...
Talk is cheap; I&#039;m not saying anyone &#039;should&#039; do this.
I&#039;m just curious what would be wrong with this approach.
TIA 
TL</description>
		<content:encoded><![CDATA[<p>Hey Jeff;<br />
 Thanks for pointing out another blindingly obvious thing that I had not realized until you wrote it.</p>
<p>What would be the effect of  truncating short records at multiples of 365 days length,  and fitting the trend to each one as #37 was suggesting?<br />
Whenever a purported discontinuity (change of equipment, location, etc) just separately truncate that segment and then  mod365.25 days. Hmm, tricky to do that fractional day thing&#8230;</p>
<p>I like the idea of avoiding as many &#8216;adjustments&#8217; as possible.<br />
I&#8217;m not sure of the value of trying to adjust the segments to get rid of shifts&#8230;<br />
Talk is cheap; I&#8217;m not saying anyone &#8217;should&#8217; do this.<br />
I&#8217;m just curious what would be wrong with this approach.<br />
TIA<br />
TL</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Things that make you go HMM … by Jeff Id</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/3649/#comment-15829</link>
		<dc:creator>Jeff Id</dc:creator>
		<pubDate>Wed, 16 Dec 2009 04:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6984#comment-15829</guid>
		<description>#37 It&#039;s important, not to calculate the trend on raw non anomaly data because the annual temperatures have a huge sinusoidal signal from seasonal change. The seasonal signal overwhelms the trend variation. That&#039;s why it&#039;s so important that technical people like yourself grab a bit of data and run a plot.  

It&#039;s not hard and the data is available.</description>
		<content:encoded><![CDATA[<p>#37 It&#8217;s important, not to calculate the trend on raw non anomaly data because the annual temperatures have a huge sinusoidal signal from seasonal change. The seasonal signal overwhelms the trend variation. That&#8217;s why it&#8217;s so important that technical people like yourself grab a bit of data and run a plot.  </p>
<p>It&#8217;s not hard and the data is available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Things that make you go HMM … by Kenneth Fritsch</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/3649/#comment-15828</link>
		<dc:creator>Kenneth Fritsch</dc:creator>
		<pubDate>Wed, 16 Dec 2009 04:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6984#comment-15828</guid>
		<description>Just to add a general observation here: In the GISS/Hansen paper that I linked above it is freely admitted that the while the calculations for the adjustment for TOB is straight forward, given that you have an accurate documentation of when the observation times changed and to what hours, the key remains that accurate documentation is first required. TOB and station change inhomogenities are the largest adjustments made with regards to trend, but in the end both depend, as noted by Hansen in the paper, on documentation.  (USHCN forgets the documentation and uses change points for some of these adjustments and it make large differences at some stations.)

Now please think about the quality control claimed by USHCN for its stations and then what the Watts evaluation team discovered and then tell me that you have good faith and trust in the TOB and change of station documentation that is claimed or at least implied by the temperature series owners.  Look at the sloppiness revealed of the CRU data set owners in &quot;read me Harry&quot; and in losing raw data. Look also how all this is waved away by the owners and claimed it does not matter. And finally look at how the users of these data and other parties who should interested in accurate data shrug and carry on.</description>
		<content:encoded><![CDATA[<p>Just to add a general observation here: In the GISS/Hansen paper that I linked above it is freely admitted that the while the calculations for the adjustment for TOB is straight forward, given that you have an accurate documentation of when the observation times changed and to what hours, the key remains that accurate documentation is first required. TOB and station change inhomogenities are the largest adjustments made with regards to trend, but in the end both depend, as noted by Hansen in the paper, on documentation.  (USHCN forgets the documentation and uses change points for some of these adjustments and it make large differences at some stations.)</p>
<p>Now please think about the quality control claimed by USHCN for its stations and then what the Watts evaluation team discovered and then tell me that you have good faith and trust in the TOB and change of station documentation that is claimed or at least implied by the temperature series owners.  Look at the sloppiness revealed of the CRU data set owners in &#8220;read me Harry&#8221; and in losing raw data. Look also how all this is waved away by the owners and claimed it does not matter. And finally look at how the users of these data and other parties who should interested in accurate data shrug and carry on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Things that make you go HMM … by Green R&#38;D Mgr</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/3649/#comment-15827</link>
		<dc:creator>Green R&#38;D Mgr</dc:creator>
		<pubDate>Wed, 16 Dec 2009 03:55:31 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6984#comment-15827</guid>
		<description>Steven,

Your post proves a point, but perhaps not the one you wanted to make.

The initial mistake I made was to assume GHCN was adjusting raw data, but at least in the US, it has already been adjusted a number of times by NCDC for the USHCN. Each step introducing more possible smaller error while removing gross discontinuities. It has been an eye opening journey to see how many times the data is adjusted by various algorithms. I&#039;m sure I still don&#039;t have it all completely right, but this is what I have seen so far at least for US data.You may want to check that the raw is actually raw.

My observation is that the accumulation of these uncertainties appears to exceed the range of detected warming signal that is claimed. 

Every time someone adjustments the data they also increase the band of uncertainty. This uncertainty builds upon the uncertainty already in the raw data prior to hand off to GHCN. Many of the adjustments appear to have legitimate reasons of trying to remove large discontinuities or false overall trends. However, every time they modify the data with an algorithm that reduces the volatility, they add some uncertainty even while these other problems are fixed.

In the US, the data is first gathered daily from the station.
The data is collected and reported in 1 degree F increments.

DSI-3200 Page 4:
&quot;The accuracy of the maximum-minimum temperature system (MMTS) is +/- 0.5
degrees C, and the temperature is displayed to the nearest 0.1 degree F. The observer records the values to the nearest whole degree F. A Cooperative Program Manager calibrates the MMTS sensor annually against a specially maintained reference instrument.&quot;
http://www1.ncdc.noaa.gov/pub/data/documentlibrary/tddoc/td3200.pdf

So before any adjustments are made, the data has an error range of +/- 1F or .5C !

Then it is adjusted least 3 times before it is handed to GISS
http://www.ncdc.noaa.gov/oa/climate/research/ushcn/

Time of Observation Bias Adjustments (Adjustment #1) (Error range unknown)
&quot;Next, monthly temperature values were adjusted for the time-of-observation bias (Karl, et al. 1986; Vose et al., 2003). 

The TOB-adjustment software uses an empirical model to estimate and adjust the monthly temperature values so that they more closely resemble values based on the local midnight summary period.&quot;

Homogeneity Testing and Adjustment Procedures (Adjustment #2) (Error range may be shown by NCDC, see below)
&quot;Following the TOB adjustments, the homogeneity of the TOB-adjusted temperature series is assessed. In previous releases of the U.S. HCN monthly dataset, homogeneity adjustments were performed using the procedure described in Karl and Williams (1987). 
Unfortunately, station histories are often incomplete so artificial discontinuities in a data series may occur on dates with no associated record in the metadata archive. Undocumented station changes obviously limit the effectiveness of SHAP. To remedy the problem of incomplete station histories, the version 2 homogenization algorithm addresses both documented and undocumented discontinuities.&quot;
Estimation of Missing Values (Adjustment #3) (Error range unknown)
&quot;Following the homogenization process, estimates for missing data are calculated using a weighted average of values from highly correlated neighboring values. The weights are determined using a procedure similar to the SHAP routine. This program, called FILNET, uses the results from the TOB and homogenization algorithms to obtain a more accurate estimate of the climatological relationship between stations. The FILNET program also estimates data across intervals in a station record where discontinuities occur in a short time interval, which prevents the reliable estimation of appropriate adjustments.
Urbanization Effects (NCDC says this is covered by their Homogenization algorithms)
In the original HCN, the regression-based approach of Karl et al. (1988) was employed to account for urban heat islands. In contrast, no specific urban correction is applied in HCN version 2 because the change-point detection algorithm effectively accounts for any &quot;local&quot; trend at any individual station. In other words, the impact of urbanization and other changes in land use is likely small in HCN version 2.&quot;

Now after starting out with an observation error range of +/- 1F (.5C). Every one of these prior adjustments adds uncertainty to the data.

For example:

1. Raw Data point is 15C +/- .5C    That means the range is 14.5C to 15.5C
2. The first adjustment add +/- .25. Now the range is 14.25C to 15.75C
3. Second adjustment +/- .25 Now the range is 14C to 16C
4. Third adjustment is +/- .505 Now the range is 13.5C to 16.5C!

I chose these numbers for 2,3 &amp; 4 as examples, I do not yet know the real numbers. However I chose their net value because the NCDC gives an example in the document that describes their process. Their chart for Reno shows error bars that look to be around 1.8C to 2C range error introduced by their adjustments. This is additive to the +/- .5 C built in to the raw measurement as there is no indication it includes the raw error range. It could actually be worse as it is unclear if the TOB &amp; Missing data interpolation is part of their uncertainty calculation.
http://www.ncdc.noaa.gov/oa/climate/research/ushcn/


Only after these adjustments are doen GISS get the data for merge into the GHCN.
http://data.giss.nasa.gov/gistemp/sources/gistemp.html

Then, incredibly, they make more adjustments!

http://data.giss.nasa.gov/gistemp/sources/gistemp.html
First they remove the Adjustment #3 data from above. So in a sense they remove one source of error. (Adjustment #4)
&quot;The reports were converted from F to C and reformatted; data marked as being filled in using interpolation methods were removed.&quot;

If they only remove part of Adjustment #3, then more uncertainty is introduced.

This indicates GISS is using the NCDC/USHCN data that has been through Adjustment #3 and they take it mostly back to Adjustment #2.

Then, they homogenize the data again! (Adjustment #5)

&quot;The goal of the homogeneization effort is to avoid any impact (warming
or cooling) of the changing environment that some stations experienced
by changing the long term trend of any non-rural station to match the
long term trend of their rural neighbors, while retaining the short term
monthly and annual variations. If no such neighbors exist, the station is
completely dropped, if the rural records are shorter, part of the
non-rural record is dropped.&quot;

The specific stated goal of this adjustment is to take into account Urban Heat Island effect. Yet, NCDC says they already adjusted for this when they homongenized the data! Now the data is twice baked for UHI. (Which I thought the IPCC and Jones, Wang (1990) said was negligible)

A bit concerning is the video data analysis show UHI is still in the data by sampling city/urban pairs around the country. Hmm... are we smarter than a 6th grader..:-) (I need the URL, but it is well known and easily reproduced independently)

Roman M has done an excellent job in his blog showing these GISS adjustments are driving a bias into the data. 
http://statpad.wordpress.com/2009/12/12/ghcn-and-adjustment-trends/

I have sampled numerous individual stations in CA and seen the same bias being introduced by this this process. I described the process for doing this in comments over at WUWT. Others using that method have found the same results in NY, Grand Canyon, Calgary, etc. http://wattsupwiththat.com/ (I need to find the exact links, sorry)

So there are two building concerns about this final step. First, it appears duplicative to (at least in the US) what has already been done. Second it appears to be reshaping the curves to fit the story. No one has any indication if this is just a bad algorithm or deliberate. 

Don&#039;t forget, this also introduces uncertainty. NCDC estimated their homogenization introduced up to +/- .9C if I read their example chart correctly.


So right now it appears the inherent cumulative range of error far exceeds the claimed warming signal that has supposedly detected. 

This chart shows GISS claiming a warming signal of .6 C detected. 
http://data.giss.nasa.gov/gistemp/2008/

Remember, even the raw data was +/- .5 C from the moment it was written down per the NCDC.

The most incredibly generous reading of the Reno example for NCDC (assuming it includes the raw error rate, TOB, Missing Value Estimates included) shows an error band of at best +/- .9 C.

Then there is whatever uncertainty is added by the GISS process that also appears to bend the curve. 

I don&#039;t claim to know all the right numbers for the total uncertainty being introduced into the data. However, this error budget must be fully disclosed and understood. It certainly appears that the signal is less than the noise introduced by the original measurement and the up to 5 adjustments. Exactly by how much is critical to prove the point that a warming signal has in fact been detected. 

I don&#039;t know what process the raw European data goes through. Until someone describes the path from observation to the end, it is hard to say.
Your post show early 20th century adjustments of +/- 1C. Given my earlier mistake on GISS &quot;raw&quot; that turned out to already have been modified by NCDC, you may want to investigate if your data may be in the same position. Assuming a similar raw observation error of +/- .5C, the cumulative error range is already +/- 1.5C. It is really hard to claim a 1C signal detection in that environment. 

Given this is an open review process, I&#039;m sure others will find mistakes in this post, let me know and I will investigate and correct as required.</description>
		<content:encoded><![CDATA[<p>Steven,</p>
<p>Your post proves a point, but perhaps not the one you wanted to make.</p>
<p>The initial mistake I made was to assume GHCN was adjusting raw data, but at least in the US, it has already been adjusted a number of times by NCDC for the USHCN. Each step introducing more possible smaller error while removing gross discontinuities. It has been an eye opening journey to see how many times the data is adjusted by various algorithms. I&#8217;m sure I still don&#8217;t have it all completely right, but this is what I have seen so far at least for US data.You may want to check that the raw is actually raw.</p>
<p>My observation is that the accumulation of these uncertainties appears to exceed the range of detected warming signal that is claimed. </p>
<p>Every time someone adjustments the data they also increase the band of uncertainty. This uncertainty builds upon the uncertainty already in the raw data prior to hand off to GHCN. Many of the adjustments appear to have legitimate reasons of trying to remove large discontinuities or false overall trends. However, every time they modify the data with an algorithm that reduces the volatility, they add some uncertainty even while these other problems are fixed.</p>
<p>In the US, the data is first gathered daily from the station.<br />
The data is collected and reported in 1 degree F increments.</p>
<p>DSI-3200 Page 4:<br />
&#8220;The accuracy of the maximum-minimum temperature system (MMTS) is +/- 0.5<br />
degrees C, and the temperature is displayed to the nearest 0.1 degree F. The observer records the values to the nearest whole degree F. A Cooperative Program Manager calibrates the MMTS sensor annually against a specially maintained reference instrument.&#8221;<br />
<a href="http://www1.ncdc.noaa.gov/pub/data/documentlibrary/tddoc/td3200.pdf" rel="nofollow">http://www1.ncdc.noaa.gov/pub/data/documentlibrary/tddoc/td3200.pdf</a></p>
<p>So before any adjustments are made, the data has an error range of +/- 1F or .5C !</p>
<p>Then it is adjusted least 3 times before it is handed to GISS<br />
<a href="http://www.ncdc.noaa.gov/oa/climate/research/ushcn/" rel="nofollow">http://www.ncdc.noaa.gov/oa/climate/research/ushcn/</a></p>
<p>Time of Observation Bias Adjustments (Adjustment #1) (Error range unknown)<br />
&#8220;Next, monthly temperature values were adjusted for the time-of-observation bias (Karl, et al. 1986; Vose et al., 2003). </p>
<p>The TOB-adjustment software uses an empirical model to estimate and adjust the monthly temperature values so that they more closely resemble values based on the local midnight summary period.&#8221;</p>
<p>Homogeneity Testing and Adjustment Procedures (Adjustment #2) (Error range may be shown by NCDC, see below)<br />
&#8220;Following the TOB adjustments, the homogeneity of the TOB-adjusted temperature series is assessed. In previous releases of the U.S. HCN monthly dataset, homogeneity adjustments were performed using the procedure described in Karl and Williams (1987).<br />
Unfortunately, station histories are often incomplete so artificial discontinuities in a data series may occur on dates with no associated record in the metadata archive. Undocumented station changes obviously limit the effectiveness of SHAP. To remedy the problem of incomplete station histories, the version 2 homogenization algorithm addresses both documented and undocumented discontinuities.&#8221;<br />
Estimation of Missing Values (Adjustment #3) (Error range unknown)<br />
&#8220;Following the homogenization process, estimates for missing data are calculated using a weighted average of values from highly correlated neighboring values. The weights are determined using a procedure similar to the SHAP routine. This program, called FILNET, uses the results from the TOB and homogenization algorithms to obtain a more accurate estimate of the climatological relationship between stations. The FILNET program also estimates data across intervals in a station record where discontinuities occur in a short time interval, which prevents the reliable estimation of appropriate adjustments.<br />
Urbanization Effects (NCDC says this is covered by their Homogenization algorithms)<br />
In the original HCN, the regression-based approach of Karl et al. (1988) was employed to account for urban heat islands. In contrast, no specific urban correction is applied in HCN version 2 because the change-point detection algorithm effectively accounts for any &#8220;local&#8221; trend at any individual station. In other words, the impact of urbanization and other changes in land use is likely small in HCN version 2.&#8221;</p>
<p>Now after starting out with an observation error range of +/- 1F (.5C). Every one of these prior adjustments adds uncertainty to the data.</p>
<p>For example:</p>
<p>1. Raw Data point is 15C +/- .5C    That means the range is 14.5C to 15.5C<br />
2. The first adjustment add +/- .25. Now the range is 14.25C to 15.75C<br />
3. Second adjustment +/- .25 Now the range is 14C to 16C<br />
4. Third adjustment is +/- .505 Now the range is 13.5C to 16.5C!</p>
<p>I chose these numbers for 2,3 &amp; 4 as examples, I do not yet know the real numbers. However I chose their net value because the NCDC gives an example in the document that describes their process. Their chart for Reno shows error bars that look to be around 1.8C to 2C range error introduced by their adjustments. This is additive to the +/- .5 C built in to the raw measurement as there is no indication it includes the raw error range. It could actually be worse as it is unclear if the TOB &amp; Missing data interpolation is part of their uncertainty calculation.<br />
<a href="http://www.ncdc.noaa.gov/oa/climate/research/ushcn/" rel="nofollow">http://www.ncdc.noaa.gov/oa/climate/research/ushcn/</a></p>
<p>Only after these adjustments are doen GISS get the data for merge into the GHCN.<br />
<a href="http://data.giss.nasa.gov/gistemp/sources/gistemp.html" rel="nofollow">http://data.giss.nasa.gov/gistemp/sources/gistemp.html</a></p>
<p>Then, incredibly, they make more adjustments!</p>
<p><a href="http://data.giss.nasa.gov/gistemp/sources/gistemp.html" rel="nofollow">http://data.giss.nasa.gov/gistemp/sources/gistemp.html</a><br />
First they remove the Adjustment #3 data from above. So in a sense they remove one source of error. (Adjustment #4)<br />
&#8220;The reports were converted from F to C and reformatted; data marked as being filled in using interpolation methods were removed.&#8221;</p>
<p>If they only remove part of Adjustment #3, then more uncertainty is introduced.</p>
<p>This indicates GISS is using the NCDC/USHCN data that has been through Adjustment #3 and they take it mostly back to Adjustment #2.</p>
<p>Then, they homogenize the data again! (Adjustment #5)</p>
<p>&#8220;The goal of the homogeneization effort is to avoid any impact (warming<br />
or cooling) of the changing environment that some stations experienced<br />
by changing the long term trend of any non-rural station to match the<br />
long term trend of their rural neighbors, while retaining the short term<br />
monthly and annual variations. If no such neighbors exist, the station is<br />
completely dropped, if the rural records are shorter, part of the<br />
non-rural record is dropped.&#8221;</p>
<p>The specific stated goal of this adjustment is to take into account Urban Heat Island effect. Yet, NCDC says they already adjusted for this when they homongenized the data! Now the data is twice baked for UHI. (Which I thought the IPCC and Jones, Wang (1990) said was negligible)</p>
<p>A bit concerning is the video data analysis show UHI is still in the data by sampling city/urban pairs around the country. Hmm&#8230; are we smarter than a 6th grader..:-) (I need the URL, but it is well known and easily reproduced independently)</p>
<p>Roman M has done an excellent job in his blog showing these GISS adjustments are driving a bias into the data.<br />
<a href="http://statpad.wordpress.com/2009/12/12/ghcn-and-adjustment-trends/" rel="nofollow">http://statpad.wordpress.com/2009/12/12/ghcn-and-adjustment-trends/</a></p>
<p>I have sampled numerous individual stations in CA and seen the same bias being introduced by this this process. I described the process for doing this in comments over at WUWT. Others using that method have found the same results in NY, Grand Canyon, Calgary, etc. <a href="http://wattsupwiththat.com/" rel="nofollow">http://wattsupwiththat.com/</a> (I need to find the exact links, sorry)</p>
<p>So there are two building concerns about this final step. First, it appears duplicative to (at least in the US) what has already been done. Second it appears to be reshaping the curves to fit the story. No one has any indication if this is just a bad algorithm or deliberate. </p>
<p>Don&#8217;t forget, this also introduces uncertainty. NCDC estimated their homogenization introduced up to +/- .9C if I read their example chart correctly.</p>
<p>So right now it appears the inherent cumulative range of error far exceeds the claimed warming signal that has supposedly detected. </p>
<p>This chart shows GISS claiming a warming signal of .6 C detected.<br />
<a href="http://data.giss.nasa.gov/gistemp/2008/" rel="nofollow">http://data.giss.nasa.gov/gistemp/2008/</a></p>
<p>Remember, even the raw data was +/- .5 C from the moment it was written down per the NCDC.</p>
<p>The most incredibly generous reading of the Reno example for NCDC (assuming it includes the raw error rate, TOB, Missing Value Estimates included) shows an error band of at best +/- .9 C.</p>
<p>Then there is whatever uncertainty is added by the GISS process that also appears to bend the curve. </p>
<p>I don&#8217;t claim to know all the right numbers for the total uncertainty being introduced into the data. However, this error budget must be fully disclosed and understood. It certainly appears that the signal is less than the noise introduced by the original measurement and the up to 5 adjustments. Exactly by how much is critical to prove the point that a warming signal has in fact been detected. </p>
<p>I don&#8217;t know what process the raw European data goes through. Until someone describes the path from observation to the end, it is hard to say.<br />
Your post show early 20th century adjustments of +/- 1C. Given my earlier mistake on GISS &#8220;raw&#8221; that turned out to already have been modified by NCDC, you may want to investigate if your data may be in the same position. Assuming a similar raw observation error of +/- .5C, the cumulative error range is already +/- 1.5C. It is really hard to claim a 1C signal detection in that environment. </p>
<p>Given this is an open review process, I&#8217;m sure others will find mistakes in this post, let me know and I will investigate and correct as required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on GHCN Antarctic, 8X Actual Trend &#8211; Uses Single Warmest Station by yonason</title>
		<link>http://noconsensus.wordpress.com/2009/12/13/ghcn-antarctic-warming-eight-times-actual/#comment-15826</link>
		<dc:creator>yonason</dc:creator>
		<pubDate>Wed, 16 Dec 2009 03:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6926#comment-15826</guid>
		<description>#75 - Re the &#039;one important person per limo&#039; was analyzed by a blogger who actually took the trouble to calculate who much Copen-ha-ha-ha-ha-thejokesonyou-hagen cost, by their own carbon standards.
http://sweasel.com/archives/5056

Whatever one believes about how the planet&#039;s temperature is changing, I do hope we can all agree that these guys are NOT the ones we want in charge of dealing with it.
http://blog.heritage.org/2009/12/15/morning-bell-they-cant-even-run-a-conference-let-alone-the-global-economy/

Finally, regarding the suggestion to go and get our own data if we don&#039;t like what they have.  That&#039;s just silly.  They are the ones who have been charged with collecting it. They have the obligation to do it right, and they are NOT.
http://static.cbslocal.com/station/wbz/wbz/2009/may/SurfaceStations.pdf</description>
		<content:encoded><![CDATA[<p>#75 &#8211; Re the &#8216;one important person per limo&#8217; was analyzed by a blogger who actually took the trouble to calculate who much Copen-ha-ha-ha-ha-thejokesonyou-hagen cost, by their own carbon standards.<br />
<a href="http://sweasel.com/archives/5056" rel="nofollow">http://sweasel.com/archives/5056</a></p>
<p>Whatever one believes about how the planet&#8217;s temperature is changing, I do hope we can all agree that these guys are NOT the ones we want in charge of dealing with it.<br />
<a href="http://blog.heritage.org/2009/12/15/morning-bell-they-cant-even-run-a-conference-let-alone-the-global-economy/" rel="nofollow">http://blog.heritage.org/2009/12/15/morning-bell-they-cant-even-run-a-conference-let-alone-the-global-economy/</a></p>
<p>Finally, regarding the suggestion to go and get our own data if we don&#8217;t like what they have.  That&#8217;s just silly.  They are the ones who have been charged with collecting it. They have the obligation to do it right, and they are NOT.<br />
<a href="http://static.cbslocal.com/station/wbz/wbz/2009/may/SurfaceStations.pdf" rel="nofollow">http://static.cbslocal.com/station/wbz/wbz/2009/may/SurfaceStations.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Things that make you go HMM … by joshv</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/3649/#comment-15825</link>
		<dc:creator>joshv</dc:creator>
		<pubDate>Wed, 16 Dec 2009 03:48:54 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6984#comment-15825</guid>
		<description>I think the sudden decrease in station counts is suspect, especially when it appears those that have survived have a marked warming bias.  Does GHCN publish their criteria for station inclusion/exclusion?  Ideally they&#039;d have some unbiased criteria which everybody could critique and verify.</description>
		<content:encoded><![CDATA[<p>I think the sudden decrease in station counts is suspect, especially when it appears those that have survived have a marked warming bias.  Does GHCN publish their criteria for station inclusion/exclusion?  Ideally they&#8217;d have some unbiased criteria which everybody could critique and verify.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Things that make you go HMM … by Green R&#38;D Mgr</title>
		<link>http://noconsensus.wordpress.com/2009/12/15/3649/#comment-15823</link>
		<dc:creator>Green R&#38;D Mgr</dc:creator>
		<pubDate>Wed, 16 Dec 2009 03:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://noconsensus.wordpress.com/?p=6984#comment-15823</guid>
		<description>Steven,

Your post proves a point, but perhaps not the one you wanted to make.

The initial mistake I made was to assume GHCN was adjusting raw data, but at least in the US, it has already been adjusted a number of times by NCDC for the USHCN. Each step introducing more possible smaller error while removing gross discontinuities. It has been an eye opening journey to see how many times the data is adjusted by various algorithms. I&#039;m sure I still don&#039;t have it all completely right, but this is what I have seen so far at least for US data. You need to ensure your raw..is in fact raw, not already cooked.

My observation is that the accumulation of these uncertainties appears to exceed the range of detected warming signal that is claimed. 

Every time someone adjustments the data they also increase the band of uncertainty. This uncertainty builds upon the uncertainty already in the raw data prior to hand off to GHCN. Many of the adjustments appear to have legitimate reasons of trying to remove large discontinuities or false overall trends. However, every time they modify the data with an algorithm that reduces the volatility, they add some uncertainty even while these other problems are fixed.

In the US, the data is first gathered daily from the station.
The data is collected and reported in 1 degree F increments.

DSI-3200 Page 4:
&quot;The accuracy of the maximum-minimum temperature system (MMTS) is +/- 0.5
degrees C, and the temperature is displayed to the nearest 0.1 degree F. The observer records the values to the nearest whole degree F. A Cooperative Program Manager calibrates the MMTS sensor annually against a specially maintained reference instrument.&quot;
http://www1.ncdc.noaa.gov/pub/data/documentlibrary/tddoc/td3200.pdf

So before any adjustments are made, the data has an error range of +/- 1F or .5C !

Then it is adjusted least 3 times before it is handed to GISS
http://www.ncdc.noaa.gov/oa/climate/research/ushcn/

Time of Observation Bias Adjustments (Adjustment #1) (Error range unknown)
&quot;Next, monthly temperature values were adjusted for the time-of-observation bias (Karl, et al. 1986; Vose et al., 2003).&quot; 

&quot;The TOB-adjustment software uses an empirical model to estimate and adjust the monthly temperature values so that they more closely resemble values based on the local midnight summary period.&quot;

Homogeneity Testing and Adjustment Procedures (Adjustment #2) (Error range may be shown by NCDC, see below)
&quot;Following the TOB adjustments, the homogeneity of the TOB-adjusted temperature series is assessed. In previous releases of the U.S. HCN monthly dataset, homogeneity adjustments were performed using the procedure described in Karl and Williams (1987). 
Unfortunately, station histories are often incomplete so artificial discontinuities in a data series may occur on dates with no associated record in the metadata archive. Undocumented station changes obviously limit the effectiveness of SHAP. To remedy the problem of incomplete station histories, the version 2 homogenization algorithm addresses both documented and undocumented discontinuities.
Estimation of Missing Values (Adjustment #3) (Error range unknown)
Following the homogenization process, estimates for missing data are calculated using a weighted average of values from highly correlated neighboring values. The weights are determined using a procedure similar to the SHAP routine. This program, called FILNET, uses the results from the TOB and homogenization algorithms to obtain a more accurate estimate of the climatological relationship between stations. The FILNET program also estimates data across intervals in a station record where discontinuities occur in a short time interval, which prevents the reliable estimation of appropriate adjustments.
Urbanization Effects (NCDC says this is covered by their Homogenization algorithms)
In the original HCN, the regression-based approach of Karl et al. (1988) was employed to account for urban heat islands. In contrast, no specific urban correction is applied in HCN version 2 because the change-point detection algorithm effectively accounts for any &quot;local&quot; trend at any individual station. In other words, the impact of urbanization and other changes in land use is likely small in HCN version 2.&quot;

Now after starting out with an observation error range of +/- 1F (.5C). Every one of these prior adjustments adds uncertainty to the data.

For example:

1. Raw Data point is 15C +/- .5C    That means the range is 14.5C to 15.5C
2. The first adjustment add +/- .25. Now the range is 14.25C to 15.75C
3. Second adjustment +/- .25 Now the range is 14C to 16C
4. Third adjustment is +/- .505 Now the range is 13.5C to 16.5C!

I chose these numbers for 2,3 &amp; 4 as examples, I do not yet know the real numbers. However I chose their net value because the NCDC gives an example in the document that describes their process. Their chart for Reno shows error bars that look to be around 1.8C to 2C range error introduced by their adjustments. This is additive to the +/- .5 C built in to the raw measurement as there is no indication it includes the raw error range. It could actually be worse as it is unclear if the TOB &amp; Missing data interpolation is part of their uncertainty calculation.
http://www.ncdc.noaa.gov/oa/climate/research/ushcn/


Only after these adjustments are doen GISS get the data for merge into the GHCN.
http://data.giss.nasa.gov/gistemp/sources/gistemp.html

Then, incredibly, they make more adjustments!

http://data.giss.nasa.gov/gistemp/sources/gistemp.html
First they remove the Adjustment #3 data from above. So in a sense they remove one source of error. (Adjustment #4)
The reports were converted from F to C and reformatted; data marked as being filled in using interpolation methods were removed.If they only remove part of Adjustment #3, then more uncertainty is introduced.

This indicates GISS is using the NCDC/USHCN data that has been through Adjustment #3 and they take it mostly back to Adjustment #2.

Then, they homogenize the data again! (Adjustment #5)

&quot;The goal of the homogeneization effort is to avoid any impact (warming
or cooling) of the changing environment that some stations experienced
by changing the long term trend of any non-rural station to match the
long term trend of their rural neighbors, while retaining the short term
monthly and annual variations. If no such neighbors exist, the station is
completely dropped, if the rural records are shorter, part of the
non-rural record is dropped.&quot;

The specific stated goal of this adjustment is to take into account Urban Heat Island effect. Yet, NCDC says they already adjusted for this when they homongenized the data! Now the data is twice baked for UHI. (Which I thought the IPCC and Jones, Wang (1990) said was negligible)

A bit concerning is the video data analysis show UHI is still in the data by sampling city/urban pairs around the country. Hmm... are we smarter than a 6th grader..:-) (I need the URL, but it is well known and easily reproduced independently)

Roman M has done an excellent job in his blog showing these GISS adjustments are driving a bias into the data. 
http://statpad.wordpress.com/2009/12/12/ghcn-and-adjustment-trends/

I have sampled numerous individual stations in CA and seen the same bias being introduced by this this process. I described the process for doing this in comments over at WUWT. Others using that method have found the same results in NY, Grand Canyon, Calgary, etc. http://wattsupwiththat.com/ (I need to find the exact links, sorry)

So there are some building concerns about this final step. First, it appears duplicative to (at least in the US) what has already been done. Second it appears to be reshaping the curves to fit the story. No one has any indication if this is just a bad algorithm or deliberate. 

Don&#039;t forget, this also introduces uncertainty. NCDC estimated their homogenization introduced up to +/- .9C if I read their example chart correctly.


So right now it appears the inherent cumulative range of error far exceeds the claimed warming signal that has supposedly detected. 

This chart shows GISS claiming a warming signal of .6 C detected. 
http://data.giss.nasa.gov/gistemp/2008/

Remember, even the raw data was +/- .5 C from the moment it was written down per the NCDC.

The most incredibly generous reading of the Reno example for NCDC (assuming it includes the raw error rate, TOB, Missing Value Estimates included) shows an error band of at best +/- .9 C.

Then there is whatever uncertainty is added by the GISS process that also appears to bend the curve. 

I don&#039;t claim to know all the right numbers for the total uncertainty being introduced into the data. However, this error budget must be fully disclosed and understood. It certainly appears that the signal is less than the noise introduced by the original measurement and the up to 5 adjustments. Exactly by how much is critical to prove the point that a warming signal has in fact been detected. 

I don&#039;t know what process the raw European data goes through. Until someone describes the path from observation to the end, it is hard to say. Your post shows early 20th century adjustments of +/- 1C. Given my earlier mistake on GISS &quot;raw&quot; that turned out to already have been modified by NCDC, you may want to investigate if your data may be in the same position. Assuming a similar raw observation error of +/- .5C, the cumulative error range is already +/- 1.5C. It is really hard to claim a 1C signal detection in that environment. 

Given this is an open review process, I&#039;m sure others will find mistakes in this post, let me know and I will investigate and correct as required.</description>
		<content:encoded><![CDATA[<p>Steven,</p>
<p>Your post proves a point, but perhaps not the one you wanted to make.</p>
<p>The initial mistake I made was to assume GHCN was adjusting raw data, but at least in the US, it has already been adjusted a number of times by NCDC for the USHCN. Each step introducing more possible smaller error while removing gross discontinuities. It has been an eye opening journey to see how many times the data is adjusted by various algorithms. I&#8217;m sure I still don&#8217;t have it all completely right, but this is what I have seen so far at least for US data. You need to ensure your raw..is in fact raw, not already cooked.</p>
<p>My observation is that the accumulation of these uncertainties appears to exceed the range of detected warming signal that is claimed. </p>
<p>Every time someone adjustments the data they also increase the band of uncertainty. This uncertainty builds upon the uncertainty already in the raw data prior to hand off to GHCN. Many of the adjustments appear to have legitimate reasons of trying to remove large discontinuities or false overall trends. However, every time they modify the data with an algorithm that reduces the volatility, they add some uncertainty even while these other problems are fixed.</p>
<p>In the US, the data is first gathered daily from the station.<br />
The data is collected and reported in 1 degree F increments.</p>
<p>DSI-3200 Page 4:<br />
&#8220;The accuracy of the maximum-minimum temperature system (MMTS) is +/- 0.5<br />
degrees C, and the temperature is displayed to the nearest 0.1 degree F. The observer records the values to the nearest whole degree F. A Cooperative Program Manager calibrates the MMTS sensor annually against a specially maintained reference instrument.&#8221;<br />
<a href="http://www1.ncdc.noaa.gov/pub/data/documentlibrary/tddoc/td3200.pdf" rel="nofollow">http://www1.ncdc.noaa.gov/pub/data/documentlibrary/tddoc/td3200.pdf</a></p>
<p>So before any adjustments are made, the data has an error range of +/- 1F or .5C !</p>
<p>Then it is adjusted least 3 times before it is handed to GISS<br />
<a href="http://www.ncdc.noaa.gov/oa/climate/research/ushcn/" rel="nofollow">http://www.ncdc.noaa.gov/oa/climate/research/ushcn/</a></p>
<p>Time of Observation Bias Adjustments (Adjustment #1) (Error range unknown)<br />
&#8220;Next, monthly temperature values were adjusted for the time-of-observation bias (Karl, et al. 1986; Vose et al., 2003).&#8221; </p>
<p>&#8220;The TOB-adjustment software uses an empirical model to estimate and adjust the monthly temperature values so that they more closely resemble values based on the local midnight summary period.&#8221;</p>
<p>Homogeneity Testing and Adjustment Procedures (Adjustment #2) (Error range may be shown by NCDC, see below)<br />
&#8220;Following the TOB adjustments, the homogeneity of the TOB-adjusted temperature series is assessed. In previous releases of the U.S. HCN monthly dataset, homogeneity adjustments were performed using the procedure described in Karl and Williams (1987).<br />
Unfortunately, station histories are often incomplete so artificial discontinuities in a data series may occur on dates with no associated record in the metadata archive. Undocumented station changes obviously limit the effectiveness of SHAP. To remedy the problem of incomplete station histories, the version 2 homogenization algorithm addresses both documented and undocumented discontinuities.<br />
Estimation of Missing Values (Adjustment #3) (Error range unknown)<br />
Following the homogenization process, estimates for missing data are calculated using a weighted average of values from highly correlated neighboring values. The weights are determined using a procedure similar to the SHAP routine. This program, called FILNET, uses the results from the TOB and homogenization algorithms to obtain a more accurate estimate of the climatological relationship between stations. The FILNET program also estimates data across intervals in a station record where discontinuities occur in a short time interval, which prevents the reliable estimation of appropriate adjustments.<br />
Urbanization Effects (NCDC says this is covered by their Homogenization algorithms)<br />
In the original HCN, the regression-based approach of Karl et al. (1988) was employed to account for urban heat islands. In contrast, no specific urban correction is applied in HCN version 2 because the change-point detection algorithm effectively accounts for any &#8220;local&#8221; trend at any individual station. In other words, the impact of urbanization and other changes in land use is likely small in HCN version 2.&#8221;</p>
<p>Now after starting out with an observation error range of +/- 1F (.5C). Every one of these prior adjustments adds uncertainty to the data.</p>
<p>For example:</p>
<p>1. Raw Data point is 15C +/- .5C    That means the range is 14.5C to 15.5C<br />
2. The first adjustment add +/- .25. Now the range is 14.25C to 15.75C<br />
3. Second adjustment +/- .25 Now the range is 14C to 16C<br />
4. Third adjustment is +/- .505 Now the range is 13.5C to 16.5C!</p>
<p>I chose these numbers for 2,3 &amp; 4 as examples, I do not yet know the real numbers. However I chose their net value because the NCDC gives an example in the document that describes their process. Their chart for Reno shows error bars that look to be around 1.8C to 2C range error introduced by their adjustments. This is additive to the +/- .5 C built in to the raw measurement as there is no indication it includes the raw error range. It could actually be worse as it is unclear if the TOB &amp; Missing data interpolation is part of their uncertainty calculation.<br />
<a href="http://www.ncdc.noaa.gov/oa/climate/research/ushcn/" rel="nofollow">http://www.ncdc.noaa.gov/oa/climate/research/ushcn/</a></p>
<p>Only after these adjustments are doen GISS get the data for merge into the GHCN.<br />
<a href="http://data.giss.nasa.gov/gistemp/sources/gistemp.html" rel="nofollow">http://data.giss.nasa.gov/gistemp/sources/gistemp.html</a></p>
<p>Then, incredibly, they make more adjustments!</p>
<p><a href="http://data.giss.nasa.gov/gistemp/sources/gistemp.html" rel="nofollow">http://data.giss.nasa.gov/gistemp/sources/gistemp.html</a><br />
First they remove the Adjustment #3 data from above. So in a sense they remove one source of error. (Adjustment #4)<br />
The reports were converted from F to C and reformatted; data marked as being filled in using interpolation methods were removed.If they only remove part of Adjustment #3, then more uncertainty is introduced.</p>
<p>This indicates GISS is using the NCDC/USHCN data that has been through Adjustment #3 and they take it mostly back to Adjustment #2.</p>
<p>Then, they homogenize the data again! (Adjustment #5)</p>
<p>&#8220;The goal of the homogeneization effort is to avoid any impact (warming<br />
or cooling) of the changing environment that some stations experienced<br />
by changing the long term trend of any non-rural station to match the<br />
long term trend of their rural neighbors, while retaining the short term<br />
monthly and annual variations. If no such neighbors exist, the station is<br />
completely dropped, if the rural records are shorter, part of the<br />
non-rural record is dropped.&#8221;</p>
<p>The specific stated goal of this adjustment is to take into account Urban Heat Island effect. Yet, NCDC says they already adjusted for this when they homongenized the data! Now the data is twice baked for UHI. (Which I thought the IPCC and Jones, Wang (1990) said was negligible)</p>
<p>A bit concerning is the video data analysis show UHI is still in the data by sampling city/urban pairs around the country. Hmm&#8230; are we smarter than a 6th grader..:-) (I need the URL, but it is well known and easily reproduced independently)</p>
<p>Roman M has done an excellent job in his blog showing these GISS adjustments are driving a bias into the data.<br />
<a href="http://statpad.wordpress.com/2009/12/12/ghcn-and-adjustment-trends/" rel="nofollow">http://statpad.wordpress.com/2009/12/12/ghcn-and-adjustment-trends/</a></p>
<p>I have sampled numerous individual stations in CA and seen the same bias being introduced by this this process. I described the process for doing this in comments over at WUWT. Others using that method have found the same results in NY, Grand Canyon, Calgary, etc. <a href="http://wattsupwiththat.com/" rel="nofollow">http://wattsupwiththat.com/</a> (I need to find the exact links, sorry)</p>
<p>So there are some building concerns about this final step. First, it appears duplicative to (at least in the US) what has already been done. Second it appears to be reshaping the curves to fit the story. No one has any indication if this is just a bad algorithm or deliberate. </p>
<p>Don&#8217;t forget, this also introduces uncertainty. NCDC estimated their homogenization introduced up to +/- .9C if I read their example chart correctly.</p>
<p>So right now it appears the inherent cumulative range of error far exceeds the claimed warming signal that has supposedly detected. </p>
<p>This chart shows GISS claiming a warming signal of .6 C detected.<br />
<a href="http://data.giss.nasa.gov/gistemp/2008/" rel="nofollow">http://data.giss.nasa.gov/gistemp/2008/</a></p>
<p>Remember, even the raw data was +/- .5 C from the moment it was written down per the NCDC.</p>
<p>The most incredibly generous reading of the Reno example for NCDC (assuming it includes the raw error rate, TOB, Missing Value Estimates included) shows an error band of at best +/- .9 C.</p>
<p>Then there is whatever uncertainty is added by the GISS process that also appears to bend the curve. </p>
<p>I don&#8217;t claim to know all the right numbers for the total uncertainty being introduced into the data. However, this error budget must be fully disclosed and understood. It certainly appears that the signal is less than the noise introduced by the original measurement and the up to 5 adjustments. Exactly by how much is critical to prove the point that a warming signal has in fact been detected. </p>
<p>I don&#8217;t know what process the raw European data goes through. Until someone describes the path from observation to the end, it is hard to say. Your post shows early 20th century adjustments of +/- 1C. Given my earlier mistake on GISS &#8220;raw&#8221; that turned out to already have been modified by NCDC, you may want to investigate if your data may be in the same position. Assuming a similar raw observation error of +/- .5C, the cumulative error range is already +/- 1.5C. It is really hard to claim a 1C signal detection in that environment. </p>
<p>Given this is an open review process, I&#8217;m sure others will find mistakes in this post, let me know and I will investigate and correct as required.</p>
]]></content:encoded>
	</item>
</channel>
</rss>