This might the site you are talking about.

http://saratoga-weather.org/wdparser.php

-----
Tom
On May 19, 2019, 6:35 PM -0500, gjr80 <gjroder...@gmail.com>, wrote:
> Ok, that fixed a few issues with clientraw.txt but now the parsing of 
> clientraw.txt is failing when it hits fields containing a time. Again no spec 
> for clientraw.txt to work from but we have found that any field representing 
> a time needs to be in the format HH:MM:SS or HH:MM. At the moment your time 
> fields are in the format HH:MM:SS XX where XX is AM or PM. This probably 
> comes down to changes you may have made when troubleshooting (or perhaps 
> something else). Rather than me asking 20 questions it is probably easier if 
> you could post your [StdReport] stanza from weewx.conf - that will give me 
> the [[wdClientrawReport]] and [[Defaults]] stanzas.
>
> As an aside the parsing issues with clientraw.txt become fairly evident when 
> you view your clientraw.txt in a parsed and tabulated format. There was (may 
> still be - not sure) an online parser that you could give the url to your 
> clientraw files and it would parse and display in tabular form. I created my 
> own version and have plugged in your clientraw.txt data - I will leave it up 
> for a while and you can view it here. Have a look down the 'Value' column and 
> you will soon see where the values do not match the description/units (field 
> 134) onwards). You can then see why you are getting correct data in day and 
> month but incorrect year - because year is after the initial parse error.
>
> Gary
>
> On Monday, 20 May 2019 02:16:07 UTC+10, Sean Garland wrote:
> > Good morning!
> >
> > Thanks Gary for that insight.  I've noticed the behavior of the correct 
> > into being overwritten by something in the past and didn't really 
> > understand what was happening.  It's very clear now.
> >
> > What was really interesting is that although N/A was still present in the 
> > clientraw.txt, the page was displaying correctly this morning.  I did add 
> > the section you recommended, and it did replace the N/A's with "- -".  Now 
> > when I use the Saratoga clientraw parser, things seem to be in all the 
> > right places, and correct in value.  Doing a refresh however, shows 
> > incorrect date now (after showing correct), but everything else looks good.
> >
> > Since the date should be M-d-YYYY (which shows for a second), and then 
> > after refresh is m/d/-Y (negative)... I'm assuming now it's a simple(r) 
> > data parsing issue.
> >
> > Thank you!
> > Sean
> --
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/e7a5108e-e9ef-459e-a65c-6fd1a12a5840%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5663a0bd-81d3-4565-a37d-438b34c3b9e5%40Spark.
For more options, visit https://groups.google.com/d/optout.

Reply via email to