I, myself, happen to work in a meteorological company and have an easy indicator: When our meteorologists all take off at the same time, rain is imminent.
Topological or topographical? It's kinda both in your example.
I'm no expert, but I don't think topology features much in the weather models. It's mostly numerical analysis and statistics.
As for competing with looking at NOAA radar images, try a little experiment: Next time rain is headed your way, look at a radar animation and try to quantify when the rain will start. The fact that I'm completely unable to do that (even while looking at the damn radar animation) with any accuracy is the reason I started building this app.
Your points about feedback are valid, however.
Does anyone think it could also be useful to tie a twitter feed in with weather information? I feel like weather is one of those things that ppl complain about on twitter all the time; some simple geolocation and keyword matching and you could pull up recent geolocated tweets near you. Could be a nice qualitative weather report to accompany the actual data (people like a personal face on the weather).
It is very popular and it beats looking out of the window by a large margin. When it is raining you can see very accurately how long it's going to take for it to stop so you can decide if it's worth waiting. When it's not raining but it looks like it could be going to rain you can similarly make good predictions.
Note that they're not doing actual prediction, they're just showing radar images of the clouds of the last hour.
Because what appears to be missing is any sort of feedback mechanism by which to improve the accuracy of it's predictions on the same scale as which it is making its predictions.
In other words, if the prediction was rain in 8 minutes for 15 minutes, how can the program determine if it was accurate? (And suggests the question, is rain in 4 minutes for 18 minutes an acceptable level of inaccuracy?). Where does the data that it was 18 minutes of rain come from?