October 21, 2008 15:27
Hi August: Thanks for the updates. I'd noticed the incorrect implementation of daylight saving times in Australia, and was going to ask.
Now, if I go to the state of Queensland (where they don't have DST, or Western Australia, where it starts this Sunday (eastern states of Australia began beginning of October -- don't ask why, long story: times here http://www.australia.gov.au/Time), I presume my iPhone will recognise the local time, and will AyeTides also adjust accordingly?
Another thing I've noticed (and sorry if this seems over-picky) is that the times and heights in AyeTides can differ by up to 15 minutes, and by up to 150 mm from the "official" tide times/heights.
Currently for us this doesn't matter, but there's certain places in Queensland (which has enormous tides) where the "window" to get through a few spots can be only a few minutes, and having the correct tide times is critical.
I noticed the same disparity on TideTool, which was my previous favourite tides system on my Palm Treo. Are you using different data or algorithms to what are used in Australia?
Here's a couple of sites where you can compare differences:
http://www.seabreeze.com.au/graphs/nsw.asp
http://www.bom.gov.au/oceanography/tides/
The BOM (Bureau of Meteorology) site would be the most accurate, and I would presume most other sites derive their data from here.
This is today's tide times and heights from the BOM site for Sydney (but note this site doesn't add 1 hour for DST, but I've done that in the brackets); also variations don't seem that much today:
Wed 22
Time Ht
0237 (0337) 1.16
0805 (0905) 0.61
1436 (1536) 1.57
2135 (2235) 0.38
AyeTides
Wed 22
Time Ht
0338 1.10
0907 0.59
1537 1.52
2238 0.34
I just checked the times and heights for Gladstone (Queensland), where the tides are much bigger, and the differences are considerably more.
Please don't regard this as a complaint (if I were sailing in Queensland or other critical waters, I'd be foolish to rely on anything but official government tide times and heights); it's more in the nature of an observation.
I'd be interested to know your response.
Thanks again for a great product.
Now, if I go to the state of Queensland (where they don't have DST, or Western Australia, where it starts this Sunday (eastern states of Australia began beginning of October -- don't ask why, long story: times here http://www.australia.gov.au/Time), I presume my iPhone will recognise the local time, and will AyeTides also adjust accordingly?
Another thing I've noticed (and sorry if this seems over-picky) is that the times and heights in AyeTides can differ by up to 15 minutes, and by up to 150 mm from the "official" tide times/heights.
Currently for us this doesn't matter, but there's certain places in Queensland (which has enormous tides) where the "window" to get through a few spots can be only a few minutes, and having the correct tide times is critical.
I noticed the same disparity on TideTool, which was my previous favourite tides system on my Palm Treo. Are you using different data or algorithms to what are used in Australia?
Here's a couple of sites where you can compare differences:
http://www.seabreeze.com.au/graphs/nsw.asp
http://www.bom.gov.au/oceanography/tides/
The BOM (Bureau of Meteorology) site would be the most accurate, and I would presume most other sites derive their data from here.
This is today's tide times and heights from the BOM site for Sydney (but note this site doesn't add 1 hour for DST, but I've done that in the brackets); also variations don't seem that much today:
Wed 22
Time Ht
0237 (0337) 1.16
0805 (0905) 0.61
1436 (1536) 1.57
2135 (2235) 0.38
AyeTides
Wed 22
Time Ht
0338 1.10
0907 0.59
1537 1.52
2238 0.34
I just checked the times and heights for Gladstone (Queensland), where the tides are much bigger, and the differences are considerably more.
Please don't regard this as a complaint (if I were sailing in Queensland or other critical waters, I'd be foolish to rely on anything but official government tide times and heights); it's more in the nature of an observation.
I'd be interested to know your response.
Thanks again for a great product.