Re: [weewx-user] Re: Question about the Realtime Gauge-Data Extension

On Tue, Mar 21, 2017 at 4:49 PM, gjr80 wrote: > I have added HTTP POST to rtgd.py using a similar approach to that taken > in the weeWX RESTful API in restx.py. It seems to work well. The php I am > using is: > > // we are only interested in HTTP POST >

Re: [weewx-user] Re: Question about the Realtime Gauge-Data Extension

I have added HTTP POST to rtgd.py using a similar approach to that taken in the weeWX RESTful API in restx.py. It seems to work well. The php I am using is: If OK with you Alec I have mentioned you in the comments as the source of the idea and referenced your repo. I will publish 0.2.11

Re: [weewx-user] Re: Question about the Realtime Gauge-Data Extension

Thanks Tom, that was good to read, will tuck that away for reference in future. Gary On Wednesday, 22 March 2017 01:46:21 UTC+10, Tom Keffer wrote: > > On the general problem of what makes a good RESTful API, I found the > document *RESTful Service Best Practices, Recommendations for Creating

Re: [weewx-user] Re: Question about the Realtime Gauge-Data Extension

Hallelujia, figured out the Weather Underground style wind gauge: http://sinkingsensation.com/wind (Note that the above page is set up for mobile, and lets you swipe to get to a second page). Compare it to my PWS page on Weather Underground:

Re: [weewx-user] Re: Question about the Realtime Gauge-Data Extension

On the general problem of what makes a good RESTful API, I found the document *RESTful Service Best Practices, Recommendations for Creating Web Services * very informative. It would definitely recommend a POST. -tk On Tue, Mar

Re: [weewx-user] Re: Question about the Realtime Gauge-Data Extension

> > A lot of thank's for your great work. > Please... could we have a copy of this example wind page? Sure, I'll add a stripped down version to my GitHub. Note that all the code is a available currently by viewing the source. > Thank's a lot. > > El martes, 21 de marzo de 2017, 3:28:02

Re: [weewx-user] Re: Question about the Realtime Gauge-Data Extension

> > Just wondering if there was any particular reason you used a GET rather than > a POST? I think the code to support passing the data via GET is a little > simpler than a POST but since GET includes all of the data in the URL my > nginx access log is getting hammered. I estimate about 55Mb

[weewx-user] Re: Question about the Realtime Gauge-Data Extension

Alec, Just wondering if there was any particular reason you used a GET rather than a POST? I think the code to support passing the data via GET is a little simpler than a POST but since GET includes all of the data in the URL my nginx access log is getting hammered. I estimate about 55Mb per

[weewx-user] Re: Question about the Realtime Gauge-Data Extension

A lot of thank's for your great work. Please... could we have a copy of this example wind page? Thank's a lot. El martes, 21 de marzo de 2017, 3:28:02 (UTC+1), Alec Bennett escribió: > > I made a quick page that updates some data from the real time gauge using > Ajax: > >

Re: [weewx-user] Re: Question about the Realtime Gauge-Data Extension

On Mon, Mar 20, 2017 at 8:34 PM, gjr80 wrote: > Since you have rapidfire on WU should be being fed the loop windSpeed > values. The loop windSpeed values appear in gauge-data.txt in the wlatest > field not the wspeed field you are using; wspeed is the 'average wind > speed'

[weewx-user] Re: Question about the Realtime Gauge-Data Extension

Since you have rapidfire on WU should be being fed the loop windSpeed values. The loop windSpeed values appear in gauge-data.txt in the wlatest field not the wspeed field you are using; wspeed is the 'average wind speed' which will be the average wind speed over an archive period or 5 minutes

[weewx-user] Re: Question about the Realtime Gauge-Data Extension

Good work, I must admit I had been stuck in the 'file transfer' paradigm rather than 'data transfer' and whilst I have had loop based RSYNC working on my LAN there was too much contention for my liking. I will have have a look at this and see how your approach works for me. Gary On Tuesday,

[weewx-user] Re: Question about the Realtime Gauge-Data Extension

On Tuesday, 21 March 2017 12:28:02 UTC+10, Alec Bennett wrote: > > I made a quick page that updates some data from the real time gauge using > Ajax: > > sinkingsensation.com/wind > > It takes some data from live_data.json (currently wspeed, wgust, bearing, > domwinddir) and displays it,

[weewx-user] Re: Question about the Realtime Gauge-Data Extension

And comparing the page I just made (sinkingsensation.com/wind) to my Weather Underground page (https://www.wunderground.com/personal-weather-station/dashboard?ID=KCAPETAL93#history), the data is slightly different. Does anyone know what data the WU updater uses, and why it would be different?

[weewx-user] Re: Question about the Realtime Gauge-Data Extension

I made a quick page that updates some data from the real time gauge using Ajax: sinkingsensation.com/wind It takes some data from live_data.json (currently wspeed, wgust, bearing, domwinddir) and displays it, updating every 2 seconds. I'd like to add the highest gust of the day though, and

[weewx-user] Re: Question about the Realtime Gauge-Data Extension

Hi, The short answer to your question is no, nothing like that exists at the moment. If you have your web server (or process that wil use gauge-data.txt) on your weeWX machine then it is a simple matter for the generated file to be saved wherever you want, but if you need to transfer the file