StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19621517
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-27T18:09:30.790
FavoriteCount
0
LastActivityDate
2013-10-27T18:09:30.790
LastEditDate
LastEditorUserId
0
OwnerUserId
2905768
ParentId
19437569
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Your code is hard to follow, but I'll try to get you some tips: <ul> <li>There are existing libraries out there that compute solar angle/azimuth and sunrise/sunset for a given date. Use google as a help, here's some relevant resources: <a href="http://www.esrl.noaa.gov/gmd/grad/solcalc/" rel="nofollow">http://www.esrl.noaa.gov/gmd/grad/solcalc/</a> If you don't find any useful source code, I could post some.</li> <li>Do not use double to calculate with dates and times. That's confusing and results in errors. Use a data type that is intended to store dates. </li> <li>For your code, you say that the time is running to fast. Since referenceTime and day in the last line are constant (at least for half a day), the error must be in proportion. I think you're mixing to many cases there. The interpolation should go from the start of the range to the end, so in the case proportion = (distanceAlong - previousDayEvening) / (closestDayMorning - previousDayEvening); referenceTime = previousDay + day * 3 / 4;</li> </ul> proportion should run from (previousDay + day * 3 / 4) to (closestDay + day * 3 / 4), or, described differently, from the dusk to dawn of closestDay. But it's completely unclear how this interpolation should work. Try to draw a diagram of the different cases (I believe there should only be two, one for day and one for night) and the corresponding interpolation. But: What are you trying to achieve after all? The resulting time is just a forward running time, it is actually independent of latitude or longitude or time of day. So to make the time run, you don't need to know where the sun is. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhere is the bug in these length-of-daylight/night approximations?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPMF
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhere is the bug in these length-of-daylight/night approximations?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.