Not enough table entries about aptimezones HOT 3 CLOSED

Please, provide me with your lat/lon (or closest ones with wrong timezone result, to not show your real position:)). I'll check it asap.
Anyway, did your try "CLLocation" or "CLPlacemark" way?

18 ãðóä. 2013 î 22:00 kirk-kerekes [email protected] íàïèñàâ(ëà):

Pertaining to use with lat-long:

Doesn't produce correct results for my home location in the US (CST, Tulsa, OK) because "closest" timezone location (Vincennes, Indiana) is in another timezone (EST).

Needs some way to weight the results for latitude offset, or more entries in the table to minimize this issue. Timezones aren't tidy, but they are mostly a function of longitude.

—
Reply to this email directly or view it on GitHub.

from aptimezones.

Thank you for rapid response!

Tulsa: 36.1314° N, 95.9372° W

Tried both methods, but as CLPlacemark just narrows by country code, was not surprised to get same results.

Vincennes is about 800km NE of Tulsa.

Kirk Kerekes
(iPhone)

On Dec 18, 2013, at 2:15 PM, Serg Krivoblotsky [email protected] wrote:

Please, provide me with your lat/lon (or closest ones with wrong timezone result, to not show your real position:)). I'll check it asap.
Anyway, did your try "CLLocation" or "CLPlacemark" way?

18 ãðóä. 2013 î 22:00 kirk-kerekes [email protected] íàïèñàâ(ëà):

Pertaining to use with lat-long:

Doesn't produce correct results for my home location in the US (CST, Tulsa, OK) because "closest" timezone location (Vincennes, Indiana) is in another timezone (EST).

Needs some way to weight the results for latitude offset, or more entries in the table to minimize this issue. Timezones aren't tidy, but they are mostly a function of longitude.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

from aptimezones.

Thanks for the feedback, I'll keep common issue (#2) open.

from aptimezones.