nextcloud / nextcloud/maps

Wrong geo position for an adress. It seems that the townname is ignored

Open
#535 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
598
Forks
113
PR merge metrics
No merged PRs in 30d

Description

I added a contact with
Name, Street + Number, Postal code and Townname.
The Marker is placed in another town nearby (with an other town name of course) which has the same postalnumber and also has a street with the same name.

Example - Contact:
Peter Pan
Famous Street 10
22419 Whereever

Example - Wrong Marker at:
Peter Pan
Famous Street 10
22419 Example Town

My guess is that the town name is not taken into account, because most of the time the key with street and postal code is unique.
If this is the case it would be an easy fix.

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.

Research direction

No file or test is named in the issue. Start from the address geocoding flow and reproduce the example with two towns sharing a postal code and street name; trace whether the town name is passed to the lookup. Done means the marker resolves to the contact's town without breaking other address searches.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.