geocoder-php / geocoder-php/Geocoder

Nominatim geocoder - returns different results for postalcode before vs after city name

Open
#1,114 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

provider
Dominant language
PHP
Stars
4k
Forks
525
Avg merge
8m
Merged PRs (30d)
1

Description

Maybe this is not an issue of geocode-php/nominatim-provider , it maybe an issue of Nominatim itself:

https://github.com/osm-search/Nominatim/issues/2167

But Nominativ has closed the issue instead of solving the problem.

Please check the problem and example on https://github.com/osm-search/Nominatim/issues/2167 and help to solve this problem.

Thank you.

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

Start by reading and reproducing the example in the linked Nominatim issue 2167. Then compare the provider's behavior with Nominatim's response for postalcode-before-city versus city-before-postalcode queries. Done means establishing whether the defect belongs in this PHP provider and documenting or implementing a confirmed resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.