kjaymiller / kjaymiller/fire-map
Figure out Map Data Structure
Open
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
There are 280 Countries that we need to pull map data from whenever it's requested.
We're better off only pulling the popular maps all the time and then the less popular maps on demand.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing how the Python project obtains map data from the NASA FIRMS API, then define what data structure and retrieval behavior support always-available popular maps and on-demand less-popular maps; done means that strategy is specified clearly enough to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100