Places: search returns bad coordinates

Open
#1,044 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, java
Domain
mobile-dev, search

Research direction

Start with the Places search feature in the demo app and reproduce the coordinate mismatch using the Portland Starbucks examples in the issue. Trace how selected search results become map markers, then verify that returned coordinates match the expected locations on the affected devices. Done means the marker is accurate for these cases and the regression is verified.

Written by the indexing model from the issue text.

Description

confirmed

The search feature returns coordinates up to several blocks away from the selected location. This happens in both my own app and the demo app, tested on 2 different devices. These pictures from the demo app show the marker and expected location of several Starbucks locations in Portland.

419_sw_morrison
555_sw_oak
910_sw_2nd
1039_nw_couch

Dominant language
Java
Stars
242
Forks
116
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/mapbox-plugins-android

All issues in mapbox/mapbox-plugins-android

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.