You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we use object height/shadow length at a known time to identify a list of potential locations.
If you have a shadow at 2 different times, with angle A and angle B, then that change in angle for these times corresponds to a list of potential locations.
Having a section that would allow for an input like this could increase the potential use cases for the shadow finder.
In other words. Right now the inputs are:
Object height + Shadow length + known time = locations.
I propose adding a new section with the inputs
Shadow Angle 1 + Time 1 + Shadow angle 2 + Time 2 (essentially: Shadow Angle difference + Time difference) = locations
The text was updated successfully, but these errors were encountered:
Also just to be clear @JackCollins91, the focus of the inputs should be on the shadow angle difference. Since obviously if you don't know the location (which you'd be using this for) you're not gonna really know the exact angle relative to f.ex geographic north.
Now we use object height/shadow length at a known time to identify a list of potential locations.
If you have a shadow at 2 different times, with angle A and angle B, then that change in angle for these times corresponds to a list of potential locations.
Having a section that would allow for an input like this could increase the potential use cases for the shadow finder.
In other words. Right now the inputs are:
Object height + Shadow length + known time = locations.
I propose adding a new section with the inputs
Shadow Angle 1 + Time 1 + Shadow angle 2 + Time 2 (essentially: Shadow Angle difference + Time difference) = locations
The text was updated successfully, but these errors were encountered: