keplergl / keplergl/kepler.gl

[Bug] Geocoder fails to find a locality

Open
#1,642 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
12k
Forks
2k
Avg merge
1d 5h
Merged PRs (30d)
66

Description

**Describe the bug**
Geocode does not find the "Forest Hill" neighborhood of San Francisco, even if the map is right over it.

**To Reproduce**
Steps to reproduce the behavior:
1. Open the "Interactions" side menu
2. Enable "Geocoder"
3. Move the map until it is over the "Forest Hill" neighborhood of San Francisco
4. Enter "Forest Hill" into the Geocoder's search box

**Expected behavior**
Search results from the area the map is open over are given higher priority in search results

**Screenshots**
Screen Shot 2021-10-10 at 9 30 38 AM

**Desktop (please complete the following information):**
- OS: macOS
- Browser: Chrome Beta 95
- Version: production

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the Geocoder entry in the Interactions side menu and reproduce the search for “Forest Hill” while the map is centered on the San Francisco neighborhood. Trace how the visible map area affects search-result ordering; done means nearby results receive higher priority and the reported search returns the locality.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.