Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Discussion and questions about Cumulus weather station software version 1. This section is the main place to get help with Cumulus 1 software developed by Steve Loft that ceased development in November 2014.
garytx wrote:The VP doesn't send signal strength, but does transmit the reception percentage (with perfect reception being 100% and declining from there.)
Yes that what I mean, tks. But I,m sure is something else it transmits - I will have to check when I am home
Some of the features in Easyweather could be quite handy in Cumulus 2. Such as the format for viewing data, even though it stretches across 2 screens, and the ability to export that data in different formats.
When displaying graphs, it would be handy to be able to set the time and value parameters.
Suggestion from a non-British user: please support decimal commas & periods for thousands separators!
Cumulus works beautifully if I set my system to British standards - but crashes when I use my normal Danish standard.
Ib http://www.ibtest.dk/cumulus/index.htm
dane wrote:Suggestion from a non-British user: please support decimal commas & periods for thousands separators
Yes, it's a pain, isn't it? I use commas to separate the values in the data files, which is one problem, and I use a mixture of routines for converting from floating point numbers to strings (and back), some of which always use decimal points and some use the regional settings. So it all goes horribly wrong with decimal commas.
Cumulus 2 uses an SQLite database to store its data, and obeys regional settings, so the problem will go away if I ever finish it.
Super-T wrote:Some of the features in Easyweather could be quite handy in Cumulus 2. Such as the format for viewing data, even though it stretches across 2 screens, and the ability to export that data in different formats.
This would all be included as part of saving the data in a database.
When displaying graphs, it would be handy to be able to set the time and value parameters.
The Select-a-graph facility allows this, or is that not what you meant?
I guess the Graphs auto size for the Y axis but setting the X axis could be handy. If you can already set it then I haven't noticed it
All's been going well with this latest version. http://www.wunderground.com/weatherstat ... IAUCKLAN33
Separate translation files so that it easily can be translated. Could I suggest using JRC Editor as a translation tool.
I have been doing some translations with this tool and it's really good (and free )
The most of these suggestions are really good, especially the part with PHP and mySQL. This would ease the work with merging it with a portal system (CMS).
Back to the JRC Editor - I haven't got the downloadable version to work yet, but I got a modified version that works if anybody is interested.
steve wrote:
I looked up JRC Editor, but isn't it just for Java apps?
Steve
I'm not sure, I have used it to translate a few java apps, but I would think it could work for other apps as well.
The oonly thing it does is to save translations with ext. ".properties"
So I don't see why php could not be directed to .properties lang files instead of .php lang files. or even just rename the files it produces into .php
I use carter lake templates so I would love to see support for the tags/txt files used by that, of course to remain apart from that other software they could be called something different
One of the issues that normally arises is that the program itself starts to get unwieldy. This then starts to cause system problems when more and more features are added causing bloat.
One way of dealing with that is to break the system into main components like...
1) Data acquisition module. This module simply obtains data from the weather station and stores it in a simple ISO data formatted raw format. The format of the data should remain the same regardless of user desired format so that it is easy to import and use in other external applications. The module itself, does little else but obtain the data and store it.
2) Database module. For those that want to have their data stored in some sort of database, this module reads the raw data and stores the information in the format the user has chosen in their setup.
3) Display and Report module. Displays the current status of the system, using the users desired formats. Provides reports of what has been collected as needed in the formats the user has setup.
4) Export Module. This module provides for export of data to various different services, websites etc... XML format is okay but a bit verbose. If you break up the data into different files based on how often the data is updated you can minimize the amount of data that is sent though. Each system like CWOP, Wunderground etc... created as a simple plugin, makes it easy to add new exports wtih minimal programming.
This type of modularity allows the system to run in a minimal configuration for those that simply want to collect the data and provide the output on their external website (using PHP or other dynamic web generation.
