<div><br></div> This was pretty close to my reaction.<div><br></div><div> When everyone first started picking up CB radios in the 1980s, the explicit purpose was to coordinate observation efforts and to share information with people in the area that could enable them to see something they might otherwise miss. When it comes down to it, the purpose hasn't changed. In addition to eruption times, this includes such information as extended overflows of North Goggles, event cycles at Fan and Mortar, and the beginning of hot periods at Giant, for example.</div> <div><br></div><div> By that measure, the signal-to-noise ratio has gotten truly horrendous in recent years, and even if it hadn't, it's not clear what use this information would be to anyone farther away than local radio range. This listserv, Geyser Times, and <a href="http://geysers.net" target="_blank">geysers.net</a> already provide eruption data and descriptions within minutes to hours after it happens. That really ought to be good enough for those of us located hundreds or thousands of miles away.<br> <div><br></div><div> For the sake of perspective, consider this: Before the existence of the internet and the listserv, if something rare like Giant, Morning, or Steamboat happened, unless someone called and told you, the first you'd hear about it would be days to weeks later when you received a postcard from GOSA. For less dramatic developments (Fan and Mortar emerging from dormancy, say), the news might not arrive until the next Sput, potentially months later.</div> <div><br></div><div> The daily updates from the internet are nice by comparison, but they're also more than sufficient for practical planning purposes. Like Jim, I can't imagine why anyone would subject themselves to geyser basin FRS traffic if they weren't in a position to act on the information it occasionally contains.</div> <div><br></div><div>David Schwarz</div> <div><br><div class="gmail_quote">On Thu, Jul 12, 2012 at 7:58 PM, <span dir="ltr"><<a href="mailto:jimscheir@aol.com" target="_blank">jimscheir@aol.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <font color="black" face="arial"> <div>I cannot imagine why anyone wants the FRS radio calls from the Geyser Basin broadcast over the internet. The vast majority are of no interest to those of us in the Park, let alone those not here. The incessant calls to repeat the last transmission, the requests for help in finding lost children, the calls from the Visitor Center of "has anyone seen Daisy or Riverside", the requests to go to channel 5, the constant calls this year from the crane operators at the Inn to one another, the visitors calling to one another not knowing it is the Geyser Channel (this year for a whole day in Spanish), the often garbled calls, the people who have put their radio on Voice Activation, etc. make it a real pain much of the time to listen to channel 4.5 in the Basin when we have to listen to hear the Geyser Eruption times. A high proportion of the calls never reach the Visitor Center because the reception inside is terrible and the noise level is high. </div> <div> </div> <div>There are also issues of legality that would have to be settled. Some statements I have seen indicate that no FRS signals may be sent over phone lines at any time. Whether that would apply to the internet sent over lines that include phone lines in some places is unclear. There are also other legal issues to be investigated and permissions that would be needed.</div> <div> </div> <div>Another issue is whether permission is needed to rebroadcast transmissions made by those speaking. This also includes the issue of privacy. A number of gazers have already stated that they will stop all broadcasting on their radios if the transmissions are put on the internet. </div> <div> </div> <div>I talked to all the Gazers who are here now and spend a lot of time in the Park and none of us thinks that the FRS radio calls should be broadcast.</div> <div> </div> <div>Jim Scheirer</div> <div> </div> <div> </div> <div> </div> <div> </div> <div> </div> <div></div> <div style="font-size:10pt;font-family:arial,helvetica"><div><div>-----Original Message-----<br> From: Will Boekel <<a href="mailto:wolveslax65@comcast.net" target="_blank">wolveslax65@comcast.net</a>><br> To: Listserve <<a href="mailto:geysers@lists.wallawalla.edu" target="_blank">geysers@lists.wallawalla.edu</a>><br> Sent: Tue, Jul 10, 2012 8:11 pm<br> Subject: [Geysers] FRS Radio Broadcasting Project<br> <br> <div> <div dir="ltr"> <div style="font-size:12pt;font-family:"Calibri""> <div>Yesterday I was playing around with my new FRS radios and was able to get my laptop to record the transmissions by plugging in a ipod headphone cord from the radio’s headset jack to my laptop’s microphone jack. I then mentioned that I was able to do this on the chat page and KC listed off a few services that can broadcast the FRS radio calls . I am currently busy right now with my own projects but if some one would like to take on the project of making the FRS radio calls available on the internet feel free to do so. I bet many people including myself will be thrilled at having the FRS calls broadcasted over the internet.</div> <div> </div> <div>Will Boekel</div> </div> </div> </div> </div></div><div style="font-size:12px;font-family:Tahoma,Verdana,Arial,Sans-Serif;margin:0px"> <pre style="font-size:9pt"><tt>_______________________________________________ Geysers mailing list <a href="mailto:Geysers@lists.wallawalla.edu" target="_blank">Geysers@lists.wallawalla.edu</a> <a href="https://lists.wallawalla.edu/mailman/listinfo/geysers" target="_blank">https://lists.wallawalla.edu/mailman/listinfo/geysers</a> </tt></pre> </div> </div> </font><br>_______________________________________________<br> Geysers mailing list<br> <a href="mailto:Geysers@lists.wallawalla.edu" target="_blank">Geysers@lists.wallawalla.edu</a><br> <a href="https://lists.wallawalla.edu/mailman/listinfo/geysers" target="_blank">https://lists.wallawalla.edu/mailman/listinfo/geysers</a><br></blockquote></div><br></div></div>