Modify

Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#17696 closed defect (needinfo)

misleading warning about "duplicate housenumbers"

Reported by: dieterdreist Owned by: dieterdreist
Priority: normal Milestone:
Component: Core validator Version:
Keywords: validator addr:housenumber duplicate Cc:

Description

The duplicate housenumbers warning is forcing a certain mapping style on the mappers which is not universally useful: in Italy (and likely in some other place as well) the housenumbers refer to entrances (of properties or houses), so it is agreed they should be mapped as nodes.
On the other hand, mappers also want to store explicit address information of features. The result is duplicate occurences of addr:housenumber, one as address on a feature and one on the gate or entrance.
If we would require addr:housenumber to be unique we would have to create relations to assign the same address to multiple features for most of the features in the country.

Attachments (0)

Change History (5)

comment:1 by Don-vip, 6 years ago

Owner: changed from team to dieterdreist
Status: newneedinfo

Please attach an example.

comment:2 by Klumbumbus, 6 years ago

Duplicate housenumbers are not reported if they are POIs. POI means in this context "has one of these keys": "shop", "amenity", "tourism", "leisure", "emergency", "craft", "office", "name"

comment:3 by dieterdreist, 6 years ago

I must admit I don’t recall the object where the false warning occurred, looking at the list it was probably some “historic” tag. I’ll keep an eye open and update this when I can provide more details

comment:4 by Klumbumbus, 6 years ago

Resolution: needinfo
Status: needinfoclosed

OK, please add the example here if you find one again.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain dieterdreist.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.