Add search to maps
- Dominant language
- TypeScript
- Stars
- 38
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
### Description
Adding search to maps for both collection and edit experiences.
The big decision to make is what service(s) to support and how to pass the API key needed.
Service options:
* [MapTiler](https://docs.maptiler.com/openlayers/examples/geocoding-control/)
* [Google](https://developers.google.com/maps/documentation/geocoding/overview)
* [Mapbox](https://docs.mapbox.com/api/search/geocoding/)
---
### Checklist
- **Does it need UI/UX design?**
- [X] Yes. Describe the UI/UX requirements or attach a Figma link in the "Design" section.
- [ ] No
- **Does it need API design?**
- [ ] Yes. Specify the endpoints, methods, or data structures needed.
- [ ] No
- **Does it need design around state flow?**
- [ ] Yes. Outline the state flow requirements.
- [ ] No
- **Does it need a test plan?**
- [ ] Yes. Add the test plan as a comment in this task or attach the document.
- [ ] No
---
### User Stories
- **As a** [user type],
**I want** [functionality],
**so that** [benefit].
---
### Design
- **Figma**: [Insert URL]
- **Design Docs**: [Insert URL]
---
### Dependencies
-
---
### Additional Notes
-
---
### Related Issues
-
Contributor guide
No contributing guide indexed for this repository
Research direction
No implementation files, entry points, tests, design, user stories, or API-key requirements are named. Start by resolving the service choice and UI/API-key design for search in both collection and edit experiences; done should include an agreed design and a working, tested search flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100