Modify ↓
Opened 16 years ago
Closed 14 years ago
#2255 closed defect (fixed)
incorrect warning report about addr:housenumber
| Reported by: | hatzfeld | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core validator | Version: | latest |
| Keywords: | address node | Cc: | hatzfeld, delta_foxtrot@… |
Description
Nodes and ways which have no other tags than addr:* should NOT be checked for low distances to or crossings with nodes/ways which do not have such tags.
It is not a mistake if an address node (which easily is a "way end" of addr:interpolation) is situated closed to a road or to the border of a residential area.
Attachments (0)
Change History (8)
comment:1 by , 16 years ago
| Cc: | added |
|---|---|
| Version: | → latest |
comment:2 by , 16 years ago
| Cc: | added |
|---|
comment:3 by , 16 years ago
| Priority: | major → minor |
|---|---|
| Version: | latest → tested |
In version 1788 of JOSM (validator version 16439) it is improved: intersections of addr:interpolation with roads don't trigger any more. But address nodes close to roads still do it.
comment:5 by , 15 years ago
| Keywords: | node added; nodes and ways removed |
|---|---|
| Priority: | minor → normal |
| Summary: | incorrect error reports about addr:interpolation and addr:housenumber → incorrect warning report about addr:housenumber |
| Version: | tested → latest |
comment:7 by , 14 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Sorry. Validator does not find any "way end node near other way" right now.
comment:8 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Note:
See TracTickets
for help on using tickets.
Is this still an issue with the current code?
If it's still a problem I can try and take a look at it if you can provide me with an example area to test.