The tide prediction function in WD is out by 1 hour (fast) and the increase,decrease,leave as is, function boxes don’t work [in version 10:28k]
For now…as a work around, try this: Shutdown WD. Open the wdisplay.ini file found in windows. Look for an entry string like this: (it’s usually found somewhere in the first 1/3 of wdisplay.ini.)
[Tide]
minute adjust=0
do it=yes
do it upload=yes
adjust=+1
Change adjust=+1…to adjust=0
Then restart WD and open the tideprediction program from WD…and see the results.
I have mine set to adjust=0…and it’s accurate with other tide tables found on the internet.
Many thanks for the “work around” I wonder if the fault will be fixed or not!
so i have an error with the setting/resetting/getting of that hour offset in the ini file…?
Yes…It appears that’s what’s happening. It’s been around for quite awhile. You were so busy trying to iron out the VP 2 problems…and then the memory leak thing. I figured out a work-around to manually reset it, so I decided to wait until things settled down to report the problem. I forgot all about it until Oldun’s report! #-o :oops:
I am puzzled as to why the offset is needed in WD. My setup for WXTide provides tidal data correctly all year round whether I am on Daylight saving or not.
Stuart
i found the bug
setting as zero was applying a 1 hour increase…
a setting of 1 hour was then applying no change…default…
just has things a bit mixedup
(this is via the command switch -htoff
Brian do you also adjust the low tide time via the -ltoff switch as well? I am just interested as to why this is needed since it is possible to set the correct time offsets within WXTide itself and -htoff only does the high tide according to the docs. I think it is easier and you get more accurate tidal predictions by setting up your own usser station with WXTide and just using WD to do the upload for the website. I have now fine tuned this and got my almost identical to the official figures.
Stuart
I have decided to stick with my free “WTIDES” a NZ written program [ www.wtides.com ] and my manual upload.
just checked mine, for the manukau, Onehunga
its up to date, but its an hour to much ahead, becuase of daylight saving, so I have now ticked to reduce by 1 hour
which then makes it an hour too early
so there is something wrong there…
investigating
solution:
i had to tick increase by 1 hour instead
seems a bit backwards, must be how it works, now the time time is OK
Brian I am still puzzled as to why this offset is needed for daylight saving. We change our daylight saving at the end of the month and if you look at my uploaded tide times at http://www.stella-maris.org.uk/tides.shtml you will see that it takes care of the change between the 29th and 30th October already. I am using the latest WXTides version which is 4.2. I did not have to do anything when we went onto daylight saving either.
Stuart