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 > if($_SERVER['REQUEST_METHOD'] == '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 later

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: https://www.wunderground.com/cgi-bin/findweather/get

Re: [weewx-user] WMR200 Station data in Customization Guide

The driver and documentation change were included in v3.3.0, published 5-Dec-2015. If you have a version later than that, the changes are included. -tk On Tue, Mar 21, 2017 at 9:00 AM, Douglas Striff wrote: > How do Obtain this change. My station shows everything fine I believe just > not posti

Re: [weewx-user] WMR200 Station data in Customization Guide

How do Obtain this change. My station shows everything fine I believe just not posting the pressure to Wunderground. On Monday, February 15, 2016 at 8:18:12 PM UTC-5, Tom Keffer wrote: > > Sharp eyes! > > Fixed in commit bca880b >

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 p

Re: [weewx-user] Re: how to provide the csv data source of the charts in StandardReport

On Tue, Mar 21, 2017 at 8:11 AM, Andrew Milner wrote: > The data for the dailyplots is taken from the archive table in the > database by a select statement anyway > The data for the monthly and yearly is taken from the daily summary tables > in the database by appropriate queries (select statemen

Re: [weewx-user] Re: how to provide the csv data source of the charts in StandardReport

If you extend your sql statement a little you can get things like sqlite3 -header -csv weewx.sdb "select inTemp from archive where DateTime > xx;" > out.csv or sqlite3 -header -csv weewx.sdb "select * from archive where DateTime > xxx;" > out.csv or sqlite3 -header -csv weewx.sdb

Re: [weewx-user] Any work receiving a Davis ISS with a SDR?

Today i have received the 915mhz receiver. I downloaded Davissi1000 utility from https://github.com/tridge/DavisSi1000 And added all last patches. I have could install the new Davis Firmware: root@MeteoElche:~/DavisSi1000/Firmware/tools # ./uploader.py --port /dev/ttyUSB0 --resetparams --baudra

[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 da

Re: [weewx-user] Re: how to provide the csv data source of the charts in StandardReport

Hi El 21/03/17 a las 13:22, Andrew Milner escribió: Can you be more precise? The data used to create a plot is the data from the database - can you specify more clearly what you are trying to achieve - a csv of the entire database? a csvfile for specific fields? There are also a couple of exte

[weewx-user] Re: how to provide the csv data source of the charts in StandardReport

Can you be more precise? The data used to create a plot is the data from the database - can you specify more clearly what you are trying to achieve - a csv of the entire database? a csvfile for specific fields? There are also a couple of extensions (see the wiki) which create a csv file as the

[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: > > sinkingsensation.com/win

[weewx-user] how to provide the csv data source of the charts in StandardReport

Hi everybody We're happily using weewx since some time in my institution and it works great, thanks! We use the standard report and the default skin to show data and charts in our website. We would like to provide to our visitors with the data used to create each plot, along with the plot i