Modify

Opened 3 months ago

Closed 3 months ago

Last modified 3 months ago

#23876 closed enhancement (wontfix)

Ignore "duplicate housenumber" for node "entrance"

Reported by: MichaelFS Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: template_report housenumber Cc:

Description

for an existing building an entrance is mapped, this node should have addr*-keys (ref. OSM-Wiki). Typically, the building also has addr*keys (ref. OSM-wiki.
In such cases, after any modification for the node "entrance" or the way "building" JOSM claims an error "duplicate housenumber".
In my eyes, JOSM should not run the "duplicate housenumber"-test for nodes "entrance".

Attachments (0)

Change History (3)

comment:1 by taylor.smock, 3 months ago

We can probably fix this by modifying Addresses.java. I don't know if we would want to consider entrance as a POI, but I can see arguments either way.

comment:2 by stoecker, 3 months ago

Resolution: wontfix
Status: newclosed

I'd say mapping the house number to an entrance makes no sense except you have more than one entrance with different numbers in which case mapping the house number to the building makes no sense. So the warning is valid.

For single entrance buildings map the entrance without any additional tags. The tags go to the building. For multi entrance buildings with different numbers map the numbers to the entrance, but not to the building.

The first wiki page you link also states this:

Add a node node at the building outline and tag it with entrance=yes.
The house number should be added at another node in the building or at the building itself. 

comment:3 by skyper, 3 months ago

Component: CoreCore validator
Keywords: housenumber added
Type: taskenhancement

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
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.