-
Notifications
You must be signed in to change notification settings - Fork 3
/
readme.html
100 lines (97 loc) · 7.05 KB
/
readme.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
<!DOCTYPE html>
<html>
<head>
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-169907378-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-169907378-1');
</script>
<meta charset="utf-8" />
<title>MR Weather - Readme</title>
</head>
<body>
<h1>Mussel Rock Weather Conditions Readme</h1>
<p><b>DISCLAIMER:</b> This website is beta. It is going to have bugs and bad data. Always use your
personal judgement before flying.</p>
<h2>How to use this website</h2>
<p>This is <b>NOT</b> a site guide to flying at Mussel Rock. This is just a guide on how to correctly utilize
<a href='index.html'>this website.</a> I made this site for my personal use. And for the record, I can't claim
to be an expert on Mussel Rock flying conditions. I made this website, because I was trying to accumulate enough
flight hours to complete my P3 rating, and I found the forecasts/data to generally not be reliable. And I would see on
Telegram that other people were flying when conditions on wunderground looked unflyable. I live about 20 minutes
away, so if conditions seem good it's easy enough to just hop in the car to check it out. But it also is a waste
of time if conditions are unflyable/unsafe. I just want to maximize my effort, and I think this website works
pretty well as a spot check before driving down.
<br/><br/>
So I generally read the whole page top to bottom before deciding to go. There is data from multiple sources,
and individually they mostly have mediocre data quality. But if you combine and correlate the data, you can
get much more value out of them. And if you don't look through all the data, you can easily miss out on a red flag
such as rotor/fog/whitecaps/etc. and then waste a trip out to MR. I built this website, and even I've still wasted
a few trips due to not looking at all the data.
<br/><br/>
KCADALYC1. This station is hosted at someone's house on Longview drive. I think that they also
host the Mussel Rock webcams. I don't know the person, but I am very grateful for their data. This station is
frequently in rotor when the wind has a South component. The easiest way to confirm that it's in rotor is to
compare the wind speed with the station at Coyote. If Coyote is showing higher winds, then KCADALYC1 is probably
in rotor. When it's in rotor, just ignore all the data from this station.
<br/><br/>
KCADALYC37. This station is at the Coyote launch. If you are standing on launch, and facing
the water, it's just on your left. This station has had some past problems with solar power, it's battery, and
wind direction sensor. Those issues seem like they are fixed now. I think this wind meter frequently
under-reports data by approximately 1-2 mph. I like to launch from Coyote and Walker, so I pay a lot of attention
to this meter.
<br/><br/>
KCAPACIF205. This station is at Sharp Park Beach. It's run by the same person who operates the
Pacifica webcams(pacificaview.net). As of September 2020, this is a brand new station. I don't have any
specific knowledge on how it might be effected by rotor. The elevation of the station is very low, so I would
expect that it will under-report if there is any wind gradient. And also it's not on-site, so it's possible
that conditions could be different between Mussel Rock and the Pacifica Pier. I believe that this could be really
valuable data, but only time will tell.
<br/><br/>
KCASANFR69. This station is at Fort Funston. This station isn't at Mussel Rock, so it can be somewhat
different. Most importantly it is higher than the other two stations. So if there is a wind gradient, it might
show the wind as higher than the other two meters. This is important to avoid getting blown over the back. So
if Fort Funston is reporting 20mph, and the others are reporting 12mph, you better be careful.
<br/><br/>
Mussel Rock webcams. The still image data might be stale. I couldn't find a programatic way to check the staleness
of that data. But check for fog. It's possible that the fog could be low enough to show up on the webcams, but high
enough to still be able to do some flying.
<br/><br/>
The Cheetah YouTube live stream is awesome. You can check fog levels down lower than the static webcams. And
I've sometimes seen people flying Cheetah. If someone is already flying, it's on.
<br/><br/>
Fort Funston webcams. These are potentially useful for checking fog height, and a wind sock is in view as well.
Sometimes you can see hanggliders staging, which can be a good indicator.
<br/><br/>
Pacifica Webcams. I only show the webcam pointed at the flag, but there are a few webcams at Pacifica. The ones
on YouTube are really great video quality. The flag should act as another data point to confirm wind direction
and speed. Remember the flag is closer to sea level, so it's possible to have light winds there, but stronger
winds higher. The pier points directly West, so try to use that to determine the direction of the wind. This
webcam also has enough detail to show whitecaps. Put it in full screen mode on YouTube to get the best view of
potential whitecaps.
<br/><br/>
Fog chart. I think this is useful for seeing how thick the fog is. Some days it makes sense to do some
parawaiting, and wait for the fog to clear. Some days it's not going to clear. This thing uses satellite
data, and I don't think it can really tell clouds from low fog. Low fog is not flyable, but high fog might be
fine.
<br/><br/>
Tide chart. The data for the tide chart actually refers to a NOAA station at the Golden Gate
Bridge near Chrissy Field. So it's not exactly the same as Mussel Rock. But you get the big picture of
approximately where the tide is at, and which way the tide is going to move with time. And I think that's what
really matters. Also it's best to confirm these things visually on site, maybe the beach is getting pounded
with giant waves and it's not a safe landing site.
<br/><br/>
NWS Forecast. I haven't really used this too much. Another developer added it in recently, but it could be useful.
<br/><br/>
Windy Forecast. I don't know how useful that thing is. But I use it to forecast
how stable conditions will be. I don't compare the data from the sensors to Windy. I check if Windy thinks
the wind will be consistent or if it thinks that winds will increase/decrease over the next few hours. In
my experience Windy will over report gusts at MR.
<br/><br/>
Also follow the Telegram group for Pacifica. <b>Nothing</b> beats the knowledge from experienced local pilots
onsite.
</p>
</body>
</html>