You should be happy with general logic and PHP.
You should be uploading your dayfile.txt to 'the web' on a regular basis.
You should have a good understanding of your own data and spot any anomalies or glitches.
You should be able to follow comments and have little (If any) instruction ! - Cumulus, saratogaWX and WeatherByYou examples in "How To" file.

It can be used as a stand-alone or dropped into a suitable site template.
It can 'read' saratogaWX templates for language and $SITE Units Of Measure decisions.
It can 'read' Weather By You templates for language decisions.

5th March 2020 - v7.1.3

beteljuice_7_1_3.zip

Main file - betel_readDayfile - bug fix in changes to Seasonal stuff

Distribution Contains:

Three 'default' holders which use
Three different css files. (plus meteo template css)
betel_readDayfile.php

Edit: Dec 2019 ...
There are many things that can be 'tweaked', refer to 'How To' and comments in script.
A further suggestion from BCJKiwi for the SANITIZE list.

Just a thought about heatdays and cooldays.

I added these to the SANITIZE list quite a long time ago.
Why?
Well it seems to me that if the value on any one day is zero, then by definition it is NOT a heating day NOR a cooling day.
This change makes the average values make more sense to me.

You do not have the required permissions to view the files attached to this post.

Last edited by beteljuice on Fri 06 Mar 2020 5:29 am, edited 71 times in total.

I have broken the layout when I add my .css (which has some same names in it) and reduce width in this q&d include page here.
I had to add a font size to '#table_container table td,table th' as data table font remained large.

Functionality is spot on, data totals/averages are correct (compare with my page from db) - I would just need to sort out styling.
I only removed 'UV' and altered menu_split number.