Modify ↓
#17036 closed defect (fixed)
"Way terminates on Area" validator warning should not be raised for ways that are explicitly tagged as ending on area
Reported by: | mkoniecz | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 18.12 |
Component: | Core validator | Version: | |
Keywords: | template_report | Cc: |
Description (last modified by )
What steps will reproduce the problem?
- encounter steps leading to gate in fence and terminating there (both steps and path leading further are abandoned, but steps were made from more durable material and path was not paved, so only steps, gate and fence remained)
- tag it ( https://www.openstreetmap.org/node/6048384794 ) including noexit=yes to mark steps as not going further
- run validator
What is the expected result?
Validator is not complaining
What happens instead?
Validator raised "Way terminates on Area" despite noexit=yes
Please provide any additional information below. Attach a screenshot if possible.
URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2018-11-25 21:25:56 +0100 (Sun, 25 Nov 2018) Build-Date:2018-11-25 21:15:39 Revision:14454 Relative:URL: ^/trunk Identification: JOSM/1.5 (14454 en) Linux Ubuntu 16.04.5 LTS Memory Usage: 479 MB / 869 MB (137 MB allocated, but free) Java version: 1.8.0_191-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Screen: :0.0 1920x1080 Maximum Screen Size: 1920x1080 Dataset consistency test: No problems found Plugins: + OpeningHoursEditor (34535) + buildings_tools (34724) + continuosDownload (82) + imagery_offset_db (34641) + measurement (34529) + reverter (34552) + todo (30306) Last errors/warnings: - W: No configuration settings found. Using hardcoded default values for all pools.
Attachments (0)
Change History (3)
comment:1 by , 6 years ago
Description: | modified (diff) |
---|
comment:2 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 6 years ago
Milestone: | → 18.12 |
---|
Note:
See TracTickets
for help on using tickets.
In 14563/josm: