<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=utf-8"> <meta name=Generator content="Microsoft Word 12 (filtered medium)">  <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=WordSection1> Jake,<o:p></o:p> Would text messages be able to upload directly to a viewable web page or would some interim programming be needed to, for example, batch process a set of entries? Ultimately the processed data should be available for free downloading. Perhaps a standard format for the input would be best to drive such a system, for example:<o:p></o:p> Giant (space) 1322 (space) 08.20.1989<o:p></o:p> Grand (space) 2120 (space) 09.10.2000 (space) T2Q (space) d11.5 [The last entry is an optional duration in decimal minutes. Decimal minutes aren’t hard to calculate – 0.1 is 6 seconds, which is generally close enough even if rounded. Other optional notation such as p6 for a Great Fountain pause could be included.]<o:p></o:p> <o:p> </o:p> All,<o:p></o:p> I’d like to clarify my statement by saying that we should continue to provide data to the Visitor Center. An electronic repository that everyone including NPS can freely access could and should run in parallel to the current process. IMO duplication is far better than not noting an event. Multiple inputs for the same eruption are not a bad thing if the system is properly designed to handle that. Of course, one is better than none but two or more reliable sources are a solid foundation for good journalism. <o:p></o:p> <o:p> </o:p> Udo Freund<o:p></o:p> GOSA Store<o:p></o:p> <a href="www.gosa.org">www.gosa.org</a><o:p></o:p> <o:p> </o:p> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> From: geysers-bounces@lists.wallawalla.edu [mailto:geysers-bounces@lists.wallawalla.edu] On Behalf Of Jacob Young Sent: Monday, August 09, 2010 9:29 PM To: Geyser Observation Reports Subject: RE: [Geysers] OFVC Logbook -- Please Read<o:p></o:p> </div> <o:p> </o:p> I have been thinking about an electronic log book for a while now.  I am happy to lend my programming services to such a project.  A web-based log book would be fairly easy to setup so that anyone with a web browser could add entries.  Each entry can be tagged with the enterers name so future users of the data could say whether it is a 'VR' or not.  An entry could be linked to a YouTube video of the eruption. The possibilities are endless.  With full signal 3G cell reception in the UGB and the advent of smart phones making the real-time update of eruptions from the Monkey Cage a possibility, the time for this is now. I will be embarking on a project for this soon so please contact me with ideas.  I need to speak with Mr. Koenig of <a href="http://geysers.org">geysers.org</a> too since he already has something like this running. -Jake Young<o:p></o:p> <div class=MsoNormal> <hr size=2 width="75%" align=left> </div> On Aug 8, 2010 18:17, GOSA Store <gosastore@roadrunner.com> wrote: <o:p></o:p> <div> The Old Faithful Logbook is an official U.S. Federal Government document, not simply a notepad like the ones we carry around in the basins.  As such it isn’t to be treated lightly.  I’m fairly certain that access to the logbook falls under, among others, the Freedom of Information Act, which governs the public’s rights to access government documents.  U.S. Code 552 basically states that copies of any public record must be made available upon request, but may require payment of a fee for the cost incurred in copying.  Looking at original documents may be restricted for various reasons.  The responsible agency, in this case NPS, should have rules in place regarding access to their original documents.<o:p></o:p>  <o:p></o:p> In the past I have been told that I could not write in the log.  Fine, I have no problem with that and will share my personally collected data as I see fit.  I think now is a good time to discuss building and maintaining a GOSA logbook (preferably electronic) that is kept totally separate from NPS.<o:p></o:p>  <o:p></o:p> Udo Freund<o:p></o:p> GOSA Store<o:p></o:p> <a href="www.gosa.org">www.gosa.org</a><o:p></o:p>  <o:p></o:p> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> From: geysers-bounces@lists.wallawalla.edu [mailto:geysers-bounces@lists.wallawalla.edu] On Behalf Of inezaustin@aol.com Sent: Friday, August 06, 2010 8:34 PM To: geysers@lists.wallawalla.edu Subject: Re: [Geysers] OFVC Logbook -- Please Read<o:p></o:p> </div>  <o:p></o:p> I think we would all like clarification on this.  I, for decades, entered times for obscure geysers.  Then about ten years ago I was pretty much told to take a hike.  Consequently I stopped.  In the last two years when I have requested to see the log I was told no.  So as far as I am concerned the powers that be and I have split the sheets.  If we are once again going to help out with times, I want to know that the battle to get into the VC and do it is worth the effort.  There will be no second chances again as far as I am concerned. Inez <o:p></o:p> <div>  <o:p></o:p> </div> <div>  <o:p></o:p> </div> <div>  <o:p></o:p> </div> <div>  <o:p></o:p> </div> <div> -----Original Message----- From: Ken Reeves <kreeves5@cox.net> To: Geyser Observation Reports <geysers@lists.wallawalla.edu> Sent: Fri, Aug 6, 2010 7:40 am Subject: Re: [Geysers] OFVC Logbook -- Please Read<o:p></o:p> <div id="AOLMsgPart_0_0a05813b-51af-411b-a209-183e1df2cbef"> Dave,    Can you please provide what should or should not be turned in, how we get it into the logbook, which geysers should we turn in, etc. especially for those of us who are fairly new or don't get up there very frequently.    A few years ago, I turned in my observations of some of the lesser geysers, I believe it was Solitaire Geyser, but was told by the ranger at the visitor center, that "we do not record data for that geyser", and it kind of left me with a bad taste on spending the time to gather the data.    Thanks    Ken Reeves    David Monteith wrote:  > .... To be successful,  > geyser gazers need to share information. The logbook provides a  > centralized place for us to put that information. I'm being very  > selfish here. I want to know what is going on. The logbook provides  > the details that don't get onto the list serve. I doesn't matter if the  > NPS wants the information or scientists of park visitors. What matters  > is that we, the geyser gazer community, want the information. So please  > take the time to get your data into the logbook. Your efforts will be  > greatly appreciated.  >  >   _______________________________________________  Geysers mailing list  <a href="mailto:Geysers@lists.wallawalla.edu">Geysers@lists.wallawalla.edu</a>  <a href="https://lists.wallawalla.edu/mailman/listinfo/geyse">https://lists.wallawalla.edu/mailman/listinfo/geyse</a><o:p></o:p> </div> </div> </div> </div> </body> </html>