Understanding Temperature Readings in New York City
If you live in or visit New York City and check a weather source reporting temperatures in Celsius, the numbers can feel arbitrary until you understand what they actually represent. The National Weather Service operates reporting stations at Central Park, JFK, LaGuardia, and several smaller sites. Each records data differently. Central Park, which sits near the urban core, tends to run warmer than coastal stations during winter nights because of the heat island effect. That gap matters more than people realize. The core reading most people see comes from the Central Park station, specifically the one maintained by NOAA at the old Central Park Observatory. It records temperatures at roughly 142 feet above sea level with instruments shielded about 2 meters off the ground. That height and location were chosen decades ago to be representative of the broader city. They still are, mostly, though surrounding construction and paving have shifted readings slightly over time. When you look at Celsius conversions of NYC temperature records, keep in mind that the official record-keeping format uses tenths of a degree. A reading of 98.6 degrees Fahrenheit converts to exactly 37.0 Celsius. The precision is real, not cosmetic. Historical records from before 1869, when systematic recording began at Central Park, relied on less consistent instrumentation, so the earliest data carries more uncertainty than the modern era.
I spent a week last February trying to correlate daily high temperatures with how cold it actually felt while walking around Queens. The Central Park forecast called for a high of -6.7 Celsius (20 degrees Fahrenheit), but wind gusts from a nor'easter pushed the real-feels down further. Checking the nearby Central Park South station, which is slightly more sheltered, the wind chill was worse by about three degrees compared to the main observatory. If you are planning outdoor activity, do not rely on a single station reading. Cross-reference at least two nearby sites.
What the Numbers Actually Show
New York City has seen its average annual temperature rise about 1.5 Celsius over the past fifty years. That sounds small. It is not. The shift shows up most clearly in the number of days per year where the low temperature stays above 0 Celsius during winter. Fifty years ago, Central Park averaged roughly 42 days above freezing in December through February. Now that number sits closer to 58 days. The change is gradual enough that locals barely notice it year to year, but it alters everything from winter maintenance costs to the types of plants that survive in community gardens. Heat records tell a similar story. The all-time highest temperature recorded at Central Park is 106 degrees Fahrenheit (41.1 Celsius), set on July 9, 1936. Since then, temperatures in the 40s Celsius have become more common. The year 2023 saw New York City cross 100 degrees Fahrenheit (37.8 Celsius) for the first time ever in its record-keeping history. That does not mean the thermometer broke. It means the baseline has shifted. There is a common misconception that Celsius readings for New York winters are more bearable than Fahrenheit ones because the numbers are lower. A temperature of -1 Celsius feels just as brutal as 30.2 Fahrenheit. The conversion does not change the physical reality. People who move here from countries using Celsius sometimes make the mistake of thinking New York weather is mild because summer highs only reach into the mid-30s Celsius. They underestimate humidity. A reading of 35 Celsius with 80 percent relative humidity hits the body differently than dry heat at the same number. The apparent temperature, or heat index, pushes past 45 Celsius under those conditions.
Get the Full Details

How to Read Records Accurately
The official records live on the NOAA National Centers for Environmental Information website, specifically the daily summaries for Central Park and the airport stations. The data is downloadable as CSV. I prefer pulling raw data rather than trusting third-party summaries because some websites round aggressively or omit outlier days entirely. If you download the raw file for Central Park from 2000 to 2025, you will find nearly 9,000 daily entries. Each row contains the date, max temperature, min temperature, and average temperature, all in both Fahrenheit and Celsius columns. One thing most people miss when reviewing these records: the Celsius column is calculated, not independently measured. The raw instrument data comes out in Fahrenheit. The Celsius values are derived by applying the conversion formula after the fact. This means there can be tiny rounding differences between what a Celsius-native observer would record and what appears in the NOAA tables. The differences are usually less than 0.1 degrees, but if you are doing precision work, like analyzing microclimate shifts across neighborhoods, you should calculate Celsius yourself from the raw Fahrenheit values rather than trusting the pre-converted column. Another detail that trips people up involves daylight saving time. The weather records use local civil time, which switches between EST and EDT. That means some days in March and November have 23 or 25 hours instead of 24. When you are aggregating monthly averages, those shift days do not materially distort the numbers, but if you are looking at hourly patterns, the transition can create the illusion of a temperature anomaly that does not actually exist.
What This Means for People Here
For residents, the most practical application of understanding these trends is planning. The gradual warming means heating seasons are shortening by roughly five to seven days per year in the current decade compared to the early 2000s. That translates to a small but real reduction in heating bills for buildings that rely on older systems. At the same time, cooling seasons are lengthening, and the days when air conditioning becomes necessary have increased by about ten days over the same period. If you own property or manage a building, factor both directions into your budgeting. Visitors often approach weather data with little context. A forecast showing a high of 2 Celsius in January sounds cold but manageable if you are coming from somewhere like Sweden or Canada. In reality, New York January wind and precipitation make 2 Celsius feel sharper than that number suggests. The wind factor alone can drop the perceived temperature by 5 to 8 degrees Celsius on a typical winter day. Pack accordingly, regardless of what the thermometer says. Summer visitors face the opposite problem. They see 30 Celsius and think mild. New York humidity regularly pushes the heat index well past that number. A day forecast at 32 Celsius with high humidity can produce conditions equivalent to over 40 Celsius in terms of how the body experiences it. That is the distinction between the number on the screen and what actually affects your comfort or safety outdoors.
Where the Data Falls Short
The biggest limitation of relying on Central Park as the sole reference point is that it does not represent the whole city. Astoria runs cooler in summer due to the water proximity. The Bronx interior can spike several degrees warmer on stagnant summer days. Staten Island experiences different lake-effect patterns in late fall. Using a single station for city-wide decisions creates blind spots, especially for event planning, construction scheduling, or emergency preparedness. There is also the issue of data gaps. Older records, particularly from the 19th and early 20th centuries, contain missing days and inconsistent measurement times. Some entries are interpolated from nearby stations, which means certain Celsius values in the historical dataset are estimates rather than direct observations. If you are researching long-term trends, these gaps matter less for broad conclusions. If you are checking whether a specific date in 1921 was the warmest on record for that month, you may be working with incomplete information. The best workaround I have found is to cross-check Central Park data against the JFK and LaGuardia records whenever possible. The airport stations have their own quirks, but comparing three sources smooths out individual station anomalies and gives a clearer picture of actual citywide conditions. It takes extra time, maybe ten to fifteen minutes per data query, but it prevents wrong assumptions that come from trusting one location.
