developmentseed / developmentseed/pearl-frontend
Remove OSM features from retraining samples
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 21
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
At the moment when you add the OSM layer, all available features are used for retraining. The user should be able to remove features they don't want to include as part of the process.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the OSM layer and retraining flow in the frontend, then identify where all available features are collected for retraining. Done means a user can remove unwanted OSM features before the retraining process uses the remaining selection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100