record-tags shows wrong values

[weatherc]

Hi,

Struggling with a problem, i have table where its meant to show alltime monthly highs and lows using the customtags like
$recordhightempjan = "%recordhightempjan%";
$recordlowtempjan = "%recordlowtempjan%";
output from those two are:
$recordhightempjan = "-0.9";
$recordlowtempjan = "-23.1";
But ex. January shows only data from this year, has done it so since beginning of the year...And when month changed started February-tags to show only data from today (01.02)
The averagetag works fine and seems correct.

Table in action here: http://www.nordicweather.net/index.php?sivu=12&lang=en (second table, that small one)
Using WD .37P b16

Ideas?

Henkka

[weatherc]

Bump...

For me starts the recordtags showing this years records after the month has started, not the alltimercords...

henkka

[TrevP]

This is exactly the same problem that I raised a couple of years ago (using the equivelent xml  %tags) and re raised it a couple of days ago as it was never rectified

http://www.weather-watch.com/smf/index.php/topic,44497.0.html

TrevP

[Weather Display]

I am not clear on what the exact problem is

I am thinking that what you are trying to say that is come Feb, %recordhightempjan% gets reset
yes/no?

[TrevP]

I am not clear on what the exact problem is

I am thinking that what you are trying to say that is come Feb, %recordhightempjan% gets reset
yes/no?

The problem is:  The highest/lowest values for any month of the year,  replace the exisitng all time high/all time low for the month even though the month value is not the all time high/low.  (this happened each month since i first reported it back in 2008, in the thread I have referred to)

TrevP

[Weather Display]

I have replied to your other thread

[weatherc]

I am thinking that what you are trying to say that is come Feb, %recordhightempjan% gets reset
yes/no?

What i try say is, when it come January, when i saw it for first time, January's max/mins started showing this years max/min's, not the alltime-values. Same thing now with February, in January they seemed ok, but when February beginned, they started to show this months values. Now in February January's values are still from this year, not alltime, with theese tags:

$recordhightempjan = "%recordhightempjan%";
$recordlowtempjan = "%recordlowtempjan%";

EDIT: Using the newest zip from the another thread don't fixed the %recordhightempjan% if they are updated continous. Runned 2 updates (5min rate) and still the wrong values.

Henkka

[TrevP]

What i try say is, when it come January, when i saw it for first time, January's max/mins started showing this years max/min's, not the alltime-values. Same thing now with February, in January they seemed ok, but when February beginned, they started to show this months values. Now in February January's values are still from this year, not alltime, with theese tags:

$recordhightempjan = "%recordhightempjan%";
$recordlowtempjan = "%recordlowtempjan%";

EDIT: Using the newest zip from the another thread don't fixed the %recordhightempjan% if they are updated continous. Runned 2 updates (5min rate) and still the wrong values.

Henkka

Henkaa,

I think you will have to amend the values for Jan and Feb that are stored in your wdisplay.ini file to get the right extreme values back....

Stored here
[Record monthly high temp]
jan year=2010
jan=88
jan day=18
feb year=2010
feb=98
feb day=5
.........
[Record monthly low temp]
jan year=2010
jan=-44
jan day=4
feb year=2010
feb=-17
feb day=1

...... and if Brian's fix works then these values should only be overwritten if/when all time extremes are broken, rather than this years monthly extremes.

TrevP