AnnualDataSummary - Revision history

Sfws: spelling

2022-01-09T10:02:01Z

spelling

← Older revision		Revision as of 10:02, 9 January 2022
Line 12:		Line 12:


	'''An updated article, that ~~supercedes~~ this one is called [[Daily_Summary]]'''		'''An updated article, that supersedes this one is called [[Daily_Summary]]'''

	'Annual Data Summary' is a small tool to read the [[dayfile.txt]] produced by Cumulus and summarise this in a table, arranged like a calendar, showing a full years worth of a selected criterion such as maximum daily temperature.		'Annual Data Summary' is a small tool to read the [[dayfile.txt]] produced by Cumulus and summarise this in a table, arranged like a calendar, showing a full years worth of a selected criterion such as maximum daily temperature.

SaratogaWX: Text replacement - "cumuluswiki.wxforum.net" to "cumuluswiki.org"

2020-04-21T19:48:34Z

Text replacement - "cumuluswiki.wxforum.net" to "cumuluswiki.org"

← Older revision		Revision as of 19:48, 21 April 2020
Line 60:		Line 60:

	*A working example was [http://silveracorn.co.nz/weather/datasummary.php here] and also [http://www.fordingbridgeweather.co.uk/datasummary.php here]		*A working example was [http://silveracorn.co.nz/weather/datasummary.php here] and also [http://www.fordingbridgeweather.co.uk/datasummary.php here]
	*Download the following file...[https://cumuluswiki.~~wxforum.net~~/files/AnnualDataSummary_12.zip AnnualDataSummary_12.zip], the zip contains 3 files:		*Download the following file...[https://cumuluswiki.org/files/AnnualDataSummary_12.zip AnnualDataSummary_12.zip], the zip contains 3 files:
	*#'''readDayfile.php''' - script for reading the dayfile.txt and for creating the table structure that displays selected statistics in a calendar style		*#'''readDayfile.php''' - script for reading the dayfile.txt and for creating the table structure that displays selected statistics in a calendar style
	*#'''datasummary.php''' - example 'carrier' web page, this one uses the Saratoga template system, so also requires 2 more scripts (not provided) ''Settings.php'' and ''common.php''. You can use your own page instead of this file.		*#'''datasummary.php''' - example 'carrier' web page, this one uses the Saratoga template system, so also requires 2 more scripts (not provided) ''Settings.php'' and ''common.php''. You can use your own page instead of this file.
Line 70:		Line 70:
	= Original 1.1 Fileset and instructions:- =		= Original 1.1 Fileset and instructions:- =

	*download the following file...[https://cumuluswiki.~~wxforum.net~~/files/AnnualDataSummary.zip AnnualDataSummary.zip]		*download the following file...[https://cumuluswiki.org/files/AnnualDataSummary.zip AnnualDataSummary.zip]
	*Unzip the contents (five files will be extracted)		*Unzip the contents (five files will be extracted)
	*Edit the file 'readDayfile' file in a a good text editor (for example, [http://notepad-plus-plus.org/ notepad++]). Edit the .js version or the .php depending on your choice		*Edit the file 'readDayfile' file in a a good text editor (for example, [http://notepad-plus-plus.org/ notepad++]). Edit the .js version or the .php depending on your choice

SaratogaWX: Text replacement - "http://sandaysoft.com/forum/" to "https://cumulus.hosiene.co.uk/"

2018-11-02T15:57:00Z

Text replacement - "http://sandaysoft.com/forum/" to "https://cumulus.hosiene.co.uk/"

← Older revision		Revision as of 15:57, 2 November 2018
Line 84:		Line 84:
	Along the top will be a menu of the six data sets available and on the top left of the table is the year currently being shown. Change either the year, or click one of the top buttons to change the dataset. Depending on the speed of your internet connection, and your browser, the data may take a few seconds to be processed.		Along the top will be a menu of the six data sets available and on the top left of the table is the year currently being shown. Change either the year, or click one of the top buttons to change the dataset. Depending on the speed of your internet connection, and your browser, the data may take a few seconds to be processed.

	If you select the pure Javascript solution available here, it means the page viewer's browser is doing all the work. The complete dayfile.txt is loaded each time you select a dataset, and your PC then filters and processes it. An [~~http~~://~~sandaysoft~~.~~com/forum~~/viewtopic.php?f=18&t=8690 alternative Javascript/jQuery solution] that only reads the dayfile.txt once, however many times you choose a different data set or a different year is in the 3rd party tools forum. That alternative is thus considerably faster, especially with large dayfile.txt files.		If you select the pure Javascript solution available here, it means the page viewer's browser is doing all the work. The complete dayfile.txt is loaded each time you select a dataset, and your PC then filters and processes it. An [https://cumulus.hosiene.co.uk/viewtopic.php?f=18&t=8690 alternative Javascript/jQuery solution] that only reads the dayfile.txt once, however many times you choose a different data set or a different year is in the 3rd party tools forum. That alternative is thus considerably faster, especially with large dayfile.txt files.

	This is in contrast to a PHP solution also available here, where the source server does all the work and only sends the results to the viewer's browser.		This is in contrast to a PHP solution also available here, where the source server does all the work and only sends the results to the viewer's browser.

SaratogaWX: Text replacement - "http://wiki.sandaysoft.com/" to "https://cumuluswiki.wxforum.net/"

2018-11-02T15:05:48Z

Text replacement - "http://wiki.sandaysoft.com/" to "https://cumuluswiki.wxforum.net/"

← Older revision		Revision as of 15:05, 2 November 2018
Line 60:		Line 60:

	*A working example was [http://silveracorn.co.nz/weather/datasummary.php here] and also [http://www.fordingbridgeweather.co.uk/datasummary.php here]		*A working example was [http://silveracorn.co.nz/weather/datasummary.php here] and also [http://www.fordingbridgeweather.co.uk/datasummary.php here]
	*Download the following file...[~~http~~://~~wiki~~.~~sandaysoft~~.~~com~~/files/AnnualDataSummary_12.zip AnnualDataSummary_12.zip], the zip contains 3 files:		*Download the following file...[https://cumuluswiki.wxforum.net/files/AnnualDataSummary_12.zip AnnualDataSummary_12.zip], the zip contains 3 files:
	*#'''readDayfile.php''' - script for reading the dayfile.txt and for creating the table structure that displays selected statistics in a calendar style		*#'''readDayfile.php''' - script for reading the dayfile.txt and for creating the table structure that displays selected statistics in a calendar style
	*#'''datasummary.php''' - example 'carrier' web page, this one uses the Saratoga template system, so also requires 2 more scripts (not provided) ''Settings.php'' and ''common.php''. You can use your own page instead of this file.		*#'''datasummary.php''' - example 'carrier' web page, this one uses the Saratoga template system, so also requires 2 more scripts (not provided) ''Settings.php'' and ''common.php''. You can use your own page instead of this file.
Line 70:		Line 70:
	= Original 1.1 Fileset and instructions:- =		= Original 1.1 Fileset and instructions:- =

	*download the following file...[~~http~~://~~wiki~~.~~sandaysoft~~.~~com~~/files/AnnualDataSummary.zip AnnualDataSummary.zip]		*download the following file...[https://cumuluswiki.wxforum.net/files/AnnualDataSummary.zip AnnualDataSummary.zip]
	*Unzip the contents (five files will be extracted)		*Unzip the contents (five files will be extracted)
	*Edit the file 'readDayfile' file in a a good text editor (for example, [http://notepad-plus-plus.org/ notepad++]). Edit the .js version or the .php depending on your choice		*Edit the file 'readDayfile' file in a a good text editor (for example, [http://notepad-plus-plus.org/ notepad++]). Edit the .js version or the .php depending on your choice

Sfws: Small tweaks to the version as at 17 Dec 2012

2018-04-13T21:26:34Z

Small tweaks to the version as at 17 Dec 2012

Show changes

Sfws: Undo revision 2207 by Sfws (talk)

2018-04-13T21:02:31Z

Undo revision 2207 by Sfws (talk)

Show changes

Sfws at 21:01, 13 April 2018

2018-04-13T21:01:30Z

← Older revision		Revision as of 21:01, 13 April 2018
Line 134:		Line 134:
	Example of a row,....		Example of a row,....
	<pre>['maxtemp','Max Temp','Maximum Temperature',true]</pre>		<pre>['maxtemp','Max Temp','Maximum Temperature',true]</pre>
	*The first element, in this case 'maxtemp' -- is a system variable to identify the data set, used for the URL parameter option~~, used for the ''Switch'' coding (so any chnage here needs to be reflected there)~~, and tested elsewhere in the code (in the Rainfall and Windgust data sets a particular style is applied to any zero values, so their system variables should not be changed just in this list).		*The first element, in this case 'maxtemp' -- is a system variable to identify the data set, used for the URL parameter option, and tested elsewhere in the code (in the Rainfall and Windgust data sets a particular style is applied to any zero values, so their system variables should not be changed just in this list).

	However, if you add a new dataset, then your new first element should be a unique identifier.		However, if you add a new dataset, then your new first element should be a unique identifier.
Line 143:		Line 143:
	*Finally, 'true' will display this button at the top; 'false' will hide it. Therefore, if you do not wish to allow users to jump to the 'Rainfall data set' change the 'true' to 'false' in the 'rainfall' element of the variable. (true/false MUST be lowercase)		*Finally, 'true' will display this button at the top; 'false' will hide it. Therefore, if you do not wish to allow users to jump to the 'Rainfall data set' change the 'true' to 'false' in the 'rainfall' element of the variable. (true/false MUST be lowercase)

	(NOTE: [[User:Sfws\|Sfws]] 12:22, 31 December 2012 (UTC)
	The ''switch'' part of the coding identifies the columns in dayfile.txt for the values to be displayed. If you wish to add new data sets then see the alternative JavaScript version in the forum for more explanation about this coding.)
	<br>		<br>

Sfws at 21:00, 13 April 2018

2018-04-13T21:00:42Z

← Older revision		Revision as of 21:00, 13 April 2018
Line 134:		Line 134:
	Example of a row,....		Example of a row,....
	<pre>['maxtemp','Max Temp','Maximum Temperature',true]</pre>		<pre>['maxtemp','Max Temp','Maximum Temperature',true]</pre>
	*The first element, in this case 'maxtemp' -- is a system variable to identify the data set, used for the URL parameter option, used by the ''Switch'' coding (so any ~~change~~ here needs to be reflected there), and ~~also~~ tested elsewhere in the code (in the Rainfall and Windgust data sets a particular style is applied to ~~their~~ zero values).		*The first element, in this case 'maxtemp' -- is a system variable to identify the data set, used for the URL parameter option, used for the ''Switch'' coding (so any chnage here needs to be reflected there), and tested elsewhere in the code (in the Rainfall and Windgust data sets a particular style is applied to any zero values, so their system variables should not be changed just in this list).

	However, if you add a new dataset, then your new first element should be a unique identifier.		However, if you add a new dataset, then your new first element should be a unique identifier.

Sfws at 21:00, 13 April 2018

2018-04-13T21:00:02Z

← Older revision		Revision as of 21:00, 13 April 2018
Line 136:		Line 136:
	*The first element, in this case 'maxtemp' -- is a system variable to identify the data set, used for the URL parameter option, used by the ''Switch'' coding (so any change here needs to be reflected there), and also tested elsewhere in the code (in the Rainfall and Windgust data sets a particular style is applied to their zero values).		*The first element, in this case 'maxtemp' -- is a system variable to identify the data set, used for the URL parameter option, used by the ''Switch'' coding (so any change here needs to be reflected there), and also tested elsewhere in the code (in the Rainfall and Windgust data sets a particular style is applied to their zero values).

	However, if you add a new ~~data set~~, then your new first element should be a unique identifier.		However, if you add a new dataset, then your new first element should be a unique identifier.
	*Second, '''Max Temp''' is the text to be displayed in the ''button'' at the top of the table. You may change this to your own language		*Second, '''Max Temp''' is the text to be displayed in the ''button'' at the top of the table. You may change this to your own language

	If you add a new ~~data set~~, remember to consider how many buttons can be fitted across the top of the table, you may wish to split into multiple rows.		If you add a new dataset, remember to consider how many buttons can be fitted across the top of the table, you may wish to split into multiple rows.
	*Third, '''Maximum Temperature''' is the text shown at the top of the table to ''describe the current data set''; again you may change this		*Third, '''Maximum Temperature''' is the text shown at the top of the table to ''describe the current data set''; again you may change this
	*Finally, 'true' will display this button at the top; 'false' will hide it. Therefore, if you do not wish to allow users to jump to the 'Rainfall data set' change the 'true' to 'false' in the 'rainfall' element of the variable. (true/false MUST be lowercase)		*Finally, 'true' will display this button at the top; 'false' will hide it. Therefore, if you do not wish to allow users to jump to the 'Rainfall data set' change the 'true' to 'false' in the 'rainfall' element of the variable. (true/false MUST be lowercase)

Sfws at 20:59, 13 April 2018

2018-04-13T20:59:11Z

← Older revision		Revision as of 20:59, 13 April 2018
Line 185:		Line 185:
	*Version 1.1 has been tested and runs on IE 7, IE 8, IE 9, FireFox 3 to 14, Chrome/Dragon/SRWare Iron, and Safari -- running on the non IE browsers for both Windows and the Mac.		*Version 1.1 has been tested and runs on IE 7, IE 8, IE 9, FireFox 3 to 14, Chrome/Dragon/SRWare Iron, and Safari -- running on the non IE browsers for both Windows and the Mac.
	*IE7 is notoriously slow for Javascript processing so there will be a longer delay as you change the data set (a few more seconds in some cases)		*IE7 is notoriously slow for Javascript processing so there will be a longer delay as you change the data set (a few more seconds in some cases)
			*The original version defaults to current local calendar year, but the dayfile.txt only contains records up to the last rollover time (using the timezone local to the weather station). So at new year there can be a period of up to 2 days when the default year is ''not'' available to be displayed (depending on timezone differences and rollover time).
	*Non-standard attributes are generated by this routine that will not pass validation against standards.		*Non-standard attributes are generated by this routine that will not pass validation against standards.

	*Version 1.0 and 1.1 default to showing a table for viewer's local current calendar year. Remember the dayfile.txt (even if updated each day) only contains records up to the day ending at the last rollover time using the timezone local to the weather station. Timezone differences when combined with rollover time variations can lead to a period of 2 days discrepancy. At New Year a blank table will be displayed during this period by default. For example, 30 or 31 (depending on whether rollover has occured) in December of the last year could be the latest available for a site in USA whilst the original version of the code is showing a blank table of the next year during early morning on 2 January in Austrailia. Even when station and viewer are in same timezone, there will be a blank table until the first rollover on 2 January.

	= Version Control =		= Version Control =