bellingcat / bellingcat/ShadowFinder
Shadowfinder 2.0
- Dominant language
- Python
- Stars
- 604
- Forks
- 53
- Avg merge
- 3m
- Merged PRs (30d)
- 3
Description
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 length A and length B, then the proportional change from A to B (or B to A) for that specific change from time A to time B corresponds to a specific list of potential locations. The general theory is the same, just the inputs are different.
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 length 1 + Time 1 + Shadow length 2 + Time 2 (essentially: Proportional change in Length + Time difference) = locations
Contributor guide
Research direction
Start by locating the existing object-height, shadow-length, and known-time input flow in the Python notebook or command-line entry point. Trace how those inputs produce potential locations, then determine where a two-shadow-length, two-time input section would fit. Done means the new four-input flow returns potential locations using the proportional length change and time difference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100