This repository has been archived by the owner on Jan 25, 2021. It is now read-only.
forked from weewx/weewx
-
Notifications
You must be signed in to change notification settings - Fork 0
/
NEW_FEATURES.txt
84 lines (56 loc) · 2.94 KB
/
NEW_FEATURES.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
Possible NEW FEATURES
Eliminate the need for Ftp/skin.conf and Rsync/skin.conf. More generally,
do not require a skin.conf file for each report. In the case of Ftp and Rsync
one can simply put the generator_list in weewx.conf as part of the report
definition. A report with no skin.conf should run with sane defaults.
Templates should also be "drop in." If they appear in the directory, they
get used.
Minor cleanup to the Standard skin:
- improve layout, possibly like http://www.kanonbra.com/veret/
- punt the buttons for week/month/year, use regular html links instead
- include a table instead of duplicating html code for stats
- make the info section easier to grok with a structured layout, perhaps
similar to weather display or cumulus default templates
Offer tags to support JSON. In particular, vectors. A tag like
$day.outTemp.vector would offer a vector of temperatures for the day.
Aggregation would be nice.
Allow new derived types to be created by the user. Right now, things like
heating and cooling degree days are hardwired in, but it ought to be possible
to add things like that modularly.
The Davis console could intercept new archive record events and add
rxcheckpercent and rain to software generated records.
Consider breaking the rule that reporting can only be done through the
databases and, instead, offer up the last record when the reporting thread
starts.
A QC "Spike" detector.
Harden up the MySQL database connection.
Allow reporting services to be fired off at something other than every
archive period. In particular, FTP.
Offer "cumulative" as an aggregation type.
Allow rain-to-date to be added to a partial rainyear.
Current ET for the VP2 should show the value it emitted at the top of the hour.
Fix scaling for aggregate interval of a week, so it starts on a Sunday.
More dynamic access to the database. Check out
Werkzeug. http://werkzeug.pocoo.org
Dynamic web updates, using AJAX, or Meteor.
Port to Windows.
Allow variable y-axis labelling. Right now it's hardwired to every other major
tick mark.
Add log_success/log_failure parameters for subsystems other than just restx.
Graphing system feature requests:
- user suggestions are here:
https://groups.google.com/forum/#!topic/weewx-user/0hGKjHwD3J0
- image background for plots - useful when overlaying a wind rose on a
satellite image of the earth, for example.
- wind direction plot over time (e.g., as in weather display)
http://jaxweather.net/WeatherImages/WD/dirplot.gif
- multiple y scales
- "current wind dial"
http://www.hasslosa.se/weather/wd/wx3.php
- other wind rose variants
http://en.wikipedia.org/wiki/Wind_rose
http://www.therodericks.id.au/saratoga/wxtrends.php
- add ability to specify start date as well as time length on plots
- compound graphs such as forecast graphs from yr.no
- wind summary graphs such as those from windfinder
http://www.windfinder.com/windstats/windstatistic_raa.htm