There is either a display or setting in the app which tells you that or there is no way to know.
There are lots of ways to guess. But the app will decide what to display using whatever logic it wants from whatever source(s) it wants. It will either share that info with you in the UI or it won’t. And if it won’t, we’re all guessing.
Note that most of what we know as Weather Channel was bought by IBM. They do the analytics (marketing Watson heavily en route) and re-sell to all kinds of 3rd party. The TV station is the only part that was left behind, and they have tried to sell it twice.
They do use input from local “volunteer” stations for forecasts as well as the NWS data (which you can turn off, and only see the local volunteer station for current conditions). Slate’s writeup on it from a few years ago:
Apart from the accuracy and locality of their forecasts, which seems pretty good to me, I really like their 10 day forecast display, which shows a graphical timeline of up to 10 different things with about hourly granularity.
NBC/Universal owns it now, which is why you see shows with Today show people, NBC correspondents on some of the the bigger stories, and crap on weekends.
On the West Coast they go into “Most horrible storms ever” stuff during our prime time, which is post primetime in Atlanta.
Your comments piqued my interest in several things, primarily the significant figure issue in your attached URL. Decimal coordinates are never taken to that extreme: 13-14 characters after the decimal point… Under any circumstance. By my calculations, I arrived at an equivalent area that is orders of magnitude less than yours i.e. .0111 micron squared, further increasing the ridiculous-ness factor (by orders of magnitude). But who’s math is correct isn’t the point (mine were Tequila influenced) but rather:
As others have implied, the “problem” must lie in the URL coding. Interestingly, when I click on your link, sure enough, there are the offending excess of decimal places in the URL. However, when I searched the National Weather Service site myself for that same location, here’s the URL that turned up:
[noparse]“National Weather Service”]http://forecast.[/noparse]
Notice the small derivation in coordinates. Additionally, every location I searched afterwards contained the same minimal 2 to 4 (hence more believable) decimal positions.
Perhaps it’s a browser issue, or a DNS lookup routing difference peculiar to your locale. Who knows? It is certainly not a conspiracy by the NWS to masquerade accuracy with outrageous numbers, in a lame attempt to appease some folks’ lack of confidence in their forecasting.
After the fact: I just noticed a four mile discrepancy (yours to mine) in the location descriptor on the two web pages.
I’ve learned so much here. Always suspected the numerous “weather apps” simply rehashed NWS data with their own twist, but I didn’t know that some utilize independent local observation stations… Interesting.
I wonder if/how this improves their forecast accuracy. It seems to me, other than stating the obvious, (It’s raining on Euclid Ave. right now) unless they possess a magic algorithm that the NWS doesn’t have, this information would be pretty topical.
Another interesting thing: Some comments here reinforce the impression I’ve often had of some folks when it comes to weather forecasters, i.e. they truly resent it when a prediction falls short of perfection. It makes me wonder: In what form of reality do they base their discontent, and begs the question: name any other profession that has a better track record predicting the future? Granted, sometimes it’s a bummer when they are wrong, but over the decades, weather forecasting has dramatically improved, and continues to do so. No one else can make that claim. If so, speak up… I’m listening.
Unfortunately, accuracy of the volunteer stations depends on the person not being an idiot.
Two days ago, we had winds to 27, gusts to 38 NW(at the airport). All the volunteer stations had winds from 7-17 and some didn’t register gusts. Directions from W to SE with one SSW.
Not to undermine your statement but, how is the accuracy of their instrumentation a reflection on the volunteer’s intellect? Or is it something else?
FYI: Our local statistics often vary greatly from our local airport two miles away.
Flat as a pancake here. Wind is about 85-90% of the time from the NW.
There’s a large flag an the entrance to the park we live in and it was clearly in a high wind on the day in question.
It’s obvious that the wind gauges are not sited correctly to get a clear reading.
There’s also no reason for stations a few blocks apart to have a 10 degree difference(usually summer) in temps. We don’t do microclimates here.
Yes, it sounds unrealistic in your situation, (no microclimates) but again… Why must it be the volunteer’s intellect at fault, as opposed to the corporation that solicited that particular inappropriate location in the first place?
From what I understand, the volunteers buy their own station and install it themselves. Wunderground does provide instructions for mounting the sensors to get the most accurate readings. Weather station buying guide Installation guide
On the NWS home page http://www.weather.gov/ if you enter your town name and state into the search box at upper left you’ll go to http://forecast.weather.gov/MapClick.php with lat & long parameters showing silly numbers of decimals. Likewise if you go to that page and enter your zip code. The auto-suggest will come up with something like “12345, Yourtown XY, USA”. Select that and you’ll go to the same http://forecast.weather.gov/MapClick.php with the same silly numbers of decimals. But not necessarily the same exact location since towns and zips can have different centroids.
But … once you’re already on the MapClick.php page, entering either a town name or a zip code will refresh that same page with just 4 decimals in the latlongs. It looks like the same search box as the home page but whatever’s going on backstage is not quite the same.
Even 4 decimal places is a bit much. That’s ~36 foot resolution in latitude and ~25’ resolution in longitude at US latitudes. Really?
As I mentioned, this latlong was 20 decimal places a few years ago … someone at the NWS thought that was excessive and reduced to a more reasonable 14 decimal places … great work, folks, no one would think you’re compensating for anything now …
Weather forecasts have improved over the years, but I wouldn’t call this improvement dramatic … we’ve always had a good handle on tomorrow’s weather, and the day after … but then as today, the three-day forecast and beyond involves too much guesswork and the accuracy suffers …
The problem is the lack of good data aloft, sometimes what’s happening at the surface doesn’t reflect what’s happening at 18,000 feet … it’s good we have thermometers every few miles on the ground, but here’s a map of the NWS Rawinsonde Network … it’s a couple hundred miles between sites that measure temperature through the entire air column … this is like asking a chemist to test a chemical with an acid without telling the chemist which acid he’s using, or how strong that acid is …
Another major problem is that unsaturated air behaves differently than air that is fully saturated with water vapor … if the air is at 99.5% relative humidity we’ll see sunny weather, however if the air is 100% RH then the weather will be cloudy and rainy … just a tiny difference changes the weather completely … I think we can see the problems the average weather forecaster has relying on a humidity reading aloft from 100 miles away … this is like giving the chemist a bottle of HCl that’s been unstoppered the past three months, it’s not 12 molar anymore …
The good news is that computers are getting faster by leaps and bounds … so computer modeling of weather is getting better by leaps and bounds … plus this new generation of weather satellites are just amazing in their detail … all-in-all the future is bright for forecasting accuracy, but we’re not quite there yet …
Most people in a city or inner ring suburb don’t have the space to meet those specs.
If you get to watch a windy football game watch when they show the flags around the stadium blowing in multiple directions; the general winds aren’t doing that, the structure is what’s causing the winds to swirl. Buildings, trees, ground elevations (hills, mountains, cliffs) & even wind farms* can cause micro wind changes.
I know of one wind farm that looks like convective activity (thunderstorms) on radar; given the forecast & other (lack of) storms showing on radar, we ignore that ‘storm cell’ when we otherwise wouldn’t fly.
It appears you an I have a difference in opinion over the NWS’s competence compared to other forecasting entities. In support of your issue related to this, is the observation of their (obvious) (sometimes) decimal excess in their Lat/Long URL references. To this, I’ve suggested it is perhaps an issue of software import… To which you reject in favor as proof of a NWS conspiracy…
I contacted (on 12/18) the NWS technical support site for an answer to this question, but as of yet, have received no answer on this issue. I’ll get back to you ASAP when they reply.
We’ll just to have to agree to disagree on your statements here. Perhaps it is a matter of perspective (age). I remember when tomorrow’s forecast was sketchy at best, and day two was 50/50. Day three was in fact, a total wild guess… Now, the three day forecast is nearly a lock cinch. I consider this improvement to be very substantial.
Weather Underground is great. I count 14 stations in my town, and since it’s on the side of a mountain, knowing what is going on at your altitude can be important, because a mile away will be quite different. I usually center my data on the station down the block, next to the sub shop.
That is great for being aware of what is happening a mile away from you at the present time (as it would be anywhere) However, how does this help in your long range planning for general forecasts?