Extras: time at geographic point

[zverok]

Interface:

# minimal
Reality.city('Buenos-Aires').current_time # => 2016-01-11 06:38:51 -0300

# more:
Reality.city('Buenos-Aires').time(2015, 1, 11, 6, 38) # => 2016-01-11 06:38:00 -0300
Reality.city('Buenos-Aires').time('2015-01-11 06:38')  # => 2016-01-11 06:38:00 -0300

# or, better (?) alternative:
Reality.city('Buenos-Aires').time.zone
Reality.city('Buenos-Aires').time.now
Reality.city('Buenos-Aires').time.local(2015, 1, 11, 6, 38)
Reality.city('Buenos-Aires').time.parse('2015-01-11 06:38')

Implementation:

• case1: Entity has explicit time_zone field: use it;
• case2: Entity has geographic coords, or place name: guess timezone (some methods -- maybe this gem should be ok, at least for the beginning)

[smostovoy]

should wait for #3 and #17 ?

[zverok]

@smostovoy No, I don't think so. About #3 (which, in any case, I'll plan to do today/tomorrow) -- there is Country already, heaving time_zone field. About #17 -- it seems like earlier (and not well-thought) version of current ticket, let's ignore it for now.

[zverok]

NB: some (very rough) city data added.

[zverok]

Want something be done, do it yourself :( https://github.com/zverok/wheretz

[smostovoy]

ok, will change to use it)

[zverok]

Fixed with coord.timezone and TZOffset class