Part 2 is now online here.
One of the things I am often accused of is “denying” the Mann hockey stick. And, by extension, the Romm Hockey stick that Mann seems to embrace with equal fervor.
While I don’t “deny” these things exist, I do dispute their validity as presented, and I’m not alone in that thinking. As many of you know Steve McIntyre and Ross McKitrick, plus many others have extensively debunked statistics that went into the Mann hockey stick showing where errors were made, or in some cases known and simply ignored because it helped “the cause”.
The problem with hockey stick style graphs is that they are visually compelling, eliciting reactions like whoa, there’s something going on there! Yet, oftentimes when you look at the methodology behind the compelling visual you’ll find things like “Mike’s Nature Trick“. The devil is always in the details, and you often have to dig very deep to find that devil.
Just a little over a month ago, this blog commented on the hockey stick shape in the USHCN data set which you can see here:
The graph above was generated by” Stephen Goddard” on his blog and it generated quite a bit of excitement and attention.
At first glance it looks like something really dramatic happened to the data, but again when you look at those devilish details you find that the visual is simply an artifact of methodology. Different methods clearly give different results and the”hockey stick” disappears when other methods are used.
The graph above is courtesy of Zeke Hausfather Who co-wrote that blog entry with me. I should note that Zeke and I are sometimes polar opposites when it comes to the surface temperature record. However, in this case we found a point of agreement. That point was that the methodology gave a false hockey stick.
I wrote then:
While Goddard’s code and plot produced a mathematically correct result, the procedure he chose (#1 The All Absolute Approach) comparing absolute raw USHCN data and absolute finalized USHCN data, was not, and it allowed non-climatic differences between the two datasets, likely caused by missing data (late reports) to create the spike artifact in the first four months of 2014 and somewhat overstated the difference between adjusted and raw temperatures by using absolute temperatures rather than anomalies.
Interestingly, “Goddard” replied and comments with a thank you for helping to find the reason for this hockey stick shaped artifact. He wrote:
stevengoddard says:
http://wattsupwiththat.com/2014/05/10/spiking-temperatures-in-the-ushcn-an-artifact-of-late-data-reporting/#comment-1632952 May 10, 2014 at 7:59 am
Anthony,
Thanks for the explanation of what caused the spike.
The simplest approach of averaging all final minus all raw per year which I took shows the average adjustment per station year. More likely the adjustments should go the other direction due to UHI, which has been measured by the NWS as 8F in Phoenix and 4F in NYC.
Lesson learned. It seemed to me that was the end of the issue. Boy, was I wrong.
A couple of weeks later in e-mail Steven Goddard circulated a new graph with a hockey stick shape which you can see below. He wrote to me and a few others on the mailing list this message:
Here is something interesting. Almost half of USHCN data is now completely fake.
http://stevengoddard.wordpress.com/2014/06/01/more-than-40-of-ushcn-station-data-is-fabricated/
After reading his blog post I realized he had made a critical error and I wrote back an e-mail the following:
This claim: “More than 40% of USHCN final station data is now generated from stations which have no thermometer data.”
Is utterly bogus.
This kind of unsubstantiated claim is why some skeptics get called conspiracy theorists. If you can’t back it up to show that 40% of the USHCN has stopped reporting, then don’t publish it.
What I was objecting to was the claim if 40% of the USHCN network was missing – something I know from my own studies to be a false claim.
He replied back with a new graph and the strawman argument and a new number:
The data is correct.
…
Since 1990, USHCN has lost about 30% of their stations, but they still report data for all of them. This graph is a count of valid monthly readings in their final and raw data sets.
The problem was, I was not disputing the data, I was disputing the claim that 40% of USHCN stations were missing and had “completely fake” data (his words). I knew that to be wrong. So I replied with a suggestion.
On Sun, Jun 1, 2014 at 5:13 PM, Anthony wrote:
I have to leave for the rest of the day, but again I suggest you take this post down, or and the very least remove the title word “fabricated” and replace it with “loss” or something similar.Not knowing what your method is exactly, I don’t know how you arrived at this, but I can tell you that what you plotted and the word “fabricated” don’t go together they way you envision.Again, we’ve been working on USHCN for years, we would have noticed if that many stations were missing.Anthony
Later when I returned, I noted a change had been made to Goddard’s blog post. The word “fabrication” remained but made a small change with no mention of it to the claim about stations. Since I had open a new browser window I had the before and after that change which you can see below:
http://wattsupwiththat.files.wordpress.com/2014/06/goddard_before.png
http://wattsupwiththat.files.wordpress.com/2014/06/goddard_after.png
I thought it was rather disingenuous to make that change without noting it, but I started to dig a little deeper and realized that Goddard was doing the same thing he was before when we pointed out the false hockey stick artifact in the USHCN; he was performing a subtraction on raw versus the final data.
I then knew for certain that his methodology wouldn’t hold up under scrutiny, but beyond doing some more private e-mail discussion trying to dissuade him from continuing down that path, I made no blog post or other writings about it.
Four days later, over at Lucias blog “The Blackboard” Zeke Hausfather took note of the issue and wrote this post about it: How not to calculate temperature
Zeke writes:
The blogger Steven Goddard has been on a tear recently, castigating NCDC for making up “97% of warming since 1990″ by infilling missing data with “fake data”. The reality is much more mundane, and the dramatic findings are nothing other than an artifact of Goddard’s flawed methodology.
…
Goddard made two major errors in his analysis, which produced results showing a large bias due to infilling that doesn’t really exist. First, he is simply averaging absolute temperatures rather than using anomalies. Absolute temperatures work fine if and only if the composition of the station network remains unchanged over time. If the composition does change, you will often find that stations dropping out will result in climatological biases in the network due to differences in elevation and average temperatures that don’t necessarily reflect any real information on month-to-month or year-to-year variability. Lucia covered this well a few years back with a toy model, so I’d suggest people who are still confused about the subject to consult her spherical cow.
His second error is to not use any form of spatial weighting (e.g. gridding) when combining station records. While the USHCN network is fairly well distributed across the U.S., its not perfectly so, and some areas of the country have considerably more stations than others. Not gridding also can exacerbate the effect of station drop-out when the stations that drop out are not randomly distributed.
The way that NCDC, GISS, Hadley, myself, Nick Stokes, Chad, Tamino, Jeff Id/Roman M, and even Anthony Watts (in Fall et al) all calculate temperatures is by taking station data, translating it into anomalies by subtracting the long-term average for each month from each station (e.g. the 1961-1990 mean), assigning each station to a grid cell, averaging the anomalies of all stations in each gridcell for each month, and averaging all gridcells each month weighted by their respective land area. The details differ a bit between each group/person, but they produce largely the same results.
Now again, I’d like to point out that Zeke and I are often polar opposites when it comes to the surface temperature record but I had to agree with him on this point; the methodology created the artifact. In order to properly produce a national temperature gridding must be employed, using the raw data without gridding will create various artifacts.
Spatial interpolation (gridding) for a national average temperature would be required in a constantly changing dataset, such as GHCN/USHCN, no doubt, gridding is a must. For a guaranteed quality dataset, where stations will be kept in the same exposure, producing reliable data, such as the US Climate Reference Network (USCRN), you could in fact use the raw data as a national average and plot it. Since it is free of the issues that gridding solves, it would be meaningful as long as the stations all report, don’t move, aren’t encroached upon, and don’t change sensors- i.e. the design and production goals of USCRN.
Anomalies aren’t necessarily required, they are an option depending on what you want to present. For example NCDC gives an absolute value for the national average temperature in their State of the Climate report each month, they also give a baseline and the departure anomaly from that baseline for both CONUS and Global temperature.
Now let me qualify that by saying that I have known for a long time that NCDC uses in filling of data from surrounding stations as part of the process of producing a national temperature average. I don’t necessarily agree with their methodology as being perfect, but it is a well-known issue and what Goddard discovered was simply a back door way of pointing out that the method exists. It wasn’t news to me and to many others who have followed the issue.
This is why you haven’t seen other prominent people in the climate debate ( Spencer, Curry, McIntyre, Michaels, McKitrick) and even myself make a big deal out of this hockey stick of data difference that Goddard has been pushing. If this were really an important finding you can bet they and yours truly would be talking about it and providing support and analysis.
It’s also important to note that Goddards graph does not represent a complete loss of data from these stations. The differencing method that Goddard is using detects every missing data point from every station in the network. This could be as simple as one day of data missing in an entire month, or a string of days, or even an entire month which is rare. Almost every station in the USHCN at one time or another is missing some data. One exception might be the station at Mohonk Lake, New York which has a perfect record due to a dedicated observer, but has other problems related to siting.
If we were to throw out an entire month’s worth of observations because one day out of 31 is missing, chances are we’d have no national temperature average at all. So the method was created to fill in missing data from surrounding stations. In theory and in a perfect world this would be a good method, but as we know the world is a messy place, and so the method introduces some additional uncertainty.
The National Cooperative Observer network a.k.a. co-op is a mishmash of widely different stations and equipment. the co-op network is a much larger set of stations than the USHCN. The USHCN is a subset of the larger co-op network comprising some 8000 stations around the United States. Some are stations in Observer’s backyards, or at their farms, some are at government entities like fire stations and Ranger stations, some are electronic ASOS systems at airports. The vast majority of stations are poorly sited as we have documented using the surface station project, by our count 80% of the USHCN as poorly sited stations. The real problem is with the micro-site issues of the stations. this is something that is not effectively dealt with in any methodology used by NCDC. We’ll have more on that later but I wanted to point out that no matter which data set you look at (NCDC, GISS, HadCRUT, BEST) the problem of station siting bias remains and is not dealt with. for those who don’t know NCDC provides the source data for the other interpretations of the surface temperature record, so they all have it. More on that later, perhaps in another blog post.
When it was first created the co-op network was done entirely on paper forms called B – 91’s. the observer would write down the daily high and low temperatures along with precipitation for each day of the month and then at the end of the month mail it in. An example B-91 form from Mohonk Lake, NY is shown below:

Not all forms are so well maintained. Some B-91 forms have missing data, which can be due to the observer missing work, having an illness, or simply being lazy:
The form above is missing weekends because the secretary at the fire station doesn’t work on weekends and the firefighters aren’t required to fill in for her. I know this having visited this station and I interviewed the people involved.
So, in such an imperfect “you get what you pay for” world of volunteer observers, you know from the get-go that you are going to have missing data, and so, in order to be able to use any of these at all, a method had to be employed to deal with it, and that was infilling of data. This has been a process done for years, long before Goddard “discovered” it.
There was no nefarious intent here, NOAA/NCDC isn’t purposely trying to “fabricate” data as Goddard claims, they are simply trying to be able to figure out a way to make use of it at all. The word “fabrication” is the wrong word to use, as it implies the data is being plucked out of thin air. It isn’t – it is being gathered from nearby stations and used to create a reasonable estimate. Over short ranges one can reasonably expect daily weather (temperature at least, precip not so much) to be similar assuming the stations are similarly sited and equipped but that’s where another devil in the details exists.
Back when I started the surfacestations project, I noted one long-period well sited station, Orland was in a small sea of bad stations, and that its temperature diverged markedly from its neighbors, like the horrid Marysville Fire station where the MMTS thermometer was directly next to asphalt:
Orland is one of those stations that reports on paper at the end of the month. Marysville (shown above) reported daily using the touch-tone weathercoder, so its data was available by the end of each day.
What happens in the first runs of the NCDC CONUS temperature process is that they end up with mostly the airports ASOS stations and the weathercoder stations. The weathercoder reporting stations tend to be more urban than rural since a lot of observers don’t want to make long distance phone calls. And so in the case of missing station data on early in the month runs, we tend to get a collection of the poorer sited stations. The FILNET process, designed to “fix” missing data goes to work, and starts infilling data.
A lot of the “good” stations don’t get included in the early runs, because the rural observers often opt for a paper form mailed in rather than the touch-tone weathercoder, and those stations have data infilled from many of the nearby ones, “polluting” the data.
And we have shown back in 2012, those stations have a much lower century scale trend than than the majority of stations in the surface network. In fact, by NOAA’s own siting standards, over 80% of the surface network is producing unacceptable data and that data gets blended in.
Steve McIntyre noted that even in good stations like Orland, the data gets “polluted” by the process:
http://climateaudit.org/2009/06/29/orland-ca-and-the-new-adjustments/
So, imagine this going on for hundreds of stations, perhaps even thousands early on in the month.
To the uninitiated observer, this “revelation” by Goddard could look like NCDC is in fact “fabricating” data. Given the sorts of scandals that have happened recently with government data such as the IRS “loss of e-mails”, the padding of jobs and economic reports, and other issues from the current administration I can see why people would easily embrace the word “fabrication” when looking at NOAA/NCDC data. I get it. Expecting it because much of the rest of the government has issues doesn’t make it true though.
What is really going on is that the FILNET algorithm, design to fix a few stations that might be missing some data in the final analysis is running a wholesale infill on early incomplete data, which NCDC pushes out to their FTP site. The process gets to be less and less as the month goes on, as more data comes in.
But over time, observers have been less inclined to produce reports, and attrition in both the USHCN and and the co-op network is something that I’ve known about for quite some time having spoken with hundreds of observers. Many of the observers are older people and some of the attrition is due to age, infirmity, and death. You can see what I’m speaking of my looking through the quarterly NOAA co-op newsletter seen here: http://www.nws.noaa.gov/om/coop/coop_newsletter.htm
NOAA often has trouble finding new observers to take the place of the ones they have lost, and so, it isn’t a surprise that over time we would see the number missing data points rise. Another factor is technology many observers I spoke with wonder why they still even do the job when we have computers and electronics that can do the job faster. I explained to them that their work is important because automation can never replace the human touch. I always thank them for their work.
The downside is that the USHCN and is a very imperfect and heterogeneous network and will remain so; it isn’t “fixable” at an operational level, so statistical fixes are resorted to. That has both good and bad influences.
The newly commissioned USCRN will solve that with its new data gathering system, some of its first data is now online for the public.
Source: NCDC National Temperature Index time series plotter
Since this is a VERY LONG post, it will be continued…in part 2
In part 2 I’ll talk about things that we disagree on and the things we can find a common ground on.
Part 2 is now online here.
Discover more from Watts Up With That?
Subscribe to get the latest posts sent to your email.





![marysville_badsiting[1]](http://wattsupwiththat.files.wordpress.com/2014/06/marysville_badsiting1.jpg?resize=480%2C360&quality=83)

Talldave2,
Interestingly enough, my recent paper on UHI found results similar to Steve’s blog post in the raw data:
I look forward to the corrections that will restore the 20C negative US trend. 🙂
Also, you may have missed the part in Steve’s post where he uses anomalies rather than absolute temperatures :-p
Not relevant, as he wasn’t looking for something hidden in baseline cooling. Do you at least acknowledge that using anomalies will tend to hide baseline cooling?
Its worth mentioning again that infilling (as done by NCDC) has virtually no effect on the trends in temperatures over time
Not the homogenized temps, no, because you’re smearing them around anyway. That’s why you need to use the absolute, unhomogenized data. It’s like you’re mixing plain and chocolate milk together, pouring the result into cups marked PLAIN and CHOCOLATE, and then noting that removing the cups labelled CHOCOLATE doesn’t change the overall chocolate content of all your milk. Well, of course not!
This kind of 3-card monte is why Goddard insists on using actual recorded temperatures.
Sigh, I feel like we’ve had the same conversation way too many times now. But I thank Zeke for stopping by and engaging anyway, it’s more than anyone else seems willing to do.
I’ll reserve further comment until Tony’s part 2 and try to do something productive 🙂
Well, I guess Zeke is going to once again ignore my request for a valid link to the NCDC data processing software. That’s OK – whenever we get into these discussions, no one wants to give us the software source codes that NCDC is using so we can see exactly how they are arriving at their adjustments! [sigh].
And it doesn’t matter what metrics GISS and other publish since they start with the NCDC adjusted temperatures, and rightly point to them if there is a problem or glitch (unless of course the issue is with the crappy processing algorithm GISS is using…).
Dave, that’s a great analogy…..
This claim: “More than 40% of USHCN final station data is now generated from stations which have no thermometer data.”
—–
He replied back with a new graph and the strawman argument and a new number:
—–
The data is correct.
Since 1990, USHCN has lost about 30% of their stations, but they still report data for all of them.
——-
UH, he was talking about two different things………..
The trouble with anomalies …
By my count, there are only 51 stations with 360 monthly values from 1961-1990 (Zeke’s baseline) that are not estimated.
Its all chocolate milk …
Nick Stokes, Zeke, Anthony.
What we need is an R script that creates Estimated values for any set of USHCN monthly values we choose to throw at it.
Just the Final Step to start with.
Then we can compare what USHCN “estimates” to reality by randomly removing stations.
That way we could actual see how “Estimating” works … or doesn’t work. And run it for the next year or 2.
And we need the old data to quit changing.
Transparency is important.
“I assume the trend continues and that similar corrections have been/are being applied to global data.”
Nick Stokes said at 2:33 am
No. TOBS is an issue with the volunteer observers of the US Coop. In ROW, observers are usually employees who are given instructions.
So the adjustments stopped at the U.S. border and the beginning of the new millennium. Interesting.
Sort of like sea level rise notching up a click or two when the altimetry satellites were launched in 1992
Anthony says:
“The newly commissioned USCRN will solve that with its new data gathering system, some of its first data is now online for the public.”
And cited said “first data” via the Contiguous US Average Temperature Anomaly graph.
Source: NCDC National Temperature Index time series plotter
——————–
I found that graph quite interesting given the fact that the greatest “anomaly” (+/- of the 0.00 grid line) for each of the years covered by said graph (2004 thru 2014) always occurred between the normally “coldest” of months of November and February inclusive.
None of said greatest “anomalies” occurred during the normally “hottest” of months of June and August inclusive.
Now if I am reading said graph correctly ….. then my question is:
What has the most effect on the US Yearly Average Surface Temperature calculations, ….. the “winter” (Nov/Feb inclusive) temperature anomalies ….. or the “summer” (June/Aug inclusive) temperature anomalies?
In other words, are the “warmer” winter temperatures “driving” the claimed increase in Average Surface Temperatures, ……. or are the “hotter” summer temperatures “driving” the claimed increase in Average Surface Temperatures?
Or, “in other words” as stated by:
GeologyJim on: June 25, 2014 at 2:33 pm
“The averages seem to show upward trends over time, but much of that seems due to rising overnight low values – – not to rising daytime high temperatures. Does anyone really doubt this?”
—————-
Just change the two (2) “noted” words in his above comment to read …. “The averages seem to show upward trends over time, but much of that seems due to rising winter time low values” …….. not to rising “summer time high temperatures”.
————
And my next question is, …… why is anyone getting excited or concerned about the adjusted, … infilled …. and/or interpolated data that is contained within the various temperature records of/for the past forty (40) years …. when they are, …. in actuality, …… like 500% more accurate than the adjusted, … infilled …. and/or interpolated data that is contained within the various temperature records from pre-1950?
It is of my opinion that if one wishes to have more accurate Average Surface Temperature measurements then it is prerequisite that all Surface Measurement Stations be converted to “liquid anti-freeze” based measurements ….. whereby the “liquid” volume itself would do the “averaging” of all the daily/weekly variations in/of near-surface air temperatures.
“It takes less time to do a job right … than it does to explain why you did it wrong”
“No record has been destroyed”
Is that true? Didn’t CRU toss the originals because they “lacked storage space?”
Even if you believe that no recorded raw data is missing, it is abundantly clear that thermometers have been destroyed. There are fewer of them today than 30 years ago. Given the “save the Planet” peril believed by key people governing the disbursement of funds, you’d think we would be measuring with more thermometers more frequently than ever. So there is no doubt that records that should have and could have should be made have been destroyed. It is far easier to fabricate data than it is to actually measure it.
Finally, I return to BEST. (See WUWT June 10, Why Automatic Temperature adjustments Don’t Work and my concuring comment. The BEST process of slicing long running records, preserving instrument drift and cutting out the recalibration destroys records. It destroys recalibration information. It preserves noise from drift as signal. The scalpel it destroys long records and replaces them with shorter segments, thereby attenuates and filters out the lower frequency components of the Fourier spectrum in the original data. Climate signal is ALL low frequency — it is Weather that is high frequency. No amount of regional homogenization can preserve the low frequency content destroyed in the slicing process. The most homogenization can do is “fabricate” low frequency in the final product. In this case, perhaps a better word than “fabricate” is “counterfeit” — to make something that looks real, to use it as real, but has little real intrinsic value. The coin looks good, but most of the gold has been removed from the alloy.
“Well, I guess Zeke is going to once again ignore my request for a valid link to the NCDC data processing software. That’s OK – whenever we get into these discussions, no one wants to give us the software source codes that NCDC is using so we can see exactly how they are arriving at their adjustments! [sigh].”
ftp://ftp.ncdc.noaa.gov/pub/data/ghcn/v3/software/52i/
http://www1.ncdc.noaa.gov/pub/data/ghcn/v3/techreports/Technical%20Report%20NCDC%20No12-02-3.2.0-29Aug12.pdf
http://www.ncdc.noaa.gov/oa/climate/research/ushcn/#phas
“Reg Nelson says:
June 25, 2014 at 8:03 pm
This debate seems to me to be an exercise in futility.
Goddard could arguably be misguided or biased, and may have used flawed logic, but he is absolutely correct, there is missing data.”
################
when there is missing data there is ONE THING you can NEVER do.
average absolute temperatures.
If people can begin to see that, then we can have a real discussion about the OPTIONS
one has when data is missing.
But one thing is clear. If there is missing data you cannot average absolute temperatures.
that is what goddard does. it is wrong. It is the most wrong solution to the problem of missing data
“It takes less time to do a job right … than it does to explain why you did it wrong” Excellent this is why Zekes and Stokes and other modelers replies go on for hourssssss. LOLJust joking please take it lightly.
I await part 2 but on one (small) point I must disagree with Anthony when he writes ” The word “fabrication” is the wrong word to use, as it implies the data is being plucked out of thin air. It isn’t – it is being gathered from nearby stations and used to create a reasonable estimate.” The word fabrication means exactly what it says – the data has been constructed and not observed.
It many be that the construction is soundly based but it is still a construct. If, as suggested by RossP, Sunshinehours1 and Eliza, 40% of the data is fabricated then the room for error is substantial, no matter how sound the estimation.
Didn’t CRU toss the originals because they “lacked storage space?”
=============
At 09:41 AM 2/2/2005, Phil Jones wrote:
Mike, I presume congratulations are in order – so congrats etc !
Just sent loads of station data to Scott. Make sure he documents everything better this time ! And don’t leave stuff lying around on ftp sites – you never know who is trawling them. The two MMs have been after the CRU station data for years. If they ever hear there is a Freedom of Information Act now in the UK, I think I’ll delete the file rather than send to anyone.
“The two MMs have been after the CRU station data for years. If they ever hear there is a Freedom of Information Act now in the UK, I think I’ll delete the file rather than send to anyone.”
For the past few weeks I’ve lurked at nearly all the sites doing the arguing on this subject, and it dawns on me that the arguments against Steve G’s approach are tenuous. It seems to me for a variety of reasons starting with the actual measured and unadjusted data is considered wrong when question is how do the adjustments effect the unadjusted data.
But then when we see alternative solutions, it is to adjust the unadjusted data, or ignore major portions of it away.
What am I missing in this discussion?
Mosher: “But one thing is clear. If there is missing data you cannot average absolute temperatures.”
But if only 51 stations have 360 monthly values for 1961-1990, you can’t do anomalies either. The “baseline” is contaminated by missing data.
So do I have this right
Every station has an individual climatology from which the anomalies are calculated
When a station is missing data it refers to the nearest station that has data using the nearest stations climatology.
All the stations are then grid averaged (grid weighting included of course)
OK so now a whole lot of missing stations report in. However with the new data the climatology reverts to its old self so that as data is added the climatology is constantly shifting (for each station). This then triggers a change in the past record because using the new un-infilled data changes the past climatology therefore the anomaly calculations. The algorithm is built to constantly scan for problems so the changes in reporting stations constantly alter the past.
This sounds crazy…. a constantly shifting climatology data record…just weird someone please tell me I am wrong.
Part 2 is now online here http://wattsupwiththat.com/2014/06/25/on-denying-hockey-sticks-ushcn-data-and-all-that-part-2/
Oh, by the way Mosher. There is only ONE station with no data flags between 1961 and 1990.
USH00301012 BUFFALO NIAGARA INTL
Steven Mosher says:
June 26, 2014 at 10:00 am
Link #1 is dead (does not work for me)…does it work for you? If so, please upload the software to a third party site.
Links #2 and #3 have no source code.
Sorry…
Averaging these intensive properties is completely physically meaningless. So no, averaging “absolute temperatures” or “anomalies” doesn’t “work fine”, unless your goal is something meaningless.
Steven Mosher says:
June 26, 2014 at 10:07 am
“……..
################
when there is missing data there is ONE THING you can NEVER do.
average absolute temperatures……”
//////////////////////////////////
I sometimes wonder whether you read what you write before you submit your comments.
If there is missing data, there is missing data. It makes no difference as to whether the missing data is the absolute temperature, or the anomaly. The underlying data is mssing, simples.
When you fabricate the anomaly, you are in effect fabricating the absolute temperature, albeit you are entering it in your ‘records’ as an anomaly, not as an absolute temperature figure.
The importent point is that every time there is missing data, the error in the record grows. Every time there is missing data, it becomes more and more uncertain what the observed and collected data is telling us. This becomes particularly problematic when we are trying to wean out a signical in the form of anomalies measured in tenths of degree in circumstances where the underlying uncertainty in the raw data is in whole degrees. The signal is less than the bandwith of the marghin of error in the data stream,
I understand your arguments when discussing the thermometer record ‘well that’s all we have’, and whilst I accept that this forces us to make the best of a bad bunch, what is important is to make it absolutely clear how unreliable the record being discussed and interpreted actually is, and its true margins of error. The biggest problem when discussing these data sets is the less than honest (and I use that expression deliberately) detailing and recognition of the margin of error bandwidth, and consequential over reliance upon the certainty of what they are telling us. we are over extrapolating the record beyond its reasonable bounds, and this should be faced up to. .
Averages are abstract numbers. The sole purpose of “averages” is to obtain a “snap-shot” picture of a specific entity at a specific time. Thus, they only exist in “time & place” but can be or are represented by a numerical figure. They are neither concrete nor physical quantities …. and therefore should never be used to make “statements-of-fact” about anything except the calculated “average” itself.
Given the fact that “averages” are abstract numbers it matters little if the “number set” is in error or not, ….. the calculated “average” for said “number set” is still a correct figure.
Remember, ….. “averages” are akin to ”boats”, ….. they “rise & fall” with the changes in/of the “waves & tides”. And “tsunamis”, also. 🙂 :)