Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Country-specific Address Formats #213

Open
pyrog opened this issue Dec 17, 2014 · 6 comments
Open

Country-specific Address Formats #213

pyrog opened this issue Dec 17, 2014 · 6 comments

Comments

@pyrog
Copy link

pyrog commented Dec 17, 2014

I would like to test existing Country Address Format. The goal is to create some for my country.

Could you give me some query/examples that display adresses in theses format ?

@mtmail
Copy link
Collaborator

mtmail commented Dec 17, 2014

To my knowledge the configuration on that wiki page is not used (yet).
Have a look at the configuration and test cases in https://github.com/lokku/address-formatting/ . Always looking for more test cases.
To create pretty output you need a formatter which interprets the Nominatim data output. There is one written in Perl https://github.com/lokku/perl-Geo-Address-Formatter, somebody is working on Python and Javascript.

@lonvia
Copy link
Member

lonvia commented Dec 17, 2014

Indeed. If this feature ever gets implemented, it's much more likely to use the data from the lokku project.

@pyrog pyrog changed the title Ho to use Country Address Format How to use Country Address Format Dec 20, 2014
@lonvia lonvia changed the title How to use Country Address Format Country-specific Address Formats Aug 8, 2015
@freyfogle
Copy link

Just to update this issue, the address-formatting repo has moved to https://github.com/OpenCageData/address-formatting

we now have 100% coverage and 86% of territories have at least one test. Slowly I am adding more, I expect 100% test coverage by 1 April 2016. Of course there are many, many edge cases, so more eyeballs and tests are definitely needed. All help much appreciated

@RafalR
Copy link

RafalR commented Aug 19, 2016

when addresses will be fixed?
Example 1:

all valid addresses -> http://overpass-turbo.eu/s/hVV
adama mickiewicza 6, lublin -> incorrect! first result from zamość,
should be http://www.openstreetmap.org/way/319339020
adama mickiewicza 8, lublin -> incorrect! first result from zamość,
should be http://www.openstreetmap.org/node/2604114620
adama mickiewicza 10, lublin -> incorrect! first result from zamość,
should be http://www.openstreetmap.org/node/2604092061
adama mickiewicza 12, lublin -> incorrect! first result from zamość,
should be http://www.openstreetmap.org/way/352817713
adama mickiewicza 14, lublin -> incorrect! first result from zamość,
should be http://www.openstreetmap.org/node/2604099139
adama mickiewicza 16, lublin -> incorrect! first result from chełm,
should be http://www.openstreetmap.org/way/352817730
adama mickiewicza 18, lublin -> incorrect! first result from zamość,
should be http://www.openstreetmap.org/way/352817758
adama mickiewicza 19, lublin -> correct :)
adama mickiewicza 21, lublin -> correct :)
adama mickiewicza 23, lublin -> correct :)
23...107 -> correct :)
adama mickiewicza 107, lublin -> correct :)

Example 2:

all valid addresses -> http://overpass-turbo.eu/s/hVY
tadeusza kościuszki 1, lublin -> incorrect! first result from włodawa,
should be http://www.openstreetmap.org/node/833340653
tadeusza kościuszki 2, lublin -> correct :)
tadeusza kościuszki 3, lublin -> incorrect! first result from puławy,
should be http://www.openstreetmap.org/node/833340651
tadeusza kościuszki 4, lublin -> incorrect! first result from puławy,
should be http://www.openstreetmap.org/node/814991082
tadeusza kościuszki 5, lublin -> incorrect! first result from puławy,
should be http://www.openstreetmap.org/node/833340647
tadeusza kościuszki 6, lublin -> incorrect! first result from puławy,
should be http://www.openstreetmap.org/way/67508881
tadeusza kościuszki 7, lublin -> incorrect! first result from puławy,
should be http://www.openstreetmap.org/node/833340681
tadeusza kościuszki 8, lublin -> incorrect! first result from puławy,
should be http://www.openstreetmap.org/node/814991080
tadeusza kościuszki 10, lublin -> incorrect! first result from puławy,
should be http://www.openstreetmap.org/node/814991077


@saerdnaer
Copy link

FYI: iD uses a small lookup table based on country code, c.f. https://github.com/openstreetmap/iD/blob/master/data/address-formats.json

Why not use the same or a similar lookup table to generate a places' display_name attribute?

@Bibi56
Copy link

Bibi56 commented Jul 1, 2020

Just to update this issue, the address-formatting repo has moved to https://github.com/OpenCageData/address-formatting

@lonvia, Apparently one implementation of this exists in PHP: https://github.com/predicthq/address-formatter-php, any good reason (except time ;-)) not to use it?

@lonvia lonvia added this to 4.0.0 in Planning board Jul 27, 2020
rotdrop added a commit to rotdrop/nextcloud-maps that referenced this issue Nov 16, 2021
rotdrop added a commit to rotdrop/nextcloud-maps that referenced this issue Nov 16, 2021
…ay name.

See upstream issue osm-search/Nominatim#213

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-maps that referenced this issue Dec 30, 2021
rotdrop added a commit to rotdrop/nextcloud-maps that referenced this issue Feb 11, 2022
rotdrop added a commit to rotdrop/nextcloud-maps that referenced this issue Mar 9, 2022
rotdrop added a commit to rotdrop/nextcloud-maps that referenced this issue May 24, 2022
rotdrop added a commit to rotdrop/nextcloud-maps that referenced this issue Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Planning board
  
4.0.0
Development

No branches or pull requests

7 participants