Databases
StackOverflow2013
Postsdbo
POPython Ephem / Datetime calculation
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPython Ephem / Datetime calculation
    primarykey
    data
    text
    <p>the output should process the first date as "day" and second as "night". I've been playing with this for a few hours now and can't figure out what I'm doing wrong. Any ideas?</p> <p><strong>Edit</strong> I assume that the problem is due to my date comparison implementation </p> <p><strong>Output:</strong></p> <pre><code>$ python time_of_day.py * should be day: event date: 2010/4/6 16:00:59 prev rising: 2010/4/6 09:24:24 prev setting: 2010/4/5 23:33:03 next rise: 2010/4/7 09:22:27 next set: 2010/4/6 23:34:27 day * should be night: event date: 2010/4/6 00:01:00 prev rising: 2010/4/5 09:26:22 prev setting: 2010/4/5 23:33:03 next rise: 2010/4/6 09:24:24 next set: 2010/4/6 23:34:27 day </code></pre> <p><strong>time_of_day.py</strong></p> <pre><code>import datetime import ephem # install from http://pypi.python.org/pypi/pyephem/ #event_time is just a date time corresponding to an sql timestamp def type_of_light(latitude, longitude, event_time, utc_time, horizon): o = ephem.Observer() o.lat, o.long, o.date, o.horizon = latitude, longitude, event_time, horizon print "event date ", o.date print "prev rising: ", o.previous_rising(ephem.Sun()) print "prev setting: ", o.previous_setting(ephem.Sun()) print "next rise: ", o.next_rising(ephem.Sun()) print "next set: ", o.next_setting(ephem.Sun()) if o.previous_rising(ephem.Sun()) &lt;= o.date &lt;= o.next_setting(ephem.Sun()): return "day" elif o.previous_setting(ephem.Sun()) &lt;= o.date &lt;= o.next_rising(ephem.Sun()): return "night" else: return "error" print "should be day: ", type_of_light('45.959','-66.6405','2010/4/6 16:01','-4', '-6') print "should be night: ", type_of_light('45.959','-66.6405','2010/4/6 00:01','-4', '-6') </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmjv
    1. USdassouki
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPython Ephem / Datetime calculation
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPython Ephem / Datetime calculation
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPython Ephem / Datetime calculation
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAren't you passing the same values to both "should be day" and "should be night" ?
      singulars
      1. POPython Ephem / Datetime calculation
      1. USmiara
    2. CO@miara I fixed that ...
      singulars
      1. POPython Ephem / Datetime calculation
      1. USdassouki
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload